Related
Hi i have a big problem with my new htc one s
i follow all instructions: clear data, factory reset, install rom, then install boot.img
Roms boot until it shows wallpaper and top toolbar with the battery icon and time, then can read preparing phone storage.... and an error appears asking me to wait or close system process
The rom restarts and stucks at this point dont know what else do, i try installing stock recovery and clear data factory reset and try install with 3 versions of recovery whith same result, have tried some different roms and its the same.
Wonder if anyone knows what i have to do solve this..
Thankyou in advance.
--------------------------
solution on post #7
Moved To Q&A
This is a development section, its not the place for questions.
Which roms did you try to flash? Did you flash the correct boot.img
Sent from my HTC One S using XDA
thanks for your answer
Yes i flash [ROM][ICS] |June 13th| Energy™ -.¸¸.·´¯ Blue with the boot.img from the downloads
and [ROM] Ir2 1.78.401.2 - HTC One S Stock ROM DUO [Deodexed-Updated-Optimised]
When finish flasing from recovery reboot on fastboot and flash the boot.img and always is the same result.
I've tried to change to stock version of recovery and wipe all, reset to factory default then flash custom recovery and start the process but is the same.
when i whipe from stock or custom version of recovery there isn't any error message.
thankyou very much.
you don't flash the boot.img from recovery--read OP
boot.img
I flash it from fastboot not installing a zip from recovery. I also try installing by script like on [ROM][ICS] |June 14th| Energy™ -.¸¸.·´¯ Blue that there is an script that makes the installation always from fastboot
[solved]
Hi, find a way to make my htc one s woking again
This is the solution:
first i've to change my CID because my phone is from ORANGE spain and cannot flash a official RUU.
for this i follow this tutorial
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Second flash stock recovery and lock boot
finally i've downloaded the last europe RUU, and execute it.The process works like a charm and in 15 or 20 minutes my one s was working again.
Now i have lock boot, stock recovery and unrooted phone and have one question:
for root my phone again have to unlock and flash a custom recovery, and then.....
should I need to put back again stock recovery and lock boot for working an official RUU?? or can work without problems with unloked boot an custom recovery?
Thanks in advance.
Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?
joemanbui said:
Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?
Click to expand...
Click to collapse
i too have same prob tried all kinds of ruu's. been trying for 14 hours if you find soething please report how you did it
I have the same problem any ideas?
anyone know of any gurus in the forum knows how to fix
I've been trying for a month
any rom to put loads and after a 10-20sec reset
For you with sd-card problems, have you tried to flash stock recovery and then boot to bootloader and choose clear storage? It worked for me.
If you installed a RUU, ofcourse you already have stock recovery.
Sent from my One S using Tapatalk 4 Beta
I have the same problem, and decided to work on it today... I can say frustratingly i've not had ANY success in getting past the screen that pops up with the lock ring on the bottom...I've tried RUUs , the clear storage ... what is going on... I'm S-off as well so i really don't get why this would happen.
One S (s4)
twrp 2.5
S-on
T-mobile US
CM10.2
kernel 3.4
Hboot 2.15
openDsp v31.1.0.45.0815
current raido :1.11.50.05.28_10.27.50.08L
using the getvar method
i get this
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__203
using fastboot getvar version-main
Version-main : ( BLANK)
Click to expand...
Click to collapse
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
boot into android and issue the 3 commands
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
Click to expand...
Click to collapse
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
I have the same problem..
qwerty warrior said:
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
I have the exact same problem did you ever figure out a way of fixing it?
qwerty warrior said:
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.
xxgummyxx said:
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.
Click to expand...
Click to collapse
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings
dosariland said:
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings
Click to expand...
Click to collapse
For about some days, I flash an RUU when I was still s-off and boot-unlocked, then I flash twrp-recovery, make the adb thinks with mmcblk* (dd flash) and flash again a RUU. As you can read here.
But same boot loop problem with "Preparing Phone Storage...".
Because dd flash (the mmcblk* file) under linux and with startet recovery did not solve my bootloop / prepairing sd card problem (I had still access to my sd card with twrp-recovery! All the time!) I really think about to enable s-on
I am only scared when I do:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
How can I re-enable s-off if my os still hangs on "Preparing Phone Storage" after putting s-on and try to flash an ruu to fix my bootloop/Preparing Phone Storage problem?
I did my s-off with rumrunner.
Would be very thankfull about help.
Greetings by I_did_it_just_tmrrow
you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
Click to expand...
Click to collapse
THX!!!
I leave superCID and it works! I hope my signal would be fine under stock.
THX a lot!
Greetings by I_did_it_just_tmrrow
Unlocking Bootloader
What you need:
PC
Phone
Installed HTC sync (phone drivers)
Unlocking "tool" (batch file and fastboot / adb files)
With unlocked bootloader you will be able to flash custom recovery needed for flashing ROM, rooting etc.
Guide:
Download unlock.rar from attachment
Extract contest of rar to your desktop
Restart your phone
When powering up, press and hold “Volume Down” to enter Bootloader
With volume up / down select “Fastboot” and select it with power button
You should see “Fastboot USB” on your phone screen
Run “Unlock bootloader.bat” from your desktop
Press “t” and confirm with enter to get token
Go to HTC Dev registration and register
Go to HTC Dev unlock bootloader
Select “all other supported models” on right
Skip all steps till step 9
Paste your token like shown in step 9
After some time you will receive E-Mail with Unlock_code.bin in attachment
Save Unlock_code.bin to your desktop
In “Unlock bootloader.bat ” press “u” and confirm with enter
On your phone you should see unlock menu, move with Volume Up and select with Power
That’s it, your phone bootloader should now be unlocked and ready to flash custom recovery.
Flashing Recovery
After you are done with unlocking bootloader you can flash custom recovery.
Recommended recovery for HTC One S Ville C2 is TWRP, because it is most stable one that works with device.
You can use Superboot to root your phone and than install Goomanager from play store and flash TWRP from it
or you can try this:
download latest TWRP recovery from HERE (one with villec2 in name is the one you need)
download attached recovery flashing utility and extract content to your desktop
rename recovery image to twrp.img and place it on desktop (or location where you extracted flashing utility)
reboot your phone into fastboot (restart it and while starting press and hold volume down, when in bootloader press power to enter fastboot mode)
run flash-recovery.bat
press f and confirm with enter
your recovery should now be flashed and you can enter it by selecting recovery from your bootloader screen (volume up / down to navigate, power to select)
Flashing custom ROM
After you have unlocked bootloader / installed custom recovery you can flash custom ROM
After you have found ROM that you would like to flash and saved it on your phone this are the steps you need to take:
reboot into recovery
wipe data (factory reset) and cache
go back chose "install"
locate ROM you have downloaded to your phone
after rom has been installed reboot into fastboot
now you need to flash boot.img
Boot.img is usually included inside ROM .zip file, but since ONE S has S-ON it cannot be flashed from recovery but you need to flash it from fastboot.
Click to expand...
Click to collapse
download fastboot files from attachment and extract them to c:/fastboot
Start cmd (win+r -> cmd)
in cmd:
cd\
cd fastboot
fastboot flash boot boot.img
fastboot erase cache
reboot phone
HBOOT versions and ROM compatibility
Not all ROMs are compatible with all HBOOT versions.
Minimum required HBOOT version for flashing SENSE based, android 4.04 or 4.1.1 (JellyBean) ROM is 2.11 (you will get it with official 4.0.4 OTA update).
You can run older versions of Sense based ROMs (4.0.3) on newer hboot versions.
This does not comply to AOSP ROMs
Thank you, great how-to.
As i made my phone ready for New Roms i stucked at TWRP. If anyone else has problems there. Try this after unlocking bootloader
http://forum.xda-developers.com/showthread.php?t=1788974
And install goomanager from play store and install open recovery
AW: [HOW TO] Unlock bootloader, root, flash custom recovery, rom ..
Good job.
This should answer a lot of questions for new users
Sent from my HTC One S
Elias96 said:
Thank you, great how-to.
As i made my phone ready for New Roms i stucked at TWRP. If anyone else has problems there. Try this after unlocking bootloader
http://forum.xda-developers.com/showthread.php?t=1788974
And install goomanager from play store and install open recovery
Click to expand...
Click to collapse
i'm not sure will superboot work with devices upgraded to 4.1 (or if any one even ships with 4.1) but i will add it as option in OP
Great one! Just to get ti to stick
Any requirements/restrictions for all this due to branding, android version, cid?
should work with all devices
Nice job:good: Sticky
I'm on VIP Serbia 4.0.3 stock rom, and I don't have any updates through software update on phone. Bipe wrote me in mail that it should be at least 4.0.4 software to be sure that this would work. Any workaround? Like debranding or flashing internatioal stock rom?
4.0.4 is needed for JB based custom ROMs to work
If you don't have OTA update you can try flashing 4.0.4 RUU
Forgive my noobness,
ruu is an offline pc update tool? Folowed the links and got to site hosting files:
PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916.zip
And
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed.exe
I suppose one is an update (zip) and the other is full rom, and that both are 4.0.4.
Should I try to install just update or full? And is the update flashable zip to be installed through stock recovety?
Sent from my HTC One S using Tapatalk 2
Cayman.n2o said:
Forgive my noobness,
ruu is an offline pc update tool? Folowed the links and got to site hosting files:
PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916.zip
And
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed.exe
I suppose one is an update (zip) and the other is full rom, and that both are 4.0.4.
Should I try to install just update or full? And is the update flashable zip to be installed through stock recovety?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
its best to use ruu, but ensure make a full backup of data through twrp because ruu will erase all user data, secondly for ruu you will need to relock your bootloader. After your phone is updated, unlock your bootloader again.
I haven't done anything to my phone yet. Its stock as it can be So no twrp, unlocked bootloader or so.
When you mention backing up data, you mean rom and such?So if (hope it won't) anything goes wrong with ruu, I can restore phone to a present state? I have all I need synced and copied to my pc that would be called "user data".
Cayman.n2o said:
I haven't done anything to my phone yet. Its stock as it can be So no twrp, unlocked bootloader or so.
When you mention backing up data, you mean rom and such?So if (hope it won't) anything goes wrong with ruu, I can restore phone to a present state? I have all I need synced and copied to my pc that would be called "user data".
Click to expand...
Click to collapse
ok so go with ruu and just be sure that the CID of ur device is supported with RUU that u r going to flash and if there will be some error it will give prior to flash so most probably nothing should go wrong
How to know which one should I use? On villec2.info folowed the link to this: http://www.androidfiles.org/ruu/?dir=VilleC2
There are few europe ruu files, just want to be sure... The Europe_2.15.401.100 seams to latest. Also how to check the CID compatibility? My CID is HTC_032 (got it by CID Getter app from store)
Hope this will clear things out for you:
x.xx.401.x - World Wide English (WWE):
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
x.xx.709.x - Asia TW (Taiwan)
cidnum: HTC__621
x.xx.720.x - Asia (India)
cidnum: HTC__038
(x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
(x.xx.708.x - Asia HK (Hong Kong)
cidnum: HTC__622
Click to expand...
Click to collapse
what you need is the one with "x.xx.401.x" in name, latest version
Hello everyone!
I have updated my phone to 4.0.4 using ruu. Now I'm going to try to flash recovery and root it.
Anyone tried and sucsseded in flashing stock 4.0.4 after using some custom 4.1.1 roms? I would love to try out some custom roms but it would be nice if I could get back 4.0.4.
Cayman.n2o said:
Hello everyone!
I have updated my phone to 4.0.4 using ruu. Now I'm going to try to flash recovery and root it.
Anyone tried and sucsseded in flashing stock 4.0.4 after using some custom 4.1.1 roms? I would love to try out some custom roms but it would be nice if I could get back 4.0.4.
Click to expand...
Click to collapse
You can go back to stock just don't forget to make nadrod backup first... Or if you don't you can always use RUU
Sent from my HTC One S using Tapatalk 2
I have the one-s with (Serbian Telenor) Android 4.0.3 (soft. 1.11.401.110) , Do I have to install this first (EXE file) RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
or this one first (zip file) : PJ4020000_OTA_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100-1.11.401.110_release_2865916
and then do with the update zip file OTA_VILLEC2_U_JB_45_S_HTC_Europe_3.17.401.102_16.22.20.03U_16.11.20.24_M_release_305849f16hjx6h6neosbyn
most probably ruu will give error
bilal_liberty said:
most probably ruu will give error
Click to expand...
Click to collapse
Why do you think that ?
Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.
What stock Rom did you chose?
Try to flash the RUU
Old.Splatterhand posted the correct link.
Gesendet von meinem HTC One SV mit Tapatalk
Fabian2103 said:
What stock Rom did you chose?
Try to flash the RUU
Click to expand...
Click to collapse
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
mrrrdude said:
Hi,
I have an HTC ONE SV and i tried to flash a stock rom but i haven't any experience with it, and now my device is stucked in boot loading screen.
For what i understand i can install a new stock rom with fastboot because also my recovery mode is corrupted and factory reset as well because when i try to enter it remains in "Loading Recovery Mode boot screen". Could someone help me with a fix and a stock rom for:
K2_UL XC SHIP S-OFF RH
CID - 11111111
HBOOT- 2.19.0000
RADIO - 1.15.49a.00.07
Also i have S-Off as you can see from above and Bootloader Unlocked.
Thanks,
I hope that someone can help me.
Click to expand...
Click to collapse
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.
old.splatterhand said:
Not so fast, before you tell people to use a RUU, tell them also, how to use. Otherwise people could be lost.
I think it could be solved without RUU.
It seems (because of your hboot), you had already the update to Android 4.2.2? Can you tell us which software you were running? Or if you are using an european k2ul? Or any other information could be important.
Please try to use/flash this recovery for flashing a rom:
http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
You have to flash with fastboot. It is made to work also on your hboot.
Click to expand...
Click to collapse
I don't really know if i had the update to Anroid 4.2.2 in Fast Boot Menu it sais OS-3.03.401.1? does that help you? and i think it's an european k2ul. After i flash this recovery image? what do i do next? i mean i want to revert the phone to stock but like i said the Recovery menu dosn't load is there any way to flash the recovery image and then install a stock rom through flasboot commands? i have found this post http://forum.xda-developers.com/showthread.php?t=2277112 and it sais that it's possible but i didn't have the recovery image, now i do but i'm still missing a stock rom that would work with my device.
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Thank you, i will try this out and i will let you know if i make any progress
mrrrdude said:
Thank you, i will try this out and i will let you know if i make any progress
Click to expand...
Click to collapse
old.splatterhand said:
You had an older recovery, which don't work with your hboot.
Flash the recovery i have linked for you with fastboot, then you should be able to enter recovery.
From recovery you can flash the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from here. It's a stock rom, with the same software number as you have had.
Click to expand...
Click to collapse
Hi,
The phone now boots into recovery so i'm on the right track thanks to you, but i don't know how to flash the stock rom? what do i need to do? i put the stock on a sd card and plug it in through an external cable and a card reader but i don't seem to find where is the file? Do i need to flash the boot.img from the zip file too? or rename the zip file somehow in the sd card?
You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.
old.splatterhand said:
You have to flash it from recovery.
First go (in recovery) to "Wipe"-> "Advanced Wipe" and wipe everything but sd card and internal sd card.
Put the rom on your sd card, choose "Install" and navigate to the k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip.
Choose it and confirm with"Swipe to flash".
As you are S-off, you usually don't need to flash boot.img afterwards.
When flashing is done, Reboot.
Wait some minutes, first boot takes some time.
Click to expand...
Click to collapse
It fails to wipe with this error: E:Unable to mount internal storage. do i need to place the sd card inside the phone?
Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.
old.splatterhand said:
Hmmm, strange. Yes, put your sd card into your phone. If the rom is there, you can't find it, if its not in the phone.
Go on and try to flash.
Click to expand...
Click to collapse
I found my rom on the sd card but after a few seconds the installing fails because of the same error "unable to mount internal storage" is there a way to flash this rom through fastboot?
No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
old.splatterhand said:
No.
Seems, something got corrupted on your device.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.19.0000
version-baseband: 1.15.40a.00.07
version-cpld: None
version-microp: None
version-main:
version-misc: XC SHIP S-OFF
meid:
product: k2_ul
platform: HBOOT-8930
modelid: PL8010000
cidnum: 11111111
battery-status: good
battery-voltage: 3909mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0049fc265e
hbootpreupdate: 11
gencheckpt: 0
Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.
old.splatterhand said:
Ok, i see what i wanted to see.
Because the rom will not flash, you should really try to flash the RUU.
To do that, you need to downgrade your hboot.
Please read and follow this guide, to downgrade hboot and flash the RUU afterwards.
Click to expand...
Click to collapse
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials? because i can't do that because my device is only recognize in fastboot. when i hit the command adb devices my serial number is not shown. but in fastboot device is. or if i use command like su in adb i get an error message like this "error: device not found"
mrrrdude said:
Do i really need to change the supercid to downgrade the hboot as mentioned in the tutorials?
Click to expand...
Click to collapse
Supercid is fine, no need to change it.
old.splatterhand said:
Supercid is fine, no need to change it.
Click to expand...
Click to collapse
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!
mrrrdude said:
It WORKED LIKE A CHARM! THANK YOU! you are a real life saver! I could not have done it without you, thanks allot!
Click to expand...
Click to collapse
Nice, so have fun with your new born device :laugh:
old.splatterhand said:
Nice, so have fun with your new born device :laugh:
Click to expand...
Click to collapse
Thank you, i will definitly
Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!
Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?
same
i've ****d mine to lmao
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!
If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.
Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?
Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way
Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..
Hi everyone! Have a big problem with wife's HTC ONE SV K2UL. In the start he has official last ROM with no root, s-off and other things. In one fine day he starts work with a tons of lag's, restarts after boot and write message about “System force close”. I read many post's here and other forum and try to upgrade to custom firmware. Yes, of course I do unlock and flash TWPR, can't s-off cos don't have stable working firmware, try to write SuperSId, but w/o root it didn't work. Then I try different rom's: viper, simple etc (yes, I flash with "fastboot flash boot boot.img", cos S-ON) But every time have the same problem with lags and restarts. Try to flash RUU, but have errors: "12 signature verify fail", when boot lock and "99 signature failed" when tempered or unlock. In the end I try to use SimpleRom v4 with mod f2fs. It's starts, but haven't root, say that he lost binaries. Try to CHMOD 755 System folder, use TWPR to flash different *.zip with SuperSU and SuperUser, but the path /system/bin/su /system/bin/.ext/.su /system/xbin/su are empry anyway.
Now have: Unlock (TEMPERED), TWRP 2.7.1.1 (f2fs), HBOOT 2.00, S-ON, NO supercid, SimpleROM v4 + f2fs, NO root.
It's also restarts and don't work properly. What method's I can try to restore my fully worked HTC One SV.
P.s Sorry for my bad Eng and thx a lot for helping.
I would try a stock rom first!
SimpleROM is highly modded. Give this one a try. Moonshine S-off should also work with it.
To think about other steps we need more information.
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
And maby explain your restart (after reboot?) issue a bit more detailed.
old.splatterhand said:
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 3818mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Today I will try to flash ROM from your link. Thx.
Yes, flash it and see how it works. If your problems are still there, you should try moonshine to get S-off. Then you should be able to downgrade hboot and run the RUU.
After installation official rom from link I have message:
"Setup isnt't responding. Do you want to close it?"
"Process system isn't responding. "
After boot, when I try to move circle for unlock phone, i see green HTC on white and after some second's it's restarts. Can't do anything.
P.s Lock screen also be on black pole (
Never had such message.
Have ypu done already the update to 4.2.2?
I would try another rom to noot, but if all get such problems, i think it is the phone itself.
Usually the roms which are released, don't have such big problems and if they really have, devs are working on a solution.
Hi there!
Any news related to the problem? I have exactly the same problem (problem show up after doing factory reset, before that almost a year past by using it with absolutely no problems, of course didnt perform factory reset before, rom was stock 4.1.2, CID htc_032)HTC one SV k2ul stuck at htc logo, able to enter bootloader, unlocked at HTCdev, flash TWRP, tryed several roms (flash over recovery, flash boot.img with fastboot, wipe cash...cose I am S-on). First time it boot up OK (everything is working), but after turning it off, and power it back on, it stuck at lock screen. When unlock it show white htc screen, and after a while show "system not responding.......". Sometimes factory reset over recovery bring the phone up, working normaly (sometimes), but if no luck with factory reset, only thing is flash again rom and it work...until next reboot (what is needed for S-off). Im on k2ul_JB_2.14.401.6_stock_odexed_03_06_13 , and I have tryed Saturn III v1.20 (after first boot all OK, day after mobile data not working, boot problem same like rom mentioned before) and k2ul_4.2.2_3.11.401.1_stock_odexed_v3 (booting problem less expressed, booting normaly after "power down" with power button, stuck only after rebooting from adb, sound while calling heavily distorted....).
So, any idea what went terribly wrong after factory reset??? Why the system is not responding after reboot (what is blocking it, or where is gone???) And, how to fix distorted in call sound on 4.2.2. rom with S-on, and no superCID?
Please help me get my HTC working normally!
thx in advance
To update firmware to the newest do the following:
- relock your bootloader
- download this http://fotadl.htc.com/OTA_K2_UL_JB4...2.14.401.6_release_338297mseg08soslxcubit.zip and extract firmware.zip to your pc.
- rename firmware.zip to PL80IMG.zip and copy to your ext sdcard
- boot to bootloader and confirm to flash with vol+
- reboot to fastboot mode and unlock your bootloader (usually you can use the unlock token from first time)
After firmware has flashed, you have no TWRP anymore and your old rom will not boot.
So, best is to download a 4.2.2 rom for your device and copy to you sdcard before.
And also grab the latest (!) TWRP from my index thread, because you need to flash this right after firmware in fastboot mode.
Hi there!
First, thank you for your answer!
so, I have to:
-relock bootloader (enter bootloader, fastboot, open adb, fastboot oem lock)
-extract firmware, rename to PL80IMG.zip, put on sd, reboot to bootloader (I have try once to downgrade hboot with PL80IMG, but it didnt ask vol+ to confirm, blue vertical bar in right corner filled up and bootloader starts, is that OK, or not, I mean, not asking vol+ to confirm?)
-unlock bootloader, flash TWRP recovery
-go in recovery (perform any wipe?), install from sd (perform any wipe after install finish?)
-what after instaling rom from recovery? I am S-on, do I need to take out of rom boot.img file, go to fastboot, and flash again boot.img?
thx in advance
The answer is inside the quote:
1vanK said:
Hi there!
First, thank you for your answer!
so, I have to:
-relock bootloader (enter bootloader, fastboot, open adb, fastboot oem lock) Lets say: open cmd, not adb. But i think you mean the right step.
-extract firmware, rename to PL80IMG.zip, put on sd, reboot to bootloader (I have try once to downgrade hboot with PL80IMG, but it didnt ask vol+ to confirm, blue vertical bar in right corner filled up and bootloader starts, is that OK, or not, I mean, not asking vol+ to confirm?) Downgrade hboot is not possible with S-on, maybe that was the reason. Usually it asks to confirm, but if not it should be ok also. It is no modded file, it is firmware by HTC.
-unlock bootloader, flash TWRP recovery
-go in recovery (perform any wipe?), install from sd (perform any wipe after install finish?) Only wipe before, not after. A backup before the wipe does not hurt also.
-what after instaling rom from recovery? I am S-on, do I need to take out of rom boot.img file, go to fastboot, and flash again boot.img? The boot.img is inside the firmware.zip. It depends on the updater script of the rom you are using. Some wipe the partition with boot.img, some not. Try first without, if phone does not boot, flash boot.img.
thx in advance
Click to expand...
Click to collapse
All depends that you have an k2ul and the cid matches the android-info.txt inside of firmware.zip!
Hi,
right after flashing PL80IMG you provided everything start to work ok :good: ! Even rom that was currently on (4.1.2) reboots ok (didnt stuck like before). But, no matter what, I carried out all steps from previous post, an I am now on 4.2.2, and all is so far running great (try to reboot several times, with power button, from fastboot, from recovery,factory reset... didn stuck at htc screen at all, and no distorted sound during calls)! Thank You so much!!!
Any way, even "so far so good", I wonder, what was wrong? Why everything crashed last time after factory reser (on stock, no root, locked)?
I guess there is no way to get superCID on 4.2.2? What about S-off?
Thank you very much on provided link! :good:
Great news. Happy to help!
What was wrong, hard to tell, if we don't have your device here.
You can get S-off with http://rumrunner.us then Supercid.
old.splatterhand said:
Never had such message.
Have ypu done already the update to 4.2.2?
I would try another rom to noot, but if all get such problems, i think it is the phone itself.
Usually the roms which are released, don't have such big problems and if they really have, devs are working on a solution.
Click to expand...
Click to collapse
Yeah, on start i have full stock rom 4.2.2, now have ROM from your link. This message's be in all rom's which i flash to my htc.
MakOS said:
Yeah, on start i have full stock rom 4.2.2, now have ROM from your link. This message's be in all rom's which i flash to my htc.
Click to expand...
Click to collapse
It is important to use the firmware from the OTA update with the rom version, means: if you want to use a 4.2.2 rom, you need the firmware from 4.2.2.
If you want to use a 4.1.2 rom you need the firmware. So please don't mix that.
Have you already done (some time ago) the OTA update to 4.2.2?
I would be no surprise, if you use 4.2.2 rom on 4.1.2 firmware and you get errors.
old.splatterhand said:
It is important to use the firmware from the OTA update with the rom version, means: if you want to use a 4.2.2 rom, you need the firmware from 4.2.2.
If you want to use a 4.1.2 rom you need the firmware. So please don't mix that.
Have you already done (some time ago) the OTA update to 4.2.2?
I would be no surprise, if you use 4.2.2 rom on 4.1.2 firmware and you get errors.
Click to expand...
Click to collapse
Yes, on start it have 4.2.2 OTA update. But i try to flash 4.2.2, 4.2.1, 4.1, try all link, but anyway have the same message's. Want any stable w/o error's firmware, cos now it not work properly ((
Hi there,
so now i have managed some how (I don`t know how) to brick my one sv. I was moving TWRP folder with backup files from PC to phone internal storage, got ext4 error, and phone just died... no lights on charge, no bootloader, nothing.......
When I reconnect USB it is detected as QHSUSB_DLOAD device, so that indicates that there is no more bootloader... I was reading that this is fixable (without jtag box), there was explanations how to do it for sensation, and M7, but there is nothing for ONE sv...
Can U help me with advice??? How to get bootloader back on rolling???
THX in advance!!!
Sorry, no idea. If you have guides for other phones you should look there, i guess.