Database Info

NO ROm stuck at bootscreen

Can someone direct me to a tutorial to restore my phone

dee163 said:
Can someone direct me to a tutorial to restore my phone
Click to expand...
Click to collapse
Boot to the bootloader, select fastboot, then plug it in to your PC. Now on your PC, where you have adb and fastboot installed, open a command prompt and type 'fastboot oem lock'. This will relock your bootloader and allow you to run a stock AT&T RUU. (downloaded here http://d-h.st/bS4)
After you install the stock RUU you will need to unlock the bootloader again to start flashing custom roms. If you need more help let me know.

dee163 said:
Can someone direct me to a tutorial to restore my phone
Click to expand...
Click to collapse
Follow the steps I wrote in the 2nd post here
http://forum.xda-developers.com/showthread.php?t=1780860

[Q] Need hard help (URGENT)

I received my T-Mobile One S, and for some reasin decided to update it to custom Jellybean.
result: Doesn't booting after HTC logo(started after I flashed the kernell), installed sdk, but adb can't see my device, drivers up to date. can't see my sd card(Can see the E-removable drive, but when I try to enter it, it says there's no E-drive, when I unplug the device the E-drive dissapears). Factory reset doesn't help. I think the is that I flashed the kernel, and I can't find the stock one. Any suggestions, guys? I am very new to all these, and English is not my native, sorry.:crying:

Try to download and run this RUU.
But first lock your bootloader in fastboot.
fastboot oem lock
https://dl.dropbox.com/u/76257867/R..._2_10.22.31501S.10L_release_263233_signed.exe
Sent from my HTC One S

kaiser347 said:
Try to download and run this RUU.
But first lock your bootloader in fastboot.
fastboot oem lock
Sent from my HTC One S
Click to expand...
Click to collapse
Code:
C:\Users\Owner>fastboot oem lock
< waiting for device >
how to fix it? thank you

I had exactly the same problem, try to flash stock boot.img and relock bootloader to flash RUU, or try adb in recovery (for me adb works only in recovery in this situation) and send a rom to sd card, hope will help you

psylooooo said:
I had exactly the same problem, try to flash stock boot.img and relock bootloader to flash RUU, or try adb in recovery (for me adb works only in recovery in this situation) and send a rom to sd card, hope will help you
Click to expand...
Click to collapse
The problem is that I can't find the stock boot.img, any suggestions?

BariyevOlexiy said:
Code:
C:\Users\Owner>fastboot oem lock
< waiting for device >
how to fix it? thank you
Click to expand...
Click to collapse
Try to reboot in fastboot mode.
Do you have all the proper drivers installed?
Sent from my HTC One S

BariyevOlexiy said:
The problem is that I can't find the stock boot.img, any suggestions?
Click to expand...
Click to collapse
Here is my stock boot.img and stock recovery
https://www.dropbox.com/sh/qmviq0npxnfsfcq/ZaTRoHHjZX

it work now, but still can't mount the sdcard, and adb is not working

[Q] CID at 11111111 but not rooted

I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?

ctennenh said:
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
Click to expand...
Click to collapse
You need to flash a rooted Rom. you were on 2.20, it is a temp.root to change your cid so you can unlock your boot loader.
Did you flash teamwin recovery yet?
Sent from my HTC One XL using xda app-developers app

Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.

ctennenh said:
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
Click to expand...
Click to collapse
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for

absolutelygrim said:
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
Click to expand...
Click to collapse
Retry what part? I'm sorry. Do you mean I should do the whole process from the start, or just part of it? It actually says "unlocked" at the top of the bootloader screen right now. Should I just go ahead and flash the TW openrecovery?
I downloaded the latest CM10 and ran fastboot on the boot.img. After flashing openrecovery should I be good to flash the ROM and gapps? Thanks for your help.

ctennenh said:
Retry what part? I'm sorry. Do you mean I should generate a new token?
Click to expand...
Click to collapse
Use the same token, but retry the process

Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.

ctennenh said:
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
Click to expand...
Click to collapse
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.

absolutelygrim said:
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
Click to expand...
Click to collapse
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?

ctennenh said:
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
Click to expand...
Click to collapse
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery

absolutelygrim said:
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
Click to expand...
Click to collapse
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!

ctennenh said:
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
Click to expand...
Click to collapse
Recovery. if you can't use adb reboot recovery use fastboot reboot instead and hold volume down until you get into the boot loader, then scroll down to reboot, hit the power button, scroll down to recovery and hit the power button again. That should put you in TWRP

After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.

ctennenh said:
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
Click to expand...
Click to collapse
Hold the power button and volume down until the phone turns off. When the screen turns off let go of the power button but not volume down. Continue holding volume down until you see your bootloader screen. It will say UNLOCKED at the top
edit: btw, when flashing boot.img, use the following command fastboot flash boot boot.img so put the boot.img in the folder with fasboot.exe and use that command. When it flashes, then you can flash your ROM
Sent from my HTC One XL using xda app-developers app

Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?

ctennenh said:
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
Click to expand...
Click to collapse
Unmount.
Wipe System
Factory Reset (wipes /data and /cache)
Flash your boot.img from fastboot using "fastboot flash boot boot.img"
Flash your ROM
Flash gapps
Reboot and enjoy

Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.

ctennenh said:
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
Click to expand...
Click to collapse
Reboot back into bootloader. and then boot into fastboot from your boot loader, then try the command again.

You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning

ctennenh said:
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
Click to expand...
Click to collapse
You got everything working? Enjoy your root, unlock, and ROM, and good night

Recovery failing to flash

So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!

I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?

in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help

First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?

berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess

Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.

berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!

ok i did all that but it removed fastboot what do i do to get it back?

Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.

ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.

Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial

berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.

ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os

Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.

_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue

(fixed)Back to stock recovery is not working

Hi guys!
I have installed twrp recently but i decided to install stock recovery back. After installing stock recovery still twrp appears.(tried it 3x times)
Any idea?
Thank you for your answers.

Are you using fastboot to flash the recovery? If so what gets displayed when it fails?

As BakedOnSomeSour said, stock recovery must be flashed through fastboot using the same command you used to flash TWRP, and so "fastboot flash recovery <recoveryname>.img". That's the only way to flash a recovery (unless that you use dload and reflash full firmware).

BakedOnSomeSour said:
Are you using fastboot to flash the recovery? If so what gets displayed when it fails?
Click to expand...
Click to collapse
I got a message: (remote:Commant not allowed).

killershan said:
I got a message: (remote:Commant not allowed).
Click to expand...
Click to collapse
Allow USB debug and OEM unlock by developer settings menu and retry... Plus, tell me what your fastboot says about FRP and Phone

BakedOnSomeSour said:
Are you using fastboot to flash the recovery? If so what gets displayed when it fails?
Click to expand...
Click to collapse
RedSkull23 said:
Allow USB debug and OEM unlock by developer settings menu and retry... Plus, tell me what your fastboot says about FRP and Phone
Click to expand...
Click to collapse
Phone:Unlocked Frp:Locked.

killershan said:
Phone:Unlocked Frp:Locked.
Click to expand...
Click to collapse
If FRP is locked, read my post above. OEM unlock must be enabled by developer options.
Anyway, procure yourself a valid copy of your actual firmware's recovery and retry a flash by fastboot. Then, try to boot directly to recovery

Thank you for your asnwers.Finally i fixed my problem.