ROM Won't Flash - G2 and Desire Z Q&A, Help & Troubleshooting

Jeeze, after all the tinkering that I have done with this phone in back in the days, you'd think I would know what to do in this situation haha. But if anyone is still out there, I'm having a bit of an issue. The one rom I want to flash on this phone so I can temporarily use it for a few days whilst in between upgrading phones, Desire Gingerbread Sense v1.2 refuses to flash for some reason. I keep getting Status 0, installation aborted in CWM and I have never had the issue in the past, same file I have used in the past as well. I originally thought it might be due to it having an EXT 4 filesystem from a prior rom, but I flashed a few GB roms and then tried reflashing it, and still spitting out the same thing. If I solve this on my own I'll post my remedy, just found it odd.
-Edit-
Welp, exhausted all options. Redownloaded the file, tried different recoveries, formatted my SD card, etc to no avail. Turns out in the end it wasn't worth it since the SIM slot no longer reads SIM cards. So, time to bust out my ancient iPhone 2G as a temporary phone for a few weeks xD
-11/29/15 Edit-
Yet another update on this. I'm one to not give up on certain things so I mildly opened up the phone and managed fixed the sim slot, no progress on the rom getting to flash though

Related

Constant boot loop, all ROMs...

My phone is mullered :-(
Whenever I flash a new ROM, all I get is a constant boot loop on first boot.
Flashing a different ROM results in the same behaviour.
The only way out of it is to re-root, taking me back to version 1.15 or something, and then if i try to flash a new ROM - you guessed it, boot loop....
This first started when I had OpenDesire installed, which was fine to begin with, but then it randomly rebooted and started boot looping.
Since then I've tried about 4 or 5 different ROMs and nothing changes.
Any ideas as to what's wrong/a solution?
Just to add, I have one the lastest radios (.08) when I try and flash.
Perhaps flashing the radio after might help?
After much struggling, I've managed to sort it.
Ended up clearing storage in recovery, which helped so long as there was no SD card in it. Had to format and repartition the card, and fingers crossed, all seems well now.
Whenever you change between diferent ROMs it is a good practice to do a full wipe via recovery. 90 to 99% of the boot-loops can be fixed doing it...
The strange thing is that I did wipe between ROMs. I'm not sure why I had a problem this time round, as I haven't had with the previous 10 flashes...
Still, it's sorted now
Funny.. found this thread via google.
I'm having the exact same issue where no matter what rom I flash it gets stuck on bootloops during the startup animation and never makes it into the rom.
NANDroid backups are perfectly fine to restore, just unable to flash any new roms. Spent all last night trying everything from swapping recoveries, to re-rooting, flashing multiple roms, urgh.
Only thing I didn't try is re-formatting the SD card so gonna give that a go now (thanks to this thread) and report back later.
Annoying to say the least.
Well what do you know... a 'partition my SD card' through rom manager (after copying said contents to my computer) worked a charm.
Most interesting......... Praise this thread and any others that gain help from it.
Did you update your radio ?
Sent from my spectrum zx
Man i'm lucky. Two hugely annoying problems in one go.
First up, yes I have replaced my radio, many times The SD card was obviously not too happy with its ext partition, so repartitioning that worked.
I also had another issue crop up straight away that was probably caused by unhappy sdcard, where when restoring apps via titanium backup, phone would reset.
After running a RRU, re-rooting, all the full works.. I find that some of the apk backups are 1kb... Which is not normal. There were about 15 apps like this. I had a backup of these apps from a week or so ago and copied those to the titanium backup directory, restored, no problemo.
Even more annoyingly TB has a verrify backups option which reported all was well. FML.
Well that was a fun morning. Time to finally get back on track *sighface*

Need Help!!

Hey
I apologize if a thread like this has appeared before, but i have just about had it with playing about with my desire after i tryed to flash a new ROM, il try and explain is as best detail as i can, and hopefully, one of you will be able to help me get back to normal, as im tearing my hair out over this now...
So...Last night, i noticed that LeeDroid (The custom rom i use) had updated his firmware to 3.0, and in the interest of keeping my phone upto date, i went ahead, downloaded the rom, put it on my SD, did a nandroid backup, wiped and flashed as i would normally
the install seemed to go fine, but when i rebooted the phone, it hung on the HTC screen for about 15-20 mins, so i figured the flash hadnt worked, so i went back, wiped again and restored my backup
this is where the issues begin, the bacup restores fine, BUT, when the phone reboots and loads up, ALL of my apps etc have gone, no longer apparently anywhere on my SD card (which is where most of them were stored) I now had a bare bones android, with no apps (not even market, as that was updated manually too)
at this point, i start to panic, i have seemingly lost everything off the phone (apart from the SD backup i had performed before), and only have a bare bones version of the LeeDroid rom i was using before, with no apps what so ever
so, i thought, i might as well start afresh, so i boot back into recovery, wipe again and re-flash a fresh Leedroid rom, which seemingly again, goes fine, but again, hung on boot
getting more worried still, my SD-EXT then stops mounting, giving me an error, so i re-partition it, format it, and try again, and again, it still hangs on boot
at this point, i realize im screwed, and just restore the bare bones backup i had saved on my computer (nandroid), which at least allows the phone to boot and be semi-usable
i have no idea what im doing wrong here, nothing wants to flash anymore, it just hangs, and i cant even seem to un-root the phone, all the RUU's i use just give me a "CUSTOMER ID ERROR" which i have no idea how to fix
can anyone PLEASE point me in the right direction, im panicing here, i cant seem to get anything to work, and i have been going around in circles for almost 7 hours now...
thanks very much
Looks like you'll need to start from sguare 1 again. Seems like the SD issue, might have corrupted the SD card.
My suggestion, is that you format the sd card (backup all files to the pc)
Create a new gold card again.
Flash to stock again if need be, then root.
You can download googleapps and flash it also. There are some downloadable links in this site you can save to your sd card. Or you can download it at cyanogenmod.com (where I downloaded mine I believe).
i thought going back to square one would be the way forward too, except that i cant seem to find an RUU that will work, as i mentioned, all of the ones i have tryed give me the CUSTOMER ID error, which i have no idea what to do with...
so, im a little stumped..
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Moscow Desire said:
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Click to expand...
Click to collapse
i have a stock froyo RUU, should i apply the goldcard, then try the update again then?
im new to this, so im probably going to need taking through all this
edit: so i made my SD into a goldcard. and now it wont mount on the phone, and when i run the RUU, it still gives me the CID error..
im going insane here, someone help >.<
ok, i got it
after doing some reasearch, i found that alot of people were saying that the phone needed to be S-OFF to flash it correctly
so, after reading up, and S-OFFing, i wiped, partitioned and flashed...
and, finally, after 9 hours of tinkering, errors etc, it has flashed and booted
this can be locked now, thanks
partitioned th sd card,
works sometimes, but glad we could somewhat lead you in the right direction, by proxy........
Little puzzeled by the s-off, but hey, it's fixed!!!

Can internal memory be corrupted??????

Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one

[Q] Evo vibrates 5 times on boot, only hboot accessible

A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
VaughnOnix said:
A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Click to expand...
Click to collapse
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
nrm5110 said:
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hboot finds the renamed CM7.1 zip and checks it, but does not offer to flash it. I assume this is because s-on is back. Also, I mentioned that RUU is claiming my battery is too low to flash.
OMGWTF_BBQ said:
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
Click to expand...
Click to collapse
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
I appologize I didn't see it man
Sent from my PC36100 using Tapatalk
VaughnOnix said:
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
Click to expand...
Click to collapse
Sorry, my previous post was in a rush. (As is this one, lol)
Really? So your phone just screwed up out of no where while flashing the ICS alpha4 rom? Were you using CWM? Because if so, I'm switching to Amon RA asap.
Moving on, I know how you're feeling right now. But, I still have hope.
As previously stated, after ruining my EVO I was able to flash a PC36IMG.zip that allowed me to boot my EVO. I had to do some serious digging, but I found the thread I used with the ROM that worked http://forum.xda-developers.com/showthread.php?t=884060.
None of the old Megaupload links work, but this filesonic one does. Download it and flash it in your bootloader. Its signed, it should work. Try to flash it twice if anything. If it still doesn't work, try one of the newer ROMs. I'm only guessing that's the one that worked for me.
The only problem is that I don't think that's a 2.3 ROM, and we need a 2.2 ROM. Because the only root method that doesn't use a USB/SD Card is this: http://forum.xda-developers.com/showthread.php?t=701004 If you can get
If you can get your EVO rooted again with S-Off, follow this guide here: http://forum.xda-developers.com/showthread.php?t=695243 (Original) and you might be home free. But as of now, your goal is to find a stock 2.2 PC36IMG. Hopefully someone else can help here.
I sadly have to get to bed. Just got off work and I need to get some rest, another long day tomorrow. Good luck! I'll be back here next chance I get.
Same thing here
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Update on previous post
spoonydx said:
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Click to expand...
Click to collapse
*** Update ***
Ok, so after all that, I was able to restore my backup from within recovery, copy all of my data back to the sd card, and now I'm back in business...mostly. I still get the 5 vibrations on boot *unless* i'm plugged into the computer, and even then it's not a sure thing (usually takes 3 or 4 tries to get it to boot). At least I have a functioning phone again. Next step - RUU and factory reset, and see what happens. Again, I'll post back with my results. Hope this helps someone

[Q] Bootlooping

So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A

Categories

Resources