I rooted successfully via Towelroot but did not unlock the bootloader. I ran the 1.1 Update and lost root. I ran Towelroot again and rerooted but I had to redownload the binaries and got everything functioning properly. I decided I wanted a custom recovery for backups and such so I installed Flashify and downloaded the CWM recovery file.
Here's the problem. I apparently flashed the recovery as a boot image as I now boot into CWM every time. CWM seems to be functioning properly but the system just boots into CWM every time.
I have not done anything else to try and fix this as I'm feeling rather like, at this point, I'm more likely to break it further if I haven't already broken it beyond repair.
Is there a file I can flash through CWM to restore the correct boot image?
I've been rooting and ROM'ing since early 2010 on my OG Droid and this is the first device I've actually thought I might have flashed myself into a brick but it's also the first device I've tried anything on without an unlocked bootloader.
Any constructive advice will be most appreciated. Thanks.
You are not bricked. Get the recovery image from https://developer.nvidia.com/develop4shield, and enter the bootloader and flash it following the instructions at https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt.
In your case you probably only need to flash the boot partition, but if that is not enough then flash them all.
Gnurou said:
You are not bricked. Get the recovery image from https://developer.nvidia.com/develop4shield, and enter the bootloader and flash it following the instructions at https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt.
In your case you probably only need to flash the boot partition, but if that is not enough then flash them all.
Click to expand...
Click to collapse
I'm working on it now; thank you! It appears I must be a Registered Developer to d/l the recovery file so I've applied and am awaiting approval.
Narsil007 said:
I'm working on it now; thank you! It appears I must be a Registered Developer to d/l the recovery file so I've applied and am awaiting approval.
Click to expand...
Click to collapse
Here is the boot.img file that you need, extracted from the Nvidia Recovery file.
cam30era said:
Here is the boot.img file that you need, extracted from the Nvidia Recovery file.
Click to expand...
Click to collapse
Fast boot=lifesaver
It took awhile but I'm back in business. Thank you!
Unfortunately, I lost everything and it started with the setup screen but at least I'm not out a $300 tablet :laugh:
Narsil007 said:
It took awhile but I'm back in business. Thank you!
Unfortunately, I lost everything and it started with the setup screen but at least I'm not out a $300 tablet :laugh:
Click to expand...
Click to collapse
Glad to hear it.
Related
Hi,
I had before the OTA for Jelly Bean an ICS unlocked and rooted.
I tried to use ShabbyPenguin to get it rooted again but now I have a broken recovery.
So not sure what do I need to get it rooted again.. Is it possible?
Thanks!
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Not sure if it is possible to flash cwm trough adb... However I will try it later today...
And yes, bootloader is still unlocked...
rustyjay said:
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Click to expand...
Click to collapse
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
hhhmmmm... no luck yet...
I tried to flash a recovery and it keeps giving me a message
<waiting for device>
After that it seems like stuck..
I read somewhere else that maybe because of the drivers, but I already tried a couple of versions 1.3.8 and 1.5.6 with the same result...
btw I'm using a Windows 7 64 bit machine...
Not sure if use a Linux machine will have any benefit...
rustyjay said:
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
Click to expand...
Click to collapse
Well...
Also tried the google usb drivers with no luck....
I guess that I will try it with some other windows/linux version later today...
Off but on topic. Describe what you call a broken a recovery please.
When I try to run the recovery it appears a dead android with a red exclamation mark on the screen....
After that it takes some time to reboot again...
albundy2010 said:
Off but on topic. Describe what you call a broken a recovery please.
Click to expand...
Click to collapse
That is stock recovery. It is not broken.
Yes I was saying it was broken because before the OTA update I had twrp as recovery, and now I can't flash any recovery
albundy2010 said:
That is stock recovery. It is not broken.
Click to expand...
Click to collapse
When you flash/install a ota your recovery gets wiped back to stock once it boots up due to the flash recovery script in the stock ROM.
Nothing is wrong with your device. Just follow a real guide on how to unlock and root. Real meaning using the SDK. Or even use one of those stupid one click crap. should not have a issue.
Guides are in the forum stickies.
Hi Guys,
Well not sure what the problem was.... maybe the drivers, maybe Win7 64 bits or I don't what...
I used a WinXP machine with the pdanet installed and it worked like charm...
I succesfully installed the recovery and root again.
Anyway... thanks for your time.
Glad to hear that.
I bought a used TF300T, 16GB
Unlocked
It has TWRP 2.4.4.0, JB 4.2 bootloader, and EnergyROM 3/28 10.6.1.8
Kernel 3.1.10-g59bc3cb
I was wondering if I should leave it alone, or restore it to factory. Is that even possible?
If I keep it as it is, how do I update?
I knew I should have bought a virgin Asus, lol.
Thanks for any info!
You can restore it to factory by flashing a stock Asus blob in recovery (I recommend using the 10.6.1.8 ROM since that was the last one on your tablet). It will wipe all data, including whatever's on the internal storage. Once you get that set up, flash the OTA updates incrementally to avoid issues (there are only two updates to flash). You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be.
All the blobs you need should be on Asus' website. If you need more help, there are lots of "how to flash back to stock" threads with instructions. Just read carefully, and if you decide to flash a custom recovery when you're done, DO NOT flash one with "-JB" at the end of it or you could brick your tablet. You will need a recovery that ends in "-42". Be absolutely sure, because there are 3 different bootloaders for the TF300, and flashing one from either of the other bootloaders will brick your tablet.
EndlessDissent said:
...You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be...
Click to expand...
Click to collapse
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
skank_boy said:
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
Click to expand...
Click to collapse
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
EndlessDissent said:
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
Click to expand...
Click to collapse
Okay, I will try again. Maybe three times the charm. Thanks!
skank_boy said:
Okay, I will try again. Maybe three times the charm. Thanks!
Click to expand...
Click to collapse
You've flashed the stock blob in TWRP twice already? You're not flashing TWRP afterwards, are you? I've flashed a stock blob in TWRP, and I had the stock recovery afterwards. Are you rebooting into Android after you flash it?
I tried to flash, it failed....BUT this time it worked (??!!) lol.
Obviously I wasn't doing something right, but I have now. I installed 10.6.1.8, now on to the next in the normal manner.
Thanks again!
I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
theoreticaljerk said:
I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
Click to expand...
Click to collapse
Flash recovery manually.
Turn on USB debugging
Open the folder that has the tool files. Find the one that had adb, fastboot and aapt. Go up one folder. Hold the shift key and right click the folder that has adb etc. There is a option in the right click menu that says something to the effect of 'open in command prompt', select it. in the command prompt type: adb reboot bootloader Hit enter.
Copy the cwm img file into the folder with adb and fastboot. Go back to the command prompt. Then type fastboot flash recovery <name of recovery>.img Hit enter. If it doesnt reboot type: fastboot reboot Hit enter.
Enjoy.
Tip: when typing the name of the cwm image type the first few letters then hit tab to autocomplete the name.
Unfortunately, while the commands went through without error, it still has the stock recovery.
theoreticaljerk said:
Unfortunately, while the commands went through without error, it still has the stock recovery.
Click to expand...
Click to collapse
Bad download maybe? Give TWRP a try.
Unfortunately I did.
theoreticaljerk said:
Unfortunately I did.
Click to expand...
Click to collapse
When you go into the bootloader it does, in fact, say you are unlocked?
Sent from my DROID RAZR HD using Tapatalk 4
I was using mattlgroff's utility and the first time I tried CWM it failed. I didn't have my phone rooted, but I had the bootloaded unlocked. So, I just rooted the phone and reflashed CWM and it was fine. I think that same utility has the old software on it, so if nothing else, just flash the old software, root, and then install your recovery.
mentose457 said:
When you go into the bootloader it does, in fact, say you are unlocked?
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
It does still say UNLOCKED.
al2fast said:
I was using mattlgroff's utility and the first time I tried CWM it failed. I didn't have my phone rooted, but I had the bootloaded unlocked. So, I just rooted the phone and reflashed CWM and it was fine. I think that same utility has the old software on it, so if nothing else, just flash the old software, root, and then install your recovery.
Click to expand...
Click to collapse
I can't root because I'm on the latest VZW version.
theoreticaljerk said:
It does still say UNLOCKED.
I can't root because I'm on the latest VZW version.
Click to expand...
Click to collapse
You can flash back to the last version then root. Then you can try flashing CWM or TWRP.
EDIT: Im pretty sure they found a way to root the latest OTA.
mentose457 said:
You can flash back to the last version then root. Then you can try flashing CWM or TWRP.
EDIT: Im pretty sure they found a way to root the latest OTA.
Click to expand...
Click to collapse
Correct me if I'm wrong though...but I don't believe you need root to flash a recovery.
theoreticaljerk said:
Correct me if I'm wrong though...but I don't believe you need root to flash a recovery.
Click to expand...
Click to collapse
You shouldn't but these phones are a bit wonky when it comes to that sort of stuff. For example you dont need root to unlock the bootloader on any other phone except this one.
What does the stock recovery even look like? Ive never been there. After flashing the recovery how are you getting to recovery? Are you using the terminal or command prompt on your computer or are you holding the up/down/power combo the arrowing down to recovery and then arrowing up?
theoreticaljerk said:
I had my phone bootloader unlocked, CWM loaded, and rooted. I decided I didn't really need root and was messing around so I took the VZW update which, of course, required me to flash the stock recovery.
Well, I wanted to play with the new CM 10.2 so I went to flash CWM back on using mattlgroff's utility and while I don't receive any errors and it reboots the phone, the stock recovery is still there.
Any way to flash a recovery or am I hosed? I thought it was only motochopper I couldn't use on the new VZW firmware.
Click to expand...
Click to collapse
Ive found the solution to this if you still haven't...
You need to have root. How you get that is up to you. I flashed back to the last rootable OTA, rooted, used voodoo root keeper to backup root, then took the OTA and restored root with voodoo. Once I had root again i used Root Explorer to rename the file called recovery-from-boot.p in /system . Then I booted into fastboot mode and flashed the recovery like normal. That was it.
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
albert_htc said:
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
Click to expand...
Click to collapse
dont use root toolkits.
flash the factory img via fastboot. then flash twrp again, flash a kernel that allows root, then flash the latest supersu.
Thanks for the reply.
Just want to claify to make sure I don't make it worse..
I've got the L image from Googles site, do I extract the factory.img from that ?
Then flash it using :
fastboot flash factory factory.img
Thanks
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
albert_htc said:
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
Click to expand...
Click to collapse
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
Found out how I've managed to double click.. The trackpad on my laptop is playing up.
I'll have to remember to use a USB mouse with it.
The phone has just rebooted and is coming back up.
Thanks for the advise.. looks like it's working.
I'll start a new thread with a couple of follow up questions.
Thanks
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Jmurf said:
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Click to expand...
Click to collapse
it appears that the flash-all is having issues and skipping. so by flashing them all individually, you will make sure to flash them all.
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/