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
I had the can't mount sdcard issue on my tablet
I read somewhere that you can - erase the command system -. and so on. The boot-related files would be preserved
Unfortunately I have now only the acer logo and the boot loader on the screen.
When I press power and volume, nothing happens. Is there any possibility to rescue the Tablet?
I can just connecting and sending commands via usb and aio toolbox.
Please help me, my records from the study are in this tablet.
OK, lets summerize:
Tablet Acer 510
something happen - what does you've done?
I can just connecting and sending commands via usb and aio toolbox.
Click to expand...
Click to collapse
What is the AIO Toolbox? I didn't know....
If you've connect the Tablet on the PC, could the PC know the Tablet? Does you've access to the Tablett via adb ? Does the Tablett stopped at this point or it is in a reboot loop?
If you've an access via adb, you have the possibility
a) safe you work on PC
b) restore the 3 *.img on your tablett
If you need the 3 img files, I can give you a link of my 3 files (after root and NO-AD installation)
I tried this
Yes i can connect to pc by manipulating the lock screen button while starting with volume and power button.
Then i can send commands like this "fastboot oem unlock" or this "fastboot flash recovery recovery_nothrills.img"
I tried to send the nothrills image again, and it accepts the image and says image receyved but doesn't help.
Please can you mention what i have to do now.
Did you get my private message
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
farris said:
Isn't it possible to mount the sdcard in ADB, and then pull the files you need?
In that way you have your records back and you can flash stuff without the fear of losing your files.
Click to expand...
Click to collapse
I can connecting via acer fastboot interface
Please can you tell me how is the command to connect sdcard in adb mode and where cani get the files and where have i need to drop it
Sorry, iam a very beginner
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
From what I have gathered on your thread on the other board you have erased your /sdcard partition
I believe CWM needs /sdcard (If I remember right, it says something to this effect when booting to CWM)
1) Try to flash the stock recovery from NoThrill's thread http://forum.xda-developers.com/showthread.php?t=1866378
2) put a stock ROM on an external SD card (rename to update.zip) http://forum.xda-developers.com/showthread.php?t=1897791
3) boot into recovery
4) keep your fingers crossed that it will install
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
ercuem said:
Can i push files in acer fastboot interface mode
I think i'd erased the bootfiles for the bootloader of nothrills boot image
i can just connect in fastboot interface mode and can sending commands
Click to expand...
Click to collapse
Should be:
fastboot flash boot [file]
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
ercuem said:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot flash recovery boot.img
sending 'recovery' (3970 KB)... OKAY [ 1.275s]
writing 'recovery'... OKAY [ 1.410s]
finished. total time: 2.686s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot reboot
rebooting...
finished. total time: 0.427s
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
i tried what you mentioned, unfortunately no success.
Click to expand...
Click to collapse
Where did it go wrong?
Did you boot to recovery? (Vol- + power)
YEAH
a little success
I put updare.zip on external sd
Used this command "fastboot flash boot boot.img "This is the stock kernel of nothrill"
And now i got:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Now it stays on this state until 7 minutes an nothing happens
What boot.img did you flash?
Randomwalker said:
What boot.img did you flash?
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/showpost.php?p=31137321&postcount=1
Are you having issues with the ThrillsKernel (freezes, reboots, etc.)? Download the Acer kernel below:
Acer original kernel (mirror) (mirror)
(MD5 for the .ZIP file: b6e4f3fed3c96468ee25a0c3a8925433)
Flash this from the Recovery and wipe dalvik-cache. Note: This Acer kernel will only work with the ROM in this thread, do not attempt to use it on other ROMs!
In this zip is a boot.img and a directory called Meta.inf
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Randomwalker said:
OK, so that would be a stock kernel.
Can you try to flash the whole ROM via fastboot?
- copy the update.zip to your fastboot directory
- fastboot update update.zip
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>fast
boot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
D:\eigene Dateien\Downloads\ACER_AIO_TOOLBOX_v2.3.0\ACER_AIO_TOOLBOX_v2.3.0>
I USED THIS STOCK ROM
OS_Acer_RV28.RC04.EMEA.DE_A40I_A.zip
But you did unzip it first, right? Not just renamed the download to update.zip?
Randomwalker said:
But you did unzip it first, right? Not just renamed the download to update.zip?
Click to expand...
Click to collapse
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
Yes unfortunately i'm getting the mentioned message.
Thank you for helping me
shall i try "fastboot boot recovery_nothrill.img?"
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
shall i try "fastboot boot recovery_nothrill.img"
Click to expand...
Click to collapse
Definitely, give it a go! I thought you already tried that.
Randomwalker said:
No worries, maybe someone more knowledgeable will come around . Unfortunately I no longer have an A510.
So, you currently are on stock recovery and it hangs after: "Booting recovery kernel image", right?
Maybe we really need to reconstruct /sdcard... but I have no idea how.
EDIT:
Definitely, give it a go! I thought you already tried that.
Click to expand...
Click to collapse
unfortunately no success, i got the same message:
erasing cache before sd update...
sd update command: recovery
update package=sdcard: update.zip
Booting recovery kernel image
Where can i get an update zip, which it will accept for update?
I got the exactly the same message as attached as jpg and pdf.
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.
Guys, I already looked everywhere and I can't fix it. It started after I updated my OS to 5.0.1 (using a stock rom). But there was some problems at the camera (didn't save the photos) and didn't open the sound recorder (for WhatsApp). I think a simple Fix Permission would help me, but I was dumb and I WIPED EVERYTHING. Including the OS...
I have TWRC v2.8.0.1, the device connects with my PC (Windows 8.1 64-bits), I already tried A LOT of tutorials (like installing Android USB Drivers, Motorola USB Drivers, ADB Sideload) nothing works. The "new" thing is: my computer don't even recognize the Android anymore (it just makes the sound of connecting a device).
I tried:
1- adb kill-server/start-server
2. re-installing USB drivers
3. re-installing Motorola Device Manager
The real problem is simple: I know how to fix the OS. I just need to move the TWRP backup to my internal storage. But I don't have a SD Card and my PC doesn't recognize the phone (so I can't access the internal storage and I can't "push" the file via ADB).
There is hope? Do I really need to send my device to repair?
The device is Moto G (XT1069). Is Brazillian, so is dual sim + DTV (but I don't use the TV thing).
BTW:
I also tried to flash via mfastboot (never knows...). This is what shows:
C:\Users\Yeltsin\Downloads\ADB+Fastboot>mfastboot flash ./sdcard1 "Stock 5.0.2
Lollipop XT1069.zip"
target max-sparse-size: 256MB
Invalid sparse file format at header magi
Sparse-Flash is enabled!
sending sparse './sdcard1' (262140 KB)...
OKAY [ 9.102s]
writing './sdcard1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 9.138s
There is two sdcards (I sent to both, unsucessful). Tried to do the same at the recovery mode and...
C:\Users\Yeltsin\Downloads\ADB+Fastboot>mfastboot flash ./sdcard1 "Stock 5.0.2
Lollipop XT1069.zip"
< waiting for device >
My Windows detects my phone (showing the option to Eject XT1069) but adb/fastboot don't.
C:\Users\Yeltsin\Downloads\ADB+Fastboot>adb devices
List of devices attached
So:
I'm without OS, adb/fastboot doesn't work, I don't have a SD card (I'm currently ordering a 16GB microSD, just in case). Can someone help me?
Just a little update:
C:\Users\Yeltsin\Downloads\ADB+Fastboot>mfastboot devices
0434643185 fastboot
mfastboot is working, but I can't flash the ROM (is a stock ROM. OS 5.0.2) OR I don't know where I can flash it.
So I fixed. After many many many tries.
What I did was crazy and I don't know if it's the correct way to do it. But I extracted all content from the zip (it was not the default rom, it wsa a 5.0.2 rom for XT1069) then I pushed every single file via adb push directly to the TWRP folder, example:
C:\Users\Yeltsin\Downloads\ADB+Fastboot>adb push system.ext4.win /sdcard/TWRP/
BACKUPS/0434643XXXXX/1970-01-20--01-01-33
After this, I made a restore using the folder (instead of a specific file). The first time I tried, I got a black screen. So I said: I'll try to wipe both cache folders. Restarted, got a black screen again but my computer was getting the driver. After a few moments I received a Windows notification asking what I want to do with my phone. I waited a few seconds and then: it worked.
Don't know if this was the best solution, but worked. So if you are having the same problems that I had, hope this will fix it!
Nevermind. Didn't worked and now isn't showing at fastboot, mfastboot or adb.
It loads the motorola globe animation but 1 sec later shows only a black screen. Tried to wipe dalvik cache and everything, without success....
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.