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.
Hello,
I have a TCL 20y (model 6156D) phone and i'm trying to gain root access in any way.
I've tried to enable oem unlocking and go to fatboot mode, but the command
fastboot oem unlock returns "FAILED (remote: 'Command not supported in default implementation')".
On producer website i can't find this model and in the "repair software" this model (6156D) is missing.
I don't have any recovery file (stock or trwp), and i don't know how to dump original recovery to file (for install magisk, but anyway i think i can't flash modified versions without unlock bootloader).
Is there anything i can try?
---
Edit: I finally found the original flash tool at the following url:
Modello
www.tcl.com
https://www.tcl.com/content/dam/tcl-html/TCTService/support/tcl-20-r-5g/Mobile_Upgrade_S_Gotu2_v1.1.5_Setup.exe
It seems to support model 6156 and, with connected phone, it has downloaded a lot of files and created a folder "6156D-2ALCWE12\ANAJEAJ0" (model\version) with a lot of files with MBN extension and a zip with system.img inside.
Maybe these files may be useful to root the phone. Anybody knows how to open MBN files?
--
Edit: I've notice a strange thing. When I boot to recovery, i see two interesting options:
- Enter fastboot: this stats "fastbootd", a graphical menu with a few reboot options. In this phase the computer recognizes the phone with fastboot driver and list it with "fastboot devices" command.
- Reboot to bootloader: this clear the screen, writes "FASTBOOT>" in the low position of the screen. In this phase the computer recognizes the phone with adb driver and don't list it in fastboot devices nor adb devices.
I've also tried to flash magisk apk (renamed as zip) with adb sideload, but as expected i got Error 21.
Is there a way to sign any root manager or su binary and install it using this method?
What am i doing wrong?
Hi!
I've managed to unlock the bootloader on a TCL 20Y by following this guide: https://romprovider.com/tcl-20y-unlock-bootloader/.
I used the mtk_gui utility, which is really straightforward. The only tricky thing was going into brom/preloader mode - sometimes it works, other times it doesn't.. The trick is to hold both volume buttons while plugging in the USB cable to the computer.
Then, I've also managed to root the device with Magisk by patching both the boot_a.img and boot_b.img images and flashing them using fastboot by following the official guide: https://topjohnwu.github.io/Magisk/install.html.
Haven't yet played with the orange state disabler as I've read that it can result in a brick.
BR
Hey there!
With bevvare's help I was also able to root my TCL 20Y without much issue, though I encountered a few minor differences and details so we agreed it would be good if I wrote them down here.
Regarding the first guide used to unlock the bootloader:
The mtk_gui utility packed in the, as of today, latest release of mtkclient (1.52) refused to launch. That wasn't too bad seeing as the guide provides the necessary commands, but it's something to keep in mind.
In addition, I found that the phone would stop accepting commands after the first one was issued or after the log got too long*. This might have only been an issue on my end, but just in case, this is how i ran each command:
-Turn the phone off
-Hold the power button along with both vol+ and vol- (you may plug in the phone at this stage)-While in the Recovery Mode screen, issue the command on your terminal-Select the option to restart the device in the recovery screen, then hold both vol+ and vol- until the terminal starts printing output (the phone's screen will stay off while this happens)-After the command has executed, unplug the phone (probably optional) and hold all three buttons again to restart and boot into recoveryRepeat as needed
* Remember how I mentioned the command seemed to fail if the log got too long? Well, this is what happened to me with the very first command on the guide (the one that erases three partitions at once). Just to be sure, I erased them separately using the same command.PS: booting into recovery first may not even be needed, I just found it easier that way.
The guide provides two unlock commands, the first one being python mtk xflash seccfg unlock, this ran without issue and triggered the orange state warning on boot. The second command (fastboot flashing unlock) refused to work, but the bootloader was nonetheless unlocked.
Also, the guide provides the relock command right after the unlock one as if it were the next step to take. This might be obvious, but don't relock your bootloader until after you're done flashing the new boot image (even then there's no real reason to relock it).
Regarding Magisk's guide on patching boot.img:
Magisk failed to patch boot_b.img. This turned out to not be a problem because my device was using the boot_a partition as the active one (I used this guide to check https://krispitech.com/check-partition-slot-a-b/ )
In order to get the necessary files, namely boot_a.img and vbmeta_a.img, I used this guide to dump all the partitions within the phone into my PC: https://forum.xda-developers.com/t/...sing-mtk-client-oppo-reno6-5g-mt6877.4406069/
You may also decide to dump only the two partitions you need, in which case you could issue the following command instead: python mtk rl boot_a,vbmeta_a boot_a.img,vbmeta_a.img (this assumes your phone is also using partition A, adjust as needed).
If you used the above guide to dump all the partitions, the files you need will have the .bin extension, just rename them so they are .img files instead.
I recommend flashing vbmeta_a.img (it's optional and doesn't need to be patched in the Magisk app like boot_a.img). Otherwise your device will print a spooky warning at boot about being corrupt and demand you press the power button, which is annoying.