Tried to flash the ota update 4.1.1 from takju 4.1 and had status 7 error rebooted the phone and none of my root apps are working superuser is still installed but won't download the binaries can't flash clockwork mod recovery can't get back into recover to flash super user again and won't have access to a computer until tomorrow night....
Is there anything I can do?
Sent from my Galaxy Nexus using xda app-developers app
mopardroid said:
Tried to flash the ota update 4.1.1 from takju 4.1 and had status 7 error rebooted the phone and none of my root apps are working superuser is still installed but won't download the binaries can't flash clockwork mod recovery can't get back into recover to flash super user again and won't have access to a computer until tomorrow night....
Is there anything I can do?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i hope you make a nandroid backup, and restore system and boot
You should *always* flash a superuser package (I used JB-SuperSU.zip) immediately after flashing a stock update - no reboot in-between! The stock update overwrites your recovery, so if you don't do it first thing you won't have another chance.
You're going to have to get to a computer with fastboot and reflash the custom recovery of your choice via fastboot, then boot into the custom recovery and flash a superuser.zip of some nature. You'll also want to delete /system/etc/install-recovery.sh (via adb or a file manager if your custom recovery supports it) before booting the ROM again or else your recovery will be overwritten again.
codesplice said:
You should *always* flash a superuser package (I used JB-SuperSU.zip) immediately after flashing a stock update - no reboot in-between! The stock update overwrites your recovery, so if you don't do it first thing you won't have another chance.
You're going to have to get to a computer with fastboot and reflash the custom recovery of your choice via fastboot, then boot into the custom recovery and flash a superuser.zip of some nature. You'll also want to delete /system/etc/install-recovery.sh (via adb or a file manager if your custom recovery supports it) before booting the ROM again or else your recovery will be overwritten again.
Click to expand...
Click to collapse
Yes I know I will lose root I didn't reflash the super user zip because the update didn't stick got a status 7 error.
I will just wait until I get home than.
Thanks
Sent from my Galaxy Nexus using xda app-developers app
mopardroid said:
Is there anything I can do?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
1- update cwm to 6.x or twrp to 2.2beta
2- file that restores stock recovery on reboot is /system/recovery-from-boot.p
Sent from my i9250
Related
i just flashed cwm to my gnex with rom manager after rooting the phone (without unlocking the bootloader). when i try to boot into the recovery, i get this picture of an android with its chest open and an exclamation. i would assume that the recovery partition was not flashed correctly? are there any suggestions?
thanks for your help in advance!
That just means the recovery was not properly flashed, what you are seeing is stock recovery. Try again via rom manager, or do it manually using fastboot.
Your phone needs CPR.
iphone. helping computer illiteracy become popular since 2007.
pretty sure u need to unlock the boot loader to write a custom recovery
Sent from my Galaxy Nexus using xda premium
jasonpantuliano said:
pretty sure u need to unlock the boot loader to write a custom recovery
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not true. If you have root, you are good to go.
@OP: the reason CWM is not sticking is because you updated your build with an OTA (or link). When you do this, the update adds 2 files to your ROM that re-flash the stock recovery on every reboot. You need to delete them and re-flash CWM.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Not true. If you have root, you are good to go.
@OP: the reason CWM is not sticking is because you updated your build with an OTA (or link). When you do this, the update adds 2 files to your ROM that re-flash the stock recovery on every reboot. You need to delete them and re-flash CWM.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
thanks so much! managed to get itt to stick by getting rid of those.
joshtb86 said:
thanks so much! managed to get itt to stick by getting rid of those.
Click to expand...
Click to collapse
You still can boot into CWM Recovery without deleting or change the filenames..
Just before you want to boot into CWM recovery...from CWM App..clck flash recovery..after that click Reboot into recovery.. doing these 2 steps..you will get booting into CWM Recovery yet not losing the stock recovery..
hmanxx said:
You still can boot into CWM Recovery without deleting or change the filenames..
Just before you want to boot into CWM recovery...from CWM App..clck flash recovery..after that click Reboot into recovery.. doing these 2 steps..you will get booting into CWM Recovery yet not losing the stock recovery..
Click to expand...
Click to collapse
Yup, you can do that as well. But you would need to flash CWM every time.
Not sure why you are so concerned with having a stock recovery though. The "I want to be able to get the next ota" reason doesn't make any sense at all for these reasons:
1) The link for the next OTA update will show up on XDA before you get it. So in this case, you need either CWM or root to install.
2) Irrespective of whether you have a stock or custom recovery, you will receive notification of the next OTA update regardless. If you have the stock recovery, just click install. If you have CWM, start ROM Manager, install the stock recovery, and then install the update.
Sent from my Galaxy Nexus using Tapatalk
Hey there
I'm currently working through the below process... on my Verizon CDMA LTE Galaxy Nexus runing 4.0.2 Stock.
http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
Also watched this Video (but he doesn't get the error)
http://www.youtube.com/watch?v=dQ1HuteSnDE
And when i get to the part about running mempodroid as sh I get an error that says the following:
Segmentation fault See the below screen shot.
Does anyone have any advice on how i can get past this? I have restart phone and desktop many times and happens every time. I have the PDAnet drivers installed and everything else adb seems to be working.
Would love some help,thanks in advance. Really want to get this working tonight if possible.
Conty
You are not developing anything
Moved to Q&A
FNM
Sent from my PantechP4100 using xda premium
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
imnuts said:
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
Click to expand...
Click to collapse
I'm just following the process for the 4.0.4 install. How else can i do what i need? I'm quite new to my Nexus, i had a bionic before.
Thanks
Need the temp root to run mempodroid i think, can i do this another way? i honestly don't know
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
imnuts said:
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
Click to expand...
Click to collapse
Which CWM version do i want and will this include the radios if i do it this way, sorry kinda newb at this phone. very different to my bionic.
Thanks so much for your help tho
Eidt
I got into stock recovery and saw the android with the explanation point but when i click Volume up + power i get no menu...
I'm off to bed will check back in the morning and see if you have any ideas, thanks again for the help
Finally got the stock recovery to work, however it only allows flashing from ./cache and i cant get my update.zip to cache without root right?
So decided to just unlock bootloader and then it let me root and push to ./cache and then i flashed the update.zip
All seems to be working now.
Thanks for all the help
I love the fact its so easy to unlock and lock the bootloader. very happy with that lol
is there a way to re root the phone once its on 4.0.4 IMM76K ? as the Galaxy Nexus toolkit stops at IMM30B...
Thanks
Nevermind
Adrynalyne saved the day once again
http://www.droid-life.com/2012/02/06/how-to-root-android-4-0-4-on-the-galaxy-nexus/
Thanks Adrynalyne
Just got the Verizon nexus 2 days ago it was stock/unrooted.
I used wug's toolkit to root and install cwm recovery and everything was great
I installed the newest 4.0.4 update.zip and it broke root and recovery went back to stock, so I used the toolkit to flash cwm and root again. Fail
So I found a su.apk I needed to keep root and that's working great, I'm perm rooted.
Now I can't keep cwm recovery. It's good for one boot via wug's toolkit after that I can't get back to cwm recovery.
Help???
Sent from my Galaxy Nexus using Tapatalk 2
Don't use a tool kit. Flash it manually.
fastboot flash recovery cwm.img
stock rom has an automatic "feature" that will reapply the stock recovery on reboot, overwriting CWM, etc.
You can delete or rename the file "recovery-from-boot.p" from /system folder to stop it doing this
azlemad said:
stock rom has an automatic "feature" that will reapply the stock recovery on reboot, overwriting CWM, etc.
You can delete or rename the file "recovery-from-boot.p" from /system folder to stop it doing this
Click to expand...
Click to collapse
thats what i was going to say ...
That what it was. Thanks guys I should have came here first.
Sent from my Galaxy Nexus using Tapatalk 2
ok so how do you do this... i flashed on my Galaxy nexus through verizon.. but when i boot it kicks me out of SU and i cant get anything to access that folder /system and rename the file..
Is it possible to flash the stock recovery without the use of Odin or Mobile Odin? Or is it at least possible to obtain the official JB update one way or another while keeping root and without wiping any data(except maybe the caches, those don't matter) and keeping recovery(I could always download goo manager and flash twrp or get rom manager for CWM right?) if possible?
If anyone knows if OTA Root Keeper works with this update, that would be great.
Sent from my SPH-L710 using xda app-developers app
EggosEvo said:
Is it possible to flash the stock recovery without the use of Odin or Mobile Odin? Or is it at least possible to obtain the official JB update one way or another while keeping root and without wiping any data(except maybe the caches, those don't matter) and keeping recovery(I could always download goo manager and flash twrp or get rom manager for CWM right?) if possible?
If anyone knows if OTA Root Keeper works with this update, that would be great.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Recovery flashable and raw image
To flash raw image place on sd card and enter this in adb or terminal
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
And pretty sure the only way of obtaining official jb without having to do at least a factory reset would be the official that will be pushed to you.
To flash the odin tar and keep custom recovery you could uncheck auto-reboot and reflash a custom recovery when it finishes or open the .tar in 7zip and delete the recovery.img from it before you flash it
billard412 said:
Recovery flashable and raw image
To flash raw image place on sd card and enter this in adb or terminal
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
And pretty sure the only way of obtaining official jb without having to do at least a factory reset would be the official that will be pushed to you.
To flash the odin tar and keep custom recovery you could uncheck auto-reboot and reflash a custom recovery when it finishes or open the .tar in 7zip and delete the recovery.img from it before you flash it
Click to expand...
Click to collapse
So with that zip I can just flash that through CWM right?
Sent from my SPH-L710 using xda app-developers app
Yes that will give you stock recovery. If you were to select reboot recovery after flashing, you will boot to stock recovery
Cant seem to downgrade from 4.4.2,
After upgrading I tried to restore using a recovery from twrp but phone was just stuck on logo.
I then tried to restore stock recovery which didnt go well either, after flashing via adb I then tried to reboot into recovery to force a update to stock using update app i was still greeted with the team win logo which after a few seconds would just blink every few seconds, I then had a hell of a job restoring the twrp so I could then boot into recovery and reflash sh*tkat.
Phone flashes sh*tkat roms fine and runs backup and restore, so does anyone have any ideas why this is happening? If they could enlighten me I would be most grateful !
Im not sure for huawei mate but for p6 you needed a mid step before you can go down to jelly bean again. And this was all with stock recovery/rom. So search the forum and see if thetes a file like that.
Sent from my SM-G850F
tileeq said:
Im not sure for huawei mate but for p6 you needed a mid step before you can go down to jelly bean again. And this was all with stock recovery/rom. So search the forum and see if thetes a file like that.
Sent from my SM-G850F
Click to expand...
Click to collapse
Hi thaniks for the reply,
yes I thought that if I could re install stock recovery it would enable me to downgrade using hisuite but when I re flashed stock recovery I still got the team win logo showing then the phone would just flash again after about 4 seconds as it couldn't boot to recovery, it was just stuck a recovery bootloop.
See the topic "How to downgrade from B321 to B221"
sent from my MT1-U06 using Tapatalk 2
blankulus said:
See the topic "How to downgrade from B321 to B221"
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
That does not apply to this problem but thanks anyway for your reply
It actually should work for you. You are having trouble going back to stock recovery right? Use custom recovery to flash the file in that post and then you won't have a problem going back to stock recovery. Then you will be able to downgrade to stock 4.2.2
sent from my MT1-U06 using Tapatalk 2
blankulus said:
It actually should work for you. You are having trouble going back to stock recovery right? Use custom recovery to flash the file in that post and then you won't have a problem going back to stock recovery. Then you will be able to downgrade to stock 4.2.2
sent from my MT1-U06 using Tapatalk 2
Click to expand...
Click to collapse
No I know how to flash recovery and use adb, my problem as stated is phone will not boot into recovery when stock is flashed
Quote: then tried to restore stock recovery which didnt go well either, after flashing via adb I then tried to reboot into recovery to force a update to stock using update app i was still greeted with the team win logo which after a few seconds would just blink every few seconds, I then had a hell of a job restoring the twrp so I could then boot into recovery and reflash sh*tkat.
swukjay said:
No I know how to flash recovery and use adb, my problem as stated is phone will not boot into recovery when stock is flashed
Quote: then tried to restore stock recovery which didnt go well either, after flashing via adb I then tried to reboot into recovery to force a update to stock using update app i was still greeted with the team win logo which after a few seconds would just blink every few seconds, I then had a hell of a job restoring the twrp so I could then boot into recovery and reflash sh*tkat.
Click to expand...
Click to collapse
If you have custom rom up then you probably have root too. So try this: get an app called rashr from store and allow it root permisions, then get the stock image of the recovery and put it in the storage and flash it with the app. Get the update.app ready too (in dload folder) on the storage too and try to reboot in recovery.
Sent from my SM-G850F
tileeq said:
If you have custom rom up then you probably have root too. So try this: get an app called rashr from store and allow it root permisions, then get the stock image of the recovery and put it in the storage and flash it with the app. Get the update.app ready too (in dload folder) on the storage too and try to reboot in recovery.
Sent from my SM-G850F
Click to expand...
Click to collapse
As I stated its not flashing recovery thats the problem
Thanks for all your help turns out it was the wrong TWRP lol