So I went to flash a new rom from my miui and did a data/cache wipe then flashed the new rom downloaded from this forum and now im stuck on the HTC Incredible screen.
Tried:
Restoring
Flashing new roms
wiping and clearing data/cache then installing different rom
Please help me.
What version ClockworkMod/HBOOT/Radio are you? Sometimes I can wipe a few times in a row and reflash in that situation but your results may vary
Could it be the classic amend/edify update script problem.
Edit: just read you tried restoring..sorry..try alternate recovery. If all else fails ruu, I doubt your bricked bud. That would be nearly impossible
Try the info in this thread not sure if you know about applying the stock image to your sd card through hboot and restoring your phone goodluck
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
http://forum.xda-developers.com/showthread.php?t=739428
Related
I have been trying a number of different methods to fully root my EVO, yet for the life of me, cannot get a new ROM to flash properly. Each time I try flashing a new ROM, I end up in an endless boot loop & must go back into my SD card & rename my stock ROM back to 'PC36IMG.zip' in order to get out of it. I have heard that this sometimes happens from not erasing the dalvik cache, yet I have tried that too & still no luck.
Does anyone maybe have some pointers on why I may be experiencing this issue each time? Any input would be greatly appreciated! Thanks!
you rename your stock rom to pc36img.zip? What is a stock rom? Where did you ever read to do that?
I don't know what directions you read, but Something is very wrong.
Well it's A stock ROM that I picked up during the many different methods of rooting I have tried... For some reason, that has been the only way to get my phone to boot after trying to flash a ROM to it...
Most of the time if you wind up in a boot loop after flashing a new rom it's because you didn't wipe data, cache, and dalvik cache before flashing.
If you are using clockwork recovery it may be your problem. It has been reported to not complete wipes fully leading to post flash boot loops. Try amon-ra recovery.
Hi,
I was hoping some of the smart people here might be able to point me in the right direction for a solution to a problem I am having.
As the thread subject says; I've flashed several ROMs based on the official 2.2 release and I end up with a boot loop at the first HTC logo, it never makes it to the quietly brilliant screen, it just re-boots continuously until I pull the battery.
However, ROMs based on 2.1 boot fine, both official ones and modified ones obtained here on the forum. Also, the 2.2 based DeFrost ROM boots fine.
The actual flash process seems to go fine, with no errors being reported.
I've tried wiping/factory reset before I flash, after I flash, but the result is always the same.
I've tried with and without the latest radio installed.
I've tried booting with the SDCard and SIM removed, but no luck.
I've even tried downgrading from bootloader 0.80 to 0.75, again with no difference.
A bit of background info;
My Desire is a generic unbranded model.
Yesterday, I did try to install the OTA 2.2 update, but something messed up during the flash process and I ended up with a corrupted recovery partition and (once again) a boot loop.
Thankfully, I managed to flash an older RUU file and things are back to normal, except for the in-ability to boot any ROM based on the official 2.2 release.
If anyone can help I would be forever in your debt, as this really is driving me crazy.
I had the same problem when I installed the new 2.2 HTC ROM without wiping...
Anyway try to wipe both factory reset and all caches with both amon ra recovery port and clockwork recovery...
Same problem... but fixed I fixed it installing this: http://forum.xda-developers.com/showthread.php?p=7483900
I have same same loop like that
I dont know why? I use r5 modaco custom rom. it seems well. but when I try to use edge/3g, it starts loop booting. if turn off edge/3g, the phone works perfectly.
after that, I tried to flash another ROM, Wipe Factory reset, Wipe Cache, Wipe Dalvik, even wipe ext but it still happens
I put out SIM, the phone boot correctly( maybe just reboot one time). but put SIM in, it reboots.... sometime the phone vibrate 5 time at HTC screen .
somebody can help me?
ps: how to know wipe dalvik work perfectly? I cant see any info about it done
I had the same problem with the first rooted official rom I tried to install, then I restored to my modaco mcr-r5 (2.2) rom, updated to the new radio and then installed the rom from nickiberli via rom manager and it worked.
btw, I selected wipe data in rom manager when prompted, lost all my apps and data but the setup wizard ran when it booted up first time.
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
raz2133 said:
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
Click to expand...
Click to collapse
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
ratykat said:
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
Click to expand...
Click to collapse
Thanks for the suggestion, but I just tried this ROM and it wont boot for me either.
bakedecake said:
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
Click to expand...
Click to collapse
I do have an ext partition on my SDCard and I have tried ROMs with and without A2SD. In fact, the ROM I have used for most of my tests is "Rooted Official HTC Android 2.2 (FroYo) ROM [Market issue fixed]", which I don't think has A2SD.
I have tried booting with 3 different SDCards so far, and of-course I have tried with no card.
I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
whyteboyello said:
I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
Click to expand...
Click to collapse
Did you try fixing permissions? I hear doing that can help fix constant fc's. You can do it either through ROM Manager or in recovery. The only way I know how to do it in recovery is in Clockworkmod, as I have not tried out amon_ra. Advanced > Fix Permissions.
Sent from my Droid Incredible running CM7.0.3.
Have you tried flashing peanut and formatting internel storage, wiping sd card and reformatting to fat32? What ever you do, never restore data, it will cause issues.
Sent from my ADR6300 using XDA App
whyteboyello said:
I have been searching like crazy through every thread on every forum and cannot find anyone with a similar problem. I had CM7 running fine then everything started force closing. I wiped data/cache and dalvik cache and reinstalled CM7 and now cannot get past the Splash screen. I went into HBoot and flashed the stock RUU went back to stock re-rooted tried everything again and cannot get past the splash screen again. Tried to flash a stock PB31IMG with s-off already and that booted fine. Flashed clockwork through a PB31IMG and got to recovery tried to wipe and install and same results. Did everything I just did back to stock then flashed the alternate recovery same issue. Anyone have any idea why I cannot get a custom rom going?
Click to expand...
Click to collapse
did you reroot after flashing to stock just b.c. your s-off and flash a recovery dont mean you can flash a rom successfully... i would run the ruu again then reroot with unrevoked...... then wipe and flash again.. if that dont work then you prob have a harware problem
Are you doing wipe data/factory reset, wipe cache, and wipe dalvik cache?
Sent from my ADR6300 using XDA App
Thanks
Hey guys thanks for the response, I was about to give up and stay on stock sense and for the hell of it tried root wipe and install again and it worked. No clue what was causing me issues so I am probably going to stay on my current setup for now haha
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
jethro650 said:
What rom were you on and what rom were you trying to flash originally? Also what recovery are you using? Need a little more info because usually wiping caches dies the trick. Provide a link to the rom you were trying to flash of your can.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1986893
This is the rom, i was using CMW to flash it, then it made me switch to TWRP (think its called that)......hope that helps.
Sorry I can't be of more help aside of redoing the installation of your recovery and redownloading the rom ( bad downloads happen) and making sure you do all the wipes (cache, dalvik cache and factory reset). If none of that works I'm sure someone more knowledgable than myself will chime in.
I've never run into a bootloop problem myself, but this might help you out :
hxxp://galaxynote2root.com/galaxy-note-2-tutorials/how-to-unrootunbrick-galaxy-note-2-with-stock-firmware/
Good luck
Have you had any luck with this yet? I've been unable to get my phone back up.
QuantumPSI said:
Have you had any luck with this yet? I've been unable to get my phone back up.
Click to expand...
Click to collapse
No luck, but then again i am a Mac user, so its a little more difficult for me to solve this problem.
Anirchy said:
I tried installing a rom last week on my Galaxy Note II (Rogers), i followed orders (this isn't my first time flashing roms), and it has been stuck in a constant boot loop.
I've tried everything, wiping cache, factory reset, tried to flash different roms, etc....
I am a mac user (which means Odin isn't an option).
If you guys have any suggestions on how to fix this it would be greatly appreciated.
Click to expand...
Click to collapse
Put another ROM on an sdcard. Take your battery out then press the button combo for recovery mode before you slip your battery back in. Then it'll force download mode. Reflash the new ROM after full wiping and you should be good.
Sent from my SGH-I317 using xda premium
Definitely a bad ROM. Run a MD5 checker against it prior to copying to the SD card. Note: your SD card could be the culprit.
If you have a recovery installed, ensure you WIPE everything, Fix permissions (i'm on CWM) and reflash the modem and carrier files POST rom install.
I experienced my first boot loop yesterday but I was able to recover from it thanks to a little common sense and patience. :fingers-crossed:
Good luck!
first of all, don't freak out, a bootloop isn't the end of the world. Sounds like it was a bad flash.
ppl above have obviously told you to wipe caches, and all that stuff and if it hasn't worked then you are still down and out.
I would suggest you get yourself into recovery - not going to explain that here as you said you were able to flash other roms and it didn't work and try flashing your nand backup - hopefully you have a nice clean backup from before you flashed. if so, clear caches, etc and then try flashing it it should be back to at least working.
your nand backup will have all your stuff in it as you would have had to backup from recovery, which means you'll at least still be rooted. you can then go ahead and get another rom - check the md5 and flash it
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.