my phone will not boot into recovery mode through CWM or by powering off and manually starting it. I get a dead android with a red triangle and ! sign, how can i fix this?
galaxy nexus (verizon)
4.0.2
rooted via Gnex tool kit
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
If you are rooted, you need to check the CWM thread for the file to delete through root explorer and then re-flash CWM to get it to stick.
Or use rom manager to flash it.
Jubakuba said:
Or use rom manager to flash it.
Click to expand...
Click to collapse
Ah yea, good point.
I prefer the difficult and manual way lol
Or re-flash your recovery from fastboot, then boot into it, and install whatever ROM you wanted.
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
bk201doesntexist said:
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
Click to expand...
Click to collapse
I agree. This option will let you boot into cwm once. when you finish there and reboot your nexus will wipe every trace of cwm. When you need it again just use the same trick again.
Sent from my Galaxy Nexus using XDA
anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
Before anybody suggests I use search - I DID search, and it brought me to this thread.
Background: After unboxing my shiny new GNex last week, I immediately flashed stock yakju IMM76D using GNex Tookit.
So ... let me make sure I understand this. With stock recovery, when I fire up fastboot and select recovery, it is NORMAL to get the little dead robot with a red triangle above him? And the only way I've found to get out of it is to pull the battery? Seems odd.....
(I did temporarily flash CWM via the Toolkit and it worked fine. I don't want to leave it on as I understand it will prevent me from getting future OTA updates.)
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
If you get that error, your phone will reboot after a minute or so, but like I said it should be gone after flashing a custom ROM.
Theshawty said:
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
Click to expand...
Click to collapse
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Zepius said:
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Click to expand...
Click to collapse
I renamed it, it should be the same as doing away with it. However, upon rebooting, I faced that triangle. I ran stock 4.0.4 by the time.
you still have to reflash CWM after deleting/renaming the file.
Zepius said:
you still have to reflash CWM after deleting/renaming the file.
Click to expand...
Click to collapse
Which I did, but the problem wouldn't wanna go away.
Theshawty said:
Which I did, but the problem wouldn't wanna go away.
Click to expand...
Click to collapse
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
efrant said:
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
Click to expand...
Click to collapse
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
I haven't read about the install script but ill be sure to follow your guide when and if I ever return to stock. They're awesome.
Sent from my Galaxy Nexus using Tapatalk 2
Theshawty said:
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
Click to expand...
Click to collapse
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Theshawty said:
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Click to expand...
Click to collapse
Who knows? I personally don't care, and no one else should either, as:
1) the OTA update file to IMM76D is availability for any yakju user to install,
2) the full IMM76D image is available to install,
3) the IMM76D source has been pushed to AOSP.
Those are three options for you to get IMM76D on your device, with the first one being the same as an OTA update.
For me, IMM76D runs perfectly fine, and better than ICL53F.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
For me, IMM76D runs perfectly fine, and better than ICL53F. 2
Click to expand...
Click to collapse
What radio are you using? The XXLA2?
Related
Hello. I'm not eligible to post in the development section so I'm posting it here instead. So I've unlocked the bootloader and rooted the phone via the GNex Toolkit 3.0. My next step is flashing CWM but since I'm keeping my stock rom, I need to delete recover-from-boot.p from /system.
However, I can't find this file anywhere in the /system folder. I'm using root explorer, btw. Should I just go ahead and flash CWM and not worry about the stock recovery coming back?
Thanks in advance.
gtm3nky said:
Hello. I'm not eligible to post in the development section so I'm posting it here instead. So I've unlocked the bootloader and rooted the phone via the GNex Toolkit 3.0. My next step is flashing CWM but since I'm keeping my stock rom, I need to delete recover-from-boot.p from /system.
However, I can't find this file anywhere in the /system folder. I'm using root explorer, btw. Should I just go ahead and flash CWM and not worry about the stock recovery coming back?
Thanks in advance.
Click to expand...
Click to collapse
good call posting here (question = Q&A) gsm versions don't have it
ogdobber said:
good call posting here (question = Q&A) gsm versions don't have it
Click to expand...
Click to collapse
I have same issue, cannot find recovery-from-boot.p in /system? I need to rename it or delete it because must to flash recovery image at every phone reboot... Or do you have some other solution?
vintermut said:
I have same issue, cannot find recovery-from-boot.p in /system? I need to rename it or delete it because must to flash recovery image at every phone reboot... Or do you have some other solution?
Click to expand...
Click to collapse
flash a custom rom, every custom rom has it removed(or flash a rooted stock/aosp).
Only ota puts the files there; if you flashed a factory image, then the files ain't going to be there. If they aren't there, can't delete them. Why would you want to put them there again? lol
Dump that toolkit and do it proper. Also, search/dig through q&a before posting.
Sent from my i9250
simms22 said:
flash a custom rom, every custom rom has it removed(or flash a rooted stock/aosp).
Click to expand...
Click to collapse
I have custom ROM (Minco v5). If there is no that file why I must flash recovery every time at phone reboot?
vintermut said:
I have custom ROM (Minco v5). If there is no that file why I must flash recovery every time at phone reboot?
Click to expand...
Click to collapse
clockworkmod has a new feature that gives the option to disable "recovery from boot" on the first restart from it.
however, what commands are you using to flash your recovery?
it must be
Code:
fastboot flash recovery name-of-recovery-image.img
ogdobber said:
clockworkmod has a new feature that gives the option to disable "recovery from boot" on the first restart from it.
however, what commands are you using to flash your recovery?
it must be
Code:
fastboot flash recovery name-of-recovery-image.img
Click to expand...
Click to collapse
Yes, that is the command that I use.
I've installed it correctly but once i boot into recovery I just get a picture of android with a warning sign being pulled out of his stomach...
so im with factory reset phone in the middle of flashing a new rom and can't continue
I really don't know what's wrong bud you may need to use a toolkit or a program to fast boot your device back to stock. Which version of the nexus do you have?
Sent from my Galaxy Nexus using xda app-developers app
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you update your Android build either using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse
This is from Efrant's Android 101 guide: http://forum.xda-developers.com/showthread.php?t=1812959
Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.
Petrovski80 said:
Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.
Click to expand...
Click to collapse
or you can just flash the stock recovery with fastboot.
thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted
Fking1 said:
thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted
Click to expand...
Click to collapse
You have to mount /system as read/write
DynamicRam said:
You have to mount /system as read/write
Click to expand...
Click to collapse
no idea how to do that
Fking1 said:
no idea how to do that
Click to expand...
Click to collapse
Use another file explorer such as Solid Explorer. https://play.google.com/store/apps/details?id=pl.solidexplorer
This is amazing, got help within minutes and as i write this the new rom is being installed, thank you so much!
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
19blacktiger77 said:
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Click to expand...
Click to collapse
...
19blacktiger77 said:
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
Click to expand...
Click to collapse
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
19blacktiger77 said:
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Click to expand...
Click to collapse
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
19blacktiger77 said:
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
Click to expand...
Click to collapse
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
bk201doesntexist said:
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
Click to expand...
Click to collapse
Sorry, fastboot.
bk201doesntexist said:
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
Click to expand...
Click to collapse
I read this, but i remember that with my phone i use a option with Galaxy Nexus ToolKit or Nexus Root Tolkit to prevent the recovery from be rewritten.
bk201doesntexist said:
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
Click to expand...
Click to collapse
My phone works fine, i can't understand why in phone's friend after installing GooManager and flash TWRP recovery, system got crazy...
If you did not use the toolkit I may get around my last arse helping you......
Beamed from Maguro
When going through the options before you install your twrp use option 5 to change the name and then use option 5 after you install twrp again... then the recovery will stick. It's all in the tool kit to read. Read everything that's in the instructions. It's right there when you go to install your recovery.
This is meant to be a friendly suggestion, so hopefully I won't get trounced but here goes. In the Sprint GNEX android development section, there are two stickies that explain the GNEX toolkit method of rooting, one by QBKing77 and the other by MSkip., two smart guys. A new guy or gal might think because there's no other way presented here that using a toolkit is the way to go. Maybe a correct, long form rooting guide could be placed along side these two guides in the development section.
In the Q and A section there is a stickie by Jobakuba that explains how to root the "right", long way. It might help new people and even people that have been around a while, if her guide or something similar was along side the QBKing videos and MSkips toolkit guide.
BTW, the QBKing video is new. He added the toolkit method fairly recently with the jellybean OTA. His new video replaces a video that showed the adb, fastboot method. When you go to the old video, you get redirected to the toolkit video.
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
bk201doesntexist said:
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
Click to expand...
Click to collapse
Two threads to teach people how to use the brainless toolkits... vs the 6 or 7 step guide by Jubakuba on how to actually do it yourself and know what's going on.
This is what's wrong with today's Android community.
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
El Daddy said:
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
EDIT - deleted
Sent from my Galaxy Nexus using Tapatalk 2
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Just download superuser and simply place it on your phones SD card it's really easy
Sent from my SPH-L710 using xda app-developers app
ricanjoe said:
Hey guys I followed this guide
http://forum.xda-developers.com/show....php?t=2235366
I used a file called "CF-Auto-Root-d2spr-d2spr-sphl710.tar"
Everything goes well and I get a green pass from oden3, the phone reboots. But superSU is not installed and when I check "Root checker" there is no root....
I have 4.1.2
Thoughts?
Click to expand...
Click to collapse
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
billard412 said:
Your phone is not finishing the process it seems. After Odin says pass do you get a big red Android on the screen? If not flash the cf auto root file but uncheck auto reboot in Odin first. Then when it finishes, pull the cable and remove the battery. Reinsert the battery and manually boot to recovery by holding volume up+home+power and it should finish installing root.
I don't know what the post above me is taking about. Installing superuser isn't going to magically give you root. js
Click to expand...
Click to collapse
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
ricanjoe said:
Yes its a screen with red letters and numbers saying the phone will reboot in 10 seconds.... So I re root in oden? then I pull the battery out before reboot? Could this brick my phone?
Thanks foe the help
Click to expand...
Click to collapse
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
About to give it a shot. Placing the root file on my external SD and phone into download mode, about to launch the odin app on pc.
billard412 said:
It wouldnt brick the phone but if you are seeing the red android then i was mistaken about what your issue is so disregard. Is your phone new? I bet the issue is related to one others are having where recovery cant mount partitions. To confirm that try this. Download this and place on pc http://goo.im/devs/billard412/d2spr/AUTOBOOT_RECOVERY/SPH-L710_TWRP_AUTOBOOT.exe
Its a odin one click that will autoboot you to twrp recovery just open it and click start with your phone connected in download mode.
Download this and place on your sd card. (preferably external)
http://forum.xda-developers.com/attachment.php?attachmentid=1584076&d=1356201390
If you can successfully flash that zip, it will root the phone.
Click to expand...
Click to collapse
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
ricanjoe said:
my man, so far im in a 'team win recovery project screen' its all blue and stuff
this is pretty exiting for me.
So what do I press now? what does this screen mean?
(some personal insight, I have rooted my old evo 3d back in the day but il still pretty noobish, the twrp thing rings a bell)
Click to expand...
Click to collapse
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
billard412 said:
You want to press install then hit "up a level" until youre in the root "/" directory. Then choose "external_sdcard" then tap "root.zip" and swipe to confirm at the bottom.
Click to expand...
Click to collapse
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
ricanjoe said:
sweet man, Im in root checker and it says "congratulations this device has root access"
I wanted to ask you how does this method differ from the method I was trying to perform?
Click to expand...
Click to collapse
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
billard412 said:
It's basically the same thing. Cf auto root will install a special recovery made by chainfire and a cache.img with a root zip. It's supposed to flash that zip then restore stock recovery. I've never seen cf auto root fail to do the job so im not sure what went wrong.
But the way you did it was you installed your own custom recovery and manually flashed a root zip created by me instead. Only thing different here is that you still have that custom recovery instead of stock recovery now.
Click to expand...
Click to collapse
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
ricanjoe said:
Got it man, is this custom recovery better than the stock or is it essentially the same? I plan to install a custom rom soon.
(I didn't find many threads like this on google nor the search tool so hopefully people with the same strange problem as me will now find it. Should be useful)
Click to expand...
Click to collapse
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
STOCK RECOVERY TAR
billard412 said:
The custom recovery is the same with the exception that it gives you additional privileges over stock recovery. Like installing custom roms, so if you're planning on a custom rom soon then you may as well just stick with the custom one. I do however recommend you download goo manager from the playstore and updating your recovery to the newest with it before trying to flash anything. The recovery I gave you may be a little outdated. And if for any reason you want stock recovery back I'll make a odin tar of it and place it in this post
Click to expand...
Click to collapse
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
ricanjoe said:
I got the goo manager, which recovery do I update to?
The app wants me to update to open recovery twerp 2/6/2/0/d2spr.img
Click to expand...
Click to collapse
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
advocatebutdfh
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Click to expand...
Click to collapse
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
ricanjoe said:
Alright man I wont waste anymore of your time here, just want to say thanks for all the help, this gives me the courage to continue to learn more about rooting and custom roms. I was about to give up last night because of this frustrating issue I had. Thanks again!
Click to expand...
Click to collapse
No problem glad to help. And just in case u need it, the stock recovery tar is attached below.
billard412 said:
Just open it. Hit Menu then tap "install openrecoveryscript" Then "Yes". Then "Yes" again. It'll download the latest TWRP and flash it automatically.
Edit:sorry had to reread that. Twrp 2620 is right
Click to expand...
Click to collapse
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
ricanjoe said:
about to install moar rom. I saw a video saying you should wipe dalvic cache and do several other things before.
Is there anything you reccomend I do before I flash this custom rom (Moar)
Click to expand...
Click to collapse
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
billard412 said:
Just a factory reset. It should automatically wipe the cache and other areas that need wiped. I've ran moar before it's am awesome rom
Click to expand...
Click to collapse
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
ricanjoe said:
Awesome im working on it now, also do you backup efs? Or is that just for the paranoid crowd?
(I will give you a shout out on my next vid
Click to expand...
Click to collapse
Personally I think the chances of your efs going bad are slim and a backup is more for paranoid people. With that said it never hurts to back it up. I just wouldn't restore it unless you have to.
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
MColbath said:
I updated the software on my DEB Nexus 7 from KOTH49H to KVT49L and now I can't install TWRP.
Are they in progress of making a new recovery img so that it works or should I revert back to KOT49H?
Click to expand...
Click to collapse
Do you still have root? What was the error?
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
MColbath said:
There is no error it flashes TWRP and then when I boot recovery it is still stock recovery. I am unrooted.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you outline the exact steps you are doing to flash?
mdamaged said:
Can you outline the exact steps you are doing to flash?
Click to expand...
Click to collapse
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
MColbath said:
I originally started out with PA 5.0 BETA but, then I reverted to stock to get the update. Full flash black to 4.4.2 KOT49H then I factory reset it once more to make sure everything is okay. After that I completed the setup Wizard and let all the apps update, after that was done I would reboot the tablet and then activate developer options. I flash using a batch I made that simply boots the tablet into bootloader then it uses the command fastboot flash recovery openrecovery-twrp-2.6.3.1-deb.img and reboots the device. Once it boots up I reboot into recovery and it shows the stock recovery instead of TWRP.
Click to expand...
Click to collapse
In the process of resetting back to factory, did it relock your bootloader? I ask only because some tools do this automatically. I had to ask.
mdamaged said:
In the process of resetting back to factory, did it relock you bootloader? I ask only because some tools do this automatically. I had to ask.
Click to expand...
Click to collapse
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
MColbath said:
Nah, I did it manually to see if locking and re-unlocking it would allow TWRP to be flashed but, that didn't work.
Click to expand...
Click to collapse
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it (a suggestion to use goo was here, but forget that).
If you can boot into twrp using the above suggestion, you can at least root and get some stuff done while waiting for a fix or update or someone more knowledgeable than I to solve your issue.
The only thing I can think of is that the bootloader changed and we are back to where you started, waiting for them to update it for your bootloader.
mdamaged said:
Welp, can you BOOT into twrp...i.e. fastboot boot openrecovery-twrp-2.6.3.1-deb.img then you can root it and try using...goo manager (never used this myself heard some good, some bad things, about it YMMV etc etc).
Click to expand...
Click to collapse
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
MColbath said:
No, well I can temporarily boot into TWRP using Wugfresh's kit but, that's the only way I can boot into TWRP. I'm not sure if that will work but, I will give it a shot.
Click to expand...
Click to collapse
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Okay seems good.
mdamaged said:
Don't bother with goo (they disabled downloads and it seems for good reason), see my edits in last post.
Click to expand...
Click to collapse
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
MColbath said:
Worked well I was able to root, install BusyBox (latest), and install glitch kernel without bricking. Thanks for the help.
Click to expand...
Click to collapse
No problem, thanks for the update.
mdamaged said:
No problem, thanks for the update.
Click to expand...
Click to collapse
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
MColbath said:
I am browsing the root and it seems like they made a backup file that defaults it back to the original recovery. I am assuming this has something to do with Verizon because they patched a lot of stuff in the update or so it seems.
Click to expand...
Click to collapse
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or location or added a new one (with a diff name) or did something with the permissions so it could not be renamed, and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
mdamaged said:
Hmm, as you probably know there is a file that is normally renamed in the process of installing recoveries to prevent that, my guess is they changed the name or added a new one (with a diff name), and I'll bet if you boot into twrp and rename that file you'll be able to flash and boot into twrp, though I'd make sure the contents of that file ONLY do that one thing, and that renaming it won't cause it to boot loop.
Click to expand...
Click to collapse
Yeah there are new backup files all over the place in System partition.
MColbath said:
Yeah there are new backup files all over the place in System partition.
Click to expand...
Click to collapse
Stupid providers.
mdamaged said:
Stupid providers.
Click to expand...
Click to collapse
I'm checking the developer block section of recovery right now.
I'll upload the log for the recovery too. Hold on.
Here it is.
MColbath said:
Here it is.
Click to expand...
Click to collapse
Is there a file in /system named recovery-from-boot.p?