[Q] 1.57 - back to stock - tried everything - One (M7) Q&A, Help & Troubleshooting

Hello,
Since it's my first post on the forum let me introduce myself. My name is Marc, I live in the Netherlands and I'm a Java/C software engineer.
I'm trying to flash my phone to stock, since I need a repair. The problem is, however, with my previous repair they changed my phone to HBOOT 1.57. Since then I have a ton of problems. I'm trying to put my phone to stock for about 3 weeks now, but with no success... Everything I have tried. RUU flash, RUU zip-flash, multiple roms, Firewater, Revone everything. But without success.
Can someone please help me! For now, my phone is bricked at RevolutionHD Google Edition in an endless loop. I can (if I'm fast) change language, and than: reboot.
Help will be usefull, an I'll donate to the answer wich help me. Thank you.
Phone details:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SECRET
(bootloader) imei: SECRET
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

CupOfThee said:
Hello,
Since it's my first post on the forum let me introduce myself. My name is Marc, I live in the Netherlands and I'm a Java/C software engineer.
Click to expand...
Click to collapse
Hello Marc, welcome the xda
Everything I have tried. RUU flash, RUU zip-flash
Click to expand...
Click to collapse
Your phone is S-ON, Hboot 1.57 and CID/MID confirm you are on a 6.xx.401.x firmware version (erased version-main because of TWRP recovery). So any ruu you'll find will not work on your phone. When S-ON you can only flash RUU that are same version or newer than your firmware version. The latest RUU for your CID is 4.19.401.9. so it can't be used on a s-on phone (or any other ruu version below this one). So you must S-OFF your phone for 2 things.
To be able to flash and RUU to reset your firmware and software to 100% stock
To remove the Tampered flag from the bootloader and also to set it back to *LOCKED* (not RE-LOCKED) so you warranty is valid.
Firewater, Revone everything. But without success.
Click to expand...
Click to collapse
Firewater is discontinued so it will not work (firewater was working with online resources that are not available anymore)
Revone is only able to s-off phones on hboot 1.44 (yours is 1.57)
Sunshine S-OFF is currently the only way you can S-OFF your phone and unfortunately that exploit cost 25$. (you wont pay anything if the exploit doesnt work btw)
Can someone please help me! For now, my phone is bricked at RevolutionHD Google Edition in an endless loop. I can (if I'm fast) change language, and than: reboot.
Click to expand...
Click to collapse
Your phone is bootlooping because this rom require s-off, like its mentioned in the OP of ARHD 6.1:
{
"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"
}
So what you'll need to do
Achieve S-OFF using Sunshine S-OFF
Removed "Tampered" flag and set your bootloader back to "locked"
flash the 1.28.401.8 ruu.zip
Everything explained in detail in this thread
Read carefully and follow step by step what said in post #1, #2 and #4 (you'll be using the ruu.zip method so skip post #3)
Carefully read the FAQ (post 2), almost every issue that you could have (and how to avoid them) are explained there
then your phone will back to 100% stock and ready for repair under warranty.
---------- Post added at 08:24 AM ---------- Previous post was at 08:19 AM ----------
Forgot to say, sunshine will only work on a stock or close to stock rom so you'll have to flash a rom before attempting to s-off.
This one should do the job: https://www.androidfilehost.com/?fid=95916177934521261
flash it from twrp recovery

Thank you for your time!
For using Sunshine I must have a stable OS, but even that I can't get to work... For now I dont mind the "tampered", I just want the stock rom. Is that possible without S-OFF?

CupOfThee said:
Thank you for your time!
For using Sunshine I must have a stable OS, but even that I can't get to work..
Click to expand...
Click to collapse
try that one linked above

alray said:
try that one linked above
Click to expand...
Click to collapse
I saw it, downloading right now. Tonight I'll try it. For now I have work to do
Work should be forbidden.

Related

HTC ONE (dual SIM) dead

Yes, I am retard of the day.
I tried downgrading hboot to 1.44. Don't ask me why. I was on 2.44.
It was 100% success in CMD. On the phone, progress bar did not go full.
I restarted phone, and now I get only black screen. When I connect it to the PC, I heard connection sound.
Now I can't do anything with CMD. I tried connecting with Squabbia HTC One toolkit, and I tried getvar all:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010 ([U][B]THIS IS NOT MY IMEI[/B][/U])
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.034s
Any advice?
SpineSurgery said:
I tried downgrading hboot to 1.44. Don't ask me why. I was on 2.44.
Click to expand...
Click to collapse
I have no idea why I'm even replying, but: Why can't we ask?
... and why did you think an m7_u/ul hboot would be good for your m7xxxxxx ? what model do you have?
nkk71 said:
I have no idea why I'm even replying, but: Why can't we ask?
... and why did you think an m7_u/ul hboot would be good for your m7xxxxxx ? what model do you have?
Click to expand...
Click to collapse
It is just an expression... "don't ask". Of course you can ask. I was trying to get my phone back to 100% stock for past two days... And for some reason I thought that HTC ONE and HTC ONE DUAL SIM hboot's are the same.
My phone model is:
M7C_DUG – Device ID: HTC 802w
Networks: Dual Sim W-CDMA/GSM
MID: PN0771000, PN0772000
Region: China, Russia, Europe
SpineSurgery said:
It is just an expression... "don't ask". Of course you can ask. I was trying to get my phone back to 100% stock for past two days... And for some reason I thought that HTC ONE and HTC ONE DUAL SIM hboot's are the same.
My phone model is:
M7C_DUG – Device ID: HTC 802w
Networks: Dual Sim W-CDMA/GSM
MID: PN0771000, PN0772000
Region: China, Russia, Europe
Click to expand...
Click to collapse
Well MIDs are quite "sensitive" (and I'm pretty sure you had to edit the android-info.txt, to actually get your MID in there, for it to flash... even with S-OFF, it would have given you an MID mismatch) and unless you're into some serious testing and bricking mood, you should have done more research!
I'll just leave these two threads here:
http://forum.xda-developers.com/showthread.php?t=2617159
http://forum.xda-developers.com/showthread.php?t=2495697
maybe they can help you.
If (yes, it's a big if) you are able to get back to an hboot which is appropriate for your phone, then maybe you can get it back up and running using a ruu.zip flash.
By the way, you can only have one MID, not two!! so just copy/pasting information from a different thread, such as:
{
"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"
}
doesn't really help.
Anyway, Good Luck!
nkk71 said:
Well MIDs are quite "sensitive" (and I'm pretty sure you had to edit the android-info.txt, to actually get your MID in there, for it to flash... even with S-OFF, it would have given you an MID mismatch) and unless you're into some serious testing and bricking mood, you should have done more research!
I'll just leave these two threads here:
http://forum.xda-developers.com/showthread.php?t=2617159
http://forum.xda-developers.com/showthread.php?t=2495697
maybe they can help you.
If (yes, it's a big if) you are able to get back to an hboot which is appropriate for your phone, then maybe you can get it back up and running using a ruu.zip flash.
By the way, you can only have one MID, not two!! so just copy/pasting information from a different thread, such as:
doesn't really help.
Anyway, Good Luck!
Click to expand...
Click to collapse
The first one (MID) is that I have.
I will check links you've sent.
If no success, I will get this phone to my friend who is professional GSM unlocker and repair center and has box for HTC repair.
Thank you!

[SOLVED] REQUEST how to unroot htc one full stock

Am s-off and I need to get back to stock for warrenty
device CID HTC__J15
emirates UAE
cant find correct RUU
raido 4A.25.3263.21 DONT know if it was modified but i did not modified any radio or CID before
if rom installation changes it i dont know im noob
hboot 1.56.0000 modified for no red warning
read a thread says this is the RUU for middle east is it right is it safe to use older RUU to restore am really new to this
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in samsung i only need odin and stock Rom Here is a whole different situation
Iloudsan said:
Am s-off and I need to get back to stock for warrenty
device CID HTC__J15
emirates UAE
cant find correct RUU
raido 4A.25.3263.21 DONT know if it was modified but i did not modified any radio or CID before
if rom installation changes it i dont know im noob
hboot 1.56.0000 modified for no red warning
read a thread says this is the RUU for middle east is it right is it safe to use older RUU to restore am really new to this
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
in samsung i only need odin and stock Rom Here is a whole different situation
Click to expand...
Click to collapse
post the output of "fastboot getvar all" except imei and serialno
yes you can safely apply an older ruu if you have s-off, but first lets be sure if its the right one for your phone with the "fastboot getvar all"
also post a picture of your bootloader screen.
alray said:
post the output of "fastboot getvar all" except imei and serialno
yes you can safely apply an older ruu if you have s-off, but first lets be sure if its the right one for your phone with the "fastboot getvar all"
also post a picture of your bootloader screen.
Click to expand...
Click to collapse
------------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH Deleted it for safety
(bootloader) imei: Deleted it for safety
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
----------------------------------------
is it ok to flash RUU with modded Hboot while in s-off
im scared of doing anything Wrong
BOOTLOADER
-------------------------
{
"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"
}
dont know why the OS does not show Up
this the file name of the modded hboot
mod_hboot_1.56.0000_M7_4.19.401.11.zip
does RUU install stock hboot???
do i need to restore stock frimware or Hboot before proceeding to RUU installation
is this the file i need http://www.androidfilehost.com/?fid=23329332407579952
ok i took the risk and flashed the RUU my device is now not tempered
but the i dont get the red warning while booting is this means that the hboot did not restored?
Iloudsan said:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
Click to expand...
Click to collapse
Do you need to S-On?
EDIT: check my guide http://forum.xda-developers.com/showthread.php?t=2541082
use RUU.ZIP method (post #1, #2, and #4) using the 1.28.401.7 RUU.ZIP from guru
or AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
S-On/S-Off is your decision, but you should definitely set it LOCKED (not relocked) and untampered.
nkk71 said:
Do you need to S-On?
EDIT: check my guide http://forum.xda-developers.com/showthread.php?t=2541082
use RUU.ZIP method (post #1, #2, and #4) using the 1.28.401.7 RUU.ZIP from guru
or AFH mirror: http://www.androidfilehost.com/?fid=23329332407584993
S-On/S-Off is your decision, but you should definitely set it LOCKED (not relocked) and untampered.
Click to expand...
Click to collapse
I used the ruu i posted and and then installed TWRP for Guru_Bootloader_Reset_1.0
and then accidentally installed root via Twrp
and when i use The RUU again it gives me error 158 image error and hw to get stock recovery after finishing from Guru_Bootloader_Reset_1.0
i think i will get stuck with the recovery at the end but know even the RUU is not installing now again what to do
i wish that i found your thread before i think you the one who will help me through this
and yes i need S-on for the warranty
downgraded hboot to 1.44 to avoid any problem
is RUU files can be used once???
Iloudsan said:
I used the ruu i posted and and then installed TWRP for Guru_Bootloader_Reset_1.0
and then accidentally installed root via Twrp
and when i use The RUU again it gives me error 158 image error and hw to get stock recovery after finishing from Guru_Bootloader_Reset_1.0
i think i will get stuck with the recovery at the end but know even the RUU is not installing now again what to do
i wish that i found your thread before i think you the one who will help me through this
and yes i need S-on for the warranty
downgraded hboot to 1.44 to avoid any problem
is RUU files can be used once???
Click to expand...
Click to collapse
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download
nkk71 said:
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download
Click to expand...
Click to collapse
yes im still S-off
but the RUU had worked once why is not working again ERROR 158
i am trying it now again
what im doing now is trying to get the device the way it was before the RUU running
maybe it wil work i hope it works
Iloudsan said:
yes im still S-off
but the RUU had worked once why is not working again ERROR 158
i am trying it now again
Click to expand...
Click to collapse
Check md5 first
Sent from my HTC One using Tapatalk
nkk71 said:
Check md5 first
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
how to ??
which application should i use
i dont have .md5 file
dont lnow what am saying
nkk71 said:
Check md5 first
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i got the RUU to work
before working with the RUU i used guru reset like in your thread
just now the RUU finished
and now waiting it to bootup
and confirm no tampered
locked
to s-on the device
thank you
dont leave me still in need for you
the only step left S-ON
nkk71 said:
so you still have S-Off right?
please check MD5 on the RUU download, sounds like a corrupt download
Click to expand...
Click to collapse
ok now im s-on no tampered and locked
is it good to go for warranty?
now am installing OTAs
you are amazing
Iloudsan said:
ok now im s-on no tampered and locked
is it good to go for warranty?
now am installing OTAs
you are amazing
Click to expand...
Click to collapse
yep it's good to send to warranty, why bother with OTAs, they'll probably update it for you anyway
and if all is good please mark the thread as [SOLVED]
nkk71 said:
yep it's good to send to warranty, why bother with OTAs, they'll probably update it for you anyway
and if all is good please mark the thread as [SOLVED]
Click to expand...
Click to collapse
Thank you.
Hoping to mark the thread now
Just one last question is the camera lens glass (cover) replaceable.
Is it under warranty or I should pay for it to be fixed
I don't know how the he'll did it broke

[q] q my htc one not entering recovery mode

HI ALL
MY HTC ONE AT&T UNLOCKED
MY HTC ONE hade a problem with battery
three days back i replace the battery but my device keep rebooting :crying:
i can enter bootloader menu but not revcovery
i try to flash boot.img from cmd its don completely but device same
i try to run ruu rom its don completely but device same
there on different in one case the htc screen come with wirning "This build is for development purposes only do not distribute outside of HTC without HTC's permission ..."
- Device details -
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
openDSP-v31.120.274.0617
OS-3.17.502.3
eMMc-boot 2048MB
sep 10 2013,01:32:23.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3562mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
hope you can help guys
best regards
fastboot flash recovery recovery_name.img
fastboot erase cache
First off, remove your IMEI and Serial Number from the post above. That's sensitive information.
Second, normally the "Development Purpose" message should disappear once you flash back to stock with RUU. are you positive that flashing finished successfully?
Anyhow your problem should be solved - as BenPope has said - by reflashing your recovery. Just pick a suitable revocery image, enter Bootloader in FastbootUSB mode and give it a try:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
i did this guys and my device still same
supermagic49 said:
i did this guys and my device still same
Click to expand...
Click to collapse
Which recovery exactly did you flash? Are you absolutely positive it was a suitable version for your device?
How by the way did you change the battery yourself? Did you disassemble the phone? If so you might perhaps have broken something?
Gesendet von meinem SM-T705 mit Tapatalk
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
- i changed battery in maintenance center but u think it can start bootloader accept flashing an there is something broken
do u advice to disassemble n see
regards
supermagic49 said:
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Those are Stock Recoverys if I'm not mistaken. So even if you flashed those you wouldn't recognize any difference as they don't change anything compared to stock.
But first there's something else I oversaw. In your OP you stated your details. It seems you haven't yet unlocked your bootloader? Or did you just leave out that information? That would be the reason why flashing anything does not work - AT ALL.
Unlock your Bootloader (use seach, there are lots of tutorials on how to do that). Second, please don't temper with the boot.img right now. There is no reason for you to change or overwrite a working bootloader. In fact the chances are you would mess up things even more. So leave the boot.img alone for now.
My suggestion is:
- Unlock your Bootloader (with HTCDev)
- Flash a Custom Recovery (e.g. TWRP - http://forum.xda-developers.com/showthread.php?t=2173870)
- Take it from there. See if recovery works and if so, go ahead an flash a Custom ROM, a Nandroid Backup or get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON. So although you theoretically should be able to flash a (newer) RUU even with S-ON, you can make sure it works by being S-OFF first. SInce only then can you also downgrade your Device via RUU plus it then does not matter if you're locked / unlocked / relocked / tempered. Thing is you need a working Android to get S-OFF. That's why I suggested flashing a Custom ROM. Just about any suitable M7 ROM will do, for example: http://forum.xda-developers.com/showthread.php?t=2334294. Give it a try and tell me how it went, will you? Best of luck. But if you're unsure about anything, ask first. Don't mess things up even more
Ok nosmint
thnx for ur kind following
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
-flash zip and flash recovery is not allowed i think if i clear this problem every thing will be fine
one more thing i open my device i found to cable not fixed i fix bu no changes
that,s the cable was not fixed
{
"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"
}
http://i.ytimg.com/vi/S5KNmDeJ4Ww/maxresdefault.jpg
nosmint said:
... get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON.
Click to expand...
Click to collapse
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
nkk71 said:
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
Click to expand...
Click to collapse
Any advice dear
supermagic49 said:
Any advice dear
Click to expand...
Click to collapse
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
Click to expand...
Click to collapse
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
How can i clear the message of " remote not allowed so i can flash recovery
Regards
supermagic49 said:
How can i clear the message of " remote not allowed so i can flash recovery
Regards
Click to expand...
Click to collapse
you would need to unlock bootloader (it's pretty easy with S-Off), but please first tell us what you want to achieve
nkk71 said:
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
Click to expand...
Click to collapse
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
supermagic49 said:
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
Click to expand...
Click to collapse
use this RUU: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
that will wipe your phone completely and install stock ROM and firmware.
i had tried this too but no change
ruu info
When looking for ruu.exe I went through 6 or 7 different ones. 1 way to know if u have the right ruu is by searching your android and sense version also provider currently on your phone otherwise the ruu won't work s-off dosnt matter I never turned it off on my phone and still got the ruu to work

Problem when I install a RUU.

I'm trying to lose 4.4.4 version (3.30.654.2) to 4.4.2 (1.54.654.15) with an RUU is this ---> https://www.androidfilehost.com/?fid=23578570567720610 and have a VenomROM ROM and I'm trying to do the update to 4.4.2 and I've waited over 1 hour and left me so ...
{
"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"
}
Are you S-off?
Magnum_Enforcer said:
Are you S-off?
Click to expand...
Click to collapse
Yeap S-OFF, Bootloader Unlocked, etc.
What state is your phone in (bootloader menu, Android OS, etc.) ?
Magnum_Enforcer said:
What state is your phone in (bootloader menu, Android OS, etc.) ?
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) imei2: Not Support
(bootloader) meid: Mod Edit
(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
You need to remove your serial number & IMEI info from your post.
Magnum_Enforcer said:
You need to remove your serial number & IMEI info from your post.
Click to expand...
Click to collapse
And as I do that?
byViruZz said:
And as I do that?
Click to expand...
Click to collapse
I removed it from your post for you
BD619 said:
I removed it from your post for you
Click to expand...
Click to collapse
Ok thanks
I think your issue has to do with your Hboot & firmware versions not matching up. Hboot 3.16 is the original Hboot for the M8 while your firmware version is from Hboot 3.19. I would update the Hboot and then try to downgrade.
Just curious, why are you trying to downgrade to begin with? If you downgrade your firmware and Hboot you are going to have issues running Android 4.4.3 & 4.4.4 ROM's.
Magnum_Enforcer said:
I think your issue has to do with your Hboot & firmware versions not matching up. Hboot 3.16 is the original Hboot for the M8 while your firmware version is from Hboot 3.19. I would update the Hboot and then try to downgrade.
Just curious, why are you trying to downgrade to begin with? If you downgrade your firmware and Hboot you are going to have issues running Android 4.4.3 & 4.4.4 ROM's.
Click to expand...
Click to collapse
I'm around trying to be downgraded to do this ------> http://forum.xda-developers.com/showthread.php?t=2718150
And this http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
Did you try to SIM unlock prior to attempting to downgrade?
Magnum_Enforcer said:
Did you try to SIM unlock prior to attempting to downgrade?
Click to expand...
Click to collapse
Yes ... and this version does not work for me and I tried many times and nothing does not work.
byViruZz said:
Yes ... and this version does not work for me and I tried many times and nothing does not work.
Click to expand...
Click to collapse
Ok. Well, try updating your Hboot so it matches your firmware version. That, or run the latest RUU so everything matches up and then downgrade. What ROM were you on?
Magnum_Enforcer said:
Ok. Well, try updating your Hboot so it matches your firmware version. That, or run the latest RUU so everything matches up and then downgrade. What ROM were you on?
Click to expand...
Click to collapse
You pass me a tutorial on how to downgrade the HBOOT? Please and Thanks
I have VenomROM
Thanks for the help.
byViruZz said:
You pass me a tutorial on how to downgrade the HBOOT? Please and Thanks
I have VenomROM
Thanks for the help.
Click to expand...
Click to collapse
HK or non-HK version M8?
Magnum_Enforcer said:
HK or non-HK version M8?
Click to expand...
Click to collapse
HK version .
I would run the RUU from the latest update. It can be found at the top of the first post in the thread linked below (software version 3.31.654.2). Afterwards, try the other RUU to downgrade.
http://forum.xda-developers.com/showthread.php?t=2729173
Curious, but have you looked into using this method to SIM unlock? You have to be using OMJ's ROM. Hit the link below.
http://forum.xda-developers.com/showthread.php?p=52145162
Magnum_Enforcer said:
I would run the RUU from the latest update. It can be found at the top of the first post in the thread linked below (software version 3.31.654.2). Afterwards, try the other RUU to downgrade.
http://forum.xda-developers.com/showthread.php?t=2729173
Curious, but have you looked into using this method to SIM unlock? You have to be using OMJ's ROM. Hit the link below.
http://forum.xda-developers.com/showthread.php?p=52145162
Click to expand...
Click to collapse
Ok thank you very much
And if this method and also did not work for me keeps saying invalid Sim
byViruZz said:
Ok thank you very much
And if this method and also did not work for me keeps saying invalid Sim
Click to expand...
Click to collapse
Ok. Are you trying to SIM unlock to use the phone on another domestic U.S. carrier?

HTC One M7 bootloop, locked bootloader, s-off, nothing works, recovery, flashing

Hi. Everyone I just bought a second hand HTC One M7 and the phone has software issues. I already researched hours into it and tried to fix it by my self but it seems that HTC phones are the hardest phones to fix... So when I start the phone it goes into a infinite bootloop, if I start the bootloader by holding volume down + power, the phone goes into hboot and shows this:
{
"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"
}
So it looks like the phone's bootloader is Locked and S-ON.
Now going deeper into the rabbits hole, the phone appears to be SuperCID 11111111, but who knows? Maybe the previous owner changed its CID...?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA416W901137
(bootloader) imei: 3594050*******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Anyway I tried, Factory Reset, NOTHING, I tried Recovery, nothing, still infinite bootloops. I tried making the phone S-OFF with rumrunner_HTC_0.5.0 and damn I can't even do that. It says "Failed"....
I tried flashing this zip RUU with fastboot: PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip
And it says FAIL file too large or something... the file is about 1.56GB
I even tried copying the RUU archive on a memory flashdrive and connect it via OTG cable. I saw on many threads on this forum suggestions that if the phone can't be flashed through a computer + fastboot, then it must be flashed via "SD card method". What in the world does this even mean? I don't understand?? M7 does NOT have a SD card slot.
Maybe the previous owner accidentally flashed a wrong rom? I don't know, all I know is that this phone consumed at least 12 hours of my time and all for nothing, I still haven't fixed it.
Can someone help me fix this phone? I would be very grateful!
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
myrunes said:
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
Click to expand...
Click to collapse
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
alray said:
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
Click to expand...
Click to collapse
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
myrunes said:
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
Click to expand...
Click to collapse
When you phone is S-ON it must have a locked or re-locked bootloader to flash RUU. Only with S-OFF you can flash a ruu with an unlocked bootloader. TWRP should flash fine if your bootloader is unlocked. Try MDMower's universal version of twrp: https://android.cmphys.com/twrp-m7/
Try flashing this 7.19.401.51 RUU.zip file.
https://androidfilehost.com/?fid=24369303960689843
Don't forget to relock the bootloader and use htc_fastboot.exe to flash the zip

Categories

Resources