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.
Related
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?
I softmodded to the developer version from a T-Mobile HTC ONE, and it's heading back for service within the next few days. What I need to know is what RUU files do I need to download, etc to put the phone back to 100% stock?
fastboot getvar all (output)
(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.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4097mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If you need any other information about the phone, let me know and I'll get it for you. Thanks in advance!
BTW, I tried searching, etc to figure out how to do this, but it's all older information and they were all using HBOOT 1.44 (if I need to downgrade that, I've done it before.)
digital4282 said:
I softmodded to the developer version from a T-Mobile HTC ONE, and it's heading back for service within the next few days. What I need to know is what RUU files do I need to download, etc to put the phone back to 100% stock?
fastboot getvar all (output)
(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.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4097mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If you need any other information about the phone, let me know and I'll get it for you. Thanks in advance!
BTW, I tried searching, etc to figure out how to do this, but it's all older information and they were all using HBOOT 1.44 (if I need to downgrade that, I've done it before.)
Click to expand...
Click to collapse
I found this RUU from @Behold_this, it is the 5.14.531.1. There is a Guru Bootloader Reset Tool to make it easier to lock your bootloader.
Well, the CID and MID have been modded, but other than that it's stock aside from the developer rom.
Also, don't forget you will need to change your MID & CID. Here is a tool for changing the MID without ENG HBOOT | Aroma GUI. The MID and CID you might want to change before running the RUU.
Also if TMOBILE cares for s-on then you need to go back all the way to 1.44 hboot with 4.1.2
That's what I did. I changed the MID/CID, removed the "tampered" flag, flashed hboot 1.44, locked the bootloader, flashed the RUU, then locked the bootloader, and set s-on. It's all back to stock now, unrooted. Looks like I never touched a thing. Also, it's going back to HTC I did the advanced replacement, hence the reason I needed to make sure it was completely back to stock. I'm sure if HTC wanted to they could figure out that it had been messed with, but I seriously doubt they would bother since it's for the purple haze in the camera.
Okay, so I returned to to stock yesterday using the correct htc1guru rom. After OTA by phones screen goes pixelated blue and then pink and stops on the htc splash screen. Ive tried re rooting and flashing a custom rom to no avail. I don't have a back up as my PC died and now its stuck on an old update. Does anyone have any idea? I'm going to flash a nandroid back up offline of the uk unbranded htc one but htc1guru is down so I can't download it.
Thanks
Bump. Desperately need this fixed.
Baby_Harris said:
Bump. Desperately need this fixed.
Click to expand...
Click to collapse
HTC1Guru is back up! Have you tried a factory reset from the bootloader screen? Make sure you check the MD5 of the files you download to avoid a corrupt file. It is difficult to help you when you already have a plan in place and are waiting some action from another source. Which seems like a reasonable way out of your issue. Nor did you provide any information on what CID, MID or OS version!
I'll look when I get home from work. I was using paranoid android 4.6 beta 3. Never flash new firmware or radio. My cid is htc u 001 and mid is pn1000. (I'll check exactly as soon as I'm home) the nandroid back up is corrupted. Yes I have tried factory reset
Heres my phone detail. Any Help at all?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(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
Bump
Baby_Harris said:
Heres my phone detail. Any Help at all?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000 << This is the newest hboot
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON << This means you can't flash an older RUU
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) security: on
Click to expand...
Click to collapse
From the looks of it you have already updated the phone to the latest firmware.
Try flashing this firmware>> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.5.zip
and then TWRP 2.6.3.3
and then use this Stock rooted system twrp backup http://goo.gl/zN5ARs or mirror http://goo.gl/tvT1z2
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"
THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
Click to expand...
Click to collapse
Remove your IMEI number and serial number from your first post.
Just use this to return to stock by @clsA put TWRP recovery on your phone, do a full wipe, push or sideload the zip file to your internal storage and then flash it.
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
You don't get rid of dirty, its normal, they all say that.
THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38WW902359
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"
Click to expand...
Click to collapse
Which RUU do you want to flash. A link would be great :good:
I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:
THC Butterz said:
I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:
Click to expand...
Click to collapse
in all honesty, you should of just found the firmware matching the RUU you were trying to flash and flashed that first as you are s-off, you've pretty much done that just manually, glad you got it sorted though :good:
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)