Database Develop

Restoring HTC ONE to Stock (Vodafone UK)

I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance

robot1000 said:
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
Click to expand...
Click to collapse
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.

gee2012 said:
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?

robot1000 said:
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
Click to expand...
Click to collapse
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik. You can`t do anything with the OTA atm, not even flash a Vodafone CWM recovery i`am afraid.

gee2012 said:
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik.
Click to expand...
Click to collapse
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?

robot1000 said:
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
Click to expand...
Click to collapse
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.

gee2012 said:
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
Click to expand...
Click to collapse
I've just gone into Bootloader and it's showing Hboot as 1.44.0000 !!
Would you mind giving me a brief outline on what I should be doing to get my phone back to vodafone stock?y
Many Thanks

Would flashing the Vodafone OTA zip file in recovery be safe or do I need to S-Off the device?

Please can someone advise
Thanks

Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!

postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU

robot1000 said:
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
Click to expand...
Click to collapse
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.

postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
rider5512 said:
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
Click to expand...
Click to collapse
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?

robot1000 said:
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
Click to expand...
Click to collapse
Ok... you need to change that ID in the phone.
Reboot the phone to bootloader then fastboot and connect to pc then from your ADB directory on PC issue the command "fastboot oem writecid HTC__001" this will then give you the right ID for the RUU.
Note it's HTC__001.... 2 underscores !

S-Off issues... need help!

i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!

ssreynolds said:
i apologize in advance for the noob issues... I am having issues trying to achieve s-off on my htc one. i am rooted right now, running stock 4.3 GPE rom. I have TWRP recovery installed. everything works perfectly. however i would like to do a complete conversion so i will recieve OTA updates from google, and not have to worry about flashing roms. so when i first tried to achieve s-off , i was using revone method. i was getting an error code (-1) then i read that that method wouldnt work, if you were running 4.3. so i then restored my nandroid backup, which i was running 4.1.2. but before flashing my backup i did a system wipe, just to be safe. so i tried revone method again. only now i get error code (-6) so i gave up. but i think when i did my system wipe , i lost my stock back up? so my 2 questions are, where is my nandroid backup? did i lose it when i did a system wipe? and how can i achieve s-off? i am not sure how to tell what firmware version i am running, i didnt see it in settings anywhere, nor do i know what hboot i have (1.44 or 1.54?) how do i tell? thanks guys!
Click to expand...
Click to collapse
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again

LibertyMarine said:
Ok sir, I try to help you.
First, you need to have knowledge with ADB and fastboot, but you should have them both in a folder since you unlocked your device through HTCdev. Then open a terminal and navigate to this particular folder. When you connected your HTC One M7 with the computer and UNINSTALLED HTCSync you can type "adb devices" to ensure you have a connection to your cell phone. Then you have to boot into the bootloader with this command "adb reboot bootloader" and there you see on the first couple of lines your HBOOT version. You'll see it! Then you boot into the recovery from the bootloader and install a ROM from this side that matches a version of rumrunner s off: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
Secondly then getting updates from Google you need to proceed these steps:
http://forum.xda-developers.com/showthread.php?t=2358781
This will turn your device into a Google Play Edition!
Hit the thanks button if you understood it, for questions simply ask again
Click to expand...
Click to collapse
that helps some, lol. so i now know how to find out what hboot version i have (i'm assuming that because i have 4.3 i am running hboot 1.54).... so thank you! i saw the rumrunner thread for the latest s-off. i will proceed with those steps... as far as completing the full google play conversion that actually sounds pretty easy once you have s-off. i can handle that. ( change cid to googl0001 and flash the new ruu, and stock recovery done!)
so now i just need to know what firmware version i have?
did i delete my back up when i did a system wipe?

To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1

ssreynolds said:
To reiterate...
I am on hboot 1.44, rooted running a stock GPE 4.3 Rom. Also, I feel stupid, but I can't seem to find out what firmware version I have? So I have tried twice with no avail. First I tried the typical revone method , but i was getting an error code -1, because I was on 4.3. So I flashed my backup, and returned to my stock rom on 4.1.2, and tried again. This time I was getting an error code -6? So I temporarely gave up, until I saw the rumrunner method here on xda. Worst part is when I returned to stock, I did a system wipe before flashing back to my 4.3 GPE rom, and deleted my backup! So I am nervous about flashing anything else, being that I dont have a backup! Long story short, all I want to do is finish a complete GPE conversion, and I need s-off to change my CID. At this point, all I need to do is achieve s-off, flash the GPE CID, and then flash a stock recovery and I'm done! So any thoughts on how to help me achieve s-off without potentionally bricking this thing?
edit: my build number is JWR66Y.H1 , does this mean I am on 3.07.1700.1
Click to expand...
Click to collapse
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.

nkk71 said:
boot to bootloader -> FASTBOOT, connect your phone to PC and it will change to FASTBOOT USB (picture attached)
then type "fastboot getvar all" and post it (remove IMEI and s/n before posting), also post the date it shows on that white screen.
Click to expand...
Click to collapse
I don't have a camera to take a pic right now, but I can tell you the date is July 5th

ssreynolds said:
I don't have a camera to take a pic right now, but I can tell you the date is July 5th
Click to expand...
Click to collapse
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)

nkk71 said:
no need for camera, but you still need to post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1

ssreynolds said:
will do, as soon as I get home!
however if I flash a stock rom like the one I have attached, couldnt I just use revone method (./revone -P)?
http://forum.xda-developers.com/showthread.php?t=2370507 > this rom would put me on firmware version 2.24.401.1
Click to expand...
Click to collapse
Why don't you use a RUU and flash the stock recovery, so you can recieve OTA updates and then you can just choose the correct rumrunner s off file and let it do the work. Then you don't really have to worry about the version number and btw. you can simply look it up in the settings. Can you pls ask if I didn't explane it well? Because this is very probable^^

[SOLVED] CID change and repairs

There is no ruu for my phone (02___001) so now I have s off I was going to run a stock ruu and update to the latest firmware. If I send the phone back for repair and change my cid to HTC_001 would HTC know I have changed my cid even if I s on?

Anyone help me at all?

stovie_steve said:
Anyone help me at all?
Click to expand...
Click to collapse
Two things:
1- I dont know if they keep a record of IMEI (or s/n) <--> carrier, but I think they have to and do.
2- the CID is stored in several partitions, not only the one you change with fastboot writecid.
HOWEVER, it really depends on how far they're going to dig into this, if they are going to check their IMEI database or check the different partitions on the phone, just to "prove you wrong", I guess they could.
But then again, would it be worth all that hassle for them?
I dont have any experience with repair centers or how far they would go to prove that you changed something on your phone, and it's really quite country (and HTC people) dependent; for some they have no problem with an unlocked or relocked phone, and other even have a problem with S-Off (though they can't prove the phone didn't ship that way in the first place)
Better have someone from your region (O2 so UK?) post their experience(s)

Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?

stovie_steve said:
Ah that's ok
So you reckon it would be better to be completely stock with stock CID and leave it s-off as it could ha e shipped that way anyway even for a carrier branded phone?
Click to expand...
Click to collapse
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.

nkk71 said:
I honestly cannot say mate, have ZERO experience with this, just what I've read from other people; can't remember which countries, but some have sent their phone in for repair (eg for the purple camera issue) with tampered, unlocked etc and got either a repair or a brand new phone, others sent it completely stock, only with S-Off and were refused service (and the service center can't even prove it didn't ship that way, nor did they try).
Sorry can't help you out, or give any good advice about that.
I can help get you back to stock, or at least as close to stock as possible (you can check some of the other guys I've helped out in the Q&A section), but that's about as far as I can go.
Cheers & good luck
EDIT: one guy I helped (I think from Canada) got it 100% stock and S-On, and the a**holes still gave him a hard time, don't know what happened in the end, hope they fixed it for him.
Click to expand...
Click to collapse
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!

stovie_steve said:
If you could help me yes that would be great mate
The steps I took to get where I am are as follows:
1. I was running a stock 02 UK Rom (2.24.206.7) and achieved s off using rumrunner
2. I downgraded hboot to 1.44 and installed a stock ruu for cid HTC__001
3. I flashed cwm recovery and nandroid restored my phone to o2 backup 1.29.206.1 and flashed a stock recovery before locking the bootloader using adb shell command and then installing the updates (my cid was also changed back to 02___001 to do this). I note also that I'm not sure that the recovery was completely stock, as I had to manually reboot the phone a few times to allow the ota to install.
4. I upgraded my phone via various OTA's until the latest 3.62.206.1 firmware
5. Satisfied that the OTA had flashed the latest stock hboot, stock recovery and stock Rom I did fastboot oem writesecureflag 3. I got success and when I reboot it said tamper detected - rebooting. The bootloader is now locked, s on and tampered
What steps would you add/take away or change?
I can unlock again using htcdev and start again I guess
Would you advise maybe re running rumrunner once I'm back to version 2.24.206.7 and run all the commands again (lock, remove tampered) and then s on?
The reason I ran the ota from an earlier nandroid was because I thought I would restore everything to stock by ota
If you help me achieve this I will gladly buy you a beer lol!
Click to expand...
Click to collapse
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.

nkk71 said:
1- Well the steps you took sound very good (I personally, would have skipped all the OTAs), but can you elaborate on "when I reboot it said tamper detected - rebooting", do you mean that you had removed TAMPERED and it suddenly came back by itself???
2- For you to be able to fix this, you will need S-Off, I just checked rumrunner, and there's only a 3.62.401.1 package around, hopefully it will work, otherwise you will need: "If you mainver is not listed, please contact [email protected] with firmware version AND a link to the corresponding RUU and/or firmware ota package." (http://forum.xda-developers.com/showthread.php?t=2487888)
3- I guess you're going to have to unlock again, and try rumrunner 3.62.401.1 package and hope it works without the hassle of having to send in you firmware.
4- Beer won't be necessary, I'm actually enjoying a scotch at the moment ; maybe when I'm in London next time Otherwise hitting the thanks button, is more than enough!
So I guess, go ahead an unlock and try to get S-Off, post back with results. I'll keep an :cyclops: on the thread and help as much I can.
Click to expand...
Click to collapse
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?

stovie_steve said:
Yes the phone said on booting up the Rom - "tamper detected - rebooting" and then my bootloader said tampered
Click to expand...
Click to collapse
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
stovie_steve said:
I had to do the ota as I didn't have the stock recovery for version 1.29.206.7 as I knew the ota would flash an official recovery
Click to expand...
Click to collapse
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
stovie_steve said:
I guess I could 're-run s off rumrunner when I'm on 2.24.206.7 (the 2.24.401.7 version works for this) and reset all the flags and then s on again?
You think that could work?
Click to expand...
Click to collapse
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).

nkk71 said:
Hmmm, interesting (only saw 1 other post like that, I think), did that happen after the last OTA which updated hboot to 1.55; wondering if they "patched" something in 1.55.
The first OTA would have been enough, you didn't need to go all the way to 3.62; you had to manually reboot the first OTA yourself because stock recovery wasn't 100% correct, but after the OTA was successfully installed, you could have stopped at that.
Problem is you are already on 3.62 and downgrading isn't possible with S-On, so you're going to have to unlock and try a rumrunner package that get's you s-off. If the 3.62.401 rumrunner works or the 2.24.206.7 or whichever one works to get you S-Off it doesn't matter, but you do need to get S-Off (IMHO).
Click to expand...
Click to collapse
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner

stovie_steve said:
I'm going to unlock via HTC dev, install guru reset via recovery and s off again. Then 're run the nandroid backup ota til 2.24.206.7, n 're run rumrunner
Click to expand...
Click to collapse
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.

nkk71 said:
Okidoke, good luck :fingers-crossed:.
I'm two hours ahead of you... okay that sounds bad :silly:, what I mean is there's a two hour difference between us, but I'll keep checking your thread for a while longer (an hour or two). if you post something and I don't get back to you tonight, I'll definitely check again tomorrow.
Click to expand...
Click to collapse
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho

stovie_steve said:
No problem!
Right these are the steps I'm going to do
1. Unlock bootloader via HTC dev
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off
4. Downgrade hboot to 1.44
5. Restore nandroid backup for my 02 version 1.28.206.7
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match)
7. Go s-on to see what happens
8. If s-on fails in any way then redo the HTC dev unlock, 're run rumrunner and get s off again using the same version of rumrunner
9. Reset tampered flag and lock bootloader via adb shell
10. Retry s-on again
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Thoughts on this method? I'm just wondering if people tried going s on in hboot 1.55 caused this tampered message to appear or if I s on first and then update will it appear then after? I do t know. I'd like to hear your thoughts tho
Click to expand...
Click to collapse
Ok, my thoughts, in a nutshell
1. Unlock bootloader via HTC dev <- YES
2----- try rumrunner 3.62
2. Install guru reset for 2.24.401.8
3. Run rumrunner and get s off <- Ok, try, if it fails use above rumrunner 3.62
Once S-Off:
--- remove tampered: revone or http://forum.xda-developers.com/showthread.php?t=2477792
5. Restore nandroid backup for my 02 version 1.28.206.7
--- set phone to LOCKED, using revone (or http://forum.xda-developers.com/showthread.php?t=2475914)
------- you will need to have SU privileges which you can get using revone or flashing SuperSU; if you do flash SuperSU, uninstall it after getting LOCKED
6. Upgrade via OTA to 2.24.206.7 (mostly to fix the stock recovery to match) <- Yep
11. Upgrade to latest hboot without having to do writesecureflag 3 again
Once you have your bootloader "LOCKED", no TAMPERED, no red text on bootup, do "fastboot oem writesecureflag 3"
reboot three times and see if everything sticks, and don't take any other OTAs.
Hit me with a thanks if this was useful

So you think I shouldn't upgrade to the latest OTA once I get s on?

stovie_steve said:
So you think I shouldn't upgrade to the latest OTA once I get s on?
Click to expand...
Click to collapse
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )

nkk71 said:
Since you're sending it in for repair, why would you want to?
But anyway, as long as the above steps work to get S-Off (again and again, if necessary), you can try and see if you dont get that "tamper detected" thing again. If it doesnt show up again you're all good to go.
(and I would be curious if we could find out where that comes from. the "tamper detected" hmmm )
Click to expand...
Click to collapse
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol

stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either

stovie_steve said:
Ok so I'll do the HTC dev unlock and install the guru reset by recovery and s off again. The rumrunner for 3.62.401 does not work with my rpm version
After that I'll downgrade the hboot to 1.44, install an android 4.1.2 RUU and then flash my nandroid backup. I'll reset the tamper and lock bootloader after flashing stock recovery
Then I'll upgrade to 2.24.206.7 and try s on. If it fails. I'll run the rumrunner for version 2.24.401.8 which def works with that Rom version as confirmed by others. Then I'll do the reset flags again and try s on. Try few reboots then send in for repair once satisfied
Sound like a plan? I hope so lol
Click to expand...
Click to collapse
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.

nkk71 said:
Yep, sounds good, except I would unlock using HTCdev then immediately try the 3.62 rumrunner to get S-Off, if it works GREAT and you're pretty much sure to be able to "easily" get S-Off on any version.
If it doesn't S-Off then try the Guru Reset.
BTW, as soon as you unlock, do a nandroid and "adb pull" it to your PC! just in case.
Click to expand...
Click to collapse
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?

stovie_steve said:
N I need to downgrade the hboot otherwise my touch screen won't work with the nandroid backup. Then again I don't necessarily have to run the ruu either
Click to expand...
Click to collapse
the touchscreen drivers were part of the 2.xx firmware package, not hboot, so if you don't use a full RUU, it will break the touchscreen drivers, but you can use an OTG cable + mouse.
stovie_steve said:
And how to I keep hold of the 3.62.206.1 recovery before I do a nandroid backup?
Click to expand...
Click to collapse
Unfortunately you can't (anymore), but this one should be close enough: http://d-h.st/users/guich/?fld_id=25920#files, or the best thing is to get a hold of the OTA 3.62.206.1 file and extract it from it.
Anyway, in my humble opinion, first things first: unlock using HTCdev and see if you can get rumrunner to S-Off on 3.62.

Help me please! :(

My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me

JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
tried to boot into recovery with this command:
fastboot boot "C:\pathtorecovery\recoveryname.img"
Click to expand...
Click to collapse
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...

Thank you but have to wait until I get home in approx 4-5 hrs, will try it! Thanks

LibertyMarine said:
tried to boot into recovery with this command:
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...
Click to expand...
Click to collapse
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF

stovie_steve said:
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF
Click to expand...
Click to collapse
JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:

klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Edit: I found a way with HTC ONE Toolkit 2.0, hope I´ll get everything You said working

JeySee said:
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Click to expand...
Click to collapse
I already put it up mate it's "adb push Rom.zip /sdcard

klashnikoff said:
I already put it up mate it's "adb push Rom.zip /sdcard
Click to expand...
Click to collapse
Got Rom installed

JeySee said:
Got Rom installed
Click to expand...
Click to collapse
Ooo good good let me know how it goes

klashnikoff said:
Ooo good good let me know how it goes
Click to expand...
Click to collapse
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!

JeySee said:
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!
Click to expand...
Click to collapse
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware

klashnikoff said:
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware
Click to expand...
Click to collapse
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?

JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.

Everything done, thanks for your help!
Good night ;;?
Sent from my HTC One using xda app-developers app

klashnikoff said:
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.
Click to expand...
Click to collapse
Your welcome good night
Sent from my HTC One using xda app-developers app

klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair

LibertyMarine said:
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair
Click to expand...
Click to collapse
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris

klashnikoff said:
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris
Click to expand...
Click to collapse
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54

nkk71 said:
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54
Click to expand...
Click to collapse
Thought so. Thanks for clarifying

klashnikoff said:
Thought so. Thanks for clarifying
Click to expand...
Click to collapse
no problem, it might have actually been broken by accident, someone disassembled the code and saw a bad memcpy; sort of lost track of the post though

[Q] HTC one semi bricked (M7)

Hi guys basically i messed up, I tried installing a ruu.zip rom via TWRP which got stuck.
I then hard reset the phone and now there is no OS.
I can boot into the bootloader and TWRP recovery (2.5.0.0)
I have tried to flash several roms via sideloading and OTG but they keep failing.
The phone was rooted and had a unlocked bootloader and was running 4.1.2 android stock.
As you can tell i'm quite the noob. any help would be appreciated.
Forgive me if im in the wrong thread etc

Simplyalif said:
Hi guys basically i messed up, I tried installing a ruu.zip rom via TWRP which got stuck.
I then hard reset the phone and now there is no OS.
I can boot into the bootloader and TWRP recovery (2.5.0.0)
I have tried to flash several roms via sideloading and OTG but they keep failing.
The phone was rooted and had a unlocked bootloader and was running 4.1.2 android stock.
As you can tell i'm quite the noob. any help would be appreciated.
Forgive me if im in the wrong thread etc
Click to expand...
Click to collapse
Enter to fastboot and post fastboot getvar all .
Don't forget to delete serialno and imei details on your post.
You didn't mentioned the error that preventing to install the roms
Then we can see how to help you.
Thanks.

oksagi said:
You didn't mentioned the error that preventing to install the roms
Click to expand...
Click to collapse
my guess would be set_metadata errors

oksagi said:
Enter to fastboot and post fastboot getvar all .
Don't forget to delete serialno and imei details on your post.
You didn't mentioned the error that preventing to install the roms
Then we can see how to help you.
Thanks.
Click to expand...
Click to collapse
Bootloader info
M7_UL PVT ship S-ON RH
Hboot- 1.44.0000
Radio-4A.14 3250.13
OpenDSP-v26 .120. 274.0202
eMMC-Boot
I'm hoping that is what you mean. i'll update my OP as soon as it lets me

Simplyalif said:
Bootloader info
M7_UL PVT ship S-ON RH
Hboot- 1.44.0000
Radio-4A.14 3250.13
OpenDSP-v26 .120. 274.0202
eMMC-Boot
I'm hoping that is what you mean. i'll update my OP as soon as it lets me
Click to expand...
Click to collapse
no that's not what they meant, but it will do, that's not all the info though, does it list your CID in that list, usually HTC__XXX ?

Seanie280672 said:
no that's not what they meant, but it will do, that's not all the info though, does it list your CID in that list, usually HTC__XXX ?
Click to expand...
Click to collapse
my comment still holds
"I can boot into the bootloader and TWRP recovery (2.5.0.0)"
that's a lot of info, right there

nkk71 said:
my comment still holds
"I can boot into the bootloader and TWRP recovery (2.5.0.0)"
that's a lot of info, right there
Click to expand...
Click to collapse
I know he's using the wrong TWRP.
but......... im thinking this is his RUU (based on his current rom version and his baseband version)
http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
But to be sure I need his cid at least.
doesn't seem to know what he's doing with custom rom's, so this will put him back to stock, at least he'll have a working phone. :good:
EDIT: correction, that's not his RUU.

Seanie280672 said:
I know he's using the wrong TWRP.
but......... im thinking this is his RUU (based on his current rom version and his baseband version)
http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
But to be sure I need his cid at least.
doesn't seem to know what he's doing with custom rom's, so this will put him back to stock, at least he'll have a working phone. :good:
Click to expand...
Click to collapse
that is an M7_U ruu, and the OP is M7_UL... but right now RUU is irrelevant / a premature step
i can assume the OP is angry, frustrated, and panicking, so first priority would be to get his phone up and running, just to alleviate some of the tension... so let him flash a proper recovery for 4.4+ ROMs, then the installation will go fine, and then he's relaxed enough not to hit his phone with a hammer