Database Users

wifi Xoom 3.1 unlocking bootloader error...

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

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.

Help with rooting P8-lite Ale L21 dual-sim C432B564

I have a relatively new P8-lite L21 dual sim phone and I am quite happy with it. It came with C432B170 which is Lollipop I think 5.01. After a few days it updated to B172. I have unlocked the bootloader after registering with Huawei and waiting 2 weeks. Then I have successfuly rooted the phone with Kingroot phone version. Two or three weeks ago I have updated the phone to MM (6) and Emui 4 with local update (B560) that I have gotten from this forum. 2 days ago I recieved the notification of OTA B564 which went smoothly beside the fact that it reset the phone but i have succesfully restored (contacts, data etc.) All of this time since I upgraded to MM i have tried to root the phone but I was unsuccesful either with any software solution ( Kingroot, Kingoroot or others). After reading most if not all discussions on this forum and several blogs and how -tos, I tried the so called fastboot method others have recommended but here is now the gist of my problem. My phone is seen by my PC - OK so USB drivers are properly installed (by the way my PC is Win 10) and I have installed Android SDK as well as minimal ADB. When i try to flash TWRP 3.00.2 I can not do it (the message says something about not able to access or i think remote command not allowed. So since I cannot flash TWRP i am unable to put SU on the phone and root it. I hope someone more experienced and skillfull in Android world can point me in the right direction and help me. Thank you

Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.

VladHD said:
Download mininal adb fastboot and then try to flash twrp via fastboot.
That error occurs because your adb doesn't have full permissions.
Minimal adb will solve this.
Click to expand...
Click to collapse
Downloaded minimal adb fastboot and installed it. Tried the procedure. Copied TWRP recovery to the minimal folder. Shift right clicked in the folder of minimal and opened command window. Adb rebooted to bootloader. Phone shows it is unlocked. The device is seen in fastboot window but flashing recovery doesn't work (same message) I am really confused. How do I give adb full permissions ?
Any way thanks in advance.

Did you activate usb debugging ?

VladHD said:
Did you activate usb debugging ?
Click to expand...
Click to collapse
Yes of course !

Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.

VladHD said:
Try reinstalling drivers with universal adb.
Are you sure your bootloader is unlocked?
Type fastboot devices and let me know the output.
Click to expand...
Click to collapse
The drivers were reinstalled. My bootloader shows unlocked on bootloader (bottom of fastboot screen). Fastboot devices does nothing. Adb devices shows my phone serial number correctly (I have it written down). But then when i try to flash recovery it is unsuccessfull. It says "FAILED (remote: Command not allowed)"

What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
What is the command that you typed..?
Fastboot flash recovery xxx.img
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img

doomking_99 said:
Fastboot flash recovery recovery. img I renamed the twrp 3.0 to recovery.img
Click to expand...
Click to collapse
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)

amageek said:
sorry, if you've already answered this, but you can also do it by flashify... flash the recovery image via flashify (root needed though)
Click to expand...
Click to collapse
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.

doomking_99 said:
Thanks, but my problem is that i cannot root without installing TWRP is my understanding.
Click to expand...
Click to collapse
ahhh... sorry mate, dont know the solution.. but try re-installing adb drivers again ...

Are you logged as adminstrator on pc?
Try to plug usb into different slots.

VladHD said:
Are you logged as adminstrator on pc?
Try to plug usb into different slots.
Click to expand...
Click to collapse
I am and I have. I am stumped. Obviously something is wrong with windows permissions I think. Is it possible to put recovery. img on sd card or on phone and flash recovery from the phone ?

This is the output every time no matter which usb port
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
W3D7N15C08019820 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.624s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
C:\Program Files (x86)\Minimal ADB and Fastboot>
The thing i don't understand is why fastboot command doesn't show device while adb command does.

You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app

amageek said:
You said that you have android sdk too... Have you tried using that?
If it doesn't help them try to do it on other computer or reset your windows...
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.

doomking_99 said:
Thank you but i have tried with SDK and with minimal and always the same result as i posted. I will try and do it on my wife's PC.
Click to expand...
Click to collapse
Sorry for the zombiethreading here, but... what whas the solution? I'm curious

For the time being there is no solution. Can not flash TWRP - phone not rooted

doomking_99 said:
For the time being there is no solution. Can not flash TWRP - phone not rooted
Click to expand...
Click to collapse
Weird... i can't think of anything else myself that hasn't been said. Perhaps... redownloading twrp? Maybe the image is corrupted by something... ot's a long shot because ot should flash everytging that comes its way. But it's the only thing you hven't tried.

Root HTC Bolt

Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay

jortiz31877 said:
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
Click to expand...
Click to collapse
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system

Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?

jortiz31877 said:
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
Click to expand...
Click to collapse
you said u were good w/ that step so I didn't mention....fastboot is not an option in the menu, it's a tool...you need to use fastboot command to unlock bootloader & also to flash twrp
install this for fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.

jortiz31877 said:
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
Click to expand...
Click to collapse
after unlocking bootloader, you will need to flash twrp (fastboot flash recovery nameofrecovery.img), the twrp.img needs to be in you sdktools folder on pc, after flashing, then boot into twrp...from download mode, choose reboot to bootloader, then reboot to recovery. once in twrp, you should probably leave /system read only, then copy either supersu or magisk to sd card, and choose install from main menu of twrp....once done, boot device. if using magisk, update from store
u only need to connect to pc when entering fastboot cmds

will this root work with boost mobile HTC bolt or is there a root that will work for this phone

Chrism1971 said:
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Click to expand...
Click to collapse
Either should work fine
Sent from my unknown using XDA Labs

Question
OMJ said:
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Click to expand...
Click to collapse
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.

craftingatic said:
I am scared to lose my warranty on my phone.
Click to expand...
Click to collapse
You will lost your warranty anyway, if you open the bootloader via HTCdev.

craftingatic said:
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
Click to expand...
Click to collapse
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look

OMJ said:
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
Click to expand...
Click to collapse
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up

roadkill42 said:
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
Click to expand...
Click to collapse
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then

OMJ said:
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
Click to expand...
Click to collapse
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
Click to expand...
Click to collapse
No triangle just HTC in gray then flashes red letters under it

roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
No triangle just HTC in gray then flashes red letters under it
Click to expand...
Click to collapse
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode

OMJ said:
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
Click to expand...
Click to collapse
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow

roadkill42 said:
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
Click to expand...
Click to collapse
Is there a complete in full detail way of flashing tarp in download load mode?

roadkill42 said:
Is there a complete in full detail way of flashing tarp in download load mode?
Click to expand...
Click to collapse
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html

OMJ said:
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
Click to expand...
Click to collapse
OK thanks there is a lot out there I might did wrong one I try this way and let u know thanks again is there a special key combo to get into twrp after flashing ?

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
HT7120403511 device
when i try to reboot to recovery under the htc says this build for devloping purpose only im on n with no updates installed this phone came to me like this bran new
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
sending 'recovery' (8156 KB)...
OKAY [ 1.782s]
writing 'recovery'...
(bootloader) HOSD CL#821651
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.311s]
finished. total time: 4.096s
C:\Program Files\Minimal ADB and Fastboot>adb reboot
error: device not found
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.004s
C:\Program Files\Minimal ADB and Fastboot> I'm on 7.0