How do I backup my stock recovery? - One (M8) Q&A, Help & Troubleshooting

I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?

tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist

v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile

Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---

Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.

tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)

Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.

redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.

Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.

Related

[Q] Nexus 7 Newb would like feedback on plan for setting up my device

I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick
I presume you have a custom recovery installed in addition to the ClockWorkMod Manager? If not, use the WugFresh Nexus Root Toolkit to install that, then boot into the recovery and select the backup option. It will create a folder on the root of your device called clockworkmod which will contain your backups. Just copy that to your PC, and transfer it back to the device when you need it.
C5Longhorn said:
I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.
Wrngway said:
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.
Click to expand...
Click to collapse
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
TWRP working fine here..
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
Just backed up stock KitKat to a thumb drive and flashed newest 4.4 Omni Rom from thumb Drive. Use the WugFresh Nexus Toolkit to flash recovery. It makes it much simpler.
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.
Wrngway said:
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.
Click to expand...
Click to collapse
Ok, maybe I was doing something wrong. The command line indicated it was installing correctly when I flashed it. However, when I rebooted to recovery it was never TWRP.
I just installed Clockworkmod Recovery so it was probably an error on my end.
Now, since I have made a backup, how can I identify where it is stored? I would like to move it to my computer since I only have a 16gb 7.
Thanks for all the replies,
Rick
I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.
Wrngway said:
I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.
Click to expand...
Click to collapse
great, thanks for all the help. I will probably reflash back to stock and then rebuild my device and backup. I have OCD about making sure I've got the cleanest install and right now don't know that for sure since it's been trial and error.
They are saved in /mnt/shell/emulated/clockworkmod/backup
They are hidden from other apps, so you need a file explorer with root to move them.
Great, thank you for the reply. The help from folks on the forum has been fantastic and really helps a newb.
Rick

[Q] What to do now?

So I have to admit I am pretty overwhelmed but the amount of information. So I wanted to find out from the community what do I do now.
My RAZR my is rooted, boot loader unlocked and on stock KK 4.4.2. I have no idea how to get the customer recovery on my phone the forrest ways as I have seen it many different ways. SO how it it I get TWRP on my device now. Once I do, is that how I install a rom? Will that wipe the stock one?
Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.
xKroniK13x said:
Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.
Click to expand...
Click to collapse
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?
nxion said:
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?
Click to expand...
Click to collapse
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.
xKroniK13x said:
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.
Click to expand...
Click to collapse
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.
nxion said:
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.
Click to expand...
Click to collapse
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.
xKroniK13x said:
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.
Click to expand...
Click to collapse
Boot image is linux kernel, do not try to touch it.
Klen2 said:
Boot image is linux kernel, do not try to touch it.
Click to expand...
Click to collapse
Good to know lol. Thank you.

HTC One M8 How to backup stock image

Hey All,
Model: HTC One M8 - 0p6b160
CID: TELUS0001
Got a HTC One M8 the other day, I have already dev unlocked it via HTC, but I'm looking to have root and if possible s-off but stay on the stock image.
I've been wanting to backup the recovery image (since there seems to be very little resources for the TELUS001 CID) but from everything I've read this can only be done once you have root using adb and dd. To get root I need to install TWRP or PHILZ.
What I'm not clear about:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Thanks
felix2000 said:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Click to expand...
Click to collapse
1 and 3. You can backup stock recovery by booting into custom recovery that is located on your computer, instead of flashing custom recovery to the phone. This is already what you have described in Item 3. Is your phone in fastboot mode? The TWRP file is located in the same folder as fastboot.exe? Are you sure you have fastboot connectivity? To check this, type "fastboot devices" (with no quotes) and see if your device ID comes up.
Also, a great many stock recoveries are already posted here: http://forum.xda-developers.com/showthread.php?t=2701376
This thread also describes the process of backing up stock recovery via fastboot.
2. Not sure what you are asking. But yes, recovery can't backup something that isn't there (just current installed state).
4. Having custom recovery will prevent install of OTA, if that is what you mean. But return to stock recovery and restore any system files altered by root allows install of OTA. Or you can just install a custom ROM based on Android L when it comes out, as custom ROMs are sure to come quickly after L is available. Maybe even sooner than your version's OTA.

From Stock 5.1.1 to Custom 5.1.1

Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

Categories

Resources