[Q] wifi issue with 3.28.401.7 - One (M8) Q&A, Help & Troubleshooting

Hi,
version-bootloader: 3.18.0.00
version-baseband: 1.19.213311
version-cpld: None
version-microp: None
version-main: 2.26.73.2
version-misc: PVT SHIP S-ON
CID: ORANG202
I tried to install the One_M8_3.28.401.7_odexed.zip, but now I lost the wifi.
I can't update the firmware because I can't s-off, or maybe I don't know how.
What can I do to fix this issue ? install an old version or the orange version ?
Thank you for your help,
Regards,

k4mik4zi42 said:
Hi,
version-bootloader: 3.18.0.00
version-baseband: 1.19.213311
version-cpld: None
version-microp: None
version-main: 2.26.73.2
version-misc: PVT SHIP S-ON
CID: ORANG202
I tried to install the One_M8_3.28.401.7_odexed.zip, but now I lost the wifi.
I can't update the firmware because I can't s-off, or maybe I don't know how.
What can I do to fix this issue ? install an old version or the orange version ?
Thank you for your help,
Regards,
Click to expand...
Click to collapse
Your version-main is your firmware. You are still on 2.26.xxx. The 3.28.401.7 that you see in settings > about phone is the ROM base (software version). You need to either update your firmware to 401.7 or later (actually 401.6 will work too, but I don't want to be confusing), or use a 4.4.3 based ROM for your wifi to work. There are tutorials all over XDA, but since you are S-On, you will probably have to run the 4.4.4 RUU in fastboot.
You can download the RUU here.

xunholyx said:
Your version-main is your firmware. You are still on 2.26.xxx. The 3.28.401.7 that you see in settings > about phone is the ROM base (software version). You need to either update your firmware to 401.7 or later (actually 401.6 will work too, but I don't want to be confusing), or use a 4.4.3 based ROM for your wifi to work. There are tutorials all over XDA, but since you are S-On, you will probably have to run the 4.4.4 RUU in fastboot.
.
Click to expand...
Click to collapse
Hi,
I relocked the phone, but now I have the error : Error 131 customer id error.
CID: ORANG202
Thank you,

k4mik4zi42 said:
Hi,
I relocked the phone, but now I have the error : Error 131 customer id error.
CID: ORANG202
Thank you,
Click to expand...
Click to collapse
Go to this thread.
Find the stock ROM and recovery backups there for your phone. The thread explains how to find them.
Once you get back to stock you can take the OTAs to update your firmware.

xunholyx said:
Go to this thread.
Find the stock ROM and recovery backups there for your phone. The thread explains how to find them.
Once you get back to stock you can take the OTAs to update your firmware.
Click to expand...
Click to collapse
Hi,
The wifi is back.
Thank you for your help and your time,
Regards,

Related

[Q] SkyDragon 5.0.1 firmware

Hi all,
Currently I'm running Viper 1.8.0 ( Android 4.4.2 ) as you can see I'm behind my update schedule.
I'd love to give LP a try but in the SkyDragon thread I can see that i should check my firmware before upgrading to ensure WiFi is working.
Now the problem is that when i want to check my firmware there are no numbers so I have no clue what to update to.
Could anyone push me into the right direction to ensure a smooth upgrade ?
Other specs when booting into bootloader
- Tampered
- Unlocked
- M8_UL
- S-ON
- OS- [ This line is empty ]
Its a bit confusing, but OS or software number will actually not tell you the firmware number. The OS numbers will just tell you what software build the ROM was based off of, and will change if you flash the ROM.
To check firmware, look at hboot and radio number and post those here.
But essentially:
hboot 3.16 = 1.x firmware
hboot 3.17 = 2.x firmware
hboot 3.19 = 3.x firmware; and also 4.x (not many of those have OTA'ed yet)
Hi, excuse me for my late response.
My HBoot is 3.16. Beneath is an output of
Code:
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Actually i frankly do not mind what rom I should take next as long as its a 'stable' 5.0.x version.
Also right now I'm still running Venom 1.8.0 on 4.4.2.
I read about sunshine and S-OFF the device but I was thinking about reverting to stock and OTA updating.
Or should I proceed otherwise.
Thanks in advance !
Wickedd said:
Actually i frankly do not mind what rom I should take next as long as its a 'stable' 5.0.x version.
Also right now I'm still running Venom 1.8.0 on 4.4.2.
I read about sunshine and S-OFF the device but I was thinking about reverting to stock and OTA updating.
Or should I proceed otherwise.
Click to expand...
Click to collapse
If you want to run Lollipop Sense, you need Lollipop firmware. Has Lollipop OTA started rolling out for your version yet? Far as I know, only the Dev Edition have gotten it, in addition to some Euro versions (just started rolling out yesterday).
If your version hasn't gotten the LP OTA yet, you either need to wait or s-off and update the firmware "manually".
redpoint73 said:
If you want to run Lollipop Sense, you need Lollipop firmware. Has Lollipop OTA started rolling out for your version yet? Far as I know, only the Dev Edition have gotten it, in addition to some Euro versions (just started rolling out yesterday).
If your version hasn't gotten the LP OTA yet, you either need to wait or s-off and update the firmware "manually".
Click to expand...
Click to collapse
And what if I dont care about Sense, would i be update without changing my firmware ?
Also the only 'working' method I read about is Sunshine or does firewater still work ? I'm a bit careful because of the risks involved.
Any idea what would be my next step ? And what ROM should I keep as a backup, since I dont have a copy of Venom 1.8.0
Thanks in advance,
- Wickedd
Or would I be able to grab a 'factory' ROM for my device and let it update OTA, at least so I'm off my current ROM.
Wickedd said:
And what if I dont care about Sense, would i be update without changing my firmware ?
Click to expand...
Click to collapse
If the intent is to install Skydragon GPE, you need 4.4.4 firmware, as it states right in Post #2 of the Skydragon thread.
Your current firmware is very old. There aren't many (if any) current ROMs that it will support. You need to update firmware one way or another.
Wickedd said:
Also the only 'working' method I read about is Sunshine or does firewater still work ? I'm a bit careful because of the risks involved.
Click to expand...
Click to collapse
Sunshine is the only way to s-off. Firewater was discontinued in December.
---------- Post added at 11:30 AM ---------- Previous post was at 11:28 AM ----------
Wickedd said:
Or would I be able to grab a 'factory' ROM for my device and let it update OTA, at least so I'm off my current ROM.
Click to expand...
Click to collapse
Yes, this will get you on whatever current firmware your carrier version has had released.
You need the stock ROM and the stock recovery for your CID, in order for OTA to install. Root and unlocked bootloader are okay to OTA.
Thanks again for your help, When i check this thread I can't seem to find any numbers matching mine. So what image and recovery am I going to flash ?
http://forum.xda-developers.com/showpost.php?p=58606328&postcount=4278
Also : Firewater is discontinued in December, but my rom is in a state way before that. A reason to get my hopes up ? Also any risk in trying ?
Thanks in advance
Wickedd said:
When i check this thread I can't seem to find any numbers matching mine. So what image and recovery am I going to flash ?
Click to expand...
Click to collapse
hboot 3.16 means you are on 1.x firmware (and 1.x software before you flashed custom ROM). Which one from there is anyone's guess (1.12 or 1.54). I'd guess to try the more recent 1.x ROM, or 1.54.161.10.
Wickedd said:
Also : Firewater is discontinued in December, but my rom is in a state way before that. A reason to get my hopes up ? Also any risk in trying ?
Click to expand...
Click to collapse
Nope, absolutely no reason to get your hopes up. Firewater was an online service, so it will not work anymore.
When I said it was discontinued, I meant it. If there was a reason to think it would work, I would have said so.
Wickedd said:
Thanks again for your help,
Click to expand...
Click to collapse
There's a button for that.
How can I confirm this ? The only one I found was 1.54.401.5 as build number That'd be my firmware ?
Oh but the stock ROM doesn't have to match my current build number, so with 1.54.161.10 for VODAP102 i'd be good right ?

[Q] Wondering...

I know i need to pay for sunshine to get S-Off,i'm considering doing it sometime soon,but just asking,would firewater work if i flashed rom to earlier version of android,like 4.4.0 or so? Also would it need to be official or could costume rom work too? Sorry for another annoying S-Off question. :angel:
No does not work.
SynoX4 said:
Sorry for another annoying S-Off question. :angel:
Click to expand...
Click to collapse
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
redpoint73 said:
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
Click to expand...
Click to collapse
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
SynoX4 said:
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
Click to expand...
Click to collapse
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
xunholyx said:
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
Click to expand...
Click to collapse
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
SynoX4 said:
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
Click to expand...
Click to collapse
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
xunholyx said:
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
SynoX4 said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
Click to expand...
Click to collapse
Here's the RUU you need. It'll bump you to Lollipop.
xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Error 132 signature something... I did lock bootloader before doing it.
Will do nandroid recovery to android 4.4.3,lock again and try.
SynoX4 said:
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
Click to expand...
Click to collapse
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
xunholyx said:
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
Click to expand...
Click to collapse
Thing is,that requires s-off which i don't have...
SynoX4 said:
Thing is,that requires s-off which i don't have...
Click to expand...
Click to collapse
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
xunholyx said:
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
Click to expand...
Click to collapse
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
SynoX4 said:
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
Click to expand...
Click to collapse
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
xunholyx said:
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
Click to expand...
Click to collapse
Alright,thanks for all your help.

[Q] Stuck in Bootloader and Signature Error 132 in RUU

I have been trying to upgrade my phones Firmware, but it has given me some difficulties.
First off I could not get a Recovery Mod to work, I tried to flash both CWM and TWRP but both would only go to a black screen.
I live in New Zealand, and I bought my One X a while back. It seems to have HBOOT 1.25.0002 and I thought this was somehow preventing me from getting a recovery, so I did something stupid. I misinterpreted the Cyanogen wiki page and flashed the boot.img from their zip file. Woops.
Now my phone is stuck in the bootloader, so all is not yet lost.
I tried to find an RUU to restore the stock firmware, but I'm not sure the correct one to get. The first I tried gave me Signature Error 132.
Here is the phone version from fastboot getvar:
version: 0.5
version-bootloader: 1.25.0002
version-baseband: 1.15.40.04
version-cpld: None
version-microp: None
version-main: 2.22.707.8
version-misc: PVT SHIP S-ON
What version of RUU should I be looking for to restore my phone? None of the ones available seem to match up with this version number. Also, is there a way I can update the HBOOT version at the same time so I can install cyanogen?
Thanks in advance!
cosmikal said:
I have been trying to upgrade my phones Firmware, but it has given me some difficulties.
First off I could not get a Recovery Mod to work, I tried to flash both CWM and TWRP but both would only go to a black screen.
I live in New Zealand, and I bought my One X a while back. It seems to have HBOOT 1.25.0002 and I thought this was somehow preventing me from getting a recovery, so I did something stupid. I misinterpreted the Cyanogen wiki page and flashed the boot.img from their zip file. Woops.
Now my phone is stuck in the bootloader, so all is not yet lost.
I tried to find an RUU to restore the stock firmware, but I'm not sure the correct one to get. The first I tried gave me Signature Error 132.
Here is the phone version from fastboot getvar:
version: 0.5
version-bootloader: 1.25.0002
version-baseband: 1.15.40.04
version-cpld: None
version-microp: None
version-main: 2.22.707.8
version-misc: PVT SHIP S-ON
What version of RUU should I be looking for to restore my phone? None of the ones available seem to match up with this version number. Also, is there a way I can update the HBOOT version at the same time so I can install cyanogen?
Thanks in advance!
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/showthread.php?t=1975140
Hit the thanks button if helped
My phones CID is VODAP022, which doesn't seem to be on the list.
Does that mean there's no hope?
cosmikal said:
My phones CID is VODAP022, which doesn't seem to be on the list.
Does that mean there's no hope?
Click to expand...
Click to collapse
are you sure your cid is proper if it is then the post should contain it either in the listed one or in the missing one ...just confirm once again your cid
What do you mean? How would I know if the CID is incorrect? The post doesn't seem to list this CID anywhere.
cosmikal said:
What do you mean? How would I know if the CID is incorrect? The post doesn't seem to list this CID anywhere.
Click to expand...
Click to collapse
do fastboot oem readcid and check the cid

Orange UK RUU (ORANG001)

Hi, Does any one has latest Orange UK RUU OS v. 2.10.61.6 (cid = ORANG001)? Thanks in advance
Anyone please... My device is currently in bootloop. BL is locked , OEM unclocking is disabled. There no other way I can do but to flash an RUU
side_flip15 said:
Anyone please... My device is currently in bootloop. BL is locked , OEM unclocking is disabled. There no other way I can do but to flash an RUU
Click to expand...
Click to collapse
As far as I know there is no RUU you could use unless you are S-OFF. But maybe llabtoofers RUU service can help you out.
Flippy498 said:
As far as I know there is no RUU you could use unless you are S-OFF. But maybe llabtoofers RUU service can help you out.
Click to expand...
Click to collapse
Thanks! I already made an inquiry..
another option I am thinking is to unlocked BL and install custom rom and recovery but unfortunately I cannot unlocked BL since OEM unlocking is disabled in dev option. Is there anyway to toggle OEM unlocking may in adb or fastboot?
side_flip15 said:
Thanks! I already made an inquiry..
another option I am thinking is to unlocked BL and install custom rom and recovery but unfortunately I cannot unlocked BL since OEM unlocking is disabled in dev option. Is there anyway to toggle OEM unlocking may in adb or fastboot?
Click to expand...
Click to collapse
Not as far as I know...
Flippy498 said:
Not as far as I know...
Click to expand...
Click to collapse
After several wipes of cache and factory reset, my phone booted but I am stuck at initial setup as it requires the previous gmail synced. Unfortunately I forgot the password and no way to recover because the email was just a dummy for testing. Anyway to bypass FRP on the M9?
I want to make update to android 6, now i have version 5.1 firmware orange uk. (I have no official update) BOOT LOCKED, LK -1.0.0.0000 S-ON data on phone: HTC HIMA UHL PVT S-ON, cid orang001, mid opja 10000 o.s .. 2.10.61.6, radio u 11,440,601. * - I want to know if it can unlock boot, install TWRP and super su, then i can install a custom rom with android MM and what custom rom ????????????? expect an answer, thank you very much
Hi Everybody, plz help me, my phone HTC M9 is crached, and it can't boot to the OS, I tried to unlock it many time but no result, it's always relocked. now I need the officiel RUU to return the life to my HTC
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001

Lineage & Rooted HTC 10 - Cellular/LTE Radio broken

Hi All,
Here's hoping someone can help as I've made no progress in solving this issue in the past few hours.
So some background, I've installed TWRP on my HTC and have been using Lineage OS. I unlocked the bootloader via HTC dev, it is still S-ON. All has been well until recently when I decided I'd like to try out the stock rom again - mostly I wanted the HTC camera features back. So I downloaded the TWRP backup for my phone from XDA (CID: HTC_039). I run the restore via TWRP but it will not boot, so I followed the rest of the guide and flashed the stock recovery then relocked the bootloader. But to no avail... now it's in a very quick boot loop.... Managed to get out of it and unlock the bootloader again and flash TWRP once more.
So at this point I'm happy to return to Lineage with the backup I made before starting. But after restoring my pin doesn't work... so I followed another guide and deleted some files in TWRP which solved it. But I can't get any signal now. Apparently this is an encryption issue. I've also tried 'format data' in TWRP which apparently removes encryption. But following this installing lineage OS from zip or restoring stock or lineage results in the same error.
I'm just about at my wits end... I'd be super grateful for any input
Thankyou
Hope fully not to soon to *bump*
I have no idea what to do, surely someone know more about this than I do?
debatingrooster said:
Hope fully not to soon to *bump*
I have no idea what to do, surely someone know more about this than I do?
Click to expand...
Click to collapse
Have you tried running an RUU for your device?
Try looking here:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page118
Tarima said:
Have you tried running an RUU for your device?
Try looking here:
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page118
Click to expand...
Click to collapse
Hey Tarima I'm having a look at the link from the post at the top of that page, but how do I choose the right RUU? there's no CID mentioned in any of them?
Thanks
debatingrooster said:
Hey Tarima I'm having a look at the link from the post at the top of that page, but how do I choose the right RUU? there's no CID mentioned in any of them?
Thanks
Click to expand...
Click to collapse
You can go by your software version. Do
fastboot getvar all
from download mode and you'll know what yours is. You can only flash a version that's same or higher than your current one.
Tarima said:
You can go by your software version. Do
fastboot getvar all
from download mode and you'll know what yours is. You can only flash a version that's same or higher than your current one.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: Apparently should remove this
(bootloader) current-slot:
(bootloader) imei: Apparently should remove this too
(bootloader) version-main: 2.42.710.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__039
Is version main the one I'm interested in? 2.42.710.2?
Seems there's no RUU for my case, so I downloaded sunshine, thought I could s-off and run an older RUU. But apparently sunshine can't run on non-stock ROMs...
debatingrooster said:
Seems there's no RUU for my case, so I downloaded sunshine, thought I could s-off and run an older RUU. But apparently sunshine can't run on non-stock ROMs...
Click to expand...
Click to collapse
Sorry not sure how else to help. I don't think you're screwed though.
Tarima said:
Sorry not sure how else to help. I don't think you're screwed though.
Click to expand...
Click to collapse
No worries, Thanks for your help! I might try viper rom and see If I can run sunshine on that...
Hopefully not screwed, hardware should all still be fine in any case. Hopefully someone else can chime in with some ideas??
Happy days!!
Installing Team Venoms Viper ROM Fixed it. Good ROM too. It also remained working when Lineage OS was installed again.
It seemed to reenable encryption - I'm being prompted once more to enter my password in TWRP
Hopefully this helps anyone who might find themselves in the same situation

Categories

Resources