Related
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!
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy paste into search bar - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
okantomi said:
OK, I will first say that I'm not an expert, but have gone through this process and have had to use ADB a number of times, so
1) why did you copy all the platform tools into tools folder? It should be otherway around, but clearly you have it working, so OK with that,
2) do you have all the files you need in your tools folder (since that's what you are using)?
3) are you using the proper syntax? No additional spaces where they don't belong, and so on?
4) are you getting any messages at all on the Xoom itself when you enter these commands?
5) Review all of your steps. Start over. If no luck, why not try to chat with experts on Xoom Channel on IRC? Maybe they can help you pinpoint the problem.
It doesn't seem serious but I think you've maybe missed a step in your prep work or have something simple turned around.
Good luck.
Click to expand...
Click to collapse
-copied to tools folder, because that's what I was directed to do... Guess it works either way.
-I do have all the files needed.
-How do I know if I'm using proper Syntax or not? that might be where I went wrong. But idk...
-No messages AT ALL on the xoom screen. (actually, 1 time out of the hundreds of times, Below the 'fastboot' words, I got red words that said cannot process command, or something like that.)
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
Do you know what you did to be able to unlock? I think you really have to be careful to type commands EXACTLY as shown. No extra spaces, but don't leave anything out either. Looks like commands aren't typed in correctly. Take your time. You'll do it.
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
eqppwqqep said:
I had this error followed by "unknown partition". When I tried fastboot boot recovery.img, it would say it could not access recovery. I deleted every partition and sent the device the stock imgs. Recovery would still fail.
STRANGELY ENOUGH, I rebooted my PC, unplugged the cable from the Xoom, let the device boot, changed USB debugging to on (stock unchecked it when imaged), and it took the recovery flash that time. I can't explain why, but it worked for me.
Click to expand...
Click to collapse
So is everything ok now?
okantomi said:
So is everything ok now?
Click to expand...
Click to collapse
Yes. I am not rooted. am I supposed to change the thread to solved or something?
different error on trying to flash this recovery
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
If you haven't already. Delete the .img file. and reinstall it. try the process again.
make sure you're inputting the full command prompt from the beginning. That was my problem. Hope that helps.
jesmitty said:
I get a strange error when trying to "fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img I get:
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img
The file is there. In fact I have used this file before. Am I really hosed. Any ideas.
Click to expand...
Click to collapse
fastboot flash recovery(you missed this) recovery-Tiamat-R4c-100611-1150-cwm.im
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.
So I followed the XDA guide on rooting. After getting back to the setup screen, I constantly got:
Unfortunately, the process com.google.process.gapps has stopped.
It was literally constant to the point where I could only type one letter at a time. Okay, so I tried factory reset via TWRP. No good. So I downloaded a factory image and tried to flash it, and now my phone sits at the Google/padlock screen forever.
What do I do? I still have fastboot and TWRP access. I'm not sure the images are completely copying to the Nexus when I try to put them directly on the phone. Using Google's image and flash-all command ends in:
writing 'system'...
FAILED (remote: unknown command)
I don't understand this. Please help me. I can't use my phone at all.
Are you unlocked? Can you fastboot flash?
I can, yes. I figured out at least part of my problem - the USB 3 port on my laptop is misbehaving somehow. The USB 2 port works. I was able to fastboot flash. It remains to be seen why I had the gapps issue originally...
Hi all!
First of all, Im new here, sorry if this is in wrong section (please don't delete the thread, move it to other section if needed) and that this has been posted millions of times but Im in really really dire need of help, and people told me this is best place to come to!
So here it is, I've tried countless methods and read alot of threads all over internet and nothing seem to work for me. (All info is down below just read it )
I tried with ADB and Fastboot, but where I get stuck always is with that my phone, somehow rejects new recoveries (TWRP, CWM) (???). What I mean is that when I try to start phone in a custom recovery(either holding +-volume and power button , or volume + and power or volume - and power) I get nothing(I can get him into his own recovery, but only options are to reset, shutdown and update and recovery and that is from first holding -volume and power then from fastboot and rescue mode and then by holding +volume). I got him ONCE to recovery(or whatever/however that place is called) where I can wipe partition cache and dalvik , it just stays at Huawei logo.
I tried both with scripts and with manual way where I input commands in cmd. I've bricked my phone about 4-5 times , and I know how to unbrick it with ease. What I dont know is how to get phone to take a custom recovery. And yes, I have unlocked BootLoader and followed all and every step there was in each guide I found. I tried with the most hated method (KingRoot and other kinds) but nothing.
Info you might need:
-As stated, phone is p8 lite, with marshmallow 6.0. (ALE-L21C432B584)
-BootLoader unlocked.
-I have all necessary drivers installed and all permissions on my computer for drivers to work correctly.
-Kernel Version - 3.10.86-gd9a2b44
-Yes of course I have debugging enabled everytime.
Once again, methods I have tried:
-ADB and FlashBoot
-All kinds of programs through phone (Kingroot, Iroot, KingOroot etc.. (I read that you can't root phone through this method but gave it a shot.))
-I don't remember if there was any other method to do it tbh because Ive been doing it for last 2 days and Im kinda tired and super pissed hehe.
But if I forgot/missed something of information that you need please just ask.
Sorry if there is too much of detail, I just wanted to describe my problem as perfectly as possible and as in much detail as needed.
Thank you all who will read/read (Oh the typing world) my thread I really appreciate your time and effort. All and any help regarding my problem will be tried out and appreciated ^^!
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
keikari said:
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
Click to expand...
Click to collapse
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Ebilog said:
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Click to expand...
Click to collapse
Weird, though you must have done something wrong when installing TWRP, because it removes stock recovery. Make sure you have typed everything right. Because if you type like "flash recvery" insted of "flash recovery" it shows stuff that by quick glance might seem correct. Oh I forgot you need root to reboot with terminal emulator XD mb. Could you show what fastboot shows when you install TWRP.
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Ebilog said:
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Click to expand...
Click to collapse
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
keikari said:
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
Click to expand...
Click to collapse
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Ebilog said:
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Click to expand...
Click to collapse
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
keikari said:
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Ebilog said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Click to expand...
Click to collapse
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
keikari said:
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
Click to expand...
Click to collapse
So i managed somehow to get the to twrp menu and i flashed supersu and i flashed new version of twrp . but i think thats what made it crash. Would it be ok if my phone stayed with 3.0.2.0 ver instead of getting 3.1.0.0?
Bcoz when i flashed 3.1.0.0 phone got stuck on 2nd logo and didnt reset or anything.
Thank god i know how to unbrick a phone at least hahahah
Edit: If this thread stays and people with problem like mine need help , feel free to pm me ill gladly help
yeah older TWRP is good if it works.
Though problems you got are still weird.
I had this problem ..
If you have restored your system and can access twrp recovery , download supersu v2.62 and install it .. this version worked for me after trying many ..
Every time my phone bricks i was downloading new whole system , instead try flashing it with twrp its better ..
Good luck .