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.
Related
Hello everyone. I am having an issue and cannot seem to understand what I am doing wrong. I have a view I got for Christmas. It seems like it was partially got the OTA updates. It ran for a while and then started just cycling through the power on / sprint 4g splash screen then would reboot. I can get into Fastboot. I have been messing with it for a few days. Here is where I am at. I was able to find this link http://forum.xda-developers.com/showthread.php?t=1423397 and follow the recomendations there. I flashed the firmware.zip and that went fine then i was able to unlock the bootloader via the HTC dev site (I was unable to do this prior to flashing). After that it seems that everything else fails.
on the fastboot screen I am showing:
unlocked
express PVT SHIP s-on RL
hboot-1.14.0005
microp-0656
radio-1.05.01.1006_3
emmc-boot
c:\htcview>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.05.01.1006_
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT163HY00369
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f821d4db
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have tried flashing:
RUU_Express_KT_KT_KR_1.24.1010.1_Radio_20.35c.30.089BU_3809.06.05.01_M_release_199840_signed
which fails once it hits the signatures on the install. So it is communicating and deletes the user data and starts the install. I have tired several different RUU packages and they all fail. Right now this thing just reboots constantly. any ideas? Suggestions?
Thanks,
Aaron
Wait, are you implying that OTA updates bricked your stock view?
You are not rooted or s-off'ed or anything, is that correct?
the only thing I did was try to unlock the device via the htcdev site. followed their instructions and then started getting the reboots not sure what I did wrong. I would like to be able to s-off and load custom roms but I cannot get anything to load. I have tried the viper rom and also the ruu file in the above post. I do not believe I am rooted but I cannot tell as I cannot boot into the operating system. I can get to the fastboot menu and I can get into Revolutionary CWM v4.0.1.4 console. I am stuck there as nothing else seems to load or install. everything keeps failing.
Downgrade to Gingerbread using RUU and then run revolutionary then just use the update method posted in the forums.
the problem is that when I run the RUU it fails. I cannot get anything to complete for me to be able to even get the system up. The ruu starts and eventually gives me an error stating it cannot communicate with the phone.
still trying different things, but have not progressed anywhere past that yet.
Fastboot flash a recovery (i made a supertool that flashes a recovery its in flyer and view development boards.)
Sent aboard the Evo Express
where do I find the recovery image?
....I suggest you just use the tool I made. It comes with all the images you could need and automatically chooses your device. You just decide which recovery you want and you need to declare which OS you're on (Honeycomb or Gingerbread)
cool got it. Finally got an image to take. Thanks for all your help!
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,
As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.
Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked
Can anyone verify what the problem might be? This is beginning to really piss me off...
(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: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(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
digitalism said:
Hello all,
As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.
Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked
Can anyone verify what the problem might be? This is beginning to really piss me off...
(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: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(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
Click to expand...
Click to collapse
Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's
clsA said:
Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's
Click to expand...
Click to collapse
Strange...but I ended up doing the same. I was hoping to find a .zip of this RUU, but have had absolutely no luck. Everything is running good now, so no troubles to speak of at the moment.
It happened to me as well. I couldn't complete the 4.4 RUU flashing. Instead, I had to flash the 4.3 RUU and then use the OTA package from stock recovery.
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.
Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.
digitalism said:
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.
Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.
Click to expand...
Click to collapse
I pretty much only use Stock Rooted with a custom kernel (ElementalX) or Insertcoin
clsA said:
I pretty much only use Stock Rooted with a custom kernel (ElementalX) or Insertcoin
Click to expand...
Click to collapse
Yes, I was at one point, but after trying out Sense 6, I fell in love. The only problem is the battery performance.
Um theres the rom I put out thats made from developer us build which is same as att device...battery life is good from whats been reported...
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.
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?