Related
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
New Jer-Z said:
I achieved the unlocked bootloader, at least I believe, per instructions via the HTC website. But I can't seem to be able to flash a recovery or achieve root. I can boot into HBOOT, when I try to click Recovery, it takes me to some page explaining software is not to be distributed, blah blah. Then it just boots up like normal?
I'm afraid I don't understand? Everything i've tried fails, why is that?
Click to expand...
Click to collapse
You skipped right over the "can't seem to able to flash a recovery."
Please explain in detail the instructions you followed AFTER unlocking via HTCdev.com. This includes files you downloaded, where you put them, how you attempted to flash, etc.
These details will be very helpful. Don't worry, sounds like you're not in any serious trouble at all. Just don't go flashing anything you see.
Also, please post this to the Q&A forum or General next time. This development forum is intended for development posts ONLY (ie. ROMs, Kernels, Radio's, etc). Just a heads up. Welcome to the forums
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Moved To Q&A
Please post all questions in the Q&A section
New Jer-Z said:
Aahhh, forgive me!
And thank you for the patience and understanding!
I used the Hasooon2000 toolkit. I got as far as getting to the screen where HTC wants to confirm with me that I do want to unlock the bootloader, I clicked yes, and it rebooted. Then I tried to flash recovery. The CMD prompt will say it was pushed to the phone successfully, but when I try to reboot into recovery, I don't get very far. To my understanding, I can't apply perm root without getting to recovery, but with the bootloader unlocked, why can't I even flash one?
Click to expand...
Click to collapse
Ahhh, not to stir up the pot here, but you're getting vague again with what's going on. You say "when I try to reboot into recovery, I don't get very far". What do you mean by this? Details are extremely important in helping you. Sounds like you're saying that recovery was successfully pushed, but then I didn't get any details as to what's going on when you attempt to load recovery. Also, which recovery file did you use? Use this one
I'm not trying to get on to your case here, but you've got to be really specific when you say stuff doesn't work, because that doesn't help us diagnose your issue. When your recovery is done flashing, you should be able to access the bootloader by holding Pwr + Vol-Down for like 5 secs, then choose recovery (that or fastboot>recovery....I cant recall if recovery is a main menu item). What happens after you choose that? Mine shows the htc splash screen, with a development message in red, and then it boots Clockworkmod.
No, no, lol I totally understand, I guess I am being vague.
I was going to go into details, but I was at work. Interestingly enough, my phone died, and when I plugged it and let it charge for a little bit, the phone booted right into CWM touch - so odd! So I was like, ok, i've achieved root - well, no, cuz I opened ROM Manager and it says SU couldn't be found.
BEFORE, when I would do what you said I should do, it would take me to the HTC splash screen where it was in red text, some disclaimer about some proprietary information crap, then it would skip recovery and just boot into Android -___-
Let's see if I can replicate booting into recovery now. (What method are you using to flash your recoveries?)
EDIT: Well it looks like I can't get back into recovery. Same thing as mentioned above. I can get to the fastboot screen, but if I click recovery, it takes me to that HTC disclaimer screen, the little loading bar loads then - poof - screen goes blank and Android boots up.
I have the same problem -_-! Can someone help please
The recovery image was flashed succesfully from Hasoon2000's toolkit. But when i go to the bootloader and select Recovery, I get the red warning for from HTC about how this is for development purpose only... then the phone's screen goes black, then it boots into the stock ROM.
Cant flash recovery
Hello everyone.
I have a similar problem. I successfully proceeded with the bootloader, but now I can't install the recovery. It simply wont flash.
I was following the xda tutorial that's in this very forum, but i got stuck: In my desktop i downloaded the needed files (or so I believe), and so i have in my desktop a folder called "carpeta" (random name) with these files within: adb.exe, adbwinapi.dll, fastboot and 3 different recovery images i have tried to flash.
I use mac, so i open the command prompt for mac (terminal) and go to the "carpeta" folder and after that, I type "cd fastboot flash recovery xxxxx.img" (the xxx are the names of the recovery images that i have in the folder, one at a time) but it simply wont flash anything. I attach a screenshot to ilustrate what happens...
Please help me
http :// img710.imageshack.us/img710/6026/capturadepantalla201205.png
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
I'll give it a shot later tonight on my lunch break.
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
alexjuanes said:
tried unsuccessfully.
on screen this is what I see in my htc one s:
***unlocked***
vle put ship s-on rl
radio- o.15.315018.19_2
opendsp-v21.1.0.32.0314
emmc-boot
mar 15 2012.23:37:23
fastboot usb
bootloader
reboot
reboot bootloader
powerdown
------------------
and each time i try to flash the recovery, i get a "not a directory" or "no such file or directory" message...
Click to expand...
Click to collapse
Make sure that you navigate to the proper folder using the "cd" command.(for example" cd C:\Fastboot ", if your adb and recovery are in that location)
Make sure that the Clockwork Mod recovery file is in the same folder as the adb and make sure that you type the file name correctly
I used these file and put the recovery image inside the folder after unzipping
http://www.mediafire.com/?50baad8rykng2j0
Here is the recovery I used :
http://loadbalancing.modaco.com/download.php?file=r2-modaco-recovery-clockwork-touch-ville.img
But your running Mac so I don't know if the method I used will work for you because I'm on Windows
Doesnt work...
I have the bootloader (when i start in bootloader mode my phone says ***tampered*** and also ***unlocked***.
BUT
I've been 2 days trying to flash my recovery on my htc one s from my macbook, and after i use the command prompt to get to the folder where i have adb, fastboot, my recovery .img file,etc... this is what happens:
-----
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$ fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
-bash: fastboot: command not found
MacBook-Pro-de-Alejandrolatform-tools alexjuanes$
-----
ive already updated all that i could in the sdk manager, or whatever its name is...
please some help?
batiste93 said:
Guys it works if you flash the recovery manually through the command prompt. I think there might be a bug or something in the toolkit because the manual way worked for me.
Here is what I did:
(I am not a programmer so I can't guarantee this will work for you. Worked for me, but try at your own risk)
-Copied the recovery image to the same folder as abd
-Plugged in the phone with USB debugging on
-Opened command prompt
-navigated to the folder with adb with "cd folder_location"
-typed: "adb kill-server", then "adb devices"to make sure the device was connected
-typed "adb reboot-bootloader" to boot into bootloader
-typed "fastboot flash recovery recovery_file_name.img"
-Select bootloader>recovery using the vol up and down and pwr button
and voila recovery
Hope this helps
Click to expand...
Click to collapse
This actually worked for me. I am rooted, and am now running a custom ROM.
Thanks so much for all your help!
Hey everyone
i seem to have made a very tiny bit of progress here since now i can type the commands and make it start, but only that... starting.
my command box is stuck in a "waiting for device" message that will start nothing, and my phone is just there, untouched.
i never thought flashing a recovery would give me this much of a long headache...
help anyone? how do i make my pc stop "waiting for device"?
Have you tried a different USB cable/port? I had a similar problem but moving to a different port worked.
Sent from my HTC VLE_U
I have the same problem i did everything as in the guide posted here http://forum.xda-developers.com/showthread.php?t=1583427
But when i flash recovery through fastboot ( fastboot flash recovery recoveryname.img) everything goes ok but when i want to boot into recovery i get stuck on the HTC screen.
Than i wanted to go to recovery trough fastboot ( fastboot boot recovery ) i get message cannot load recovery.
If you need more info for help i can provide you guys with the screenshots.
Thanks in advance Nikola.
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
You're phone isn't bricked if it still turns on. If you can still access recovery why don't you just perform a full wipe then flash a new rom
lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Have you tried any of the other methods
There are two things you need to look at
1) Is the device in usb debugging enabled?
2) other than using the standard ADB method there are a few other easier methods
a) Droid explorer
i can supply a link if needed
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404
if you have any other ? feel free to contact me as i have been there
kampj007 said:
There are two things you need to look at
1) Is the device in usb debugging enabled?=Invalid the OP can not currently boot to OS.
2) other than using the standard ADB method there are a few other easier methods=Invalid the OP can not currently boot to OS.
a) Droid explorer
i can supply a link if needed=Invalid the OP can not currently boot to OS.
b) The sensation all in one toolkit
http://forum.xda-developers.com/showthread.php?t=1497404=Invalid because the only tool needed by the OP from the toolkit is boot to recovery, but it uses ADB to do this and without being booted into the OS and having USB debugging enabled this will not work
if you have any other ? feel free to contact me as i have been there=Thanks for your willingness to help
Click to expand...
Click to collapse
Also about the toolkit, seeing as they will have to boot to Hboot and then select fastboot to be able to use ADB and fastboot commands. So the toolkit is not going to do the OP any good. The OP will have to either change firmware versions or flash a ROM that is compatible with the firmware version they have to solve the problem.
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
kampj007 said:
Wait a minute...
I have been in same situation and what i did was connect the phone via Usb and turn it on. Went into fastboot and then using the programs i talked about it allowed me to load software and change items as needed. I was able to connect through droid explorer as soon as it turned on and it helps u load into recovery and fastboot so that u can adjust as needed.
Click to expand...
Click to collapse
Exactly you had to boot to the Hboot and then choose fastboot for them to use the programs. Plus the OP is already S-off and can manually boot into Hboot then to recovery. So the tool kit has nothing to offer the OP at all. Yes they can be in fastboot and use Droid Explorer to copy any needed .zip be it a PG58IMG.zip or a ROM.zip, but they can also do this within their recovery by USB mass storage in recovery.
I do not mean to offend but I just do not want to see this made more complicated than it is for the OP. It is really a very simple problem and has a very simple fix.
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
twocrows said:
Hello,
I am in similar situation. I cannot get my device to be recognized either. Here is what getvar all showed me:
"C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: SH164T500176
INFOimei: 355066045001866
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5810000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3905mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.497s"
Any help would be appreciated. Thanks!
C:\adb>
Click to expand...
Click to collapse
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
just install htc sync and do again
rzr86 said:
do you have enabled usb debugging mode from settings?
do you have installed htc drivers?
use also usb 2.0 ports not 3.0
Click to expand...
Click to collapse
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
twocrows said:
No to usb debugging mode
Yes to installed htc drivers
will make sure to use usb 3.0
Click to expand...
Click to collapse
wait not 3.0 use 2.0 ports
T-Macgnolia said:
Your device is boot looping because the fermware version is not compatible with the ROM you flashed. To get ADB to detect your device you need to boot into Hboot and the select fastboot, then you can use ADB or fastboot commands.
It would be very helpful to post what ROM you flashed. Also you have Hboot 1.27.1100 which is part of the the firmware you need to use ICS so why you were told you need a later version is kind of confusing to me, unless you were wanting to go back to Gingerbread. Please run the following command and post back everything except your IMEI number.
Code:
fastboot getvar all
Click to expand...
Click to collapse
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
scottspa74 said:
Adb will recognize device while in fastboot?
I always thought fastboot cmds were for while in fastboot, and adb was for while booted to android?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No fastboot mode is a developer tool first and secondly a fail safe to be able to communicate with ADB and fastboot if something goes drastically wrong such as not being able to boot to recovery or boot to the OS either one with the device and it needs to have the OS re installed. Try booting to fastboot mode and then connect your device to your computer with working ADB and type in adb devices it will show you the device ID.
miillaaad said:
just install htc sync and do again
Click to expand...
Click to collapse
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Funnily enough, I never got adb recognized on stock rom.
After custom rom, it does.
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
use adb toggle app from play store
see how it goes
twocrows said:
Did that, no dice
Still not seeing via adb and for whatever reason that means unable to flash new boot.img
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
So ended up going back to stock ruu.
Got bootloader unlocked, but adb still says device not found!!
I flash new (4EXT) recovery and it says it flashes ok, but never ever works.
Tried different laptops, usb cords, and installing htc sync, uninstalling htc sync, htc sync manager, etc
All have made no difference
USB debugging is enabled
Any ideas?!?
Click to expand...
Click to collapse
Maybe you should check everything is in order on low level, when your phone is connected to your computer, use lsusb under linux (usbview under windows) to check if the device is recognized by the OS.
OK, so I am a bit embarrassed on two counts:
1) when phone was booted up into ROM adb finally recognized it! I had a big duh moment.
2) it seems that at the root of the problem was a syntax error.
I was not renaming the recovery.img file properly. I was typing the command "fastboot flash recovery 4ext.img" and didn't rename file 4ext.img to "recovery.img" Cause when I renamed the file to "recovery.img" and then typed command "fastboot flash recovery recovery.img" I could finally boot back into recovery!
I did however have to flash boot.img after installing the newest Viper ROM. But here I am back on a great custom ROM! Thank you for all your help even if it didn't work it gave me the encouragement to keep trying.
Peace!
Sent from my HTC Sensation 4G using xda premium
Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev
Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit
Phone will not boot to android OS
when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK
Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did
fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img
worked
Now have
Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot
CID reported by fastboot getvar cid is BM__001
Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before
At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(
How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?
thanks
The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder
This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)
2.you deleted those images from the controlbear folder
Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img
That will get you out of the Juopunutbear screen..
No need to run the ruu in this case
Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup
Sent from my pyramid.. Through blazing fast sonic waves
If your problem was solved, it's a good idea to add [SOLVED] to the topic.
Still in trouble
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
markwatson said:
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
Click to expand...
Click to collapse
Copy the unlock_code.bin to the folder with adb & fastboot.
Then
Code:
fastboot flash unlocktoken unlock_code.bin
Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED
Solved Problem
Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.
Hello Guys, I need your help.
I got this INSPIRE 4G from a friend. When he gave it to me, he said it needed to be flashed.
The thing is, When you press the power button, it boots straight up into Fastboot.
Here Is my Hboot Info
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
Emmc-boot
Apr 12 2011,00:55:45
In Fastboot, i can move around with the volume buttons and power buttons(so that means the phone booting straight into Fastboot isnt a result of one of the volume buttons being stuck.)
When i try to access recovery from the Bootloader, It vibrates 6 to 8 times then the screen becomes black,it stays that way until i do a battery pull.
When i select factory reset from the bootloader, it does nothing.
WHen i select Image CRC from the Bootloader,These is what is printed on the screen.
OSBL: 0xC2C4DD79
AMSS: 0x6CC260EB
HBOOT: 0xF9E06F63
BOOT: 0x0
RECOVERY: 0x0
SYSTEM: 0x0
As the digit are displayed, the first three look okay,but the last three which are BOOT RECOVERY and SYSTEM seem to have no digits, Which kinda looks like its empty.
THESE ARE THE SOLUTIONS I HAVE TRIED.
1. I tried flashing a recovery from Fastboot, but it gives an error like this:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0BFRX06133 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3704 KB)...
OKAY [ 0.664s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.672s
I get the same errors when i try to flash,erase or format the rest of the partitions(BOOT,SYSTEM).
2. I have also tried the HTC RUU, it finds the device and then gets stuck when it tries to boot into Android.
I have also tried the HTC RUU Hboot update but it also fails like the RUU ROm update.
3. I have also tried to flash the STock rom as PD98IMG.zip via bootloader, but when it finds the file, it asks me to press volume up to start update, when i press volume up, it loads the file and when its suppose to flash it, it sort of skips it and move to the next. It does that until its done the asks me to press power to reboot. Since it skips the files it stays the same after reboot.
3.I have Also tried flashing Eng-Hboot as PD98IMG.zip, But it skips that also.
4. I also tried to use this command Fastboot oem boot
And this is what i get:
C:\Program Files\Minimal ADB and Fastboot>Fastboot oem boot
...
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [ERR] boot image does not exist!!!
OKAY [ 1.418s]
finished. total time: 1.418s
I am begining to think that some how the partitions are corrupt or something.
PLEASE HELP ME OUT!!
@krook6023 The reason why i posted there also was because i wasnt sure what device it is wether its a DHD or INSPIRE 4G since it doesnt boot up and is stuck in bootloader,thats why i posted there also.Hope you understand and open the other thread incase someone over there has the answer to my problem.
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
spokanite said:
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
Click to expand...
Click to collapse
Thanks for your reply.But i tried 2. and made sure android-info.txt was appropriate, it just wouldnt flash. Looked like the partitions were corrupt thats why it wouldnt flash.
This is how it usually acts.
It finds the file, Loads the file on the upper right side of the bootloader with a green loading bar, after that, when its time for it to flash, normally shows up in red loading bar. It just moves as if it was flashing a 1kilobyte file. Then asks me to reboot.
After reboot nothing happens. Stays the same way.
But Right now, its even worse. After installing QHSUSB_DLOAD drivers, its refused to boot into bootloader ever since. but shows up as QHSUSB_DLOAD when connected to my pc.
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
bananagranola said:
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
Click to expand...
Click to collapse
I tried flashing CWM,TWRP,STOCK.... but non of them worked.
But as i said, after installing some drivers i found for QHSUSB_DLOAD, it no longer boots into bootloader.
But when i connect the device to a computer it only shows up as QHSUSB_DLOAD.
Any Help On that?
Nope, no idea. What drivers? From where?
bananagranola said:
Nope, no idea. What drivers? From where?
Click to expand...
Click to collapse
I found it on one of the threads.
at first, when the phone is connected to the pc, the charge light turns on and shows up as QHSUSB_DLOAD, but now no light or bootloader, just QHSUSB_DLOAD
Was it a DHD thread?
bananagranola said:
Was it a DHD thread?
Click to expand...
Click to collapse
Yea i guess so.
After the driver stopped the device from booting into bootloader, i read the README file that came with the driver and found out that it was for Some sort of Qualcomm Modem Device.
I guess thats why it bricked the device.
What thread?
bananagranola said:
What thread?
Click to expand...
Click to collapse
I cant seem to remember what thread it is. Cause I downloaded lost of the drivers from different threads. So I cant tell which one is from which thread.
Yeah, I don't think I can help you then.
Is it actually fully bricked yet? What exactly happen when you power on the device unplugged usb?
So I've read the other threads about this and tried pretty much everything what am I doing wrong?
1: type in "/k cd c:\" to switch from C:\Users\johan> to C:
2:C:\>adb\fastboot flash unlocktoken Unlock_code.bin (which gives error cannot open "Unlock_code.bin")
file is in C:adb along with:
adb.exe
adbwinapi.dll
adbwinusbapi.dll
fastboot
fastboot.exe
additional info:
the unlock file is only 1kb is this normal?
"adb devices" shows no devices but fastboot works don't know why
any of the above causing the problem?
I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).
HTCDreamOn said:
I assume you're simply trying to unlock the bootloader? Could you post more details please about your device, e.g. manufacturer, exact model, then I'll be able to help you. Also can you show me what guide you're following and exactly what you're trying to accomplish?
(I'm assuming you're missing drivers which is why I'm asking you for this info).
Click to expand...
Click to collapse
It's a HTC ONE S that I got and since I hadn't used android b4 I instead of doing a system update I updated some kind of CID that was on the phone which locked the phone in to "this build is for developers only..."
trying to bring it back to stock installing an RUU failed for some reason(the RUU being the one already in use since the phone is S-ON)
fastboot and adb drivers are installed, I can find my device in fastboot but not adb. enabling USB debugging should fix this but I can't enter the phone while it's looping and I've found no way of enabling it via cmd
this is what the phone shows while in boot:
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28 (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 is the RUU I tried running)
OpenDPS-v31.1.0.45.0815
eMMC-boot
Dec 14 2012. 17:10:57:-1
and correct I'm trying to unlock bootloader through htcdev then repeating the process and locking the loader, running the RUU again... if this doesn't work I guess I can go S-OFF (but then I need USB debugging) and picking any RUU see if that works
and prior to getting this phone I had never touched an android so I have 0 experience
I have downloaded the SDK and htc sync
tried following these guides:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
http://forum.xda-developers.com/showthread.php?t=1315947
and this is my original asking thread trying to get my phone back to stock:
http://forum.xda-developers.com/htc-one-s/help/help-purchased-dev-phone-accidently-t2813586
I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help!