Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
sbdags said:
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
Click to expand...
Click to collapse
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Motawa88 said:
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Click to expand...
Click to collapse
They'll know you unlocked it as you had to use their unlock tool which dialled home and got the unlock keys....... so yes it is in their database so you warranty is now void I'm afraid.
Asus TF700T Tablet fix
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
A big big thanks. This instructions worked for my Asus tf700t. It was hard bricked.
Browndog181 said:
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Click to expand...
Click to collapse
I am trying to fix my tf700. Trying to flash the blob..
Code:
D:\Desktop\TF700>fastboot -i 0x0B05 flash system d:\desktop\TF700\blob
erasing 'system'...
OKAY [ 0.702s]
sending 'system' (800927 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3.439s
Any idea?
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
berndblb said:
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
Click to expand...
Click to collapse
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
krugm0f0 said:
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
Click to expand...
Click to collapse
Are you up and running now?
You may want to try a different USB port. I had the same error when I tried to use a USB hub to connect to my CPU.
Related
Tools
1. Flash Tools for HTC Magic (inculed USB driver, Fastboot.exe, nandroid img) HTC_G2_TOOL.rar http://www.hiapk.com/bbs/download.p...e825b983cad5661d08bef017c59522a12d38ed3f63b09
2. SDK Tools AdbWin.zip (adb for Windows)
3. SPL HBOOT Rom http://forum.xda-developers.com/showthread.php?t=529019
4. USB Cable
How to check your SPL Version
1. Power off your phone
2. Push “Back” + “Power” about 5s (**After that you should see three androids on skateboards)
3. Check your version and go here (http://forum.xda-developers.com/showthread.php?t=529019) download a downgrade version. (In my case, I will download Modded HBOOT-1.33.2004)
My HTC Magic SPL info:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009,21:02:32
How to go Recovery model:
1. Put the files Adb and AdbWinApi.dll from AdWin.zip into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2. Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3. Create a folder on the C: drive of your PC called android. The path should be C:\Android and unzip HTC_G2_TOOL.zip into C:\Android.
4. Unplug the USB cord and power off your phone
5. Power up your phone by holding “Black” + “Power” , you should see three androids on skateboards.
6. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
7. Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in HTC_G2_TOOL.rar.
8. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
9. Type cd C:\android
10. then enter the following command C:\android > fastboot boot recovery.img
11. Your phone should now be reboot and booting in Recovery model
How to Backup your Rom:
1. After booting into recovery model
2. select [Alt+B] – Nandroid Backup 2.1
3. After few minutes all backup file will save in your SD card
How to restore from your backup file
1. Download one of the above signed SPL updates and rename it to update.zip
2. Copy update.zip to the root of your SD-card
3. Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder C:\Android.
4. booting your Magic into recovery model
5. select [Alt + S] – Apply sdcard:update.zip
6. select [Home + Back] – reboot system now
7. After reboot it will update upgrade/downgrade your SPL version, then power off your Magic again
8. Push “Back” + “Power” to HBOOT model
9. double check your SPL version is upgrate/downgrate
10. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
12. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
13. Type cd C:\android
11. then enter the following commands C:\android >
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
12. After reboot your Magic, it need about 2-5 min to restore
13. then a band new original Android 1.5 is restored
Remark:
**Please make sure your battery got enough power (Suggestion: more than 50%)
where is the restore img?
You can backup from your Phone~~
Hi there toneytse!
I have the exact same SPL/Hardware. The guide is extremely useful therefore, as it eliminated any doubt I had about the procedure, so thank you for that. I need a small clarification, though, if you care to oblige.
In order for the warranty to be valid no "tampering" must be evident, so if at some point I need to return the device for repair I will need to be able to replace the SPL (as well as the Nandroid backup) to the original ones.
How can I be sure that the provided signed SPLs are exactly-bit wise identical to the original one? Is there a way to back my own SPL (in case it is slightly different) instead of using one the signed provided ones? Or shouldn't I worry since all the SPLs with identical specs are actually identical?
Cheers
rayg256 said:
Hi there toneytse!
I have the exact same SPL/Hardware. The guide is extremely useful therefore, as it eliminated any doubt I had about the procedure, so thank you for that. I need a small clarification, though, if you care to oblige.
In order for the warranty to be valid no "tampering" must be evident, so if at some point I need to return the device for repair I will need to be able to replace the SPL (as well as the Nandroid backup) to the original ones.
How can I be sure that the provided signed SPLs are exactly-bit wise identical to the original one? Is there a way to back my own SPL (in case it is slightly different) instead of using one the signed provided ones? Or shouldn't I worry since all the SPLs with identical specs are actually identical?
Cheers
Click to expand...
Click to collapse
I suggest you find the same version SPL in here(http://forum.xda-developers.com/showthread.php?t=529019)
In my case, i can use SHIPMENT SPL HBOOT-1.33.0009H Signed update.zip to upgrade back to same SPL version, but i am not sure repair center will check it or not. So take your risk when you hacking in other Rom.
Hi Toneytse, i'm a little bit confused by the following description from you:
3. Check your version and go here (http://forum.xda-developers.com/showthread.php?t=529019) download a downgrade version. (In my case, I will download Modded HBOOT-1.33.2004)
I have exactly the same version of SPL with you, and i found our version is listed there http://forum.xda-developers.com/showthread.php?t=529019 which is HBOOT-1.33.0009 (SAPP10000), why you use HBOOT-1.33.2004 instead of HBOOT-1.33.0009 is it a must to use that version? i thought all the SPLs listed there are all MODIFIED?
Thanks. I am thinking of going back to my original ROM...
after i selected [Alt+B] to backup, got the following errors:
can't mount /dev/block/mmcblk0....
can't mount sdcard
update:
after got these errors listed above, i selected [Alt+B] again, it works!
thanks you ar.... i can backup and restore my rom....
one more think want to know, how can i root my magic(HK)???
cheers mate, brill!
when i type the command - fastboot erase system -w, i get waiting for device. whats wrong?
question. must i change my spl no matter what to be able to use nandroid backups?
jfive74 said:
when i type the command - fastboot erase system -w, i get waiting for device. whats wrong?
Click to expand...
Click to collapse
double check your USB cable and driver is installed, then check your Phone is ready on Recovery model
toneytse said:
double check your USB cable and driver is installed, then check your Phone is ready on Recovery model
Click to expand...
Click to collapse
got it to work. was the spl and i wasn't in fastboot usb mode(w/white screen) but in recovery mode. But thank you.
do you think its possible to swap the nandroid backup data.img from daldroids rom that i have with the nandroid backup data.img from rogers rom and then flash to device? just because i find the daldroid rom not really customised for rogers 7.2mbps data connection. i could be wrong. Please advise. Thanks.
I'm getting an errorm while trying to restore. any ideas? see below.
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>fastboot erase system -w
erasing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
D:\android\tools>fastboot erase boot
erasing 'boot'... OKAY
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>
aussiebuddha said:
I'm getting an errorm while trying to restore. any ideas? see below.
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>fastboot erase system -w
erasing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
D:\android\tools>fastboot erase boot
erasing 'boot'... OKAY
D:\android\tools>fastboot flash system system.img
sending 'system' (73515 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
D:\android\tools>
Click to expand...
Click to collapse
You need to upgrade your SPL first~~
download here http://forum.xda-developers.com/showthread.php?t=529019
toneytse said:
You need to upgrade your SPL first~~
download here http://forum.xda-developers.com/showthread.php?t=529019
Click to expand...
Click to collapse
thanks mate that did it for me.
However, now I have a different SPL than what the phone came with.
How do I restore the original SPL?
thanks.
Thanks toneytse,
Thanks for the detail instruction, I have successfully backup my ROM. I have one question about the SPL. The shipment one 1.33.0009 while the modded one is 1.33.2004/2005. Does it mean 1.33.2004 is newer, or it is just the same thing just that it is modded to make flashing possible?
Hello! If i backup my rom , will it included the software which downloaded from market?
thanks
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
cheers
-Buster
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
At this part:
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
Click to expand...
Click to collapse
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
OMIGHTY1 said:
At this part:
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
Click to expand...
Click to collapse
When in doubt, disconeect all android devices and issue the command without the ID (usually fastboot/adb use the default id when only 1 device is connected.
"fastboot flash system c:\blob"
The erase worked on my TF300t/A700/Galaxy Nexus.
If you are having flashing probs make shure to switch cable and usb ports &/or try a linux to test.
gl
-Buster
Here's the input and output from that:
C:\android>fastboot flash system c:\blob
error: cannot load 'c:\blob': No error
Click to expand...
Click to collapse
Would I need the stock image in the blob folder, or should it be empty? Should I create it at all?
The screen problem is identical to the problem in this post:
http://forum.xda-developers.com/showthread.php?t=1976209
OMG - Thought My Prime was Dead In The Water...Thanks Buster!
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
Was getting the dreaded Option 2 - Unrecoverable Bootloader Error that was supposed to be the ultimate death sign. As a last resort, I tried the steps Buster provided and my Prime is up and running again!
When i turn on tablet, goes straight to recovery, even after have tried rebooting into system, i followed the button combinations to boot into RCK. The version installed of CWM was based in Recovery v6.0.2.3 occurs that after opening CWM immediately below error messages are displayed.
E:Can’t mount /cache/recovery/command
E:Can’t mount /cache/recovery/log
E:Can’t open /cache/recovery/log
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
And now can’t grab any rom in SD card when I’m forced into recovery. I tried with two kind of SD, 1Gb Sandisk, 4Gb Kingston HC-(4). when I try to mount any partition like /data and /sdcard from “mounts and storage” obtain:
Error mounting /sdcard!, Error mounting /sdcard!, Error mounting /emmc!
Also i download android tools and installed adb universal drivers, from recovery mode, If I type "adb devices" shows a proper reorganization.
List of device attached
0123456789ABCDEF recovery
So every time when start up, even without hitting vol+power key, it goes into the recovery mode.when i type "adb reboot-bootloader",it goes power off.Nothing happen.Please help me.
TWRP recovery for Nabi Bigtab 20"
Must have unlocked bootloader
Download:attachment below
install via adb
"adb reboot-bootloader"
"fastboot flash recovery recovery.img"
Compiled by me with help from @aicjofs
I need help getting a fastboot driver to work for this tablet. So far I've had no luck. What drivers did you use?
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
Woah, wasn't expecting to see you here.
Thanks for that guide, had one as well but had since sold it
Thanks - the guide helped me unbrick my Nabi Big Tab 20"
AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to "system" and select it.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".
hexagon_founder said:
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".
Click to expand...
Click to collapse
Glad it helped!
And thanks for the note, yes, priv app is under system, and I forgot to mention that! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10
Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.
I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.
CCrusader said:
I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.
Click to expand...
Click to collapse
CCrusader said:
Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.
Click to expand...
Click to collapse
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10
AlaskaLinuxUser said:
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10
Click to expand...
Click to collapse
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.
CCrusader said:
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.
Click to expand...
Click to collapse
I used Ubuntu 18.04, and installed adb and fastboot from the Ubuntu repository. I did not need any drivers, as Ubuntu Linux was able to talk to fastboot right out of the box. Literally, the above steps was all I did.
Not bashing Windows, but Android runs a Linux kernel, and most Linux distributions can work with it much easier than Windows.
You can download a Ubuntu live CD and install adb and fastoob on your live run to do the job, if you don't want to install Ubuntu on a computer.
Hope that helps.
Sent from my Sony Xperia XA2 Ultra with Android 10
I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.
CCrusader said:
I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.
Click to expand...
Click to collapse
Glad it worked out! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10
I cannot get my WIndows 10 pc to recognize the big tab as an adb device. It is in fastboot mode (Start, Power off, and Recover mode menu) and I have installed all proper adb and fastboot drivers as well as tried using NabiLab and Mehtuus Nabi Root to install any sort of drivers. The tablet will either appear as "Unknown USB Device (Device Descriptor Request Failed)" or as "Fastboot" with the little exclamation mark and triangle next to it.
I have also tried booting into a live linux installation and get the same issue: adb will not detect the device.
I got a 24" paper weight...
I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.
crazytiger1983 said:
I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.
Click to expand...
Click to collapse
I'm also looking for files for the 24" version. Did you figure out what this file was for?
I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.
crazytiger1983 said:
I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.
Click to expand...
Click to collapse
So the file you attached in your post from March is the in focus flash files?
No, this is the one
crazytiger1983 said:
No, this is the one
Click to expand...
Click to collapse
Thanks. I just recently purchased one of these and am waiting for it to arrive. I don't know what state it will be in when I receive it. So what is the file for then from back in March?
tried to post in the venue area but got a pop up saying i had to post here. so, heres the situation.
i have a retail dell venue 7, i dont know the model as i cant boot in to it (thus the problem) i did "not" try to root the device, 1.5 years old, checked some messages, locked it, came back later, it wouldnt unlock, did a hard shut down, went to start it up and it just sits at the dell logo. so heres what ive tried so far.
1. if i power on i get a quick USB logo flash.
2. if i power on with usb cable hooked to pc the USB logo stays on the screen.
3. if i go in to droid boot and try recovery it reboots to the dell logo and just sits there.
im legally blind and am having a bit of trouble getting around here but ive tried the "IntelAndroid-FBRL-07-24-2015"
using the above, if i boot in to droid boot it shows up as "android phone" i have to install the adb driver each and every time (windows 8.1) i dont mind that. the above sees the tablet and even issues commands. the tablet reboots and i get a logo with a hat, but it goes no further. if i hold power up and connect to the pc it shows up as a "CloverviewPlus Device" under intel Soc.
this is what "IntelAndroid-FBRL-07-24-2015" shows when i try to do a "5 cwm" then a "T3"
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: DellVenue7000143194 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.887s]
writing '/tmp/recovery.zip'...
OKAY [ 0.686s]
finished. total time: 1.573s
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.604s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.686s]
finished. total time: 1.291s
target reported max download size of 1322942464 bytes
sending '/sbin/partlink' (349 KB)...
OKAY [ 0.571s]
writing '/sbin/partlink'...
OKAY [ 0.687s]
finished. total time: 1.259s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
(bootloader) Stop partitioning
(bootloader) Stop partitioning
A
FAILED (unknown status code)
finished. total time: 0.635s
---------------------------------------
at which point the tablet reboots, but just sits there with that hat thing.
i dont care if i loose data, id just like to get this tablet back in working order. unfortunitly i have no idea how to do that. im comfortable with the command line but may need a bit of hand holding (i.e. step by steps, ive looked at the wiki but i cant figure it out sadly)
after digging through some emails and finding the service tag, i can now update this to say its a DELL venue 7 3770. and ive still had no luck.
so, i downloaded kernel.tar.gz from Venue_7_3730_CloverTrail_plus/ (yeah i fat fingered the model number above, my bad)
1st sign this wouldnt work? when i unzipped with 7zip i got an error about files all ready existing, not possible since it was an empty folder, but i went ahead any way. installed virtualbox, ubuntu, got that all set up. tried to run from in there and got a boat load of "read only" errors (even though other write/read tests worked fine)
so i figured, ok, lets just keep it "in the box" so to speak, made a folder with in ubuntu, redownloaded said file. used file manager to unpack it only to get an error about "no such file or directory" eh?
so i went over to terminal and tried to unzip it again, this time getting a "not a gunzip file" error, do what?
all of my googling seems to say im hosed any way as every thing i read says you need a good clean copy of /system from your "phone" (what , no one ever does this with a tablet?) to build the rom, kinda defeats the purpose of releasing the source dont it?
oh well, ive tried all i can try and with no one around here pointing me in the right direction, i guess i have a nice paper weight.
As the title says, I (without thinking) did a factory reset from within the settings menu while using a custom rom. My tablet boots and sits on the attached screen. I cannot access fastboot but while on the screen I have ADB access and can send commands. Also, none of the Volume&Power Buttons combinations will work. Please advise..
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggested thread, unfortunately after the "adb shell insmod /bootit.ko" command my tablet simply powers off and does not reboot. I read through the thread and saw that someone else experienced the same but there doesn't seem to be a resolution.
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
JGuinan007 said:
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
Click to expand...
Click to collapse
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
berndblb said:
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
Click to expand...
Click to collapse
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
jmms1124.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/show...2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Thanks to Browndog181 for this great instruction he made.
Good luck to bring back live to your tablet.:
Scenic-3.
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
So you got a little software engineer in the house, eh? :cyclops:
For these little rascals you need Apple devices: Safely locked down so the average user cannot do much damage :laugh:
You can do the buster99 described in the post above, but I would leave that as a last resort.
Sounds to me as if your son formatted something and since nothing exciting happened after typing "yes", he tried pushing some other buttons, interrupting the format and corrupting the partition.
I assume you can still boot into recovery and use it and fastboot is also accessible to you. Correct me if wrong.
Use TWRP's build in file manager to check if you can see the contents of your sdcard. If you can, it was not /data he formatted, but /cache or Dalvik. If so, just format cache, wipe Dalvik and reflash the rom
If /data is not accessible you'll have to format it from the Wipe > Advanced menu. That process takes 1 hour+, so send your son out of the house on a play date or some such....
That you see "md5 not found" probably means the box for "Verify MD5" (or "Check MD5" or something similar, can't remember what the official TWRP had there) is checked on the Install page just before you flash. TWRP will abort the installation if it does not find a MD5 for the zip you are trying to flash if you told it to look for one...
Make sure that is unchecked, then flash the rom.
If none of this works, take screenshots or write down the error messages you get and post them.
Here are pictures of what happens when I try to reflash
View attachment 4004171
View attachment 4004172
View attachment 4004173
View attachment 4004174
View attachment 4004180
Yes, /data and /cache cannot be mounted. Did you format them in TWRP?
Your version of TWRP is pretty outdated. You should update it to 2.8+ at the least, the last version is 3.0.2.
Did 2.7 even support f2fs? Can't remember....
Remember that if you format data you end up with ext4 file system and have to convert to f2fs again.
Sent from my TF700T using Tapatalk
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
JGuinan007 said:
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
Click to expand...
Click to collapse
No man, you have a working recovery now. Fix your problems first, then update the recovery.
BTW, I don't even know if you can properly flash Nougatella with TWRP 2.7. Maybe it's YOU who should be sent to boarding school... :angel:
Ok, so go to Wipe > Format Data, type yes and place the tablet on a high shelf. Leave it alone for an hour plus, this takes a while (and make sure it has enough juice)
Then go to Wipe > Advanced > check Cache and swipe the button. This will take a minute or two
Now go back to the home page, go to Mount and see if it lets you mount data, cache and microSD (check mark next to it). If it does not, reboot into recovery, go to Mount and see if they are mounted now. You are probably ok at this point. If you can mount the partitions you can flash a rom, but I think you should update TWRP first.
I don't believe anyone has made a recovery flashable package for 3.0.2 so flash it in fastboot. If you are not sure how, go to the General section and check out my Beginners Guide - it's all in there.
Once that is done, when you reboot (fastboot reboot), be ready to grab the tablet. Let it buzz once, then push and hold the Volume Down button to get into fastboot again and enter recovery through the RCK icon.
You should now have TWRP 3.0.2 on there.
Now convert data to f2fs (there's another guide in General for that), then flash the rom, gapps and SuperSU.
Enjoy