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
Related
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
Okay, so I seriously messed up my phone hardcore.
CURRENTLY: My phone would turn on to a htc logo screen. If I turn the screen off then on again, the stock version lock screen would show up. But if I unlock the screen, the white htc boot logo would show up.
- I flashed a rom through adb sideload (Guru_Reset_M7_4.19.401.11-TeHashX.zip)
- still showing that htc logo screen when unlocked
I went from using a Lollipop 5.0 unofficial build, somehow my s-off became s-on, without realizing I flashed some other roms, which got my phone not being able to detect my sim card...
Somehow I was able to adb sideload a cm11 rom and get it working again, but my sim couldn't be detected... SO I decided to be stupid and go back to stock to see if anything changed.
But I messed up badly, I messed around with almost everything.
Firmware, adb sideloading, hboot, ruu, to try to go back to stock.
Now I'm just stuck I have no idea what to do.
I'm only able to access bootloader and (twrp) recovery.
I just want to go back to stock. OR just be able to work my phone again.
This is some information:
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-T-MOB010
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-v.32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
....
_______________
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.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: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
_____________________
Can some one please help me..?
I soft bricked my AT&T M8 and am hoping some of the great minds here at XDA can help. Unfortunately, this happened back in September so I've forgotten a lot of what I did to get myself in this mess, but I will try to remember as best I can.
I had originally modified my MEID and was running a GPE ROM. When an OTA update was pushed by Google, I foolishly tried to install it and the phone became stuck in a bootloop. I tried to rectify the situation by performing a system wipe, relocking the bootloader, and running the stock AT&T RUU from the SD card. The RUU failed to run and I received "ERROR 159." I am now stuck with the stock recovery image and my device is no longer recognized in fastboot.
First 6 lines of text on the HBoot screen:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning**
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx (this was populated, I just masked)
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done! finished. total time: 0.013s
Correction, I think it was a GPE RUU that I had installed and not a ROM because my recovery screen is black. I read in another thread that a black screen may indicate this.
I unlocked my bootloader, installed TWRP, and installed Android Revolution 22.1 and the phone still will not boot past the HTC splash screen. I also tried both available RUUs; 1.58 and 2.23. Any suggestions?
I think youd have to revert back to mid of sense version. if s-on I am not sure how you got it to convert in the first place.As I havent ever liked or had the idea of changing the device to gpe. Maybe in the conversion thread you used to convert the device that got you to this point. Are you able to install a gpe rom? I am unfamiliar with ARHD builds
I also have no clue how you got as far as you did without S-OFF. You shouldn't have been able to run a GPE RUU.
ARHD also won't play nice without the 3.x firmware.
Try the desktop .exe versions of the RUUs, if you haven't already, and make sure the md5 matches.
If you can still get twrp on your phone, try restoring a 1.12 or 1.54 backup from here http://forum.xda-developers.com/showthread.php?t=2701376 or http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966.
Make sure to factory reset in twrp.
Your cid and mid are still at&t stock, so I don't think those are the cause of your problem. The fields where the firmware version should be displayed are empty though, and I don't know how you got to that state.
If none of that works, then I'd try a 4.4.4 based GPE rom that still works with the 2.x firmware, like an older version of skydragon. An older version of a sense based rom still using 4.4.3 might still work.
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?