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
Related
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 just tried to preform an OTA update to the latest CM11 nightly and so it installed it through Teamwin recovery and now it is just stuck at the Teamwin splash screen. I cannot boot into recovery but I can access the yellow downloading screen. Any Idea on what to do? Am I going to have to use Odin to revert the phone back to stock rom?
Flash back to Stock
joejames542 said:
I just tried to preform an OTA update to the latest CM11 nightly and so it installed it through Teamwin recovery and now it is just stuck at the Teamwin splash screen. I cannot boot into recovery but I can access the yellow downloading screen. Any Idea on what to do? Am I going to have to use Odin to revert the phone back to stock rom?
Click to expand...
Click to collapse
I am pretty sure that happens if your Teamwin recovery is not new enough (I don't recall the required version). This happened to me as well.
My solution was to ODIN back to stock and install CWM (v5.0.2.7), CM11 will update it to v6.0.4.7. If I recall correctly I had to install the CM11 update twice (once for the CWM update and once to flash ROM)
Hope that helps
Chris
From what I know, the latest official TWRP (2.6.0.0) CAN NOT flash 4.4.x ROMs. Use CWM as included in CM nightlies, or try @unjust's 2.6.3.0 test build.
Sent from Google Nexus 4 @ CM11
hey all, im stuck running the jedi elite rom (apps constantly FC, laggy, bulky) and so I downloaded AOSB rom. I booted into recovery, which was TWRP 2.6.3.8 i believe, maybe .9. I made a full backup, then I tried to install TWRP 2.7. I flashed the .zip file from the official site, then after flashing, i went to main menu, reboot, then i hit recovery. when it went to reboot into recovery, it got stuck on the black startup screen, it says
RECOVERY BOOTING....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Click to expand...
Click to collapse
this didnt bother me, as thats what it normally says when it boots up, but this time it was stuck. I downloaded Odin 3.09, then downloaded the TWRP 2.7 .tar and installed that, it booted into my old rom, and i tried to boot into recovery from there, same result. I used odin to boot back into the rom, downloaded goomanager, and downloaded the older 2.6.3.9 recovery and everything installed fine as far as i can tell, rebooted into recovery, nothing. I used odin to flash a CWM recovery, same results. It seems recovery is broken. Can anyone help me? I just want stock, AOSP android, tired of TouchWiz's bullcrap.
bump
Sent from my SM-N900T using XDA Premium 4 mobile app
Version 2.7 of TWRP requires that you have the new 4.4.2 bootloader. Have you installed the new 4.4.2 bootloader?
If not, then downgrade your TWRP version to the previous one.
ah, no I haven't. How do upgrade the bootloader? And am I fine to flash the 4.4.2 AOSB ROM on TWRP 2.6.3.9?
Sent from my SM-N900T using XDA Premium 4 mobile app
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
I have a Samsung Galaxy G4 (T-Mobile version). I had a boot loop on Recovery problem with it. I reflashed the recovery a couple of times, TWRP and CM recovery. Neither wants to start up when I try to boot into recovery. (I have tried adb and using the keys.) Usually when I would flash a new kernel it would drop into recovery. When I upgraded to the nightlies, it went into recovery, installed the kernel, and rebooted.
Now I have a CM 13 kernel, but I am missing the proper gapps package.
Is there a way to install the gapps package with heimdall? Is there a trustable twrp app I can sideload? Is there a trick to get gapps to install with adb?
Looking for a useful solution. Thanks!
After flashing twrp using Odin, are you immediately trying to boot into recovery or are you restarting the phone and booting the rom?