Related
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
ericsundiu said:
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
Click to expand...
Click to collapse
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
ericsundiu said:
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
Click to expand...
Click to collapse
Unlocking and rooting are two different things. There is no known root method at this time for the 10.6.1.14.10 firmware. The Unlock Tool should still work.
I don't think it's a question which firmware you have - sometimes it works like a charm and other users cannot unlock at all due to incorrect or incomplete S/N database on Asus servers. At least I have not heard anything that people have trouble unlocking after the last update.
Just download the latest version, v8 I think, install and run it. The worst that can happen is it fails.
Do yourself a huge favor and educate yourself thoroughly before you try to flash custom software to the tablet.
There is little risk in flashing a custom rom IF you do it right. But yesterday night I tried to help someone who did it wrong and hard bricked his tablet. Read 3 times, ask twice, flash once!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot
Click to expand...
Click to collapse
For flashing via adb and the staging partition, Android must be rooted. Fastboot works without root.
I did a clean wipe of my tablet and installed 10.6.1.14.10 onto my tablet.
I have unlocked the bootloader, but when booting up I then have the default recovery and rom supplied by Asus with no root.
I tried motochopper and debugfs method, and as described above neither work, the cmd prompt windows just record failures.
Read this forum regarding what is what (fastboot, root, unlocked etc.) and why you do them
http://forum.xda-developers.com/showthread.php?t=1833212
The way I gave root to the stock rom was by loading into fastboot mode and pushing a twrp image to my tablet off CHROMI rom site. I then used that to root the system. To be honest I did not need to root as I could have just then flashed the CHROMI custom rom which comes with SU anyway....
Get fastboot into a folder and also copy the TWRP recovery img inside the fastboot folder
Attach your device to the PC
Start fastboot mode by switching off your tablet then switching on in bootloader by holding down power on and volumn down
Connect tablet to PC (need approperiate drivers)
Open cmd prompt as admininstrator and goto directory with recovery image in the fastboot folder
Type the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot (though I don't think i typed this if honest, struggling to remember)
Unplug tablet from the PC and reboot into recovery mode
If you got the image of twrp from CHROMI site which includes bootloader also, i think it includes SU, therefore just exit and close recovery and it should ask to install SU. Select yes
Reboot the device
Your device is now rooted, though think you need to run SU in the tablet to get it fully setup.
Sorry this is not 100% perfect, I will recall what I did tonight when at home in front of PC with files.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Click to expand...
Click to collapse
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
M1ster1 said:
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
Click to expand...
Click to collapse
You can try to install from your system, not stock recovery. You need to boot your system normally and look in the lower right corner at your notification. It should notify you that their is an update for you. When you click on it, it will walk you through the update process. You need to make sure that you have only one zip file in your directory which is the Asus firmware that you want to update.
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
LetMeKnow said:
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
Click to expand...
Click to collapse
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (right click on your device, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your phone.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
Good job! Congrats!
And thank you for putting this guide together. That's what I call sharing! :victory:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
It is a nice written How to do list, good job... :good:
You can add these command for fastboot to your list instead of using the power button and volume down..
> fastboot reboot-bootloader # Exit fastboot and reboot into bootloader.
> fastboot reboot # Exit fastboot and reboot to your system
Good job.. :good:
FAILED (InvalidSize)
I am attempting to install a ROM on my Transformer Infinity as it pretty much sucks these days but am a complete NOOB. Have never attempted this with any of my phones or tablets, but figure I would try since these directions are so detailed. After following most the steps you have listed, I get the error below in the command prompt. Can someone please help, I tried searching XDA and Google to no avail. If possible please be as basic and speak in layman's terms b/c all this technical jargon goes right over my head. Thank you in advance!!!
Step followed:
- Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
epps720 said:
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
Click to expand...
Click to collapse
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
epps720 said:
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
Click to expand...
Click to collapse
Actually yes.
Just read in another thread about someone having the same problem as you, getting the incorrect file size error.
Download the TWRP 2.5 blob and try it with that file. I have no idea why, but TWRP 2.6 may cause this error.
At least that bloke got the recovery installed that way. Once you have TWRP, it's easy to upgrade to the latest version.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
I have no idea why, but TWRP 2.6 may cause this error.
Click to expand...
Click to collapse
The blob for TWRP 2.6.3 is bigger than the recovery partition. 2.6.1 should work.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Ive had the same question as the OP, i also have a .10 version, i have a US sku, and i downlaoded said associating item but when I went but when i go to either do it with sd, or intewrnal sd, or how ever. through manual or through android, either method both resulted in error when trying to downgrade, i dont know if its because its a downgrade or what.
Ive some linux experience over the years, and have rooted and run custom roms in the past. im trying to achieve the same as the OP, fix my lag, and more options and tweaks.
I have the .zip of the rom i want whitch i found I liked the xcromi rom, so I downloaded it. so, i can put that in and name it what and how do i do the update than through the volume down + pwr combo into that menu? (not sure what its called) but i can't do sideloads because i can't havbe the ultity to sideload without rooting and i can't root with .10, so i have been trying to get past this single step all night and this morning now.
@M1ster1
Thanks for posting this guide. It doesn't do a perfect job however on the TF700t running Android build 10.6.1.14.10. Tried to use the "fix permissions" option in ROM Manager but failed due to insufficient permissions. I installed CWM Superuser and cleaned up the version of SuperSU (prefer Superuser anyhow)... updated the binaries and still no love when trying to correct the permissions, despite all tests showing the device fully rooted.
After a day of pulling my hair out I finally came across vRoot and after even longer found a guide in English. Ran that, again swapped out the Superuser that went with vRoot and again reinstalled Superuser. Used Ti to install as system app. After reboot ROM Manager was finally able to correct permissions and all is golden again.
Hi ,
My Transformer has 10.6.1.14.10 and I am trying to install TWRP thru fastboot as per "M1ster" instructions.
these are the results I see from my command prompt.
C:\Users\Ken>fastboot devices
015d2bbce7041e07 fastboot
C:\Users\Ken>cd c:\Android-adb
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
OKAY [ 0.066s]
writing 'recovery'...
OKAY [ 3.374s]
finished. total time: 3.441s
c:\Android-adb>
after I reboot and select RDK , i get the sick droid error,
I feel like I have missed something, hopefully somebody can point me in the right direction
Thanks
helihaole said:
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
Click to expand...
Click to collapse
Your "twrp.blob" apparently doesn't contain a recovery - it should be around 6 to 8 MB.
Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018
"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin
volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs
Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.
unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!
Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this
@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs
not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s
What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs
Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.
@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs
I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?
ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.
@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs
I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).
I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.
unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.
Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.
Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk
It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse
domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock
In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it
Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.
Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.
EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there
Maybe a short video would be a help to some of us newbies
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps
WARNING
By doing this you may lose your data, this is intended for when you have nowhere else to turn to.
Back Story
Hi All,
Like a massive child I stupidly jumped on the Pie bandwagon away from a very well maintained Honor 10 ROM which ran beautifully on my P20 Pro..
After restoring EMUI, the PIE update quickly made itself visible, so i took a deep breath and committed.
After the installation, I tried to install a bunch of ROM's, I messed up a bit.
Anyway, what I found was, I was unable to recovery from eRecovery OR HiSuite, so I then found myself on the wobbly road that is restoring each parition via the bootloader using fastboot, tried to install just the recovery_ramdisk, didn't work, tried to install, kernel / cust / system / recovery_ramdisk..... STILL Didn't work.
So i downloaded another firmware, this time the exact version i was using albeit for the L-09 and not the L-29, I needed to extract the update part of the zip then read it using a tool called firmware extractor.
Ton of files in there, the files i just mentioned which are all .img files and some others.
In the end i needed several to get a perfect restore which has worked every single time without fail.
As it was a massive ballache and a learning curve for me as I'd never done it before, so I thought i'd share my experience and the files required on Mega so there aren't any ads blocking your way Yaay, also what to do and where to obtain the firmwares from my experiences.
Hope it helps someone avoid the pain I had to go through when downloading firmwares for 5 hours at a time, wasn't fun.
Good luck, any questions let me know. :good:
START HERE
*NOTE: You can do this from scratch by downloading the firmware for your device, i required 9.0.0.190 for the L29 - c432.
The best place I found was this site https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=105974
They require an account to be made but besides that they were faster and had more choice.
Once you have the firmware you'll need the Extractor, then you'll need to move several of the files into the ADB folder for flashing, see below...
Anyway, moving on........
FILES
At the foot of this guide is a link, inside it is everything you should require in order to complete this guide
ADB - Move this folder to the root of C, it should be like this C:\ADB (reason for this is it's much easier to navigate to, most people will already have this)
IMG Files for 9.0.0.190 - All of the file names you see below are img files which we'll be using to un-brick / recover / restore your device to a functional state.
Move all of them after downloading to the ADB folder in C:\ADB
CACHE.img
CUST.img
ERECOVERY_RAMDI.img
KERNEL.img
RECOVERY_RAMDIS.img
USERDATA.img
VENDOR.img
SYSTEM.img
EMUI Extractor - Not a part of this guide but you will need it should you need to download your own firmware and obtain the above files.
Pre-requisites
- A device on a maximum firmware of 9.0.0.190 (If you are on a higher firmware, then use the link above to obtain it)
- A device variant of either L-09 or L-29 (others may work but i have not tested)
- A device variant of c432 (the 782 may work but i have not tested)
- Access to the bootloader (white screen with vol down and power whilst connected to a laptop)
- Drivers so that fastboot / adb commands can be sent to your device (I won't show how to do this, it's pretty standard stuff)
- I have an unlocked bootloader myself and OEM unlocking is on (REQUIRED)
- A Windows based PC /Laptop and a functional USB-C cable. (I'm sure you can
GUIDE
On your computer / laptop
STEP 1 Download all the files from the mega link provided.
STEP 2 Copy the ADB Folder to the root of C: so it looks like this
C:\ADB
STEP 3 Open the folder called "IMG Files for 9.0.0.190" Copy the .IMG files to the ADB folder so they are loose.
STEP 4 Press Start / Windows key and type in cmd then press enter, a black window will appear
STEP 5 In the black window type the following:
cd c:\adb then press Enter
STEP 6 Connect your phone to your laptop using the USB-C cable and allow it to be seen by windows
On your Phone
STEP 7 Press and hold the power button and volume down, don't let go, your screen will go blank, once it turns back on, release the power key but continue holding vol down, a white screen should appear, you can now release the power volume key, you are now in fastboot mode and can input commands.
On your computer / laptop
Step 8 Click the CMD window and type in the following commands, you will have to wait for them to go all the way through, some take longer ie: System.img
*NOTE: For speed you can use the tab key to pre fill certain words or files, so if you've typed in "Fastboot flash cust "
You could then press the tab key and scroll through the files in the folder.
eg: if you were to press enter with this command listed fastboot flash cust c after pressing tab it would say fastboot flash cust CUST.img
PRESS ENTER AFTER EACH COMMAND, MAKE SURE EACH ONE COMPLETES.
fastboot flash cust CUST.img
fastboot flash cache CACHE.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash userdata USERDATA.img
fastboot flash kernel KERNEL.img
fastboot flash vendor VENDOR.img
fastboot flash system SYSTEM.img
STEP 9 Once they've all been flashed, in CMD simply type the below command and allow the device to boot up, you can disconnect now.
fastboot reboot
If all has worked and it should have, then you will have a stock ROM of PIE on 9.0.0.190
You can then root and use your device as you see fit.
Here is the link to the said files (WHICH WILL NOT BE TAKEN DOWN )
NOTE: they actually now have, sorry
https://mega.nz/#F!qdMWDKZA!5PIsAnakvENegV-4GPWKdg
Any questions, please ask away and i'll do what i can to help
c:\ADB>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (176429 KB)...
OKAY [ 4.121s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.130s
OEM is LOCKED
@mdda7
You must have an unlocked bootloader.
titi66200 said:
@mdda7
You must have an unlocked bootloader.
Click to expand...
Click to collapse
bootloader is unlocked
but
OEM is locked
mdda7 said:
bootloader is unlocked
but
OEM is locked
Click to expand...
Click to collapse
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
dladz said:
As I said in the guide you need OEM to be unlocked. I have no idea how you can unlock it without accessing the system. I think one version of pie locked it down but then the next one unlocked it.
Did you turn off OEM unlocking yourself?
What version are you on?
Maybe a paid service can help mate. Not sure.
Click to expand...
Click to collapse
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
mdda7 said:
Did you turn off OEM unlocking yourself?
- NO
What version are you on?
- 9.0.0.108
Click to expand...
Click to collapse
OEM unlocking needs to be off mate, 108 shouldn't matter but i believe that it's the version that has the OEM greyed out.
There is a way around it but i'm not sure.
any way?
mdda7 said:
any way?
Click to expand...
Click to collapse
Certainly not with this method as you don't meet the pre-requisites.
That being said I suppose some kind of low level flash tool may work, like i said before a paid for service maybe?
Lets find out everything there is to know.
So your bootloader is unlocked.
Have do you have TWRP installed?
Did any of the images i've listed actually flash successfully?
Have you tried to use eRecovery? or Hi Suite (neither of these worked for me hence this guide)
Beyond that i suppose the only way would be a paid service but their pre-requisites may be the same as mine. In that case I would say you're out of luck, afaik this guide is essentially the lowest you can go. I don't believe anything will work without OEM unlocking turned on.
How do you get onto the firmware you're currently on ? 108 and what state is the phone in right now?
What works? Whats accessible?
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
~clumsy~ said:
@dladz thanks for the guide. You got me out of a jam already and this useful information to restore to stock.
Click to expand...
Click to collapse
Haha no worries fella.
dladz said:
Haha no worries fella.
Click to expand...
Click to collapse
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
chrissyyyw said:
Used your guide @dladz, everything flashed perfectly but on the fastboot reboot command, the PC made a noise to say the USB had disconnected as expected.
All I've got is a black screen and red flashing LED.
Click to expand...
Click to collapse
Weird. Not sure pal. This is what I did when I was stuck. Did you read everything and follow to the letter? A higher or same firmware?
On fastboot reboot the pc saying it's disconnected is correct. Should have come on.
Does anything ever come on screen?
Thank you, life saver!!
:good:
Johnny Eng said:
Thank you, life saver!!
Click to expand...
Click to collapse
You're very welcome Use the thanks button buddy :good:
dladz said:
:good:
You're very welcome Use the thanks button buddy :good:
Click to expand...
Click to collapse
Done buddy ?
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Johnny Eng said:
Done buddy
Anyway when I extract update.app, I did not find userdata.img
However I go ahead and flash only. It works too.
Thanks
Click to expand...
Click to collapse
Which FW version did you flash? I’ve got the same on .282
chrissyyyw said:
Which FW version did you flash? I’ve got the same on .282
Click to expand...
Click to collapse
As i'm still on 190 I wouldn't know this, but would it be possible that userdata isn't actually a part of the update app no more?
Seeing as it still works I would assume that is the case.
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
chrissyyyw said:
There’s a user data.app packaged with update.app, just noticed it.
In update.app I’ve got file names 11.cache.img 09.cust.img
Did you have to rename yours?
Click to expand...
Click to collapse
No because you're going to be picking them via fastboot anyway, I don't believe the name matters.
The ones in the update I used were not named like that IIRC.