Related
As you can see in the picture the phone boots up to this screen. A friend of mine bought an HTC One on ebay and he found out it was rooted/unlocked so he went to put it back to stock and may have bricked the device while doing so.
EDIT: so I am able to use fastboot, but not adb because I can't get into Windows. Flashing the stock Verizon RUU I found still doesn't get me anywhere though.
Is there any hope for this device? Thanks in advance!
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
cmlusco said:
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
Click to expand...
Click to collapse
Yea I saw that after messing around with it some more. It is Windows 7 x64.
I tried the one at the bottom of the page as I can't find one anywhere else. I also used the commands at the bottom to try and flash it.
http://www.htc1guru.com/downloads/ruu-zip-downloads/
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
cmlusco said:
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
Click to expand...
Click to collapse
OK cool I will try that once it downloads. It shows "My HTC" in the device manager. Also with the fastboot devices command it does give me the device ID.
EDIT: That worked! Thanks a lot for the RUU file, as I could not find that anywhere.
Hello. A friend of mine has the same problem. She tried to flash this RUU: "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted" but the phone doesn't boot. Here is more info about the problem: http://forum.xda-developers.com/showthread.php?t=2688936
Can she flash the RUU posted here?
This is what the hboot says:
Unlocked
m7_wlv pvt ship s-off rh
cid-11111111
hboot 1.54.0000
radio 1.12.42.0906
opendsp v31.120.274.0617
os 1.10.605.10
Thank you very much.
She can, but since she is s-off, its better to flash the decrypted one. http://vzw1files.dyndns.org/RUUs/2.10.605.1/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
cmlusco said:
She can, but since she is s-off, its better to flash the decrypted one.
Click to expand...
Click to collapse
First, thank you very much. She changed the CID to VZW__001. That's not a problem, right?
Does the CID and MID have to be compatible with the RUU? She has this MID: PN0731000.
Downloading this RUU, will report back.
Again, thank you.
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
cmlusco said:
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
Click to expand...
Click to collapse
Hello again. Before we try to flash the RUU, I would like to ask you the steps to do it. This is what we gonna do:
1. Download RUU
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
And that's it? Nothing else is needed, right?
EDIT: we flashed the RUU. Now the phone boots always in fastboot. No matter what option we choose, the phone does nothing and goes back to fastboot. On the bottom of hboot there is a new line in red: "Active cmdline overflow! (1073 Bytes)"
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
cmlusco said:
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
Click to expand...
Click to collapse
Hello. We just did it, and still the same problem. We were reading that some people solved this by doing a downgrade to hboot 1.44. But I don't want to make this problem worse.
You can try it, its worth a shot. Just flash an older ruu. http://vzw1files.dyndns.org/RUUs/. Dont remember which one goes with 1.44
cmlusco said:
You can try it, its worth a shot. Just flash an older ruu. Dont remember which one goes with 1.44
Click to expand...
Click to collapse
You can't be more kind. We made a downgrade, and now we can use CWM again. (We did the downgrade before reading your post, so we didn't use an older RUU) Now thinking hwat should be the next step: flashing a ROM (custom or stock, mounting a pendrive) or flashing an older RUU or anything else. Again, dude, you're awesome.
I'm stuck in a similar situation and any help would be appreciated so I don't screw this up. I can get into the bootloader but not into recovery (gets to the first TWRP screen then reboots). Safe mode works fine too.
Win7 64bit
S-off
Rooted
Stock ROM
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW-001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OS-1.10.605.8
I can get into ADB. Would just like to know if I need to flash a new RUU or should I flash updated TWRP first? And the proper commands so I don't botch this.
Any help would be greatly appreciated.
Thanks
I would try reflashing twrp first. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
fastboot erase cache
fastboot flash recovery recovery.img
cmlusco said:
I would try reflashing twrp first.
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Didn't work. Got to the TWRP splash screen and back into the bootloop again.
Ok then i would do an ruu. http://vzw1files.dyndns.org/RUUs/
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip (may fail with flush error, just do the cmd again)
fastboot reboot
Hi,
Similar problem here.
This is my situation:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
CID: VZW__001
MID: PN0731000
Only fastboot. Can't access to recovey (CWM). Can't access to OS, so no adb.
Every time I try to RUU it gives the "Signature verify fail" message.
So, I tried encrypted ROMs (those at vzw1files. dyndns. org), and I could go a step forward; but the flashing hungs up after giving this messages:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
Thanks in advance, I hope I didn't screw it up.
The problem is nicouy that you are s-on, and on the newest kk firmware. An s-on phone will not allow you to "downgrade" firmware, and we do not yet have the latest ruu available, at least to my knowledge. So your kind of screwed right now untill we get our hands on a kk ruu.
Hey guys!
I really hope anyone can help me out with this.
So, today I thought "Why not upgrading to 5.1 and unbranding it?". I followed a tutorial on a german android forum to unbrand it.
But I was unlocked and rooted so I had to return the changes in order to update it. I changed the CID to HTC__102, made it S-ON again and even locked it, then tried flashing a non branded european RUU via my microSD card, which somehow failed and I ended up having a bootloop. So I upgraded my firmware aswell to 2.10.401.1 but now the recovery is not even working i only get a red triangle, which might be a common problem with 5.1 on our M9, as I read later on.
Download mode, fastboot etc is working fine
edit: stock recovery is working as well
Can anybody help me get my M9 going again?
I thought about try another flash with a unlocked ROM via microSD card but I'm not sure which one as the one I mentioned failed.
Here are some more details about my current situation:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXX
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__102
Click to expand...
Click to collapse
edit: In another thread I read how to boot into the stock recovery and it's working. But still not booting
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
LLegion said:
easy...soff again unlock bootloader, then download dev 2.8 zip rom, place it on sdcard and enter download mode, press volume up to start flash and you will have a brand new developer edition 2.8 (you will loose all info) you must have mid 0JPA11000 cid BS_US001., read a topic on this on xda how to change att to developer...
Click to expand...
Click to collapse
Thanks, but how do i set it to S-Off again? I've used Sunshine's S-Off app before. But I'm not able to boot anymore.
At first never post your IMEI number online.
If you are not S-OFFed any more you cannot flash anything to recovery partition as long as you are not at least htc_dev unlocked.
The only thing that could help you now is to flash a custom recovery in boot partition and then to try to fix the recovery partition from it.
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
then you should reboot in download mode again
Code:
fastboot oem rebootRUU
and flash the boot partition with a custom recovery
Code:
fastboot flash boot recovery.img
Now logically you should be able to boot into recovery (probably from bootloader) or by using the command
Code:
fastboot reboot recovery
If for some reason you cannot flash a custom recovery on boot partition you could try to extract the system.img from (probably any German RUU [HTC-GER] as long as you have HTC__102 cid number) and flash it with fastboot command
Code:
fastboot flash system system.img
By this way you could probably fix your breaked system partition
You should also erase the /cache and /data partitions so you could avoid the bootloop (even without to flash an original system.img)
Gatosbil said:
At first never post your IMEI number online.
Click to expand...
Click to collapse
Thanks. I've corrected it.
Gatosbil said:
In order to do this you should unlock your bootloader again by using Unlock_code.bin
Code:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I can't generate a new one because OEM unlock is turned off :\
Same goes with reflashing the previous Unlock_code.bin
> htc_fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY
Execution time is 20(ms)
Click to expand...
Click to collapse
Gatosbil said:
or if it has "relocked" status you could possibly use the command
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Indeed, it is "relocked". But when I'm using the command I'll get "[ERR] Command error !!!"
Any suggestions for that? I'll try the other steps once I solved this.
Edit: I can't use ADB because I'm using the stock recovery atm.
Also there is no RUU for 2.10.401.1 yet so I guess I have to sent it in?
Btw: I'm already hating the new 5.1 oem lock feature.
This was your mistake:
Army92 said:
made it S-ON again
Click to expand...
Click to collapse
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
iElvis said:
This was your mistake:
I don't care what anyone tells you, don't ever, ever go back to s-on once you are s-off. It's totally unnecessary and a potential risk, as you've discovered. By doing it, you've locked your phone into a bad configuration. You can't unlock unless you can boot to the OS and check "allow OEM unlocking." You can't flash a recovery because you're locked. You can't run a RUU because none exists for your CID. You're going to have to return it and hope HTC will fix it.
Click to expand...
Click to collapse
That's what I thought. Thanks, I'll contact HTC and see if they can fix it.
Edit: I'm sending it to HTC today. Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Army92 said:
Just a warning to all users out there: Do not lock your bootloader and uncheck "Enable OEM unlocking" because you are not able to do anything about it when your devices isn't working properly!
Click to expand...
Click to collapse
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
iElvis said:
If it's any consolation, you're far from the first person to get tripped up by this new feature. Lots of Nexus 6s got bricked when it first rolled out because of situations just like yours.
Click to expand...
Click to collapse
Yeah I've read that too. Thanks for your condolence. Will report again when I get my M9 back in 2 weeks (I hope).
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Army92 said:
Update: So today I got my lovely One M9 back it lasted 10 days until I got it back in my hands.
They changed the mainboard and haven't charged anything. My phone status went back to official, S-Off and locked bootloader.
Click to expand...
Click to collapse
They sent you an s-off phone?
iElvis said:
They sent you an s-off phone?
Click to expand...
Click to collapse
Oh, sorry my bad. I meant S-On of course
soft breaked htc one m9 s-off please help
hy
rom: cm13 himaul
device:htc one m9 unlocked/developer edition
statue:s-off
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) version-main: 1.32.617.30
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BS_US001
ok i have rooted cm13 20160603 nighties by supersu 2.74 beta with xposed 85 arm 64
yesterday i was disabling my boot image when it restarted by itself and never boot in to system again so i went to my custom recovery twrp latest version to reflash the whole cm13 again it didnt work then i wiped the whole internal storage and reflashed the cm13 and it said fail cant flash cm thats when my battery died so i charged it after 3 hours i came back went to bootloader menu then clicked on custom recovery it didnt even start so i plugged it to usb used fastboot to flash custom frimware from here (used the no wipe zip)
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
it flashed but custom frimware didnt fix it so i used the wipe zip version with viper one latest system image to flash it failed so now i am stock in bootloader (download mode works) without access of recovery and no system.img or recovery and i cant find a way to fix it
websites i visited just in case
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
any help would be appreciated
:crying::crying::crying:
Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following:
Code:
error 131: customer id error
The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran:
Code:
fastboot oem lock
This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with:
Code:
fastboot flash unlocktoken Unlock_code.bin
but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
Code:
FAILED (status read failed (Unknown error))
FAILED (data transfer failure (Too many links))
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Code:
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.81.5
Sep 30 2015,12:34:35(573756)
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 358509062058233
(bootloader) version-main: 2.9.841.5
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: TELST001
Thank you anyone who can lend a hand
- Alex
ABorrello said:
Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following: The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran: This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with: but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Thank you anyone who can lend a hand
- Alex
Click to expand...
Click to collapse
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Tried getting a new unlock token
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ok, I just gave that a shot with out any luck. I was sent a new Unlock_code.bin, but I diff'd the two files and found they were the same. After I ran the command to flash unlocktoken, the screen popped up for me to say 'Yes' or 'No' to unlocking the bootloader. I clicked yes, but then after the restart, my phone booted back into the bootloader saying that it was still in the ***RELOCKED*** state.
Finally was able to unlock the bootloader
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Finally I have managed to unlock the bootloader. For some reason, when the phone booted, the bootloader was not "official"?? The software status was modified. To fix it, from the bootloader, I rebooted into download mode; from download mode I booted back into the bootloader (now official); and then rebooted back into download mode. From there, I flashed unlocktoken with Unlock_code.bin and this time after I went through the prompts, the bootloader was unlocked and my phone booted into twrp. I tried to boot into cyanogenmod again, but it is in a boot loop (assumed because the system partition was wiped). I will now look to put stock HTC Sense, download the OTA update, and then upgrade to the newest build of cyanogenmod.
Hey guys,
I trying to help out with a friend’s HTC M9, which suddenly wouldn’t boot into Android. We can still access the bootloader and download mode.
The bootloader shows:
Software status: Modified
Locked
S-ON
Security Warning
I got it into download mode and tried fastboot getvar all, the relevant output is:
product: htc_himauhl
version 1.0
version-main: 3.35.206.13
mid: 0PJA10000
cid: o2___102
I had a look in the readme thread. My friend wanted to try to save the files but it seems impossible since we can’t get adb to work and can’t boot a recovery image, since that would require unlocking the bootloader which wipes the data anyways. Is that correct?
So afterwards, we tried to re-flash the official RUU. The phone is the o2 version, and the most recent RUU I could find was
Code:
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_O2_UK_3.35.206.13_Radio_01.01_U11440792_93.00.51117G_F_release_464855_signed.zip
I tried flashing the file using htc_fastboot flash zip, which failed with error 12 and some output on the phone complaining about the locked bootloader, as well as ARUWizard which resulted in the same error. Sorry I don’t have a screenshot, since I had to try it remotely.
Am I correct in thinking, that the file I downloaded should be usable to reflash the original software? It’s signed and has the same version code and was downloaded correctly with the same hash.
Not quite sure what happened there, since I don’t physically have the device. Should we try the SD-card method next?
Thanks!
at RUU Section just do sdcard method
here the link:
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
thanks to me and to them
Hello ..
i have htc one m8 and for some reason it's on deep freeze like on a same system restore point everytime i reboot i find the same
apps installed , pics and missed calls no matter how many times i erase all that and if i installed new apps every reboot it's
not there , and everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up +
power to reboot) ,tried to unlock bootloader using htc dev did all steps and when finally get to unlock bootloader screen on my
phone , i clicked yes and phone rebooted to black screen with red triangle and when i rebooted it's like nothing has been done
and still locked, i tried using official twrp from play store i managed for 1 time to open recovery mode and i wiped all data ,
erased the cache and when i rebooted it's the same issue .. tried to flash recovery using cmd still doesn't work (failed : remote
not allowed) , and also HTC sync manager doesn't recognize the phone , dk what to do , wasted alotta time trying to solve this
but no vain , plz help
*FastBoot*
*** Locked ***
M8_WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.18.0.0000
RADIO-1.08.20.0612_4
OpenDSP-v38.2.2-00542-M874.0311
OS-3.30.651.2
eMMC-boot 2048
Jul 7 2014,20:03:18.3
*getvar all*
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.08.20.0612_4
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: **************
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d4c3cae5
hbootpreupdate: 11
gencheckpt: 0
Try to flash stock ruu, if isn't working it's probably a dead nand.
Devil_55 said:
Hello ..
everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up + power to reboot)
Click to expand...
Click to collapse
Black screen with red triangle is the stock recovery. So that is expected. Hold vol up, and press and release power button, to show the stock recovery menu options.
Devil_55 said:
tried to flash recovery using cmd still doesn't work (failed : remote not allowed)
Click to expand...
Click to collapse
That message is expected when trying to flash custom recovery with a locked bootloader. TWRP is only going to flash if the bootloader is unlocked.
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173
You can try any of the RUUs there. But note that if you try the Marshmallow RUU, you will have to flash corresponding Marshmallow firmware.zip before the RUU will install properly (this is clearly indicated in red caps text on the linked thread).
I also agree with the previous response. The behavior is really suspicious (changes don't "stick", bootloader does not unlocked) and NAND failure is a real possibility, especially if the problems persist after RUU.
lucyr03 said:
Try to flash stock ruu, if isn't working it's probably a dead nand.
Click to expand...
Click to collapse
Thanks for your Help
redpoint73 said:
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571.
Click to expand...
Click to collapse
I tried this method but still locked
redpoint73 said:
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173.
Click to expand...
Click to collapse
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000) , i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible) (i'm just guessing i dk if we could use this information)
and Huge thanks to you
Devil_55 said:
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000)
Click to expand...
Click to collapse
Both HK and non-HK versions have the same model number 0P6B70000. The only different is in software/firmware.
Your OS number in getvar (3.30.651.2) leads me to believe it was originally non-HK (the "651" signifies this). But it's possible that the previous seller changed it from HK to non-HK (although I'd say that is unlikely).
Really since you are SuperCID, either RUUs will work (HK or non-HK). You can try 3.30.651.2, or the one you downloaded 4.25.651.14 is fine as well.
Devil_55 said:
i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
Click to expand...
Click to collapse
The .exe format RUU is probably the simplest method. PC is required.
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?
Devil_55 said:
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible)
Click to expand...
Click to collapse
No, that isn't possible. The Sprint version M8 is different from all other versions. Trying to flash Sprint version firmware/RUU to any other M8 version results in a radio brick (no SIM, no cell service).
We see on this forum a lot of folks with the Sprint version M8 which have been made s-off and SuperCID (by seller/vendor) to unlock them for use in other countries, and to appear "unbranded" (when they are in fact, far from it).
your Help is much appriciated
redpoint73 said:
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?).
Click to expand...
Click to collapse
It did nothing bcuz phone was on bootloader menu but when i tried RUU while phone was booted , wizard moved on to the next step ,
wizard tried to flash RUU but it's stuck on waiting for bootloader , and instead of the phone boot into bootloader it just reboot into the same restore point as if nothing happened.
-https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B%21340&parId=root&o=OneUp
- it kinda does that in every process before last step (rebooot) , I tried
1-Flash Firmware via Hboot (requires micro sd card)....
-rename firmware to 0P6BIMG.zip
-copy 0P6BIMG.zip to ext_sd card
-boot into bootloader
-make sure hboot is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
*reboot after pressing up
2- Flash Firmware via fastboot, no ext sd card needed....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
* Reboot regularly after fastboot oem rebootRUU
3- ARUwizard to flash 3.30.651.2 stuck at same point (waiting for bootloader) then phone reboot regularly
Is there any other way to flash