Related
Hello!
So, this is my first post here at XDA, so bear with me if my question has already been answered somewhere else. If so, pretty please point me to it and I'd be forever grateful, 'cause I really have searched for it without really getting somewhere. Of course, that might because I'm a real beginner at this and just cannot patch the bits and pieces of info together properly.
Background to problem
I have a TF300TG. I have unlocked the bootloader via official channels, and flashed CWM 5.5.0.4. Then I flashed CM9 stable, and got stuck in a bootloop. This was solved by a wiping of cache/dalvik and maybe a factory reset (don't really remember). Anyway, i managed to boot is, and realized that i could no use the 3G functions. Stupid i know, should have read more about it, but I finally realized that there are almost no custom ROMs for the 3G version of this transformer. So, what I now wanted to do was flash to something that would work.
I've read that it's only stock or the Hydroponic roms that are available for the TG-version, so I chose to try the Hydro. However, I read somewhere that I should use TWRP instead of CWM to flash, due to some kernel update-thingies, that CWM would not be able to do. If I understand it correctly, I needed to update the kernel back to the stock kernel, since I came from a cyanogenmod with a different kernel (?).
Flashing TWRP via fastboot was easy, and then I flashed the hydro TG rom from TWRP, which gave me bootloops again. Now I could not solve the bootloops via wiping cache or factory resets, nothing solved them. I tried reflashing several times, and also tried flashing after reverting to CWM again. This flash also worked, but I still got the bootloops.
Where I'm at at the moment
I have tried to flash the stock ROMs from Asus, both 9.4.4.40 and 9.4.4.28. However, they do not flash at all from recovery. I get a Status 7 error no matter if I use CWM or TWRP. And yes, i have extracted the downloaded .zip once, before flashing.
I have tried the fastboot -i 0x0b05 update update.zip command, but only get this:
Code:
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
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
[COLOR="Red"]Failed to process command flash: system error(0x170003)[/COLOR]
I have wiped system, cache, data etc from fastboot, so the pad is pretty much clean from everything except recovery partition. Maybe there's somehing wrong with the partitions, 'cause when I try to format them - system for example - i get the following:
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
My questions are these:
How do I flash back to stock, with a stock kernel, if the above things have not worked? Is there a way to flash via ADB that could work, instead of recovery or fastboot?
What's the deal with sometimes flashing the .zip files, sometimes .blob files, and sometimes .img files? I'm confused.
What does the status 7 error mean? Don't really get it from what I've found in my searches.
Can i somehow use the /staging partition to install? If so, how do I push the file there, and which file exacly should I use?
If anyone has any suggestions, I'd be forever grateful. And remember, I'm not an experienced android tinkerer, I have only a Desire HD with CWM and CM7 since before, which was done pretty much by following step-by-step guides and not much understanding from my side. ;P
If you need more info, just let me know.
Cheers!
Niklas
Update:
I managed to flash the hydro rom via CWM. It is still stuck on the Nexus 7-like bootanimation, though. Can't understand why it does not boot all the way into the OS. Ideas?
Update 2
I followed the tip here., and it seems to work. I managed to flash the non-3G version of the hydro rom, and could boot into the OS. Then id somehow worked to flash the 3G version, without any wipes. This time it said "updating android" and then booted! It does not recognize the SIM card, though, but I'm getting more confident that I will be able to fix this now.
So, I have been able to update to the Hydro rom, and can use the tablet, but since 3G is not working in those ROMs, I want to revertto stock ICS. However, I still get the Status 7 error when trying to flash the stock zip from Asus siste. Have tried .40 and .28 WW SKU, none of which is working. Cannot flash the roms in either TWRP, CWM or via fastboot.
Does anyone know what the problem could be? Can it be that the files are not really base roms, but only meant as updates to previous installs? If so, where can I get a base stock ROM?
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
naelme said:
Nah the work as full recoveries. What boot loader version do u have?
You can reflash stock kernel, by flashing stock ROM through fast boot.
Click to expand...
Click to collapse
Hey, thanks for answering. Where do I see the bootloader version? Kernel version is 2.6.39.4-00003-gafee6c5 [email protected] #1
I tried flashing the stock rom via fastboot, using the blob inside the update package
Code:
fastboot -i 0x0b05 flash system blob
I've also tried flashing the ZIP in CWM and TWRP, and I have unzipped the downloaded zip one time as the instructions say.
When you load in recovery mode it tells you boot loader 9.1 or 10.4
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ah, OK. It says bootloader (2.10 e) released by "WW-epad-9.4.4.40-20120704" A03.
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
naelme said:
I would try to load jb..
Just visiting the threads with the custom Roms for this device makes my device brick...
I'm sure you can bring it back, another thing you can do is let the battery in the unit fully die then try.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, then I just have to wait patiently for Asus to release JB for the TG-version. Had hoped to be able to solve it beforehand, but hopefully that will finally solve it for good.
Thank you for your time.
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
hakkukakt said:
hello
after this
Extracting the blob from the .zip and using fastboot -i 0x0b05 flash system blob does not work either, and outputs the following in the cmd prompt
Code:
D:\Mobil\Android\TF300TG\roms>fastboot -i 0x0b05 flash system blob
sending 'system' (796653 KB)...
OKAY [140.798s]
writing 'system'...
FAILED (remote: ()
finished. total time: 141.204s
and the following on the tab
Code:
Failed to process command flash: system error(0x170003)
=> that the error arrive sometime ... try to do one again and that pass, i have the same error and on the second test i have the success
see link here => http://forum.xda-developers.com/showthread.php?t=1750861
that ok if you dont have go on JB update before ....
Click to expand...
Click to collapse
too many details, none of which I was looking for
but here's my questions/recommendations
1. Are you on ICS? If yes what version of TWRP did you install there's 1 for ICS and 1 for JB
I recommend making sure you've installed TWRP for ICS and use TWRP to flash the official ICS firmware from the asus website
once everything is confirmed working then install Hydro for ICS TF300TG
2. If you're on JB. Unfortunately there is currently no going back to ICS. Also the Hydro JB Rom to my knowledge currently does not suport TF300TG, and I'm not aware of any ROM for TF300TG that is running JB
I recommend making sure the correct version of TWRP is install then, use it to flash the official ASUS ROM
hello
yes i'm on ICS
1. i use CWM
hum that's not me that have problem
i answered on the last post ...
sorry for my bad english, i speak normaly in french
Hi nikwid,
thanks for the detailed description!
Here's my story: my TF300TG is on stock 9.4.4.22, and I can't update to stock 9.4.4.28 nor 9.4.4.40. It's working normally, except the ugly screen flicker in the left lower corner and WIFI reconnect delays. The latest ASUS update promises to fix these issues, that's why I really would love to flash it.
History
Unlocked device
Flashed Root + CWM
Everything went flawless up to this point. The TF300TG is still on stock ASUS system.
Current situation
When flashing with CWM and TWRP I get:
Code:
Finding update package...
Opening update package...
Installing update...
script aborted (no error message)E:Error in /sdcard/WW_epad-user-9.4.4.40.zip
(Status 7)
Installation aborted.
fastboot outputs (no matter if flashing to system or staging):
Code:
writing 'system'...
FAILED (remote: ()
finished. total time: 142.102s
I don't dare to try `format` with fastboot, as I don't want to brick the Transformer.
I would be happy for any hint how to successfully update from stock to stock?
See you,
Berny
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
gaga-man said:
I successfully installed WW_epad-user-10.4.3.9.zip by editing META-INF/com/google/android/updater-script in the zip and removing everything except the line
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
Later on I installed the other two packages (SAM_6260_ALL.fls and TF300TL_AMSS.MRP) one by one.
After this I successfully installed WW_epad-user-10.6.2.3.zip by just removing all "show_progress" and "set_progress" lines in the updater-script.
Finally the original WW_epad-user-10.6.2.6.zip installed without editing it (TWRP 2.5.0.0).
Now I can even check for new updates using the tablet, this didn't work since installing root and CWM
HTH!
Berny
Click to expand...
Click to collapse
By the way, I think that deleting all lines in "META-INF/com/google/android/updater-script" except the following one
Code:
assert(package_extract_file("blob", "/tmp/blob"), write_raw_image("/tmp/blob", "staging"),delete("/tmp/blob"));
will do the same as extracting the "blob" file and flashing it with
Code:
fastboot flash staging blob
---------- Post added at 12:06 PM ---------- Previous post was at 12:04 PM ----------
forcemaker said:
I seem to be stuck in the same situation.
I cannot install "WW_epad-user-9.4.4.40.zip" from within TWRP2 (2.6, 2.5 and 2.4 tried) and I cannot do "fastboot" as I get the same error messages as the others reported here.
This thread is old, but maybe today someone knows the answers?
Click to expand...
Click to collapse
Current status: I can install an Asus Stock ROM by extracting the blob file and flashing that with
Code:
fastboot flash staging blob
The fastboot command never reports finishing (in this situation), so I stop it by pressing Ctrl+C in the console window, but only after giving it enough time, e.g. 10 minutes, to finish.
Code:
sending 'staging' (800933 KB)...
OKAY [135.726s]
[COLOR=Red]writing 'staging'...[/COLOR] [I](here it stays forever)[/I]
From this moment on no fastboot commands (e.g. "fastboot --reboot") are accepted until I manually reboot by pressing the "Power" button for 10-11 seconds . During reboot there will be a progress bar underneath the ASUS logo, which moves to completion within 10 minutes. After that the system reboots and the clean Stock ROM is installed.
I tried this on my TF300TG by
resetting it by "full wipe",
then via nvflash to an Android 4.0 Bootloader (if you are on a 4.0 Bootloader, go here: http://forum.xda-developers.com/showthread.php?t=1894867 !!!)
and with the latest Asus Stock ROM
4.0.3 (TF300TG: WW_epad-user-9.4.4.40.zip) and
4.2.1 (TF300TG: WW_epad-user-10.6.2.6.zip).
for TF300T (without 3G) there are different Asus ROM version numbers, you can find them here: http://forum.xda-developers.com/showthread.php?t=1697227
Remember, going to Asus Stock ROM 10.6.*.* will give you Bootloader for Android 4.1 and 4.2 which are not downgradeble to 4.0 unless you already have the nvflash backup files created with 4.0.
Hello,
I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.
Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).
It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.
Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:
adb remount (got message: succeeded)
adb shell rm /system/recovery-from-boot.p (message: no such file or directory)
adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)
Now I have no idea what else to try. I'd like to get back to stock ICS.
edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?
Hi,
It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader , if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:
Wish you the best luck
Any problems please give me an up!
​Thanks for your reply!
I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.
Here's what I did in detail when reverting to stock:
I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so?
I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).
Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.
Yea, it looks like something is going wrong there...
Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...
Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.
Good luck
Thanks! I will give that a shot and post the result here.
By the way, that is one thing I read about and didn't dare to try yet: formatting system.
From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).
When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries , it may turn out without risking
I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.
Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:
Code:
>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s
>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s
Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:
Code:
>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s
Worked fine apparently, then continued from there as normal:
Code:
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:
Code:
Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)
Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?
Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time , I will search a little and see what I can do for you.
My mistake on posting, I did flash boot.img before that, corrected my previous posting.
Now I am stranded. And I can't even turn off the device on boot screen.
edit: rescued it, thanks to this posting:
Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).
Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Landorin said:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Click to expand...
Click to collapse
Glad you made it
Congrats!!
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
dhastings said:
I have an Asus TF300T paperweight!
I started out to root my tablet and load CWM. I unlocked it, install TWRP v2.2.2.2 as I read in a blog with instructions on how to root this tablet. I loaded a CWM ROM, can't remember not which. It didn't load correctly, and kept rebooting. I got into the screen that gives the following four options:
1. RCK
2. Android icon
3. USB icon
4. Wipe data icon
Of course, thinking I would start over and try again, selected Wipe Data. Stupid, I know.
Now, my tablet only boots into TWRP. It won't mount anything; of course, since I Wiped Data, there is nothing to mount. I have tried and searched, to no avail. I can see the tablet in Device Manager, and managed to load the Naked Universal Drivers. Now it shows up in Device Manager as Asus Eee Pad Slider ADB Interface. I can issue the command - adb reboot - and it will reboot, but I can't get it to do anything else meaningful with my meager experience.
Any help would be greatly appreciated. I would like to get this working and give it to my son, as I have already purchased a replacement for myself.
Thank you.
Click to expand...
Click to collapse
Stop.
Find buster's post and thank him.
And make sure you keep twrp up to date. You have an extremely old versioin which is why you bricked.
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!
cheers
-Buster
sbdags said:
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!
cheers
-Buster
Click to expand...
Click to collapse
thanks
i was stuck on cwm
could not acess to sd card
followed those steps and there it goes
working again
thanks a lot!
submancm
So I saw that timduru posted the files for Nougatella 7.1 and couldn't wait to join the club. It has been a while since my TF700T has been upgraded. I had TWRP 2.8.4.0 so I wanted to upgrade to the latest version. Mistake #1!!!! I went to TWRP and got the img file put in on my sd card and installed in through the TWRP recovery. Now I get the RED unrecoverable bootloader error 0x000000. I can't get into the recovery but the tablet boots up into KatKiss without issue. I tried the TWRP app as well with no luck. I also can't get fastboot with adb fast boot working.
Windows 10 32bit
Asus Sync installed
Minimal ADB and Fastboot installed
USB debugging checked in settings
Any help would be appreciated.
Thank you.
My apologies I just saw that this is in the TF700 General Thread not the Help and Questions section. Moderator is this something I can move or do you need to do this? I did a quick search and nothing came up, but also having IE issues loading this site right now. Again thank you all!
It took a good 8 hours but I was finally able to get my tablet up and running. I took the advice of several posts and used their concepts to find the solution.
No ADB/Fastboot issue. I uninstalled all instances of ADB and all the drivers that referenced the device. I also removed Asus Sync.
Post by Accord281 [solved] Need Help: Can't get ADB to recognize device, there was a reference that people had good luck with the Google Driver. I installed Android Studio with SDK manager. I went in and then installed the Google Driver as well as the SDK manager for the stock ROM version (JB).
This still didn't work, so I reread the post and several other as well. I noticed that the recommendation was to set the USB connection to Picture not File. So I did this and ADB was working. Problem #1 checked off.
TWRP error was next. In the post by kansasboy001 Help Unrecoverable bootloader error. He posted a solution form "Buster" which worked spot on. See below.
This is the ONLY solution for this problem, worked great for me.
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!
cheers
-Buster
Finally I was able to flash TWRP 3.0.0 in ADB. I also followed the post from lj50036 [twrp 2.6.3.2] [read me]. This seems to still be an issue with TWRP and the TF700T. I followed the code and it took less than 10 mins to format data.
Thank you to timduru as well as I am enjoying your build as we speak.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk