This is my wifes phone she got it used about 8 months ago. Rooted shortly after receiving it but never did S-off. I didn't want to brick it.
She used Haxespresso for the longest time and then switched to SS21v2 after about 3 months of use. She got about 3 maybe 4 weeks of good use out of it and then she emailed me while I was at work and told me that her phone was stuck on the mytouch splash screen.
I guided her through clockworkmod to wipe things clean to get it working again. Then two weeks later it started looping. The only way to get it out of the loop was to wipe everything and then reflash the rom. It did it again and so I switched her to CR_Mod_2.13.531.1_OTA and I thought everything was kosher.
Then tonight she went to pick up her phone and it was looping again.
What might this be? she uses DT's app2sd with the a2sd GUI with a 1 gig ext3 partition, which by the way has never mounted in CWM. It always throws and error for me and I have to manually format the partition through my card reader on my desktop.
any help on this would be great!
Related
I flashed to pays rom, successfully yesterday.
today, i wanted to wipe my phone (entered wrong gmail account so didnt have access to paid apps)
after doing so, ive been stuck in an endless boot screen.
anyone shed some light on the situation?
Oops. I think this happened to some G1 roms too.
Reflash?
the rom was absolutely flawless before this.
ive tried.
with 2 different roms.
wiped everything i possibly can in recovers & fastboot
insult to injury; recovery-windows wont load, so i cant even get past recovery screen.
My mistake. recovery-windows is loading. now flashing. again.
so then, managed to flash some sense based roms alright, until i get past bootloader.
com.android.acore error messages all the time.
loaded nexdesire rom fine with no errors.
ideas anyone?
Out of interest, did you re-partition your SD Card for A2SD at all??
If so... Try re-partitioning it again in recovery mode, but use it all as storage (no ext partition), wipe and re-flash.
I did.
I'll try that now and pray it works
Get in!
Working absolutely fine now
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Same thing just happened to me, thi is the second time
lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk
I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.
It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.
Good for you. hopefully my new phone will behave
First i ran the phone with stock 4.0.2, and one morning when i woke up(the phone was in the charger) the phone was in a boot loop(turned off when the google letters came up), so I ended up with a factory reset.
Some days later I rooted the phone and installed AOPK rom and installed google apps. 2 days later it got into a boot loop again, but now it booted all the way till where I tyoe in the SIM code, if I did it really fast I could also get past the sim code but just seconds after it booted again. I tried everything from CWM, restore an older backup, wipe cache/data but the phone couldn't find the boot or something like that. So ended up push adb stock rom.
Is this something thats normal? I got 2 friends with the same phone, never had any problem, they both run stock 4.0.2.
I too had a problem with my Gnex, it kept freezing up and switching off, if you are getting this problem on stock and custom roms its likely hardware, so send it off to Sammy, just a heads up but mine was sent off 10.02.12 first time then 2 more finally they said thay would replace it .... That was a month ago, rang them yesterday and they said it would be another week .. what I'm getting at if your insurance could offer a quicker fix I'd go with that
Have you tried flashing google's stock images and going from there?
Yeah, I did flash 4.0.2 stock again from that site, been running it for 2-3 days now.
OK, I seem to be having a hell of an issue with my note 2. I rooted it about a week ago and installed TWRP, a couple days ago I decided to try a new rom. It booted up and everything seed fine except that I would keep getting some type of out of service error, so I decided to try a different rom, SwampMonster. I installed it though the TWRP (obviously) and it was successful, at least so TWRP said anyways. So Upon first boot it seemed to be booting fine with the Orange circle and after about 20 seconds it stops and the screen went black. As I have seen this plenty of times before I let it sit for over five minutes. Also when the Orange circle disappeared the computer beeped to indicate that it had been disconnected. Now I can only get into recovery and kies will not connect. I also cannot access TWRP.. can anyone give my a bit of advice. I was thinking of using a rom that I can install with oden but I can only find zip file based roms. Thanks in advance. Oh also, ODIN does make a connection
Hello. First post here, want to say thank you to everyone that works hard on these images and boards, you all do a great job.
Here's my issue, and I'll try to be as specific as I can. I'm semi-new to all this but I had someone helping me that knows a lot more than I.
Recently, I got an HTC Inspire HD (Same thing as the Desire HD) on the AT&T network. It was a freebie, so I decided to flash some custom stuff on it.
Currently, my backup image is ClockwordMods, and the main OS, I first tried Cynogenmod's unofficial 11 version. When that failed, we removed it and attempted Xperia4.4.2-beta-2 with OTA-2.0.1-for-Beta-2 and ota-2.0.2-for-Beta-2. I used philz custom touch interface which works beautifully. I followed the directions to a T. wiped the phone for a new image, wiped all the cache (even under advanced as it told me), and flashed in the new OS, rebooted, flashed in OTA 1, reboot, flashed in OTA 2, reboot. But it hangs on the HTC screen. Now, it's not bricked, as I can still access the menu.
here is what is getting me. I loaded on an image called PD98IMG found here:
http://forum.xda-developers.com/showthread.php?t=1248608
It rebooted, but it hung at Parsing for 20 minutes. So, after spending 12 hours trying to remove the battery case (Whoever invented this phone can die, and more like 3 minutes, but still a pain in the butt) I popped the battery, rebooted and mounted the SD card and removed the PD file. However, when i got into the bootloader, it would still look for this file! So I put it back on, and now it hangs again at Parsing. So this morning I bought a mini-SD adaptor, slapped it in the PC and removed the PD file again, redownloaded it, and attempted it again. This time it took, it parsed for about 2 seconds and seemed to be fine. So now, I rebooted the phone, and let it sit on the HTC screen for about 15 minutes (5 is norm from what i'm told, 10 is long, I figured 15 was safe), and nothing. It still hangs. I'm going to attempt another flash and put Cynogenmod 11 back on and see if it could be a bad download, but this is where I'm stuck at. Any help would be appreciated. Hopefully this was enough detail.
Edit: Ok, I put cm-11-20140609-UNOFFICIAL on from http://forum.xda-developers.com/showthread.php?t=2533007, i wiped data, cache, etc etc, everything, and still hung on the HTC screen. Not quite sure what's going on.