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
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
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!!
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
Got an HTC One M7 off ebay and it is having issues with IMEI / Dialer.
With stock settings it will not go to dialer screen, and imei wont show, it does show under getvar in fastboot.
getvar:
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: HT35ZW910932
imei: 354439XXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4282mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-c6bbb6d4
hbootpreupdate: 11
gencheckpt: 0
I have tried several things.
Called AT&T - the IMEI is not blacklisted.
Tried latest RUU for matching CID and phone still gives htcdialer error and reboots randomly.
Tried SF+TeamSeven Kernel same issue. I am trying to S-Off the phone but I dont think that will solve the problem.
With CM11 Rom the phone does not have a reboot problem, but no network or IMEI
I do not know the history of the phone but it does not show sign of damage from a fall.
The phone has no signs that it was opened.
Other problems the phone exhibits are the bottom speaker malfunction (works with pressure over speaker) and the camera has a purple haze when in dark light.
I wonder if maybe it overheated.
HTC wants 90$ to repair it so thats out.
Any suggestions?
Dear xda community,
2 days ago I accidentally wiped the Dalvik Cache, System, Cache, Data and Internal Storage of my device using TWRP advanced wipe, I'm fairly new to all of this and had trouble finding and/or flashing the right RUU on my device.
I tried installing CM 12.1 and a selection of gapps since I couldn't find any stock roms but it gets stuck on the logo.
I have access to the recovery and fastboot and can transfer files on an external SD.
Any advice would be really appreciated!
Here is my getvar all:
version: 0.5
version-bootloader: 2.49.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 3.19.161.3
version-misc: PVT SHIP S-ON
serialno: ----------------------
imei: --------------------------
meid: 00000000000000
product: t6ul
platform: HBOOT-8064
modelid: 0P3P51000
cidnum: VODAP110
battery-status: good
battery-voltage: 3731mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0