****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.
BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.
Related
Hi there,
I purchased a HTC One (M8) recently in the UK that was locked to the EE network. After unlocking the phone via a SIM unlock, I wanted to convert the phone to a Google Play Edition using this guide, but am currently unable to obtain s-off neither using firewater nor using SunShine.
My question: Is there any known way to obtain s-off for this phone at the moment?
Here the corresponding data:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: [B]3.18.0.0000[/B]
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:[B] 2.26.61.1[/B]
(bootloader) version-misc: PVT SHIP [B]S-ON[/B]
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: [B]ORANG001[/B]
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 93c21861
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Log:
These are the things I have tried so far, I provide this additional information in the hopes that it is useful. I am not sure how detailed this should be, so please let me know if something important is missing!
Original phone: UK EE 16GB Android 4.4.3
System: Mac OSX 10.10, adb, fastboot installed
1. I read both the everything explained and the the FAQ
2. I then continued to follow Volmers guide until Section 2, where the execution of firewater failed with
Code:
remember the golden rule, NEVER take an OTA? Of course you don't
****** device patched by HTC, you are out of luck *********
3. After that I moved on to install SunShine; however, SunShine complains that
Incompatible! At this time, SunShine can not work on your phone, this is a known issue and we are working to address it.
Click to expand...
Click to collapse
This is probably where I should have stopped, but I mistook a statement made in this thread as encouragement to return to stock.
4. I returned to stock using the files available here, but SunShine did not work after that.
Stock works fine for now; however, the OTA breaks my wifi, just as mentioned here.
So did I miss anything obvious? Or is the current M8 model one that SunShine can not deal with?
Alternatively, is there any non-rooted, non-HTC-Sense (hehe), ROM that I could install that does not require s-off?
Thank you all for your time and support! If you have any questions, please let me know and I will try to provide as much detail as possible.
Cheers,
Tolotos
Sunshine works on stock or close to stock roms with Dalvik runtime.
HTC One M8
Elisha said:
Sunshine works on stock or close to stock roms with Dalvik runtime.
Click to expand...
Click to collapse
OK, I am currently running a stock nandroid backup from here and the runtime is Dalvik.
Is this correct?
Cheers,
Tolotos
May I suggest that you flash the Dev Edition Brightstar RUU. The RUU will make all your partitions stock. Then try Sunshine without doing any OTA updates to the Dev Edition.
HTC One M8
Thanks for the quick reply. I just checked the HTC dev downloads and there is no RUU for the HTC M8 available (brightstar or orange), but there is for the M7, which I don't have.
Also I am unsure how to proceed with a Dev edition RUU, a little bit more detail would be great.
Cheers,
Tolotos
Here you go: http://forum.xda-developers.com/showthread.php?t=2884777
This is Sense but it is stock and bloat free. Will give you all the stock partitions. Then try Sunshine after without doing and OTAs. If all goes well, you can convert to GPE with S-off.
Make sure you change to the correct CID or Super CID. You may need to change your MID too.
HTC One M8
Brilliant! Thanks, I will try this. One last question: Can you point me in the direction to change the CID and MID without s-off? In all the tutorials I read it always states that you need to be s-off to change these!
Or maybe I am just a bit confused, my apologies!
I found this for the MID: http://forum.xda-developers.com/showthread.php?t=2708581
Does this work without s-off?
Is changing the cid as easy as:
adb reboot bootloader
fastboot oem writecid 11111111
fastboot erase cache
fastboot reboot
Cheers,
Tolotos
Yeah CID and MID works without S-off. Check out the Vomer guide in the General section for the CID commands.
HTC One M8
Good Morning,
are you sure that s-off is not required for changing the CID? I tried the command in the vomer guide and this happens:
Code:
fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.001s]
finished. total time: 0.001s
The CID is unchanged. I cannot find another method for this, so it would be great if you could point out how to change the CID/MID without s-off.
Cheers,
Tolotos
Tolotos said:
Good Morning,
are you sure that s-off is not required for changing the CID? I tried the command in the vomer guide and this happens:
Code:
fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.001s]
finished. total time: 0.001s
The CID is unchanged. I cannot find another method for this, so it would be great if you could point out how to change the CID/MID without s-off.
Cheers,
Tolotos
Click to expand...
Click to collapse
You need S-OFF to change CID/MID.
cleared rancij
BerndM14 said:
You need S-OFF to change CID/MID.
Click to expand...
Click to collapse
This is what I gathered from the information in various threads, but I am new to this, so was unsure. Is it still possible to install the RUU mentionedin this thread ?
The instructions say that you need to change your CID/MID first, but also state that you can be s-on.
Any other ideas on how to get s-off to work on this specific model/configuration?
Thank you so much for the support!
Cheers,
Tolotos
I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Miqueas111 said:
I'm on Paranoid ROM (last).
Bootloader 3.16.
I would like 3.19 or .18 in order to use Android 5.0 (CM 12).
Click to expand...
Click to collapse
What exact variant do you have and have you achieved S-OFF yet ?
jball said:
What exact variant do you have and have you achieved S-OFF yet ?
Click to expand...
Click to collapse
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Miqueas111 said:
I have the 3.16 bootloader, and I have no idea of S-OFF, so i guess I'm S-ON .
Click to expand...
Click to collapse
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
redpoint73 said:
Don't guess. Boot into bootloader, and it will say either s-on or s-off near the top.
By variant, jball is asking what carrier version or CID.
Flash the proper firmware package for your CID, if its in the collection:
http://forum.xda-developers.com/showthread.php?t=2696282
Or alternately return to stock ROM and stock recovery, than official OTA to update to hboot 3.17 then 3.19.
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Code:
C:\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43NWM03051
(bootloader) imei: 358718050169510
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
C:\One_M8_All-In-One_Kit_v\data>
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
jball said:
@bassitone
How does anyone not know if they are S-OFF/S-ON ?
Did you buy your phone second hand ?
Do you know how to boot into hboot/bootlooader mode witch will inform you if your S-OFF or S-ON
Have you tried an up to date twrp cause the one your on is very old.
At&t is furthest from receiving OTA's in my opinion
Click to expand...
Click to collapse
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Mr Hofs said:
His fastboot getvar all output clearly states SECURITY - OFF ...... so he has an S-OFF device.
Click to expand...
Click to collapse
Right, yet he still states
"I believe I'm S-OFF"
jball said:
Right, yet he still states
"I believe I'm S-OFF"
Click to expand...
Click to collapse
Because I wasn't sure if something I did yesterday managed to undo my s-off status. First HTC device, and I went pretty far in restoring to stock
Thread cleaned.
Keep it CIVIL please.
bassitone said:
I'm having the same issue as the OP. Trying to get to Lollipop from the latest Paranoid Android ROM. Here's the output of fastboot getvar all in the spoiler. Can you please tell me exactly what to do, in what order, and what specific files to flash in order to get my phone updated to a 5.0 ROM? I've been trying to follow this post, but something's just not clicking for me. I've already bricked my phone to the point where flashing the RUU from HTCDev was the only thing that'd save it - two separate times. Believe I am s-off, with TWRP 2.7.0.1 installed, but on the AT&T Stock ROM 1.58.502.1. Checked for OTAs, and I'm apparently up to date...
Click to expand...
Click to collapse
I would suggest the following thread, which has explicit step-by-step instruction on how to update firmware:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
"3.28.1540 firmware only" file is what you want.
Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done
No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.
You must relock your device first ... then try again with flash the ruu.zip
Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.
Hi all,
So I have my old M8 doing nothing (switched to Note 4)...
It's running a custom venom rom, and basically I want to put it completely back to factory state.
If you could help a guy that's moderately good at this stuff, I would be greatly appreciated.
Thanks!!
Post the output from fastboot getvar all and we'll tell you what to do
Thanks for that, err - I haven't got the tools installed any more, could you point in the direction of the tools again sorry!
Ok, getvar just sits at waiting for device...?
Ok sorry, turns out I'm just rusty!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Done, and thanks!
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Shozuki said:
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Click to expand...
Click to collapse
No other way, only sunshine.
But you don't need S-Off to revert to stock with that thread guide, you need to relock bootloader then follow all the steps.
The only thing is without S-Off, your bootloader will show RELOCKED instead of LOCKED.
Ah cool, minor.
Thanks
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
EddyOS said:
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
Click to expand...
Click to collapse
Indeed, but I'm literally giving it my uncle and let him use it.
If I may ask one more thing though, when sending the ruu.zip
I get:
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Any ideas??
Thanks for your help sirs.
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
EddyOS said:
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
Click to expand...
Click to collapse
Unfortunately it's still unlocked, but I can't seem to change that either. I'm using minimal adb and fastboot, but the htc_bootloader is in the folder.
Am I supposed to use that from the start, as I only see reference in the final stage.
Apologies, if I'm misreading!
EDIT, I followed the guide starting with recovery which kept failing... That must be the issue...
from your guide EDIT: Thread I meant:
"Well lord knows what's going on here...
I started by flashing the recovery to the one linked here. It won't boot into recovery at all it just sits at "entering recovery..."
I was using a venom custom rom and TWRP 2.8.5.0 touch recovery.
I can boot into the phone, use fastboot and adb - but can't go any further in restoring the handset back to factory... All help appreciated."
ckpv5 said:
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Click to expand...
Click to collapse
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
Yeah, That guide is for EU M8's only...
really struggling getting mine back to factory...
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
That depends. Are you s-off? If so, you can run a WWE RUU, and go back to basically stock. WWE is compatible with Rogers. You won't get OTAs though. You'll have to update firmware manually, but with s-off, that's easy to do.
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Shozuki said:
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Click to expand...
Click to collapse
What was it?
EddyOS said:
What was it?
Click to expand...
Click to collapse
Well basically I was following the instructions as if I were S-Off.
Instead I just to use: fastboot oem lock and completely skimmed over the text failing to read it!
My uncle is happy now and thats fine with me!
Thanks for your help!
I have Htc one m8 unlocked bootloader 3.19, was rooted but doesn't seem to be anymore. firmware is 4.16.401.10, supercid (was roger001). I'm not sure what I am doing wrong, I tried to flash a RUU after flashing the firmware first and i get an error 32-header error. Phone just reboots onto white HTC screen then gives me the red exclamation mark. Booting into recovery gives red exclamation mark. Not sure what else I can try, any suggestioins would be greatly appreciated. (note: tried to flash the RUU here I could be way off but I am stuck.)
Anyone have any assistance? I tried changed the mid so I could flash a RUU but still got the 32-header error. There has to be a simpler way to do this, I just want to get back to stock.
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong. I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work. I'll post that info in one sec
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
Are you s-on or s-off? Do adb getvar all and post the output (delete your IMEI and serial number, as these are personal data).
With the Rogers variant, you can't flash the Euro RUU unless you change the MID (s-off required).
Also, you need to relock the bootloader to run the RUU if you are s-on. But that doesn't matter as the RUU will fail MID check, anyway.
What exactly are you trying to accomplish by running the RUU?
Click to expand...
Click to collapse
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Kevinj17 said:
Thanks, I am on S-off. I thought that if you are s-off you didn't need to change mid but clearly i am wrong.
Click to expand...
Click to collapse
Yes, that is incorrect. CID and MID need to match what the RUU is looking for. SuperCID will pass the CID check. But the MID check will still fail if you try to run the Euro RUU (MID = 06PB10000) on a Rogers version M8 (MID = 06PB16000).
Also, are you actually using the phone on Rogers' network? If so, I do not think that returning to stock Euro WWE version by RUU is what you want. From this webpage, it looks like Rogers uses Bands 4,7, and 17 for LTE. The Euro RUU will install a full stock image, including radio firmware, and according to these specs, the Euro version (EMEA) is missing 2 of the 3 bands (Bands 4 and 17) needed for LTE to work on Rogers network.
Kevinj17 said:
I am just trying to restore to stock, I screwed up the phone trying to flash a zip and my recovery didn't work.
Click to expand...
Click to collapse
What zip did you try to flash exactly?
---------- Post added at 09:41 AM ---------- Previous post was at 09:23 AM ----------
Kevinj17 said:
Would flashing a recovery .img , for example >recovery_4.16.401.10.img< allow me to return to stock??
Click to expand...
Click to collapse
That would just be the actual stock recovery program that installs of OTA updates, etc.
Its not the actual stock OS or firmware, if that is what you are thinking.
The red exclamation indicates you are already on a stock recovery. Flashing this won't help you at all.
Yeah haha I figured that out right after posting. Thanks though. I re-flashed TWRP now and gonna try restoring from a nandrod backup i found then flash the matching firmware. see how that goes. The similiar names is what throws me off sometimes, so many different recoverys n sh*t lol
I was tryign to use a sixaxis controller to play games but kept getting and error about 'position executable variables' when loading the sixaxis app so i downloaded something called 'bypass pie' and flashed it. Clearly i should have backed up first. It was just inpatient, but it unrooted my phone and stuff so i tried to restore from a backuop like 2 weeks ago and it was corrupt so it messed things up