Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247
Related
Hi,
I also got my DS ( S-off) stuck in bootloader ( 6.98.1002 ).
I have goldcard installed !
I followed the guide from "amidabudha" for flashing the ENG bootloader via adb and all wen't well until....my PC did :
sending 'hboot' (1024kb).....
OKAY ¨[ 0.188s]
writing 'hboot'...
Now waiting for ever ????
What am i doing wrong ?
Grts
Patrick
PS: I am on Revolutionary.
Are you sure that you are using adb dd commands?
or this is the fastboot output?
also before flashing RUU make sure it is the proper version
Hi,
I don't know exactly the difference between the two, but i think fastboot.
I get the serial from the DS by typing 'fastboot devices' so i think fastboot.
When disconnecting the USB i get :
FAILED (status read failed ( to many links))
finished.total time:507.781s
It's like the PC makes connection with DS but can't transfer the data.
Goldcard has nothing to do with htis i assulme ?
Maybe i should install 4EXT first over the revolutionary ?
Revolutionary works but installing from SD is always aborted , so i can't install via SD card.
I get also the "unmount errors" , but accordingly the guide on XDA the chip isn't fried.
And what are you trying to do?
Why do you need this GoldCard?
Return to stock?
Or just replace the bootloader?
Or something else?
Truying to get my DS unstuck.
The gold card is from my older DS i unlocked with XTC clip , i have removed it already.
I have tried to flash 4ext and the same problem ??
PC staying on " writing recovery ......" and PC and HTC freeses.
How did you got stuck?
And most important - have you pulled your battery out?
How did you got stuck?
Its second hand so the guy told me by doing a download , but .....
And most important - have you pulled your battery out?
Yes , I know its very bad but the only way to stop the DS
Sorry , it was by installing an app.
Still not clear - what download? Maybe update?
So it stuck while installing an app?
So you didn't had a custom recovery like 4EXT before or you did?
What's the difference between fastboot end the dd commands ?
Cauf said:
What's the difference between fastboot end the dd commands ?
Click to expand...
Click to collapse
to make fastboot command you have to be in bootloader (white screen with 3 android guys on skateboards and text in several colors). To use adb and adb shell commands (which includes "dd") you have to be in recovery
So it stuck while installing an app? Yes
So you didn't had a custom recovery like 4EXT before or you did?
Yes, revolutionary,and this works , but when i try to install from SD card it's allways aborted .
It's like the phone allways freezes and the only way to reboot is disconnecting the battery .
Have you tried the "wipe cache" option from the recovery? Then reboot if you have not flashed anything yet (like other ROM or smth.) it should boot fine
white screen with 3 android guys on skateboards and text in several colors
Thats the screen i am in when i try to flash the IMG files via command prompts (adb).
It says in red FASTBOOT USB
Is this ok ?
Have you tried the "wipe cache" option from the recovery?
I just did.:
Cache wipe complete
and then 2 can't open.... and 2 can't mount..... errors
Then reboot if you have not flashed anything yet
This of course i am not sure what the previous owner has done.
Cauf said:
Have you tried the "wipe cache" option from the recovery?
I just did.:
Cache wipe complete
and then 2 can't open.... and 2 can't mount..... errors
Then reboot if you have not flashed anything yet
This of course i am not sure what the previous owner has done.
Click to expand...
Click to collapse
Ok. Now open the [GUIDE] Read this before going for eMMC replacement. and start reading carefully. Good luck. If any questions - post here
Ok, replied in the "guide" forum.
stuck in bootloop.
hboot info:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.06es.50.02.31
OpenDSP-v29.1.0.45.0622
eMMC-BOOT
Jun 11 2012, 14:36:28
cid is HTC__001
was on stock god knows which rom, left phone on overnight, woke up in the morning and phone was off. turned it on and it's stuck in bootloop. so i thought if i could root the phone, I could install a rom through CWM. unlocked the bootloader via htcdev, fastboot flashed CWM, tried booting into CWM and it just boot loops. i then ran out of the little amount of battery i had left, and couldn't charge the phone because of bootloop. so flashed stock recovery to get phone to charge. relocked the bootloader and tried flashing "RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed", flashed successfully but still bootloop. tried flashing an older version, RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed, didn't flash due to older hboot.
unlocked bootloader again and tried HTC One S AIO Kit by Hasoon, flashed CWM and still stuck in bootloop. flashed TWRP and also stuck in bootloop. running out of ideas here
at the moment, I still have access to bootloader. anyone have any ideas?
thanks in advance
but can u go into the bootloader mode ???
acerulz said:
but can u go into the bootloader mode ???
Click to expand...
Click to collapse
thanks for replying so quick!
not really good with my terms. i'm guessing bootloader mode is vol dn + power?, yes i can get into that. and i can see device in fastboot aswell when i type "fastboot devices"
so simply your phone is not bricked mate, read the posts and you'll get to it very quickly.
Wish u luck
drakexpl said:
so simply your phone is not bricked mate, read the posts and you'll get to it very quickly.
Wish u luck
Click to expand...
Click to collapse
ok that's a relief. can you direct me to which post? i've read through soo many and tried soo much but always failed
kid_maximus said:
ok that's a relief. can you direct me to which post? i've read through soo many and tried soo much but always failed
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1599363
in fastboot, either reflash recovery or erase cache
thanks for the replies :good:
fastboot erase cache doesn't look like it did anything, still bootloops
i tried flashing the CWM recovery i had again via fastboot, didn't work, still bootloops when i try accessing recovery. grabbed the CWM and TWRP recovery images from HTC AIO kit, tried flashing them with fastboot, still nothing stuck in bootloop.
although once i did flash the recovery image, the htc logo screen changed in that there is now red writing underneath it:
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action", after a minute, the screen goes off for 5 seconds and comes back with standard htc logo and bootloops.
any other ideas? :crying:
thanks again.
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
k1llacanon said:
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
Thats a little overkill IMO
You should be able to
fastboot flash recovery pathtoyourtwrprecovery.img
boot into recovery factory reset install a rom
reboot
and you should be ok
k1llacanon said:
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
tried that many times, but i'll try again and write what happens
i've done fastboot oem lock, it says:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.942s
i'm guessing that's right because it's gone from "unlocked" to "relocked" in bootloader, including "security warning" added underneath it.
(erased the cache next using fastboot)
ran the RUU, completed successfully, no errors...phone rebooted, still bootloops
can still access bootloader
ran the RUU again, this time as administrator...completed successfully, no errors...phone rebooted, still bootloops
still have access to bootloader and working fastboot.
there must be some way to fix this
Zarboz said:
Thats a little overkill IMO
You should be able to
fastboot flash recovery pathtoyourtwrprecovery.img
boot into recovery factory reset install a rom
reboot
and you should be ok
Click to expand...
Click to collapse
you are sooo right, if only i could access recovery, i know what to do
but the problem is, i can't...i've tried atleast 15 times if not more to flash as you said using fastboot, cwm twrp and stock recoveries, using many files (to rule out having a corrupted recovery img) and using the HTC AIO kit too to flash recovery, always bootloops
as i said, i tried to fastboot flash the recoveries provided with the HTC AIO kit, this also bootloops.
do you have any other ideas? i'd appreciate anything rather than using this as a paperweight lol
So...i purchased a HOX on Sunday and it was all working fine on straight talk not long after i got home with it. I was sick of the bloatware so i went to load a custom ROM (i've rooted/rom'd the Fascinate and RAZR before, i'm not totally clueless) and made the awful mistake of flashing an endeavoru ROM on my evita phone (at&t) along with an incorrect recovery. I didn't realize my mistake at the time and wiped cache/dalvik/factoryreset/ and system to try and install a different ROM. After failing to load that i tried other ROMs and somehow my sd card became corrupted. I tried to read many many threads (worked around 7 hours on this) to fix the sd card issue including:
http://forum.xda-developers.com/showthread.php?t=2092721
http://forum.xda-developers.com/showthread.php?t=1936198
http://forum.xda-developers.com/showthread.php?t=1942519
http://forum.xda-developers.com/showthread.php?t=1630459 post #8
I have tried to relock the bootloader, cmd shows:
C:\fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.940s
After doing that however it still says RELOCKED in fastboot, although under that is has Security Warning so apparently it still worked. Then i tried running "htc_one_x_RUU_2.20.502.7_att_us_08022012", Version is 1.0.6.2012 on the 'HTC Android Phone ROM Update Utility', it says my current image version is 2.20.502.7. After hitting 'Update' on that it says it will update to image version: http://i.imgur.com/IwD2nIQ.png. The program runs into ERROR [132]: SIGNATURE ERROR which i also can't seem to fix (it says to get the correct ROM Update Utility and try again but i'm pretty sure i have the correct one..). Here is the fastboot version and CID along with a failed recovery: http://i.imgur.com/wmg93YT.png
Once i realized my first mistake i put the correct recovery back on my phone. I even tried to sideload a rom onto the phone but it got stuck in CMD on 6% nearly instantly. I also have formatted the sd storage at least 3 times in windows.
So the current situation is:
- No OS installed. Phone gets stuck at HTC screen with red writing upon normal boot.
- Bootloader is accessible.
- TWRP 2.3.3.0 is installed and accessible through recovery.
- Can't install any ROM because the unable to mount /data error. When wiping dalvik i also get "E:Unable to mount 'cache' "
- Tried to format at least 3 times, no error in windows from formatting; sd card has no files on it in windows currently
- I've tried to push the TWRP recovery onto the device again, it works but nothing is fixed.
- Using Windows 7 64bit, HTC One X AIO Kit v2.0,fastboot tool
- Phone can be unlocked/relocked, however with an error in cmd (see above).
- Every program has been run 'as administrator', no change in result.
- Phone is recognized as 'My HTC' under 'Android USB Devices' in windows, so drivers should be correctly installed (not that i haven't tried uninstalling those twice already..)
Bootloader info:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Any help is greatly appreciated. Hopefully i've not made any noob mistakes (nice registration video btw..) since i have searched already for this problem, although it is most likely something i missed.
**Update**
Ran through the Nocturnal guide for corrupted sd card and it seems to have worked. Was able to install the cm10 nightly ROM but it failed from a symlink error. Installed evita Avatar ROM instead and it has been booting up for the last 4 minutes, will update on whether or not that works.
http://dl3.htc.com/application/htc_o...s_08022012.exe download this ruu, if it doesnt load then the download link is in post 9 of the second link below,i think you are using the wrong ruu. You have to have the same ruu for the phone version...2.20 ruu for 2.20 firmware.
http://forum.xda-developers.com/showthread.php?t=1956258&page=2
if that doesnt work read through that thread, i had the same problem as you when i first started, your phone is fine...as long as you can get into bootloader and recovery, your phone is ok..
Relock your phone again by the way (fastboot oem lock) from fastboot, if it says relocked..then it is locked again. run the ruu in fastboot as well, if that does not work try running the ruu in bootloader.
Ruu should work if you do it right...If it doesnt work.
Alternative, wipe your phone data,cache, dalvik and THEN flash boot img of a rom and LASTLY install a rom,
WhatTheAndroid? said:
http://dl3.htc.com/application/htc_o...s_08022012.exe download this ruu, if it doesnt load then the download link is in post 9 of the second link below,i think you are using the wrong ruu. You have to have the same ruu for the phone version...2.20 ruu for 2.20 firmware.
http://forum.xda-developers.com/showthread.php?t=1956258&page=2
if that doesnt work read through that thread, i had the same problem as you when i first started, your phone is fine...as long as you can get into bootloader and recovery, your phone is ok..
Relock your phone again by the way (fastboot oem lock) from fastboot, if it says relocked..then it is locked again. run the ruu in fastboot as well, if that does not work try running the ruu in bootloader.
Click to expand...
Click to collapse
OK thanks. The RUU you linked is giving me a 404 error. I've got Avatar working on it now but....sorry to the developer...its hideous, so i need to find another .
spectrum8 said:
OK thanks. The RUU you linked is giving me a 404 error. I've got Avatar working on it now but....sorry to the developer...its hideous, so i need to find another .
Click to expand...
Click to collapse
What is the Nocturnal guide for corrupted sd card ?
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?
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!
kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
I'm on the same boat as you... Any news?
wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.
zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...
OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.
What is this?
Failed to mount '/cota' (invalid argument)
AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.
i have the same problem. had you worked this out ? what's the solution ?
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)