Hello everybody, hope everyone is having a better day than I am. I will try to keep this short but I am more than happy to provide more details as they are needed.
I picked up a replacement HTC One (ATT) after a warranty claim for a bad speaker and I immediately rooted it. After rooting the phone and before flashing a custom rom it started rebooting itself every couple of minutes. I went ahead and flashed a custom rom (many to be honest) and the phone booted up just fine, however, the phone would not recognize the sim card. I tried the sim card in a different phone and it worked fine. Then, with the sim card replaced, all of a sudden the phone worked for about 30 minutes. After that it started rebooting itself at will every couple of minutes. I decided that i must have flashed a bad file or something so i decided to go back to stock with RUU.exe. I locked the bootloader and ran the .exe from my laptop (windows 7) Now my phone i "relocked" and the RUU flashed a recovery that I can not get into. My boot screen now reads this
***relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
(date and time)
this is the RUU.exe I loaded
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 - HTC1Guru
Now when I start my phone it loads to the ATT screen with the globe, sometimes plays the chim, and then goes to a white screen with the green HTC. after about a minute it reboots and loads to the exact same spot. It will do this until I enter the bootloader and power it down
I don't know what to do anymore as I have read about a thousand threads and I am getting confused on what the next step should be. I would greatly appreciate a point in the right direction.
Although the POS phone I am using with a modified sim card holder is pretty awesome
Thanks in advance
Get ATT to replace to it again?
there is more back story that I did not go into and i don't know if I can get it replaced again.
Now when I turn on the phone it loads to the initial start up screen where it ask to set up my account and set up wifi. but agian after a minute or so it just reboots and loads to about the same spot and then restarts.
I still think this is fixable
Can anyone point me in the right direction?
Thanks
What software version are you on now? I'm not near a computer but my first thought is that because you are s-on, you can not run an RUU that is older than your current version. So if you are on KitKat now, you can't run a Jelly bean 4.3 ruu.
You would need to be s-off in order to do that.
Sent from my HTC One using Tapatalk
to tell you the truth I don't know anymore because i have tried to load so many different things, how can I tell for sure?
another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.
redraider25 said:
another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.
Click to expand...
Click to collapse
Sure will work as long as RUU is same level as your phone
I would try re-running the RUU. Sometimes they don't do everything correctly. But done right, it should wipe your phone of any custom software and take you back to clean stock.
Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first
Well it looks like you are on 3.17 and the Ruu is 3.17 so give it a shot.
Sent from my HTC One using Tapatalk
redraider25 said:
Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first
Click to expand...
Click to collapse
What about factory reset from bootloader?
42 22435958
Well I tried to RUU.exe again and now the phone will load to the setup. I went through that, but it is not recognizing my sim card. I can sign on to wifi which works and I can navigate the homescreens. after about 2 minutes the phone reboots itself and the whole cycle happens again. i tried to do a software update but with out the sim card being recognized it says Network not available. the signal bar has an "X" and it does not recognize when I try to remove the sim card to reposition it.
should I try a different RUU.exe file? Thanks for all the help, I think we are getting close. One thing I think is strange is when I ran getvar all, it has a strange line I noted it below. Anybody know what this means?
c:\miniadb_m7>fastboot getvar all
(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: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88 THIS LINE HERE!!!!!!!!!!!!!!!!!!!!!!!!!
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance
While the phone is up, can you go to settings > about devices > hardware info> baseband.. is it empty?
The baseband says "unknown"
redraider25 said:
The baseband says "unknown"
Click to expand...
Click to collapse
Its dead Jim.
SaHiLzZ said:
Its dead Jim.
Click to expand...
Click to collapse
really, thats it? No mas htc one for me?
So am I the proud owner of a BRICK?
Related
Ok so i had a problem about a month ago that originally got resolved and everything was working perfectly. After some weird interactions with my PC I now have no baseband or IMEI. I have tried reinstalling the ROM that was working but no luck. Instead i just go stuck in a boot loop. If i let it sit for a while i can get it set up via Wi-Fi but it just doesnt work how its supposed to and fails to get a signal from the cell tower
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
For clarification there WERE numbers in the serial and IMEI in this mode I just ommited them.
DarkShock124 said:
Ok so i had a problem about a month ago that originally got resolved and everything was working perfectly. After some weird interactions with my PC I now have no baseband or IMEI. I have tried reinstalling the ROM that was working but no luck. Instead i just go stuck in a boot loop. If i let it sit for a while i can get it set up via Wi-Fi but it just doesnt work how its supposed to and fails to get a signal from the cell tower
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
For clarification there WERE numbers in the serial and IMEI in this mode I just ommited them.
Click to expand...
Click to collapse
how did you fix it last time? Maybe try that again.
and what weird interractions with your computer?
cr1960 said:
how did you fix it last time? Maybe try that again.
and what weird interractions with your computer?
Click to expand...
Click to collapse
It was a different issue basically last time i uninstalled the OS and had no files on the sd card and i just needed a USB-OTG cable. I believe it had something to do with drivers for the phone. I dont know what it has to do in relation to it but I can confirm that I did nothing to influence the change.
I have full root and can boot the phone up fine but its just the baseband and iemi that are missing however they do show up in the getvar. Im not sure if i should be putting my device on S-OFF and doing an RUU?
DarkShock124 said:
It was a different issue basically last time i uninstalled the OS and had no files on the sd card and i just needed a USB-OTG cable. I believe it had something to do with drivers for the phone. I dont know what it has to do in relation to it but I can confirm that I did nothing to influence the change.
I have full root and can boot the phone up fine but its just the baseband and iemi that are missing however they do show up in the getvar. Im not sure if i should be putting my device on S-OFF and doing an RUU?
Click to expand...
Click to collapse
I don't think that will fix it. There have been a few threads with the same issue - something to do with a corrupt partition if I remember. Hopefully our resident gurus @alray or @nkk71 might be able to help you out.
DarkShock124 said:
Ok so i had a problem about a month ago that originally got resolved and everything was working perfectly. After some weird interactions with my PC I now have no baseband or IMEI. I have tried reinstalling the ROM that was working but no luck. Instead i just go stuck in a boot loop. If i let it sit for a while i can get it set up via Wi-Fi but it just doesnt work how its supposed to and fails to get a signal from the cell tower
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
finished. total time: 0.047s
For clarification there WERE numbers in the serial and IMEI in this mode I just ommited them.
Click to expand...
Click to collapse
Just if i understand correctly, baseband, IMEI etc show up just fine in fastboot getvar all, but in any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
If it's saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
Then I hate to be the bearer of bad news , but it's a hardware problem,
and I haven't seen anyone able to fix it through software (i've personally tried with one user: RUUs, factory resets, even manually overwriting the modem partitions with good ones => no result)
Here's another guy who had the same problem: http://forum.xda-developers.com/showthread.php?t=2696688
(so far i've seen like 3 or 4 incidents)
Sorry buddy
That would be a borked EFS partition (which is individual for each handset so can't be taken from another phone) if it doesn't show them in Settings - nothing can be done other than sending to HTC
nkk71 said:
Just if i understand correctly, baseband, IMEI etc show up just fine in fastboot getvar all, but in any booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
If it's saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
Then I hate to be the bearer of bad news , but it's a hardware problem,
and I haven't seen anyone able to fix it through software (i've personally tried with one user: RUUs, factory resets, even manually overwriting the modem partitions with good ones => no result)
Here's another guy who had the same problem: http://forum.xda-developers.com/showthread.php?t=2696688
(so far i've seen like 3 or 4 incidents)
Sorry buddy
Click to expand...
Click to collapse
Yeah that sucks but I think I still might be in my year of warranty. In which case I noticed that you wrote the returning to stock guide. Would it be an idea to return it to stock or at least to a ROM that doesnt have tampered or unlocked and just claiming it under warranty.
DarkShock124 said:
Yeah that sucks but I think I still might be in my year of warranty. In which case I noticed that you wrote the returning to stock guide. Would it be an idea to return it to stock or at least to a ROM that doesnt have tampered or unlocked and just claiming it under warranty.
Click to expand...
Click to collapse
yeah, but in order to return to stock (to set LOCKED not relocked), you need to be s-off... i don't know how long your ROM is stable (before rebooting itself) to be able to achieve S-Off
nkk71 said:
yeah, but in order to return to stock (to set LOCKED not relocked), you need to be s-off... i don't know how long your ROM is stable (before rebooting itself) to be able to achieve S-Off
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: --------------------
(bootloader) imei: --------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fd1bd949
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
DarkShock124 said:
(bootloader) version: 0.5
(bootloader) version-main: 3.63.980.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
Click to expand...
Click to collapse
Nice, now you can follow my guide, i'm trying to find the downloads you'll need, but seems like i'm unable to access http://www.htc1guru.com/ at this time... hope it's just me, or a temporary problem.
@crushalot all OK on your site mate?
nkk71 said:
Nice, now you can follow my guide, i'm trying to find the downloads you'll need, but seems like i'm unable to access http://www.htc1guru.com/ at this time... hope it's just me, or a temporary problem.
Click to expand...
Click to collapse
Thanks for all the help buddy. I'll check back later when the website comes back up
EDIT: I had a long look at the guide post and came up with these 2 downloads. Correct me if im wrong.
First I would need to install this: http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/ but have to change my CID to one of those listed first.
Then after changing my CID back to the original I would flash this nandroid backup to CWM http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/
Then I should find the closest stock recovery to 3.63.980.2 and finally use guru reset to relock the bootloader
Thanks in advance
DarkShock124 said:
Thanks for all the help buddy. I'll check back later when the website comes back up
EDIT: I had a long look at the guide post and came up with these 2 downloads. Correct me if im wrong.
First I would need to install this: http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/ but have to change my CID to one of those listed first.
Then after changing my CID back to the original I would flash this nandroid backup to CWM http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/
Then I should find the closest stock recovery to 3.63.980.2 and finally use guru reset to relock the bootloader
Thanks in advance
Click to expand...
Click to collapse
Since this is now a return stock issue, i've answered in my thread: http://forum.xda-developers.com/showthread.php?p=51633821&postcount=747
I seem to face a similar issue,,, it says baseband unkown ever since I unlocked - S-OFF and went to GPE....
Have attached the details of the device below,,., hope u can help
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.000
(bootloader) version-baseband: 1.14.2133193
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT459WM07709
(bootloader) imei: 358716053240981
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: GOOGL001
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
I have same issue. I found that flashing Kernel fixes the issue. However after several reboots issue is back. Any suggestions?
thedrunkpretorian said:
I seem to face a similar issue,,, it says baseband unkown ever since I unlocked - S-OFF and went to GPE....
finished. total time: 0.017s
Click to expand...
Click to collapse
I googled and forumed couple of days, and tried RUU exe and zip way, Ndroid backup way, to get my phone back to original stock status, however, once I go back to stock, it will not receive any OTA update. I double checked CID, MID, they are correct and matched with current installed software, I also tried apply OTA file manually, there is a red triangle on the screen, a serious help is needed, thank you all.
D:\HTC\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FAxxxxxxxx
(bootloader) imei: 3563xxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
zhangke said:
I googled and forumed couple of days, and tried RUU exe and zip way, Ndroid backup way, to get my phone back to original stock status, however, once I go back to stock, it will not receive any OTA update. I double checked CID, MID, they are correct and matched with current installed software, I also tried apply OTA file manually, there is a red triangle on the screen, a serious help is needed, thank you all.
D:\HTC\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.19.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
all: Done!
Click to expand...
Click to collapse
is your bootloader unlocked .. are you missing files .. whats the error when you flash OTA manually ?
clsA said:
is your bootloader unlocked .. are you missing files .. whats the error when you flash OTA manually ?
Click to expand...
Click to collapse
thanks for your reply.
I tried among locked/unlocked/relocked bootloaders but no lucky. And i am not quite sure how to quick locate the missing files, I think something wrong with system files, but I think RUU will take everything back to original, am I right?
Manually update will bring me to the red triangle screen.
I have a HTC one with Viper Rom I want to go back to 100% stock to sell. I started this process days ago and I think my first step was to lock the bootloader then try to find an RUU to run. That look about 3 days off my life with bootloops until I locked the bootloader again and now have my phone back.
Here are my specs I think the experts will need- can the helpful community here help me get back to stock and direct me what steps to use?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146603692
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(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
cfclay said:
I have a HTC one with Viper Rom I want to go back to 100% stock to sell. I started this process days ago and I think my first step was to lock the bootloader then try to find an RUU to run. That look about 3 days off my life with bootloops until I locked the bootloader again and now have my phone back.
Here are my specs I think the experts will need- can the helpful community here help me get back to stock and direct me what steps to use?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34JS902192
(bootloader) imei: 990001466036928
(bootloader) meid: 99000146603692
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(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
Click to expand...
Click to collapse
Try this RUU
https://www.androidfilehost.com/?fid=23329332407573774
Thanks, I'm pretty sure I already tried that, but maybe I did the wrong steps or wrong order.
Do I just run that RUU ....no relock or anything else first?
Sent from my HTCONE using XDA Free mobile app
cfclay said:
Thanks, I'm pretty sure I already tried that, but maybe I did the wrong steps or wrong order.
Do I just run that RUU ....no relock or anything else first?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
You can find the instructions for running the RUU here. But here is a more current RUU which I think will match your hboot 1.57. Follow the instructions in the OP.
Thanks, as I recall I tried exactly those steps and that is how I ended up in a boot loop.
Specifically when I ran the RUU it would complete maybe steps 1 of 5 and I would get an error and the program would stop with error 'htc fastboot.exe has stopped working "
Pretty much no method I tried worked until I relocked the boot loader and voila the phone booted finally.
Notice I have higher boot loop version. Does that matter?
Sent from my HTCONE using XDA Free mobile app
cfclay said:
Thanks, as I recall I tried exactly those steps and that is how I ended up in a boot loop.
Specifically when I ran the RUU it would complete maybe steps 1 of 5 and I would get an error and the program would stop with error 'htc fastboot.exe has stopped working "
Pretty much no method I tried worked until I relocked the boot loader and voila the phone booted finally.
Notice I have higher boot loop version. Does that matter?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Please remove from your first post your imei and serialno.
You have a higher hboot, and I think you tried to run a RUU of a lower hboot. Since, you are S-ON you can only run RUU with the same or higher hboot, the same or higher OS/version and the CID & MID must match. If these are not met, it will fail. And the bootloader must be LOCKED or RELOCKED.
majmoz said:
Please remove from your first post your imei and serialno.
You have a higher hboot, and I think you tried to run a RUU of a lower hboot. Since, you are S-ON you can only run RUU with the same or higher hboot, the same or higher OS/version and the CID & MID must match. If these are not met, it will fail. And the bootloader must be LOCKED or RELOCKED.
Click to expand...
Click to collapse
THANK YOU! Another customer serviced. Every issue I encountered I tried to search the answer, and I never found that RUU I guess. You are lifesaver!
I'm rooted/s-off and trying to install the latest Sprint RUU, but run into an error. It happens on the black screen with the HTC logo, right after the RUU boots up the bootloader.
Any ideas on how to rectify this?
Also, is the latest fw able to be rooted, just in case I don't like it I can restore the backup I made?
Sent from my HTC One using XDA Premium 4 mobile app.
johnequickiii said:
I'm rooted/s-off and trying to install the latest Sprint RUU, but run into an error. It happens on the black screen with the HTC logo, right after the RUU boots up the bootloader.
Any ideas on how to rectify this?
Also, is the latest fw able to be rooted, just in case I don't like it I can restore the backup I made?
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
Do you have more info on the bootloader?
Also, just for reference, can we see your fastboot getvar all ?
Remove IMEI, serial No and MEID.
To answer your second questions, yes. I am running the latest firmware with no root issues.
I totally forgot to mention that it was supposed to be the progress bar screen that's black with the HTC logo in the middle.
I'll be back with a getvar later on probably.
Sent from my HTC One using XDA Premium 4 mobile app.
johnequickiii said:
I totally forgot to mention that it was supposed to be the progress bar screen that's black with the HTC logo in the middle.
I'll be back with a getvar later on probably.
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
What does that mean? Can I see a video or pics?
Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: **************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
johnequickiii said:
Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: **************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Getvar looks normal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So now that we know there's nothing really wrong with your firmware, what exactly is the problem?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Where, relative to these commands is the error happening?
Also remember to quote, or else I don't get notifs.
johnequickiii said:
Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: **************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I have noticed the latest RUU's will not run properly (M7 and M8) if the hboot does not match. The latest hboot for the M7 is 1.57.
You may have to flash the latest Full Firmware to update your hboot then run the RUU.
sauprankul said:
Getvar looks normal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So now that we know there's nothing really wrong with your firmware, what exactly is the problem?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Where, relative to these commands is the error happening?
Also remember to quote, or else I don't get notifs.
Click to expand...
Click to collapse
I attempt to run the RUU straight from my desktop.
What happens is the phone does it's initial restart into RUU mode in the bootloader, then the very next screen is the HTC logo on a black screen, which is seemingly supposed to have a progress bar right under the logo. Right there is where the error is thrown.
The RUU program suggests I unplug the phone, which I do, and it's just the bootloader screen with only RUU the only highlightable option. From there, I have to hard reset the phone and I'm back to the start, which is my phone as usual, so it doesn't seem like it ever gets to copy a file or format anything.
johnequickiii said:
I attempt to run the RUU straight from my desktop.
What happens is the phone does it's initial restart into RUU mode in the bootloader, then the very next screen is the HTC logo on a black screen, which is seemingly supposed to have a progress bar right under the logo. Right there is where the error is thrown.
The RUU program suggests I unplug the phone, which I do, and it's just the bootloader screen with only RUU the only highlightable option. From there, I have to hard reset the phone and I'm back to the start, which is my phone as usual, so it doesn't seem like it ever gets to copy a file or format anything.
Click to expand...
Click to collapse
So what's the exact error message? And no, the progress bar only appears after you issue the flash command.
Also, what OS are you using?
BD619 said:
I have noticed the latest RUU's will not run properly (M7 and M8) if the hboot does not match. The latest hboot for the M7 is 1.57.
You may have to flash the latest Full Firmware to update your hboot then run the RUU.
Click to expand...
Click to collapse
What's the latest full one? I'll grab that and give it a shot.
The only reason I'm trying to update now is because I have this issue that seems to kill my battery within 3-4 hours, and I can't figure out why. I thought I'd give a full update a try to see whether it's my phone or something in my setup doing it.
Stock 3.05.651.6, but when I did it I had to start with the very first fw the phone had and take each ota til I was where I am now. That was a long time ago, and this issue only started a week or two ago at most.
Any potential ideas in that realm would be super appreciated.
johnequickiii said:
What's the latest full one? I'll grab that and give it a shot.
The only reason I'm trying to update now is because I have this issue that seems to kill my battery within 3-4 hours, and I can't figure out why. I thought I'd give a full update a try to see whether it's my phone or something in my setup doing it.
Stock 3.05.651.6, but when I did it I had to start with the very first fw the phone had and take each ota til I was where I am now. That was a long time ago, and this issue only started a week or two ago at most.
Any potential ideas in that realm would be super appreciated.
Click to expand...
Click to collapse
5.05.651.2 is the latest
BD619 said:
5.05.651.2 is the latest
Click to expand...
Click to collapse
I probably should've mentioned this in the first post, but that's the RUU I'm trying to use.
I meant to ask which was the first one with the updated bootloader.
@BD619 should he try to flash each partition individually via fastboot?
johnequickiii said:
I probably should've mentioned this in the first post, but that's the RUU I'm trying to use.
I meant to ask which was the first one with the updated bootloader.
Click to expand...
Click to collapse
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
sauprankul said:
@BD619 should he try to flash each partition individually via fastboot?
Click to expand...
Click to collapse
Nah that would be a PITA lol.
BD619 said:
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
Click to expand...
Click to collapse
Where would I find the full one? I got the RUU from HTC.
johnequickiii said:
Where would I find the full one? I got the RUU from HTC.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2795856
BD619 said:
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
Click to expand...
Click to collapse
Now I'm confused. Is there a difference between flashing the firmware and flashing the RUU?
which one is this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
?
sauprankul said:
Now I'm confused. Is there a difference between flashing the firmware and flashing the RUU?
which one is this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
?
Click to expand...
Click to collapse
The firmware will update hboot,radio, ect.
The RUU will update the firmware aswell as the OS.
Got this trying to update with the full firmware.
Sorry about the crappy pic quality. Sensor blew long ago.
Sent from my HTC One using XDA Premium 4 mobile app.
johnequickiii said:
Got this trying to update with the full firmware.
Sorry about the crappy pic quality. Sensor blew long ago.
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
Make sure it's in the folder you are using to open the cmd window.
Make sure it names firmware.zip not firmware.zip.zip
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
arber95 said:
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
Click to expand...
Click to collapse
You have not provided much information.
Which GURU reset you used ? Which firmware you were on before flashing it ?
Also attach you phone to pc in fastboot mode, open command prompt and type in fastboot getvar all
Copy, paste the result over here. Make sure you remove IMEI and Serial No from it.
Also it's generally advised to use TWRP with HTC One.
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..
arber95 said:
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>fastboot getvar all
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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
all: Done!
finished. total time: 0.042s
I am a newbie to HTC, sorry ..
Click to expand...
Click to collapse
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
abdulwakil said:
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
Click to expand...
Click to collapse
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Hold down power button + volume down, the 2 lights on the bottom will flash approx 15 times, just keep holding, when the lights stop flashing, release to power button only, this will take you back to the bootloader.
Flash TWRP 2.6.3.3 recovery using fastboot commands http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
enter recovery, hopefully the guru reset file is still there on your internal storage, if not you'll have to push it to your internal storage using adb, then uplug your phone and flash it.
Seanie280672 said:
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Click to expand...
Click to collapse
I helped him RUU to stock.
He didn't want S-OFF. Just a working phone. He used ruu after incrementally flashing signed firmwares to 4.19.401.9..
Strangely his phone dialer was Fcing even after stock RUU 4.09.401.9
Last thing I know he catched 4.09.401.11 OTA and updated to it.
Don't know if the problem got solved.
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
@Seanie280672, help needed.
arber95 said:
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
Click to expand...
Click to collapse
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
his phone was working on cm12, how come ?
arber95 said:
This is my present getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Seanie280672 said:
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Click to expand...
Click to collapse
He is on 4.09.401.11 firmware. and S-ON
abdulwakil said:
his phone was working on cm12, how come ?
Click to expand...
Click to collapse
Someone else had the same problem recently, I was just trying to find the thread, i'll call for some expert advice, cant quite remember, CM12 / 11 does something slightly different
@clsA @nkk71 @Danny201281
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
abdulwakil said:
He is on 4.09.401.11 firmware. and S-ON
Click to expand...
Click to collapse
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Seanie280672 said:
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Click to expand...
Click to collapse
lol, he hasn't posted the present getvar all output. let him do that.
abdulwakil said:
lol, he hasn't posted the present getvar all output. let him do that.
Click to expand...
Click to collapse
well here is 401.11 full wipe https://www.androidfilehost.com/?fid=23329332407579952
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Yeah definitely sounds like unknown imei and baseband although I would expect you to only see the HTC logo after unlocking the screen.
For some reason CM roms work even with this issue. I believe it's because there is no Sense overlay with CM But I'm not exactly sure why they work.
Can you go to Settings>About>Phone Identity. And check your IMEI number is it displayed as Unknown?
Also Settings>About>Software information>More. And check your baseband is it displayed as Unknown.?
Seanie280672 said:
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
Click to expand...
Click to collapse
Again Sim not recognised, dialer FC, notification center doesn't open, and now it restarts more often (every 2 mins or so)