Okay, so I've got an AT&T M7 that has has (as far as I can tell - a stock version running 4.42 and HTC Sense 6.0) the Software number is 5.12.502.2.
The problem is, that apparently something is extremely corrupted - and I get messages like "Swiftkey has stopped", except replace Swiftkey with tons of other things, as it keeps happening over and over.
If I reboot, any changes that were made (downloads, settings, ANYTHING), apparently gets erased, or is not saved.
I can boot into recovery (which is TWRP 2.7.1.1, and again - any changes I make are not actually written. I can attempt to flash roms (cm, htc1guru stock images, etc.), and they will generally go through the motions of running - and even say 'successful' at the end, but if you reboot after that, everything is still as it was before. No changes at all (think of it like Groundhog Day... every day I can kill myself, eat whatever I want, kill other people(delete stuff, change things, add things) - but after the phone sleeps (aka restarts), the day (aka the phone) is reset as if I did absolutely nothing.)
I have tried wiping cache, data, system, literally EVERYTHING and it does absolutely nothing.
Also, if I try the main Factory Reset from inside the ROM itself, it says it is doing something, but then reboots and everything is back as it was also.
I've tried fastboot boot <insert multiple recovery images multiple times.img>, and it just locks up the phone and I have to hard restart it.
I've tried fastboot flash <new recovery.img> - it actually says successful, but again - does nothing after rebooting.
I am literally going crazy here... I can push files temporarily to the device, and try to do stuff with them, but in the end nothing can seem to make any difference.
I have tried going through htcdev unlock with Unlock_code.bin, and it doesn't do anything.
fastboot oem lock does nothing
Everything I've found says maybe S-OFF would help, but I can't seem to find any way to get that done.
Please, can ANYONE help me figure out how to get this stupid thing to be at all useful again? All help is appreciated. Below is my
e:\Downloads>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSOREDFORMYPARANOIA
(bootloader) imei: CENSOREDFORMYPARANOIA
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Follow the unlock your bootloader thread..
wingsltd said:
Follow the unlock your bootloader thread..
Click to expand...
Click to collapse
Bootloader is unlocked, and I have tried re-unlocking. Nothing changes. I mean, I appreciate the input - but did you even read the post above? Answers like that make me feel like I'm talking to Tier I tech support at Gateway or something.
Related
I bought a T-Mobile USA HTC One from a guy who said it would randomly reboot. When I got it, it was S-ON had Bixie GE Rom and would reboot consistently about every 3 minutes. I managed to downgrade to get S-OFF and have spent a week trying every back-to-stock guide, RUU, firmware flash, Nandroid backup imaginable for both Sense and GE. On GE, I can at least get past the intro and use the phone until reboot, but Sense will always boot to the lock screen and never go further. Any Sense Rom or RUU would not bring up the initial setup. All still had a 3 minute reboot.
Of everything I tried, the [ROM] [AUG 3] [ANDROID 4.3] 3.06.1700.10 - Stock HTC Google Play Edition v1.1 was the only one to fix the reboot issue, but I'm still not able to get service (Baseband and IEMI unknown).
I accept there might be problem with the SIM slot, but does anyone happen to know why this particular Rom would work when everything else failed? All my Google-fu point toward using RUU's, but they simple will not stick, unlocked, relocked, stock recovery, you name it.
T-Mobile Kernel issue?
Any help is appreciated.
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
This is after I tried stock
Sieze said:
does it go into the bootloader and can you get fastboot usb going? try doing
Code:
fastboot getvar all
and see if it looks normal. use mine for reference.
Click to expand...
Click to collapse
Yes, it goes into bootloader just fine. This is my getvar after my last attempt at T-Mo RUU:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 355**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
looks normal too me. have you tried a cutsom kernel? and have you tried full GPE conversion at any time?
it deffinately sounds like the phone is being a boner. if you have TWRP flashed try doing a factory data reset through it and see if it has issues wiping certain things most namely cache and dalvik cache.
and if after you do that nothing presents itself make sure youve got a ROM zip in phone storage or on a flash drive for use with usb otg and wipe system then try and flash a stock ROM and see if it fixes it.
best of luck and hopefully you get it working.
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 all,
So here's why I'm posting:
I'm having an issue with my M8 phone. The phone was working great until I tried to install a new third-party TWRP. I don't know if it was miscommunication or what, but in the process of installing it (https://www.dropbox.com/s/ocvavpttfo...ersion_Fix.img), the phone started having issues.
The initial issue was that the phone would get stuck during boot up. The phone was at the current 2.22 build # but in order to make it at least usable again, I flashed an RUU (1.57 build #) and that seemed to fix everything. But then when I went back from stock recovery to my original TWRP, and flashed a recent backup, the phone froze again during boot up. This process worked many times and as recently as yesterday, but now since trying to install that third-party TWRP, it doesn't. I've tried various things but nothing is working. I know that since I can still reach HBOOT and TWRP that there is hope, but I'm at my wits end as to what to do.
I should also mention that I was using the ViperOne M8 ROM (2.1.0). My phone is unlocked/rooted & S-OFF. There were no issues with it again until I tried to install that new TWRP.
I really love my phone, and hope someone on here can help me. After re-RUUing my phone, I'm going to leave it at 1.57 build # and stock recovery (1.12 #) (and USB Debugging on) until I hear from someone. Basically, I just want my phone to be normal again so I can upgrade back to build # 2.22, flash my custom TWRP recovery, and then flash my most recent backup which included the most recent ViperOne M8 update.
Other info you might want:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thank You,
RockStar2005
RockStar2005 said:
Hello all,
So here's why I'm posting:
I'm having an issue with my M8 phone. The phone was working great until I tried to install a new third-party TWRP. I don't know if it was miscommunication or what, but in the process of installing it (https://www.dropbox.com/s/ocvavpttfo...ersion_Fix.img), the phone started having issues.
The initial issue was that the phone would get stuck during boot up. The phone was at the current 2.22 build # but in order to make it at least usable again, I flashed an RUU (1.57 build #) and that seemed to fix everything. But then when I went back from stock recovery to my original TWRP, and flashed a recent backup, the phone froze again during boot up. This process worked many times and as recently as yesterday, but now since trying to install that third-party TWRP, it doesn't. I've tried various things but nothing is working. I know that since I can still reach HBOOT and TWRP that there is hope, but I'm at my wits end as to what to do.
I should also mention that I was using the ViperOne M8 ROM (2.1.0). My phone is unlocked/rooted & S-OFF. There were no issues with it again until I tried to install that new TWRP.
I really love my phone, and hope someone on here can help me. After re-RUUing my phone, I'm going to leave it at 1.57 build # and stock recovery (1.12 #) (and USB Debugging on) until I hear from someone. Basically, I just want my phone to be normal again so I can upgrade back to build # 2.22, flash my custom TWRP recovery, and then flash my most recent backup which included the most recent ViperOne M8 update.
Other info you might want:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thank You,
RockStar2005
Click to expand...
Click to collapse
You will get better information in the HTC One M8 forum!
majmoz said:
You will get better information in the HTC One M8 forum!
Click to expand...
Click to collapse
Ok thanks! As long as they can help a T-Mobile guy like me!
Thanks,
RockStar2005
I've been trying to install the newer CM Roms , and after researching I was able to set up new partition layout, update firmware, and use Captain_Throwback's modded TWRP. However, the few roms I've tried have given me the same exact issue: The OS loads up, it goes to the main screen, I can unlock screen, go to settings, etc., but after about 10 seconds, the phone freezes and restarts. This will happen infinitely.
This has happened with at least:
cm-11-20141112-SNAPSHOT-M12-jewel
cm-12-20150101-UNOFFICIAL-jewel
cm-11-20150101-NIGHTLY-jewel
I believe I've updated the firmware and setup the new partition style correctly, because:
Captain_Throwback's 4.13.651.4_jewel_stock_rooted_Sense5_Android4.3_odex
ROM works just fine.
When I install I first wipe Dalvik, Cach, system, data, internal storage, and Android secure.
Sometimes I just do a factory reset, still doesn't work. I have also tried the format Data option (erased everything on internal memory)
After it finishes installing I have done with and without Dalvik Cache wipe, same results.
Here's some info about the phone, if you need anymore info I'll gladly provide it! Thank you!
TWRP 2.8.1.0 (modded by Captain_Throwback)
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.1105
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.13.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4108mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Having same issue
I have experienced the same thing recently. Latest CM nightly on HTC EVO 4G LTE ("jewel").
When the trouble began, I was on the last-stable CM build. I would get an infinite splash screen and high temperatures on the device itself (hot to the touch, that is).
I only recently flashed to the latest, thinking it might change my situation. The phone would then boot fine, but, exactly as described above, freeze after maybe ten seconds.. The screen would blank to black, excepting the status bar, no response from buttons.
I doubt there's any correlation, but the last thing I had done on the phone was installing "youMail" voicemail app and trying to get that working. Again, not not to say there's a correlation, just throwing it out there in case someone sees something that I cannot..
I just wanted to throw my voice in and subscribe to the thread.
Eljoshyo said:
I've been trying to install the newer CM Roms , and after researching I was able to set up new partition layout, update firmware, and use Captain_Throwback's modded TWRP. However, the few roms I've tried have given me the same exact issue: The OS loads up, it goes to the main screen, I can unlock screen, go to settings, etc., but after about 10 seconds, the phone freezes and restarts. This will happen infinitely.
This has happened with at least:
cm-11-20141112-SNAPSHOT-M12-jewel
cm-12-20150101-UNOFFICIAL-jewel
cm-11-20150101-NIGHTLY-jewel
I believe I've updated the firmware and setup the new partition style correctly, because:
Captain_Throwback's 4.13.651.4_jewel_stock_rooted_Sense5_Android4.3_odex
ROM works just fine.
When I install I first wipe Dalvik, Cach, system, data, internal storage, and Android secure.
Sometimes I just do a factory reset, still doesn't work. I have also tried the format Data option (erased everything on internal memory)
After it finishes installing I have done with and without Dalvik Cache wipe, same results.
Here's some info about the phone, if you need anymore info I'll gladly provide it! Thank you!
TWRP 2.8.1.0 (modded by Captain_Throwback)
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.1105
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.13.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4108mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First, try updating to the newest TWRP (2.8.7.0). It has Captain Throwback's work done on it. It is the newest, and in my opinion, best recovery for this device. Secondly, if you're trying ROMs, use the ones I have built. They're all linked in my tag, and they are tested. For the moment, use the 5.1 builds, because the Marshmallow ones won't get you video yet, though we are making progress...
Hi, I was trying to revert back to the stock AT&T 6.0 rom using the RUU. I have "Android Revolution HD 53.1" currently installed which is Android 6.0 and Sense 7.0. It is unlocked and S-on, so I re-locked the phone using the fastboot method. After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen. I tried using the RUU anyway, and while it would detect the phone during the setup stages, as soon as it started the update and the phone switched to the htc screen, it would stop and give "error 171 - lost communication with the device."
So I've unlocked it again and it's working fine again. How can I revert it to the stock rom without making it S-off? Thanks!
Oh and if it matters, on the fastboot/hboot screen, it does show an OS version. It just has "OS-"
Edit: Looked at my previous posts as it's been a while since I've came here. Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
rockr09 said:
Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
Click to expand...
Click to collapse
Nice work figuring it out yourself!
rockr09 said:
After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen.
Click to expand...
Click to collapse
FYI, this is normal and expected. Relocking the bootloader renders the phone unable to boot, as it expects RUU to be run immediately thereafter.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?