Related
Nvflash-ICS Restore!
This guide will not provide information to install Nvflash-ICS as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
The second method to restore has been removed until further study can be done!
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
I have finished installing Nvflash but where are my files?
/sdcard/AndroidRoot/ - this is your internal sdcard
Click to expand...
Click to collapse
What files should I have?
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
Click to expand...
Click to collapse
Nvflash recovery and going back to ICS for a fresh start.
Use blobunpack to unpack a stock ICS blob. The blob is found by unzipping the stock ICS firmware twice.
You can find the ICS firmware at this link (9.4.3.30) (post #3).
[INDEX][18 April 2013]TF300T & TG-INDEX of Roms/Dev Guides/Kernels/Recoveries/etc.
Please give philos64 a thanks while there, without him you would have a very hard time finding these downloads if at all.
these files have to be in the folder with Nvflash
wheelie -r --blob blob.bin -created with Nvflash install
nvflash --resume --download 4 blob.EBT -created with blobunpack
nvflash --resume --download 10 blob.APP – created with blobunpack
nvflash --resume --download 6 blob.LNX – created with blobunpack
nvflash --resume --download 5 recovery.img-ICS twrp recovery image name
nvflash --resume --go
then press volume down to enter twrp, flash root, flash rom or whatever you wish
Click to expand...
Click to collapse
If your problem can't corrected using this information and normal use of recovery, adb, and fastboot go to this post to access the IRC channel for all Asus transformers using nvflash.
What is blobunpack?
Here are some links to download and explain use.
https://github.com/AndroidRoot/BlobTools
windows compiled blobtools - http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
There were no dates for the following information.
The current AndroidRoot.mobi bootloader versions are
Transformer Prime: 9.4.2.28r01
Transformer TF300: 9.4.3.30r01
Transformer TF700:9.4.5.30r01
ChangeLog:-
Patch: Enable ‘fastboot boot’ command (removes ‘fastboot continue’, use ‘fastboot reboot’ instead).
Patch: Force unlocked state (protect your unlock status no matter what happens to your token).
Patch: Remove blob requirement from ‘fastboot flash’ (Flash the raw images (example: ICS_recovery.img) and not blob files).
Click to expand...
Click to collapse
When failing to get into APX mode you can try the following suggestions.
Special thanks to wha2do and daws for their input!
Also wha2do has posted a guide to enter APX that provides detail not found here! Please see his guide and give proper thanks if you find it helpful!
http://forum.xda-developers.com/show...3#post36159253
1.To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2.fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store. You must be rooted for this to work.
or
6. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.You should now be in APX mode.
Thanks for the help daws.
or
Only if there is no other resort!
7. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
Click to expand...
Click to collapse
Good Luck!
Click to expand...
Click to collapse
Due to my dock smoking my motherboard I have purchased a new motherboard and luckily it came as 4.0.3 ICS.
I now have installed and use Nvflash on my tablet.
In case anyone is interested this is the unit I purchased.
The box shows - Manufacturer's Reconditioned Parts - 90 Day Limited Warranty.
Usefull guide
Good work and helpfull guide for xda members :good:
Nice stuff
philos64 said:
Good work and helpfull guide for xda members :good:
Nice stuff
Click to expand...
Click to collapse
Thank you for your kind words.
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
chanhny said:
can I use these file
blob.bin
blob.txt – the extension on this file varies
bootloader.ebt
create.bct
recovery.bct
bricksafe.img
factory-config.img
unlock-token.img
from other tf300t to unbrick my tf300T bricked ver 4.1.2.?.
Click to expand...
Click to collapse
No.
The files contain device-specific keys and cannot be used for other devices.
See the original thread for details:
[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!
There's something I've not been quite clear about with NVFlash.
So I do my backup and keep my files.
Afterwards I upgrade to Jelly Bean (because I need the JB bootloader for ROM's right?), put TWRP recovery on, and flash a new ROM that uses the bootloader version I have.
So now I have the JB bootloader, can I still enter APX mode and do a restore, or do I have to remain on ICS bootloader to do a restore?
Is NVFlash truly unbrickable? A glance at this forum shows loads of bricks, would this have sorted their problem if they backed-up first?
Thanks!
tobdaryl said:
This guide will not provide information to install Nvflash as that is covered well elsewhere.
Once you have read the information on that page click Guide.
All necessary partitions are backed up with Nvflash and you can restore only the ones necessary to recover your unit.
I have finished installing Nvflash but where are my files?
What files should I have?
Nvflash recovery and going back to ICS for a fresh start.
What is blobunpack?
Caution
Caution
There were no dates for the following information.
When failing to get into APX mode you can try the following suggestions.
Caution
Full brick recovery
Caution
Good Luck!
Click to expand...
Click to collapse
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
graphdarnell said:
I played around with your instructions today. Ran into 2 snags:
1. Using blob UI, I typed "u" for unpack, then "blob." It returned with "cannot open 'b'";
2. Typed blobunpack.exe blob. Gave me all the files as shown in attached thumb, except LNX. Where did I go wrong?
Click to expand...
Click to collapse
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
tobdaryl said:
I'm having problems with the UI myself. It worked properly when posted. We probably have had an update that broke the UI. I'll remove the link. The tools are easy to use without the UI.
You don't have an LNX extension but you do have boot.img which is the same partition. Did you possibly rename the file and forget? Packing and repacking are still working properly for me including LNX.
I also updated the download link. The link now shown is for the version that can sign when blobpacking.
Click to expand...
Click to collapse
Not really. I didn't touch it. I'll do it again today to see. Thanks for the reply.
No recovery
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
waynestatemac said:
Hello Everybody,
I followed the instructions to restore my device however when my tf300t reboots I can't get the device into recovery mode. It will start up into android or if I hold the volume down during restart it says "platform pre os boot configuration cold booting linux". I download a ICS twrp img recovery file from here for the tf300t. "http://techerrata.com/browse/twrp2/tf300t"
My only options at this point are to enter APX mode or boot into android.
If somebody could help me install a recovery so I can use custom roms I would appreciate it!!!!!
Thanks,
Mike
Click to expand...
Click to collapse
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
tobdaryl said:
Use nvflash again to flash only twrp.
or
Other options
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
or if rooted
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I use 2.5.0.0 twrp as I have problems with 2.6.0.0.
Click to expand...
Click to collapse
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
waynestatemac said:
Thanks tobdary for replying back. I tried other versions of the recovery but none seem to work. I can't do that fastboot method because I dont get the fastboot option when the I hold the volume down and power like I did when the tablet was bone stock. I can't get su access on the tablet because its not rooted anymore once I reinstalled the nvflash rom so I cant try and flash recovery that way either. I'm really stuck and not sure why this isn't working!
Thanks,
Mike
Click to expand...
Click to collapse
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
tobdaryl said:
I'm not sure either.
Try flashing stock recovery and recheck your bootloader menu for fastboot.
Click to expand...
Click to collapse
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
waynestatemac said:
Do you know where I can find the stock recovery? Is it something ziped in the original rom file?
I was able to root the tablet using a program that that uses a exploit while android is running. I then could adb through su access and flash different twrp recovery blob files to the tablet. Though the tablet rebooted and showed a blue line with recovery being installed when I restarted I have no options to load recovery, fastboot, or linux. I'm thinking the bootloader is corrupt. I own a tf201 and might have accidentally used one of the hairybean 2.3 (4.2) bootloader updates for that device on this one. Is there a way to get my bootloader back to the original and maybe that will fix it?
Thanks,
Mike
Click to expand...
Click to collapse
The first thing you flash in this guide is the bootloader. nvflash --resume --download 4 blob.EBT
With nvflash you can flash only what is needed for your situation. If you feel the problem is the bootloader you can flash just that and try again.
What you describe sounds like stock recovery is still working on your tablet. If flashing the bootloader does not help I would use stock 9.4.3.30, unzip once and place the remaining zip on your internal sdcard. You may get an update notification. Accept it and let your tablet do the work. If you don't get the notification reboot your tablet and you should see it then. Doing this will write stock bootloader, recovery, etc.
Stock recovery is the blob.SOS when you blobunpack. Just use the stock 9.4.3.30 blob and use the resulting SOS (recovery.img).
TF300T Bricked accessible using APX Mode.
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
NaderALDirany said:
Hello @tobdaryl
I have read your thread fully, but my case differs a little bit and need your advice:
I have unlocked ASUS TF300T.
I cant access FastBoot or ADB.
I can access the APX mode.
The ASUS shows only the ASUS logo when powered on.
I don't have BackUp of anything.
I have flashed everything from my ASUS, even the recovery. (I was novice):angel:
Any suggestions or advices please?
What should i do and from where shall i get the needed files, etc...
Thank you in advance.
Nader H.AL-Dirany
Click to expand...
Click to collapse
I have read your previous posts in addition to this one.
There are four vehicles to restore your tablet. (some things can be done within android but you have no access)
1. recovery - stock or twrp
2. fastboot
3. adb
4. nvflash
I notice you also posted in my guide for accessing adb, fastboot, and apx. You were unable to access fastboot, adb, or recovery with those methods.
I don't know of any way to recover through apx without nvflash previously installed and you have no access to the other three methods.
Needs Stickied ... thanks man you helped save my butt :good:
Trigger911 said:
Needs Stickied ... thanks man you helped save my butt :good:
Click to expand...
Click to collapse
Thanks! *I'm glad you found the info useful.
This Optimized Guide is for NvFlash Flatline only! That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.5.
According to this post and this post, it works with the tf300tg as well. Bootloader: 10.6.2.11
Original Thread: http://forum.xda-developers.com/showthread.php?t=2455922
Why install NvFlash?
rayman said:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF300T Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
Click to expand...
Click to collapse
You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
Guide:
1) Download files
NvFlash for windows.
and the TF300 image, which is a custom recovery for the purpose of flashing the AndroidRoot Bootloader.
Place image in ADB folder, and rename it to: flatline_device.img
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power and vol down button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6) Reboot into recovery which should be CWM at this point. Go Advanced -> Wheelie. Accept the warning.
step 1) Flash AndroidRoot BL
The device will shut down, reboot into Android. Then reboot back into recovery.
step 2) Once back in recovery select go to Advanced ->:”Generate wheelie blobs” Be patient here too.
They can be found in the device at /data/media/AndroidRoot" or /tmp/AndroidRoot
You can use ADB to get them:
Code:
adb pull /data/media/AndroidRoot
or
Code:
adb pull /tmp/AndroidRoot
Alternatively, you can use a root file explorer such as ES File Manager. Be sure to copy all of the files out of the directory. Make sure you have root access before you try to search for the files.
Keep this file safe in multiple places.
7)The next section (Accessing NVFlash) is for creating more essential backups with NVFlash.
step 1) Hold down the volume up key while rebooting and the tablet is plugged in via USB. (This may take a few tries to get into APX mode). If you are successful, the screen will be blank and the device name on the computer will be something along the lines of "NVIDIA APX"
step 2) Take the NvFlash tools zip and extract them to a folder. Shift right click in that folder and select "Open Command window here".
step 3) Copy the blob.bin from the Step # 7 above into the NvFlash folder.
step 4) run the command:
Code:
wheelie --blob blob.bin
8) Next we run some commands to get even more backup files. These should all be run from the same command window in the previous step.
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Code:
nvflash --resume --read 14 factory-config.img
Code:
nvflash --resume --read 7 unlock-token.img
These files will be stored in C:\User\AppData\Local\VirtualStore (on the computer)
If they are not there, run a search on your computer for
Code:
*img
9.) Flash any other recovery you want, including TWRP. Be sure it is the correct version for your bootloader.
10.) Store ALL of the img files AND the blob.bin AND all other files in the folder in multiple safe places (email, dropbox, HDD, flash drive, SD card, tape backup, or your favorite plant etc.)
11.) Enjoy the peace of mind that you can now restore your device if you brick it
Hit that thanks button if I helped and also thanks to @bucket81 and of course AndroidRoot.mobi devs @rayman
Recovery
For recovery from a brick when you have already made your NvFlash backups, look here:
As @ebildude123 pointed out, first try
Code:
nvflash -r --download 5 twrp.blob
where the output should be:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
ebildude123 said:
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
If that does not work, try using the method here:
http://forum.xda-developers.com/showthread.php?t=2590450
Thanks to @lj50036 and @bucket81
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
nadorf said:
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
Click to expand...
Click to collapse
If you can flash a Tf300t version of CWM recovery to your ME301 then it could work. I dont have a 301, so i cant test it but i dont think it will because this is bootloader specific and the me301 does not have the same bootloader.
Does this work with TF300TG\L?
spider623 said:
Does this work with TF300TG\L?
Click to expand...
Click to collapse
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
cmendonc2 said:
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
adb devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
Click to expand...
Click to collapse
Think you mean fastboot devices not adb devices
cmendonc2 said:
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
Click to expand...
Click to collapse
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
spider623 said:
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
cmendonc2 said:
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
Click to expand...
Click to collapse
No need, they are the same, only difference is one file that you can put in any rom before flashing to her the radio to work, same for the TL
Sent from my Nexus 4 using Tapatalk
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
cravinRiboflavin said:
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
Click to expand...
Click to collapse
Well, when you restore, you restore back to ICS bootloader so you will have to reflash the stock JB zips first. I don't think its worth the hassle if you already have them.
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
BrakeZ said:
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
Click to expand...
Click to collapse
Since it is also the latest 4.2 bootloader, it should work fine.
cmendonc2 said:
Since it is also the latest 4.2 bootloader, it should work fine.
Click to expand...
Click to collapse
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Matatusku said:
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
Installing CM does not change your bootloader, so if you were running the latest Asus firmware before, you should be fine.
To make sure, you can check the bootloader version on the top-left of the bootloader screen.
Sent from my TF300T using Tapatalk
Matatusku said:
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
cmendonc2 said:
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
Click to expand...
Click to collapse
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
aminpro715 said:
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
Click to expand...
Click to collapse
Well I'm not experienced with tf700t bootloaders, but it says that it is compatible with bootloader version 10.6.1.14.4. That may be the same as 10.6.1.14.10 but you will have to check in the tf700 forum.
Does not work for me in step 4!
hello
I have followed your tutorial on my Asus TF300T Android 4.2.1 build 10.6.1.27.5.
I installed ADB Fastboot, placed flatline_device.img file in the ADB folder.
When I get to step 4 the fastboot devices command displays the serial number of my tablet but the command to flash the image file does nothing !...
My question is: Should the tablet be rooted for this manipulation? or it could be something else?
Thank you for your help
I'm trying to restore my Shield TV back to stock. Following Neo's thread I get to the very end where I'm stuck with the message below. Can anyone help out with this message?
C:\Users\......................\Downloads\nv-recovery-image-shield-atv-5.1.0\nv-recovery-im
age-shield-atv-5.1.0>fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
error: cannot load 'tegra210-foster-e-p2530-0930-e02-00.dtb'
This is how (Or, what), you (need to do to), recover your Shield TV using the correct Recovery Image from nVIDIA.
NOTE its CRITICAL to make sure you use the correct Image Standard, or Pro 2015, or 2017 Model. Flashing the incorrect, or an older version e.g. Experience 3.x over the current Experience 5.x.x. Will most likely (Perma) -brick you Device.
That said you need to place your Device into Fastboot Mode. Than use the following commands...
Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Of these flashing system.img will take the longest. About Five-ish Minutes or so, as the Shield will first erase the contents of the /system before rewriting it again.
P.s. As an aside to this, and as a bit of advice, if your lucky enough to have a Pro version. Have a look at the few SSHD to SSD migration Threads on this Site, and contemplate making a Backup of your Device, and then storing said backups on Google Drive, and or a USB Stick. Should you ever find yourself in a brick situation. This WILL probably save your delicious Bacon.
I used the correct image. Device rebooted. How long should the Nvidia logo stay there on the first reboot? Wondering if I need to give it time or if I did something wrong.
From the link below what's then what's the difference in this thread?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Worrying about my device being bricked I was able to get back into fastboot. I'm assuming that means I can flash and flash again?
My device has some overscan going on so I can't read the complete fastboot menu options but I'm assuming I don't need to do anything with those for this to flash?
I find it odd that your using a "dtb" File as normally there isn't one. Perhaps way, way back when. But, I know Experience 3.x (i.e. Marshmallow), Recoveries never hosted such a File. Neither would any Experience 5.x (Nougat) Recovery.
This seems to suggest (to me), that you attempted to flash an otherwise correct, but older ROM., which is a HUGE NO NO!!!
It would seem that newer ROMs manage to alter the overall partition map of the SSHD / eMMC in such a way that revering to an older version will cause the Device to brick.
Besides the order is wrong. You need to go by what nVIDIA tells you to do (flashall *.bat / *.sh), and less what some outdated Website suggests. Again see above. dtb Files just (Well as far as the Pro goes...), Just don't exist anymore. I gather they had, but ONLY in the earliest Firmware ROMs.
One other thing... In some cases depending on how it goes... It may well Stick at the nVIDIA logo for up to Two plus Hours! As the Shield is rebuilding itself. In which case the best advice would be to leave it and go out for some Coffee, and a Crawler and check it out again well after the Two Hour mark. Of course this shouldn't happen on a 16Gb eMMC version. Which should be IMO near instantaneous. Alas the SSHD isn't quite that fast.
Ichijoe said:
I find it odd that your using a "dtb" File as normally there isn't one. Perhaps way, way back when. But, I know Experience 3.x (i.e. Marshmallow), Recoveries never hosted such a File. Neither would any Experience 5.x (Nougat) Recovery.
This seems to suggest (to me), that you attempted to flash an otherwise correct, but older ROM., which is a HUGE NO NO!!!
It would seem that newer ROMs manage to alter the overall partition map of the SSHD / eMMC in such a way that revering to an older version will cause the Device to brick.
Besides the order is wrong. You need to go by what nVIDIA tells you to do (flashall *.bat / *.sh), and less what some outdated Website suggests. Again see above. dtb Files just (Well as far as the Pro goes...), Just don't exist anymore. I gather they had, but ONLY in the earliest Firmware ROMs.
One other thing... In some cases depending on how it goes... It may well Stick at the nVIDIA logo for up to Two plus Hours! As the Shield is rebuilding itself. In which case the best advice would be to leave it and go out for some Coffee, and a Crawler and check it out again well after the Two Hour mark. Of course this shouldn't happen on a 16Gb eMMC version. Which should be IMO near instantaneous. Alas the SSHD isn't quite that fast.
Click to expand...
Click to collapse
Thank you for the detailed response. I wonder if that thread on here can be decommissioned. That's where I found the info about that dbt file. I left it at startup a few hours ago so I'll see if there is any change when I return.
Assuming since it's not the mechanical HD something is probably wrong. What does Nvidia tell me? Do they have steps on their site? I didn't think to go there since this shield I acquired already had regular Android on it figuring I needed the XDA or some other community.
I still couldn't get the flash dtb file name portion to work from the steps below. These were listed on Nvidia's steps. Anyways this worked! Back to stock.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb <DTB file name> (Use result from "fastboot oem dtbname" in <DTB file name>)
fastboot reboot
@Liip008, so the only thing you did was to wait? (I can't see any different steps in your second post).
I'm trying to downgrade to Marshmallow but all I get is a black screen. Not even the logo displays. Nvidia should change really consider to change their instructions since someone may brick their device. For instance, the installation readme of 3.2 says "SHIELD UNITS WITH ANDROID MARSHMALLOW OR NEWER", thus implying downgrading shouldn't be a problem.
Hello Everybody:
finally i was able to build TWRP 3.0.2.0 recovery for Chuwi Hi8 Air (Intel X5 Cherry Trail Z8350 processor)(64-bit)
i didnt test fully but i was able to mount all partition successfully and installed Magisk 17.1 and gained root
OTG is working also and MTP
Maybe after that somebody can port some ROM with higher android version than lollipop
Thanks to @Augustoandro for the guide here:
https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
also for the Hi8 Pro TWRP from here:
https://techtablets.com/forum/topic/twrp-3-0-2-0recovery-for-chuwi-hi8-pro-64bit/
and also for stock recovery
Download Link:
https://mega.nz/#!8i4C2SgK!Qvx-fw_1JdwO4u66klgfwgOItwNZ2oJX6cdCKJSTP1o
Download and flash it with fastboot:
1- in developer settings check Allow OEM unlocking
2- turn off the tablet
3- power on and when selecting os appears select android and directly press volume down and keep holding until you see the fastboot menu
4- connect to pc
5- unlock thebootloader (WARNING USER DATA LOSE):
Code:
fastboot oem unlock
6- flash recovery using this command
Code:
fastboot flash recovery Chuwi_Hi8_Air_TWRP.img
7- when flash finish select reboot recovery from the menu on the tablet
8- done successful boot of TWRP
Can it work for hi9 plus
amitporedi007 said:
Can it work for hi9 plus
Click to expand...
Click to collapse
i dont think so
excuse me am not a professional developer i just followed the guid
try to follow it or ask in the guid post maybe he can port it for you
and also check this post:
https://forum.xda-developers.com/ge...tion/chuwi-hi9-plus-unlock-root-twrp-t3863722
I reflashed the Hi8-air using the Intel Phone flashing tool: I flashed the vendor provided Android system with a modified partition file, so that the Android occupies the whole emmc. The Android was working nicely.
I then followed your description and flashed your recovery image. Since then, I was unable to boot into the Android. I was quite scared that I bricked the device, but finally I managed to flash the Android again, losing your recovery image.
Am I doing something wrong? Do you have an idea why my device does not boot into Android after flashing your recovery image? Is there any other way to root the Hi8-Air without your recovery image? I did not find any other option. I suppose I was not quite lucky when I bought this device, as Chuwi did not sell as many of these as of the others, so there is not much support for this particular model.
bubnikv said:
I reflashed the Hi8-air using the Intel Phone flashing tool: I flashed the vendor provided Android system with a modified partition file, so that the Android occupies the whole emmc. The Android was working nicely.
I then followed your description and flashed your recovery image. Since then, I was unable to boot into the Android. I was quite scared that I bricked the device, but finally I managed to flash the Android again, losing your recovery image.
Am I doing something wrong? Do you have an idea why my device does not boot into Android after flashing your recovery image? Is there any other way to root the Hi8-Air without your recovery image? I did not find any other option. I suppose I was not quite lucky when I bought this device, as Chuwi did not sell as many of these as of the others, so there is not much support for this particular model.
Click to expand...
Click to collapse
After flashing the recovery it is necessary to flash Magisk so it batches the boot.img to be able to boot (it disable secure booting)
another way to root is to batch the boot.img using another android device (copy hi8 boot.img to the other device and batch it with magisk then flash from fastboot)
would pls link me to that android system file?
jaerose said:
would pls link me to that android system file?
Click to expand...
Click to collapse
what system file exactly ?
if you need the stock firmware files here it is
https://forum.chuwi.com/t/topic/924
but if you want the modified partition table its in this file attached (i made it myself) , you need to replace the gpt.bin file when using flash tool
sorry i dont have a detailed guide but i think you can find it on google
Use the file at your own risk , and only on Chuwi Hi8 Air, and again at your own risk
Since there's a new generation of the Onn 8 tablets, and there currently isn't a rooting guide for them,
I figured I'd write one since I finally got mine to boot with magisk.
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES. CONSIDER BACKING YOUR DEVICE UP BEFORE FOLLOWING THE INSTRUCTIONS LISTED IN THIS POST.
I won't bore you with useless details, let's just get into how to root this thing.
TOOLS:
You're going to need your vbmeta.img file to flash. You can use the one I have attached below, or supply your own from your own device dumps. Either way, you're gonna need that.
You will also need EITHER, the stock boot.img file for your tab (mine is also attached), or a magisk patched boot.img file, which I'll show you how to create if you don't already have one.
You will also need ADB and Fastboot installed on your PC for your platform, as well.
A guide on how to obtain that is available here if you don't already have it.
CREATING PATCHED MAGISK BOOT.IMG:
On your device, install the magisk manager apk.
inside the app, click on Install magisk, and supply the app with your boot.img file.
It should then open a terminal and patch the boot file, and output it to your download folder.
Now you've got a rooted boot.img file for your device. Alternatively, you can use the one I've supplied at the bottom of this post.
FLASHING ROOT ON YOUR DEVICE:
Here's the part where things get interesting.
Copy the patched boot.img to your pc from your tablet, and save it somewhere you'll remember. (preferably the same place you saved your vbmeta.img file.)
You'll need to shut down your device, then power it into fastboot mode by holding Vol+ and Power at the same time. This should bring up a menu with three options: Recovery, Fastboot, And Normal.
You'll want to use Vol+ to scroll to fastboot, then press Vol- to select and boot into fastboot.
Connect your device to your pc and open your ADB and fastboot program.
In the command prompt, type "fastboot devices".
This should spit out the serial number of your device followed by the word "fastboot".
If there is no device present, make sure you have android USB drivers installed properly.
Given that your device is connected properly, type the following commands. (without the quotes.)
"fastboot flash --disable-verity --disable-verification --skip-reboot boot /path/to/your/magisk_boot.img"
then
"fastboot flash --disable-verity --disable-verification vbmeta /path/to/your/vbmeta.img"
If all goes well and you get no errors, you should be safe to reboot, and you should have root now!
Once booted, open Magisk, and you should see that V22 is installed and running. You can now install edxposed via the magisk module manager if you'd like xposed installed, since TWRP currently isnt available for this model and lots of android 10 devices don't support it.
NOTE: SAFETYNET CHECK DOES NOT PASS, WE'LL NEED TO LOOK INTO THAT.
Here's a couple pics just showing I actually DID do this, and I'm not just ****posting or something
LaikaXv1 said:
Since there's a new generation of the Onn 8 tablets, and there currently isn't a rooting guide for them,
I figured I'd write one since I finally got mine to boot with magisk.
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES. CONSIDER BACKING YOUR DEVICE UP BEFORE FOLLOWING THE INSTRUCTIONS LISTED IN THIS POST.
I won't bore you with useless details, let's just get into how to root this thing.
TOOLS:
You're going to need your vbmeta.img file to flash. You can use the one I have attached below, or supply your own from your own device dumps. Either way, you're gonna need that.
You will also need EITHER, the stock boot.img file for your tab (mine is also attached), or a magisk patched boot.img file, which I'll show you how to create if you don't already have one.
You will also need ADB and Fastboot installed on your PC for your platform, as well.
A guide on how to obtain that is available here if you don't already have it.
CREATING PATCHED MAGISK BOOT.IMG:
On your device, install the magisk manager apk.
inside the app, click on Install magisk, and supply the app with your boot.img file.
It should then open a terminal and patch the boot file, and output it to your download folder.
Now you've got a rooted boot.img file for your device. Alternatively, you can use the one I've supplied at the bottom of this post.
FLASHING ROOT ON YOUR DEVICE:
Here's the part where things get interesting.
Copy the patched boot.img to your pc from your tablet, and save it somewhere you'll remember. (preferably the same place you saved your vbmeta.img file.)
You'll need to shut down your device, then power it into fastboot mode by holding Vol+ and Power at the same time. This should bring up a menu with three options: Recovery, Fastboot, And Normal.
You'll want to use Vol+ to scroll to fastboot, then press Vol- to select and boot into fastboot.
Connect your device to your pc and open your ADB and fastboot program.
In the command prompt, type "fastboot devices".
This should spit out the serial number of your device followed by the word "fastboot".
If there is no device present, make sure you have android USB drivers installed properly.
Given that your device is connected properly, type the following commands. (without the quotes.)
"fastboot flash --disable-verity --disable-verification --skip-reboot boot /path/to/your/magisk_boot.img"
then
"fastboot flash --disable-verity --disable-verification vbmeta /path/to/your/vbmeta.img"
If all goes well and you get no errors, you should be safe to reboot, and you should have root now!
Once booted, open Magisk, and you should see that V22 is installed and running. You can now install edxposed via the magisk module manager if you'd like xposed installed, since TWRP currently isnt available for this model and lots of android 10 devices don't support it.
NOTE: SAFETYNET CHECK DOES NOT PASS, WE'LL NEED TO LOOK INTO THAT.
Click to expand...
Click to collapse
NOTE: SAFETYNET CHECK DOES NOT PASS, WE'LL NEED TO LOOK INTO THAT.
I'm glad to see that there is finally a root solution for this device. I have 2 Onn 8 first gen, Android 9 tablets and I use the Magisk module: Universal SafetyNet Fix to
pass.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Let us all know if this works. I work in a Walmart electronics department and have not bought one of the 2nd gen devices because I had assumed that it could not be rooted. I am temped just for a new challenge, even though I really don't need a new device.
Have you been able to create a backup of the stock rom? Is it flashed with spflashtool like the older device?
Thanks
I'll get the ROM backup uploaded to Google drive once I'm done updating windows.. it's taking forever, but I do have the dumps. Yes, spflashtool is what you'll need to flash the stock backup.
As for the magisk module, that seems to do the trick! Magist safetynet check reports a success for both basicIntegrity and ctsProfile.
Thanks for the tip!
LaikaXv1 said:
I'll get the ROM backup uploaded to Google drive once I'm done updating windows.. it's taking forever, but I do have the dumps. Yes, spflashtool is what you'll need to flash the stock backup.
As for the magisk module, that seems to do the trick! Magist safetynet check reports a success for both basicIntegrity and ctsProfile.
Thanks for the tip!
Click to expand...
Click to collapse
Ah, I didn't hit reply. Oops!
I'm not new to XDA persay, but I'm not usually the one making guides and actually saying things haha.
Doesn't seem to work for me
Keeps failing says
(remote: not allowed in locked state)
Boox17 said:
Doesn't seem to work for me
Keeps failing says
(remote: not allowed in locked state)
Click to expand...
Click to collapse
It sounds like maybe you did not unlock the bootloader first?
martyfender said:
It sounds like maybe you did not unlock the bootloader first?
Click to expand...
Click to collapse
Yeah exactly what it was
I have a 100011886 that I got used and has FRP lock, will this process work on it as well? Only rooted Fire tablets before, so this would be new to me and if I brick it not much will be lost. But any insight as to what I will need that isn't included in your post would be great! It seems pretty thorough though.
Edit: I've tried it, and I have done pretty much everything thanks to being able to get to the browser with one of those language keyboard tricks, but I can't enable dev mode and turn on OEM unlock so I can't unlock the bootloader. Really want to know what to do so I don't have a paper weight At least it was only $30
I'm stuck in a boot loop. Does this work with a 100011885 that has Android 11 or did I just brick it cause I didn't pay attention.
I think I have extracted the boot.img using spflashtool on the 100011885 with Android 11. abootimg seems to like it and I can extract the kernel and initrd.img I have tried booting with fastboot boot but it blackscreens the tablet. I have not tried re-flashing this image as I don't know if it will actually work.
start location and size
0x00000000085c0000
0x0000000002000000
boot.img
and another boot image found at
A5C0000
boot2.img
bowb said:
I think I have extracted the boot.img using spflashtool on the 100011885 with Android 11. abootimg seems to like it and I can extract the kernel and initrd.img I have tried booting with fastboot boot but it blackscreens the tablet. I have not tried re-flashing this image as I don't know if it will actually work.
start location and size
0x00000000085c0000
0x0000000002000000
boot.img
and another boot image found at
A5C0000
boot2.img
Click to expand...
Click to collapse
Did you get this working?
Valiante said:
Did you get this working?
Click to expand...
Click to collapse
No.
LaikaXv1 said:
I'll get the ROM backup uploaded to Google drive once I'm done updating windows.. it's taking forever, but I do have the dumps. Yes, spflashtool is what you'll need to flash the stock backup.
As for the magisk module, that seems to do the trick! Magist safetynet check reports a success for both basicIntegrity and ctsProfile.
Thanks for the tip!
Click to expand...
Click to collapse
did you happen to upload this image yet? if so, got a link?
I followed this guide for a ONN 100003561 (didn't look closely at the numbers) and this is what I get when trying to flash the vbmeta:
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (11520 KB) OKAY [ 0.287s]
Writing 'vbmeta' FAILED (remote: 'size too large')
I tried using a different vbmeta and when I restarted my tablet and got blank black screen. Tried twrp and now I can't get anything to work. Never tried rooting an Android device before, just trying to get all the annoying stuff off and now it looks like I bricked it.
Any advice from anyone?
pj_dev said:
I followed this guide for a ONN 100003561 (didn't look closely at the numbers) and this is what I get when trying to flash the vbmeta:
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (11520 KB) OKAY [ 0.287s]
Writing 'vbmeta' FAILED (remote: 'size too large')
I tried using a different vbmeta and when I restarted my tablet and got blank black screen. Tried twrp and now I can't get anything to work. Never tried rooting an Android device before, just trying to get all the annoying stuff off and now it looks like I bricked it.
Any advice from anyone?
Click to expand...
Click to collapse
Unfortunately, the numbers are important. Are you able to get to fastbootd? If you can get to fastbootd, I would recommend trying to change to boot slot. Newer androids actually have two boot partitions for updating purposes. You can check which boot partition you're using with `fastboot getvar current-slot` which should return "a" or "b". Then do `fastboot set-active x` and replace x with whichever slot is NOT active as determined by the previous command. If the other boot slot is still intact, this would hopefully result in a bootable device. I haven't tried this myself, but this is what I would try if I were in your situation.
If this doesn't work, I would try flashing stock with sp flash tool, which doesn't need fastboot if you can't access that. It's a leaked mediatek tool, so there isn't an official site to get it from unfortunately. I got it from here: https://androidmtk.com/smart-phone-flash-tool but use your discretion. And get v5, because that's what most of the guides use. Then you can try flashing the 3561 stock firmware here: https://forum.xda-developers.com/t/stock-stock-backups-images-otas.3998227/post-82619259
If you can get it to boot at this point and want to de-walmart it, I would recommend just flashing a GSI rather than messing around with the stock rom. You can find the GSI's here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
LaikaXv1 said:
Here's a couple pics just showing I actually DID do this, and I'm not just ****posting or something
Click to expand...
Click to collapse
Lol, remember those copy-pasted guides where they provide the wrong TWRP images and it messes up the device
So the 8" Onn actually has a boot-ramdisk it appears. On the 7" Onn Surf (100005206), there is no boot-ramdisk, so the alternative is patching a recovery.img and allowing Magisk to hijack the /recovery partition. The only drawback is, anytime you need to reboot, using hardware keys as though booting into recovery is necessary.
inzane105 said:
I have a 100011886 that I got used and has FRP lock, will this process work on it as well? Only rooted Fire tablets before, so this would be new to me and if I brick it not much will be lost. But any insight as to what I will need that isn't included in your post would be great! It seems pretty thorough though.
Edit: I've tried it, and I have done pretty much everything thanks to being able to get to the browser with one of those language keyboard tricks, but I can't enable dev mode and turn on OEM unlock so I can't unlock the bootloader. Really want to know what to do so I don't have a paper weight At least it was only $30
Click to expand...
Click to collapse
I'm in a similar situation, my friend got an RCA Atlas 10 Pro-S from Goodwill for $1. It had an FRP lock on it though, and we ultimately managed to get to the home screen by enabling TalkBack and watching the support video to open the browser. Then, we installed Lawnchair to access the home screen. The settings app worked, but Developer Options would not open.
GetDroidTips has published a software called Miracle Box, claiming that it can unlock MediaTek bootloaders, as well as bypass FRP. However, a VirusTotal scan indicates that it is likely malware. I tried running it in a virtual machine and it asked if I wanted to run a process impersonating "svchost.exe" as Administrator. I airgapped the virtual machine, and Miracle Box said it needed Internet access for licensing, however GetDroidTips said it was free. I suspect that this was a fake software crack.
I am aware of a program called SP Flash Tool, but that won't work because I am on Linux, and not Windows. I doubt it would work under WINE, as it requires special device-specific drivers that also only work on Windows. I have a spare Lenovo IdeaPad 110-15ACL, however I don't have the drivers needed to set up Windows 7 on it. I could, of course, use Windows 10, but I have heard it is bad for flashing, and it is very slow anyway. (I did, however, buy an SSD for it, perhaps this will speed it up enough to be somewhat usable?)
I also found an open-source MediaTek exploit script called MTKTools. It did not work, and it told me to hold all hardware buttons before plugging the device in. It still did not detect the tablet. It told me that I could also short TP1 to ground, however I could not find Test Point 1 on the tablet's motherboard.
There are no custom recoveries or FRP unlocking guides for this device, likely because it's an obscure Android 7.1 tablet from back in 2014. I wouldnt be able to flash them anyway as the bootloader is locked. It has 2 GB of RAM and the processor cores are Cortex-A35s so I'm not sure that this is worth unlocking. On the other hand, it costs over $100 from Walmart.
I am worried that the device was stolen, as it had a password, and once I reset it from Recovery mode, it had an FRP lock. If it is indeed stolen, I can't return it, due to the "as is" nature of Goodwill, and besides, I have disassembled it several times as well. Should I be concerned about the ethical implications of unlocking this device?
Does this work on Android 11? I have the Onn. 100011885 model, according to my settings app.