ARHD 84 constant rebooting on htc m7 - One (M7) Q&A, Help & Troubleshooting

I have my friends htc m7 which i installed the ARHD 84 after some one else he gave earlier had messed it up while trying to install a custom rom and was showing tampered relocked on the boot loader. i unlocked the boot-loader now it shows tampered unlocked.
i later put the ARHD 84 and it starts up well and works for some time then later reboots after like 2 min every time. please help resolve this and make it stable
here is the info from fastboot getvar all
c:\mini-sdk>fastboot getvar all
(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:
(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: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
you help will be highly appreciated.
thank you
JAMES MWANGI
[email protected]

jaychedah said:
I have my friends htc m7 which i installed the ARHD 84 after some one else he gave earlier had messed it up while trying to install a custom rom and was showing tampered relocked on the boot loader. i unlocked the boot-loader now it shows tampered unlocked.
i later put the ARHD 84 and it starts up well and works for some time then later reboots after like 2 min every time. please help resolve this and make it stable
here is the info from fastboot getvar all
c:\mini-sdk>fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
you help will be highly appreciated.
thank you
JAMES MWANGI
[email protected]
Click to expand...
Click to collapse
Remove your IMEI and serialno
What recovery (name + version) was used to flash arhd?
Have you tried to format data (not wipe) and re-install the rom?

am using v2.6.3.3 twrp i am trying the format data still dint work
alray said:
Remove your IMEI and serialno
What recovery (name + version) was used to flash arhd?
Have you tried to format data (not wipe) and re-install the rom?
Click to expand...
Click to collapse
am using v2.6.3.3 twrp i am trying the format data still dint work

jaychedah said:
am using v2.6.3.3 twrp i am trying the format data still dint work
Click to expand...
Click to collapse
TWRP 2.6.3.3 should work fine to flash arhd 84, I would recommend to try another kitkat rom (not lollipop since the firmware is to old on that phone) and see if the same issue occur and finally reset the phone back to stock using a RUU. It might be an hardware failure.

Related

[Q] Flashed RUU-HTC_One_GE-2.14.1700.15. Now i am un able to flash any custom ROM's.

Hello,
I recently flashed RUU-HTC_One_GE-2.14.1700.15 to my M7 to see what it was like. Not getting on with it very well i decided to go back to ARHD. When i tried to restore my back up it got stuck in a boot loop.
I then tried a fresh install of ARHD, deleting all data, but this time it will show the splash screen hang for a while and then reboot into recovery.
I have also tried flashing Venom's latest ROM but it dose the same as ARHD.
I am S-OFF and my HBOOT is 1.54
when i do a get getvar all i get the following
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
Pretty stumped no as i can still use the Google RUU but really want to get back onto ADHD!!
Any help greatly received
Kind regards
Russ
rustyp81 said:
Hello,
I recently flashed RUU-HTC_One_GE-2.14.1700.15 to my M7 to see what it was like. Not getting on with it very well i decided to go back to ARHD. When i tried to restore my back up it got stuck in a boot loop.
I then tried a fresh install of ARHD, deleting all data, but this time it will show the splash screen hang for a while and then reboot into recovery.
I have also tried flashing Venom's latest ROM but it dose the same as ARHD.
I am S-OFF and my HBOOT is 1.54
when i do a get getvar all i get the following
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
Pretty stumped no as i can still use the Google RUU but really want to get back onto ADHD!!
Any help greatly received
Kind regards
Russ
Click to expand...
Click to collapse
update your recovery to TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
and flash any roms you want... Do Not Go S-on with the GPE Bootloader installed... RUU back to Stock before you consider s-on .. better yet stay s-off forever !!
clsA said:
and flash any roms you want... Do Not Go S-on with the GPE Bootloader installed... RUU back to Stock before you consider s-on .. better yet stay s-off forever !!
Click to expand...
Click to collapse
This worked a treat. Had to load an older version of ARHD first but got up to 71, eventually.

Need help. I have no OS, and can't install ROMs

Hi.
I rooted my HTC One M7 with CWM as my custom recovery. It all worked fine.
Now, I bought a Chromecast and needed Android 4.4.2+ for screen mirroring, so I decided I wanted to update it.
I couldn't do it, I guess I had to unroot first. So I did a lot of crazy ****, nothing worked.
Now, I followed this, but I'm stuck on the HTC boot logo (white screen). I have TWRP v2.7.1.0a
Even after installing the ROM from sdcard after using adb push rom.zip /sdcard/rom.zip , it says that the installation failed.
Here's my getvar all, notice main version is empty, and I can't find an RRU for my radio / cmid anywhere!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT368xxxxxxx
(bootloader) imei: 357864xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help me!
Prefer TWRP 2.6.3.3
& remove imei and serial number from your post
http://forum.xda-developers.com/showthread.php?t=2791126
yatindroid said:
Prefer TWRP 2.6.3.3
& remove imei and serial number from your post
http://forum.xda-developers.com/showthread.php?t=2791126
Click to expand...
Click to collapse
If only I had a RUU to install...
ZeroTroubles said:
If only I had a RUU to install...
Click to expand...
Click to collapse
Here's your RUU
http://www.htc.com/us/support/htc-one-t-mobile/news/

HTC One 801n Black Screen

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)

[Q] HTC One M7-rooting problem

Hello All first of all
I have been rooting HTC M7 as with provided info on this forum, and have stuck in the step not entering recovery mode.
Did unlocked the phone, downloaded CWM latest version via ADB & fastboot. And when entering RECOVERY, it stucks bottloading recovery mode but doeas not enter RECOVERY MODE. Just a loading message.
The phone was locked to Vodafone. Now it does not matter if I loose waranty.
Just kind of afraid, I am stuck with some too new version. Please help, with some threads or direct solutions.
Here is info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071***
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4037mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6fa8a15d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.157s
Thank you, will await help
Justasdrk said:
Hello All first of all
I have been rooting HTC M7 as with provided info on this forum, and have stuck in the step not entering recovery mode.
Did unlocked the phone, downloaded CWM latest version via ADB & fastboot. And when entering RECOVERY, it stucks bottloading recovery mode but doeas not enter RECOVERY MODE. Just a loading message.
The phone was locked to Vodafone. Now it does not matter if I loose waranty.
Just kind of afraid, I am stuck with some too new version. Please help, with some threads or direct solutions.
Here is info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071***
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4037mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6fa8a15d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.157s
Thank you, will await help
Click to expand...
Click to collapse
try with twrp instead: http://dl.twrp.me/m7/twrp-2.8.6.0-m7.img
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
alray said:
try with twrp instead
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you for the reply!
Tried the latest TWRP too. The only thing happens, it goes to freezing "recovering mode..." and white screen and will not let into recovery mode options. That happens after entering RECOVERY, or trying to reset factory settings.
What have I most likely done, apart trying to load via ADB the CWM and TWRP?. Each time before uploading recovery would erase cache.
Justasdrk said:
Thank you for the reply!
Tried the latest TWRP too. The only thing happens, it goes to freezing "recovering mode..." and white screen and will not let into recovery mode options. That happens after entering RECOVERY, or trying to reset factory settings.
What have I most likely done, apart trying to load via ADB the CWM and TWRP?. Each time before uploading recovery would erase cache.
Click to expand...
Click to collapse
You could try to flash twrp version 2.6.3.3 if it still doesn't work you'll maybe need to relfash the stock firmware and try again to flash the recovery
alray said:
You could try to flash twrp version 2.6.3.3 if it still doesn't work you'll maybe need to relfash the stock firmware and try again to flash the recovery
Click to expand...
Click to collapse
Thak you. TWRP2.6.3.3 really did the jobe, recovering to TWRP mode, and rooting my HTC. Futher more I will study of total rooting capabilities.
Thakns fot help :good:
Justasdrk said:
Thak you. TWRP2.6.3.3 really did the jobe, recovering to TWRP mode, and rooting my HTC. Futher more I will study of total rooting capabilities.
Thakns fot help :good:
Click to expand...
Click to collapse
Hey alray, would you know if there are alternatives to set s-off rather than with SunShine? hboot is 1.61,
Thanks
alray said:
You could try to flash twrp version 2.6.3.3 if it still doesn't work you'll maybe need to relfash the stock firmware and try again to flash the recovery
Click to expand...
Click to collapse
Hey alray. Got already s-off
I am planning to go on cyanogenmod. But the recovery of 2.6.3.3 will be too old I recon. Tried install 2.7.1.1 and 2.8.5.0 on device. However these versions do not work for my device. Only 2.6.3.3 does. Could you suggest me how to succesfully get on twrp later version.
Thank you
Justasdrk said:
Hey alray. Got already s-off
I am planning to go on cyanogenmod. But the recovery of 2.6.3.3 will be too old I recon. Tried install 2.7.1.1 and 2.8.5.0 on device. However these versions do not work for my device. Only 2.6.3.3 does. Could you suggest me how to succesfully get on twrp later version.
Thank you
Click to expand...
Click to collapse
I would try to reflash the whole firmware or ruu and to retry latest twrp. Maybe CWM works?
alray said:
I would try to reflash the whole firmware or ruu and to retry latest twrp. Maybe CWM works?
Click to expand...
Click to collapse
Tried flashing different RUU, but nothing helps to push newest TWRP/CWM recovery image. Changed CID
At the moment the only recovery TWRP-2.6.3.3 works , others crash, no CWM would work either.
Can it be, I need to downgrade HBOOT to lets say 1.44
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) commitno-bootloader: dirty-331585dd
Justasdrk said:
Tried flashing different RUU, but nothing helps to push newest TWRP/CWM recovery image. Changed CID
At the moment the only recovery TWRP-2.6.3.3 works , others crash, no CWM would work either.
Can it be, I need to downgrade HBOOT to lets say 1.44
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-main: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) commitno-bootloader: dirty-331585dd
Click to expand...
Click to collapse
Change CID & MID according to RUU
better solution is to flash firmware
RUU is lengthy process
yatindroid said:
Change CID & MID according to RUU
better solution is to flash firmware
RUU is lengthy process
Click to expand...
Click to collapse
Have changed CID & MID numbers, and the same situation remains-no entrance to TWRP Recovery modes, just messaged "Entering Recovery...". Would you suggest reflashing hboot version?
Thank you.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Justasdrk said:
Have changed CID & MID numbers, and the same situation remains-no entrance to TWRP Recovery modes, just messaged "Entering Recovery...". Would you suggest reflashing hboot version?
Thank you.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
list all the versions of TWRP and Philz you have tried, and where are you getting them ?
Justasdrk said:
Have changed CID & MID numbers, and the same situation remains-no entrance to TWRP Recovery modes, just messaged "Entering Recovery...". Would you suggest reflashing hboot version?
Thank you.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4272mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Now flash 7.17.1540.7 firmware then try again

HTC M One 7 Unable to Install OS,Flash Rom,mount partitions. Need Official RUU!!!

Hey guys,i really Really need your help, need the official RUU for Device. my HTC One M7 is bricked,i previously installed HTC official RUU (developer Edition) but 6 months later,after a power drain it went off and the furthest it can boot is upto the HTC logo white screen.
Can't wipe data or perform a real format coz not a single partition can be mounted in both TWRP and CWM,it's hectic. i've tried all the mount methods in both fastboot and shell but nothing.
Getting that Invalid argument and unable to mount errors.
help me figure out the correct RUU please coz i think that's the only way out (if there's any)..Please, here's my Getvar
D:\Softwares\HTC\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-46c17580
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
PS..The model ID at the back of the device is PN07100,but as you can see in Getvar it is PN0712000,it was changed.
Heeeeeeeeeeeeelp:crying::crying::crying:
OPben said:
Hey guys,i really Really need your help, need the official RUU for Device. my HTC One M7 is bricked,i previously installed HTC official RUU (developer Edition) but 6 months later,after a power drain it went off and the furthest it can boot is upto the HTC logo white screen.
Can't wipe data or perform a real format coz not a single partition can be mounted in both TWRP and CWM,it's hectic. i've tried all the mount methods in both fastboot and shell but nothing.
Getting that Invalid argument and unable to mount errors.
help me figure out the correct RUU please coz i think that's the only way out (if there's any)..Please, here's my Getvar
D:\Softwares\HTC\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-46c17580
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
PS..The model ID at the back of the device is PN07100,but as you can see in Getvar it is PN0712000,it was changed.
Heeeeeeeeeeeeelp:crying::crying::crying:
Click to expand...
Click to collapse
reflash the same ruu , 7.17.1540.51
alray said:
reflash the same ruu , 7.17.1540.51
Click to expand...
Click to collapse
I Tried that, still hangs at the HTC Logo..
OPben said:
I Tried that, still hangs at the HTC Logo..
Click to expand...
Click to collapse
Any error or it flashed successfuly?
alray said:
Any error or it flashed successfuly?
Click to expand...
Click to collapse
It flashes succesfully..then it reboots and hangs at the htc logo
OPben said:
It flashes succesfully..then it reboots and hangs at the htc logo
Click to expand...
Click to collapse
maybe an hardware problem then. You can try with another ruu if you want but it shouldn't make any difference.

Categories

Resources