Related
hello,
I updated my M8 international running ARHD to 10.1 using TWRP and fell into a softbrick but could access recovery.
Unfortunately while trying to fix this i ran the flash recovery script found on ARHD download site.
I now am able to access fastboot but TWRP is now not loading.
Is there anyway i can recover from this?
I dont care for losing data etc...just want a working phone back.
Your help would be greatly appreciated and will make a donation to a charity of choice in gratitude.
Regards,
John
Did you flash the 2.22 firmware prior to the rom ?
Mr Hofs said:
Did you flash the 2.22 firmware prior to the rom ?
Click to expand...
Click to collapse
i was running the previous latest ARHD ROM, and had downloaded the HTC service pack from playstore.
Other than that i have not flashed any firmware.
Device was purchaced at release in april and rooted/CFW'd then also
jaybee1981 said:
i was running the previous latest ARHD ROM, and had downloaded the HTC service pack from playstore.
Other than that i have not flashed any firmware.
Device was purchaced at release in april and rooted/CFW'd then also
Click to expand...
Click to collapse
u need the latest firmware to flash the ARHD 10.1,just search the firmware and flash it
Hey guys,
I recently rooted and unlocked my boot loader , then unrooted and relocked my bootloader
I'm in Canada , provider is Fido/rogers
I flashed the recovery from the OTA onto my device
So I finally got the lollipop update for my HTC one m8 and I downloaded it just fine then when I tired to install the update it would go through half way and get a red triangle with a ! Sign .
When I hold volume key and power it says that
"Package expects build fingerprint of htc/rogers/wwe/htc_m8:4.4.4 /ktup84p/401507.4:user/release-keys or htc/rogers/wwe/htc_m8:5.0.1/lrx22c/4463267.2:user/release-keys this device has "htc/bm/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys"
If anyone could help I'd appreciate it
lloydfreed said:
Hey guys,
I recently rooted and unlocked my boot loader , then unrooted and relocked my bootloader
I'm in Canada , provider is Fido/rogers
I flashed the recovery from the OTA onto my device
So I finally got the lollipop update for my HTC one m8 and I downloaded it just fine then when I tired to install the update it would go through half way and get a red triangle with a ! Sign .
When I hold volume key and power it says that
"Package expects build fingerprint of htc/rogers/wwe/htc_m8:4.4.4 /ktup84p/401507.4:user/release-keys or htc/rogers/wwe/htc_m8:5.0.1/lrx22c/4463267.2:user/release-keys this device has "htc/bm/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys"
If anyone could help I'd appreciate it
Click to expand...
Click to collapse
Restore the correct ROM/recovery. That error is pretty self-explanatory. For the update it expects you to be on the the rogers ROM/base but the device is on Bell Mobile.
BerndM14 said:
Restore the correct ROM/recovery. That error is pretty self-explanatory. For the update it expects you to be on the the rogers ROM/base but the device is on Bell Mobile.
Click to expand...
Click to collapse
Oh Wow Sorry for the stupid question in really new to this just moved from ios thanks allot ill try that out
BerndM14 said:
Restore the correct ROM/recovery. That error is pretty self-explanatory. For the update it expects you to be on the the rogers ROM/base but the device is on Bell Mobile.
Click to expand...
Click to collapse
hey just another question/ statement , when i relock and unrooted my phone i flashed the rogers nandroid onto it so can this problem be from something else because i know im not running the bell rom
lloydfreed said:
hey just another question/ statement , when i relock and unrooted my phone i flashed the rogers nandroid onto it so can this problem be from something else because i know im not running the bell rom
Click to expand...
Click to collapse
Most of the time I've seen that error it was either the recovery or the ROM that wasn't right. I've seen it quite a bit on these forums lately.
Check the recovery. It would make sense for the recovery. It's expecting either the old htc/rogers/wwe/htc_m8:4.4.4 /ktup84p/401507.4:user/release-keys or the new htc/rogers/wwe/htc_m8:5.0.1/lrx22c/4463267.2:user/release-keys recovery but it the device has a htc/bm/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys recovery.
You can do the update fine if you have the 4.4.4 recovery for your device OR if you flash the new 5.0.1 recovery on your device, then it'll work, but now it's not picking up either. So I think just download the Rogers recovery again and flash it to your device. Should fix problem then.
lloydfreed said:
hey just another question/ statement , when i relock and unrooted my phone i flashed the rogers nandroid onto it so can this problem be from something else because i know im not running the bell rom
Click to expand...
Click to collapse
I would guess the issue is your recovery too, not ROM. Where did you get the Lollipop recovery? Make sure you use the one extracted from the OTA downloaded by your device, in your Download folder.
BerndM14 said:
Most of the time I've seen that error it was either the recovery or the ROM that wasn't right. I've seen it quite a bit on these forums lately.
Check the recovery. It would make sense for the recovery. It's expecting either the old htc/rogers/wwe/htc_m8:4.4.4 /ktup84p/401507.4:user/release-keys or the new htc/rogers/wwe/htc_m8:5.0.1/lrx22c/4463267.2:user/release-keys recovery but it the device has a htc/bm/htc_m8:4.4.4/KTU84P/401507.4:user/release-keys recovery.
You can do the update fine if you have the 4.4.4 recovery for your device OR if you flash the new 5.0.1 recovery on your device, then it'll work, but now it's not picking up either. So I think just download the Rogers recovery again and flash it to your device. Should fix problem then.
Click to expand...
Click to collapse
hey, just wanted to say thank you so much,
i was really dumb and when i thought i had flashed the 5.0.1 recovery onto my phone, i realized i didn't because my bootloader was locked,
flashed the 5.0.1 recovery properly and redid the OTA and now its updating fine!
Thanks again
lloydfreed said:
hey, just wanted to say thank you so much,
i was really dumb and when i thought i had flashed the 5.0.1 recovery onto my phone, i realized i didn't because my bootloader was locked,
flashed the 5.0.1 recovery properly and redid the OTA and now its updating fine!
Thanks again
Click to expand...
Click to collapse
Great, glad it's running smoothly now. Enjoy it :good:
lloydfreed said:
hey, just wanted to say thank you so much,
i was really dumb and when i thought i had flashed the 5.0.1 recovery onto my phone, i realized i didn't because my bootloader was locked,
flashed the 5.0.1 recovery properly and redid the OTA and now its updating fine!
Thanks again
Click to expand...
Click to collapse
Awesome. If you want to re-root in Lollipop, take a look here:
http://forum.xda-developers.com/showpost.php?p=58624271&postcount=2
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.
I installed twrp on my m8 with fastboot cmd commands and then installed a stock sense 7 aroma installer, when the install finish it restart and get into the system. all was working good except for one thing, wifi, it won't turn on. I did download and install ice 8.2.2
and the same problem again but now with a message ''Fail to load driver,reason: unkown error (1)''
any ideas of what i can do?
Well i flashed Resurrection remix and now the WiFi works without problems, but still i dont know what happen with the other 2 roms
Problem Solved, i just needed to update the firmaware before installing the roms
what other two ROMs?
i believe you need to update your firmware
ahmed.ismael said:
i believe you need to update your firmware
Click to expand...
Click to collapse
thanks you, was that. I flashed a new firmware and now wifi works without problems
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.