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.
Related
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 just spent about 5 hours reading threads looking for an answer to this problem. I have seen the question asked twice but there was no response either time.
OK, I have a TF300T with ICS. I unlocked it with the tool provided by ASUS (v7). I set up adb and fastboot and used the ASUS drivers.
On the 1st step [ fastboot -i 0x0b05 flash staging ebtblob.bin ] I have no problems.
On the 2nd step, though [ fastboot -i 0x0b05 boot nvfblobgen.img ] fastboot shows :
sending 'boot' (4588 KB)...
OKAY [ 0.796s]
writing 'boot'...
OKAY [ 1.951s]
finished. total time: 2.753s
but the device never reboots. I tried rebooting through fastboot, but nothing happened. I rebooted manually but the tablet shows the ASUS logo for a few seconds, then reboots. This happens over and over. The little spinner that used to be at the bottom of the ASUS logo never appears.
I can boot back into fastboot, but I can't get into the stock ROM to save the files generated by nvfblobgen.img.
Any help would be greatly appreciated.
Update
OK, so I managed to get the nvfblobgen.img to load properly and reboot the tablet by uninstalling the Asus bootloader driver and installing the Universal Naked driver instead. Then I used fastboot to install CMW. The tablet is still in a boot loop, though.
In the morning I'm going to try to flash a stock ICS firmware with the hopes that it will overwrite the bootloader (even though it booted just fine with the androidroot bootloader before I attempted to write the nvfblobgen.img).
I have no Idea if the bootloader is the problem, but I don't know what else to try.
If anybody see's this tonight and has any advice I'll try it before trying to flash the stock ICS firmware.
Update [partially solved]
OK, just in case anybody with similar problems is watching this thread, I'll let you know where I'm at.
I tried to use fastboot to flash the blob from the official ASUS 9.4.3.29 US firmware. It didn't work, I got an error that adroid-info.txt was missing. Next I tried using the CWM recovery I put on with fastboot to flash the same firmware. Since I could not boot into the OS, I had no way (that I know of, anyway) to put the zip on the internal memory. I instead put it on a micro SD card. This didn't work, either. I could not get CWM to recognize the external SD card.
So, I downloaded and flashed TWRP for ICS v 2.6 (i think, it was the latest version). With this recovery I was finally able to see the external SD card, but it wasn't showing the zip file that was on it. I had to update the partitions before being able to see the zip. Then I installed from external SD.
Now I have a working tablet again!
Now, back to square 1. I am going to read more stuff, then try to get nvFlash on this tablet.
Tried to update to CM 11 / 4.4 KitKat and got "unrecoverable bootloader error"
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
You can read this to see if it helps..good luck..:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2528313
ANDROiD_eKa said:
So I messed up big time. Trying to update to the new unofficial 4.4 OmniRom and had to update TWRP from 2.5.0.0 to the latest 2.6.3.1 in order to flash the new 4.4 ROM but it kept giving me an 'set_metadata_recursive'. So I used the version provided and then used Flashify app on Google play (mistake) to flash it (it said that it installed successfully). Then when I reseted to recovery it got corrupted. So I thought I installed at the wrong place and installed as a zip, recovery and IMG. (Bigger mistake). Now it won't load at all on any OS and boot loader and recovery are corrupted.
Can some one help me? Please o)v_v)o
Click to expand...
Click to collapse
Sorry, but after reading your post 4 times I still have no idea what you actually did.....
If you still have access in ADB (since you can't access the bootloader??) the link LMK gave you may save your bacon.
If you don't have any kind of access: ADB or fastboot and you do not have nvFlash blobs - sorry, you bricked.
Can I access fastboot when I get the menu at RCK / Android / Wipe? Because if I click con any of these its says that bootloader is corrupted.
What's the Command to fix TWRP using a computer / or other Android device?
ANDROiD_eKa said:
Can I access fastboot when I get the menu at RCK / Android / Wipe?
Click to expand...
Click to collapse
Does it say something about fastboot in the upper left corner?
ANDROiD_eKa said:
What's the Command to fix TWRP using a computer / or other Android device?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Thanks _that for the advice...:good: You are the expert in this area... I am done with my job to bring you in here for helps..haha...
_that said:
Does it say something about fastboot in the upper left corner?
fastboot flash recovery twrp.img
(or whatever name your TWRP blob has)
Click to expand...
Click to collapse
Yes it says
Code:
Starting Fastboot USB download protocol
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
ANDROiD_eKa said:
Ok flashed TWRP via fastboot but device freezes?
Code:
C:\Documents and Settings\HP_Administrator.CEREBRO>fastboot -i 0x0B05 flash reco
very twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.563s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 5.016s
It still won't let me boot to TWRP saying an "unrecoverable bootloader error" occured. Is there something I can do?
Click to expand...
Click to collapse
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
LetMeKnow said:
You can use the link on my previous reply and read post #3 by _that to clear your misc.. You need to use "dd=" command erase your mmcblk0p3 partition. Please be carefull when you use it and make sure you erase the right partition. Anything after "of=" is you write to....
Please ask more question with _that before execute that command...Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
berndblb said:
I think this may be different. Clearing the misc partition solved the problem of force booting into recovery.
Here he can't get into recovery... Not looking good.....
Click to expand...
Click to collapse
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
LetMeKnow said:
The fastboot write is successfull but the recovery is not updating.... You and _that may have the answer..
Click to expand...
Click to collapse
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
berndblb said:
Pff - just yesterday I used fastboot to push TWRP 2.6.3.1 and it said successful. TWRP still shows version 2.6.1. - so what do I know???
Click to expand...
Click to collapse
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
LetMeKnow said:
I think that his/her bootloader is still partly function because the fastboot is running.. I don't want to give any advice unless I know for sure that it works. If someone have a better knowledge on the bootloader and recovery, it can be up and running again, I hope...
Click to expand...
Click to collapse
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
berndblb said:
As long as there is fastboot, there is hope
http://lmgtfy.com/?q=fastboot+boot+image
Click to expand...
Click to collapse
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
buster99 said:
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
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
ANDROiD_eKa said:
Hey guys thank you for your help. I had learned that I encountered a softbrick. I got my tabby fix reading ]Unrecoverable bootloader error(0x00000000) Which led me to Softbrick - possible solution for you
Followed these steps...
Although I admit I had to these steps several times as it initially wouldn't somehow it wiped out that error. After I had fix that bootloader error I used fastboot and installed TWRP 2.6.3.1 and now life can continue.
I also followed steps right on getting CM11 to work by using CWM Touch this time to install and it looks jelly. ?! Love these 4.4 KitKat emoticons, thanks again for your help and interest in me ?
Click to expand...
Click to collapse
Buster99 deserves a medal or something for this post. Dozens of people have recovered from a brick using his method!
Glad you got it going!
So, i have noted a increased number of threads about people who have soft-bricked their phones downgrading from 4.4.4 GPE after recieving the OTA, since it includes a new partition table and there's no firmware image yet.
Worry not, i have found a solution for your problem. This method only let's you use custom ROMs (sadly), but it's meant to be a temporal solution while we wait for a 4.4.4 GPE image anyways.
So, without further ado, here's my fix:
You will need:
-The good ol' Android SDK
http://developer.android.com/sdk/index.html#download
-Motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
-A custom recovery. I recommend TWRP, since is the only one i have tested.
Official TWRP Images for Moto G: http://techerrata.com/file/twrp2/xt1032/openrecovery-twrp-2.7.1.1-xt1032.img
-The gpt.bin from 4.4.4 (this is the partition table)
I extracted it from the OTA file and uploaded to my Dropbox: https://dl.dropboxusercontent.com/u/82658555/gpt.bin
-A custom ROM of your choice (obligatory) + GApps (optional)
What to do:
Once you have the Android SDK, decompress the folder sdk/platform-tools in a place of your choice.
Inside this folder, put gpt.bin, the custom recovery image and the ROM and GApps zip's.
Start your phone on fastboot. Connect it.
Inside your decompressed platform-tools folder, hold shift and right click inside the folder. Select "Open command window here".
Make sure your phone is properly connected by typing "fastboot devices" (without the quotation marks). The command prompt should show your phone serial number.
Now we start the real deal. Fist of all, flash gpt.bin using this command:
fastboot flash partition gpt.bin
Make sure it ends on "OKAY"
Now, flash the recovery
fastboot flash recovery nameoftherecoveryfile.img
Once this is done, enter recovery using the fastboot menu on your phone (use Vol- to highlight "Recovery", and then press Vol+)
Now your phone should boot on recovery mode. If you recieve an error like "Can't mount /system/", don't worry, this is normal (there's no system partiton yet, after all). Now you can use ADB command with your PC. Once again, to be sure everything is connected properly,tyipe on the console:
adb devices
Once that is done, it's time to give your phone the custom ROM, so you can flash it. Type (or copy/paste)
adb push NameoftheROMfile.zip /sdcard/ NameoftheROMfile.zip
If you have GApps, do the same for those
adb push GApps.zip /sdcard/ GApps.zip
Now you can finally disconnect your phone from the PC! You are almost done, select "Install" in your recovery, and flash your ROM zip, then the GApps if you have them.
Once it's done, you can reboot to system.
And you will have a working Moto G again!!
Enjoy it, and don't brick it again
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
maurocds said:
the guide isw missing some info (like enter flash sideload on recovery)
and that weird command push does not work, i have to use other command
i managed to install another rom after being bricked but still that rom won´t start, i have to try another
still thanks a lot
i did not download android sdk, i have my folder with adb files
also when i am in recovery, i type fastboot devices and nothing happens, but still the recovery could receive the file
Click to expand...
Click to collapse
From my experience, you don't have to enter sideload mode in recovery to push a file, sideload mode is for pushing OTAs. And remember, the ADB push command requires you to put the exact name of the file to transfer twice, that could have failed for you.
You can't use fastboot devices on recovery because you can only use ADB commands in recovery, you were supposed to use "adb devices".
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
masa86 said:
Or you can restore 4.4.2 nandroid backup using recovery if you made one. But after that you need to flash correct baseband.
Click to expand...
Click to collapse
Not many people do NAND backups these days.
Sad, because they're really useful, and there wouldn't be as many "HALP BRICKED PHONE" threads.
It Doesn't work only say failed xD
Fresroqir said:
It Doesn't work only say failed xD
Click to expand...
Click to collapse
Care to explain what failed?
tatazeuz said:
Care to explain what failed?
Click to expand...
Click to collapse
The install for the custom rom and gapps
Fresroqir said:
The install for the custom rom and gapps
Click to expand...
Click to collapse
What error did you receive? Did you flashed gpt.bin correctly?
tatazeuz said:
What error did you receive? Did you flashed gpt.bin correctly?
Click to expand...
Click to collapse
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Fresroqir said:
i just received failed at twrp recovery and how do i flashed gpt.bin right because it say okay.
And what does gpt.bin actually? (i am a noob)
Click to expand...
Click to collapse
got.bin is the partition table of the Moto G. Its the file that indicates to the phone the size, name and number of partitions it should have.
So, I know TWRP said in red letters Failed, but I'm interested what is the specific error, what did it said on the command prompt of TWRP.
Error flashing zip sdcard pa falconzip
and then there comes this updating partitution details and do i need to put the rom twice in the cmd?
and do i need a cutom rom with 4.4.4????????
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Fresroqir said:
and do i need a cutom rom with 4.4.4????????
Click to expand...
Click to collapse
maurocds said:
yes, exactly what rom did you use to recover??????????
paranoid did not work, installed fine but stuck at logo loading
Click to expand...
Click to collapse
I used the latest version of PA + Stock GApps
Thanks!
Edit: Nope... Still same problem. Looks like the gpt file flashed but everything else is the same.
It still doesn't work for me i got th whole time failed and i don't know what i need to do ;(
It says: Z:\New folder\Android>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.372s]
finished. total time: 0.399s
is that good?
EDIT:it looks that sideload works and not that push command
EDIT: nvm i am stuck at bootanimation
EDIT: this wont work it says failed all the time at twrp
I'm kind of confused. Why couldn't people downgrade and go back to stock by reflashing all of the files from an older stock image, including the motoboot and gpt? I would think this would work...although with people saying that they are unable to downgrade I'm not willing to try upgrading to 4.4.4 myself.
What errors are people seeing if they try to flash gpt and motoboot from, say, 4.4.2 stock or 4.4.2 GPE?
-- Nathan
not work for me..
every recovery stay on black screen and return vibration on touch screen
:/
help > http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
i think this fix doesn't work because i can only sideload my roms and gapps xD
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