Database Info

Up to date with RUU 1.24.401.1 but Hboot radio S-off 1.17.0011.1

Good all
I tried to do a debrand the HTC Sensation of my brother, I have not been very clear that part of the upgrade program, so I moved on thinking it should do but not, I have found and I have rom.zip in my power, the problem: HTC Sensation has been updated leaving the chipset radio version 1.24.401.1, after S-off and root, to finish the upgrade, I left the firmware or free Rom "Vodafoneless" but the root gone, first of all I made a backup with recovery version 1.17.008 from vodafone, I thought it must return to recovery. Hboot surprise me says I have the previous radio version but instead of being the 1.17.008 is now 011 and S-off but attempting to start the recovery does not work. I restarted the process of S-off but failed because it only supports up to 012 and put me clearly that I had in my possession the 1.24.401.1 you know.
Considering I backup the previous version, there is no way to reverse the process back to the previous version to start again from 0 (You know that the recovery does not work) either through the SDK or some similar procedure to 1.24. ..
The weirdest thing is that the hboot tells me I have the radio version 1.17.011 as I have already mentioned, S-off but the recovery icon I get the attention of the phone and still no more.
If you have any idea, do not worry me too much the phone works perfectly and has no problem to version 1.24 but I can wait to see if there is a chance to reload the firmware security image above.
Thank you very much in advance and sorry for my english! A greeting

Joanmi said:
Good all
I tried to do a debrand the HTC Sensation of my brother, I have not been very clear that part of the upgrade program, so I moved on thinking it should do but not, I have found and I have rom.zip in my power, the problem: HTC Sensation has been updated leaving the chipset radio version 1.24.401.1, after S-off and root, to finish the upgrade, I left the firmware or free Rom "Vodafoneless" but the root gone, first of all I made a backup with recovery version 1.17.008 from vodafone, I thought it must return to recovery. Hboot surprise me says I have the previous radio version but instead of being the 1.17.008 is now 011 and S-off but attempting to start the recovery does not work. I restarted the process of S-off but failed because it only supports up to 012 and put me clearly that I had in my possession the 1.24.401.1 you know.
Considering I backup the previous version, there is no way to reverse the process back to the previous version to start again from 0 (You know that the recovery does not work) either through the SDK or some similar procedure to 1.24. ..
The weirdest thing is that the hboot tells me I have the radio version 1.17.011 as I have already mentioned, S-off but the recovery icon I get the attention of the phone and still no more.
If you have any idea, do not worry me too much the phone works perfectly and has no problem to version 1.24 but I can wait to see if there is a chance to reload the firmware security image above.
Thank you very much in advance and sorry for my english! A greeting
Click to expand...
Click to collapse
Hiya,
I think I get what you're saying, just try flashing the latest RUU now (1.35.401..) it will install over the 1.24 and bring you completely up to date - I did the same as you, although I remember I think I needed to SCID the phone to get the latest RUU to run properly found here --> http://forum.xda-developers.com/showthread.php?t=1192630&page=4
Download the BAT File which is easier than doing the whole adb stuff
Hope it helps..

Joanmi said:
Good all
I tried to do a debrand the HTC Sensation of my brother, I have not been very clear that part of the upgrade program, so I moved on thinking it should do but not, I have found and I have rom.zip in my power, the problem: HTC Sensation has been updated leaving the chipset radio version 1.24.401.1, after S-off and root, to finish the upgrade, I left the firmware or free Rom "Vodafoneless" but the root gone, first of all I made a backup with recovery version 1.17.008 from vodafone, I thought it must return to recovery. Hboot surprise me says I have the previous radio version but instead of being the 1.17.008 is now 011 and S-off but attempting to start the recovery does not work. I restarted the process of S-off but failed because it only supports up to 012 and put me clearly that I had in my possession the 1.24.401.1 you know.
Considering I backup the previous version, there is no way to reverse the process back to the previous version to start again from 0 (You know that the recovery does not work) either through the SDK or some similar procedure to 1.24. ..
The weirdest thing is that the hboot tells me I have the radio version 1.17.011 as I have already mentioned, S-off but the recovery icon I get the attention of the phone and still no more.
If you have any idea, do not worry me too much the phone works perfectly and has no problem to version 1.24 but I can wait to see if there is a chance to reload the firmware security image above.
Thank you very much in advance and sorry for my english! A greeting
Click to expand...
Click to collapse
The version numbers your quoting seem to be a mix of rom version's and h-boot version's but then you mention radio version's so its a bit confusing.
Have a look in THIS thread. You must really understand what you are doing though as you could brick the phone if you are messing with H-boot and radio's.
Does the phone work, boot? I restored my back up a couple of days a go, (needed it for copilot licence), and it worked fine but it does leave you s-off.

Ok let's try to explain again
i know my wrote english it's **** but, it's the only i have.
Trying to debrand the phone (htc sensation) in the step to get the rom.zip from the ruu_pyramid of 1.24 from temp folder i follow the entire process and it flash my pyramid 1.17 to 1.24. when i run the hboot it print in the screen i got 1.17.2008 (now i tryied to install the clockwork and it brings the phone to that hboot version) but my firmware is the 1.24.401.1.
i think it can be understand until here.
when i'm going to hboot and i try to run recovery the phone's show me the phone with the warning red signal and i must to reboot manually the phone.
before i started the flashing process i save 1.17 firmware with a backup, there exist some procedure to return the phone to that firmware. i couldn't do the supercid procedure.
i hope you can help me cause i don't have any idea how can i proceed.
thx in advence and one more time i'm sorry for my bad write english

Unable to use firmware 3.24,3.30, 3.32

Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!

pr0adam said:
Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!
Click to expand...
Click to collapse
Hi,
Have you had a look at THIS THREAD ?

Yes I have. Using this thread I found the firmware that is supposed to work with my phone using the CID I found using the information in that thread. However, the firmwares listed for my thread that are 3.24 onward do not work for any of the ROMs I have tried. Only 3.12 and 1.17 work for me. I'm not sure why this is.

I'm quite noob but probably you need to be supercid to flash some roms. You can follow the guide (in development forum 2nd sticky thread). Good luck
Strange you have locked bootloader btw.

Follow guide for superCID to see if that helps?
Sent from my Pyramid-T

Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !

pr0adam said:
Hello. I'm trying to run various ICS roms that require firmware 3.24 or more(Android Revolution HD for example and numerous others). For a while I was running Virtuous Inquisition on 3.12 firmware but wanted to try some others out so I downloaded the 3.30 firmware found on the firmware for beginners topic page.
I am using the correct firmware because I know what my CID/MID are:
cid:T-MOB010
mid: PG5810000
However, no matter what ROM i use, I tried VI, Revolution HD, Blitz, on either 3.24 or 3.30 or 3.32, I always get stuck in a bootloop. VI gets stuck on a bootloop on any firmware besides 3.12. What do I need to do to get the higher firmwares to work?
This is what my bootloader screen shows on the top when on firmware 3.12. If you guys need more information just ask and I'll post it when I can.
***LOCKED***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011, 12:14:25(clock seems to be super wrong idk why lol)
Thank you!
Click to expand...
Click to collapse
Hi there. There are a lot of people here who will help you but you need to work through a procedure such as this Thread and identify what you have done and where you get stuck.

Mercvtio said:
Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !
Click to expand...
Click to collapse
Well in such case I would extract the rom.zip from the official RUU (I hope you know how to do) and flash it as PG58IMG. Then start again the whole procedure.
Go to [ROM]Shipped Pyramid ROM Collection thread and dowload the RUU_PYRAMID_ICS_HTC_Europe_3.30.401.1_Radio_11.69.3504.00U_
Sorry but I cannot post links right now.
You won't lose superCID and S-OFF so it worths trying.

I have made my phone superCID and will now try to run the higher firmwares and see if that works this time around. I'll let you guys know if anything changes thanks for the help thus far

pr0adam said:
I have made my phone superCID and will now try to run the higher firmwares and see if that works this time around. I'll let you guys know if anything changes thanks for the help thus far
Click to expand...
Click to collapse
Waiting for good news

Mercvtio said:
Well, looks like I have a similar problem...
I'm SuperCID, and till this morning, I was running VI 3.5.1b.
Seeing on the VI thread that the latest firmware could be run with it, I upgraded to 3.32... and since then, I'm stuck in an bootloop.
I tried everything : rolling back to 3.24 and to 3.12 ; changing roms ; wiping everything I could ; but i won't help.
Most of the times, I'm stuck at the HTC Splashscreen ; VI and Tripnice (yeah, even tried that one) go to the boot animation, then reboot. So I'm at a loss here as to what to do to fix it. Any help would be very welcome and appreciated !
Click to expand...
Click to collapse
Can you reach recovery or bootloader?
Sent from my Pyramid-T

Nope still doesnt work. 3.32 still bootloops on various ICS roms i tested(ARHD and Blitz) even with superCID

stringer7 said:
Can you reach recovery or bootloader?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Yup, still got access to both of them. I resolved my problem by flashing both the firmware and the latest rom from He Who Must No Be Named... For a reason I still don't grasp, it seems that the firmwares I flashed previously didn't downgrade the bootloader, or something like that. Trip's one, however, is a waaaay bigger file and seems to rewrite a huge amount of things.
Don't know yet if I could switch back to VI harmlessly, though...

Sorry- of course you can reach bootloader, you listed it in your OP! Tired...
Something strikes me, you have hboot 1.23, I know this version causes issues with s-on users that have accepted OTA updates.
Have you run s-off via revolutionary in the past? Unlocked via htc.dev (which I think gives hboot 1.23)?
Does recovery work?
Sent from my Pyramid-T

Mercvtio said:
Yup, still got access to both of them. I resolved my problem by flashing both the firmware and the latest rom from He Who Must No Be Named... For a reason I still don't grasp, it seems that the firmwares I flashed previously didn't downgrade the bootloader, or something like that. Trip's one, however, is a waaaay bigger file and seems to rewrite a huge amount of things.
Don't know yet if I could switch back to VI harmlessly, though...
Click to expand...
Click to collapse
Great!
Might still be worth checking out what I posted above to see if something in that causes the problem?
Sent from my Pyramid-T

After reading more around the forums I'm pretty sure I need a custom firmware. One with the HBOOT of 3.12 but the rest of the files of a 3.32 firmware. How would I go about doing this?

I wouldn't mess things more than this.
I would go back to GB first.
Download the appropriate official RUU for your device and run it on the pc until appears the picture of a phone and "show readme file). Leave this window open.
then go to "My computer"-disk C (or wathever)- Documents and settings-name of computer (or your name)- local settings - Temp.
There you will find a folder or more folders with a weird name ie: {040EEDE2-371A-4BF6-8D25-1B12121F8D9E}.
Inside one of this folder you will find a file "rom.zip". do not extract, just drag and drop somehere in your pc.
Now close the RUU windows by clicking cancel.
Now rename "rom.zip" in PG58IMG and put in the root of your SD card.
Reboot your phone by pressing vol down+power.
At this point the file PG58IMG will be detected you will be asked to update. Say yes by pressing volume up.
Be patient as it will take a lot of time, don't touch or do anything until it has finished. a lot of files will be flashed and screen may goes black a couple times.
Dont worry and wait until it will say "press power to reboot".
Now you should be back to stock GB and start all procedures to upgrade once more if you like.
Remember then to delete the PG58IMG on the SD card.
When you will set your phone again, remember to untick fastboot for future use.
Hope it helps
PS: Forgot to say that by doing this you will lose root (not S-OFF and superCID) but you can easly re-root your device by following the guides in the forum.

So I managed to flash back to 3.32 and VI 4.0 after 2 days of mercyless bootlopping.
What I did was :
1- superwipe everything, flash latest TripOS rom
2 - reboot to bootloader and flash Trip's latest firmware (this way, I knew I woul have both a matching rom and matching firmware, avoiding incompatibility issue). Trip's firmware rewrites a huge amount of things, and that seems to put an end to what was causing my bootloops.
3 - reboot and let the phone alone for 10 minutes, just to let everything settle right.
4 - reboot to recovery
5 - Superwipe again
6 - flash my rom (in my case, VI 4.0)
7 - power off, and boot to bootloader
8 - flash 3.32 firmware
9 - reboot and let the phone still for 10 minutes
So far everything runs perfectly (I just have a splash screen saying "Trip'n Nice" on it) and it saved me from going into the process of flashing a RUU, rooting the RUU, installing recovery and so on. Give it a try, it might work for you to.

Looks like He has HBOOT 1.23, so I suspect He's using HTC-Dev method to unlock the boot loader or running FOTA that maybe gives him HBOOT 1.23.
Since Revolutionary could only S-OFF up to HBOOT 1.18, so maybe He just need to wait till Revolutionary support HBOOT 1.23 (the only options, maybe next year )
BTW, what are You doing that causing You to have HBOOT 1.23?

problem is that his bootloader shows ***Locked***.
If you go through htc-dev it would have shown ***Unlocked***.
This is why I would start from the beginning flashing a GB RUU and then start again the upgrade process.
My humble opinion, of course

[Q] Error 155 Such a case has not yet gone.

I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?

Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:

Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium

TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?

Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!

[Q] Trouble updating hboot

Evening, gents.
I'm trying to update my hboot so I can begin flashing newer roms. I'm stuck on hboot 1.14 and as many others have been posting about, it's giving me issues.
Anyway, here are my details:
S-Off
CID 22222222
hboot 1.14.0002
getvar version-main returns: 2.20.502.7
I've been messing around with my phone for a couple of weeks, trying this and that to update it, but nothing seems to be working. I even tried using a new RUU, but it doesn't seem to recognize my phone (it runs, and Windows says the software didn't install properly, but doesn't give me details).
Sorry for the vagueness - I'm not really sure what else would be pertinent at this point.
Any help would be greatly appreciated!

The only way you're meant to update is via the 3.18 RUU, this is because it isn't just the hboot you're meant to update, it's the firmware as a whole. So any other method you've attempted is wrong. Are your drivers up to date? Do you have HTC Sync Manager installed? If so you should uninstall that (leave drivers installed) because it can get in the way.
Sent from my Evita

timmaaa said:
The only way you're meant to update is via the 3.18 RUU, this is because it isn't just the hboot you're meant to update, it's the firmware as a whole. So any other method you've attempted is wrong. Are your drivers up to date? Do you have HTC Sync Manager installed? If so you should uninstall that (leave drivers installed) because it can get in the way.
Sent from my Evita
Click to expand...
Click to collapse
I saw where you recommended that to someone else, and tried it earlier this evening. It didn't work for me earlier, but I tried it again anyway. It worked this time! I think this was more the fault of Windows being unclear than anything...
I got the same error, but I told Windows to proceed "with default settings" (it didn't really say what those were), but either way, it fixed it. I now have hboot 2.14. Thanks a bunch for your help!
Now, off to re-install a custom recovery. Away!

Flashing firmware.zip from OTA's in rebootRUU mode in the order OTA's would flash them is also a valid way to update firmwares.
firmware.zip from first release 3.17 or 3.18 is always a "full" firmware.zip, then just follow the OTA chain to the latest.
Or if you are s-off you can make use of one of the modified firmware.zip's by Turge, Carl and others. Depending on the one you chose you will get a fair chunk of the firmware files. Some only include the radio in particular and lack sbl's etc. I personally prefer to do everything rather than just some of the key pieces(like radio and hboot).
Eg Turges is fairly well complete.

Hi, could you please help me http://forum.xda-developers.com/showthread.php?p=48178634#post48178634

Need help updating hboot via RUU, S-Off, etc.

I'm using CM10 and I've been wanting to update my S4 to a KitKat rom for some time and now that some stable builds are starting to come out I decided it was a good time.
On my first try flashing a new rom I got an error message asking for a newer version of hboot (mine is 1.14.0002 and it wanted 2.15.0000), so I looked around and found out I needed a RUU to update that, but since finding one for my phone is pretty difficult I decided to S-Off it, because apparently you can use any RUU that way.
Obviously it's not working, that's why I'm posting this. I did the htcdev method to unlock the phone back when I installed CM10 and to get S-Off I followed the rumrunner method. No problems whatsoever so far. They start appearing as soon as I try to update the 2.15.0000 RUU I downloaded from this other tutorial (the HTC Europe one, since I live here).
Following all the steps in that page I read about needing to change the phone's SuperCID to make it compatible with the RUU. First I tried with the default SCID that my phone had (VODAP304) with no luck. Then after a bit of searching I tried changing it to HTC__001 which seemed to be the correct one for the european RUU, but the same thing happened: it gives an incompatibility error, the process stops, the phone bootloops and I have to do a TWRP restore (the back up is from this morning and I made it just before attempting this, so no data loss of any kind)
These are the numbers bootloader gives me, if they're of any help:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-VODAP304
HBOOT-1.14.0002
RADIO-1.08es.50.02.21
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
What exactly am I missing here to update the hboot?

You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S

ka_55 said:
You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S
Click to expand...
Click to collapse
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky

Rodrows said:
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky
Click to expand...
Click to collapse
Yes it's about kernels and the problem with the new roms is nothing but the kernel. So firmware update is enough as a solution. I don't think it's dangerous if you follow the instructions correctly. But you should follow them word to word with your own risk
Sent from my HTC One S