Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe.
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP
Related
Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!
skandalous1 said:
Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!
Click to expand...
Click to collapse
Did you fastboot erase cache ?
clsA said:
Did you fastboot erase cache ?
Click to expand...
Click to collapse
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.
skandalous1 said:
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.
Click to expand...
Click to collapse
Pretty crazy .. I hope you get it solved
hello dear friends; here is lots of expert users in the forum;
I bought an AT&T phone, the seller ask me to do it is s-off, I said yes;
Everything was working fine, but when I wanted to update its ROM to ARHD 41 (4.4),
My phone became just a waste for me
I can enter hboot, I could upload a twrp 2.6.3.3, I can use adb sdeload,
And also I can flash a ROM, but; it is not starting,
when I power on it, HTC logo is showing, it is getting a Reset and after this it is directly going yo TWRP screen
and then doing this in a loop
There is no expert to correct this problem in my country
And the service will not repair it because it is an AT&T device.
If one of you be my guide, I will be greatful to you
I have tried too many things and now I am very tired to try something
I also changed the cid to upload a new ruu, or I tried to make partitions again etc etc ((((
By the way I cannot wipe the phone from TWRP, it is getting an error : unable to mount /cache and /data
If you explain me what to do step by step I can easily apply it.
Which raido? Which firmware? Which rom? Which RUU? etc... To give it a life again
My main target is to use a stable and fast custom rom. (Like maximus or arhd)
Current infos:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 21 2013, 20:19
Here is current getvar all result:
D:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38CW1234566
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4333mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
skuyumcu said:
hello dear friends; here is lots of expert users in the forum;
I bought an AT&T phone, the seller ask me to do it is s-off, I said yes;
Everything was working fine, but when I wanted to update its ROM to ARHD 41 (4.4),
My phone became just a waste for me
I can enter hboot, I could upload a twrp 2.6.3.3, I can use adb sdeload,
And also I can flash a ROM, but; it is not starting,
when I power on it, HTC logo is showing, it is getting a Reset and after this it is directly going yo TWRP screen
and then doing this in a loop
There is no expert to correct this problem in my country
And the service will not repair it because it is an AT&T device.
If one of you be my guide, I will be greatful to you
I have tried too many things and now I am very tired to try something
I also changed the cid to upload a new ruu, or I tried to make partitions again etc etc ((((
By the way I cannot wipe the phone from TWRP, it is getting an error : unable to mount /cache and /data
If you explain me what to do step by step I can easily apply it.
Which raido? Which firmware? Which rom? Which RUU? etc... To give it a life again
My main target is to use a stable and fast custom rom. (Like maximus or arhd)
Current infos:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.0000
RADIO-4A.22.3263.14
OpenDSP-v32.120.274.0909
OS-4.06.1540.2
eMMC-boot 2048MB
Nov 21 2013, 20:19
Here is current getvar all result:
D:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4333mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post and remove your serial no and the modelid was ok to leave. you already said it's at&t.
you said you flashed recovery
did you clear cache after ?
did you check the MD5 of the rom you downloaded before flashing it ?
your phone shows it was developers edition last .. is this correct ?
your probably going to need to RUU back to stock.
but first try booting to bootloader fastboot USB
and from your pc
fastboot erase cache
fastboot reboot-bootloader and try and flash your Rom again (if it passed the md5 check)
hello clsA; thank you very much for your quick answer, I edit the message and delete the serial but you quoted it
I have made all the things you wrote; but Suddenly I solve the whole problem
When I tried to install SuperSU in TWRP; everything was gone right!
I flashed the ARHD 41, and it is working now
I was trying to fix this problem for 48 hours
at&t htc one m7 problem
But Dear clsA; you can still help me about something; what firmware and radio versions would be your suggestions?
I am living in Turkey, my carrier supports HSPDA
Kind Regards
skuyumcu said:
But Dear clsA; you can still help me about something; what firmware and radio versions would be your suggestions?
I am living in Turkey, my carrier supports HSPDA
Kind Regards
Click to expand...
Click to collapse
The firmware your on now should be fine ..are you getting poor signal of other problems ?
at&t htc one m7 problem
Actually I have no problem; It's signal bars are indicating lower than my old IPhone 4S,
but its coverage and signal quality(also sound quality) is much better than it
I just wanted to be sure by asking you,
And another thing it is writing a caution with red color while booting (This rom is a development purposes only etc. bla bla bla)
This is not bothering me, it can write, if there won't be any problem with stability or performance
Thank you again for your answers
skuyumcu said:
Actually I have no problem; It's signal bars are indicating lower than my old IPhone 4S,
but its coverage and signal quality(also sound quality) is much better than it
I just wanted to be sure by asking you,
And another thing it is writing a caution with red color while booting (This rom is a development purposes only etc. bla bla bla)
This is not bothering me, it can write, if there won't be any problem with stability or performance
Thank you again for your answers
Click to expand...
Click to collapse
your fine ..enjoy your phone
Hi!
After reading massive amounts of tutorials and forums, I just have to admit I cannot handle this and a little help would be nice!
I just bought a nice second hand HTC One (the European m7_ul version, it seems) and there is a big problem: I cannot install any ROMs and the phone just kind of gets into a boot-recovery (ClockworkMod) loop.
This phone has been ridiculously tampered with no knowledge, so it's very hard to pinpoint what on earth has happened in the past. That is why I got it quite cheap. Nice, but now it does not work as a phone at all after I tried some recovery techniques myself.
THE HISTORY AS FAR AS I UNDERSTAND:
-The phone has been first rooted in order to install custom ROMs: Android Revolution HD etc I think.
-It has also been S-offed
-The original user tried to do a "Total factory reset", he wanted the phone to be completely "Stock". He failed-ending up with S-On BUT Tampered/Unlocked etc..
WHAT HAVE I TRIED:
-Tried to OTA Update as the system offered this option. Didn't work, because of Status 7 error on ClockWorkMod.
-Same problem with all of the ROMs I downloaded and then tried to install from SDcard/Sideload (Status 7 error)
-Tried also fastboot flash recoveries, just ending up in a boot loop with HTC logo and sometimes even the exclamation mark+red triangle.
-Frustrated and tired, tried also several instructed ways of S-OFF (Which probably was a dumb idea also).
THE STATUS NOW:
-HTC One only boots into the HTC Logo Screen/ClockWorkMod, but does not let me install any of the ROMs I've tried.
INFO:
Fastboot getvar all gives me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I also got some info from the last known working system while it still was running, before the stuck-in-boot-loop-era:
Android Version 4.3
Sense 5.5
Version 3.62.401.1
HTC SDK API 5.65
Build 3.62.401.1 CL264544 release-keys
The big question: IF it was first rooted, s-offed and then messed up completely (S-on seems to be now forever), is there still hope to get it to work?
--
UPDATE: Got it booting after installing Android_Revolution_HD-One_51.0, which seems to work OK. Normal fastboot sideload installation. I think this phone has been locked (S-ON) while using this exact ROM (Android_Revolution_HD-One_51.0, even the build numbers seem to match with the previously mentioned system. Still, no other ROM can be installed on this phone.
So, seems like we're just stuck with Android 4.3 and I need to backup closely. Am I completely lost with this S-ON theory?
--
Thanks!!
Hey guys,
I've seen plenty threads regarding custom ROMs boot looping, but nothing so far regarding a rooted, stock ROM. I am unaware if I received an OTA (wasn't prompted or anything) or what exactly just changed, but I've had my phone rooted for 4 months now with no issue but suddenly today I noticed that apps were lagging and acting weird so I rebooted my phone. After startup, the phone will go to the home screen and load, but will reboot after 1 minute. I've verified that the phone will not loop once I make it to recovery (TWRP 2.6.3.3) but that's as far as I've gotten. For starters, here is the getvar for the phone:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4T.24.3218.09
version-cpld: None
version-microp: None
version-main: 4.18.502.7
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4168mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-c6bbb6d4
hbootpreupdate: 11
gencheckpt: 0
I'm not that experienced with rooting and such, I was able to teach myself enough to do the rooting and adding recovery but I've not had any issues so I'm scratching my head a bit here. I don't think that resetting to factory and starting over is a good first start, but I don't think I've made any recovery points to roll back to (I'm not sure if it will auto-add recovery points), so where do I go from here? Any and all help is greatly appreciated!
light_pollution said:
Hey guys,
I've seen plenty threads regarding custom ROMs boot looping, but nothing so far regarding a rooted, stock ROM. I am unaware if I received an OTA (wasn't prompted or anything) or what exactly just changed, but I've had my phone rooted for 4 months now with no issue but suddenly today I noticed that apps were lagging and acting weird so I rebooted my phone. After startup, the phone will go to the home screen and load, but will reboot after 1 minute. I've verified that the phone will not loop once I make it to recovery (TWRP 2.6.3.3) but that's as far as I've gotten. For starters, here is the getvar for the phone:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4T.24.3218.09
version-cpld: None
version-microp: None
version-main: 4.18.502.7
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4168mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-c6bbb6d4
hbootpreupdate: 11
gencheckpt: 0
I'm not that experienced with rooting and such, I was able to teach myself enough to do the rooting and adding recovery but I've not had any issues so I'm scratching my head a bit here. I don't think that resetting to factory and starting over is a good first start, but I don't think I've made any recovery points to roll back to (I'm not sure if it will auto-add recovery points), so where do I go from here? Any and all help is greatly appreciated!
Click to expand...
Click to collapse
start by wiping cache and dalvik cache from twrp then reboot and see if you are able to boot in the OS
Hi ,
Yesterday I tried to root my htc one m7_ul ,
I unlocked the bootloader success fully , installed cwm but when I came to install Supersu a message promp after flashing It was something like :yes fix root
disable recovery flash
and no cant remember what I choose but after this I wasnt able to boot into android anymore .
So I made some reasearch and found a guide on how to unbrick using RUU
so I relocked the bootloader using fastboot and tried to flash a zip ruu (bottom of the post) and then this message pop on cmd ;
"invalid sparse file format at header magi"
so now I am stuck
i tried to re unlock the bootloader and using sideload to transfer a rom using adb but after flashing the token I enter recovery (cwm) and I dont get why because I relocked the boot loader and after rebooting I still have a relocked device.
my phone :
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.17.666.35
version-misc: PVT SHIP S-ON
serialno: HT345W913157
imei: 354439054403581
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: BM___001
battery-status: low
battery-voltage: 3527mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
this phone used to be a Bell phone but now is Unlocked .
and Im trying to flash this ruu PN07IMG_M7_UL_L50_SENSE60_MR_BM_7.17.666.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420193_signed.zip
from this forum :http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
thanks everyone :good::good: