Related
I already had a try on this on another forum:
hxxp://www(dot)transformerforums.com/forum/asus-transformer-help/25176-settings-stopped-working-tf101.html
(can't post links yet)
I have a TF101G ( sn:C20KAS035896) from a friend, everytime he went in to the settings it says: "settings stopped working"
I tried a factory reset, (from stock recovery menu), got it to reset, but now i cant get through the "first-time-setup-wizard":
at step 3 it asks to connect to a WiFi network, I select one, it asks for a password, but when I enter it and press ok it says "Unfortunately settings stopped working". After a few seconds it starts again at step one of the wizard..
I figured out it is a WW version.
So, what do I best try next?
After reading some here, i guess I get a alternative recovery and use that to flash a new stock rom onto the tablet.
But could you point me to the right posts and methods, because I'm not sure which is the right one.
http://forum.xda-developers.com/showthread.php?t=1552303
Then this you were looking for ? It is with recovery 3.2.0.1 us or ww stock rooted full rom edition
good luck
It might be. It seems to be a link to a zip file. The contents looks like the contents of a standard firmware file. Only the blob part is much smaller, and there is a system folder which isnt in the standard firmware update.
But I don't know what to do with it..
I was thinking maybe wolfs method 3 could help me out?
hxxp://forum(dot)xda-developers.com/showthread.php?t=1622628
(can't post links yet)
But i'm still strugling with adb though..
When i run "adb devices" I think it should list my TF101 but it doesn't
After some more reading and trying, I've come to the conclusion I can't get adb to connect to the device.
I also have an android phone: a HTC desire, which I can get to connect with adb. But the asus is stuck at the "first-time-setup-wizard" (as I explained above)..
Though I can see the device in windows explorer (win 7 64bit), and the 2 mounted drives "Internal storage" and "SD Card"
I can get it into apx mode, but nvflash doesn't work for my version of the device its a TF101G sn:C20KAS035896
What could i try next?
I want to flash the stock rom, as mine seems to be broken, and I cant use adb
EDIT:
Just found out about wheelie, should that tool be able to do what I want?
androidroot(dot)mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
My device isnt explicitly listed, and EasyFlasher a tool based on wheelie says it doesnt work for my device.. So should it work or not?
Do I need linux for this? I cygwin ok?
EDIT2:
As I understand it, I probably have a Secure Boot Key that isn't version 1 or 2?
There is a sbk detection tool, but afaik it only works on mac, and I don't have a mac available..
I have tried the windows beta version of wheelie, and the output i get is the following:
reflash_sbkv2.bat
Code:
J:\TF101\wheelie>reflash_sbkv2.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --o
dm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
And for the sbkv1 version the same:
Code:
J:\TF101\wheelie>reflash_sbkv1.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --o
dm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
Am I overlooking something here?
Should I get adb working with my tablet in its current state?
Or do I have to return the tablet to ASUS?
Same problem here
Hello frydac, I'm having the same problem as you.
Did you find a way to fix it yet?
Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
I am getting the same error on mine too.
Same error for me
It took a lot of effort to find a copy of nvflash for ics, but now I find that it does not work and returns the above error.
Russ
tinnymarlin said:
Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
I got the same thing. maybe the nvflash problem. It just display "bad command".
I sold my Asus Transformer Infinity TF700 to someone a while ago. I had unlocked and saved my nvflash files. Two months passed and the buyer told me his wife somehow wiped the tablet. I thought it would be easy recovering the device so I told him to send it to me.
I followed this post http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189 and on the first step when I send the command to the terminal "wheelie --blob blob.bin" it gets stuck on "Sending bootloader".
Waiting for device in APX mode...
[=] Chip UID: 0x98282857691354638
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Click to expand...
Click to collapse
Any help would be appreciated.
coolerthannos said:
I sold my Asus Transformer Infinity TF700 to someone a while ago. I had unlocked and saved my nvflash files. Two months passed and the buyer told me his wife somehow wiped the tablet. I thought it would be easy recovering the device so I told him to send it to me.
I followed this post http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189 and on the first step when I send the command to the terminal "wheelie --blob blob.bin" it gets stuck on "Sending bootloader".
Any help would be appreciated.
Click to expand...
Click to collapse
Check that if your operating system correctly loading the APX drivers and the tablet is recognized by the system as an APX device. Myabe try a different usb port. I've got problems similar to this when my windows somehow not loaded correctly the APX driver.
Need to completely remove the drivers and reinstall!
bosstom said:
Check that if your operating system correctly loading the APX drivers and the tablet is recognized by the system as an APX device. Myabe try a different usb port. I've got problems similar to this when my windows somehow not loaded correctly the APX driver.
Need to completely remove the drivers and reinstall!
Click to expand...
Click to collapse
Did all that, reinstalled the drivers, changed the usb ports and it got recognized every time as a APX device no issues there and also tried it in linux mint, no go there either .
I would like to add that in windows I am getting a different Chip UID. Has the blob file gotten corrupted somehow? I got the rest of the files using this blob file last time and it worked fine. How much time should sending bootloader take?
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbd0434160e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Click to expand...
Click to collapse
coolerthannos said:
I would like to add that in windows I am getting a different Chip UID. Has the blob file gotten corrupted somehow? I got the rest of the files using this blob file last time and it worked fine. How much time should sending bootloader take?
Click to expand...
Click to collapse
The sending should take a couple of seconds!
bosstom said:
The sending should take a couple of seconds!
Click to expand...
Click to collapse
It takes forever .
OMG, I am stuck in the very same situation! (But I am on a TF300TG.)
I was playing around with some recoveries and ICS stock ROMs and put all my faith into nvflash. Latter one I already used once or twice to make sure it was working.
After updating to the newest ICS available for my TF300TG, I installed twrp (the one for ICS), booted up the Stock ROM (which worked), booted in TWRP recovery, wiped all data. Rebooted into APX, and now I am stuck there since then.
Code:
g:\somePath\>wheelie.exe --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (it shows the right ID, just cropped it for my privacy...)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Any ideas?
forcemaker said:
OMG, I am stuck in the very same situation! (But I am on a TF300TG.)
I was playing around with some recoveries and ICS stock ROMs and put all my faith into nvflash. Latter one I already used once or twice to make sure it was working.
After updating to the newest ICS available for my TF300TG, I installed twrp (the one for ICS), booted up the Stock ROM (which worked), booted in TWRP recovery, wiped all data. Rebooted into APX, and now I am stuck there since then.
Code:
g:\somePath\>wheelie.exe --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (it shows the right ID, just cropped it for my privacy...)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Any ideas?
Click to expand...
Click to collapse
At least yours say sending file: 100% mine doesn't even come up .
OMG (again)!
I found in the Transformer Prime forum (here: http://forum.xda-developers.com/showpost.php?p=33234684&postcount=51) the solution to my problem.
It is:
Code:
wheelie -r --blob blob.bin
After that my screen is back on and wheelie completed its process.
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (still my private ID)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
forcemaker said:
OMG (again)!
I found in the Transformer Prime forum (here: http://forum.xda-developers.com/showpost.php?p=33234684&postcount=51) the solution to my problem.
It is:
Code:
wheelie -r --blob blob.bin
After that my screen is back on and wheelie completed its process.
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (still my private ID)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
Thanks man it worked but now it gets stuck on the second sending file and on the tablet it shows "Entering NvFlash recovery mode / Nv3p Server"
Waiting for device in APX mode...
[=] Chip UID: 0x98282857691354638
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
Click to expand...
Click to collapse
Any more help would be apperciated.
Anyone?
coolerthannos said:
Thanks man it worked but now it gets stuck on the second sending file and on the tablet it shows "Entering NvFlash recovery mode / Nv3p Server"
Any more help would be apperciated.
Click to expand...
Click to collapse
Hi!
You really should tell us the command that you are using after "wheelie -r --blob blob.bin"!
As far as I can tell from the output you posted that you are trying to use "wheelie" a second time, which isn't right.
I do use(1) these commands to do a "nvflash" based restore to the "Android 4.0 Bootloader":
Code:
[B]wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
[/B]nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
... where I usually do not need to use the last 2 commands. The first 2 are doing fine most of the time!
The file names I used (e.g. "bricksafe.img") are valid for me, it depends on how you have named the files during backup.
(1) "I do use" means that this works for me. I expect it to work for you, too, but I take no responsibility for the usual bad boys (bricks, nuclear war, ...)
forcemaker said:
Hi!
You really should tell us the command that you are using after "wheelie -r --blob blob.bin"!
As far as I can tell from the output you posted that you are trying to use "wheelie" a second time, which isn't right.
I do use(1) these commands to do a "nvflash" based restore to the "Android 4.0 Bootloader":
Code:
[B]wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
[/B]nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
... where I usually do not need to use the last 2 commands. The first 2 are doing fine most of the time!
The file names I used (e.g. "bricksafe.img") are valid for me, it depends on how you have named the files during backup.
(1) "I do use" means that this works for me. I expect it to work for you, too, but I take no responsibility for the usual bad boys (bricks, nuclear war, ...)
Click to expand...
Click to collapse
Sorry I meant it gets stuck on the first command which is wheelie -r blob blob.bin. It sends the BCT but when it starts sending the bootloader it shows 100% but it doesn't say "[!] Done - your device should now be ready for nvflash" like your wheelie command does.
And on my device this is displayed, "Entering NvFlash recovery mode / Nv3p Server" with the Asus logo in the middle and the powered by nvidia tegra at the right. But nothing happens and the device doesn't enter NvFlash recovery mode.
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbd0434160e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
Click to expand...
Click to collapse
coolerthannos said:
Sorry I meant it gets stuck on the first command which is wheelie -r blob blob.bin. [...]
Click to expand...
Click to collapse
Please, if you quote the command that you have used (specially after being asked for it!) it would really be good to quote the whole thing exactly the way you entered it in the console. Because now I have to guess if you entered "wheelie -r blob blob.bin" which is the wrong syntax (AFAIK), or if you were only too lazy to write/quote it completely.
I guess it is the latter one.
coolerthannos said:
It sends the BCT but when it starts sending the bootloader it shows 100% but it doesn't say "[!] Done - your device should now be ready for nvflash" like your wheelie command does.
And on my device this is displayed, "Entering NvFlash recovery mode / Nv3p Server" with the Asus logo in the middle and the powered by nvidia tegra at the right. But nothing happens and the device doesn't enter NvFlash recovery mode.
Click to expand...
Click to collapse
Did you try this:
Code:
[COLOR=Red]wheelie -r --blob blob.bin[/COLOR]
# wait until it reached 100% and a few seconds more
# then press Ctrl+C to terminate wheelie
[COLOR=Red]wheelie --blob blob.bin[/COLOR]
# execute it a second time, without "-r"
If this doesn't work: your device says that it was "Entering NvFlash recovery mode / Nv3p Server" which I expect to be already where you want it to be.
Try either:
terminate wheelie by Ctrl+C, then (try to) continue with the neccessary nvflash commands
OR
keep wheelie running, open a new console window/command prompt/cmd.exe and execute the nvflash commands in the new window.
On the one hand I expect both ideas to be "safe" as I read often enough that nvflash cannot be "disabled" or "altered" or "removed" at all
on the other hand I did not try this scenario and cannot garantuee anything. Your risk, but if it was my device, I would most likely try it.
Honestly, I am out of ideas. ATM I can only think of trying or reinstalling different APX drivers? Earlier you wrote:
Did all that, reinstalled the drivers, changed the usb ports and it got recognized every time as a APX device no issues there and also tried it in linux mint, no go there either
Click to expand...
Click to collapse
But back then you didn't use "wheelie" with the "-r" option.
forcemaker said:
Please, if you quote the command that you have used (specially after being asked for it!) it would really be good to quote the whole thing exactly the way you entered it in the console. Because now I have to guess if you entered "wheelie -r blob blob.bin" which is the wrong syntax (AFAIK), or if you were only too lazy to write/quote it completely.
I guess it is the latter one.
Click to expand...
Click to collapse
Yeah sorry was a little bit distracted so i quoted the command wrong here but I was putting it right in the command terminal.
forcemaker said:
Did you try this:
Code:
[COLOR=Red]wheelie -r --blob blob.bin[/COLOR]
# wait until it reached 100% and a few seconds more
# then press Ctrl+C to terminate wheelie
[COLOR=Red]wheelie --blob blob.bin[/COLOR]
# execute it a second time, without "-r"
If this doesn't work: your device says that it was "Entering NvFlash recovery mode / Nv3p Server" which I expect to be already where you want it to be.
Click to expand...
Click to collapse
It says "Waiting for device in APX mode". Nothing happens .
forcemaker said:
Try either:
terminate wheelie by Ctrl+C, then (try to) continue with the neccessary nvflash commands
OR
keep wheelie running, open a new console window/command prompt/cmd.exe and execute the nvflash commands in the new window.
On the one hand I expect both ideas to be "safe" as I read often enough that nvflash cannot be "disabled" or "altered" or "removed" at all
on the other hand I did not try this scenario and cannot garantuee anything. Your risk, but if it was my device, I would most likely try it.
Click to expand...
Click to collapse
Also tried everything you wrote but it still isn't responding. Whenever I try and keep the wheelie window open and try nvflash commands it gives communication error but when I close the wheelie window and try the command again nothing happens. It just shows "Nvflash v1.5.66719 started [resume mode]"
./nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
Nvflash v1.5.66719 started
[resume mode]
Click to expand...
Click to collapse
forcemaker said:
Honestly, I am out of ideas. ATM I can only think of trying or reinstalling different APX drivers? Earlier you wrote:
But back then you didn't use "wheelie" with the "-r" option.
Click to expand...
Click to collapse
I don't think these are drivers issues as I am trying it in linux now. Same issue on my brother's pc. I guess I'll have to try something else. This tablet doesn't want to get restored. I think it wants to remain bricked :laugh:.
If someone has the same issue and has somehow recovered his tablet please let me know.
First off I want to thank @lj50036 for his time and most of all his patients in helping me bring my TF300T back to life I can't thank him enough!! His original post on the TF700T is here. Make sure you go thank him!!
You must have the NVFlash generated files from AndroidRoot.Mobi for ICS or JB.
This is what I did and it might not work for your specific situation. I performed this on a Mint 15 32 bit machine. This is very important (EDIT: This has also been done on Mint 64bit); Ubuntu might not work and would not work for me .
My situation:
I had flashed the wrong recovery (TWRP 2.6.3.0). This left me with only being able to boot into a recovery that would not mount anything but it would boot into APX mode.
What you will end up needing:
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
Also needed:
Fully charged TF300T (Just plug it in, it will charge no matter what...If not, you don’t need my help!!!!)
Asus data cable
Linux Mint 15 (32 bit) PC
Stock firmware blob (from asus's website. Make sure you get the right one) Download
nvflash and wheelie Download
And fastboot for your PC
You might also need TWRP 2.5.0.0 Download
Mint
1) Lets start with Mint 15 (32 bit) Download and how to make a bootable USB. instructions this has got to be one of the easiest OS’s I have installed and setting up dual boot is cake.
2) Once Mint is booted you want to update it, and it’s a little broken but it’s what I did and you will get some updates. Click where the start menu is in windows find the search field and lookup update manager. Run it and download what you can.
3) Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob (this is not a .blob file make sure you put that in the name) file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder..
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
nvflash
wheelie
boot.blob (we renamed it in the last step)
4) Next we need to install fastboot, this is straight up Linux voodoo, open terminal and get comfy cause that’s what you’re going to be using. next type
Code:
fastboot
it will prompt you with the command to install fastboot.
These inputs and outputs are from lj50036 post on the TF700T and may very from your outputs. I used the processes and it worked for me.
Lets get started
Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
I am going to show you the output of my process
Code:
sudo ./wheelie --blob blob.bin
[email protected]:~ > sudo ./wheelie --blob blob.bin
OUTPUT
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbce2501405
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
It may shutdown after each command, get back into nvflash with the above steps.....
Code:
sudo ./nvflash -r --download 7 unlock-token.img
[email protected]:~ > sudo ./nvflash -r --download 7 unlock-token.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
/ 8388608/8388608 bytes sent
unlock-token.img sent successfully
Code:
sudo ./nvflash -r --download 14 factory-config.img
[email protected]:~ > sudo ./nvflash -r --download 14 factory-config.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
/ 5242880/5242880 bytes sent
factory-config.img sent successfully
Code:
sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
[email protected]:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully
Code:
sudo ./nvflash -r --go
[email protected]:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
This is where I ran into problems that didn’t work with the TF700T recovery process. I could not boot into Fastboot with the holding the power and the volume down no matter what I did. this is how we got around it.
download the correct .blob from TWRP rename it twrp.blob then run
Code:
sudo ./nvflash -r --download 5 twrp.blob
I don't have output for this.
At this point I could boot into the OS, but still not into fastboot. My OS had the option to reboot to download. If you don’t have this option you could try this or this. But the best way is via the buttons.
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
sudo fastboot devices
INPUT
[email protected]:~ > sudo fastboot devices
OUTPUT
015d2bbce2501405 fastboot
Code:
sudo fastboot erase system
INPUT
[email protected]:~ > sudo fastboot erase system
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
sudo fastboot erase recovery
INPUT
[email protected]:~ > sudo fastboot erase recovery
OUTPUT
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
sudo fastboot -w
INPUT
[email protected]:~ > sudo fastboot -w
OUTPUT
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it just hangs on erasing 'cache'
I just close terminal and open new one, and run the next command
If your tablet hangs just reboot back into fastboot again
Code:
sudo fastboot erase boot
INPUT
[email protected]:~ > sudo fastboot erase boot
OUTPUT
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
sudo fastboot erase misc
INPUT
[email protected]:~ > sudo fastboot erase misc
OUTPUT
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
sudo fastboot erase cache
INPUT
[email protected]:~ > sudo fastboot erase cache
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
sudo fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
INPUT
[email protected]:~ > sudo fastboot -i 0x0B05 flash system boot.blob
OUTPUT
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
sudo fastboot -i 0x0B05 reboot
[email protected]:~ > sudo fastboot -i 0x0B05 reboot
OUTPUT
rebooting...
finished. total time: 0.020s
You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
Boot fully into rom then you can do whatever you would like!!!!!!!!!!!
Make sure you go thank @lj50036
....
Great Work
Its nice to see that my work on the 700 will be able to, maybe help the 300 community out also.... Keep up the good work.... Thx as always lj :silly:
Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?
OS
Erario said:
Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?
Click to expand...
Click to collapse
I can confirm this working on mint 15 32 bit, mint 15 64 bit, and mint 16 64 bit.. I would stay away from windows if at all possible....Thx lj
When for some reason will no longer start my "unbrickable TF300TG" (hehehe) I'll try with Windows and I will tell you.
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
feedback
ebildude123 said:
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
Did you come from a brick or did you just use nvflash to flash a recovery??
lj50036 said:
Did you come from a brick or did you just use nvflash to flash a recovery??
Click to expand...
Click to collapse
A brick
ebildude123 said:
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
My device is TF201.
Here is my long story: (search for my post)
http://forum.xda-developers.com/showthread.php?p=50690267
In short, i cannot get fastboot but can get to APX (power + up)
Was thinking of trying your steps but I dun understand how to get twrp.blob.
Also, prior to my brick i flashed some cwm recovery. Does that matter?
I have all the output files from the flatline thingy.
Any ideas?
vanquishe said:
My device is TF201.
Here is my long story: (search for my post)
http://forum.xda-developers.com/showthread.php?p=50690267
In short, i cannot get fastboot but can get to APX (power + up)
Was thinking of trying your steps but I dun understand how to get twrp.blob.
Also, prior to my brick i flashed some cwm recovery. Does that matter?
I have all the output files from the flatline thingy.
Any ideas?
Click to expand...
Click to collapse
You have your generated nvflash blobs???
lj50036 said:
You have your generated nvflash blobs???
Click to expand...
Click to collapse
I'm pretty noob so i'm not sure what you mean by generated nvflash blobs.
Here are the files in my nvflash dir:
blob.bin 1,670,651
blob.log 649
bootloader.ebt 1,558,608
bricksafe.img 12,058,624
create.bct 6,128
factory-config.img 5,242,880
libnv3p.dll 54,784
libnvaes_ref.dll 45,056
libnvapputil.dll 81,920
libnvboothost.dll 43,520
libnvdioconverter.dll 45,056
libnvflash.dll 81,920
libnvos.dll 101,376
libnvtestio.dll 96,768
libnvtestresults.dll 46,080
libnvusbhost.dll 44,544
nvflash.exe 272,896
pt_patch.log 298
pt_restore.log 299
recovery.bct 6,128
unlock-token.img 8,388,608
wheelie.exe 105,264
vanquishe said:
I'm pretty noob so i'm not sure what you mean by generated nvflash blobs.
Here are the files in my nvflash dir:
blob.bin 1,670,651
blob.log 649
bootloader.ebt 1,558,608
bricksafe.img 12,058,624
create.bct 6,128
factory-config.img 5,242,880
libnv3p.dll 54,784
libnvaes_ref.dll 45,056
libnvapputil.dll 81,920
libnvboothost.dll 43,520
libnvdioconverter.dll 45,056
libnvflash.dll 81,920
libnvos.dll 101,376
libnvtestio.dll 96,768
libnvtestresults.dll 46,080
libnvusbhost.dll 44,544
nvflash.exe 272,896
pt_patch.log 298
pt_restore.log 299
recovery.bct 6,128
unlock-token.img 8,388,608
wheelie.exe 105,264
Click to expand...
Click to collapse
Ok yes you should be able to do what you need to do.. You tell me what you need and we will get your tf201t up and running again.....
lj50036 said:
Ok yes you should be able to do what you need to do.. You tell me what you need and we will get your tf201t up and running again.....
Click to expand...
Click to collapse
First, let me thank you for responding. Really appreciate this.
You mean I actually have hope even that now I only have a black screen + APX device detected in windows 7?
Should we continue this on this thread? Since its tf201 and not tf300
Or should we continue on IRC?
http://forum.xda-developers.com/showthread.php?p=50690267
(please read my story (10th reply down))
I have no idea how to proceed at all and dun wish to do anything silly.
Should i follow what you did or this:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?p=50691902
-----------------------
1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie
wheelie.exe --blob blob.bin
5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:
nvflash.exe -r --download 4 blob.EBT
7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:
nvflash.exe -r --download 5 blob.SOS
8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:
nvflash.exe -r --download 6 blob.LNX
9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:
nvflash.exe -r --download 10 blob.APP
10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)
nvflash.exe -r --go
-----------------------
vanquishe said:
First, let me thank you for responding. Really appreciate this.
You mean I actually have hope even that now I only have a black screen + APX device detected in windows 7?
Should we continue this on this thread? Since its tf201 and not tf300
Or should we continue on IRC?
http://forum.xda-developers.com/showthread.php?p=50690267
(please read my story (10th reply down))
I have no idea how to proceed at all and dun wish to do anything silly.
Should i follow what you did or this:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
http://forum.xda-developers.com/showthread.php?p=50691902
-----------------------
1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie
wheelie.exe --blob blob.bin
5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:
nvflash.exe -r --download 4 blob.EBT
7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:
nvflash.exe -r --download 5 blob.SOS
8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:
nvflash.exe -r --download 6 blob.LNX
9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:
nvflash.exe -r --download 10 blob.APP
10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)
nvflash.exe -r --go
-----------------------
Click to expand...
Click to collapse
freenote
#crombix
kk
Thanks for your great tutorials. I did this process on my TF201 and it worked great. Trying to do the same on my teenagers TF300T and I'm running into an error.
When I do fastboot -i 0x0b05 flash system boot.blob I get error: cannot open "boot.blob"
Tried renaming the file, as well at using another copy of the file from my cloud. I noticed the file is listed as a txt file not a blob file
Never mind. Used the stock blob and it worked.
JoanneDisFan said:
Thanks for your great tutorials. I did this process on my TF201 and it worked great. Trying to do the same on my teenagers TF300T and I'm running into an error.
When I do fastboot -i 0x0b05 flash system boot.blob I get error: cannot open "boot.blob"
Tried renaming the file, as well at using another copy of the file from my cloud. I noticed the file is listed as a txt file not a blob file
Never mind. Used the stock blob and it worked.
Click to expand...
Click to collapse
Great to see you up and running ....
Let us know if there is anything you need help with in the future ...
Thx Josh
tf300t
Hello, i am new here, for this: My Name is Lorenzo.
My question is: is possible to rewrite The system of My TF300T from windows 7 with nvflash?
My Win7 detect tf300t only in APX Mode. Today from apx mode with The wheelie command i think That i have entered in NVFLASH mode, It is possible?
which are The command to rewrite system That i Must do to have a tablet functional At 100%? (Someone Can write here The exactly command That i Must type in Command Prompt? Thanks)
(Sorry for My bad English and if i have repeated answer or question in this forum)
I Hope That Someone Can help me, i am desperate! :'(
(Today evening, when i finished to work, i post The exatly files That i have to use nvflash and i Hope That Someone Can help me to exit from this situation.
Very thanks
Hello,
I Know my tf300t is an old one but I brick it yesterday. I try to resolve this problem with your tutorial.
I've got two problems with it:
- the link to download nvflash dans wheelie are down (if someone have them it would be aprreciate)
Thanks a lot
I am a mid type of developer certified by me
My Zenfone 5 is hard-bricked and I tried everything to enter fastboot. iSoc and xfstk downloader showing error or refusing to accept my phone.
But luckily I can boot the phone in CyanogenMOd.
So I was trying to flash the recovery via terminal
Upper part can be ignored.
Command lines that doesn't work:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
Optional I have tried
Code:
$ su
Code:
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
So the output was
Code:
29919+0 records in
29919+0 records out
15318521 bytes transferred in 0.342 secs (35459555 bytes/sec)
After that I have tried to reboot into recovery with
Code:
[email protected]:/ # reboot recovery
Well. The phone doesn't reboot into recovery. What I can guess is the partition mmcblk0p18 was wrong.
I tried the command
Code:
mount
to get the proper answer from the device. It was too hard to get the answer or I am junior on that.
So, can anyone give me the proper partition?
smnshuvo said:
I am a mid type of developer certified by me
My Zenfone 5 is hard-bricked and I tried everything to enter fastboot. iSoc and xfstk downloader showing error or refusing to accept my phone.
But luckily I can boot the phone in CyanogenMOd.
So I was trying to flash the recovery via terminal
Upper part can be ignored.
Command lines that doesn't work:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
Optional I have tried
Code:
$ su
Code:
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
So the output was
Code:
29919+0 records in
29919+0 records out
15318521 bytes transferred in 0.342 secs (35459555 bytes/sec)
After that I have tried to reboot into recovery with
Code:
[email protected]:/ # reboot recovery
Well. The phone doesn't reboot into recovery. What I can guess is the partition mmcblk0p18 was wrong.
I tried the command
Code:
mount
to get the proper answer from the device. It was too hard to get the answer or I am junior on that.
So, can anyone give me the proper partition?
Click to expand...
Click to collapse
Reffering to this and this Roms fstable, recovery can be found at:
Code:
/dev/block/by-name/recovery
I could not find the mmcblk number, it seems the partition mmcblk0p1 is used for recovery, boot and fastboot (look here), but I cannot confirm that. But maybe the thread help you a little bit.
Yes. Helped a bit. Thanks. :laugh: