Database Info

[q] need help with nvflash please

LAST NIGHT I WAS GIVEN TWO DIFFERENT THINGS TO FLASH ONE WAS THIS
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img AND THE OTHER WAS THIS nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img CAN SOMEONE PLEASE TELL ME WHICH IS CORRECT. NOTICE ONE HAS .EXE AFTER NVFLASH AT THE BEGINNING AND THE OTHER DOES NOT. I TRIED THE ONE WITHOUT THE .EXE AND IT DID NOT WORK. I ENDED UP DOING A FACTORY RESET ON MY PHONE. (NOT HAPPY ABOUT THAT) NEED SOME HELP PLEASE AND THE CORRECT CODE. THANKS

you'll need to have nvflash setup properly and the NVidia boot-recovery driver installed. good instructions can be found here http://android.modaco.com/content/lg...-links-active/
download test2.img http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz
place the recovery-star-test2.img in your nvflash folder.
download clockwork recovery test2-- http://mirror.dal.tdrevolution.net/c...h-recovery.tgz . extract it.
in the extracted folder of cwm recovery test2, i took all the files except for test2.img and nvflash and put them in my nvflash folder.
- power off your phone. take out the battery. unplug the usb cable from the phone,you can leave the other end plugged in to the pc.
hold down both volume buttons on the phone. while holding them down, plug the usb cable in to your phone. you should hear the windows device connected sound. that's good. you'll see nothing on the phone. you can let go of the volume buttons now.
hold shift and right click an empty area inside the nvflash folder. select "open command window here".
if you can't do that, cd to your nvflash folder.
now, copy and paste this into the command window...
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img
press enter

crazythunder said:
you'll need to have nvflash setup properly and the NVidia boot-recovery driver installed. good instructions can be found here http://android.modaco.com/content/lg...-links-active/
download test2.img http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz
place the recovery-star-test2.img in your nvflash folder.
download clockwork recovery test2-- http://mirror.dal.tdrevolution.net/c...h-recovery.tgz . extract it.
in the extracted folder of cwm recovery test2, i took all the files except for test2.img and nvflash and put them in my nvflash folder.
- power off your phone. take out the battery. unplug the usb cable from the phone,you can leave the other end plugged in to the pc.
hold down both volume buttons on the phone. while holding them down, plug the usb cable in to your phone. you should hear the windows device connected sound. that's good. you'll see nothing on the phone. you can let go of the volume buttons now.
hold shift and right click an empty area inside the nvflash folder. select "open command window here".
if you can't do that, cd to your nvflash folder.
now, copy and paste this into the command window...
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img
press enter
Click to expand...
Click to collapse
ok thanks. i am going to try it that way. i just tried again with the code with .exe in it an my command prompt is just sitting still at nvflash started. in the device manager it says i am hooked up by usb and i have the nvflash folder extracted, the connection test has the system info on it but it says at the end of it command failure, no bootloader was specified. im doing this on a windows xp but will above work on a windows 7 64 bit ??

Even faster, just download "ROM manager" from the marketplace. Press "Flash ClockwordMod Recovery" then choose "Tmobile G2X".
Now you have clockworkmod recovery installed

andonnguyen said:
Even faster, just download "ROM manager" from the marketplace. Press "Flash ClockwordMod Recovery" then choose "Tmobile G2X".
Now you have clockworkmod recovery installed
Click to expand...
Click to collapse
and holding vol. down and power will perform a factory rest afterwards. unless that's been fixed.?
it's been noted here many times that doesn't work. if you get stuck in a bootloop, you can't restore backups. you'll still have to nvflash.

crazythunder said:
and holding vol. down and power will perform a factory rest afterwards. unless that's been fixed.?
it's been noted here many times that doesn't work. if you get stuck in a bootloop, you can't restore backups. you'll still have to nvflash.
Click to expand...
Click to collapse
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.

tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
I think I am about to do the same. just do the recovery through rom manager and wait till an easier, more clear method is found for nvflash. I just wanted to flash Pauls patch anyway. Thanks

tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
there were a couple people out here in a bootloop and a factory reset ended in another bootloop. nvflash is the only cure at that point.

command failure, no bootloader was specified
that's normal

crazythunder said:
there were a couple people out here in a bootloop and a factory reset ended in another bootloop. nvflash is the only cure at that point.
Click to expand...
Click to collapse
Not to mention the fact that I don't really feel like doing a factory reset every time I'm in a bootloop But hey, to each his/her own I guess.

crazythunder said:
command failure, no bootloader was specified
that's normal
Click to expand...
Click to collapse
nothing ever happened on the screen of my phone. and when i held down volume- and power I ended up factory restoring my phone. Did learn that wont remove root or superuser though and they say it is good for the battery anyway so what the heck i guess but I have almost got everything restored and I dont really feel like doing it again. Is there any other way to tell if it worked?? I dont think it did since the phone did nothing.

MWBehr said:
Not to mention the fact that I don't really feel like doing a factory reset every time I'm in a bootloop But hey, to each his/her own I guess.
Click to expand...
Click to collapse
non believers lol. is it possible that some can access recovery by hardware buttons after cwm through rom manager? and others can't?

[email protected] said:
nothing ever happened on the screen of my phone. and when i held down volume- and power I ended up factory restoring my phone. Did learn that wont remove root or superuser though and they say it is good for the battery anyway so what the heck i guess but I have almost got everything restored and I dont really feel like doing it again. Is there any other way to tell if it worked?? I dont think it did since the phone did nothing.
Click to expand...
Click to collapse
unplug your phone from the usb. leave the other end plugged in to the pc.
TAKE OUT THE BATTERY! hold down both volume buttons while plugging in the usb. you should hear the windows device connected sound. let go of the volume buttons.
open the command window by right clicking an empty area inside the nvflash folder,select "open command window here" . copy and paste this into the command window nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img .
make sure there are no spaces between emmc and _x8.bct. copying and pasting has done this to me.
now press enter on your keyboard. you should get a software update screen on your phone. and command prompt should say something like test2 sent successfully. unplug the usb. put the battery back in. press volume down and power AND HOLD BOTH FOR AT LEAST 10-15 SECONDS. you should now be in custom recovery.

crazythunder said:
non believers lol. is it possible that some can access recovery by hardware buttons after cwm through rom manager? and others can't?
Click to expand...
Click to collapse
Not that I've seen. I was wondering if it might be possible if you manually copied the update.zip to the _externalSD. Unfortunately I can't test this without reverting back to stock recovery, and I'm far to lazy for this
I'm pretty sure it's not possible without doing this, however, as recovery has no access to the internal SD (which is where Rom Manager puts the update.zip by default).

MWBehr said:
Not that I've seen. I was wondering if it might be possible if you manually copied the update.zip to the _externalSD. Unfortunately I can't test this without reverting back to stock recovery, and I'm far to lazy for this
I'm pretty sure it's not possible without doing this, however, as recovery has no access to the internal SD (which is where Rom Manager puts the update.zip by default).
Click to expand...
Click to collapse
i downloaded cwm 3.0.2.7 through rom manager, then flashed it with nvflash, just to be safe

crazythunder said:
i downloaded cwm 3.0.2.7 through rom manager, then flashed it with nvflash, just to be safe
Click to expand...
Click to collapse
Thanks for the reminder, need to update mine

I know this thread is a bit old but is there anyways someone could upload those files again? The mirrors aren't working =/
Thanks!

tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
This is the worst advice I have ever heard. Do not follow what this guy says.
ALWAYS ALWAYS ALWAYS Nvflash. If you need to reinstall the stock bootloader then nvflash it back... some peoples kids....jeez
Pin it to Win it.

Xura08, here are the files:
NVFlash(internal) http://www.4shared.com/zip/xJJN9V_S/file.html
Gapps http://www.4shared.com/zip/54MpCVPK/file.html
Root http://www.4shared.com/zip/_LhBfM8o/file.html
Unroot http://www.4shared.com/zip/Dkj8D20u/file.html
Cm7-224 http://www.4shared.com/zip/tVg0T0Y4/file.html
Sent from my LG-P999 using xda premium

Do not use rom manager it fake flashes the phone not real cwm if something happens during a flash through rom manager you end up having to do nvflash anyway to fix it
Sent from my HTC Sensation 4G using xda premium

[Q] TF101G (B80) lost CWM but still Root

Hello,
I tried upgrading CWM via ROM Manager...and can confirm: It dont work
If I try to go to CWM, equal how (Software or Hardwarebuttons) he says starting CWM and nothing happens. Only way is to boot with Vol+.
Also failt install CWM via apk.
Only way I can imagine is to flash a old rom with CWM, maybe honecomb, via MicroSD? Any working link to such a old rom? And how to flash?
Thank you in advance.

ArnomaF said:
Hello,
I tried upgrading CWM via ROM Manager...and can confirm: It dont work
If I try to go to CWM, equal how (Software or Hardwarebuttons) he says starting CWM and nothing happens. Only way is to boot with Vol+.
Also failt install CWM via apk.
Only way I can imagine is to flash a old rom with CWM, maybe honecomb, via MicroSD? Any working link to such a old rom? And how to flash?
Thank you in advance.
Click to expand...
Click to collapse
You say you lost cwm, so how are you going to flash an older rom via cwm?
Team Rouge has an nvflash version of their recovery or try RecoveryInstaller

Rom manager is bad news for the tf101, please don't use it in the future.
To fix this (Run in an adb-shell on a computer or terminal emulator on the device, if you can boot, I hope you still have root.)
Download any cwm-flashable recovery. Extract the recoveryblob file out of the zip and place it on your tf, via mass storage or ADB (I recommend rouge)
Then run these commands in term em or adb shell
Code:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4 (Please note the your/blob/here part, you need to type the path of where you placed your recoveryblob here)
reboot
Should get you backing into a non-borked recovery.

Thing O Doom said:
Should get you backing into a non-borked recovery.
Click to expand...
Click to collapse
****. It dont work.
Have read about it. But you had give me the way to try.
Have tested Rouge and Rouch recoveryblob.
Both the same.
su (Grant)
dd if=/Removable/MicroSD/recoveryblob of=/dev/block/mmcblk0p4
Gives me:
8984+1 records in
8984+1 records out
4599884 bytes transfered in...
[email protected]:/#
Looks all fine in my eyes. (I'm DOS-Windows, not Linux)
Why it dont works??
Booting recovery kernel image-> nothing happens

baseballfanz said:
You say you lost cwm, so how are you going to flash an older rom via cwm?
Click to expand...
Click to collapse
Not via CWM with CWM I wrote...
baseballfanz said:
Team Rouge has an nvflash version of their recoveryr
Click to expand...
Click to collapse
How can I flash what? Only put on MicroSD? And then?
baseballfanz said:
or try RecoveryInstaller
Click to expand...
Click to collapse
Have tried. Dont work

Via and with are the same... xD pointless from here.
Last step is to try to reflash the bootloader EBT partition and see if that's the issue, since your recovery flashed fine.
If not, NvFlash here you come!

Thing O Doom said:
Last step is to try to reflash the bootloader EBT partition
Click to expand...
Click to collapse
Ok. How do I do that?

Blobunpack a stock OTA from asus's site,
then take the .EBT rename it to blob with no extension and use the same command to flash it.

ArnomaF said:
Ok. How do I do that?
Click to expand...
Click to collapse
I think the best way now is to go back to stock.
Same way use NVflash to flash full firmware and start again rooting and installing CWM...

farsight73 said:
I think the best way now is to go back to stock.
Same way use NVflash to flash full firmware and start again rooting and installing CWM...
Click to expand...
Click to collapse
Agree with you. But then I need a link to a easy rootable firmware (up to 8.6.6.19 for Razorclaw) and a short description how to flash.

Try my PERI one-click, it should install recovery and walk you through rooting just fine, if you can boot into android. If not just flash the latest OTA completely (Everything including ebt) should fix any recovery and bootloader problems. Then you can run PERI and it will install recovery and root for sure. If you want

I think I going to be crasy, because 3 days later and no sucsess
to sum up:
1. Gnufabio's RecoveryInstaller.apk
work, reboot, stuck, Power&Vol-, Vol+ stuck at booting recovery kernel image
2. NVFlash
somebody wrote NVFlash is inpossible for B80
seems to be true:
rcm version 0X4
Comand send failed (usb write failed)
3. my last hope: ADB
a) Power&Vol+, adb shell-> device not found (Device Manager: Nvidia USB boot-recovery driver for mobile devices)
b) Power&Vol-, Vol+, adb shell:
List of devices:
0123456789ABCDEF offline
Device Manager: Asus Transformer ADB Interface
c) normal reboot, stuck on EeePad Screen, same as b)
Now I'm on the end of my ideas...
BTW. Tried also this, but dont work.
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 in Terminal on the pad->done, but nothing happens
BTW2 Im on Megatron 1.1.4 - It works but I cant take part of the development on this.
BTW3 @Thing o Doom: Your PERI also dont work. Think it belonges to the ADB Problems.
BTW4 If I try to going into recovery there is written:
Android WW_epad-user bootloader < e> released by WW_epad-8.6.6.23-20111202
Checking for Android ota recovery
Skipping android ota checking
Checking for RCK..press key <VOL_Up> in 5 sec to enter RCK
Booting recovery kernel image
If I understand that right it may possible to flash a OTA-Update with this method?
Which schould i use?
BTW5 Tried to copy Rouges recoveryblob to mmcblk04p. Was sucessful, but nothing happens

EDIT:
I just talked to Rayman and this won't work for you, TF101G devices have another SBK. I'm sorry.
Hi there.
I made this tool for you.
http://www.mediafire.com/?5wi7ga8c7b4wz1p
Unzip and start EasyFlasher.exe
1. Put your tablet in APX mode (Hold down Power and volume up)
2. Install APX drivers if needed
3. In EasyFlasher, click on the "Wheelie" button, this prepares your tablet for nvflash.
4. Click Flash recovery.
This should work if you have a SBK2 device, I have heard that newer TF101Gs have a newer SBK, if you have a newer SBK, this will not work.
EDIT:
This tool will only work with any SBK2 device at the moment.
Credits to AndroidRoot.mobi for Wheelie.

[Q] TF300 block on asus logo after cm10 update

I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.

bourrin said:
I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.
Click to expand...
Click to collapse
This is the wrong cwm for your unit; it is for TF201.
This link provides help for your problem. http://forum.xda-developers.com/showthread.php?t=1680570
Look for this heading in the link posted above. - Flashed TF201 Recovery in ROM Manager?
In answer to your question, no.
Good Luck!

The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.

bourrin said:
The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.
Click to expand...
Click to collapse
Without nvflash previously installed I have not heard of anyone getting any use of apx.
My understanding you have three choices to recover your unit.
ADB, Fastboot, and recovery. In your case current recovery is out since we know it is the wrong one, that is unless you can flash the correct one.
I have read of people flashing with adb and fastboot even when the unit appeared not to respond and getting their unit restored.
So give the commands even without a response.
On most units when in cwm recovery adb works.
Also with fastboot commands try ( this example would be to flash twrp recovery )
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
then try
fastboot flash recovery twrp.blob
fastboot reboot
I know the -i 0x0B05 designates our Asus but at this stage your unit does know what it is and may be refusing based on being called Asus, so give the generic command if the normal ones don't work.
I have also read where you use the drivers from tf201 for adb and fastboot and getting their unit to respond. http://downloadandroidrom.com/file/TransformerPrime/drivers
I believe other drivers tried after tf201 were universal naked drivers.http://forum.xda-developers.com/showthread.php?t=1766220
Here is a thread you may fine useful. http://forum.xda-developers.com/showthread.php?t=1936648
Good Luck!

With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?

bourrin said:
With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?
Click to expand...
Click to collapse
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.

tobdaryl said:
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.
Click to expand...
Click to collapse
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.

bourrin said:
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.
Click to expand...
Click to collapse
Good info, thanks. I'll do some work and be back.

Ok. I uploaded what mostly appears to match your command line.
boot.img, recovery.img, and bootloader.bin all from jb 10.4.2.17.
http://www.mediafire.com/?2cpk65c5ddyek36
If you need something more or different please tell me.

Thanks you so much.
Can you just confirm the partition number of each file , please ?

bourrin said:
Thanks you so much.
Can you just confirm the partition number of each file , please ?
Click to expand...
Click to collapse
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)

tobdaryl said:
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)
Click to expand...
Click to collapse
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?

bourrin said:
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?
Click to expand...
Click to collapse
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin​ If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.

tobdaryl said:
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin​ If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.
Click to expand...
Click to collapse
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.

bourrin said:
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.
Click to expand...
Click to collapse
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439

I had forgotten to mention something important.
As you go through trying to sort this problem don't forget to recheck adb and fastboot access. I know it sounds silly but sometimes the most minor change or another reboot will give you access that was earlier missing.

I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?

bourrin said:
I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?
Click to expand...
Click to collapse
I have see that sometimes adb reconize apx mode. Do you know what driver can I use to try this ? Now I have universal_naked_driver_0.7

SAME PROBLEM as Bourrin
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
tobdaryl said:
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439
Click to expand...
Click to collapse

dltabrvo said:
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
Click to expand...
Click to collapse
Sorry, the file expired. Here is a new link for the download. http://www.mediafire.com/?ua7krzmadu3uyc1
Good Luck!

Bricked TF300T only APX works

Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks

foxrlx said:
Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks
Click to expand...
Click to collapse
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?

tobdaryl said:
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?
Click to expand...
Click to collapse
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.

foxrlx said:
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.
Click to expand...
Click to collapse
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.

tobdaryl said:
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.
Click to expand...
Click to collapse
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks

foxrlx said:
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks
Click to expand...
Click to collapse
In my nvflash restore guide I have removed my second restore method till further study can be done.

tobdaryl said:
In my nvflash restore guide I have removed my second restore method till further study can be done.
Click to expand...
Click to collapse
Should I post about this on your thread about the nvflash?

foxrlx said:
Should I post about this on your thread about the nvflash?
Click to expand...
Click to collapse
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.

tobdaryl said:
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.
Click to expand...
Click to collapse
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah

foxrlx said:
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah
Click to expand...
Click to collapse
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob

tobdaryl said:
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Click to expand...
Click to collapse
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB

foxrlx said:
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB
Click to expand...
Click to collapse
I'm still refining my next offer. I'll give you a shout when I'm finished - testing is in progress but slow.

The only way I found to emulate your tablet was to flash cm 10.1 while running stock ICS 9.4.3.30. The next hour was spent just getting the computer and tablet to communicate. I had to boot linux and use it to gain access. Once I used linux to nvflash 9.4.3.30 bootloader, boot, system, and twrp recovery windows recognized the tablet again but I still had no bootloader menu or useable tablet.
About an hour and a half later I had a fully functional tablet. I can't post or suggest the method I used used to recover as it borders on insanity.
Later tonight I'll try for a much safer and simpler method.

Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4

foxrlx said:
Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4
Click to expand...
Click to collapse
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?

tobdaryl said:
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?
Click to expand...
Click to collapse
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4

foxrlx said:
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4
Click to expand...
Click to collapse
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.

tobdaryl said:
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.
Click to expand...
Click to collapse
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.

foxrlx said:
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.
Click to expand...
Click to collapse
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go

tobdaryl said:
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go
Click to expand...
Click to collapse
I tried several times but nothing different happened, I don't know what's happening that my bootloader menu doesn't show up.
What could interfere with this? Besides the blob.ebt file.
When you restore your device what rom and recovery you use?
Thanks.

Bootloop when starting android or RCK

I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.

Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk

Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.

That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk

Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)

I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?

double post

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.

Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385

berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??

berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks

ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!

monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks

ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.

monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks

ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.

monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!

berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.

monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?