Database Users

[Q] Fastboot Device not Recognized

I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"

Just to make sure, did you put your device in fastboot mode before flashing image?
What does "fastboot devices" return?

borodin1 said:
Just to make sure, did you put your device in fastboot mode before flashing image?
What does "fastboot devices" return?
Click to expand...
Click to collapse
Yes, I was in fastboot. It shows my options in fastboot as (Bootloader, Reboot, reboot bootloader, and Power Down). When I input fastboot devices this is what returns.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Brian>cd..
C:\Users>cd..
C:\>cd AndroidSDK\tools
C:\AndroidSDK\tools>fastboot devices
C:\AndroidSDK\tools>

ihidbehindmusic said:
I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"
Click to expand...
Click to collapse
Is your S=OFF?

My s=off. Otherwise I would get an error saying that the command is not allowed I believe. But yes, s=off.

ihidbehindmusic said:
I was trying to flash a new splash screen for my phone and I was getting the error below. I got a similar error when trying to flash a new kernel earlier this week. I always get the "FAILED (status malformed (1 bytes)) finished" error.
I have been searching for about three hours for a fix to this problem to no avail. Right now I'm thinking it could be my drivers, but I can't find HTC Sync for the MT4G. Also, I can use ADB and my phone is recognized there, which made me think it was not my drivers. Ugh, I'm just so confused.
Here is the error:
"C:\AndroidSDK\tools>fastboot flash splash1 rootedmytouchsplash.img
sending 'splash1' (750 KB)... FAILED (status malformed (1 bytes)) finished. total time: 0.021s"
Click to expand...
Click to collapse
fastboot.... you're doing it wrong... I would be glad to help, but troubleshooting over forums is annoying. hit me up on aim, yahoo, msn, gtalk, IRC, etc

I would also be hugely interested in a solution or fastboot instruction sheet. I have similar problems on my 4G trying to flash to stock Glacier 2.2.1 (post OTA).
Thanks!

ihidbehindmusic said:
Yes, I was in fastboot. It shows my options in fastboot as (Bootloader, Reboot, reboot bootloader, and Power Down). When I input fastboot devices this is what returns.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Brian>cd..
C:\Users>cd..
C:\>cd AndroidSDK\tools
C:\AndroidSDK\tools>fastboot devices
C:\AndroidSDK\tools>
Click to expand...
Click to collapse
Yeah, you're not doing something right. fastboot devices should return the serial number of your phone followed by the word fastboot. Your command returned nothing. Make sure you have the proper drivers installed. It will install new drivers the first time you hook up the phone while in fastboot, and those are necessary.

So yea I just had a breakthrough about 2 mins ago and thought I would share. I too had the same problem exactly to the T of what you where having. Then I shyte you not, I had an epiphany. While in bootloader on my phone not attached I clicked on fastboot then plugged my phone in(i am using Win7 Home 64-bit) and nothing popped up in my start bar. So I went to control panel and then to hardware and Right clicked on the Android hardware and updated my drivers automatically and viola my problem was solved.

I think I figured out my problem. When in fastboot, my phone isn't recognized by my computer. I went into manage devices, but Android Device isn't showing up at all. When I go back to bootloader, it recognizes my phone, and says its drivers are up to date. The only problem is, fastboot commands can only be used while in fastboot. If my phone isn't recognized while in fastboot, then I can't apply any fastboot commands. How can I get my computer to recognize my phone while in fastboot?
jc_byrd said:
So yea I just had a breakthrough about 2 mins ago and thought I would share. I too had the same problem exactly to the T of what you where having. Then I shyte you not, I had an epiphany. While in bootloader on my phone not attached I clicked on fastboot then plugged my phone in(i am using Win7 Home 64-bit) and nothing popped up in my start bar. So I went to control panel and then to hardware and Right clicked on the Android hardware and updated my drivers automatically and viola my problem was solved.
Click to expand...
Click to collapse

Are you sure you are in fastboot mode? I had the exact same problem and actually took the Nexus S back because I could not get fastboot to work(have to use fastboot to unlock bootloader). After reading numerous threads I booted my MT4G into recovery and cursored down to fastboot and actually clicked on fastboot and then connected the device to the usb which was already connected to the PC and lo and behold it loaded the drivers and away we went. I did the same thing with my Nexus one and my Vibrant and all now are recognized by fastboot. I do not know if this will help you but just wanted to share what worked for me.

Just had the same issue with my Incredible 2, followed the above, and worked just fine.

k3n85 said:
Just had the same issue with my Incredible 2, followed the above, and worked just fine.
Click to expand...
Click to collapse
i got a weird error,
"sending splash1...OKAY"
"writing splash1"...FAILED <remote not allowed>
phone is recognised in fastboot etc...
any ideas?
thanks

removed

fastboot device is not recognized
Here' s my case
Initially unlocked bootloader, rooted through kingroot; tried to flash xposed framework through twrp but the zip file was not compatible. hence phone was bricked.
restored my moto g updated to 5.1.1 through OTA update.
Again rooted through Kingroot, bootloader is still unlocked but now when i'm trying to again install twrp i'm getting a message that
""'fastboot' is not recognized as an internal or external command,operable program or batch file.""
the procedure i'm following is correct. Prerequisite requirements are also installed.
Please help!

KindleFire Partitions error? [Still not fixed]

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
When a wipe is issued:
C:\adb>fastboot -w
erasing 'userdata'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.

I think I'm having the same problem. When I try to boot the bootnew.img for intersectRaven's kernel, it hangs at the FIREFIREFIRE yellow triangle with an amber light. No fastboot commands will take me out of it. If it makes a difference, I installed the custom WiFi driver.

Thats the exact same thing is for me.

TyHi said:
Thats the exact same thing is for me.
Click to expand...
Click to collapse
I guess we're in the same boat then. I think my problem came from booting the kernel up, then installing the custom wifi driver, then trying to boot it up again.

When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
Click to expand...
Click to collapse
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?

rwphwp said:
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
Click to expand...
Click to collapse
Since apparently the OP and I have the same problem, yes I tried that. The command "fastboot -i 0x1949 oem idme bootmode 4000" doesn't work for me. It just boots into fastboot again.

I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.

Yes I have. It just hangs on the yellow boot with a green light.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
The thing is that I cant even root it. It is just stuck it at boot screen for FIREFIREFIRE v1.0.

Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
I suck at pushing buttons on forums now (hence the accidental thank), but I'm not really trying to install CM7.

Have you tried the hard reset? Hold power button for app. 18 seconds till screen goes totally dark, then press power bttn on again, once.

Yes I have many times.

I can suggest changing the driver on usb in pc or rebboot pc after uninstall and the change it . But I wanted to show a procedure. win utility 7 gave me the necc. usb driver v. 6 did not have.

TyHi said:
Yes I have. It just hangs on the yellow boot with a green light.
Click to expand...
Click to collapse
Gotcha. Any luck with this method?

There was also A kindlefire utility v.? with an option in red for "factory reset" on the device, perhaps.

rwphwp said:
Gotcha. Any luck with this method?
Click to expand...
Click to collapse
Yes I have. Can't even do adb push. When I get into adb with using boot boot.img from cm7. I get, exec /system/bin/sh' failed no file or directory.

I would not give in, but try to stay calm with all methods to reclaim functionality. I started with rootwiki and Jayce Ooi's And Burrito in order to stay clear of CMD console cause I was not even recognised till Win_usb drivers eventually fell in place. Saw some stuff about editing path's also. Reading alot helped.

I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.

Vashypooh said:
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Click to expand...
Click to collapse
I was in there all day, and I never got a working solution.

TheMagicPancake said:
I was in there all day, and I never got a working solution.
Click to expand...
Click to collapse
Join there ~12:45-1am EST, ill be available to help then.

[TF300TG][Guide] Flashing back the original stock ROM

Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Disclaimer:
By following this guide, you will have to issue commands that risk to damage (aka. brick) your tablet or at least void your warranty. I won't be responsible for any damage made to your device. You've been warned.
Click to expand...
Click to collapse
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
And there you have ! You are now back to stock ROM with fully working 3G

Thanks a lot for this, I found these instructions on Wolf's thread but wasnt sure it would work with our devices, Thanks for taking the first big step.
Questions.
1. Does this wipe your data?
2. Does CWM still work after?

AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173

Hi, followed the steps but it didnt work for me
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796653 KB)...
OKAY [137.443s]
writing 'system'...
FAILED (remote: ()
finished. total time: 138.477s
The Tab shows
Failed to process command flash:system error(0x170003)
The progress bar is showing under the USB logo with 1% blue, after hold power down I'm back into Onyx Rom
Any Thoughts?

I had the same problem and I just issued the same command a second time and it worked just fine
Try to format your /system (under the mounts and storage option) from CWM and wipe data and cache.

2nd time a charm!
Worked fine the second time i ran the command,
Im back to stock again :good:
I will wait for a 3G friendly Rom before flashing again
Thanks for your help
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Auliyaa said:
AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
Yip Sends you back to total stock
Stock Recovery
Stock Rom
only thing that sticks is Unlocked Bootloader

Thanks a million. This worked for me as well after 2 tries. Saved my $400!

Thanks heaps for this
I ended up in trouble when I flashed the TF300T firmware by mistake. It kept freezing and rebooting on me after that little stuff up.
Anyhow before I did that I made a backup with CWM, and after I restored it my 3G was gone but everything else worked fine.
Manual updates were failed though and they still do. At least I have my 3G back :victory:
So this method would probably work for upgrading to .40 as well, but it means a complete datawipe!
I'm sure there are many of us in the same boat now. I guess we will just have to wait and hope that some kind person makes a recovery image for the TF300TG?

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
I got a question, i had problems with the touch since the last update, so i want to go back to the original, so my question is to perform this do i have to have the bootloader unlocked?

Auliyaa said:
Hi everyone,
[*] Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Click to expand...
Click to collapse
Hi, any idea why i dont have this 'USB icon' ?? i have 'wipe data' and an android icon that performs a cold boot.

Any idea why this will seemingly flash fine, but go to bootloop when I fastboot -i 0x0b05 reboot the tab?

Don't work for me
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?

hy
i'm having a problem with my tf300t...when i turn it on it shows the asus logo and in the upper left it show device is unlocked...but i can't enter the menu showing rck and the other 3 icons...i really don't know what to do...
then there is another thing...tried to install driver...i get to the part where the tablet is visible, but with the vol up and reset with a pin...it then shuts down and if i try to power it up it dissapears from the device manager...also...if i don't turn it up, the driver can't be installed...i tried every method...please help...
can i retun it to the repair service this way or i will loose my waranty?
sorry if the spelling isn't correct...i don't speak english fluently
waiting a response...thanks in advance

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
is a tad wrong. It works, but only by accident.
You should be using
fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
The technical reason for why your command works, is because the nvidia bootloader writes files to the staging area before writing it to the partition you specify.
What essentially happens is:
Blob is written to staging
Blob is copied to system (meaning non-booting system)
On reboot, blob is "extracted" from staging and properly flashed.
Step 3 is what makes it work in the end, but you are causing an extra unneeded write to the flash (step 2 is not really needed) (In this case it works, but it potentially increases the risk of bricking)

thx didn´t know that. So all the howto´s are wrong

benoitvdh said:
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?
Click to expand...
Click to collapse
Your probably running Jellybean, if so this HOWTO does'nt work.

Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.

Blackdrag said:
Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.
Click to expand...
Click to collapse
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:

Success!
Hazaa! I can confirm that I managed to flash back to stock by flashing the blob to the staging partition. Like so many other, the first flash failed but the second time worked. I now have working 3G again!

0nyx7 said:
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:
Click to expand...
Click to collapse
Thanks for the reply 0nyx7!
I had waited a while, maybe 10-20 minutes? But I don't remember entirely. I tried flashing the stock firmware a few times but eventually I just gave up. I didn't like the possibility that my tablet was bricked so I just aborted mission and decided to go back to cm10 where it was safe. I just looked up a post on how to flash Clockworkmod Recovery with fasboot and then flashed a cm10 nightly I already had on my internal storage. So all is good... Mostly.

[Q] Back to stock help???

So I recently grabbed me a Grouper recently to *cough* remember my first Android powerhouse (before I met the Optimus G) and decided to tinker with it as usual. I've owned 6 (now 7) different Groupers in this lifetime and have great experience with it, how to get those pesky drivers working, etc. This is my first 32GB model ever. Anyways, I unlocked the BL, rooted and flashed TWRP (thanks to WugFresh's toolkit) and decided to play with the newer roms (last time I owned one, KitKat was a rumor) and kernel combos. Anyways, I decided I prefer its stock performance and battery, and that maybe I'd use Xposed to tweak apperance instead. My mistake was, I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method (which we have various threads on, and toolkits including WugFresh's). Trying the manual method, I followed the following guide using a 4.4 image zip file:
http://forum.xda-developers.com/showthread.php?t=1907796
Claims that the sysem.img doesnt exist when it gets to that part. I extracted the entire file and it DOES exist. Anyways, I tried WugFresh's tk and sort of gives me the same ending (after literally almost an hour of waiting TWICE due to my old PC).
THERE WAS A GUIDE I SAW SOMEWHERE while Googling "how to" get back to stock on Google which actually point ou how to MANUALLY flash each .img yourself one by one via fastboot, which I really intended on doing instead of the above methods (DIY anyone?) but I can't find that guide and I'm not even sure if the post was here on XDA or Android Central. I should have done all Google search on the PC instead but ATM the tablet seemed more convenient for a search.
Anybody know the guide I am mentioning or know what I am talking about? I am assuming that method will solve my dilemma, and I like doing these things manually at times anyways....
EDIT: To my disappointment, found the post, but no good:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
Apperantly everything flahes fine until it gets to the system.img part...adb/fastboot just freezes there and wont budge at all. Since I noticed that it did flash things, I've decided to flash TWRP and just flash a rom from my flash drive (thanks to a USB OTG) but I would still like to actually FIX the thing properly and return it 100% stock. Any ideas?

Crossvxm said:
I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method
Click to expand...
Click to collapse
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!

crache said:
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
Click to expand...
Click to collapse
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave

Crossvxm said:
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Click to expand...
Click to collapse
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?

crache said:
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
Click to expand...
Click to collapse
WugFresh is a toolkit made to root, unlock boot loader, relock, restore to stock, etc. And yeah I used the fastboot erase and fastboot flash commands via ADB/fast boot and as I said, everything goes well except the part where its time to flash the system.img, it just hangs there doing nothing. Tried and left it for several hours and still nothing

Try a different USB port on you computer or a different USB cable... or both.
Crossvxm said:
...
....it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all.
...
Click to expand...
Click to collapse
Hi, Crossvxm...
This seems to be a relatively common problem, and I always seem to have it myself when fastboot flashing factory stock.
I've no idea why, but the fastboot connection seems to 'time-out' when fastboot flashing 'system.img'.
Now normally, and just prior to running any fastboot flash commands, you should run this command...
Code:
fastboot devices
This command doesn't actually do anything; it's essentially just diagnostic and is used to confirm you have a viable fastboot connection prior to flashing anything. If do you have a fastboot connection, you should see something like this (with the N7 booted into the bootloader)...
Code:
015d2d42xxxxxxxx fastboot
This is the Nexus 7's unique serial number followed by the word 'fastboot'. If you don't see this, then you likely have a driver problem...
...BUT HOWEVER, I KNOW I DON'T HAVE A DRIVER PROBLEM.. so when having problems with 'sending system', and upon opening a second command prompt window on my Windows laptop, and typing fastboot devices again, the Nexus 7's serial number now no longer appears... and this is AFTER the bootloader and boot img's have been sent and written successfully.
At this point, I can only conclude, and that for unknown reasons, my fastboot connection has 'died'... and 'sending system' is now permanently 'stuck'.
And the fastboot flash attempt has failed.
-----------------------------------------------------
The solution for me, was to change to a different USB port on my laptop. Another possibility might be to try a different USB cable... I haven't tried this... just a change of USB port on my laptop was sufficient, and the problem with flashing system.img was resolved.
Either way, reboot the N7's bootloader using a differerent USB port on your computer or a different USB cable... and attempt the flash again.
One final point... 'sending system' does take longer than the other .img's, probably due to it's size... but it really should take no longer than around 5 minutes... 10 minutes maximum.
Hope this helps... and good luck.
Rgrds,
Ged.

Bricked Tilapia?

Seems I've just bricked my Nexus 7 3G. What I did:
1. After retiring my old Nexus 7 3G from car service (upgraded to Nexus 7 2013) I decided to make the system more mainstream.
2. First I decided to upgrade the TWRP to be able to flash some of the 7.1.2 ROMS. From that moment no version of TWRP I've flashed ever booted. The system booted normally, just no access to recovery. No idea why but this is not very important at the moment.
3. So I decided to go stock for the start. I downloaded factory image LMY47V and started flash_all.bat.
It went like this:
fastboot oem unlock - OK
fastboot erase boot - OK
fastboot erase cache - OK
fastboot erase recovery - OK
fastboot erase system - OK
fastboot erase userdata - OK
fastboot flash bootloader bootloader-tilapia-4.23.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasig-lmy47v.zip - failed while flashing system (I didn't remember the error)​
4. From that moment my tablet behaves like that:
- attempts to get to bootloader (all possible button-press combinations) all end up with Google logo displayed forever
- long press of power button in this state results in restart (not power-off) - again to Google logo
- I can power off by simultaneously pressing all 3 buttons
- obviously, there is no way to connect by adb or fastboot
5. So, it seems like the bootloader is gone/inaccessable. Strange - it was indeed flashed in the unsuccessful re-stock attempt.
Is there any chance to unbrick?

Here is why I gave up googling and am asking here. There seem to be 3 categories of "bricked" Nexus 7, none of which fully fits my case:
1. Unbootable system but still accessible bootloader. Usually possible to access the device via fastboot and flash recovery. Not my case.
2. Device with positively deleted or corrupt bootloader. May be my case. But flash_all.bat seemed to successfuly flash the bootloader image.
3. Nexus randomly stuck in Goole logo, which may be "repaired" by physical force or mainboard replacement. Hardware fault. May be my case, but I know I screwed it up by my flashing attempts.
There are guides for unbricking with nVidia nvflash. But the assumption is the device is visible on computer's USB. Not my case.

Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.

nalott said:
Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.
Click to expand...
Click to collapse
Did you try reinstalling the drivers after removing all other drivers? If the attempt is successful and the tab is recognised, try the Wugfresh Toolkit. The toolkit itself has proper drivers and instructions to install the drivers.
Also try another cable, another USB port (2.0 not 3.0), another PC/Laptop.
Hope you succeed.

Thanks for help. I will try. But I have very little hope: I was using the particular setup (PC, cable, connector, drivers) and it worked fine until the crashed factory image flash. I'm still using it with my Nexus 7 2013 without problem.