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?
Related
Hi,
I've rooted and unlocked my t989D. To do that I pushed recovery-clockwork-5.0.2.7-hercules.tar via odin and then flashed SGH-T989_UVLH1_Stock_Deodex_Rooted_signed and Tmo_SGH-T989_UVLE1_radio to be at at 4.0.4 ROM and radio.
Now I want to upgrade to cm 10.2. I tried flashing it, and it required a newer radio, so i flashed Tmo_SGH-T989-UVMC6_radio. Then I reflashed cm 10.2 and the installation completed, but I only get a boot loop with the CM sign. I figured it was because I was using an old recovery. So I tried to flash a newer CWM (recovery-clockwork-touch-6.0.3.1-hercules), and that failed, so instead I pushed the latest TWRP (openrecovery-twrp-2.6.3.0-hercules.tar) via Odin. I'm in the same position as with the older version of CWM: I can boot recovery, I can successfully flash 10.2, but I get stuck in a boot loop with the CM sign. Can someone correct me? Id appreciate it if you could correct my logic as well plz.
Update:
I pushed the old CWM back (5.0.2.7), then flashed an older version of CM (9.1) and it got stuck in boot loops as well. I then flashed the stock 4.0.4 ROM back and it gets stuck in boot loops (during samsung logo). I then pushed TWRP 2.6.3 back and reflashed the stock 4.0.4 rom ROM and it boots
Basically, the only combination that well allow a full normal boot is TWRP 2.6.3 + stock 4.0.4 rom (SGH-T989_UVLH1_Stock_Deodex_Rooted_signed)
Update 2:
Solution seems to be a dark side super wipe http://forum.xda-developers.com/showthread.php?t=1477955
So far, this allows me to get 9.2 working. Haven't figured out how to get 10.2 going yet.
Install latest twrp recovery then use superwipe zip file (that is mention in your archive post) than install your rom.
As far as about your boot loop issue wipe your internal and external card than just put rom installation files in it.
Sent from my SGH-T989 using XDA Premium 4 mobile app
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
I want to flash the CM 12.1 to my T-Mobile Galaxy S III but I don't know where to download the gapps for the latest nightly here
i also dont know if T-Mobile is arm, arm64, or x86
so I cant download in this site from cynogenmod
another question- is it the Cyanogen Recovery from this link will be use to flash the ROM or it is the recovery that will be use after flashing the CM12.1?
Use the ARM gapps.
I recommend using either Philz Touch recovery or TWRP, both of which can be flashed using Odin.
I have never used Cyanogen's recovery but have had great success with Philz and TWRP.
audit13 said:
Use the ARM gapps.
I recommend using either Philz Touch recovery or TWRP, both of which can be flashed using Odin.
I have never used Cyanogen's recovery but have had great success with Philz and TWRP.
Click to expand...
Click to collapse
thanks on your reply but I already solve it using the recovery from ROM manager app that I downloaded in the Play store but there is still a problem on it when I update using CyanogenMod updates it will fail to flash automatically after clicking install, so I still need to flash it manually, that's why I still need to flash the recovery provided with CyanogenMod
I have never used the recovery from cyanogen so I don't know if it will automatically dirty flash the update. I also don't know if the cyanogen recovery can flash other zips such as supersu, different gapp versions, etc.
Automatic flashing is not something I like to do because a nightly can cause problems. By using twrp, I can easily make a nandroid backup before flashing a new nightly.
Just tried the Cyanogen recovery and, after downloading a nightly update, I click install and it reboots to recovery and dirty flashes the updated ROM; however, the Cyanogen recovery would not flash the LP Gapps while Philz and TWRP were able to flash the Gapps. Also, the Cyanogen recovery does not have an option to create a nandroid backup.
EDIT: So it turns out the latest version of Philz touch actually does work, at least after reflashing stock.
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
sorcererofdm said:
The short story: I tried to update from CM11 to CM12 snapshot on 9/1/2015, but every CM based ROM would get stuck at CM boot logo, and this is true with the latest TWRP and latest Philz, along with the snapshot CM recovery provided at the official download page. After downgrading to TWRP 2.6.3.0 at the suggestion of http://forum.xda-developers.com/note-2-sprint/orig-development/rom-cyanogenmod-12-0-t2972922/page32, I got it working.
The long story:
I tried to update to CM12 over the air from CM11. That didn't work, as my philz touch recovery just boot directly back to CM11. It's too quick for me to see the install logs, but there was some error message like "can't install" etc.
So I thought maybe I need a different recovery, since the update notice does say "compatible recovery required" and I saw there is such a recovery in the CM download site.
I flashed cm12.1 snapshot recovery using flashify but I got stuck in a boot loop.
I then flashed the recovery using heimdall and that worked.
I then flashed cm12.1 snapshot using the cm recovery, but that was stuck on the cm logo for at least 4 hours before I shut it down.
I then tried a couple more times and it's the same thing.
I installed other cm11 versions and they all get stuck on the logo (even though I came from cm11).
So I tried a different recovery, the latest version of twrp and long story short it's the same thing with cm roms.
Then I flashed back to philz touch (but I didn't realize that I flashed the latest version) and it's the same thing.
Even after I restored a previous backup, the cm11 rom wouldn't boot up.
At the end I was able to use odin to flash back to stock.
I can also flash rwilco's NE2 based ROM.
I have also tried cyanideL, which is CM12 based and it gets stuck too.
Finally I found the post mentioned above and downgrading to TWRP 2.6.3.0 worked.
Hopefully this post will help someone down the road.
Click to expand...
Click to collapse
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
sorcererofdm said:
After flashing back to stock NE2 rom, the nandroid restore from philz_touch worked.
Click to expand...
Click to collapse
Actually, I got CM12 working after flashing CM12 on top of CM11 restored from philz touch after flashing stock. So this is probably more properly called an "upgrade" from CM11 to CM12
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