[Completed] Chicken & Egg problem un-soft-bricking HTC One S - XDA Assist

Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

XDA Visitor said:
Hi Guys
I'm working on reviving a soft-bricked HTC One S (tmobile, I suspect S4)
I am unable to install any android ROM that I have been able to find, because HBOOT is still version 1.14, and they all require a higher version
TL;DR;
I think I just need a ROM that will install on a HTC ONE S (ville) for HBOOT version 1.14
I'm using an OSX machine, so I don't have the ability to run RUU.exe files. (is there a way to do this?) Attempts at flashing wiht RUU.zip have uniformly failed.
My attempts to upgrade HBOOT via the firmware upgrades with "fastboot flash zip <file>" have not had any luck, I suspect because the phone
is still S-ON (More or less following this instruction set http://forum.xda-developers.com/showthread.php?p=39216236#post39216236 )
My attempts at to remove S-ON using this explanation ( http://forum.xda-developers.com/showthread.php?t=2155135 ) haven't had much for potentially one of two reasons:
Possible reason #1) Step 6 calls for a "fastboot oem boot", which then tries to boot, but there is no working android install. I tried working around this by calling "fastboot oem gotohboot" instead and then booting into recovery (TWRP).
possible reason #2) adb shell doesn't seem to have access to su for me. ("adb shell su" returns "/sbin/sh: su: not found"). I have been assuming that this is the actual problem. I am assuming that this is because I don't have superuser access.
The SuperBoot package doesn't seem to work ( I grabbed it from here http://loadbalancing.modaco.com/download.php?file=r1-ville-superboot.zip referred by http://www.android.gs/root-htc-one-s/ ). I *think* it doesn't work because there is no android version to boot into.
So in short it seems that:
Android requires higher HBOOT requires S-OFF requires Superuser requires Android
Thanks so much for any direction or help, or even just commiseration!
For reference at the moment it is/has:
unlocked
HBoot 1.14 and fastboot is working well, and behaves as expected.
S-On
TWRP (working, and able to access with ADB)
No Working android install
CID: 1111111
Here is a dump of "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.13.50.05.25
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.531.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24NW401635
(bootloader) imei: 359902041820139
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8be28a51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
I found some guide how to unbrick your device:
[HOW-TO] Unbrick Your Android Phone (HTC ONE S) by fabiane79
[TUT] Downgrade/Unbrick Ville S4 by mirGantrophy
[HOW-TO] Fix soft brick & error mounting sdcard by cannondale0815
[TUT] Unbrick Your HTC One S [TUT] by immortal_warrior
Hopefully one of them can help in your case.
If not, please register on xda and ask in the One S Q&A, Help & Troubleshooting forum.
Good luck !

Thread closed. Thank you!

Related

[Q] Help! Something went wrong while installing an RUU!

Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!
So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!
can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link
His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.
Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..
@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.
Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks
Just use Goldcard and try 1.47.401.4 again.
I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You
i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Any sugestions?
Goldcard
Sent from my HTC Desire S
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!

[Q] No Recovery, Security Warning, can't unlock bootloader

Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
masev said:
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
Click to expand...
Click to collapse
Given that this has been covered many times, you would be better off listing EXACTLY what you have tried and the results you get so that people can have a better chance to help you. However, the answers are all out there and you simply need to read and make sure that you understand what you are doing and why.
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
masev said:
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
Click to expand...
Click to collapse
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
SimonTS said:
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
Click to expand...
Click to collapse
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
masev said:
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
Click to expand...
Click to collapse
RUU to a higher version.
Had the same problem with a branded phone. Problem is - you need a higher RUU. In my case there was no higher branded RUU.
I've made a gold card and flashed a unbranded higher RUU (latest ICS), and that makes the phone work again.
But without HTC-dev unlock we now can't get root! So if you can't find a higher RUU with your brand you may can't bring it to service with the new unbranded software on it.
Gesendet von meinem HTC Desire S mit Tapatalk 2

[Q] Can't find a RUU that matches my hboot/radio

Hi everyone.
I'm trying to get back on stock (S4), but I can't find any RUU that matches my hboot and radio.
this is the result of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4005mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried several S4 RUUs, european ones gave me error 131, Vodafone UK gave error 155 (the cellphone was bought in Italy).
What I did before executing the RUU exe(s) was just locking the bootloader. I think that probably installing ROMs in the time (the cellphone belongs to a friend of mine, so I don't know what was installed before) may have somewhat changed hboot (and/or radio) version, and now I can't find a RUU matching mine. Now i can only access the bootloader (I think the previous custom recovery is gone). I managed to access recovery by unlocking again the bootloader, but I can't mount any partition from the recovery (which is the main problem that lead me to decide to get back to stock.
What are my chances to return to HTC stock?
I have the same problem
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
addsfsds said:
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
Click to expand...
Click to collapse
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
hasanalikhattak said:
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
Click to expand...
Click to collapse
Dude give a quick look around, all the guides are here! or come to androidiani.com to get italian translated guides and support!

[Q] HTC One SV - Stuck with Asia version

Hi every body,
I meet a problem when I tried to S-Off my Htc One SV with moonshine. The process was failed after step 10 and the phone was frozen. After Moonshine "crash" I tried several way to come back the constructor system without good issue. By now the system is frozen at the white HTC screen, and adb can't connect to the system. Unique way is to use fastboot but I don't know if it's possible to get a stock version from this point.
I'am sorry to disturb you guys, but by now it's hard to continue by myself
Config : Ubuntu Mint 15
About the phone : ( ASIA version buy in Malaysia )
Tampered / Unlocked
K2_U PVT SHIP S-ON RL
HBOOT-2.00.0000
Radio-1.18.40a.00.05
Open DSP-v13.2.0268.0620
eMMC-boot
fastboot getvar all
(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: 3.11.707.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4002mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
I tried also onto Windows 7 to to install the RUU_K2_U_ICS_40_hTC_Asia_WWE_1.17.707.8_Radio_0.12.40.00.06_10.45.40.11L_release_301510_signed.exe. I get a message error
___________ Install Error 158 : Erreur d'image -------
The idea for me is just to "come" back to have a phone working ! By now it's less than a torch light...
Do you have a working TWRP recovery installed? If not, flash this from fastboot.
Then you can try to flash from recovery a working rom like this from here (download k2u version).
old.splatterhand said:
Do you have a working TWRP recovery installed? If not, flash this from fastboot.
Then you can try to flash from recovery a working rom like this from here (download k2u version).
Click to expand...
Click to collapse
Yes !!! Install Succedd with K2_u (Non-LTE) by using TWRP 2.6 & install the zip file.,Thanks a lot man for your help... ! I will continue to try to get the s-Off ! adb shell / su is working fine now .
With this rom version moonshine should work.
Your previous rom was not compatible to moonshine.

[Q] How do I unbrick my device? Please help!

Hi I just wanted to try the Maximus HD 10 and thought I did what was expected but something went wrong and now the phone is totally blank.. I am new to this but read alot in this forum before I began and I am used to computers etc. so I gave it a shot.. This is what I did:
Installed the Windroid Universal Toolkit to unlock the phone, and that went well. Then followed the instructions to install the Maximus HD 10 which also went well until I had to install the newer firmware.. From here things went really bad and after a lot of different wipes and things that I don't know anything about I am stuck with an useless device
I have searched all forums (I think) but with no luck, so if anyone know what I should do I would be really thankful.
And no.. I do not have a backup!!
This is the Fastboot Getvar All:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Fastboot can communicate with the phone but ADB devices will not find the phone.
If I reboot the phone I only see the HTC start screen for a few seconds and then nothing.. It has TWRP on it which I can enter.
Please help me!
If you have TWRP you might download any ROM and flash it but since you're S-On don't forget to flash kernel in fastboot mode after you flash the ROM.
Kernel is the boot.img file on the root of the ROM zip. Extract it to PC and while in fastboot issue the "fastboot flash boot boot.img" command.
For changing firmware you need S-Off which you don't have. To gain it you should flash first a close to stock ROM (like Viper for ex) then try to gain S-Off with rumrunner or another method. Then you can flash firmwares
Sent from nowhere over the air...
Hi Rapier, thank you so much for your help. Now it's working again
Claus71 said:
Hi Rapier, thank you so much for your help. Now it's working again
Click to expand...
Click to collapse
Don't forget to do that after every ROM flash. If you'll get S-Off, you won't need to do that anymore
Sent from nowhere over the air...

Categories

Resources