Related
Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.bin --odm 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: 0x37c708542bff297
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!
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?
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin
rigidsh said:
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin
Click to expand...
Click to collapse
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.
Looking for some help on this...
Hi!
So you got the TF300T into APX mode and ran these commands?:
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
...Did you have the files on your PC or on the tablet themselves? Also, how do you get the twrp-ICS.img? I've got the openrecovery-twrp-2.2.2.0-tf300t-ICS.blob file. Do I change it to twrp-ICS.img somehow?
Sorry if this seems like a dumb question. I want to get back to ICS bootloader from JB but finding instructions has been kind of tough. Your post is the first I've found that helps!
Thanks!
-Rob
orion42 said:
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.
Click to expand...
Click to collapse
First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.
THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
orion42 said:
First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named)
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.
Click to expand...
Click to collapse
robcomet1 said:
THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
Click to expand...
Click to collapse
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Will do! Still haven't had a chance to do it yet. Will let you know.
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse
Finally got a chance to do this to my pad and it worked great! Thanks again for the help my friend! I'm back on CM10 as we speak! :victory:
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse
orion42
As you said information about restore with NVFlash is sparse. Could you create a thread with the proper information that others can follow to recover their units? I don't have NVFlash but have seen numerous threads where people needed help as you provide.
Thanks!
orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
I can't believe you posted that! Have you by chance seen how many bricks there have been on nvflash due to lack of info?
Your guide is good for creating files but no mention of how to use them. Everyone doesn't have your knowledge and insight.
Maybe it is time to reveal the secrets of nvflash. It could be a good thing but as it stands it is a brick maker due to lack of knowledge and help.
rayman said:
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM
uumeshh said:
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM
Click to expand...
Click to collapse
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
http://forum.xda-developers.com/showthread.php?t=2012033
rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Yes, of course, how mindless of me not to know those commands but now I can run them. But wait, I just remembered, I already successfully downgraded to ICS 2 months ago using the mindless method. Incidentally, I never said it was a good idea but rather it was the only idea someone as mindless as me could come up with. How could it possibly have worked? I just got lucky I guess.
tobdaryl said:
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
UI for blobtools - http://forum.xda-developers.com/showthread.php?t=2012033
Click to expand...
Click to collapse
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?
uumeshh said:
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?
Click to expand...
Click to collapse
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.
tobdaryl said:
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.
Click to expand...
Click to collapse
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !
hunterr986 said:
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !
Click to expand...
Click to collapse
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.
tobdaryl said:
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.
Click to expand...
Click to collapse
Thank you for your reply.
I have a TF300T !
Unfortunately i do not have the blob.bin . I did not create it while unlocking my device.
So after unlocking my device my friend tried to flash a rom buring which he wiped out everything, flashed and rebooted. After which it got stuck in an infinite bootloop at Asus Logo.
I can get into APX mode so i did a lot of research and realized that i dont have the blob.bin !
so i am trying every possible tutorial before declaring it as bricked.
Is there a way i can unbrick it ? The main problem is that it doesnt have fastboot or adb access.
PS: I came across a petition on the internet asking asus for giving access n all ... I am assuming its for letting people like me without blob.bin to unbrick theor devices ! Am i right ?
I have Asus TF101 b90 Eepad. It's locked in a boot loop. I have Rogue XM Recovery 1.3.0 - CWM-based recovery v 5.0.2.7. I've tried to reflash a new stock or modified ROM, but none of the methods found on the forums seems to be working. I cannot write the blob.EBT file, using wheelie+nvflash. It seems to format the EBT partition but locks during writing process, with the message: "Sending file: blob.ebt 65536/1454712 bytes sent" and that's all. I can't even format /data/media folder. Looks like the nv chip is write protected - none of the chmod methods worked. I can use nvflash or ADB so it boots in recovery, i've tried both Linux and Windows 7 nvflash+wheelie with the same result: no changes to ROM, recovery image or anything else. I don't know what hapened prior to boot loop because one of my kids was using the Eepad - i assume it started updating or something. Tablet was rooted but i don't think it was ROM Manager.
Have you tried to wipe all data, cache, and Dalvik-cache?
Sent from my Transformer TF101 using Tapatalk HD
asd25_2005 said:
I have Asus TF101 b90 Eepad. It's locked in a boot loop. I have Rogue XM Recovery 1.3.0 - CWM-based recovery v 5.0.2.7. I've tried to reflash a new stock or modified ROM, but none of the methods found on the forums seems to be working. I cannot write the blob.EBT file, using wheelie+nvflash. It seems to format the EBT partition but locks during writing process, with the message: "Sending file: blob.ebt 65536/1454712 bytes sent" and that's all. I can't even format /data/media folder. Looks like the nv chip is write protected - none of the chmod methods worked. I can use nvflash or ADB so it boots in recovery, i've tried both Linux and Windows 7 nvflash+wheelie with the same result: no changes to ROM, recovery image or anything else. I don't know what hapened prior to boot loop because one of my kids was using the Eepad - i assume it started updating or something. Tablet was rooted but i don't think it was ROM Manager.
Click to expand...
Click to collapse
Since nvflash works, flash the stock ROM.. yous said it gets stuck while pushing ROM right ? Then let tit take time and leave it to work on its own phase and wait for it to finish. In my experience easy flasher/nvflash takes little time to complete. If that doesn't work then try pushing TWRP recovery using nvflash/easy flash.. BTW I also have B90 and nvflash always worked for me..
Sent from my Transformer using xda app-developers app
No results
kenshin1388 said:
Have you tried to wipe all data, cache, and Dalvik-cache?
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
Yes, i've tried theese methods with no results. I can only format SD card - external. After reboot is all in the same place . Nothing changes.
udupa82 said:
Since nvflash works, flash the stock ROM.. yous said it gets stuck while pushing ROM right ? Then let tit take time and leave it to work on its own phase and wait for it to finish. In my experience easy flasher/nvflash takes little time to complete. If that doesn't work then try pushing TWRP recovery using nvflash/easy flash.. BTW I also have B90 and nvflash always worked for me..
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I've left it for hours to write the blob.ebt file but stays like that forever. I've tried to use nvflash --format_partition 4 (in my case is the ebt partition) with no results - it stays saying "formatting" and remains in this state.
I have tried to push other recoveries using ADB push. If a file is written to the SDcard - internal memory, after reboot it delets it. If i try to make another folder on the internal memory it says: "Read only folder" and it doesn't allow to write any files or folders. I've tried chmod with no results. I wanna use RMA for my tablet (i have 2 years of warranty for this - 1 year left but i can't delete the Rogue Recovery so i can return it).\
Thanx for your advices!
asd25_2005 said:
I've left it for hours to write the blob.ebt file but stays like that forever. I've tried to use nvflash --format_partition 4 (in my case is the ebt partition) with no results - it stays saying "formatting" and remains in this state.
I have tried to push other recoveries using ADB push. If a file is written to the SDcard - internal memory, after reboot it delets it. If i try to make another folder on the internal memory it says: "Read only folder" and it doesn't allow to write any files or folders. I've tried chmod with no results. I wanna use RMA for my tablet (i have 2 years of warranty for this - 1 year left but i can't delete the Rogue Recovery so i can return it).\
Thanx for your advices!
Click to expand...
Click to collapse
Try BRK's tool to unroot and flash a stock ROM, following the instructions in the tool.
http://forum.xda-developers.com/showthread.php?t=1688447
No results
sidneyk said:
Try BRK's tool to unroot and flash a stock ROM, following the instructions in the tool.
http://forum.xda-developers.com/showthread.php?t=1688447
Click to expand...
Click to collapse
Thanx for your reply. I've downloaded BRK's tool. It does work. Writes recovery but after restart it's all back in the same place, nothing changes!
Here is an example of nvflash:
D:\backup tablet\nvflashWW\nvflashWW>wheelie.exe -2 --bct transformer.bct --bl
bootloader.bin --odm 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: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
- 65536/1454712 bytes sent >>>>>>> And it remains like that.
Any ideas?
Thanx in advance for your help!
I'm using Windows 7 Ultimate N 32bit edition
I just remembered something. Your blob.ebt file may be corrupt. A few months back I took a nvflash backup of several recoveries so I could keep them on hand. Problem was, when I wanted to flash a copy of TWRP I made it always froze. No other recovery backups did though. Try to get a stock fresh copy of stock Rom and use blobunpack on that.
Sent from my U8652 using xda premium
Download a stock ASUS zip for your fw, fresh, the whole 300+mb file, run blobunpack on it and flash it (ebt portion of blob) through bootloader (EBT) partition or staging (mmcblk0p4) partition.
EDIT: do you have adb access? fully working
asd25_2005 said:
Thanx for your reply. I've downloaded BRK's tool. It does work. Writes recovery but after restart it's all back in the same place, nothing changes!
Here is an example of nvflash:
D:\backup tablet\nvflashWW\nvflashWW>wheelie.exe -2 --bct transformer.bct --bl
bootloader.bin --odm 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: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
D:\backup tablet\nvflashWW\nvflashWW>nvflash -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
- 65536/1454712 bytes sent >>>>>>> And it remains like that.
Any ideas?
Thanx in advance for your help!
I'm using Windows 7 Ultimate N 32bit edition
Click to expand...
Click to collapse
You are able to get the tablet into APX mode? If so, maybe try to redownload the stock firmware from Asus, in case you had a bad download. I used Asus 9.2.1.27 US as I have a US tablet.
No results
kenshin1388 said:
I just remembered something. Your blob.ebt file may be corrupt. A few months back I took a nvflash backup of several recoveries so I could keep them on hand. Problem was, when I wanted to flash a copy of TWRP I made it always froze. No other recovery backups did though. Try to get a stock fresh copy of stock Rom and use blobunpack on that.
Sent from my U8652 using xda premium
Click to expand...
Click to collapse
Thanx again for your reply. I've already tried different versions of stock ROM and blobunpack to extract the needed blob.EBT file. I'ts the same error, stuck at 65536. Anyway, yesterday i got a new mail, a reply from Asus, telling me that the problem may be a hardware memory issue (the memory chip itself, into the motherboard). If i have rooted my tablet and replaced the stock recovery with a custom one do i lose RMA or is still effective? If not, can they change the deffective chip with a new one?
Have a nice day!
Yes, i have ADB access
Thing O Doom said:
Download a stock ASUS zip for your fw, fresh, the whole 300+mb file, run blobunpack on it and flash it (ebt portion of blob) through bootloader (EBT) partition or staging (mmcblk0p4) partition.
EDIT: do you have adb access? fully working
Click to expand...
Click to collapse
Thanx for your reply.
I have ADB acces, in recovery mode, and even APX mode for nvflash. Pushing or pulling files works in ADB but the internal memory seems to be read-only. What can i do to make a full repartitioning of the internal memory? I'm at a point where i wish to do a permanent brick so i can return it to Asus using the RMA.
Have a nice day!
I'm not sure how to execute the binary for fat32 or ntfs, but I know most custom roms come with mke2fs binary with busybody. You could use that to completely reformat the internal memory.
Can get the mountpoint using this or something of the mounted area you need to reformat. I know by default mke2fs reformats to ext4. A quick Google search should return a result.
mountpoint -n /sdcard
Sent from my Transformer TF101 using xda premium
Some results
Thanx, kenshin.
I've managed to get around the "65536/1454712 bytes sent" by modifying the flash.cfg file:
[device]
type=hsmmc
instance=2 >>>>>>>> originally was 3
it sends data much slower but, hey, it works.
So now it's writing the blob files but, at the end, it runs into a new error:
C:\wheelie>cd C:\wheelie\
C:\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x3
00d8011
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: 0x251199388316139799
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile flash.cf
g --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4282368/4282368 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
\ 4044800/4044800 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x8 (0x11000008)
flags: 0
C:\wheelie>pause
Press any key to continue . . .
Aaaand, i'm stuck again! I've read about using the wrong version of nvflash so i tried several nvflash executables, including the ones found in EasyFlasher or BRK Rootkit with no results. Older version of nvflash seems to send the blob files and after that the tablet freeze. When i re-start it it's back again, in boot loop, with the original ROM and no other changes!
Again i think that the memory chip is read-only, due some hardware errors.
I can't do nothing to change even one single file in the internal memory using ADB or APX mode.
See this thread. Their answer is post 22. Different device but same problem... hope you can figure it out!
SOLVED
My ASUS TF101 was sent for RMA. They've changed the motherboard. This confirmed that my worst case scenario was true: the eMMC became Read-only and there was no way to restore the tablet. Now it works again and is everything is ok. Thanks for your interrest in assisting me.
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