Question about post flashing of jelly bean - Samsung Galaxy Nexus

After a final successful attempt I was able to flash the jelly bean rom off clockworks install rom section. I understand that after an OTA update the root goes away. However, after attempting to reboot into recovery mode and flashing a superuser zip, I get the little android with the red exclamation (oh God not that! I know if you you re flash optimus prime it normally fixes the issue, but does this reflash a stock rom? What's the best approach around this issue. You can't go into recovery from clockwork because you need SU access. Need help on the best method to fix this issue. Thanks!

bhillegass said:
After a final successful attempt I was able to flash the jelly bean rom off clockworks install rom section. I understand that after an OTA update the root goes away. However, after attempting to reboot into recovery mode and flashing a superuser zip, I get the little android with the red exclamation (oh God not that! I know if you you re flash optimus prime it normally fixes the issue, but does this reflash a stock rom? What's the best approach around this issue. You can't go into recovery from clockwork because you need SU access. Need help on the best method to fix this issue. Thanks!
Click to expand...
Click to collapse
When you flashed the ota it replaced your cwm recovery and took your root.
you'll need to reflash cwm via fastboot before you can flash superuser back

Related

Flash "Temporary" CWR, becomes Permanent?

After following Droid-Life.com's guide on unlocking the bootloader, and then rooting the phone, after installing Rom Manager and flashing CWR through the manager, the recovery truly becomes permanent.
This causes problems because if I try to install an OTA update I get the red error because I'm not running stock recovery.
I guess my question is, is there a stock recovery.img that I'm able to flash through fastboot in order to get rid of CWR and get back stock recovery? Thanks!
If you can't follow my train of thought: When I want to root, I need to install SU.zip through CWR
push su.zip thru adb to phone > flash CWR "temporarily" > install su.zip > reboot
But the problem is, the next time I try rebooting to recovery, I get CWR, not stock recovery like I wanted. And that stock-recovery.p file is still on my phone and alive.
http://forum.xda-developers.com/showthread.php?t=1399879
Shortly after posting, I just answered my own question. I downloaded the stock images from Google, found the recovery.img image in there, simply flashed with ADB and worked great. Thanks for your attention

[Q] Going back to stock recovery

Rooted with the "no tripping flash counter" method and installed TWRP afterwards so that I can have backups of my phone.
Now, from what I understand, I won't be able to flash the eventual OTA update to JB without having the stock Samsung recovery installed.
The simple question then : how do I get back to the stock recovery ?
The more complex question : is there a way to flash the stock Samsung recovery without a full wipe ?
The stupid question : does flashing the stock LH1 ROM (no root, no nothing) via (mobile) Odin also flashes the stock recovery or is it something completely appart?
Thanks
HiKsFiles said:
Rooted with the "no tripping flash counter" method and installed TWRP afterwards so that I can have backups of my phone.
Now, from what I understand, I won't be able to flash the eventual OTA update to JB without having the stock Samsung recovery installed.
The simple question then : how do I get back to the stock recovery ?
The more complex question : is there a way to flash the stock Samsung recovery without a full wipe ?
The stupid question : does flashing the stock LH1 ROM (no root, no nothing) via (mobile) Odin also flashes the stock recovery or is it something completely appart?
Thanks
Click to expand...
Click to collapse
Flashing the non-rooted stock ROM will restore everything back to stock but also wipe your data. In the 3e Recovery, you have to Reset and Wipe Cache or else it hangs on the boot logo, but I wouldn't recommend the mobile Odin, use your computer.
That's how you get the stock recovery back. Simply flashing a stock kernel and not wiping anything won't do it.
To flash the stock recovery without wiping, you would need the .img for it, and load it the way you did when following the root no trip install, but I've not actually seen anyone do that yet, so I don't know is the .img available...
My recommendation is to wait until 4.2 source hits, leaks, whatever, and stay custom... Patience...
Quasimodem said:
My recommendation is to wait until 4.2 source hits, leaks, whatever, and stay custom... Patience...
Click to expand...
Click to collapse
That's what I was thinking of doing ... thanks for your clear answer though! :good:

rooting problem

i am using team win and i did everything in the video but i am rooted but still stock.and when i flash it say failed?
This has been the case since the LG8 update. It has code that will replace the stock recovery if the signature check fails.
You need to follow the Team Epic Root from Recovery method. You flash CWM using Odin but do not reboot. Do a battery pull and boot into CWM. From there you flash the Team Epic Root from Recovery file. This gives you root but also removes the recovery signature check that is replacing the stock recovery.
m20120 said:
This has been the case since the LG8 update. It has code that will replace the stock recovery if the signature check fails.
You need to follow the Team Epic Root from Recovery method. You flash CWM using Odin but do not reboot. Do a battery pull and boot into CWM. From there you flash the Team Epic Root from Recovery file. This gives you root but also removes the recovery signature check that is replacing the stock recovery.
Click to expand...
Click to collapse
i did that one first and it still fail. i will try it again so flash cwm? when i use cwm it starts then say installing aborted
ran into a new problem when i have lbe on my phone restarts and freeze. i have to pull the battery and restore my android back up and not use lbe for my phone to work. is that a known problem?
thanks again i fix the problem. i just us rom manager and flash cm10 from it.

I can't seem to root

I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.
I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!
Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2
If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.

[Q] Won't boot rom or cwm recovery - only download mode

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

Categories

Resources