HTC One AT&T
S-off
Unlocked
Rooted
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT35SW904937
(bootloader) imei: 354439XXXXXXX65
(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: 3780mV
(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
I have read these threads very thoroughly before posting anything on forum.
Problems: No Sim detected, unknown baseband, imei #, no signal. All else seems to work. Getvar command will show IMEI & baseband.
I purchased from eBay as parts or repair because it was stuck on boot screen. Vendor sell mass phones and did not know the history. Figured it was worth a shot to fix.
Phone was stock AT&T 4.4 with 1.55. No modifications is was just stuck in boot loop. I tried newest version RUU Utility but same results, boot loop. I unlocked bootloader via htcdev and then flashed newest version cynogenmod (even with S-On) and was successful getting it to boot. All seemed great except the was no signal, unknown IMEI (with exception of getvar command), unknown baseband and also cannot save any APN. It won't allow. There are no APN profiles but when I create a new one and click save, it goes back to blank. Sim card is not issue. The problem seems to be with everything concerning network part of the phone. WifI works. I figured since boot issue is resolved I will try RUU utility again but got the same results, back to boot loop.
Next I reverted back to Cyno since it was bootable and I was able to acheive S-Off via firewater and got rooted. I have flashed from cyno 11 down to cyno 10 but same results, no service, imei unkown as well as the other related.
I have ended up with Google play version rom. Also downgraded from 1.55 to 1.54. The last two things a just done was flash darkboot, and reflashed AT&T radio version the showed in getvar and along with trying the newest radio.
Anything I flash goes thru no errors however, this most needed part of the phone won't wake up.
Maybe try international roms on it. Sounds the radio that you flashed or it has is not compatible with it's hardware.
Will do
Solarenemy68 said:
Maybe try international roms on it. Sounds the radio that you flashed or it has is not compatible with it's hardware.
Click to expand...
Click to collapse
I will try that. All I know is, it is a black version with AT&T logo on the rear. Like you stated, the radio or something is not compatible.
Whatever part of the phone that handles these missing functions is just not communicating with the rest of the phone.
Tried all the AT&T radios. None would help. Still no service, imei & baseband shows unknown, sim not detected, apn's won't save.
Tried everything imaginable. I wish I wasn't so determined I should have stopped many hours ago. Doesn't seem anyone knows what causes this. I can see my imei in the getvar but not in the OS. What's weird is that if I flashed a stock AT&T rom I go back to bootloop but I think that something totally different than the GSM part of the phone not working or detecting sim cards. I'm not sure but it seems that if the sim reader was bad I could still view IMEI in About Phone or when pressing * # 06 #
I am having exactly the same problems. Exactly. I was about to post something like this before I stumbled upon this thread. Please update if you find any solution.
Have you tried running any RUUs?
Sent from my HTC One using xda app-developers app
Yes I did. It starts bootlooping at the htc screen. It cannot b a hardware problem with right since we can see the imei in fastboot?
Sent from my HTC One using xda app-developers app[/QUOTE]
Related
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.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-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.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-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
After the ota update to 4.4.2, my phone will only let me make 1 or 2 calls when on 4g and then I can no longer make/receive any calls (until I remove the sim card or sometimes just resetting the radio or clearing the dialer app data then maybe I'll get another call or 2 if I'm lucky).
I'm looking for any help or suggestions. I'm stock, S-On, etc. I've already tried a hard reset... I also reflashed the ota firmware, but had no change.
I found a temporary fix by changing to "gsm only" in the *#*#4636#*#* menu. However, that resets every reboot, and I don't want to be stuck on edge forever.
I would prefer to stay stock, S-On, but I'll take any suggestions...
Thanks in advance
In case it is helpful:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(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: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
UPDATE: I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
enigma2446 said:
Well without achieving s off you are limited to running the ruu for your device. I suggest doing that first and if that don't help you might want to look Into s off for you can flash whatever you want.
"Coming to you live from my Straight Talk LTE One"
Click to expand...
Click to collapse
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S2 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
G8trBryant said:
I ran the ruu for the 4.18.502.7, but there was no change. Do you think there is any chance that it'll work if I flash something different, or is it a hardware issue?
As far as flashing is concerned: I've only done it before on my Galaxy S3 and it was fairly easy/straight-forward. Would you say it's the same for this phone? And is it easy to return to stock when I'm ready to trade-in?
Click to expand...
Click to collapse
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
finanandroid said:
After u run RUU you must do a Factory Reset* or phone reset from stock recovery or setting
This will reset your radios and every setting to factory state.
Click to expand...
Click to collapse
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
G8trBryant said:
Still no luck. I think the ruu did a complete wipe too, but I tried anyways.
I have a few more details: I tried to call my phone, LTE turns off (which is normal), but it never rings then the 4g icon disappears for a minute like it crashed somehow.
Click to expand...
Click to collapse
easy way..... get a new SIM Card*
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
ragnsep said:
Hey All,
To get things started I was just looking to root/rom my friends phone to get him the wifi hotspot among some other goodies associated with custom roms. I have a good amount of experience regarding flashing, rooting, command line, etc.. I change my S4 rom weekly, and have had some experience with HTC recoveries dating back to my old, old, (OLD) HTC Apache (Yeah that was windows mobile 5). More recently I've worked with a HTC EVO.
Here's where I stand with this HTC EVO 4g LTE.
I originally tried to flash a RUU that was 'one click' thinking that it would be similar to the 1-Click Root and Recovery found for Samsung Devices, I was wrong. I know now that I needed S-OFF for this particular file and well, things didnt go well. The RUU froze (guessing because of the security reasons).
So the device now only boots to the HTC Splash indefinately or I can get it into the bootloader.
In an attempt to road of recovery, I have:
Installed TWRP v2.6.1.0 - Leaving **TAMPERED**, (I suspect)
HTCDev unlocked - Leaving **UNLOCKED**
I'd be happy to just get this thing to boot stock rom, from there I think I can S-OFF and get a custom rom on. But one step at at time.
I've tried running RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.4_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_334470_signed.zip as an attempt to recover stock, I've read reports that I might need to relock the phone to get this to work. Is this true?
I've read and read and read and tried and tried to no avail, just looking for a little pointer to get me in the right direction.
Included is my fastboot getvar all:
Code:
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0000
(bootloader) version-baseband: 1.13.11.0830
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27FS401770
(bootloader) imei: 990000667854337
(bootloader) product: jewel
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ7510000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b28ce9b8
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much in advance for any advice or guidance.
Click to expand...
Click to collapse
Yes, relock the bootloader and try the official RUU again. fastboot oem lock.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
ragnsep said:
I get [Error 158] IMAGE ERROR after **RELOCKING** the bootloader. Do I need any firmware zips on my sdcard renamed to P175xxx or whatever is specified for other RUUs?
Click to expand...
Click to collapse
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Try running the RUU found here:
http://forum.xda-developers.com/showthread.php?t=2653730
Bottom of the first post, is the most recent HTC RUU.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
ragnsep said:
Thanks, I noticed this is a different image version...
Out of curiosity, was the partition table on this RUU very different from the previous one? And was that the issue?
Click to expand...
Click to collapse
This one has the partition set up the way it should have been from the start. More space internal for apps and such. Did it work?
Sent from my EVO using XDA Premium 4 mobile app
Have you tried flashing a custom recovery then flashing a sense Rom (you're on 3.17 so anything based on that or 3.16 will be compatible with the version your log says you're on)? If that works then at least you can go for s off before trying anything else.
Sent from my 831C using xda app-developers app
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(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
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(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
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
The Guru Reset would put you back at stock if you so choose. You are given the option in Aroma to "root", chose that option since you are going on to flash ViperOne.
The Guru Reset should have the same firmware in Aroma check that you want the stock radio this will help in ViperOne. I believe the issue you had earlier was the result of incompatible firmware/radio.
Purple haze issue is more likely hardware, but there has been a lot of pseudo fixes.
Thanks for your reply! Just finished backup so starting on it now. Wish me luck!
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
bzowk said:
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
Click to expand...
Click to collapse
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
majmoz said:
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
Click to expand...
Click to collapse
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
bzowk said:
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
Click to expand...
Click to collapse
You are welcome, glad that you are back up and running! :good:
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(bootloader) imei: **************
(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: 3909mV
(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
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
Theirs one big Flaw in your method DO NOT SKIP from 3.x firmware to 5.x firmware .. you'll end up in QHSUSB_DLOAD mode and that's No fun at all.
The correct way to get to the 5.x firmware is
3.x.502 RUU to 4.x.502 Firmware to 5.x.502 firmware
then the Guru reset
I have an AT&T HTC One M8 (US) and am having some issues. So I was running Android Revolution 39.0 (I think) for about a year and decided to just to do a full fresh install of Android Revolution 43.0. This flashed and booted fine, but my wifi wasn't working, so I realized that I needed to update the firmware as well. I did some reading and it seemed that for an S-ON phone, I just needed to find a firmware that matched my modelid and cidnum and then I wouldn't have to worry about changing to S-OFF. I ended up flashing firmware with version 3.11.1700.5 because its info matched my phone (I now know that this firmware is meant for GPE). I then reflashed Android Revolution 43.0 because I read somewhere that I would need to do that after a firmware flash. Now when I reboot my phone, it shows the white HTC boot screen for about 30 seconds, reboots, shows the boot screen again for about 5 seconds, and then boots straight into recovery.
Here is the getvars all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT445WM02341
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?
Find the ATT RUU floating around here, make sure to follow directions on what needs to be done.
http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
hack14u said:
Find the ATT RUU floating around here, make sure to follow directions on what needs to be done.
http://forum.xda-developers.com/att-htc-one-m8/general/lollipop-ota-twrp-backup-firmware-t3075835
Click to expand...
Click to collapse
I had tried this many times before, but I guess I just hadn't found the correct firmware yet. I followed this link found on the post you linked to and downloaded the Lollipop firmware and it worked. I then just used the RUU from HTC's website and all is well. Thanks!
poozer42zer said:
I have an AT&T HTC One M8 (US) and am having some issues. So I was running Android Revolution 39.0 (I think) for about a year and decided to just to do a full fresh install of Android Revolution 43.0. This flashed and booted fine, but my wifi wasn't working, so I realized that I needed to update the firmware as well. I did some reading and it seemed that for an S-ON phone, I just needed to find a firmware that matched my modelid and cidnum and then I wouldn't have to worry about changing to S-OFF. I ended up flashing firmware with version 3.11.1700.5 because its info matched my phone (I now know that this firmware is meant for GPE).
Click to expand...
Click to collapse
I know you sorted it out. But to clarify: You needed Lollipop firmware to support a LP based ROM. You flashed a 3.xx firmware, which is not Lollipop, its Kitkat (Android 4.4.4).
Further, the GPE version does not have the same CID and MID as the ATT version. So it shouldn't have flashed, especially with s-on. Therefore, I'm questioning whether the firmware even flashed properly or not (even though it shows the GPE firmware number in main version in your getvar output).