Develop Bugs

Can't get wifi to work/can't figure out which firmware to use

I have an AT&T HTC M8, I believe it is on 4.4.2, and I tried flashing ARHD and got the dreaded no wi-fi problem, and I can't figure out for my life which firmware to use that will let me use wi-fi. I've been looking through the internet since 2 AM this morning, so any help would be great.

http://forum.xda-developers.com/showthread.php?t=2824048
Follow the directions and flash the latest firmware.

manlavi95 said:
I have an AT&T HTC M8, I believe it is on 4.4.2, and I tried flashing ARHD and got the dreaded no wi-fi problem, and I can't figure out for my life which firmware to use that will let me use wi-fi. I've been looking through the internet since 2 AM this morning, so any help would be great.
Click to expand...
Click to collapse
When you say that, based on the time your post was made(for my time zone) you haven't been looking for very long...
Today, 02:09 AM | #1 <<< A whole 9minutes

BerndM14 said:
When you say that, based on the time your post was made(for my time zone) you haven't been looking for very long...
Today, 02:09 AM | #1 <<< A whole 9minutes
Click to expand...
Click to collapse
Hahaha it's been about 13 hours here

chuck24 said:
http://forum.xda-developers.com/showthread.php?t=2824048
Follow the directions and flash the latest firmware.
Click to expand...
Click to collapse
I'm stuck at the "4. Boot into hboot and READ, INTERNALIZE, & then EXECUTE and let it update its firmware."
How do I read, internalize, and execute it? The directions for this are very scattered.

Im assuming your phone is S-OFF?
Before this, was your phone updated by any OTA's? This is just to confirm that you were on 4.4.2.

I am S-off, but yes, firewater told me I took an OTA (must have happened before I bought the phone) so I had to use Sunshine or whatever, now I'm S-off and don't know what to do next.

manlavi95 said:
I'm stuck at the "4. Boot into hboot and READ, INTERNALIZE, & then EXECUTE and let it update its firmware."
How do I read, internalize, and execute it? The directions for this are very scattered.
Click to expand...
Click to collapse
When you reboot the phone to bootloader you'll notice a couple of options that you can select one of them is "HBOOT" I think it's written in blue.
Select it with the volume up or down key and press power to go in, it'll then show a scrolling of I think it's green text where it's looking for files on sd card. It should pick up your renamed firmware file and give you option to update with it.

Hmm, I moved the renamed file (renamed to 0P6BIMG.zip) to external SD through TWRP, but when I go into Hboot, it doesn't do anything. I feel like it's something obvious.

manlavi95 said:
Hmm, I moved the renamed file (renamed to 0P6BIMG.zip) to external SD through TWRP, but when I go into Hboot, it doesn't do anything. I feel like it's something obvious.
Click to expand...
Click to collapse
Maybe try and move it to internal storage. Check that it's named correctly, a ZERO (0) and not a O <Capital o... Make sure it's .zip and not .zip.zip else...
Do it manually with mike1986.'s flash guide.

Can I get a link to that?

manlavi95 said:
Can I get a link to that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2696282 <Mike's guide.
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 <SneakyGhost's guide.

chuck24 said:
http://forum.xda-developers.com/showthread.php?t=2824048
Follow the directions and flash the latest firmware.
Click to expand...
Click to collapse
BerndM14 said:
http://forum.xda-developers.com/showthread.php?t=2696282 <Mike's guide.
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 <SneakyGhost's guide.
Click to expand...
Click to collapse
See, I tried that, but I can't seem to find a firmware for ATT that is 3.28.401.6

manlavi95 said:
See, I tried that, but I can't seem to find a firmware for ATT that is 3.28.401.6
Click to expand...
Click to collapse
Well that's logical isn't it? AT&T doesn't use x.xx.401.x. Even if you do flash the latest 3.x firmware on your device you'll probably have problems seeing as the radio's are different.
Rather go with the Developer Edition 3.x firmware. AT&T and Dev Edition share same radio, MID etc. It's the 3.28.1540.5 firmware you can find it in the OTA zip collection.
OTA ZIP COLLECTION
Just download the OTA and extract the firmware.zip file from the OTA.zip. If you flash the 3.28.401.x you might have issues with LTE etc

BerndM14 said:
Well that's logical isn't it? AT&T doesn't use x.xx.401.x. Even if you do flash the latest 3.x firmware on your device you'll probably have problems seeing as the radio's are different.
Rather go with the Developer Edition 3.x firmware. AT&T and Dev Edition share same radio, MID etc. It's the 3.28.1540.5 firmware you can find it in the OTA zip collection.
OTA ZIP COLLECTION
Just download the OTA and extract the firmware.zip file from the OTA.zip. If you flash the 3.28.401.x you might have issues with LTE etc
Click to expand...
Click to collapse
2.22.1540.4 -> 3.28.1540.5 thanks
^This one? This one will work with my ATT phone the right way? I'm sorry I'm such a noob to all of this. I'm used to flashing a rom and continuing about my normal life.

manlavi95 said:
2.22.1540.4 -> 3.28.1540.5 thanks
^This one? This one will work with my ATT phone the right way? I'm sorry I'm such a noob to all of this. I'm used to flashing a rom and continuing about my normal life.
Click to expand...
Click to collapse
Yes

BerndM14 said:
Yes
Click to expand...
Click to collapse
Thank you for your help, I'll follow up in about 10 minutes

Yeap that zip should work, @BerndM14 beat me to it. I really need to bookmark all these threads.
Just make sure you flash it twice without leaving the RUU flash screen.

bloodhawk said:
Yeap that zip should work, @BerndM14 beat me to it. I really need to bookmark all these threads.
Just make sure you flash it twice without leaving the RUU flash screen.
Click to expand...
Click to collapse
BerndM14 said:
Yes
Click to expand...
Click to collapse
"FAILED (remote: 42 custom id check fail)"

bloodhawk said:
Just make sure you flash it twice without leaving the RUU flash screen.
Click to expand...
Click to collapse
Yes, very important. I left it out, going on the assumption that he'll follow mike's guide where it says to flash twice...
Yes, I know...
Don't assume, it makes an ass(out of)u(and)me :silly:

Missing Firmware

Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.

yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware

So what is stopping me from flashing new firmware each time?

yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.

xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.

yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?

xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.

yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.

xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.

yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.

xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.

yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.

Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.

BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.

Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:

Red Exclamation mark when updating to Lollipop

So when installing the Official Lollipop update I get red exclamation mark when hitting ( roughly 10%).
The phone was previously rooted and still has SuperSU in it, Is it because of SuperSU the phone is halting the update ?
I have formatted my phone and is obviously having Original Recovery.
Can anyone help me ?
BTW I have did some Xposed changes, flashed a custom font over deault font....
CID : T-MOB009
S-On
Rooted

MJ999 said:
So when installing the Official Lollipop update I get red exclamation mark when hitting ( roughly 10%).
The phone was previously rooted and still has SuperSU in it, Is it because of SuperSU the phone is halting the update ?
I have formatted my phone and is obviously having Original Recovery.
Can anyone help me ?
Click to expand...
Click to collapse
Question :
For what EXACTLY did you use root acces for ?
:laugh:

MJ999 said:
.
Can anyone help me ?
Click to expand...
Click to collapse
Post your error messages.
Hold vol+ and tap power button once, when you see red triangle.

Mr Hofs said:
Question :
For what EXACTLY did you use root acces for ?
:laugh:
Click to expand...
Click to collapse
I have used it to apply some Xposed tools and I have previously flashed over another zip font as well because I have noticed its not the default font when I formatted the phone it's actually the font I flashed,
So will that be the problem ?
So is there any original stock rom that I can flash over my M8 ?
idk care about the data loss
M8 is S-On
ikeny said:
Post your error messages.
Hold vol+ and tap power button once, when you see red triangle.
Click to expand...
Click to collapse
Finding update package...
Opening update package...
verifying update package...
installing update...
l50qct.01.101.007
Package expects build fingerprint of htc/tmo_pl/htc_m8 4.4.4/KTU84P/392065.9:user/release-keys or htc/tmo-pl/htc_m8:5.0.1/LRX22C/57188.2:user/release keys; this device has htc/htc_europe/htc_m8:4.4.3/KTU84L/365360.4:user/release-keys.
Installation aborted.
Write hose_mode:0 done

MJ999 said:
Click to view the error message
<div id="spoiler" style="display:none">
Finding update package...
Opening update package...
verifying update package...
installing update...
l50qct.01.101.007
Package expects build fingerprint of htc/tmo_pl/htc_m8 4.4.4/KTU84P/392065.9:user/release-keys or htc/tmo-pl/htc_m8:5.0.1/LRX22C/57188.2:user/release keys; this device has htc/htc_europe/htc_m8:4.4.3/KTU84L/365360.4:user/release-keys.
Installation aborted.
Write hose_mode:0 done
</div>
<button title="Click to show/hide content" type="button" onclick="if(document.getElementById('spoiler') .style.display=='none') {document.getElementById('spoiler') .style.display=''}else{document.getElementById('spoiler') .style.display='none'}">Show/hide</button>
Click to expand...
Click to collapse
DUDE!
Read what that says.
Package expects......
You are using WWE firmware on a T-Mo device.
There's your answer.

xunholyx said:
DUDE!
Read what that says.
Package expects......
You are using WWE firmware on a T-Mo device.
There's your answer.
Click to expand...
Click to collapse
OK So what should I do now ?
How do I get past this screen ?

MJ999 said:
OK So what should I do now ?
How do I get past this screen ?
Click to expand...
Click to collapse
Find T-Mo firmware, or flash the new WWE firmware instead I suppose.
I'm not sure what you are trying to accomplish here.

xunholyx said:
Find T-Mo firmware, or flash the new WWE firmware instead I suppose.
I'm not sure what you are trying to accomplish here.
Click to expand...
Click to collapse
So I can just flash any firmware over my phone ? Like wwe firmware over my t-mo phone ?
Where can I find firmwares ?
And how do I know which one to flash ?

MJ999 said:
So I can just flash any firmware over my phone ? Like wwe firmware over my t-mo phone ?
Where can I find firmwares ?
And how do I know which one to flash ?
Click to expand...
Click to collapse
Okay. I'm not really getting this.
Did you not flash WWE firmware already? Are you running a custom ROM perhaps, with a 401 base?

xunholyx said:
Okay. I'm not really getting this.
Did you not flash WWE firmware already? Are you running a custom ROM perhaps, with a 401 base?
Click to expand...
Click to collapse
No, I haven't done anything.
I will explain it to you again ( short )
Phone is rooted and S-ON and is having Original Rom 4.4.4 with 3.29.118.9
CID : T-MOB009
I got the Lollipop update prompt and decided to install it.
So I flashed my original recovery which I got from XDA site and when I start updating i get this issue.

MJ999 said:
No, I haven't done anything.
I will explain it to you again ( short )
Phone is rooted and S-ON and is having Original Rom 4.4.4 with 3.29.118.9
CID : T-MOB009
I got the Lollipop update prompt and decided to install it.
So I flashed my original recovery which I got from XDA site and when I start updating i get this issue.
Click to expand...
Click to collapse
Is 3.29.118.9 your firmware version, or your software version? Boot into bootloader, and your firmware is listed under OS. But you say you didn't flash firmware, so that version is the same?
Go to settings > about phone > more
What does the build number say? This is your software/ROM base. (The version of firmware that the ROM you are using is based on)

xunholyx said:
Is 3.29.118.9 your firmware version, or your software version? Boot into bootloader, and your firmware is listed under OS. But you say you didn't flash firmware, so that version is the same?
Go to settings > about phone > more
What does the build number say? This is your software/ROM base. (The version of firmware that the ROM you are using is based on)
Click to expand...
Click to collapse
3.29.118.9 is the software version.
HBOOT-3.19.0.0000
Build number : 3.29.118.9 CL392065 release-keys
I HAVEN'T FLASHED ANY FIRMWARE OVER MY PHONE.
I am trying to install OTA update btw
EDIT : I did flash the recovery from the update file( extracted the recovery from firmware.zip and flashed it)
Now error is different.
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
finding update package...
opening update package...
verifying update package...
Installing update...
L500CT.01.101.007
Verifying current system...
"/system/fonts/Robonto-Bold.ttf" has unexpected contents.
E:Error in data/media/0/Download/OTA_M*.......zip
(status 7)
Installation aborted
So I guess the font is creating the issue now.
Is there any way to flash stock rom on my phone ?
Is it possible ?

MJ999 said:
3.29.118.9 is the software version.
HBOOT-3.19.0.0000
Build number : 3.29.118.9 CL392065 release-keys
I HAVEN'T FLASHED ANY FIRMWARE OVER MY PHONE.
I am trying to install OTA update btw
Click to expand...
Click to collapse
Read this : http://forum.xda-developers.com/showpost.php?p=58511096&postcount=4106

ckpv5 said:
Read this : http://forum.xda-developers.com/showpost.php?p=58511096&postcount=4106
Click to expand...
Click to collapse
Yaw bro
I did flash the recovery from the update file( extracted the recovery from firmware.zip and flashed it)
Now error is different.
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
finding update package...
opening update package...
verifying update package...
Installing update...
L500CT.01.101.007
Verifying current system...
"/system/fonts/Robonto-Bold.ttf" has unexpected contents.
E:Error in data/media/0/Download/OTA_M*.......zip
(status 7)
Installation aborted
So I guess the font is creating the issue now.
Is there any way to flash stock rom on my phone ?
Is it possible ?
And which one should I flash/choose ?

MJ999 said:
Yaw bro
I did flash the recovery from the update file( extracted the recovery from firmware.zip and flashed it)
Now error is different.
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
finding update package...
opening update package...
verifying update package...
Installing update...
L500CT.01.101.007
Verifying current system...
"/system/fonts/Robonto-Bold.ttf" has unexpected contents.
E:Error in data/media/0/Download/OTA_M*.......zip
(status 7)
Installation aborted
So I guess the font is creating the issue now.
Is there any way to flash stock rom on my phone ?
Is it possible ?
And which one should I flash/choose ?
Click to expand...
Click to collapse
You need a clean backup because your system is messed up due to xposed

Mr Hofs said:
You need a clean backup because your system is messed up due to xposed
Click to expand...
Click to collapse
OK,so inorder to backup which RUU should I choose ?
RUU_M8_TMOUS_1.57.531.7.exe - this one didnt work for me
Mine is TM009 variant
and before you ask no I haven't made a backup of my original ROM.

MJ999 said:
OK,so inorder to backup which RUU should I choose ?
RUU_M8_TMOUS_1.57.531.7.exe - this one didnt work for me
Mine is TM009 variant
and before you ask no I haven't made a backup of my original ROM.
Click to expand...
Click to collapse
You need a ruu that starts with that version number you have *.**.118 or a stock backup that has *.**.118
The stock backup method also works with lower ones.

Mr Hofs said:
You need a ruu that starts with that version number you have *.**.118 or a stock backup that has *.**.118
The stock backup method also works with lower ones.
Click to expand...
Click to collapse
Can you please find me suitable ruu for my phone ?
Becauase now I am all confused.
Do you need to know any information from me ?
CID : TMOB-009
Build : 3.29.118.9

MJ999 said:
Can you please find me suitable ruu for my phone ?
Becauase now I am all confused.
Do you need to know any information from me ?
CID : TMOB-009
Build : 3.29.118.9
Click to expand...
Click to collapse
there are some backups here:
http://forum.xda-developers.com/showthread.php?t=2701376

Mr Hofs said:
You need a ruu that starts with that version number you have *.**.118 or a stock backup that has *.**.118
The stock backup method also works with lower ones.
Click to expand...
Click to collapse
leefear said:
there are some backups here:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
So I found the ruu for my phone and it was in rar file and I extracted it and it made a folder inside some files.
Now the question is how do I flash this folder into my m8 ?

[Q] OTA Failed Returned to Stock w/S-off

I've restored my stock nandroid backup and flashed stock recovery, but I can't get the OTA to install. My M9 is from T-Mobile, and it has S-off. Here's what I get.
E:missing bitmap oem_unlock_bg
(Code-1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
E:Find no match PARTITION: for package path @/cache/recover
/block.map
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
L50QCT.01 . 104 . 020
Verifying current system. . .
/dev/block/bootdevice/by-name/system has been remounted R?W
reflash device to reenable OTA updates
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted
Any help with this?

Another thought, I had problems getting Lollipop OTA with my M8, and I had to run earlier RUU then do OTA's. Is that what I have to do now. It doesn't seem like I should have to go that route. Also I had a completely different error message then.

For you now RUU is a must..
The steps needed as I wrote somewhere there:
http://forum.xda-developers.com/showthread.php?p=60114607
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection

jauhien said:
For you now RUU is a must..
The steps needed as I wrote somewhere there:
http://forum.xda-developers.com/showthread.php?p=60114607
HTC ONE (M9) RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection
Click to expand...
Click to collapse
I was afraid of that. I hate having to redo everything. Thanks for your input.

This is why you need to take a backup of the stock system before rooting... Once system is mounted rw no OTA will be taken naturally...

sgt. slaughter said:
This is why you need to take a backup of the stock system before rooting... Once system is mounted rw no OTA will be taken naturally...
Click to expand...
Click to collapse
I did do a backup before I rooted, but I still have this problem.
Sent using XDA Free Mobile App

Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data. ?
Sent From My HTC One (M9)

Rydah805 said:
Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data. ?
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks I will go there tonight and check it out, and I will let you know what happens.
Sent using XDA Free Mobile App

Rydah805 said:
Or you could just go to the T-Mobile forum and find my thread and find out what to do to correct this, and maintain your data.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thank you Rydah805 for your suggestion and work in that Thread. I also want to thank @Captain_Throwback for his work in the thread that you linked to in your thread. I wiped everything except storage, took the nandroid backup I did when I first got my device and restored that. Then I extracted the system.emmc.win from my backup, and after renaming it to system.img I flashed it via fastboot then rebooted the phone. I then rebooted into recovery checked to see if the system option was missing from the mount menu in TWRP, and it was. After that I extracted the recovery.img from the update I had downloaded and flashed it via fastboot. After that it was automatic. I went to software updates, downloaded the update and let it install. Then I did another nandroid backup and rooted the phone again installed Titanium Backup and restored my apps and settings. All good! Thanks again!

[Q] EU M9 still says "software status:modified" after RUU

Hi all
i wanted to go fully stock on my M9 to get official OTA.
but after i flashed the 1.40.401.8 RUU it still says "software status: modified" in the bootloader.
so the question is; will it break OTA or is it just annoying looking at?
thanks in advance.

KasperHermansen said:
Hi all
i wanted to go fully stock on my M9 to get official OTA.
but after i flashed the 1.40.401.8 RUU it still says "software status: modified" in the bootloader.
so the question is; will it break OTA or is it just annoying looking at?
thanks in advance.
Click to expand...
Click to collapse
If you were soff then you could return to full stock, just unlocking the boot loader then relocking it will show the tempered flag, personally never wanted to go back to stock for an ota so not 100% as to whether it'll work, a fair few people have said returning to stock and then accepting the ota is a way to get the firmware upgraded so I assume that it's OK.
If its not then it'll just fail. Shouldn't break anything, ota should always leave a way back

KasperHermansen said:
Hi all
i wanted to go fully stock on my M9 to get official OTA.
but after i flashed the 1.40.401.8 RUU it still says "software status: modified" in the bootloader.
so the question is; will it break OTA or is it just annoying looking at?
thanks in advance.
Click to expand...
Click to collapse
I think you have to flash an untouched system image for your device to take OTA that way. Why not just run the RUU for the new software/firmware?

dladz said:
If you were soff then you could return to full stock, just unlocking the boot loader then relocking it will show the tempered flag, personally never wanted to go back to stock for an ota so not 100% as to whether it'll work, a fair few people have said returning to stock and then accepting the ota is a way to get the firmware upgraded so I assume that it's OK.
If its not then it'll just fail. Shouldn't break anything, ota should always leave a way back
Click to expand...
Click to collapse
so there is no going back to unmodified after i modified the software, without throwing 20$ at sunshine?

BUBBA DUB'S said:
I think you have to flash an untouched system image for your device to take OTA that way. Why not just run the RUU for the new software/firmware?
Click to expand...
Click to collapse
the newest RUU i can find is 1.40.401.8 and i already flashed that and it still says that its modified

KasperHermansen said:
the newest RUU i can find is 1.40.401.8 and i already flashed that and it still says that its modified
Click to expand...
Click to collapse
Oh ok gotcha, I know to go back to completely stock to get OTA you have to find untouched system image and change something's around in twrp. Check out post #3 in this thread and read FAQ's #8.
http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720

KasperHermansen said:
so there is no going back to unmodified after i modified the software, without throwing 20$ at sunshine?
Click to expand...
Click to collapse
nope...
it's $25, not $20...

jollywhitefoot said:
nope...
it's $25, not $20...
Click to expand...
Click to collapse
I though with twrp if you made a system image back up in "read only" you can flash that and stock recovery after making a few changes in twrp and be fine to take OTA.

BUBBA DUB'S said:
I though with twrp if you made a system image back up in "read only" you can flash that and stock recovery after making a few changes in twrp and be fine to take OTA.
Click to expand...
Click to collapse
That's correct. I wasn't disagreeing with anything. Just saying Sunshine S-Off is $25, not $20...unless it's been discounted since I did it.
But no matter what you do, once your device status in bootloader changes to modified, you can't change it back to "official" without s-off.

jollywhitefoot said:
That's correct. I wasn't disagreeing with anything. Just saying Sunshine S-Off is $25, not $20...unless it's been discounted since I did it.
But no matter what you do, once your device status in bootloader changes to modified, you can't change it back to "official" without s-off.
Click to expand...
Click to collapse
Lol gotcha yea I'm at work so I don't always completely read things. My bad.

BUBBA DUB'S said:
I though with twrp if you made a system image back up in "read only" you can flash that and stock recovery after making a few changes in twrp and be fine to take OTA.
Click to expand...
Click to collapse
That's what my understanding is too. After installing TWRP take stock backup before rooting. Then install backup before taking OTA. One question though. SuperSU has an option to remove root. Will have to try this on the next OTA.

BUBBA DUB'S said:
Lol gotcha yea I'm at work so I don't always completely read things. My bad.
Click to expand...
Click to collapse
LOL. Who has time to read these days???
Flash first...then ask cryptic questions...find an outdated M8 youtube video or skim some old M7 tutorials...worst case scenario is to read and understand. (BTW, this is not directed at you...your post just made me think of the typical non-reading user)

KasperHermansen said:
so there is no going back to unmodified after i modified the software, without throwing 20$ at sunshine?
Click to expand...
Click to collapse
No there isn't. Soff, you will have been down this prior to unlocking
---------- Post added at 06:37 PM ---------- Previous post was at 06:36 PM ----------
jollywhitefoot said:
That's correct. I wasn't disagreeing with anything. Just saying Sunshine S-Off is $25, not $20...unless it's been discounted since I did it.
But no matter what you do, once your device status in bootloader changes to modified, you can't change it back to "official" without s-off.
Click to expand...
Click to collapse
Still 25

To return to official status instead of modified simply run the RUU.zip using the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
Click to expand...
Click to collapse
With s-off it will not change back to modified again
you can read all about it here >> http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882

clsA said:
To return to official status instead of modified simply run the RUU.zip using the 0PJAIMG.ZIP method
With s-off it will not change back to modified again
you can read all about it here >> http://forum.xda-developers.com/one-m9/general/how-to-restore-software-status-original-t3092882
Click to expand...
Click to collapse
After it's relocked, it'll still say tampered.

Sorry to bother, could someone help me please? http://forum.xda-developers.com/one-m9/help/conversion-to-developer-edition-t3151596
Thanks!

dladz said:
After it's relocked, it'll still say tampered.
Click to expand...
Click to collapse
m9 do not say tampered - they say Official or Modified
as far as I know the 0PJAIMG.ZIP method works on s-on also ... (never tried it though)

clsA said:
m9 do not say tampered - they say Official or Modified
as far as I know the 0PJAIMG.ZIP method works on s-on also ... (never tried it though)
Click to expand...
Click to collapse
Sorry I meant modified
I've never had to do it, but what would be the point of it if you could just flash that zip and you're back to stock?

dladz said:
Sorry I meant modified
I've never had to do it, but what would be the point of it if you could just flash that zip and you're back to stock?
Click to expand...
Click to collapse
I don't understand your question "what would be the point of it if you could just flash that zip and you're back to stock?"
if you use the 0PJAIMG.ZIP flash method it resets the phone to Official (isn't that what this thread is about ?)
with s-on the 0PJAIMG.ZIP would have to be your current firmware version or newer (you need s-off to go backwards)
this is all in theory as I have never flashed the 0PJAIMG.ZIP with s-on but it should work
OMJ describes using it with s-on here >> http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Those are Sprint files but the method is the same

clsA said:
I don't understand your question "what would be the point of it if you could just flash that zip and you're back to stock?"
if you use the 0PJAIMG.ZIP flash method it resets the phone to Official (isn't that what this thread is about ?)
with s-on the 0PJAIMG.ZIP would have to be your current firmware version or newer (you need s-off to go backwards)
this is all in theory as I have never flashed the 0PJAIMG.ZIP with s-on but it should work
OMJ describes using it with s-on here >> http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Those are Sprint files but the method is the same
Click to expand...
Click to collapse
I don't think they'll work. It'll still say modified.