Related
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7
Hi all,
yesterday my desire GSM running CM7.0 (running for many weeks/months) experienced some problems not showing some menu's, empty, no icons etc. So i rebooted, and.. got stuck on HTC/white bootscreen. After this I did the following:
- mount sd to pc, clear catch, factory reset in CWRM.
- put back a backup of android 2.2 (Defrost) works fine!
(but i want to go back to CM7).
- Trough RomManager tried to install CM7 --> stuck at boot
- In CWRM tried to install CM7 --> stuck at boot
- Wipe Davik, system, cach everyting, then installed CM7 --> stuck
- Installed android 2.2 rom --> works
- Installed android 2.3 rom --> stuck
Am I missing something stupid here? Forgot to do something?
Thanks in advance for all your help
HBOOT says:
BRAVO PV1 SHIP S-ON
HBOOT 0.93.0001
RADIO 5.11.05.27
(maybe something else:
When i install Rom of defrost this is the log:
Installing update
formatting cache
deleting files
coping files
formatting system
copying files
formatting boot
writting boot
installation complete
when i install CM7 it only tells me:
installing update
installation complete
of course formatting data and cache i did manually, but not formatting boot and system... but if i format boot, and something goes wrong starting up.. will this brick my phone? I Guess yes)
Hello.
Don't try anything else that ain't recommended. It is very hard to brick the phone, but if you bricked it, then he is gone.
Anyway I see that your Radio is not up-to-date. Usualy CM7 recommends any radio that is 2.2+ compatible. It will do you no harm if you try to upgrade your Radio to 5.17.05.08 (it's not the latest but the one before it; most people agreed this one performs better than the latest one, but this differes from phone to phone, also region, sim etc.).
How to flash Radio (CWM Recovery):
Code:
1. Go into recovery
2. Choose install zip from sd
3. Choose zip from sd
4. Confirm
5. Reboot
6. The phone will then reboot a couple of times. This is normal. Do not touch or move the phone during the process.
OR if you are used to fastboot commands:
Code:
fastboot flash radio c:\radio.img
After this Wipe everything again (User Data, Cache, Dalvik-Cache) and install CM7 again.
Hope this helps you.
I doubt it's radio, it would boot just fine even with old radio, do you have any partitions on SD?
Thanks for you reply's.
I managed to fix it, how ... and why everyting happend is not clear to me
I thought about the radio too since there are always warnings everywhere about having the correct one, but since i have no real clue what it precisely does, and my previous CM7.0.0 worked fine I had doubts.
I installed android 2.2 for the night (I needed a alarm in the morning) that worked fine. But next day when I tried to put on CM7 It failed (again). But now going back to android 2.2 failed too! And I got error clearing the extra partition (I didn't receive those before!) I though I wait to fix the ext3 partition till I managed to get CM7 working again.
Thanks you your tip, I paid more attention to the ext partition and got Gparted installed and recreated the partition. Now everything went smooth again, and got CM7 installed! Thanks!
(still couple of questions left:
- how can a rom force the phone on restart to suddenly go into a bootloop
- was this the whole-time related to the extra partition?
- why could Linux access the ext partition when I backedup my data trough CWRM, and later when CW gave me error, Linux did too!?
- Is this common error, or is this something new?
)
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
go to http://forum.xda-developers.com/showthread.php?t=1074445, choose the stock rom for your device and flash it.
it's that simple? awesome! thanks so much
::EDIT::
not working
it keeps bringing up an error when trying to install the rom :s
also tried to install using the rom.zip by choosing install from zip in recovery menu...no joy
::EDIT::
trying a completely fresh install of CM7, wipe everything, format and repartition Sd card, totally start from scratch...as this is the only thing i seem to be able to do at this point....none of the RRU's are installing....wish I hadn't tried this CM7 now :s
My cm7 is completely stable and much more responsive and less bloated than any stock rom
Dunno where your problems are coming from but I don't have any.
I'd recommend doing a full wipe and reflash of CM7. Some bugs appear at first.
Make sure you wipe dalvik, cache and full wipe before flashing.
ok guys, just completely restarted everything from scratch, wiped everything, reformated everything, cleared every possible option.
this time i installed CM7, then the google pack, then DATA2SD (before anything i partitioned the sd card 1GB/256MB)...
seems to be working a bit better...my facebook and twitter accounts are still signed in and show under the sync and accounts settings etc...
i haven't got all those FC's at boot so far....but then i didn't initially yesterday either....so we'll see how it plays out tomorrow :s
however the calendar still doesn't work well, and infact if i open it, goto menu then select calendars, i still get FC on that app :s
maybe i should just get another calendar app?
i think alot of the preview errors might have been due to the fact that i had just manually chose the "move to sd" option for all my apps instead of installing data2sd (which tricks the phone into thinking the 1gb partition on the sd card is the internal memory?)
so fingers crossed it will hold up a bit better now. like i said, i actually can't go back from CM7 now, since none of the RUU's will install. but so far so good, hopefully it will last more than a day this time :s
Gloris said:
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
Click to expand...
Click to collapse
Give it one more shot but in CWM do this:
Factory reset
Then Mounts/ Format System
Then Advanced/Wipe Dalvik Cache
Then install zip and gapps zip.
See if that clears up any ghosts in the machine. That behaviour shouldn't happen Gloris. I can assure you I've been running the release 1218 since well...1218 and it's been a pleasure.
Same as d33ps1x this is a great rom.
Everything's working fine with no force closing
If your problems continue follow d33ps1x instructions carefully and all should be fine.
Are you using the latest nightly or RC version?
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
this is the reason why you should have made a nand backup of your rom with cwm BEFORE installing a custom rom.
Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
eoghan2t7 said:
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
can you elaborate on that and give the exact commands
Gloris said:
can you elaborate on that and give the exact commands
Click to expand...
Click to collapse
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
dont forget fastboot -w to wipe the data of the previous rom
d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
I can confirm this working.
if you flash recovery, too from the zip, you can return to stock from cwm.
then apply "fastboot oem lock" and the bootloader will be locked again.
This can be used as a way back to warranty maybe, since then everything is stock again
d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
thanks, do you have the link?
eoghan2t7 said:
dont forget fastboot -w to wipe the data of the previous rom
Click to expand...
Click to collapse
fastboot -w is not allowed.
>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Click to expand...
Click to collapse
also, the only RUU i have in rom.zip format is the gingerbread 2.3.5 update....the others are all .exe only...how do i extract those? as i'm not sure the zip i have will work as it's 151Mb (i think the phone only has a genuine 150Mb total internal storage?)
for extracting from ruu exe:
- clear temp folder on windows
- run ruu.exe until first dialog
- go to temp files
- search in the folders for a rom.zip
- extract
- flash
this method is definitely not working
tried flashing the using fastboot, and not my phone won't even boot, it just starts up in recovery mode (it's actually lucky the recovery mode is there or else i'd have a definite brick on my hands).....for those that are wanting to back to stock, DO NOT TRY THIS....NOT WORKING!
Hi everybody,
I'm getting into the new AOKP Milestone 4 from the Codename 1.5.0 - so I downloaded the files and get recovery (clockwork 5.5.0.2) to make the wipes and flash the new rom and gapps... the usual routine.
Wipe data - Wipe Cache - Wipe Dalvik - Flash AOKP - FLASH GAPPS - REBOOT
1st strange thing after that: the Old Franco Kernel bootlogo. And in stuck, obv.
Why the Franco bootlogo? Bah, re-wipe everything and go on...
Nothing, stuck on Franco. So I decided to re.wipe everything again and re install the Codename android, 1.5.0 - the same wich i was coming from - to get the phone work for tomorrow. And here we go for the biggest surprise.
EVERYTHING IS HOW I LEFT BEFORE THE WIPES WHEN I WAS ON CODENAME!!!!!
Same routine, flashed Codename and reboot. Franco logo and then no configuration wizard, no backups.. everything was EXACTLY like how i left before the first attempt!!! My apps, my homescreen, even my login account, like i have never attempt any wipe or flash!!!!
IT DOESN'T WIPE ANYTHING, ANYMORE!
I'm getting mad.. tried this ten times. It's like nothing is getting wiped!
P.s: clockwork is correctly installed.. i've tried TONS of roms on my gnexus, everything has ALWAYS worked fine. No errors during wiping, usuals script "wiping /data .... wiping /cache etc.." until "DONE". No error flashing the AOKP.
Help please..
Fab
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
You are not wiping correctly. You are having problems because the system and boot partitions were not wiped at all....
Sent from my Galaxy Nexus using xda premium
SynFox said:
Hey there,
mike, the dev from Android Revolution HD, has a super wipe script in his thread, on the first page, might want to try that one.
It works like flashing a ROM
-Syn
Click to expand...
Click to collapse
Already tried. Same results, it ends successfully the superwipe string.. and then no wipe at all!
adb reboot bootloader
fastboot -w (might wipe SD card)
or
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot update update.zip (for installing the rom)
Ok new infos.
From the log file the /data wipe seems to be undone due to the "filesystem is read only".
Any ideas?
Stupid question... but maybe check if the device is still rooted and unlocked correctly?
Maybe something messed up there...
these are signs that the internal hdd is getting screwed up... like the partition values... its a known issue for all samsung devices. the i9000 had it, the nexus s had it. they even have a lot of threads out there reporting issues abt it but no fix till now. i even had it with my nexus s (which is now a paperweight)
some fixed it with a simple wipe using oem lock n unlock, others fastboot wipe....
the most common symptom is that you can see a lot of files on your phone, but can neither delete them nor add anyting to the sdcard.
As anton2009 said, you should try wiping all the partitions, then reflash CWM, then flash your ROM/kernel.
Reboot into fastboot and type the following:
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot erase userdata Note this will wipe/sdcard
fastboot erase cache
Then flash CWM and then ROM/kernel.
Sent from my Galaxy Nexus using Tapatalk
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Cptsamir said:
I am also having the same issue. However I just reflashed a bunch of roms and even though all my data is still there everything seems to be working fine.
Click to expand...
Click to collapse
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
efrant said:
Guys, all of your data is stored on the userdata partition. Most ROMs I don't think flash that partition, so all the data still remains. As well, I don't think every ROM includes a kernel, so the boot partition is not erase either. Wiping in CWM does not wipe /sdcard (which is actually located on the userdata partition as /data/media).
Use what I had posted 2 posts up and it will certainly wipe.
Click to expand...
Click to collapse
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
fab2disco said:
I also think your solution will work well.
My only question is about new rom flashing: erasing ALL datas even in the /sdcard how will I be able to flash new roms if there will be nothing more on the phone? Where will i get'em?
Will I need to flash again even the CWM?
Sorry for the stupid question..
Click to expand...
Click to collapse
You can still wipe userdata, boot into Android (obviously you can't do this if you wipe system), and download a rom from there. Otherwise you can download a rom onto your computer and then:
adb push /where/your/file/is/rom.zip /data/media/download
This will put the file from your computer to your download folder in your SD card. I'd recommend pulling any necessary files before you wipe userdata (such as music, pictures, etc) or you can pull the whole SD card (adb pull /data/media) and then cherry pick what you want to add back later.
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
fab2disco said:
SOLVED.
Wiped all with fastboot, pushed new rom with adb push and flash it.
Just to feel relaxed installed a couple of apps, gone back in recovery and tried to wipe data/cache/dalvick then re-flashed AOKP, everything is now working fine, the wipe erase all app and userdata now.
Hope this won't happen anymore.. thank you all..
Click to expand...
Click to collapse
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
anton2009 said:
Good to hear! Glad everything worked out for you. You can put [Solved] in the thread title so other people with the same problem will know what to do.
Click to expand...
Click to collapse
I feel sooooo newbie, but.. how can I do that?
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Jimmy Flip said:
Backing up and restoring /sdcard is very time-consuming and usually unnecessary in these situations. It only takes a minute to fix the filesystem errors on /data and then you can wipe data as normal (in CWM, no need to use fastboot which also erases /sdcard). Just boot into CWM and in an adb shell:
Code:
e2fsck /dev/block/mmcblk0p12
Answer 'y' to everything if prompted. Done.
Click to expand...
Click to collapse
Confirmed working.. Thanks a lot for your help. You are a life saver.
Help
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Dobie999 said:
I can't delete anything, i can't flash anything..
everything stay where it is, wipe or format doesn't work.. and my phone is stucked on infinite reboot..
please help!
Click to expand...
Click to collapse
Try to lock the bootloder and if it fails, your phone is bricked...the emmc is broken.. try warranty
Hi, I have a Desire HD and I just flashed this ROM: http://forum.xda-developers.com/showthread.php?t=1460820
It installed without any errors, but after the installation during the reboot, nothing happens. The phone just keeps rebooting endlessly with the HTC logo and then the beatsaudio logo and back to the HTC logo again. I pulled out the battery and turned it on again but the same thing happens. Please help!
MaxhBao said:
Hi, I have a Desire HD and I just flashed this ROM: http://forum.xda-developers.com/showthread.php?t=1460820
It installed without any errors, but after the installation during the reboot, nothing happens. The phone just keeps rebooting endlessly with the HTC logo and then the beatsaudio logo and back to the HTC logo again. I pulled out the battery and turned it on again but the same thing happens. Please help!
Click to expand...
Click to collapse
did u do a full wipe? just do a full wipe, and then reflash the rom.
Also, make sure that the md5sum is the correct for the rom zip file. If the file is corrupted, then u will never be able to flash it.
How do I do a full wipe? I can access recovery, so how do I do it from there?
select the option wipe data/ factory reset
BUT as you can imagine all your data will be deleted!
and use the + / - buttons for selecting; wake up button should be the enter button
I did that, but the problem still persists.
then use an other rom that you can flash.. maybe the rom you downloaded is broken?
MaxhBao said:
I did that, but the problem still persists.
Click to expand...
Click to collapse
Every rom in the site has a MD5SUM, that is a unique number to check is the file is corrupted or not.
When in the sdcard, the check using a cmd as admin the following
(whatever directory the sdcard is) ¿?:\FOLDER THE FILE IS ON\md5sum NAME OF FILE.ZIP
check that number...if that is ok, then change the rom.
Do you use alot of apps perhaps ?
Are these moved to SD ?
I too had problems with Rebooting after upgrading and it appears a HUGE BUG was introduced in the official Gingerbread OS ...
Check this link out and see how many hundred of others have this reboot bug:
http://code.google.com/p/android/issues/detail?id=25563
There is however a fix for those with rooted phones, simply install LINK2SD, which runs a boot-up script and allows you to save/link all your apps on SD card in a 2nd seperate partition (ideally use format ext4 for this partition) and makes the phone believe these are all installed on the local data space ..