Hi,
I installed TWRP and now, when I restart my nexus 7, it defaultly boots into TWRP. Is there a way to stop this and make nexus automaticaly boots into system? Because now, automatic updates are not working, cause when nexus reboots, it's in TWRP and update stops.
Thanks
In that case you most likely have a corruped boot partition and the kernel cannot be started. In hat case it's going automatically into recovery mode.
AndDiSa said:
In that case you most likely have a corruped boot partition and the kernel cannot be started. In hat case it's going automatically into recovery mode.
Click to expand...
Click to collapse
but when I choose reboot into system, it goes into system normally.
There is also a flag which says 'reboot to recovery', but this should be reset automatically when booting up the recovery. There is a chance that this flag will not get erased. What version of TWRP do you have installed?
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
There is also a flag which says 'reboot to recovery', but this should be reset automatically when booting up the recovery. There is a chance that this flag will not get erased. What version of TWRP do you have installed?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have v2.6.3.0
Try to flash 2.6.3.1, as far as I remember there were some issues with 2.6.3.0 and KitKat.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Try to flash 2.6.3.1, as far as I remember there were some issues with 2.6.3.0 and KitKat.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
that's the point, I do not have kitkat yet, cause everytime I launch auto-update, nexus reboots into TWRP instead of installing update.
jonny_pasta said:
that's the point, I do not have kitkat yet, cause everytime I launch auto-update, nexus reboots into TWRP instead of installing update.
Click to expand...
Click to collapse
??? But if ypu have TWRP installed as recovery, it's normal that it is booting to TWRP to apply the update. Then from TWRP you need to select "apply the update" and after that you will have KitKat installed. Or didn't I understand you well? But be aware that you will loose TWRP by applying the OTA.
AndDiSa said:
??? But if ypu have TWRP installed as recovery, it's normal that it is booting to TWRP to apply the update. Then from TWRP you need to select "apply the update" and after that you will have KitKat installed. Or didn't I understand you well? But be aware that you will loose TWRP by applying the OTA.
Click to expand...
Click to collapse
there is no such thing as "apply the update", I can only choose "install" and go into memory and select the file. But I do not know where the file is, I found one in chache with some strange name (random string), but it sais, that it's not compatibile with my system.
Related
Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
fastboot flash recovery recovery-image-file-name.img
while in boot loader mode.
Please use the forum search capability.
christanya99 said:
Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
simms22 said:
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
Click to expand...
Click to collapse
I have the same problem as the 1st poster, an i did what you said, in regards to letting goomanager do the work but it still didn't work
Sent from my rOot3d Samsung Galaxy S3
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
sashank said:
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
No I haven't did that. I'm away from my computer on a trip, an will do this when I get home
Sent from my rOot3d Samsung Galaxy S3
i tried installing cwm and twrp using fastboot.
everything is successful, but when i reboot to recovery it is still stock??
you must root your phone before installing custom recovery
None of the other methods work?
Sent from my Nexus 7 using Tapatalk 4 Beta
Coreym said:
None of the other methods work?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sorry, it's just that some tutorials are not complete at all.
To my understanding is that the device will recover the original recovery every reboot
ironlady said:
Sorry, it's just that some tutorials are not complete at all.
To my understanding is that the device will recover the original recovery every reboot
Click to expand...
Click to collapse
I'm pretty sure TWRP has an option to keep it. I'm using cwm and I can reboot fine. Its when flashing new firmware it will replace your custom recovery. CWM asks if you would like to disable recovery flash and selecting Yes let's you keep your custom recovery!
Sent from my X909 using Tapatalk 4 Beta
Coreym said:
I'm pretty sure TWRP has an option to keep it. I'm using cwm and I can reboot fine. Its when flashing new firmware it will replace your custom recovery. CWM asks if you would like to disable recovery flash and selecting Yes let's you keep your custom recovery!
Sent from my X909 using Tapatalk 4 Beta
Click to expand...
Click to collapse
the missing line in the script from your post was this
fastboot.exe boot cwm.img
edit: i haven't tried twrp yet
edit2: works for twrp too but don't need that line if coming from custom recovery already
So a while back I went through the process to root my phone and went with safestrap. Now it appears the new roms aren't compatible with safestrap (is it because of 4.3 gapps?).
How would I go about switching over to CWM? Is there anything fancy? Is there a guide? Any help appreciated.
Thank You.
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Leraeniesh said:
Is your boot loader unlocked?
If so, flash CWM through fastboot (there are a few guides on XDA of how to do so). Flashing a new ROM through CWM will remove safestrap.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yes unlocked. I will look it up. Thanks.
I believe you can also use backups made in Safestrap in TWRP (/data/ only)
Sent from my XT907 using xda premium
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
So I am getting the "cannot load cwm.img" on the command prompt.
cwm.img is in the same folder as fastboot and adb.
not sure what is up. Currently searching for solution....
EDIT: Typed full path. Seems to have worked....
RikRong said:
You'll need to uninstall recovery through the actual SafeStrap app. Then, you'll need to delete the app and all the SS folders.
Click to expand...
Click to collapse
Booted back into safestrap. I'm assuming this is why?
jagsfan82 said:
Booted back into safestrap. I'm assuming this is why?
Click to expand...
Click to collapse
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
RikRong said:
Yep that's why. SafeStrap works seperate from your recovery. If you actually boot into recovery do you get CWM? If not, you'll probably need to re-flash it. When you re-flash, boot back into recovery prior to booting into OS. This will assure that the install script is complete. Otherwise, your stock recovery will override CWM.
Click to expand...
Click to collapse
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
jagsfan82 said:
Just saw your last post... too tired. You mentioned deleting the app and folders. Is this most likely the issue?
Click to expand...
Click to collapse
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
jagsfan82 said:
Gotcha. Well I can uninstall it via a recovered system that still has safestrap on it. I did something weird trying to boot into CWM and when i start my phone it goes into the bootloader due to flash failure. I can override this with "fastboot continue", but i don't want to do something really bad... am I going to run into any issues if I get to CWM and flash a new rom?
Thanks for the help fellas
EDIT: Flash failure problem went away. Reflashed CWM, wouldn't boot via fastboot boot cwm.img, managed to get to recovery before system loaded... but still went to safestrap.. trying old fashioned SS uninstall now, then reflash, then boot into recovery.
EDIT 2: Uninstalled safestrap.. doesn't boot to bootloader now?
EDIT 3: Brought up safestrap on my eclipse rom, uninstalled safestrap. Went to bootloader. Flashed CWM supposedly successfully. Tried to run "fastboot boot cwm.img" only to get cannot load. Tried to go from bootloader to recovery manually (power button --> key press) but just loads up the OS.
Clueless now
Click to expand...
Click to collapse
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Leraeniesh said:
Do "fastboot flash recovery cwm.img" and open up the power menu via three button press, then select recovery.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
RikRong said:
I don't think that's the issue. Deleting the app and folders just frees up some space. I'll have re-read your other post and then I'll get back to you on it.
Click to expand...
Click to collapse
My first thought is I need to strip down the system.. maybe i didn't wipe something properly or what have you.
jagsfan82 said:
This is more or less what I did except the only difference is I hit power first, phone went off, then quickly did keypress. Went strait to OS.
Seriously appreciate help btw
Click to expand...
Click to collapse
Yeah unfortunately there's no command to boot recovery from fastboot.
You can try running "fastboot reboot" while holding the volume buttons right after flashing cwm. That should do the trick. It should boot to the boot selection menu, then you can choose to boot to recovery.
Also, thought you killed yourself when I read your other post...
fastboot boot cwm.img is one argument away from a very, very bad day... If you put "flash" before boot, you'd be in trouble... Lol
Maybe I should write up a root app that will rename install-recovery.sh... That's not a bad idea...
Sent from my XT907 using Tapatalk
I always just power down the phone after flashing recovery and then manually reboot into recovery.
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
sloosecannon said:
And done. Here's a link...
ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
I forgot to declare superuser in the manifest... I know, shoot me. Needs root access and all that jazz. Run the app before flashing recovery
Oh and rikrong, stole your avatar for the app icon
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Haha, nice.
RikRong said:
Haha, nice.
Click to expand...
Click to collapse
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
sloosecannon said:
Thankee
So, if someone on stock who wants to flash custom recovery could test this, that would be great. It should work, but as I have no stock RAZR Ms, I can't confirm it will work
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Installed on phone. Says found but disabled. Tried flashing cwm.img and rebooting into recovery. Still goes straight to OS...
Enable install-recovery doesn't work
this all seems very straightforward of a process that should be working...
Do I need to try wiping everything down as bare as possible?
Is this the process that works for others? Take safestrapped, rooted, bootloader unlock device on an old pre-bootloader-unlocked rom. Uninstall safestrap. Flash cwm.img using fastboot comand. Boot into recovery. Then you should be in CWM?
Hello,
I want to update my DEFY MB525 to 4.4.
I downloaded all necessary files from the thread
http://forum.xda-developers.com/showthread.php?t=2515036
In it, it is written "To install KitKat, need update recovery."
I did the update but I don't know how to verify it is ok.
What is the version that I should have ?
When I check, I have the Bootmenu ICS Recovery v5.6.7-jordan.
Is it ok ?
Can somebody help me on this ?
limonair said:
Hello,
I want to update my DEFY MB525 to 4.4.
I downloaded all necessary files from the thread
http://forum.xda-developers.com/showthread.php?t=2515036
In it, it is written "To install KitKat, need update recovery."
I did the update but I don't know how to verify it is ok.
What is the version that I should have ?
When I check, I have the Bootmenu ICS Recovery v5.6.7-jordan.
Is it ok ?
Can somebody help me on this ?
Click to expand...
Click to collapse
There is a tutorial in the general section, couldn't you read it?
Sent from my Nexus 7 using Tapatalk
[Q] DEFY MB525 - update to 4.4 : ok with Bootmenu ICS Recovery v5.6.7-jordan. ?
hotdog125 said:
There is a tutorial in the general section, couldn't you read it?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I read the GUIDEfrom that page : http://forum.xda-developers.com/showthread.php?t=2568325
But it it not written the version that is needed to install KitKat...
I just want to know if it's ok with the version I have ?
It looks like you haven't read the guide properly or don't have basic knowledge of what to do.
How did you "update the recovery"?
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
It looks like you haven't read the guide properly or don't have basic knowledge of what to do.
How did you "update the recovery"?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I rebooted my Defy, went to the stable recovery (volume down when blue light and select the right option).
Then I chose "Install zip from sdcard" and selected the file from defy.bytekiste.de directory cm11-nightly-defy+ file update-recovery.zip I have placed on my sdcard.
limonair said:
I rebooted my Defy, went to the stable recovery (volume down when blue light and select the right option).
Then I chose "Install zip from sdcard" and selected the file from defy.bytekiste.de directory cm11-nightly-defy+ file update-recovery.zip I have placed on my sdcard.
Click to expand...
Click to collapse
Follow the guide in that thread. It has not actually updated the recovery, since it updates a newer version of recovery than what you are using now.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Follow the guide in that thread. It has not actually updated the recovery, since it updates a newer version of recovery than what you are using now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Well, in the guide it is written :
# Updating Recovery: Go to recovery Mode in TWRP its better to wait for at least 30Sec after entering in recovery this waiting will ensure that your device won't Reboot when you are working in it. After update, reboot your device it is not necessary but it is okay to have one. DON'T ENTER IN SYSTEM GOTO TO RECOVERY AGIAN
Click to expand...
Click to collapse
I have the app TWRP manager, but I don't see a Recovery mode in it.
I don't understand what I do wrong ?
TWRP is the name of the recovery. I'll dumb it down for you.
Follow this procedure.
1. Go to the normal recovery (reboot phone, when blue LED lights up, press volume down. Then select custom or stable recovery.)
2. Download this zip to SD card and Install -
http://d-h.st/dWr .
3. Now reboot and press volume down when LED becomes blue.
4. Now, install this from SD card - http://d-h.st/dz8.
5. Immediately install the KitKat zip and then gapps. Also flash the update to the 29-12 build.
6. Reboot.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
TWRP is the name of the recovery. I'll dumb it down for you.
Follow this procedure.
1. Go to the normal recovery (reboot phone, when blue LED lights up, press volume down. Then select custom or stable recovery.)
2. Download this zip to SD card and Install - .
3. Now reboot and press volume down when LED becomes blue.
4. Now, install this from SD card - .
5. Immediately install the KitKat zip and then gapps. Also flash the update to the 29-12 build.
6. Reboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your procedure.
I followed it exactly.
I have a problem, when the system launches, I can't access to the desktop.
And I have an error "The proccess com.android.systemui has stopped"
I tried doing a wipe and restarting but it doesn't change anything.
Any idea ?
limonair said:
Thank you very much for your procedure.
I followed it exactly.
I have a problem, when the system launches, I can't access to the desktop.
And I have an error "The proccess com.android.systemui has stopped"
I tried doing a wipe and restarting but it doesn't change anything.
Any idea ?
Click to expand...
Click to collapse
Are you sure you used correct gapps?
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Are you sure you used correct gapps?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I took the file 12-14_GApps_Standard_4.4.2_signed.zip from http://forum.xda-developers.com/showthread.php?t=2012857
Try latest banks gapps
Sent from my MB526 using Tapatalk 4
thekguy said:
Try latest banks gapps
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
You mean the previous one (GApps_4.4.1_signed.zip) ?
limonair said:
You mean the previous one (GApps_4.4.1_signed.zip) ?
Click to expand...
Click to collapse
No, don't use the standard gapps. It's too large and fills up the /system partition. Instead, use banks Core gapps (the file called "12-14_GApps_Core_4.4.2_signed.zip").
Edit: Since you've already tried flashing the standard gapps, your system partition is probably full now. Here's what I'd recommend:
Go into Team Win (TWRP) recovery, and wait at least 30 seconds to make sure that it is behaving in a stable way. (Sometimes TWRP reboots suddenly within the first 20 seconds or so. It's a known bug.) Then flash safewipe.zip to wipe your system, cache, and data partitions. Then flash CM11, followed by the 03.01.14 Update, followed by Core gapps.
Proverbs2 said:
No, don't use the standard gapps. It's too large and fills up the /system partition. Instead, use banks Core gapps (the file called "12-14_GApps_Core_4.4.2_signed.zip").
Edit: Since you've already tried flashing the standard gapps, your system partition is probably full now. Here's what I'd recommend:
Go into Team Win (TWRP) recovery, and wait at least 30 seconds to make sure that it is behaving in a stable way. (Sometimes TWRP reboots suddenly within the first 20 seconds or so. It's a known bug.) Then flash safewipe.zip to wipe your system, cache, and data partitions. Then flash CM11, followed by the 03.01.14 Update, followed by Core gapps.
Click to expand...
Click to collapse
Thanks for you recommandations.
I will try it tomorrow, for the moment went back to CM10 as I need my phone to be operational for tomorrow morning
I've had the exact same problem like OP...and I can confirm that this order of things works!
4.4.2 KitKat on Motorola Defy+
Hi everyone.
I tried to flash latest CM11 and Gapps at my Defy.
It boots but i can only see the notification bar. Everything else is black. No launcher etc. I can go to settings from the notification bar but nothing more.
Any suggestions?
svizi said:
Hi everyone.
I tried to flash latest CM11 and Gapps at my Defy.
It boots but i can only see the notification bar. Everything else is black. No launcher etc. I can go to settings from the notification bar but nothing more.
Any suggestions?
Click to expand...
Click to collapse
Which gapps did you use? If you used standard gapps (rather than core gapps), your system partition is probably full now. Read a few posts above yours for the solution.
Hi,
I achieve to install CM11 on my Defy MB525.
As far as now, everything is working well.
My previous try was bad (black screen and no access to the apps) because of the GApps ("full" and not "core" ones).
Thank you hotdog125 & Proverbs2.
limonair said:
Hi,
I achieve to install CM11 on my Defy MB525.
As far as now, everything is working well.
My previous try was bad (black screen and no access to the apps) because of the GApps ("full" and not "core" ones).
Thank you hotdog125 & Proverbs2.
Click to expand...
Click to collapse
Well in fact I have a little problem.
I no longer have the superuser application.
How can I root the phone again ?
I have TWRP recovery, and stock rom.
Thing is, I sold to phone to a guy, he tried to install the update and now the phone reboots to recovery. I told him to restore the backup, he did so, but he says it still reboots to recovery everytime he tries. He doesn't boot to bootloader or recovery, but presses power off and then manually turn the phone on - still to recovery. I can't really help him because I can't see what's the problem.
What should we do?
If you have custom recovery you shouldn't take ota search for g2 ota twrp and you will find some helpful threads
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app
XxZombiePikachu said:
If you have custom recovery you shouldn't take ota search for g2 ota twrp and you will find some helpful threads
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok but my question is why when I restore it still boots to recovery? If I restored it then it should reboot regularly.