Hi there,
Is it as simple as just flashing a stock rom (RUU)? If this is the case, which RUU version do I need, I have an unlocked phone (Europe, Belgium).
Need to revert back to stock because I need to get it fixed under warranty.
I am aware there are some guides on the forum, but I haven't found a clear one yet...
Best Regards
yannickwellens said:
Hi there,
Is it as simple as just flashing a stock rom (RUU)? If this is the case, which RUU version do I need, I have an unlocked phone (Europe, Belgium).
Need to revert back to stock because I need to get it fixed under warranty.
I am aware there are some guides on the forum, but I haven't found a clear one yet...
Best Regards
Click to expand...
Click to collapse
I would try running this one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed
Thanks for the link. I've tried it and it all works, yet my phone is still S-OFF.
Bootloader gives this info:
-Revolutionary-
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.06.03.03_M
eMMC-boot
I'm not sure what they check in order to find out if the warranty is voided, but I reckon they'll stumble upon this info.
yannickwellens said:
Thanks for the link. I've tried it and it all works, yet my phone is still S-OFF.
Bootloader gives this info:
-Revolutionary-
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.06.03.03_M
eMMC-boot
I'm not sure what they check in order to find out if the warranty is voided, but I reckon they'll stumble upon this info.
Click to expand...
Click to collapse
Yes now that you have the ROM installed, you need to remove S-Off and Revolutionary HBOOT if you want it completely stock to return for warranty.
Search this forum for the process to remove Revolutionary.
I've searched the forums and came up with yet again a number of posts all describing another process. I really don't want to brick it, so if you would be so kind to give me the link that'll work on my incredible s .
yannickwellens said:
I've searched the forums and came up with yet again a number of posts all describing another process. I really don't want to brick it, so if you would be so kind to give me the link that'll work on my incredible s .
Click to expand...
Click to collapse
Follow the steps 2 - 2d in this post and then re-run the2.30.405.1 RUU:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
Alright, worked like a charm. Thanks a million, now I only need to worry that they don't see the broken void sticker on the screws inside(wanted to see if my problem was due to a faulty connector) .
Hopefully all goes well
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
mbinic said:
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
Click to expand...
Click to collapse
I just went through this a couple days ago with someone
go here and read pages 2-5 and see if you understand or still have questions read it all before moving on
http://forum.xda-developers.com/showthread.php?t=2593387&page=2
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
mbinic said:
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
Click to expand...
Click to collapse
yes after the conversion to .401 you will have a EU device and can update and flash all the new roms as they come out.
make note of the 2 links posted about changing your MID / CID their important steps in the whole process
http://forum.xda-developers.com/showthread.php?t=2535365
this guide by @nkk71 is a good source of information your just doing a few things differently
http://forum.xda-developers.com/showthread.php?t=2541082
OK, so part one is going mostly smoothly for now - unlocked bootloader, flashed TWRP, backed up (uploading for sharing) + saved partitions for rumrunner if I end up needing them (also uploading), had a few bootloops but managed to get ARHD 31.6 running. Now onto rumrunner...
I got S-OFF with rumrunner in the first try! Now to re-read and change CID and MID (4:40 AM, fingers crossed, heart pounding)
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
mbinic said:
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
Click to expand...
Click to collapse
Almost
1- change you MID to PN071000 using the tool
2- with SuperCID you cannot receive OTAs, so you need to change CID to European unbranded, there are several (this will affect the country/language options): http://forum.xda-developers.com/showpost.php?p=48195855&postcount=98 (instructions are also in that post)
so for example, if you wanted Eastern European languages you would need to set CID to HTC__032
3- since you're on hboot 1.55, you need to downgrade that separately to 1.44
4- you can leave the phone UNLOCKED, and even TAMPERED, but if you prefer to set them LOCKED and remove TAMPERED you can follow my guide.
5- run the RUU you mentioned
6- KEEP S-OFF!!
OTAs will not be affected by unlocked bootloader, or S-Off
let me know if you need more details
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
mbinic said:
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
Click to expand...
Click to collapse
yep, that works!
don't want to confuse you , but 1 2 and 3 can be run in any order, most important is to do run the ruu as last step, once the ruu has completed you should immediately receive OTAs.
remember, stay S-Off, consider it your "get out of jail" card, in case you ever want to change something again.
Thanks again I'll try it in a couple of hours and report my progress.
Edit:
OK, got CID HTC__032 and changed MID successfully. AROMA hung at 0.00%, but a restart helped like it was described in the post. Now onto HBOOT and RUU.
Edit 2:
Installed HBOOT 1.44 and the Guru Bootloader reset - removed tampered and set locked (why not ). Running RUU in a few minutes...
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
mbinic said:
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
Click to expand...
Click to collapse
Congrats mate
Can you also edit main thread title to include [SOLVED], thanks
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
mbinic said:
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
Click to expand...
Click to collapse
4.4 (hopefully 4.4.2) not out yet for most, only US Dev Edition, and has a few "bad habits" for the rest of the world... no need to change CIDs, it'll come soon enough....
ARHD 41.0 and MaximusHD are based on the US Dev Edition, not the WWE edition.
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
my htc
mbinic said:
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
Click to expand...
Click to collapse
hi friends first my english is not so good so excuse me i a have some mistakes, then i want to say i was reading your experience, i got the same version of htc one HTC_332 this is the cid for latin america this is what htc supports tell me by email, ok i got a little questions maybe u can help me
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
for last i want to thanks for the time you take to anwer me
Hello edulaffont,
edulaffont said:
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
Click to expand...
Click to collapse
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
first
mbinic said:
Hello edulaffont,
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
Click to expand...
Click to collapse
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
edulaffont said:
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
Click to expand...
Click to collapse
I also got that update as soon as I bought the phone, some time in October/November I think, it's old.
I didn't change the firmware when I was converting to WWE, a .401 version wasn't out yet.
I did change it last night though, and installed ARHD 51 (it gives me more options than stock) and everything went smoothly (I even did a dirty flash).
Anyway, I recommend you stick to the original instructions (use old ARHD for rumrunner), and when you're done converting to WWE, ran the RUU and everything works you can choose wheter you want to get the OTAs and stay stock (KitKat 4.4.2 OTA for WWE just came out, with new firmware), or root and install any ROM you wish
Hi folks, long time listener, first time caller.
I have an HTC One (M7_UL) from EE UK.
Last year I unlocked, rooted and tried a few methods from XDA (toning down the crazy vibration, etc), then wanted to go back to stock in order to easily receive the 4.2.2 update that EE were sending out OTA. I messed something up and ended up having to sideload Teamwin recovery and the European 4.2.2 (2.24.401.1) ROM in order to have a working phone again. My own stupid fault. Have had no problems with it since and just left it as is.
However, I recently realised that I wasn't gonna get any more OTA updates, and having very little time to update to different ROMS myself these days, I'd kinda like to go back to the boring, easy life of getting the OTAs (probably six to nine months late, but whatever!)
I have been searching for a while but always end up with about twenty XDA browser tabs open and end up really confused.
The two issues I need to get sorted:
1) Does anyone know if EE UK have their own specific ROM, or if it is just the General European RUU that they send out? I can't find any specific EE ROMs anywhere, months of searching.
2) I only have access to Macs, not Windows machines.
Bootloader info:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO- 4A.17.3250.14
OpenDSP- v31.120.274.0617
OS- 2.24.61.1
eMMC- boot 2048MB
Jun 21 2013
QUESTION - Can anyone help me return to a state where I can receive OTA updates from EE UK *using a Mac*?
I would very much appreciate your input, please bear in mind I am not a n00b but neither am I particularly advanced in this stuff. So basically… I'm a n00b :silly:
blackpepperjc said:
Hi folks, long time listener, first time caller.
I have an HTC One (M7_UL) from EE UK.
Last year I unlocked, rooted and tried a few methods from XDA (toning down the crazy vibration, etc), then wanted to go back to stock in order to easily receive the 4.2.2 update that EE were sending out OTA. I messed something up and ended up having to sideload Teamwin recovery and the European 4.2.2 (2.24.401.1) ROM in order to have a working phone again. My own stupid fault. Have had no problems with it since and just left it as is.
However, I recently realised that I wasn't gonna get any more OTA updates, and having very little time to update to different ROMS myself these days, I'd kinda like to go back to the boring, easy life of getting the OTAs (probably six to nine months late, but whatever!)
I have been searching for a while but always end up with about twenty XDA browser tabs open and end up really confused.
The two issues I need to get sorted:
1) Does anyone know if EE UK have their own specific ROM, or if it is just the General European RUU that they send out? I can't find any specific EE ROMs anywhere, months of searching.
2) I only have access to Macs, not Windows machines.
Bootloader info:
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO- 4A.17.3250.14
OpenDSP- v31.120.274.0617
OS- 2.24.61.1
eMMC- boot 2048MB
Jun 21 2013
QUESTION - Can anyone help me return to a state where I can receive OTA updates from EE UK *using a Mac*?
I would very much appreciate your input, please bear in mind I am not a n00b but neither am I particularly advanced in this stuff. So basically… I'm a n00b :silly:
Click to expand...
Click to collapse
Have a read of this excellent guide created by @nkk71: http://forum.xda-developers.com/showthread.php?t=2541082
Should help get you on your way.
cr1960 said:
Have a read of this excellent guide created by @nkk71: http://forum.xda-developers.com/showthread.php?t=2541082
Should help get you on your way.
Click to expand...
Click to collapse
Thanks for the quick response cr1960!
First issue:
"First you need to be S-Off, this will NOT work with S-On!!!"
I'm S-On as seen in my bootloader info above. I've read it's dangerous to go back to S-On from Off, so does this mean I can't use this guide, ruling out going S-Off then S-On in order to follow it?
blackpepperjc said:
Thanks for the quick response cr1960!
First issue:
"First you need to be S-Off, this will NOT work with S-On!!!"
I'm S-On as seen in my bootloader info above. I've read it's dangerous to go back to S-On from Off, so does this mean I can't use this guide, ruling out going S-Off then S-On in order to follow it?
Click to expand...
Click to collapse
1- you can stay S-Off, it won't affect OTA updates
2- the only reason for going S-On (in my opinion), is if you're selling the phone or sending it in for warranty
3- it's not dangerous to go S-Off to S-On (unless you're using a modded hboot), however, if you do that on hboot 1.55+ it will very likely trigger a "tamper detected - rebooting" and TAMPERED is back in the bootloader, hence the guide says to go from S-Off to S-On at a very specific time.
nkk71 said:
1- you can stay S-Off, it won't affect OTA updates
2- the only reason for going S-On (in my opinion), is if you're selling the phone or sending it in for warranty
3- it's not dangerous to go S-Off to S-On (unless you're using a modded hboot), however, if you do that on hboot 1.55+ it will very likely trigger a "tamper detected - rebooting" and TAMPERED is back in the bootloader, hence the guide says to go from S-Off to S-On at a very specific time.
Click to expand...
Click to collapse
Ok, so I should just go S-Off and then proceed with your guide?
Thanks nkk
blackpepperjc said:
Ok, so I should just go S-Off and then proceed with your guide?
Thanks nkk
Click to expand...
Click to collapse
yep,
if you need more info, please post a "fastboot getvar all" (excluding IMEI and s/n)
Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MID: PN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
DorianG said:
Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MID: PN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
Click to expand...
Click to collapse
Nope it won't work, simply because you are s-on, you require 631 RUUs simple as that, you cannot flash a 1540 RUU, however if you go s-off then you can.
M7 UL mean HTC One model 7 not sure what the u stands for, but the L is with LTE support.
You would need to s-off your phone to change the cid and flash the developer firmware in order to flash the developer 1540 ruu, s-off can only be done using sunshine and will cost $25.
DorianG said:
Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MIDN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
Click to expand...
Click to collapse
1.56 rumrunner S Off
nothing will stop you just change CID BS_US001 and flash ruu
yatindroid said:
1.56 rumrunner S Off
nothing will stop you just change CID BS_US001 and flash ruu
Click to expand...
Click to collapse
So if I S-Off using rumrunner then change my CID to "BS_US001" I can successfully flash the RUU?
The thought of S-Off scares me slightly, can someone confirm that there's no chance that this method will brick my device, and that I won't have any issues with the radio?
DorianG said:
So if I S-Off using rumrunner then change my CID to "BS_US001" I can successfully flash the RUU?
Click to expand...
Click to collapse
Yes with s-off you'll be able to flash the firmware and then the RUU
The thought of S-Off scares me slightly, can someone confirm that there's no chance that this method will brick my device
Click to expand...
Click to collapse
The procedure to s-off itself is not risky, but when s-off is achieved, you'll always have to be careful what you flash. S-OFF remove protection from crucial partitions on your phone and let you flash anything you want without verification. So if you flash something not compatible with your phone, you can brick it.
and that I won't have any issues with the radio?
Click to expand...
Click to collapse
You'll be fine using dev edition on Canadian carriers. I have personally tested on Fido, Rogers, Telus and Koodo. Should work too on Bell/Virgin.
alray said:
Yes with s-off you'll be able to flash the firmware and then the RUU
The procedure to s-off itself is not risky, but when s-off is achieved, you'll always have to be careful what you flash. S-OFF remove protection from crucial partitions on your phone and let you flash anything you want without verification. So if you flash something not compatible with your phone, you can brick it.
You'll be fine using dev edition on Canadian carriers. I have personally tested on Fido, Rogers, Telus and Koodo. Should work too on Bell/Virgin.
Click to expand...
Click to collapse
Great, thanks! In terms of what's compatible, is it pretty much just using common sense, i.e. not flashing a rom meant for the M8 or some other phone, or are there more things that could make something incompatible that I would need to learn about in the future?
Also, the ROM I posted here and intend to flash, it's for sure compatible? Sorry I know I'm probably being a bit overcautious
DorianG said:
Great, thanks! In terms of what's compatible, is it pretty much just using common sense, i.e. not flashing a rom meant for the M8 or some other phone, or are there more things that could make something incompatible that I would need to learn about in the future?
Also, the ROM I posted here and intend to flash, it's for sure compatible? Sorry I know I'm probably being a bit overcautious
Click to expand...
Click to collapse
Yes its safe to use that ruu on your phone.
TO avoid potential brick, always make sure you flash files for
M7_U or M7_UL variant. Files for other variants (e.g M7WLS will brick your phone)
Do not try to flash roms for other phones. We often see ppl bricking their M7 because they have mistakenly flashed an HTC Droid DNA rom on it.
Check MD5 values on your download to make sure your files are not corrupted before flashing <--- important!
Ask questions if you are not sure of the file you want to flash.
---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ----------
and if you want to update your firmware, very important:
use a full firmware package
if using firmware package from ota files, they must be flashed incrementally.
alray said:
Yes with s-off you'll be able to flash the firmware and then the RUU.
Click to expand...
Click to collapse
Sorry, one final question. Do I understand you correctly that I need to first flash a new firmware for my phone before using the RUU? If so where would I find this? I originally thought that the RUU would update the firmware for me.
DorianG said:
Sorry, one final question. Do I understand you correctly that I need to first flash a new firmware for my phone before using the RUU? If so where would I find this? I originally thought that the RUU would update the firmware for me.
Click to expand...
Click to collapse
You normally need to be on 6.xx.xxx.x or 7.xx.xxx.x firmware to use the 7.xx.xxx.x RUU. You can try to use it but im pretty sure the ruu will stop at 5% (checking headers). If so, you must flash the firmware first. You can use the 6.07.1540.2 firmware posted in my thread.