Develop Bugs

[Q] Possibly stupid NANDROID question...

Okay, so I'm a Samsung Note 3 owner that's helping out a guy to unscrew his AT&T M8. We're trying to return to nandroid stock using this guide http://forum.xda-developers.com/show....php?t=2701376, and I'm at the step where it says to flash the nandroid .zip file in TWRP. This is all fine and dandy, but even though it's located in the TWRP/backups folder, and apparently it's the correct nandroid version, it FAILS immediately. Maybe I got the wrong version??? I've googled around, but I can't seem to get the right info on this one!
Any and all help would be appreciated!!!:good:

Read that thread thoroughly ...
You don't flash the nandroid.zip
You extract the nandroid.zip and transfer the content to TWRP backup folder.
Anyway ... browse thru AT&T forum, you should be able to find the correct RUU
http://forum.xda-developers.com/att-htc-one-m8/general

No RUU will flash!!!! No main version shown in RUU utility...
ckpv5 said:
Read that thread thoroughly ...
You don't flash the nandroid.zip
You extract the nandroid.zip and transfer the content to TWRP backup folder.
Anyway ... browse thru AT&T forum, you should be able to find the correct RUU
http://forum.xda-developers.com/att-htc-one-m8/general
Click to expand...
Click to collapse
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead???
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0

[Q] Can ANYBODY help me!?! No ROM showing installed....

I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0

........

jreed3786 said:
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.

xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?

jreed3786 said:
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?
Click to expand...
Click to collapse
It didn't work? That's weird. Does it show "unlocked" in your bootloader?
And yes it is the correct CID. I wondered why you asked, then saw saw your signature. I knew AT&T because of you being in the US and your CID.

Never mind. I figured it out on my own.
xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!

jreed3786 said:
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!
Click to expand...
Click to collapse
That's funny, I'm glad I chose to leave Samsung products.

RUU - Signature Verify Fail

I'm trying to restore my S-ON One M8 to stock using RUU. I relocked my bootloader .
My Device Details:
cid: HTC__J15 (Region : Arabic). version-main: 3.28.401.7.
So I flashed a few RUU zip files (using fastboot) from htc dev website with versions higher than mine.
But I keep receiving signature verify fail.
I would very much appreciate if someone could point me to the correct RUU.

Larzee said:
I'm trying to restore my S-ON One M8 to stock using RUU. I relocked my bootloader .
My Device Details:
cid: HTC__J15 (Region : Arabic). version-main: 3.28.401.7.
So I flashed a few RUU zip files (using fastboot) from htc dev website with versions higher than mine.
But I keep receiving signature verify fail.
I would very much appreciate if someone could point me to the correct RUU.
Click to expand...
Click to collapse
If you got it from HTC Dev, it's not an RUU, it's kernel source.
You can get the proper RUU.exe file here :
https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
You can get the RUU.zip file, if you would prefer that, from here :
https://docs.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/edit?pli=1

xunholyx said:
If you got it from HTC Dev, it's not an RUU, it's kernel source.
You can get the proper RUU.exe file here :
You can get the RUU.zip file, if you would prefer that, from here :
Click to expand...
Click to collapse
Tried flashing those. Still getting signature fail error.
This is what i get when i type fastboot getvar all.
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.21331147A1.19_2G
version-cpld: None
version-microp: None
version-main: 3.28.401.7
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__J15
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0
Which RUU would work for me??
Thanks in advance.

[Q] Which RUU for my Device?

This is what I get when I type fastboot getvar all
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.21331147A1.19_2G
version-cpld: None
version-microp: None
version-main: 3.28.401.7
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__J15
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0
Can someone link me to right RUU?
Thank you

Larzee said:
This is what I get when I type fastboot getvar all
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.21.21331147A1.19_2G
version-cpld: None
version-microp: None
version-main: 3.28.401.7
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__J15
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: df77f8b7
hbootpreupdate: 11
gencheckpt: 0
Can someone link me to right RUU?
Thank you
Click to expand...
Click to collapse
Go to here and look for the RUU that is 3.28.401.7

Where are the full ruu's ? These are updates, kernel sources and binaries ? Or am i wrong here
Maybe the OP has more success in flashing the latest 401 ruu from here
http://forum.xda-developers.com/showthread.php?t=2911563

Mr Hofs said:
Where are the full ruu's ? These are updates, kernel sources and binaries ? Or am i wrong here
Maybe the OP has more success in flashing the latest 401 ruu from here
Click to expand...
Click to collapse
Tried flashing the latest 401 ruu. Getting signature verification fail.
But I was able to flash the 3.28.401.7 firmware from this link
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/ .

Larzee said:
Tried flashing the latest 401 ruu. Getting signature verification fail.
But I was able to flash the 3.28.401.7 firmware from this link
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/ .
Click to expand...
Click to collapse
Just flash the latest Lollipop RUU for your phone: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
Edit, sorry I just noticed someone else suggested that too, however, if your getting problems flashing it, if you are s-on you will need to re-lock your bootloader first, and you may also need to use the htc_fastboot.exe to flash it rather than standard fastboot: https://www.androidfilehost.com/?fid=95916177934550031

Seanie280672 said:
Just flash the latest Lollipop RUU for your phone: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
Edit, sorry I just noticed someone else suggested that too, however, if your getting problems flashing it, if you are s-on you will need to re-lock your bootloader first, and you may also need to use the htc_fastboot.exe to flash it rather than standard fastboot: https://www.androidfilehost.com/?fid=95916177934550031
Click to expand...
Click to collapse
Used the htc_fastboot and it worked like a charm
Thanks for all the support.

M8 starting up in Fastboot, won't load installed ROM

I've stuffed something up along the way and now my M8 seems to refuse to load any ROM I've installed on it. What's the best way to go about fixing this? It's unlocked with S-Off.

Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers

Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?

shirreer said:
Flashing an RUU is a silver bullet for starting over, as an RUU formats all your device's partitions and flashes them with stock images.
You'll need to provide CID & MID or your current firmware version (i.e. 4.16.401.10) if you need help locating a compatible RUU.
Cheers
Click to expand...
Click to collapse
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
redpoint73 said:
Need some more details to see why the phone won't boot into OS after flashing a ROM.
Is an OS number indicated on the bootloader screen? If so, what is it?
What version TWRP?
What ROMs have you tried?
Click to expand...
Click to collapse
My OS number is 4.16.1540.8, I've tried TWRP 2.7.0.1, 2.8.7.0 and 3.0.0.0, roms I've tried include CM13, SkyDragon and a stock TWRP backup I found in another thread here.

roseyhead said:
I've tried flashing a few different RUUs and they all come out with an error 155. Googling it suggests I need to relock my bootloader but locking it and running the RUU again gives me the same error. I'm using SuperCID 11111111 and my MID is 0P6B70000. Currently on firmware 4.16.1540.8.
Click to expand...
Click to collapse
Your MID and firmware number don't jive; and it can indicate something pretty dangerous (and possibly a radio bricked phone).
Need more info on what you've done.
Do fastboot getvar all, and post the output (delete serial number and IMEI before posting).
Was the phone new and stock (unmodified) when you got it; or did it have a previous owner?
Please list all the mods you have applied (s-off, changed CID, changed MID? etc.).

Ok, here's what getvar all reports:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -snip-
(bootloader) imei: -snip-
(bootloader) imei2: Not Support
(bootloader) meid: 99000499014851
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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
all: Done!
finished. total time: 0.035s
I bought the phone second-hand, it was running a custom ROM (SkyDragon) with cid already set to 11111111 and I wanted to return it to stock. I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
I've also tried restoring assorted TWRP backups, installing new roms and so on, directly flashing boot.img, things seem to flash ok but the phone just boots direct into fastboot.

Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!

roseyhead said:
Update: I'm not sure what went differently this time but I've installed the latest Cyanogenmod nightly and it's starting up as expected.
I'd like to get back to stock though. What's the best way to go about doing this? The phone was already modified when I got it so I'm not sure what it would've had on it when it was purchased originally.
Edit: A bit of googling suggests this is a Sprint handset (I dismissed this to begin with since I'm in Australia and didn't think it'd be an overseas handset, but ok) so I've flashed 6.20.651.3 firmware and am waiting for a matching RUU to download. Fingers crossed!
Edit again: All sorted now, thanks for your help!
Click to expand...
Click to collapse
I'm glad you're all set. But for other users' benefit, here is a link to HTC's official Sprint RUU page, with instructions for flashing the RUU as well as a download link for Sprint M8 marshmallow RUU 6.20.651.3
Sprint RUU instructions page:
http://www.htc.com/us/support/htc-one-m8-sprint/news/
Sprint M8 marshmallow RUU 6.20.651.3 Direct Link:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
Cheers

i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.16.654.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 99000499165808
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

roseyhead said:
I got the Unlocked/Developer RUU from HTC's site but that didn't start up for me so I tried a bunch of stuff, fiddling with firmwares and unlocking/relocking bootloader and so on but in the end the RUU just hadn't downloaded properly. Once I managed to get the RUUs to run they've all come up with error 155 when they start the flash and flashing the rom.zip direct gives me an error (I forget if it's the same or different)
Click to expand...
Click to collapse
Happy to see your sorted it out.
I agree it appears to be the Sprint version, based on the the MID (0P6B70000) and product name (m8_whl). While the MID can be modified, the product name is typically not (never seen a mod method for that - so the product name is very reliable).
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
---------- Post added at 11:38 AM ---------- Previous post was at 11:30 AM ----------
mushfiq20 said:
i am having the same problem. i dont even know what carrier this phone was from. but the model number written on the back is OP6B110 M8x... and this is the result of getvar all..
(bootloader) version-main: 2.16.654.4
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
This is Sprint version, same as OP based on the model ID and product name. Although main version would indicate the Sprint Harmon Kardon version. RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
The M8x designation on the back cover can't be trusted in this case. The back cover has been replaced to remove the "Sprint" logo branding. We've seen several phones like this (back cover replaced to remove evidence of branding) on the forum. You have to go by the getvar data.
Also, be sure to remove your IMEI and serial number from the getvar output. These are personal data, and should never be posted online.

redpoint73 said:
That being said, I would strongly caution you moving forward, to not flash any firmware or RUU to this device except Sprint M8 firmware/RUU. Reason being, the partitioning on the Sprint phone is different from most other versions; and flashing another version's firmware can lead to a radio brick (phone boots, but nothing requiring the radio will work).
Click to expand...
Click to collapse
Thanks a lot for the tip! I'll bear that in mind going forward.

Hi there I seem to be having similar issues. I purchased a refurbished M8. The case indicates 0P6B110 M8x however fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [REDACTED]
(bootloader) imei: [REDACTED]
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237658
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Going off the info in the thread I downloaded RUU 6.20.651.3.
While verifying I want to update the ROM version it states:
From:
Image Version: 1.54.651.8
To:
Image Version: 6.20.651.3
After clicking next and progressing I get Error 155.
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.

metalbassist33 said:
On the fastboot recovery screen shows:
*** LOCKED ***
m8_whl pvt ship s-off
cid-111111111
hboot-3.16.0.0000
radio-1.09.20.0209
opendsp-v38.2.2-00542-m8974.0311
os-3.30.651.2
eMMC-boot 2048
loading zip info fail
RUU
Any help with this would be greatly appreciated.
Click to expand...
Click to collapse
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3

ckpv5 said:
To run a Marshmallow RUU, you need to fastboot flash its firmware.zip first.
1. flash 6.20.651.3 firmware.zip
2. run RUU
You should be able to find the firmware.zip in Sprint section
Or you try to find one version lower (lollipop) than 6.20.651.3 RUU, run it then do OTA to 6.20.651.3
Click to expand...
Click to collapse
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?

metalbassist33 said:
Just to confirm, if I get a lollipop version, do I still need to fastboot flash a firmware.zip?
Click to expand...
Click to collapse
No .. not needed, run Lollipop RUU then do OTA to Marshmallow