Develop Bugs

Cannot find recovery-from-boot.p

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.

Jellybean root

ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su

Thanks. May I clarify if I have to do both to get root or either one?

mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed

Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.

mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute

Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img

Thanks guys appreciate the tip.

not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.

krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update

Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.

Thanks guys you are amazing!!!

Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update

tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)

ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.

other superuser
still doesn't work, do you think you can try the other SuperUser app? D:

Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM

[please delete]

IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.

[Q] HELP. I may have bricked my phone.

I unlocked and rooted my phone just fine. I had CM10 zip on my SD, but I can't find it on my device to install it. I must have erased it along with my OS. I never wiped my internal storage so I have no idea what happened. Is there anyway I can get the zip back on the internal storage through TWRP? The device won't even reboot because there's no OS. Thanks,

Adb sideload a rom through TWRP.

thanks
063_XOBX said:
Adb sideload a rom through TWRP.
Click to expand...
Click to collapse
I'm a bit of a noob. I've done this with other devices, but never had any issues. Would you mind explaining how to sideload a Rom.

jquanmusic said:
I'm a bit of a noob. I've done this with other devices, but never had any issues. Would you mind explaining how to sideload a Rom.
Click to expand...
Click to collapse
Do u still have the rom
Try copying it to ad and flash using twrp.

am i screwed
I've been searching around and apparently TWRP 2.2 (what I have installed) can't ADB sideload. Am I screwed?

If you're proper worried reflash the factory image (guides are on here - you should have the file already as anyone would make sure they have a get out should things go wrong)

EddyOS said:
If you're proper worried reflash the factory image (guides are on here - you should have the file already as anyone would make sure they have a get out should things go wrong)
Click to expand...
Click to collapse
That's the thing. My Internal storage/sd card is wiped.

I think u dont have ur os
Download it and flash using odin.

jquanmusic said:
That's the thing. My Internal storage/sd card is wiped.
Click to expand...
Click to collapse
1991prince said:
I think u dont have ur os
Download it and flash using odin.
Click to expand...
Click to collapse
Doesn't matter, you can download the factory image and reflash the phone back to stock. Once working you can then try again

1991prince said:
I think u dont have ur os
Download it and flash using odin.
Click to expand...
Click to collapse
Don't listen to him. Keep Odin away from your Gnex.

okay i have din installed on my PC and my deice in DL mode, but Odin isn't recognizing my device. Ant ideas.

jquanmusic said:
okay i have din installed on my PC and my deice in DL mode, but Odin isn't recognizing my device. Ant ideas.
Click to expand...
Click to collapse
1. Ignore Odin as advised
2. Download the factory image from Google
3. Flash it
4. Learn to read instructions and search before posting

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Help no os on m8!!!

I have developer m8 and i accidently removed my Os please help I am rooted with twrp installed and unlocked bootloader!!
EDIT: Used RUU to fix phone worked like a charm!

Stop asking the same question in multiple threads or new threads. Its called cross-posting and is against forum rules. More importantly, it clutters up the forum; and makes it confusing for those trying to help you.
Case in point: I responded to one of your other posts. Go find it. See, isn't that confusing?

SomeArabDude said:
I have developer m8 and i accidently removed my Os please help I am rooted with twrp installed and unlocked bootloader!!
Click to expand...
Click to collapse
well, if you have no OS installed then you are no longer rooted, but that's pretty much irrelevant.
anyway, install a compatible ROM, using either:
1- the microsd card
2- adb push <name of rom>.zip /sdcard/
3- [start sideload in twrp] then adb sideload <name of rom>.zip
4- usb-otg

nkk71 said:
well, if you have no OS installed then you are no longer rooted, but that's pretty much irrelevant.
anyway, install a compatible ROM, using either:
1- the microsd card
2- adb push <name of rom>.zip /sdcard/
3- [start sideload in twrp] then adb sideload <name of rom>.zip
4- usb-otg
Click to expand...
Click to collapse
I have tried but it makes the zip corrupt

redpoint73 said:
Stop asking the same question in multiple threads or new threads. Its called cross-posting and is against forum rules. More importantly, it clutters up the forum; and makes it confusing for those trying to help you.
Case in point: I responded to one of your other posts. Go find it. See, isn't that confusing?
Click to expand...
Click to collapse
oops, sorry, didnt know about that.
OP, please do not cross-post or multi-thread. thanks!!

nkk71 said:
oops, sorry, didnt know about that.
Click to expand...
Click to collapse
No worries. Its his fault, not yours.

SomeArabDude said:
I have tried but it makes the zip corrupt
Click to expand...
Click to collapse
so from what you've been cross-posting, seems either
1- you have a bad download
2- the "zip" is not a flashable ROM

nkk71 said:
so from what you've been cross-posting, seems either
1- you have a bad download
2- the "zip" is not a flashable ROM
Click to expand...
Click to collapse
I suspect its number 2. I asked in another thread where he got the file, but he has yet to answer.

@SomeArabDude
@redpoint73 has already asked you:
Where did you get it from (link it)?
Click to expand...
Click to collapse

redpoint73 said:
I suspect its number 2. I asked in another thread where he got the file, but he has yet to answer.
Click to expand...
Click to collapse
I had got the file from this thread. Its a NANDROID backup. http://forum.xda-developers.com/showthread.php?t=2701376
I have tried multiple time but to no avail. I had sideloaded, pushed from adb and even got from ext sd to twrp . Nothing works
Just a bit frantic because my Dad had bought this for me unlocked for about ~600USD and I don't wanna let him down.

SomeArabDude said:
I had got the file from this thread. Its a NANDROID backup. http://forum.xda-developers.com/showthread.php?t=2701376
I have tried multiple time but to no avail. I had sideloaded, pushed from adb and even got from ext sd to twrp . Nothing works
Click to expand...
Click to collapse
well if it's a nandroid backup, then it is not a flashable zip. you need to extract that backup (whichever one you are using), and place it in the twrp backup folder (probably /sdcard2/TWRP/BACKUPS/<your serial number>/<backup folder name>)
then use restore, not install

Ok will try thanks for the help will inform of what happens!
Oh and will I get the OS back too?

SomeArabDude said:
Ok will try thanks for the help will inform of what happens!
Oh and will I get the OS back too?
Click to expand...
Click to collapse
yes, that's generally what backups are for. good luck
or you could just download a rom from the development section and "install" that (as opposed to restoring)

or just read the whole nandroid backup opening post, second post and even the third post.... just like the thread title says in capital text ! its all there under the "questions&answers"

nkk71 said:
yes, that's generally what backups are for. good luck
or you could just download a rom from the development section and "install" that (as opposed to restoring)
Click to expand...
Click to collapse
It doesn't work here is my log
Restore folder: '/external_sd/TWRP/BACKUPS/FA43VWM02209/2104-10-20--10-20-53 KTU84P release-keys'
Skipping MD5 check based on user setting.
Calculating resotre details...
Restoring 2 partitions...
Total resore size is 2247MB
Wiping Data...
Wiping data without wiping /data/media... Done
Restoring Data
Then it says FAILED at top in red

Mr Hofs said:
or just read the whole nandroid backup opening post, second post and even the third post.... just like the thread title says in capital text ! its all there under the "questions&answers"
Click to expand...
Click to collapse
How would I flash boot.img in TWRP from my Backup I open it and theres nothing from TWRP.
And there no boot.img in the NANDROID either from my computer.

you are clearly reading the half of it !
a boot.img or emmc.boot.win file is flashed by fastboot and not within the recovery.....read it.....read it ALL

look its written here.....

Mr Hofs said:
you are clearly reading the half of it !
a boot.img or emmc.boot.win file is flashed by fastboot and not within the recovery.....read it.....read it ALL
Click to expand...
Click to collapse
Now I have lost recovery because of this I had wrote fastboot flash recovery boot.emmc.win
EDIT: I reflashed TWRP and now do I restore the NANDROID BACKUP?

you dont loose a recovery when you flash a boot file !
if you can't follow those clearly written steps than i have no clue how to guide you !

Stuck rooting

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?

@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.

cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!

smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.

cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.

Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.

Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.

How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.

Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).

spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?

smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?

spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.

Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.

toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??

smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!

smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.