Develop Bugs

[Q] I can't flash CWM recovery on s-off HOX, advice?

I've been following the steps provided here and am stuck at step 8 where I am unable to flash a custom recovery (i.e. CWM) no matter what i do!
I've tried rebooting the computer; resetting the phone and trying another computer but no go. I have s-off and SuperCID (11111111).
I'd like to know what else i should try? What am I doing wrong? Is this a driver problem?
I had issues with flashing the firmware also (actually flashing anything in general), but i just changed my CID to 11111111 and so was finally able to update the hboot (currently 1.39) and software (currently 3.17.728.1)
The error message i get when trying to flash the recovery through fastboot is :
sending 'recovery' (5742KB)...
OKAY [ 0.759s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.970s
I haven't unlocked my bootloader before flashing recovery because i assumed with a s-off HOX you didn't need to?
Please i need some advice as the ROM I started with (ARHD) is wiped out!

Remote not allowed is an error that pops up indeed when the bootloader is locked, just unlock it via the HTC dev site and flash again.
And your assumption is right but it does not seem to work in your case.

Yeah. With S-OFF, you can probably set it back to **LOCKED** state when needed.
Sent from my One X

Of course It's that simple! :s
Mr Hofs said:
Remote not allowed is an error that pops up indeed when the bootloader is locked, just unlock it via the HTC dev site and flash again.
And your assumption is right but it does not seem to work in your case.
Click to expand...
Click to collapse
Ok I'll try that right now, cheers.

Thanks, but no touch on ARHD 18.1
Thanks for that, it all worked out But I had the same issue that some people have with the touch screen not working, at all!
So I've just flashed the very first nandroid backup listed here since my original CID was HTC_023 and am now running on a stock android 4.1.1 Sense ROM.
It seems to be a problem with HTC_023 devices. These two threads (1) (2) discuss this issue further if anyone is interested.
So far there seems to be no progress in getting a custom ROM working with touch according to them, i think?

Odp: [Q] I can't flash CWM recovery on s-off HOX, advice?
Jam0rama said:
Thanks for that, it all worked out But I had the same issue that some people have with the touch screen not working, at all!
So I've just flashed the very first nandroid backup listed here since my original CID was HTC_023 and am now running on a stock android 4.1.1 Sense ROM.
It seems to be a problem with HTC_023 devices. These two threads (1) (2) discuss this issue further if anyone is interested.
So far there seems to be no progress in getting a custom ROM working with touch according to them, i think?
Click to expand...
Click to collapse
You might want to check this topic
http://forum.xda-developers.com/showthread.php?t=2120714

[Q] unlock with HTCdev fails

I have done this with a previous INC2, however I get this error with a new phone I received 2 days ago:
r>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s
I have repeated the steps 3 times , generating an unlock file from HTC every time (double checking device , cut and paste erros , etc).
My goal is to root for superuser access not S-OFF the device
My versions of SW are:
FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722
1- Anyone has an idea of the HTCDev error solution?
2- If it is not possible to use HTCDev and I need to rS-OFF to get superuser privileges; what procedure should I follow based on my FW v4.08.605.3 and Hboot 0.98? (will taco root work with this Hboot?, links please)
thanks

vlsi99 said:
I have done this with a previous INC2, however I get this error with a new phone I received 2 days ago:
r>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s
I have repeated the steps 3 times , generating an unlock file from HTC every time (double checking device , cut and paste erros , etc).
My goal is to root for superuser access not S-OFF the device
My versions of SW are:
FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722
1- Anyone has an idea of the HTCDev error solution?
2- If it is not possible to use HTCDev and I need to rS-OFF to get superuser privileges; what procedure should I follow based on my FW v4.08.605.3 and Hboot 0.98? (will taco root work with this Hboot?, links please)
thanks
Click to expand...
Click to collapse
Wau 72 views and nobody can help?
Ok, I know there are many posts about S-OFF with FW v 6.....xxxx, use TACOroot or with V6.yyyy use this one. Can someone tell me if a simple downgrade will work with my FW version v4.08.605.3 and Hboot 0.98?
thank you

vlsi99 said:
Wau 72 views and nobody can help?
Ok, I know there are many posts about S-OFF with FW v 6.....xxxx, use TACOroot or with V6.yyyy use this one. Can someone tell me if a simple downgrade will work with my FW version v4.08.605.3 and Hboot 0.98?
thank you
Click to expand...
Click to collapse
did u updated to latest Hboot?
Send my E-960/S4 LTE/N2 GSM and /Galaxy Y to xda

Ryanrioz said:
did u updated to latest Hboot?
Send my E-960/S4 LTE/N2 GSM and /Galaxy Y to xda
Click to expand...
Click to collapse
The phone came with these
FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722
HctDev is not working as I posted previously.
I only wanted superuser rights (don't care for ROMs). Since HctDev root does not work , I want S-OFF (which will give me SU anyway),
The question is what procedure to follow since I see different posts where the FW version is important to do the right thing. So what link is the correct for the Hboot and FW versions that I have.
thank you

vlsi99 said:
The phone came with these
FW version is 4.08.605.3
Hboot 0.98
And 2.3.4
radio 01.0722
HctDev is not working as I posted previously.
I only wanted superuser rights (don't care for ROMs). Since HctDev root does not work , I want S-OFF (which will give me SU anyway),
The question is what procedure to follow since I see different posts where the FW version is important to do the right thing. So what link is the correct for the Hboot and FW versions that I have.
thank you
Click to expand...
Click to collapse
There are several posts about using HTC Dev unlock. I think I could get my 10yr old niece to use use search n figure it out.
You need to get the unlock .bin file from your email that u use to submit all your info n out that .bin file in the same file as adb resides in.
Sent from my ADR6350 using xda app-developers app

[quote
]there are several posts about using htc dev unlock. I think i could get my 10yr old niece to use use search n figure it out.
Click to expand...
Click to collapse
[/quote]
Please read the first post.
fordnate said:
you need to get the unlock .bin file from your email that u use to submit all your info n out that .bin file in the same file as adb resides in.
Sent from my adr6350 using xda app-developers app
Click to expand...
Click to collapse
Please read the first post.
I am sure your 10 year old nice can also read very well. The file is in the right place. Re-read the error message again if you really want to help.
r>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.165s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.169s
thanks

HTC 10 non-standard behavior

Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
Code:
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxx
(bootloader) current-slot:
(bootloader) imei: xxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
all:
finished. total time: 0.064s
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
Code:
target reported max download size of 1579200000 bytes
sending 'recovery' (20852 KB)...
OKAY [ 1.711s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.810s]
finished. total time: 3.528s
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message
Code:
33 RU_UPDATE_FIRMWARE_FAIL
33 RU_UPDATE_FIRMWARE_FAIL
FAIL33 RU_UPDATE_FIRMWARE_FAIL
as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.

madzur said:
Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.
Click to expand...
Click to collapse
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.

Captain_Throwback said:
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.
Click to expand...
Click to collapse
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?

madzur said:
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?
Click to expand...
Click to collapse
You sure you don't have a hardware problem? That's what it sounds like.

Captain_Throwback said:
You sure you don't have a hardware problem? That's what it sounds like.
Click to expand...
Click to collapse
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.

madzur said:
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.
Click to expand...
Click to collapse
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.

Captain_Throwback said:
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.
Click to expand...
Click to collapse
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks

madzur said:
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks
Click to expand...
Click to collapse
Nope, that only happens well, when you've modified the software by installing an unsigned image like a custom recovery or kernel or made modifications to system. So getting an RUU to flash is really the only way to restore it back to official status.

Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?

Same thing
madzur said:
Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?
Click to expand...
Click to collapse
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.

djgreyghost said:
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.
Click to expand...
Click to collapse
Pretty sure you saved my phone from extinction :good: I'm not sure I would of tried the S-On version.

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.

Dukenukemx said:
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.
Click to expand...
Click to collapse
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.

djgreyghost said:
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.
Click to expand...
Click to collapse
Guess I'll be installing LineageOS then. The phone works fine like this, but it bothers me that I can't flash it completely.

Ok the problem with [email protected] is that you installed an aftermarket screen and that causes the failure. The solution is to remove the tp_SYN3708.img file from the rom and then flash it, but I'm still working on how to do that. The tp_SYN3708.img file is specifically for flashing the screen and the screen I have is Chinese replica, so of course it doesn't work. So my options are to remove the file and flash that way or to get another LCD screen. I'd rather find a software solution as looking for an original HTC 10 screen is probably harder than it sounds.

My htc 10 is dead ?

Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!

ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.

yldlj said:
Boot to download mode, use Fastboot and type Fastboot getvar all
Post the output deleting your imei amd serial number.
Click to expand...
Click to collapse
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15

ubadafatta said:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: **********
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: *************
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__J15
Click to expand...
Click to collapse
Since there Is no RUU and you re locked your Bootloader there's not much I can help you with sorry.

ubadafatta said:
Hello guys
i have a htc 10 i rooted the phone , unlocked the boot-loader, flashed twrp ,installed a stuck rom , then i changed my mind and decided to back to stock , so i formatted the system , wiped every thing , re-locked the bootloader and forgot to install the stock recovery , now i have no recovery no twrp not even the stock , no system on my phone , s-on , my phone is dead now can any one help me out please ?!
Click to expand...
Click to collapse
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).

Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on

Rolo42 said:
You're in this predicament because you didn't follow directions. Henceforth, follow directions precisely and if you're unclear, then ask specific questions about those instructions.
IIRC, Nougat RUU won't flash with S-On but you can try it and then see if it takes the OTA to Oreo.
Can you unlock the bootloader? (I don't know if you can just flash the same file you originally used or if you have to get a new one after relocking.) If you can do that, you should be able to install TWRP and flash any of the custom ROMs (LeeDroid for a stock-based ROM).
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.011s]
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 [ 0.080s]
finished. total time: 1.094s
this what i get when i try to flash unlocktoken or oem unlock bootloader or even when i try get_token_identifier

You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
ubadafatta said:
Okay thanks , im gonna try this , but i dont think that i can flash ruu without stock recovery
and i also cant lock the bootloader cause it needs to enable (oem unlocking) from developer settings and i have no system to do that and i dont know how to do it from fastboot
i tried many times to flash twrp nut i dont think with relocked bootloader and s-on
Click to expand...
Click to collapse

Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.

Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The threory of the OTA is fine but not in this case.
Cheers.
Click to expand...
Click to collapse
Yeah thanks. I deleted all my post because there's no point in arguing. Your correct I totally forgot what the OP problem was after all this. Thanks for the clarification.

Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Mr Hofs said:
Just to enlighten you all, the OP says he formatted everything, all the partitions including the system. So there is no OS present on the phone.
In this case a RUU is much better because it also holds the full stock system. The OTA does not contain the full OS. So flashing the OTA on a phone without the OS present is not going to help. The phone will not boot.
All this info is because i had a good read in the OP post. The theory of the OTA is fine but not in this case.
So before you guys will wave your precious little genitals towards me i suggest to read more carefully and base your help on that
Cheers.
Click to expand...
Click to collapse

It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
ayyu3m said:
Hi Mr Hofs,
Thanks for the enlightenment.
In my case I had erased the OS also. Not only that. I had erased system. Last time I had access to TWRP it kept giving me unable to mount several partitions. After which I lost access to TWRP. The bootloader did not allow me to enter any recovery after that. It just kept rebooting to download mode. Much less I had no OS that would load. Luckily I did not relock bootloader and it was left unlocked. With my past experience with my several HTC devices I know for sure that a major OTA such as this OREO OTA has the ability to completely rewrite the whole system and restore the device to working. I have repeated the scenario and even posted pictures in the post above. You can clearly see the system image is being installed in one of the pictures. So with much respect I really disagree with the whole OTA is not gonna work in this case concept. Because for me I have proof of concept. ?
I stressed several times in this post that it has worked for me. That in my case I had access to download mode and that I used the sdcard method. Download detected the OTA renamed as 2PS6IMG.zip and my phone got fully restored HTC 10 to working condition.
As per my experience as mentioned above HTC phones like many other are designed to pickup "correct" types of installable and device matching zip files from sdcard no matter what the situation is and would try to restore the lost functionality to ensure a device can be used again.
I just hope OP gets his device recovered. Because the OTA link I have provided OP is the same I used. It contains OS and everything vital. Just the OP needs to try. Unless he has a mismatching CID I assume it will work for him too.
Thanks ?
Thanks to XDA community as well.
This would be my last post in this thread unless OP requests my intervention. Speaking of which I wonder where he is when so much has been said. Haha.
Click to expand...
Click to collapse

Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Mr Hofs said:
It's great it worked for you and i truly hope it helps the OP too. The other weird thing that notices me actually is that in fact the OTA is in this case the same as the RUU ? Why isn't there a 3.16.401 RUU ? I think there are some hiccups when the OTA is refferenced as a RUU (which feels like it is in this thread because it seems to contain the OS and firmware)
intriguing .........
Click to expand...
Click to collapse

ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I will have a look at it when i have more time, and let's not bash but learn ?
:highfive:
Cheers guys.

ayyu3m said:
Thanks Mr Hofs,
Now that was good reply to the predicament we were having here. Yes I would like to know too why this OTA had the same effects of an RUU. Please let me know if you get to know the findings.
And here I also publicly apologize wholeheartedly to @yldlj
Sorry mate. Just went a little overboard when what I should have said was it did work for me. I just hope it works for OP. Cos if it doesn't you guys are gonna have a bashing party ready for me. Hahaha
Click to expand...
Click to collapse
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:

Yeah i got your PM. Thanks for that. After reading your PM i also knew how stupid i was being. And when i came to delete the post, they were already deleted by the thread administrators.
Sorry once more man. Wont happen again
yldlj said:
I also apologise and I'm not sure if you got my pm apologising also. This is very strange that the OTA acts the same as ruu. I never knew that you had no os when you used the file. I think we got caught up in different things. I also believed that it's did work for you. Hopefully the OP can try it and get back to the thread. Cheers guys :good:
Click to expand...
Click to collapse

ayyu3m said:
You dont NEED RUU. OTA is enough!
Try this. Download this OTA which is for your device
https://androidfilehost.com/?fid=890129502657577036 > remember to refresh link as sometimes androidhostfile shows as not found or error
"OTA_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4-2.41.401.41_release_519849u8ji7j8e2tj4znyo.zip"
rename it to 2PS6IMG.zip
(make sure its not 2PS6IMG.zip.zip again. show extension in windows to make sure)
put into the root of your SDCARD (transfer via microSD card reader)
put SDCARD back into your phone
boot phone in download mode (volume down + power) let go of power but keep holding volume down for a while
once in download mode the 2PS6IMG.zip will get detected and you can proceed to install by pressing volume up.
YES IT DOESNT MATTER IF UR BOOTLOADER IS LOCKED AND S-ON or EVEN IF RECOVERY IS MESSED UP. As long as CID matches (i assume it will since yours is .401 variant as per your bootloader info "version-main: 3.16.401.2" which is unbranded cid / europe /mid.east/africa the link i gave should work)
i screwed up my htc 10 but it got rescued too because of this
Let me know how this went
Click to expand...
Click to collapse
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on

[email protected] said:
i ve tried this method but it gives me FAIL22 RU_HEADER_ERROR
i am running 3.16.401.2
no OS
bootloader is relocked and s-on
Click to expand...
Click to collapse
Flash ruu
https://androidfilehost.com/?fid=673956719939830809

yldlj said:
Flash ruu
https://androidfilehost.com/?fid=673956719939830809
Click to expand...
Click to collapse
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%

[email protected] said:
it started flashing but after some system.img installed, it gives me 8 RU_SIGNATURE_FAIL
I 've tried to reset everything from the recovery but it did nothing
and in the first queue of flash there is some of them bypass didn't give me 100%
Click to expand...
Click to collapse
Yeah everyone I flash RUU it does bypass some things. Relocking bootloader usually causes problems and I don't know people still keep doing it. I would say flash twrp followed by leedroid but pretty sure you need an unlocked bootloader to flash twrp. Sorry but I'm out of ideas.

M8 won't flash RUU

Hello everyone,
- i'm sry if i posted abt the same issue but i managed to gather more information abt the situation
- 1st of all 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, I wanted to get it back to stock as new but i couldn't and here what i have tried :-
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
-Phone couldn't boot into bootloader while on fastboot mode so it reboots regularly.
3-tried to flash RUU (3.30.651.2 & 4.25.651.14) wizard while phone was on
https://onedrive.live.com/?cid=AC7B...23EA2B!344&parId=AC7BFAC4E523EA2B!341&o=OneUp
-did the first steps ok but again when wizard is waiting for bootloader while phone was in fastboot mode, it just reboot regularly.
4-tried renaming another (4.25.651.14) RUU to 0P6BIMG.zip and put it on sd-card and went to Hboot.
https://onedrive.live.com/?cid=AC7B...23EA2B!342&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after clicking yes to confirm the update, Phone rebooted in the middle of the steps .
5-tried flashing same 0P6BIMG.zip from recovery mode.
https://onedrive.live.com/?cid=AC7B...23EA2B!347&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after 3 mins of hope crushed by verifying update package.... - Installation aborted....
6-tried flashing RUU.zip via fastboot
https://onedrive.live.com/?cid=AC7B...23EA2B!346&parId=AC7BFAC4E523EA2B!341&o=OneUp
-phone just reboots regularly when trying to reboot RUU .
7-I contacted HTC support and after givin 'em alot of images and getvar they told me that my phone was modified in two ways (s-off) &
(Recovery tool) , They are telling me that (i must install the android recovery tool once again before proceeding) !! and i need to search on this site (Xda) for the stock recovery, but i think i have the stock recovery tool, and i can't flash any recovery because bootloader is locked, So is there any other way to flash recovery.
-here is some photos and getvar
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!339&parId=root&o=OneUp
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!350&parId=root&o=OneUp
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

Devil_55 said:
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
Click to expand...
Click to collapse
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Devil_55 said:
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
Click to expand...
Click to collapse
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
All Sprint RUUs are available here: https://forum.xda-developers.com/showthread.php?t=2729173

Thanks for the fast reply
redpoint73 said:
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
-I already Tried that several times but not working still locked
redpoint73 said:
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
Click to expand...
Click to collapse
-Yea but How to return to full stock
redpoint73 said:
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Click to expand...
Click to collapse
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
redpoint73 said:
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
Click to expand...
Click to collapse
-I was flashing 3.30.651.2 RUU.exe while phone was on bootloader mode, The thing is if the phone is on bootloader mode and wizard is showing that it's (Waiting for bootloader...) ,then phone reboots regularly and nothing changed
-And if phone was just on with activated usb debugging and i opened RUU.exe, the first step is to get to bootloader mode and then will send all the data of the RUU, Then it will show it's (Waiting for bootloader....) again, But because the phone is already in bootloader mode, The phone will just reboot as i showed in step 3, so when wizard is trying to go bootloader mode while phone is on bootloader mode that's what make it doesn't work.
-This is another link of Step 2 (Flashing 3.30.651.2 RUU.exe) while on fastboot mode
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!351&parId=root&o=OneUp
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.

Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Devil_55 said:
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
Click to expand...
Click to collapse
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Devil_55 said:
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.
Click to expand...
Click to collapse
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------
Devil_55 said:
-I already Tried that several times but not working still locked
Click to expand...
Click to collapse
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?

redpoint73 said:
Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Click to expand...
Click to collapse
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
-I don't know if it has stock Rom installed on it, I just want to delete everything and start over with unmodified OS
redpoint73 said:
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Click to expand...
Click to collapse
-sry for the confusion, I just thought if i could flash stock one by myself i could get around this situation somehow and at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
redpoint73 said:
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
Click to expand...
Click to collapse
-Thanks for the clarification
redpoint73 said:
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?
Click to expand...
Click to collapse
-Nope, I followed the guide then after adb reboot bootloader, Still locked

Devil_55 said:
at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
Click to expand...
Click to collapse
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.

Thanks for your time and effort

Devil_55 said:
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
Click to expand...
Click to collapse
I've got the same issue, it's eMMC failure and you have to replace with the new one.
My topic: https://forum.xda-developers.com/htc-one-m8/help/help-wifi-off-t3762549

NoIP said:
I've got the same issue, it's eMMC failure and you have to replace with the new one.
Click to expand...
Click to collapse
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?

redpoint73 said:
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.
Click to expand...
Click to collapse
I just found out that on the back of the phone .. Model : 0P6B100 !!!

Devil_55 said:
I just found out that on the back of the phone .. Model : 0P6B100 !!!
Click to expand...
Click to collapse
You can't trust what is on the back cover. We've often seen these swapped to remove US carrier logos. All indications on your getvar point to the "internals" of the phone (which is the important factor - and what you need to go by) being the Sprint version M8. It's very common to see the Sprint version to have its back cover replaced in order to remove the Sprint logo and sell it as an "unbranded" version (which it really is not).
---------- Post added at 09:03 AM ---------- Previous post was at 08:54 AM ----------
Devil_55 said:
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?
Click to expand...
Click to collapse
I'm not really a "hardware" guy. I can never seem to perform any hardware-related repairs on small electronics; despite being an engineer (very technically-minded) and all-around very careful about doing things (too obsessive about the minutia, in fact). But I have to say, changing emmc seems really delicate, and will not turn out well unless you are already experienced with this type of thing, and good at it. As far as I can tell, it involves heating up the chip, then installing the new one and "reflowing" the solder points. All of which looks really tricky, with a bunch of things that can go wrong along the way.
Might be better to have a repair shop do it, or change the whole motherboard, if you really want to go through the effort of hardware repairs to get this phone working again.
If you do change the emmc (or have a shop do it) I would only recommend using one intended for the Sprint M8. If you look at the thread NoIP linked, you will see I'm trying to help him with a weird emmc-motherboard combo, which I am not sure is fixable.

Thanks mate for explaining that