Database Info

[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] Using nvflash to install custom recovery image on TF700T

I have an ASUS TF700T. The bootloader is unlocked and I have successfully used wheelie and nvflash to generate my blob files and create bricksafe images. I just installed the most recent jb firmware from the ASUS website and it wiped out my clockworkmod recovery. This would normally be ok but when I boot into the (now) stock recovery android tries to apply an update, immediately fails and the only options I have are to reboot, wipe/factory and wipe/cache. Thus, I cannot apply updates via recovery. I also can't install .img or blob files from fastboot as a result of the nvflash/custom bootloader process. As an added bonus, I can't get root in android because the only way I've found to do that is apply an update from recovery! APX mode is working fine and wheelie and nvflash are still working fine. If I could figure out how to a.) somehow get root in jb without flashing via fastboot or recovery or b.) get clockworkmod back I would be fine. I'm hoping someone can tell me how to flash a custom recovery using nvflash. The only stuff I've found is for the gtablet and I'm not familiar enough with nvflash (or android rooting in general) to be comfortable just "trying" commands intended for a different tablet.

wmarple said:
I have an ASUS TF700T. The bootloader is unlocked and I have successfully used wheelie and nvflash to generate my blob files and create bricksafe images. I just installed the most recent jb firmware from the ASUS website and it wiped out my clockworkmod recovery. This would normally be ok but when I boot into the (now) stock recovery android tries to apply an update, immediately fails and the only options I have are to reboot, wipe/factory and wipe/cache. Thus, I cannot apply updates via recovery. I also can't install .img or blob files from fastboot as a result of the nvflash/custom bootloader process. As an added bonus, I can't get root in android because the only way I've found to do that is apply an update from recovery! APX mode is working fine and wheelie and nvflash are still working fine. If I could figure out how to a.) somehow get root in jb without flashing via fastboot or recovery or b.) get clockworkmod back I would be fine. I'm hoping someone can tell me how to flash a custom recovery using nvflash. The only stuff I've found is for the gtablet and I'm not familiar enough with nvflash (or android rooting in general) to be comfortable just "trying" commands intended for a different tablet.
Click to expand...
Click to collapse
Have you looked at this thread, post #189:
http://forum.xda-developers.com/showthread.php?t=1901479&page=19
I think the info you need is there. Unfortunately I have no personal experience since I foolishly updated to .30 just prior to the release of NVFlash for the TF700. I'm *very* jealous Good luck!

wmarple said:
I also can't install .img or blob files from fastboot as a result of the nvflash/custom bootloader process.
Click to expand...
Click to collapse
fastboot should still work, why doesn't it work for you?

Fastboot still works in the AndroidRoot bootloader. Make sure you flash .blob files to staging, though.

[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.

[Q] Power on/Reboot now goes into APX mode

Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!

APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI

lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).

wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???

lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!

wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??

lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?

wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??

lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.

wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??

lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.

wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know

lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far

wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....

lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol

One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...

wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....

lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!

wha2do said:
Good to go!
Click to expand...
Click to collapse
??????

Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!