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
Related
Hey everyone!
Basically I've got the HTC sensation (H Boot 1.27) & what happened was...
I rooted the phone & got clockwork mod recovery on it also without turning s-off.
Without backing up the rom (very silly of me) I did a full wipe on the phone to try flash a new rom but the rom wouldn't boot so I tried flashing a different rom & that wouldn't boot also so now i'm soo stuck & really neeed someone's help because I cant get the phone to work!
I was thinking that maybe someone who's on the same hboot as me could back up there system give it to me so i can try use there backup to start my phone?
Please XDA' people help me!
I'm willing to buy ANYONE a beer (via paypal) if they can help! :crying:
Flash the rom you want via clockwork, then when it's finished go to fastboot, connect the phone with usb to the computer and use ADB to flash the boot.img of the rom you just flashed
kgs1992 said:
Flash boot.img from the ROM manually from fastboot.
Put the boot.img from the zip file to your adb folder.
Connect your phone in fastboot USB
Open a command window
cd to the adb folder
for example:
Code:
cd c:\android
Then type:
Code:
fastboot flash boot boot.img
Then type:
Code:
fastboot reboot
Click to expand...
Click to collapse
Here is a guide for you for flashing with s on
After you follow the above instructions for the future
http://forum.xda-developers.com/showthread.php?t=1631861 from my HTC Sensation 4G using xda premium
TimMun said:
Flash the rom you want via clockwork, then when it's finished go to fastboot, connect the phone with usb to the computer and use ADB to flash the boot.img of the rom you just flashed
Click to expand...
Click to collapse
When i go on to fastboot with my usb in it doesn't show me my sd card contents (it doesn't get read in my laptop) is that normall?
zakiyyhaider said:
When i go on to fastboot with my usb in it doesn't show me my sd card contents (it doesn't get read in my laptop) is that normall?
Click to expand...
Click to collapse
yes its completely normal ..and just follow the guide linked by realsis above
Finally it works! thank you guys so much! :victory:
BUT there's still one MAJOR problem...WIFI does't work is there any way to fix this?! (I've tried the boot.img through adb thing already soo...)
zakiyyhaider said:
Finally it works! thank you guys so much! :victory:
BUT there's still one MAJOR problem...WIFI does't work is there any way to fix this?! (I've tried the boot.img through adb thing already soo...)
Click to expand...
Click to collapse
Enable smart flash and re-flash the rom
.. But don't do complete wipe.. Just do wipe of Dalvik + cache.. And re flash the rom
You won't lose a single spec of data and voila the WIFI works too
Sent from my pyramid.. Through blazing fast sonic waves
In November, I helped my friend unlock and root his T-Mobile HTC One S using Hasoon's All-In-One-Toolkit.
He left the ROM as stock, and hasn't uninstalled any apps or bloats.
A couple weeks ago he got the OTA message to update. When he hits the notification to proceed with the update, the following happens:
phone resets
clockwork mod recovery v5.8.3.1
finding update package...
e: unknown volume for path [internals dcard: download/OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.10-1.84.531.2_release_2978576yp8mjiw19tsxxey.zip]
e: can't mount INTERNAL SDCARDownload/OTA(tons of numbers).zip
His current software version is 1.84.531.2.710ORD, and he's on Android 4.0.3.
What needs to be done to enable the OTA update? I'm not near him, but I can talk him through it with Skype. I'm just not used to the HTC environment and terminology.
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
http://db.tt/YTK06p9b
how to install stock recovery
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
Click to expand...
Click to collapse
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Put the phone into bootloader.
Type in the following command in a command shell, opened in the adb directory: fastboot oem lock
espaniol said:
Can you please explain how to relock the bootloader and how to install the stock recovery.
shadowch31 said:
All he needs is to relock bootloader and install stock recovery, here is a link to download it from my dropbox..
Click to expand...
Click to collapse
Your friend will need to have the phone drivers installed and an adb/fastboot folder set up (similar to the "data" folder from Hasoon's All-In-One-Toolkit with fastboot, adb, etc.). Get the phone to the bootloader then go to fastboot mode and connect the USB (it should say "fastboot usb"). Now flash the stock recovery by running the following command in the terminal:
Code:
fastboot flash recovery stock_recovery.img
then lock the bootloader with this command:
Code:
fastboot oem lock
as Raptylos suggested
Click to expand...
Click to collapse
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
chmiela1991 said:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
Click to expand...
Click to collapse
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
Thanks flashing new boot helped
rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
I have the same problem, but i cant find the command in the bootloader
Noam_Nissel said:
I have the same problem, but i cant find the command in the bootloader
Click to expand...
Click to collapse
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
rzr86 said:
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
Click to expand...
Click to collapse
i don't fully understand what to do, can you be more detailed?
Noam_Nissel said:
i don't fully understand what to do, can you be more detailed?
Click to expand...
Click to collapse
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
rzr86 said:
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
Click to expand...
Click to collapse
i have this problem agian, and it doesnt help this time
Noam_Nissel said:
i have this problem agian, and it doesnt help this time
Click to expand...
Click to collapse
what kind of problem and what did you do now?
rzr86 said:
what kind of problem and what did you do now?
Click to expand...
Click to collapse
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Noam_Nissel said:
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Click to expand...
Click to collapse
i replied in the other thread
Does S-on and S-off matter for this issue?
Hi,
I am facing the same issue, my Sensation z710e is stuck in Cyanogenmod boot logo. following are the details.
bootloader unlocked
s-on
rooted
cwm recovery installed
tried latest CM10 for pyramid devices
I didnt try 'fastboot flash boot boot.img' command yet but i would like to know if s-on matters, my device is already rooted with cwm recovery.
I am having a similar issue as well. I have followed the instructions in this thread [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 18, 2014]. I have followed all the steps including doing a full wipe, flashed the ROM zip, gapps zip, and the aroma installer for the flash kernel several times with the same result. My screen keeps getting stuck on the white HTC loading screen.
Currently I have restored my phone to my previous ROM using a backup through 4ext recovery (v1.0.0.6 RC2). My HTC Sensation 4G T-mobile is unlocked and rooted with s-on. I have smartflash enabled on 4ext and my ROM is currently stock android 4.0.3. I did search the above mentioned thread for similar issues and a potential solution but none of the things I tried worked.
I would appreciate any help on how to fix this problem. If you need additional information I would be glad to provide it.
Tried another re-install today and everything worked fine, I guess the 5th time is the charm? I still don't know why it didn't work the other times, I did the exact same thing each time.
no access to recovery
I've got big problem. My One Mini is fine until I try to go into recovery. It refuses to go there.
I get fastboot and bootloader menus fine. It enters bootloader, but if I try to go into recovery, it just goes back to the main bootloader menu.
The problem started when I flashed CWMRecovery. Fastboot and adb recognise my phone, and accept commands, but when I try to fastboot flash recovery in it sends an error message. File not found.
I tried " fastboot boot recovery.img" but that just froze the machine .
When I try to get into recovery from rom manager or ROM toolbox pro, it takes me to the fastboot menu, not into recovery, and we're back to square one, as above.
Running android 4.3 Sense 5.5 software 2.12.401.1 Supercid 11111111
rooted and unlocked
To get the phone to work again, I have to hold power down for about 10 secs direct from fastboot/bootloader...may have to do this several times before it boots into Android.
If I turn power off from bootloader, it returns to bootloader when I power up again.
If I don't turn the phone off, once in main application, it's all OK.
Ho hum.
As I say , it works like a dream until I want to go into recovery.
Any ideas, please?
Thanks
Hi
Boblud said:
I tried " fastboot boot recovery.img" but that just froze the machine .
Click to expand...
Click to collapse
The correct command to flash the recovery is
Code:
fastboot flash recovery your_recovery_image.img
see also: wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Booting into recovery should be possible with
Code:
adb reboot recovery
I didnt tried CWM on the Mini, but used it on my old Marvel. I'm satisfied with TWRP for the Mini.
greetings
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Boblud said:
Yes, thanks. I know the commands should work...but that's the trouble..they don't!
I can get into the recovery menu...HBOOT /FASTBOOT / RECOVERY and so on, but selecting "RECOVERY" simply sends me back to HBOOT menu.
I can't flash anything under FASTBOOT, either. I've been doing this sort of thing for several years without trouble....until now!
So come on chaps..thinking caps on , please.
Click to expand...
Click to collapse
lock the bootloader RUU back to stock and start over ?
clsA said:
lock the bootloader RUU back to stock and start over ?
Click to expand...
Click to collapse
Thanks, will do when I can find ruu to download! Any pointers, please?
Uhm.... have u read Frequently Asked Questions by @KidCarter93 ?
KidCarter93 said:
[SIZE=+1]Q11: I have a custom recovery installed but I can't boot into it.[/SIZE]
Use the command - fastboot erase cache.
You should now be able to boot into recovery.
Click to expand...
Click to collapse
Maybe it helps.
Boblud said:
Thanks, will do when I can find ruu to download! Any pointers, please?
Click to expand...
Click to collapse
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
clsA said:
here's the RUU
http://www.androidruu.com/getdownlo...14_10.20.40.4408L_release_333483_signed_2.exe
Click to expand...
Click to collapse
Thanks for help all round.
The RUU wouldn't run: it reported an unknown error, but having done so, it must have done something, as when I rebooted, I had access to recovery once again...briefly! Then it went again.
Anyway, I re locked / unlocked , locked a few times, and hey presto, it's sprung back into life!
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.