Why Did a Factory Reset clear Sprint's Network/Cell Data - One (M9) Q&A, Help & Troubleshooting

Whatever info the Sprint techs put into your device in order for it to get service from their network, that information was cleared when I wiped /data/ and /cache/.
Shouldn't that information be saved somewhere safer?
I am now unable to get service. What do?

RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!

blksith0 said:
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
Click to expand...
Click to collapse
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.

blksith0 said:
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
Click to expand...
Click to collapse
That's not correct. As mentioned several times here on xda the boot.img of 3.35.x firmware-based roms is not compatible with 3.y firmware versions where y is not the same as 35. If you're trying to use a non-sense-based custom rom (e.g. CM) you need to flash thicklizard's mono kernel. For sense-based roms you need to re-flash the stock boot.img of your currently installed firmware. After that you can use the chosen rom without problems.
Sent from my HTC One M9 using XDA Labs

So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?

blksith0 said:
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
Click to expand...
Click to collapse
No and no. Viper is using a boot.img for 3.35.x. You need the boot.img of your stock firmware. You could for example back up the stock boot.img with TWRP before you delete your stock rom and restore it after you flashed the viper rom. However, since the latest viper version is based on an HTC 10 port you still might face issues. Viper 4.3 on the other hand should be working fine since it's based on the HTC One M9. I'd suggest you to ask in the viper thread whether additional steps are needed for getting viper 5.3 to work on your phone.
Edit @blksith0: Sorry, I totally forgot that the viper rom has a special aroma installer with several options for the different branded M9 versions when I wrote this post. Although you might not be using the device on the sprint network you still need to choose the optimisations for sprint. Those options are made for being able to support the different firmware versions and not for the carrier you're actually using. Because of this flashing the stock boot.img shouldn't be needed in case of the viper rom.
Sent from my HTC One M9 using XDA Labs

Related

[Q] One V cdma boot problem. please help

Hey guys my buddy asked me to root rom and install a kernel on his one v from virgin mobile. being as i have done this before to multiple phones i was happy to help. i unlocked the bootloader, rooted it. everything was smooth up til there. i did not put a rom on it yet because he urged me to install a kernel so he could overclock his one v. i was aprehensive but i did it anyway. now his phone wont work. im not surprised but i need to fix it. ive tried installing roms to make it work because the backup ive created in twrp wont boot. so im thinking its a kernel problem. no matter what rom i use it will either not boot it will freeze at the screen that says htc and with the red wording below it. or it will boot into the rom and then freeze or run for about 30 sec then restart and it will repeat this until it dies. ive looked everywhere for ways to get it back to stock ive flashe countless roms none work ive flashed many kernels and none work as well. please help. i would like to get it working on a rom with a working kernel but i will put it back to stock if i have to. any help is greatly appreciated. thank you for your time.
You could flash a ruu ....but the problem is you don't have your software number ...or you have to go to another Rom ...which will make the phone boot normally .but don't forget to flash its specific kernel ...if you don't so that the Rom won't boot
What he said. I recommend using the RUU to restore back to stock.
Re-reroot/unlock it, then read more on which kernel to use. You most likely are using the wrong kernel.
What rom are you using currently - ?
What Kernel did you flash - ?
What error do you get with TWRP - ?
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Nazz45 said:
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
Click to expand...
Click to collapse
Nazz45 said:
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Click to expand...
Click to collapse
Ok. That's good. You use the same ICS kernel with the same ICS roms. No need to keep reflashing. I wouldn't flash a JB rom using a ICS kernel though.
Use this zip - http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
1. Extract the Boot.img from that zip and Fastboot flash boot boot.img in Bootloader
2. Wipe everything. Factory Reset, Dalvik, and System.
3. Flash an ICS based rom, Sense, or CM9.
4. Flash this after rom to get wifi working the zip above or below to fix Wifi.
http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
Just ran the RUU and it did work everything is back to stock. the sprint RUU worked. i ran into a snag installing the Android SDK it wouldnt recognize that i had my Java JDK. even after messing with my registry it still wouldnt work so i just downloaded the x86 jdk and it worked. its unfortunate cuz now i have a jdk in x64 and x86 and its taking up space on my ssd. oh well i hope it doesnt mess with eclipse. i am now going to unlock the bootloader again and re root it and install probably cm9. thank you for all your help i will post again after i attempt to re unlock reroot and rom. thanks again

HTC One V boot loops

So I was craving vanilla android on my HTC One V (CDMA, primoc) so I unlocked the boot loader, rooted it and installed TWRP. I tried AOKP first, but I ended up in what was basically a boot loop (it would boot up into the setup/startup but within about 30 seconds to a minute it would reboot). After digging around a bit I found some information indicating that only AOSP ROMs would work on my phone, I think because I had taken all the OTA updates before installing the ROM. So I tried some AOSP ROMs, but virtually all of them do the same thing. I have been able to get the CodefireX ROM working, but MMS doesn't seem to work with it (I can send texts but don't recieve them). I'd love to be able to install CM9 or 10 but I can't seem to find any AOSP ROMs (other than CFX) that don't put me in a boot loop. Any help would be greatly appreciated!!!
Flash kernel mate
Sent from my One V using xda premium
cybervibin said:
Flash kernel mate
Sent from my One V using xda premium
Click to expand...
Click to collapse
I always flash the boot.img from the ROM zip, that is flashing the kernel isn't it?
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.
Sounds like you have what I had yesterday. Had you already allowed any over-the-air updates?
If so, check out this thread: http://forum.xda-developers.com/showthread.php?t=2018518
Option #2 worked nicely for me.
still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy
cybervibin said:
still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy
Click to expand...
Click to collapse
Please read the op. The poster has a primoc.
Ya I had actually already tried option #2 over there but got this error...
Hboot Version is older!
Update Fail!
Press <POWER> to reboot
Click to expand...
Click to collapse
From what I understand from the responses I got on that thread my main ver was updated with the OTA and the RUU they are using only supports the one previous to it.
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
Click to expand...
Click to collapse
Thanks for the info! I'll give those a try.
tallnproud said:
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.
Click to expand...
Click to collapse
Well RhythmicROM is giving me the same issue as all the others. I might try flashing demi_fiend's kernel and see if that helps...
*EDIT* So I just realized it might be important to mention that every time I do a factory reset with TWRP it fails and says sd-ext can't be wiped. I've been able to wipe everything else though, and was able to get CFX working so I assumed that wasn't the problem.
my bad sorry

How do I move back to stock? More related questions inside.

Hello Guys,
I am currently on Shpongle and want to move back to stock. Reason being frequent hanging and sluggishness. I have installed the swap performance updates and greenify, but still at times, the phone gets the better of my patience.
MY Questions:
1. How do I go back to stock? I dont think I have the stock nandroid backup. I have the Unlock_code.bin that was sent by HTC.
2. Is there a lightweight Sense ROM? I like the camera, and looks, but I dont like the friendfeed and stuff.
Thanks.
thetuxracer said:
Hello Guys,
I am currently on Shpongle and want to move back to stock. Reason being frequent hanging and sluggishness. I have installed the swap performance updates and greenify, but still at times, the phone gets the better of my patience.
MY Questions:
1. How do I go back to stock? I dont think I have the stock nandroid backup. I have the Unlock_code.bin that was sent by HTC.
2. Is there a lightweight Sense ROM? I like the camera, and looks, but I dont like the friendfeed and stuff.
Thanks.
Click to expand...
Click to collapse
You can use myONEv RC9.5FX+ or Ignorance X for a lighter Sense ROM. You can remove the bloatware with titanium backup as well.
MameTozhio said:
You can use myONEv RC9.5FX+ or Ignorance X for a lighter Sense ROM. You can remove the bloatware with titanium backup as well.
Click to expand...
Click to collapse
Ignorance X does seem nice. Can I use the stock skin with it?
thetuxracer said:
Ignorance X does seem nice. Can I use the stock skin with it?
Click to expand...
Click to collapse
yes it won't look as nice though, since it has internal theming for Ignorance X skin.
MameTozhio said:
yes it won't look as nice though, since it has internal theming for Ignorance X skin.
Click to expand...
Click to collapse
Thank you. Its about to complete downloading. I will install it soon. Will use Titanium Kernel.
Thanks MameTozhio, you are very helpful!
A few questions about it
Sorry for my mistake, please remove it
Hi people.
My device is curretly like this:
N9005
Knox 0x1
TWRP recovery
Stock Kernel
Stock ROM 4.4.2
I would like to return completly to stock. I know I won't be able to be Knox 0x0 again but I want the stock recovery, kernel and ROM.
My question is: can I simply restore the firmware in Kies to get back to stock (including the recovery)?
Stock Rom: http://www.idroidspace.com/primou-original-stock-rom-for-htc-one-v-android-4-0-3-ics/
Stock Kernel and Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1221449&d=1343236979
I can't tell you if this stock rom is the original one by htc or with some modifications, I only found it and there are much more ruu uploads out there.
jonas2790 said:
Stock Rom: http://www.idroidspace.com/primou-original-stock-rom-for-htc-one-v-android-4-0-3-ics/
Stock Kernel and Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1221449&d=1343236979
I can't tell you if this stock rom is the original one by htc or with some modifications, I only found it and there are much more ruu uploads out there.
Click to expand...
Click to collapse
Thanks for the links. I have a problem. I decided I want to go back to comfortable stock ROM. I used a custom ROM, on a rooted HTC One V (GSM - Primo U). I followed the intructions: First I installed stock kernel and stock recovery. After I relocked the bootloader. I downloaded the RUU file according to my region (there are 4 european RUU version???). I connected my phone to computer and run the downloaded setup and followed the steps. Only after I started the update process, the progress bar stopped moving (before entering bootloader - the HTC One V didn't reboot into bootloader) and I got an error (155) message. What may be the problem? I have tried the all RUU files according to my region.
Thanks in advance,
Tejcsi
Tejcsi said:
Thanks for the links. I have a problem. I decided I want to go back to comfortable stock ROM. I used a custom ROM, on a rooted HTC One V (GSM - Primo U). I followed the intructions: First I installed stock kernel and stock recovery. After I relocked the bootloader. I downloaded the RUU file according to my region (there are 4 european RUU version???). I connected my phone to computer and run the downloaded setup and followed the steps. Only after I started the update process, the progress bar stopped moving (before entering bootloader - the HTC One V didn't reboot into bootloader) and I got an error (155) message. What may be the problem? I have tried the all RUU files according to my region.
Thanks in advance,
Tejcsi
Click to expand...
Click to collapse
First, install a custom recovery again. Then do a full wipe and install the rom you downloaded (PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip or PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_LITE.zip) with the custom recovery like you would install a custom rom. Then reboot to fastboot and flash boot.img (not boot-signed.img because this didn't work for me). Try to reboot and if everything works you may install recovery_signed.img, but this is only useful for ota updates, which obviously the hov doesn't get anymore.
jonas2790 said:
First, install a custom recovery again. Then do a full wipe and install the rom you downloaded (PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip or PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_LITE.zip) with the custom recovery like you would install a custom rom. Then reboot to fastboot and flash boot.img (not boot-signed.img because this didn't work for me). Try to reboot and if everything works you may install recovery_signed.img, but this is only useful for ota updates, which obviously the hov doesn't get anymore.
Click to expand...
Click to collapse
Thanks. Yesterday I've installed the PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip ROM, everything O.K., but there is no WIFI on my phone. So I decided to use the RUU. So I don't use boot_signed.img. Which boot.img can I use. Do you send me one?
Tejcsi said:
Thanks. Yesterday I've installed the PrimoU_Europe_2.22.401.1_Stock_Rooted_ODEX_FULL.zip ROM, everything O.K., but there is no WIFI on my phone. So I decided to use the RUU. So I don't use boot_signed.img. Which boot.img can I use. Do you send me one?
Click to expand...
Click to collapse
the boot.img inside the zip file
jonas2790 said:
the boot.img inside the zip file
Click to expand...
Click to collapse
So if i use the boot.img file inside the primou_europe_2.22.401.1_stock_rooted_odex_full.zip file, the RUU can reboot the ONE V into bootloader?
Tejcsi said:
So if i use the boot.img file inside the primou_europe_2.22.401.1_stock_rooted_odex_full.zip file, the RUU can reboot the ONE V into bootloader?
Click to expand...
Click to collapse
I don't really understand your problem. If you want to reboot into bootloader just use adb reboot bootloader.

Slow performance, lagging, low battery

Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff
tugratolunay said:
Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff
Click to expand...
Click to collapse
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?
high_voltage said:
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?
Click to expand...
Click to collapse
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1
tugratolunay said:
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1
Click to expand...
Click to collapse
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!
high_voltage said:
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!
Click to expand...
Click to collapse
What if I want to use current custom or similar one?
tugratolunay said:
What if I want to use current custom or similar one?
Click to expand...
Click to collapse
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
Would you be angry if i said i didnt get it?
high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?
tugratolunay said:
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?
Click to expand...
Click to collapse
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.
high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Click to expand...
Click to collapse
Can you help me to find the correct rom to flash please?
high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.
Click to expand...
Click to collapse
This one requires S-off mine is s-on
Ryokan said:
Can you help me to find the correct rom to flash please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.
high_voltage said:
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.
Click to expand...
Click to collapse
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?
Ryokan said:
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?
Click to expand...
Click to collapse
There is at&t android development section in the M8 forum, I am sure there will be noticed if MM is released.
Also in general thread in the sticky thread updates. Cheers!
Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that
Anonaru said:
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that
Click to expand...
Click to collapse
How can i know if my firmware matches?
Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
By asking you what firmware version you have. So, which version do you have? I put the big "If you have the right firmware" in there for a reason :laugh:
Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.
redpoint73 said:
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.
Click to expand...
Click to collapse
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:
Anonaru said:
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:
Click to expand...
Click to collapse
You are correct, in that general rule of thumb is to update firmware to match the ROM. Especially having KitKat firmware with a LP ROM, which caused major problems (no WiFi, audio issues, no boot or extreme long boot times).
But MM ROMs in general seem to work fine with LP firmware. It seems minimal changes to the firmware this time around. I haven't seen any issues (at least not anything major or significant) reported running MM ROMs with LP firmware.
And for the OP's AT&T version, he can't update firmware unless he does s-off. So at least for the time being, I don't see a compelling reason to do that; and look at other options to help his performance issues.

No Radio on ROM Flash

no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
twosaltyy said:
no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
Click to expand...
Click to collapse
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Mr Hofs said:
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Click to expand...
Click to collapse
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
twosaltyy said:
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
Click to expand...
Click to collapse
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Mr Hofs said:
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Click to expand...
Click to collapse
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
twosaltyy said:
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
Click to expand...
Click to collapse
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Mr Hofs said:
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Click to expand...
Click to collapse
Hmm... what about purefusion though, i cant see anything on that page about what firmware i have to be on but i read somewhere you have to be on O firmware for any O roms to work and you cant flash N roms if you are on O firmware.
Mr Hofs said:
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
Click to expand...
Click to collapse
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
twosaltyy said:
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
Click to expand...
Click to collapse
Read the specs ?
Look all the info is there. Take your time and take all info in, don't be hasty, read it a second time if needed.
Mr Hofs said:
Read the specs
Click to expand...
Click to collapse
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
twosaltyy said:
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
Click to expand...
Click to collapse
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
kazuki1 said:
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
Click to expand...
Click to collapse
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
UPDATE 2: The rom flash didnt go as well as i thought, the camera and flashlight didnt work nomatter what i did so i went back to RUU Stock and it worked fine
twosaltyy said:
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Click to expand...
Click to collapse
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
kazuki1 said:
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
Click to expand...
Click to collapse
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
G
Mr Hofs said:
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
Click to expand...
Click to collapse
I am flashing nougat roms, the wwe/dev rom I have running atm(which is giving me airplane issues) is the same as the official T-Mobile ruu I have that works, only difference is that it's the dev edition instead of t-mobile, same firmware and both are Android 7.0. Flashing full RUU and not any of these custom roms on here. I had only flashed lineage to see what it was like But got rid of it and put on my working T-Mobile ruu.
Both T-Mobile and dev edition RUU is taken from the official HTC website, they're the exact same thing.

Categories

Resources