Ok, so I was on CM10.1 and I wanted to update my nightly, so I downloaded the newest one. I had it on my computer and checked the md5SUM it was clean. Every time I boot into recovery, TWRP 2.4.1.0, and I go to flash any ROM it just says "FAIL" and I can't flash. I've already tried reflashing TWRP but no luck. Any hep?
jamcar said:
Ok, so I was on CM10.1 and I wanted to update my nightly, so I downloaded the newest one. I had it on my computer and checked the md5SUM it was clean. Every time I boot into recovery, TWRP 2.4.1.0, and I go to flash any ROM it just says "FAIL" and I can't flash. I've already tried reflashing TWRP but no luck. Any hep?
Click to expand...
Click to collapse
This happens to me often, by rebooting my recovery, it fixes the issue for me. I'm also on 2.4.1.0.
Related
I just got a Kindle today and decided to root it. Here are my exact steps.
Downloaded latest KFU
Ran it, ran input 2 for permanent root
installed TWRP and FireFireFire
made a backup of my current rooted stock ROM
wiped everything
flashed CM9 reloaded ICS ROM
didn't like the ROM, so I went back into recovery
wiped everything
flashed AOKP ROM
reboot
and nothing.. the screen went black
I click the power button and the green light will come on and then everything goes black again
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
kendallc123 said:
I reinstalled the drivers and got it to boot in recovery. I wiped cache, dalvik, and factory reset. I tried to boot but it won't boot into anything, it just turns off.
I'll try to restore my nandroid and see what that does
Edit: It rebooted into my nandroid of the stock ROM. Was it just a bad AOKP download? Should I run the perm root =, TWRP recovery instal and FireFireFire install on KFU again?
Click to expand...
Click to collapse
I have no idea why your AOKP install failed, but you should check the MD5 sum on those zip files before you flash any new ROM. You don't need to root stock again if you intend to flash a new ROM, but make sure you have TWRP 2.1.1 and FFF 1.4a installed on your device before you try it again. As long as you have those two piece in place, you can get back to recovery and flash something again if anything else should go wrong.
Download a new update zip and give it a try!! check md5 sum first!!
Alright I have never checked an md5sum. I never really knew it was important! I found out how yo do it and what program to use, so I will definitely do that next time! Thanks
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
tenpin416 said:
Finally rooted my s3, when I first tried to flash cm 10 I was getting an install aborted message. A post on this forum suggested tryong twrp instead of clockwork so I downloaded goo manager. I downloaded cm 10 and gapps through twrp and started by wiping. When I went to flash couldnt find the files for cm 10 so went to restore so I could start over...discovered my clockwork backup wouldnt work with twrp(rookie mistake lol) so reflashed clockwork so I could restore and start over. Redownloaded cm 10 and gapps with twrp checking the filepath for the save this time. Problem is I cant get twrp to be my boot recovery so that I can save a nandroid with it and try flashing the rom.ive tried setting the boot recovery to twrp with clockwork itself,tried rebooting through goo, tried setting twrp to default with rom toolbox, tried rebooting with twrp manager and finally uninstalled clockwork ....no matter what my boot recovery is clockwork .how can I get twrp to load as boot recovery so I can save a backup with twrp and try flashing cm 10? Flashed roms on old devices before and never had this much trouble.
Click to expand...
Click to collapse
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
DMF1977 said:
Did u have the latest cwm recovery (6.0.3.6) installed when u originally tried to flash? I have never had an issue with cwm, and until I do, I'm not switching to twrp. Which version of cm 10 specifically were u trying to flash?
Click to expand...
Click to collapse
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
tenpin416 said:
I had the latest version of cwm and I am trying to flash the latest stable release of cm 10, 10.1.2 I believe
Click to expand...
Click to collapse
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
DMF1977 said:
Is it android 4.2.2 or 4.3? Pretty sure u have to update to the latest bootloader for 4.3...
Click to expand...
Click to collapse
After doing some reading I think the abort is caused by having the older ics bootlaoder.ive never had to update one before so im a bit hesitant. ..do you know if I update and try to switch back to my original restore or to a different rom (other than cm 10) Will I have to change the bootloader back again or will I run into a greater chance of problems in the future?
Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
Hello,
I tried to update my recovery from Phils 5.x to TWRP. SO recomended way was to use goomanager. I tried and it downloaded image and got stuck at checking MD5. Ao I waited and after a while killed the process and downloaded recovery in zip format (openrecovery-twrp-2.7.1.0-t03gub.zip) and flashed it from my Phils.
After that, my phone booted with black screen with green android logo saying "Downloading... Do not turn off target!!"
What do I do?????
Thanx!!
EDIT:
OK, to reply to myself
Tried flashing TWRP from recovery (zip) from Odin (tar), no go. Tried flashing latest Phils' - no go. But I successfuly flashed older Phils' (v5.x) and it works OK.
After this success I againg tried latest Phils', but it just reports failed. Will try to update it from recovery (zip), see what happens....
any clues welcome
OK, managed to install latest Phils' but the strange thing is that after installing zip, I did "reboot recovery" and it rebooted to download mode...??? After I turned it off and back on it booted correctly to updated recovery....
Still weird I can't seem to install TWRP....
Which file should I choose i.e. if I'm installing it from Phils'? There are several possibilities I have standard intl N7100:
openrecovery-twrp-2.7.1.0-t03g.zip
openrecovery-twrp-2.7.1.0-t03gduoszn.zip
openrecovery-twrp-2.7.1.0-t03gub.zip
? I suppose the 1st one?
dalanik said:
Which file should I choose i.e. if I'm installing it from Phils'? There are several possibilities I have standard intl N7100:
openrecovery-twrp-2.7.1.0-t03g.zip
openrecovery-twrp-2.7.1.0-t03gduoszn.zip
openrecovery-twrp-2.7.1.0-t03gub.zip
? I suppose the 1st one?
Click to expand...
Click to collapse
Ya use the t03g one , and you can flash 2.7.0. or 2.7.0.2 ,I haven't tested the latest TWRP version so not sure if it's working right or not.Good luck
I am using TWRP 2.7.0.0 and works fine
I´ve instaled via TWRP Manager. Just flashed img file
Hi. Today, I wanted to check for CWM Updates with ROM Manager, but there isn't supported version, so I didn't do anything. One hours later, I booted the phone to recovery, and the recovery changed to CR. I wanted to flash a new ROM, so I tried, it worked, but it can't flash GApps and it's not so stable. How can I get back to CWM?
Berecz said:
Hi. Today, I wanted to check for CWM Updates with ROM Manager, but there isn't supported version, so I didn't do anything. One hours later, I booted the phone to recovery, and the recovery changed to CR. I wanted to flash a new ROM, so I tried, it worked, but it can't flash GApps and it's not so stable. How can I get back to CWM?
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/showthread.php?t=2678420