Database Develop

[Q] Tried to get my One back to Stock, gone wrong somehwere

Hi, recently the screen broke on my 2 week old HTC One.
Amazon were kind enough to send me a new one, but I had modded the hell out of the first one (using various online tutorials to root and then ROM it), and now have the need to return it.
So I followed various tutorials to try and restore it back to 100% stock. (Didn't bother making it "Locked" rather than "Unlocked").
What I did was I used the HTC One All-In-One Toolkit, and "relocked bootloader". I then tried to flash the RUU, all went well, but when I try to start it up after, it gives a blank black screen. However, after giving it a while, holding the power button, or pressing the back button sometimes results in a vibration, so I'm presuming that it is starting, but not displaying anything. I was hoping that my phone would come up in windows so I could re-flash twrp and flash Sense that way, but it does not appear.
I tried factory resetting in this state, but when I try boot it up after that, a logo comes up which is a phone, with 2 green arrows forming a circle inside it, then a green arrow pointing down inside that.
Also, flashing twrp.img seems to go well, but when select "recovery", nothing happens, it just seems to boot up normally.
I am now at a loss of ideas, as this process was suggested by all the sources I could find, and it works perfectly for them, see no reason for it not to for me.
If anyone has any idea how to fix this, please, please respond as quickly as possible, it has to be with Amazon by the 4th, and I have no clue what to do!
Thanks,
-Accudio

yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?

matt95 said:
yeah i got the point here, just one question, are you S-OFF or not? if yes, which is you bootloader?
Click to expand...
Click to collapse
No, I'm S-ON, when I first did it I was a bit of a noob, and none of the tutorials I followed said anything about S-ON/S-OFF. Only just found out about it when researching how to put it back. :/

You can't access recovery because your phone is locked, so first off you need to unlock again your phone

matt95 said:
You can't access recovery because your phone is locked, so first off you need to unlock again your phone
Click to expand...
Click to collapse
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?

Accudio said:
Gotta go now, but well do when I next can. Using the "Unlock Bootloader" tool on the HTC Dev website yeah?
Click to expand...
Click to collapse
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...

matt95 said:
Yeah, however you can use the previous Unlockcode.bin that you used to unlock it the first time...
Click to expand...
Click to collapse
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?

Accudio said:
OK, I have now unlocked it, I'd flash TWRP now yes?
EDIT: Now flashed TWRP, it's working fine, but how can I transfer the ROM zip across without having a version of android that works?
Click to expand...
Click to collapse
adb commands work in recovery too.
either use "adp push rom.zip /sdcard/" or use the sideload method

Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
EDIT: I am downloading a different ROM to try, so hopefully that will work better.

Accudio said:
Thanks a lot guys, you've been a great help! 2 more questions for you if you don't mind:
1. The ROM I found doesn't seem to work properly, so have you got any ideas of ROMs of Sense 5, no root, so it will appear to amazon that it is stock, even if it isn't exactly, or do you know where I can get an RUU and how to flash it to get my phone back to exactly stock?
2. This won't be a big deal, but how could I achieve S-OFF to revert my HTC recovery to say "Locked" rather than "Tampered" and "Relocked"
If they aren't possible, no big deal, just would be nice if I can. Again, thanks a ton, you've saved my neck! xD
Click to expand...
Click to collapse
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
Click to expand...
Click to collapse
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.

Accudio said:
Yeah, I dropped it onto my carpet and the screen cracked pretty majorly, so I contacted HTC pretty annoyed (as you can expect), and they said that I must have had a dodgy model for it to have broken so easily. Amazon was reluctant but because I had HTC's word they sent me a free replacement.
Click to expand...
Click to collapse
Wow. thats nice of them. Read my previous post to answer your questions. I added another option.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.

Accudio said:
I have HBOOT version 1.54, so as the Revone thread says I cannot use that. Is there any other way or will I just not be able to do it? Had a quick look and couldn't find anything.
Click to expand...
Click to collapse
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?

aooga said:
ohhh..that might be a problem. How did you manage to get on hboot 1.54? I don't think there is a S-off method for that yet. Do you still have the unlockcode.bin from when you unlocked it the first time?
Click to expand...
Click to collapse
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
You should be able to unlock your bootloader again with the unlockcode.
If I'm not mistaken, in order to flash a RUU you need to:
- Flash stock recovery.img through bootloader+fastboot
- Flash stock boot.img through bootloader+fastboot
RUU should flash now whether bootloader is locked, unlocked or relocked.

Accudio said:
I don't know, if I remember correctly it was actually on that when I got it, not certain though. I do have my first unlockcode.bin saved.
Click to expand...
Click to collapse
as long as you used that file to unlock this phone, then it will work.

Ok, I'm getting an error saying:
"Unfortunately, HTC Sense has stopped."
and also
"Unfortunately Contacts Storage has stopped."
I had the Contacts srtorage one with my old S2, which I fixed by clearing data of contacts storage, but the one about HTC sense stops anything from working.

aooga said:
1. Just download a stock odexed rom from the development section. There are many to choose from.
OR
Pick a RUU from here. http://forum.xda-developers.com/showthread.php?p=39588860
2. Use this link to do that. Then read the instructions on how to reset the flags.
Did amazon really replace your broken phone for free? Thats what I call customer service. Too bad I bought mine from ATT.
THIRD OPTION:
Download http://forum.xda-developers.com/showthread.php?t=2353083
And remove supersu.apk from the zip file before you flash it.
Click to expand...
Click to collapse
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?

Accudio said:
Sorry if I'm being a bit of a noob, how would I remove superuser.apk?
Click to expand...
Click to collapse
if you have a pc, before you push the rom to your phone, open the zip file and delete the apk in /system/app/supersu.apk

Developer red message when booting!

Hi, I just flashed Revolution HD 31 rom to my HTC One... Great Rom BTW! Its there any way to disable or delete the Red developer build message when phone is booting? I looked around and found that its better to leave it that way or flashing stock room before dealing with it.. its there an easy method to delete it? like triangle away or something for samsung phones? Thanks:good:

Pidis said:
Hi, I just flashed Revolution HD 31 rom to my HTC One... Great Rom BTW! Its there any way to disable or delete the Red developer build message when phone is booting? I looked around and found that its better to leave it that way or flashing stock room before dealing with it.. its there an easy method to delete it? like triangle away or something for samsung phones? Thanks:good:
Click to expand...
Click to collapse
If you are s-off there are hex-edited hboots around without the red text, but if you ever go s-on by mistake with the modified hboot you'll probably have a brick on your hands.

Pidis said:
Hi, I just flashed Revolution HD 31 rom to my HTC One... Great Rom BTW! Its there any way to disable or delete the Red developer build message when phone is booting? I looked around and found that its better to leave it that way or flashing stock room before dealing with it.. its there an easy method to delete it? like triangle away or something for samsung phones? Thanks:good:
Click to expand...
Click to collapse
Question really is how often do you restart your phone

Pidis said:
Hi, I just flashed Revolution HD 31 rom to my HTC One... Great Rom BTW! Its there any way to disable or delete the Red developer build message when phone is booting? I looked around and found that its better to leave it that way or flashing stock room before dealing with it.. its there an easy method to delete it? like triangle away or something for samsung phones? Thanks:good:
Click to expand...
Click to collapse
If you really want the latest modified hboot with no red message, there ya go

attanasi0 said:
If you really want the latest modified hboot with no red message, there ya go
Click to expand...
Click to collapse
I never really cared about it, but when i found out i could load the GE Hboot on my regular One (despite is only 1.54 for now).. I was sold. Seriously love to have a black background on my HBOOT (And gettin´ rid of the red text.)

nkk71 said:
If you are s-off there are hex-edited hboots around without the red text, but if you ever go s-on by mistake with the modified hboot you'll probably have a brick on your hands.
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 won't run with a modded hboot. Going back to s-on another method may cause a brick.

ok thanks everyone ^^

[Q] Velocity 4G (VODAP120) boot loop / can't RUU

Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings

deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice

rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!

Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk

rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.

deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk

rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:

is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?

deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk

rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...

deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!

The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One

WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?

Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.

well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?

AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk

If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.

I need help 5.03.651.3

I NEED HELP WITH THIS http://forum.xda-developers.com/showthread.php?t=2795856
how my phone is now
HTC one m7 rooted S-off unloacked
Hboot 1.55
4.4.2
4.06.651.9
openrecovery-twrp-2.8.0.2-m7wls
I did everything in the video
using Fast boot with the Modified Firmware everything went ok with no problems
I did not even get the "please flush image again immediately" thing
after booting back into the phone I find out that nothing has changed what so ever
& I know what to look for because my mom has the same phone all up to date but with out root & s-off etc...
I want this update real bad so I can turn off blinkfeed & you can only do that on Sense 5.5 or higher.
Well the place where you go to turn it off is not there :crying:
I'm no noob but I don't do this kind of updating everyday
so what am I doing wrong????

Are you trying to use that RUU?
If so you will need to flash the full firmware first then the RUU.

Now my phone is fubar!!!!!!
I was trying 5.03.651.3_modified_firmware_RUU.zip when I did it
the full what??
be descriptive
and to make matters worst I have ****ed up the OS.
I got sick of w8ing for help so I tried doing the full 5.03.651.3_firmware_RUU.zip
it will no longer boot into the OS
all I got now is Hboot & twrp This is bull **** there has got to be easier ways then this
So now what do I do????????????????????????????
The good news I'm now on Hboot 1.57

I know it's frustrating but easy with the swear words.
Run the RUU and you should be good.

I need help!!!!!!
ok dude I'm not trying to be an ass H
I'm just realy realy realy Fing mad
so if you are not going to give me step by step instructions
then your not going to be much help to me
I'm no pro at this
so to recap my HTC one is fubar & all I got is Hboot 1.57 & twrp-2.8.0.2-m7wls
I went into twrp & did a wipe on sys in the hope that would fix
so I did the wipe & went back to Hboot & flash boot the 5.03.651.3_modified_firmware_RUU.zip & now when I boot into the OS
all I get the white HTC screen & nothing more

is there anyone who is going to help me?????

Well looks like it a brick now
nothing I do is fixing this
not 5.03.651.3_modified_firmware_RUU.zip
not 5.03.651.3_firmware_RUU.zip
and I tried rolling back to the old one modified_firmware_4.06.651.9.zip
no matter what I do all I get the white HTC screen & nothing more :crying:
looks like I will have to go to sprint tomorrow :crying::crying::crying::crying::crying::crying::crying:

Flash Full Firmware
Run RUU

OMG!!!!!!!!!!!!!!!!!
OMG! dude you are killing me "give me step by step instructions"
what is Run RUU??????????
I am not a pro at this I don't do this everyday!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

E-TARD_The_LifeCaster said:
OMG! dude you are killing me "give me step by step instructions"
what is Run RUU??????????
I am not a pro at this I don't do this everyday!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
-Download Sprint_HTC_One_m7wls_5.03.651.3_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock

OK I'm downloading that now
OK I'm downloading that now, its big so will take 19 min to D/L
but why do I need that one?
why can't I use the 5.03.651.3_modified_firmware_RUU.zip?
just so I know for next time...

E-TARD_The_LifeCaster said:
OK I'm downloading that now, its big so will take 19 min to D/L
but why do I need that one?
why can't I use the 5.03.651.3_modified_firmware_RUU.zip?
just so I know for next time...
Click to expand...
Click to collapse
You need to RUU because you wiped your OS in twrp.
The modified firmware does not include hboot/recovery/boot.img(kernel)
The reason you don't have an OS is you wiped it in twrp.
Build number/Software won't change unless you flash a 5.03.651.3 rom.
The best way to check if it worked is to check the baseband to see if it changed.

ok its working again
ok its working again
I did not know that was the file I needed, I thought that's a stock rom so why would I want that
so I went for the other files.
This RUU app is new to me.
Thank you for helping me I just feel the way this http://forum.xda-developers.com/showthread.php?t=2795856 post was typed up did not help me at all (I was lost)
Be descriptive people! make life easy for everyone

No No-Thanks Meter? Damn!
Just checking in/out. Just sold my m7wls for 182$ on ebay.
Trying to figure out if the colorfly i108w 4g will work on any US dataservice...?
Thanks Cyanogen!!! and thanks to all the helpful people who make this forum a pleasure.
Please lock this thread.:good:

BD619 said:
You need to RUU because you wiped your OS in twrp.
The modified firmware does not include hboot/recovery/boot.img(kernel)
The reason you don't have an OS is you wiped it in twrp.
Build number/Software won't change unless you flash a 5.03.651.3 rom.
The best way to check if it worked is to check the baseband to see if it changed.
Click to expand...
Click to collapse
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2

all fixed
JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
no the OS was Fed up before I did that sys wipe .
I only did the sys wipe because I thought that would help fix it what the modified firmware Fed up by removing the bad OS & retry installing the modified firmware.
before that I did the modified firmware & it soo did not work!!!!!
so I don't know what happened but I do know that post with the update was really vague for someone who does not do this kind of thing often.
I do have a?
& that is next time I do this
will it keep the app-data? or is there away to back that up
my phone is fine but I lost all app-data witch is kind of a pain in the but having to go over all the settings for all of my apps

JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
yes, I agree.BD is a good man.

E-TARD_The_LifeCaster said:
no the OS was Fed up before I did that sys wipe .
I only did the sys wipe because I thought that would help fix it what the modified firmware Fed up by removing the bad OS & retry installing the modified firmware.
before that I did the modified firmware & it soo did not work!!!!!
so I don't know what happened but I do know that post with the update was really vague for someone who does not do this kind of thing often.
I do have a?
& that is next time I do this
will it keep the app-data? or is there away to back that up
my phone is fine but I lost all app-data witch is kind of a pain in the but having to go over all the settings for all of my apps
Click to expand...
Click to collapse
Use titanium backup next time. It will save game progress, app settings etc.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2

JoeNeckbone said:
@BD619 your a saint with the patience of a monk...you help people all day long that can find the answers by simply searching but they are at least grateful for your help... But then you go a step further and help people like this.
Sent from my kangaroo powered Inverted ViperONE using Tapatalk 2
Click to expand...
Click to collapse
+1 for BD FTW
perfect example of why not everyone should be rooting their phones.

How to flash from 1.32 to 1.40 without losing your freaking mind (requires S-Off)

So yeah the people in the Int'l forums got that 1.40 OTA and the ROM devs have updated their ROMs to the 1.40 base.
Of course, this means we T-Mobile users are absolutely screwed unless we too update to the 1.40 base since trying to flash anything with the 1.40 base will make us bootloop and cry and swear. Mostly cry...and swear.
So here's a quick guide on getting your device to the 1.40 base so you can actually flash those ROMs again. Here we go. Note: I'm not responsible if anything bad happens. I sympathize, but it's not my bad.
Prerequistes:
1. You need S-Off. That means you'll need to fork out $25 to Sunshine and get it done.
2. You need Minimal ADB and Fastboot. The link for that is here.
3. An external SD card large enough to hold one nandroid backup and one ROM.
4. You'll need to make a Nandroid backup for your protection.
Guide:
1. First thing's first. You'll need to download ANY 1.40-based ROM. It doesn't matter which one, whatever one you want. Put that on your EXTERNAL SD CARD. You can find those in the Android Development section of the HTC One M9 international forums. The link for that is here. I highly recommend one that boasts that it's compatible with T-Mo devices. I flashed one of the Int'l-only ones and lost mobile data. Had to download and install another ROM. Learn from my mistakes.
2. Next you'll need to pick up the 1.40 firmware. The one I used is linked here. You'll want to download the latest one.
3. Now we get to have some fun. Open up minimal adb and fastboot and put your One M9 into DOWNLOAD MODE. Type "fastboot devices" without the quotes to make sure your device is recognized. If not, you need to go download the HTC One M9 drivers (just download and install HTC Sync). Once fastboot recognizes your device, type this command:
Code:
fastboot oem writecid 11111111
That is eight 1's, by the way. This will make your phone capable of flashing just about any firmware. Be careful and don't flash everything you find on the Internet. Once done, reboot back into download mode if it's not already there.
4. Rename the 1.40 firmware you downloaded to "update.zip" (no quotes) and put it in the minimal adb and fastboot folder (usually under C drive in the program files x86 folder).
5. Okay kids, this is the hard part so pay attention. You're going to flash the update TWICE. Why? I'll explain in the moment. Type these commands in order:
Code:
fastboot oem rebootRUU
followed by:
Code:
fastboot flash zip update.zip
Now at this point you'll probably get something like "90 Fail" or "Fail 90". What's just occurred is that part of the update was flashed, but not all of it. Sometimes it'll un-**** itself and continue on its own but usually not. To fix it, simply type the command a second time:
Code:
fastboot flash zip update.zip
This should complete the flash.
6. Reboot back into your recovery. Mount any partitions that may not be mounted.
7. Flash the ROM you downloaded back in step 1. Make sure you wipe everything (system, data, cache, dalvik) before doing so.
8. Reboot and enjoy.
Now that should be it. If you have problems, you'll want to visit this thread and the thread you downloaded the 1.40 firmware from (linked above) because those guys seem to know what they're doing and I really don't.
From this point forward, you SHOULD be able to flash any 1.40 based ROM without issues or cheap fixes (like in the ViperROM...by the way, it was really awesome of them to include that fix, even if it was a cheap fix. Thanks guys!).
Also, a big thanks to NO ONE for writing this guide anywhere else. Good job, jackass. As per the norm, you don't have to thank me and I don't care if you copy/paste the guide somewhere else without giving me credit. Information is free.

Is there any way to keep WiFi calling? Do I need to flash a modern or radio?

Is the T-Mo version of this updated ROM expected to release soon ?

I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?

jbfountain said:
I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?
Click to expand...
Click to collapse
Flash the firmware and then the T-Mobile radio

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
Anyone try the 2.7 firmware with a TMO radio?

123421342 said:
Anyone try the 2.7 firmware with a TMO radio?
Click to expand...
Click to collapse
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
That's the way I did it, but still had bad reception until I flashed the T-Mobile firmware again.
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
xHVGx said:
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983. You can flash it using TWRP according to this thread. Let us know how you do.
Cheers

Prasad said:
Is the T-Mo version of this updated ROM expected to release soon ?
Click to expand...
Click to collapse
Expect something newer than 1.40 coming very soon. ? I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
so pretty much 2.7 TMO confirmed within a week?

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.

guyverzero said:
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.
Click to expand...
Click to collapse
I've forgotten that this thing heats up. ? expect something very soon.
Sent From My HTC One (M9)