Related
hi
I´ve rooted and flashed my desire several times. rooted with unrevoked3 everytime and tried different roms like leedroid 2.2d, 2.2 f and rcmixhd 0.13. First time i did it i flashed leedroid 2.2d and it worked fine. After 1,5 months running leedroid my phone rebooted due to the overheating problems that 50 % of us suffer from (i rebooted it manually several times during those months and it worked until this day).
It got stuck at the bootupscreen with white background and green HTCtext. couldn´t install RUU via windows, had to grab the PB99IMG.zip onto my SD and boot into bootloader and restore my phone this way. Then i rooted it AGAIN, and flashed rcmixhd 0.13. Success! But only until i rebooted it manually, stuck at bootupscreen again.
I restored the phone from SD with pb99img as earlier. Flashed rcmixhd again and made sure i wiped everything (dalvik, cache, formatted sdcard and created a EXT), success! Until i rebooted my desire...back again.
Now im running stock non-rooted froyo. I´m getting tired of spending the night fixing it but i still want to use senseHD and i like tweaking stuff..
Do any of u guys recognize this problem and what can i do to fix it?
If any of you are from sweden, plz answer in swedish!
Same problem here, the only way i got to install a custom rom was by installing update-cm-6.1.0-Desire-signed.zip. Then installed a custom rom by using the "Rom Manager" tool.
Downloading and flashing through recovery mode, "No, can do!"
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Suddenjr said:
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Click to expand...
Click to collapse
yes this is a custom rom, i did a normal flash first to "update-cm-6.1.0-Desire-signed.zip" (some how that worked???). Then i reflashed through the "ROM manager" tool.
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
remmyhi said:
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
Click to expand...
Click to collapse
i wiped everything even the Dalvik Cache, didn't help a thing.
Could is be that is has something to do with rom's that are not signed?
I have this same problem now, any possible sollutions?
Perdonally i would suggest to reformat your sd cards and try again. Dont forget to wipe everything.
Sent from my LeeDroided Desire HD
Happend to me once or twice.
What to do is, Turn of the phone take out battery do the neccessary wipes and formatting,
root
install clockwork mod from market, go to it and choose install recovery
install rom
install kernel (might affect it somehow)
reboot
I'm rooted, unrevoked; I'm currently stuck in a boot loop. I can not reach recovery. I can not get to my rom. I can only access bootloader.
So far I have taken these steps to cure my problem:
Ran RUU software in Windows (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Cleared Storage using fastboot in command prompt
Cleared Recovery and then Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
Flashed Sprint Lover's as PC36IMG in hboot
Flashed eng-PC36IMG from Toastctfh's Old Root Tutorial as PC36IMG in hboot
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Before the bootloop this is what I was doing:
I had the initial CM7 nightly installed for about 2 weeks. It was buggy, and a few days ago restarted and deleted all my texts, and desynced from google. On rebooting, google apps acted as if I had never ran the phone before - it asked me to enter google account info, etc, upon reboot.
I decided CM7 was too unstable and so I wiped data and davlik, and flashed CM6. When CM6 booted google apps was already on, before I had even flashed it! Anyways I figured I wanted to give MIUI a run, so I wiped data and davlik, and flashed MIUI. It ran fine for about two hours, and then rebooted out of nowhere... and never came out of the boot loop.
I'm really starting to sweat this as I have gone three days now without a phone. Does anyone have any ideas that may help me? Thanks.
hmm, you could flash recovery through bootloader i think
davidc23 said:
hmm, you could flash recovery through bootloader i think
Click to expand...
Click to collapse
thanks for the suggestion!, but thats what i meant by
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
all i need to know can u get into recovery? cause if u can flash calkulins format all and flash the rom and ur good
Nope, I can't reach recovery
idk what to say hopefully a expert drops by im sorry that i cant help
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Jimdog420 said:
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Click to expand...
Click to collapse
I had same problem, the radios messed my phone and was stuck in a boot loop and mess with my usb drivers as well so I couldnt charge my phone...i had to buy spare battery charger and flash different radio and rom through hboot
I'm pretty sure Sprint Lover's and RUU have the latest radios in them
You shouldnt be bricked and if you flashed an RUU, you wont have root anymore, nor will you have a recovery img. I would suggest running the RUU again. As long as it finishes without errors, you should be fine. Now, just a quick question, what are you seeing that makes you think you are in a bootloop??
Are you sure RUU removes root? I've RUU'd through my computer, as well as flashing an RUU zip as PC36IMG, and I still have S-OFF. If it would turn it to S-ON, that would be amazing.
your ruu file could be bad as well .. it happened to me once and had to redownload...for some reason it wasnt as big as it should of been
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Flash the stock ROM on the phone. You have access to recovery so use it then after you verify you can boot with the stock ROM then try flashing another ROM on again.
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
No idea what caused you from being able to boot to this issue but this is my advice.
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
Click to expand...
Click to collapse
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
polish_pat said:
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
Click to expand...
Click to collapse
Go into cwm, do a wipe and also go into advanced and wipe dalvik. You should then be able to reflash your custom rom to fix your boot loop. If thats successful then go back to cwm and make a NANDROID backup so they have a restore point if anything goes wrong in the future.
If you want to flash back to stock its quite simple and can all be done from my ToolKit. Its basically going to http://code.google.com/android/nexus/images.html and downloading the latest factory rom for your model, moving it to the correct folder in the ToolKit and then selecting option 8 from the ToolKit to extract the images and flash it.
Mark.
polish_pat said:
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Click to expand...
Click to collapse
I've run into the same issue tonight going back to Apex 1.0.2 from the 4.0.4 leak. I'm trying the suggestion below to wipe and re-flash the ROM. I'll report back when I'm finished.
Edit: Yep, it worked!
Hi i've come here many times before for any hiccups that came up for me with my phone but this time I believe I need help. I'll start it off with me earlier this week I was running CyanogenMod 10.1 and felt like I wanted to change it up leading me to isntall synergy onto my S3 (completed two nights ago). Today I decided it just wasnt doing it for me. Picked a new ROM ( Paranoid ).
This is where the problem comes in, I started the usual to flash a new ROM, put it into recovery and then started the factory/data reset. it froze waited half an hour for it to complete but it did'nt. Rebooted it into recovery as now I cant boot back into the software anyways. tried the same thing but wiped the cache and dalvik cache first. same thing happened froze on the factory reset. At this time I decided to reset it completley and get rid of the root, flashing the stock firmware. Odin also froze everytime, I cant even reinstall the stock firmware after failing everytime around the Nand area. I found this thread (http://forum.xda-developers.com/showthread.php?t=1840030) with I think a similar problem im really not sure as I cant do anything but the thing is, is that its for Verizon Galaxy S3 ( im on Rogers Canada). I'm sure I can fix this somehow as I can put it into download mode still but any help from the community would be greatly appreciated.
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
CZ Eddie said:
How far does Odin get during the stock ROM flash, before it freezes up on you?
I would try to Odin a stock recovery. Not the ROM & everything, just the recovery. Then go into the stock recovery and wipe everything.
Then Odin the stock ROM. Maybe try an ICS one if you were failing on the JB one.
Click to expand...
Click to collapse
It says Nand write start, and then complete (write) operation failed. On the phone in download mode it says Secure check Fail : aboot . CMW works for me still ? is that what you mean ? if so the data/factory reset freezes. I do have a RecoveryGalaxyS3USCanada.tar file in my Root folder, if I should flash that.... but its been so long I forget what its for. Thank you for the feedback ive been searching all day and wasnt able to find anything useful so far. Right now im downloading older stock firmwares to attempt to flash them, hopefully they pan out.
The utility in this thread offers an option to flash the stock recovery. I'd try it out and see what happens!
http://forum.xda-developers.com/showthread.php?t=1746665
Flash stock recovery and then boot to the stock recovery and restore to defaults. Then flash a stock ROM.
Stock recovery = Samsung recovery, not TWRP or Clockwork.
I had 2 soft bricks with cm this week. Had to Odin back to rooted stock for one. The other back to rooted stock and had to factory reset with Samsun 3e recovery before the phone would boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
French1747 said:
Okay i've installed everything (drivers, toolkit, deleted Kies) and now when im going in to flash the stock recovery it says its waiting for USB debugging, which I can't re-anable since im stuck in a boot loop. Am I screwed here ?
Click to expand...
Click to collapse
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
http://d-h.st/8OQ
xBeerdroiDx said:
can you still access recovery? i'm assuming it's twrp or cwm
if so, here's cwm flashable stock firmware from upndwn4par. flash it, boot in, turn on debugging.
]
Click to expand...
Click to collapse
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
First, sorrt to speak french, but thatnll be more easy for me to tell it.
A partir du moment ou tu peux passer en mode download, tout va bien ^_^
Il m'est deja arrive sur mon teos de corrompre ma partition systeme et de repartir comme si de rien n'etait avec un flash.
Reflashe avec odin et reessaie
Sent with my AiKi and optimus rom
CZ Eddie said:
If it were me, I'd Odin a stock/rooted JellyBean ROM first. Just to get to get all the correct files & structure on there. THEN I would flash whatever you want.
Click to expand...
Click to collapse
French1747 said:
Thank you so much! I doubted it at first just because of the other roms and stock ones also never worked but this one has it up and running smoothy. I want to play it safe just so I dont screw up again so I'm gonna ask you guys one more thing.. Would it be safe to try and flash the Paranoid ROM now? ( I dont believe it was the problem earlier since I never actually got to installing it). The problem was something around the lines of not being able to write things onto the device. ex Data/Factory reset freezing everytime on CMW, while Odin also failed everytime it made to the step of flashing/writing in the stock ROM.
Thanks everyone, your're all very helpful !
Click to expand...
Click to collapse
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
xBeerdroiDx said:
i agree with coming from stock firmware when flashing. i would also make sure my cwm was up-to-date while i was at it. i would also boot into recovery and make a nandroid now so you'll have one. with that being said, here ya go:
http://forum.xda-developers.com/showthread.php?t=2179330
in the above link:
step 1: take the time to backup your imei if you havent already
step 2: this is stock with root already injected
step 3: if you dont have rom manager, download it and update your recovery if you're not running 6.0.2.3 or higher
step 4 & 5 are self explanatory
cheers
Click to expand...
Click to collapse
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to get rid of the stupid data reset problem.
French1747 said:
The only thing so far (that I have noticed) is that the data/factory reset still does not work, I'm going to continue like you said earlier and flash stock recovery and my own stock firmware for Rogers now that I have turned debugging mode on. my cmw currently is 6.+ and my previous Nandroid backups would also get stuck when I tried to restore to them, I'm assuming that since I still can't factory reset that I wont be able to restore back to them but I will see. Should I make another nandroid even when its still in a semi-messed up state ?
Right now I seriously just want to go back to step one of everything, unrooted stock fimrware with access to Gapps and continue from there. Most of all get rid of the stupid data reset problem.
Click to expand...
Click to collapse
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
xBeerdroiDx said:
where are you saying the data/factory reset isnt working? cwm or in android settings?
i would download rom manager and update cwm to latest (6.0.3.0), boot into cwm recovery and try making a nandroid.
and i dont think you're as messed up as you think you are right now. you're rooted, with stock firmware and a custom recovery.
when i was ready, i would update recovery, in recovery make a backup, (still in recovery) wipe data/factory reset, wipe cache/dalvik, flash rom
Click to expand...
Click to collapse
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
French1747 said:
Google apps arent showing up for me either, Tried installing them and they did succesfully but i still dont see them. anyways I'm on a slightly lower version of cmw then 6.0.3.0 , can I flash the new version over the current one im on, since I cant install through the play store ?
Click to expand...
Click to collapse
boot into cwm and flash gapps again. flash twice to be sure. reboot. lemme know
I believe everything is working perfectly now, installed Rom manager from the web and updated cmw. Once more tried to data wipe from cmw and it froze again this time crashing by itself, I then went back into it went and formatted my data and then tried the wipe data, this time it worked for me and I proceeded to wipe the cach and dalvik, installed paranoid and everthing is working fine, ill post an update if i notice anything else happens but so far it looks perfect. Thank you so aton, I appreciate it guys especially you "Beer". Now I can relax on my birthday and stop tinkering around on my phone haha.
( Not sure why Gapps wer'nt working earlie,r but i'm done )
Same problem here
The same thing happened to me while trying to Odin to ATT stock rom. Flash stopped half way and Odin showed failed. Tried to reboot into download mode to repeat procedure and would not go into download mode. Phone will reboot but into android recovery mode. When I try to run an update from sd card I get a "file verification error" and the process aborts. I'm going to try this process to see if I have any better results.
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739
what recovery are you currently sitting on?
Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739
here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted
Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still
I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.
Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.
now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]
Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.