[SOLVED][help][modified][sense home unfortunately stopped] - One (M8) Q&A, Help & Troubleshooting

Hello, Greetings XDA members
I have HTC M8x, unlocked bootloader, S-ON,rooted, stock rom, software status was official.
the phone and keys were in the same pocket and i guess volume up + power button might have been pressedd while the phone was in pocket.
the phone vibrated and restarted and was stuck on HTC screen with the famous red warning saying this build is for developement purpose..............and took 1 minute to boot, when the phone booted a screen came saying "ANDROID IS STARTING, OPTIMIZING APPS"
normally when this screen comes the total apps to optimize are 176 , but this time it was only 43, finally the phone booted completely. Now all i have is lockscreen and notification bar i cannot use the phone as it pop comes on a blank screen saying
1-"Sense home stopped unfortunately do you want to send this report to HTC"
2- .the process.com.google.gapps has stopped
3-exchange service stopped
i booted the phone into bootlader the software status has changed to modified.
i had made a nandroid after rooting the phone but the backup being of 7 gb i shifted it to SDcard.
i booted the phone to TWRP recovery to restore the backup but TWRP is unable to find it, it shows nothing when i select sdcard at recover option in twrp( i think its in sdcard so)
and now my phone takes lot of time to reboot. as everytime i restart my phone it gets stuck a while at htc screen with red warning message.
i cannot transfer the backup to twrp internal storage as i do not get the pop to select file transfer when i connect my phone to my laptop
i do have a RUU of my phone matching my region. I will have to relock my phone to flash the ruu
can i unlock it back i do have the unlock.bin file.
what shall i do.
PS: any way to remove the red warning i just dont want to wait so long for my phone to boot
below is my phones getvar all
version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT53LWM01208
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

HTC backup solved the problem.
it restored the apps and later downloaded sense home playstore

Related

Stuck on splash screen- desperately need help!

Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I look forward to your advice.
Thanks a lot in advance.
ronf0303 said:
Hi guys,
I received my AT&T HTC M8 last week.
I wanted to flash the Android Revolution HD rom so I unrooted the device, installed TWRP, super CID it and S-Off it.
I tried to install the Rom but the WIFI didn't work so I rolled back to the Stock using TWRP.
I did some reaches and realize I need to update the Firmware so I did. The messaged at the end of the process was "completed successfully" but when I rebooted the device it got stuck at the splash screen. I can hear the ATT load chime but the AT&T icon is not displayed and that's it, stuck!!!!
I entered the HBoot and tried to access the recovery. The screen gets black with a red triangle icon in the center and the device reboot after several minutes. I think the Hboot message is no image.
When I connect the device to the computer it is recognized and I can access the files etc. but the ADB doesn't see the device any more.
I'm really lost and frustrated after hours and hours of reading and research without any luck.
Any help will be truly appreciated.
This is the device variables before I updated the firmware:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT453WM01167
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I look forward to your advice.
Thanks a lot in advance.
Click to expand...
Click to collapse
You have old, 4.4.2 firmware. That is the issue. Get new firmware and instructions on installing it here or here.
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
ronf0303 said:
Thanks for getting back to me.
The firmware you see in the var. list I placed above is before I changed the Firmware.
As a result the phone is stuck on the splash screen.
I found post Firmware Flashing without the panic attacks... ; (you recommended) and followed the instructions.
The firmware update was complete...
Since that point the phone doesn't boot.
I did a Factory Reset yet still no change.
The most annoing fact is that I can get to the device with ADB.
When I type ADB Devices I get empty list
Click to expand...
Click to collapse
ADB only works in custom recovery or when booted into OS
Fastboot will work on fastboot mode.
Do flash a custom recovery using fastboot. And also erase cache position before booting into custom recovery
It's working - I'm so happy
Hi guys,
Thanks for your support.
Bottom line - The phone is up and running ARHD Ver 21.
I repeated the whole process (flashing the firmware and the rom) but this time instead of flashing the FW I downloaded from the Revolution site (3.32.531.2) I flashed 3.32.531.2_Firmware_TMUS.ZIP I downloaded from
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
So thanks so much for your support.
I'm really really happy

[Q] Phone can't boot for 5+ minutes everytime flashing ROM

Currently running:
Android Revolution HD 21.1
Firmware: 3.28.401.7
Recovery. TWRP 2.8.1.0
Bootloader unlocked
S-OFF
Super CID
Hi guys I need some help as I feel like I'm at risk of bricking my phone everytime I flash a ROM. Just got my M8 recently and everytime I flash a ROM, it is very difficult to turn the phone back on after flashing. This has happened for both ARHD 21.0 and 21.1 for me, they are the only ROM'S I have tried since having this phone. But after the ROM finishes flashing and I select "finish now", the phone shows a split second of the TWRP lock screen and then turns off. From there it is very difficult to turn on the phone no matter what I try. I have tried holding power button for more than 30 seconds, holding power button+down, and power button+up and still no luck. However when I plug the charger in, the red charging light turns on but nothing comes up on screen still. I have to constantly attempt to hold/press the power button for over 5 minutes for the phone to turn on, and once it's turned on its fine to turn back on even when I restart/turn it off. This has happened EVERY time I flash a ROM and I need help as I really feel like I bricked my phone every time.
Does anyone know how to fix this problem? Thank you.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
oblivianz said:
Currently running:
Android Revolution HD 21.1
Firmware: 3.28.401.7
Recovery. TWRP 2.8.1.0
Bootloader unlocked
S-OFF
Super CID
Hi guys I need some help as I feel like I'm at risk of bricking my phone everytime I flash a ROM. Just got my M8 recently and everytime I flash a ROM, it is very difficult to turn the phone back on after flashing. This has happened for both ARHD 21.0 and 21.1 for me, they are the only ROM'S I have tried since having this phone. But after the ROM finishes flashing and I select "finish now", the phone shows a split second of the TWRP lock screen and then turns off. From there it is very difficult to turn on the phone no matter what I try. I have tried holding power button for more than 30 seconds, holding power button+down, and power button+up and still no luck. However when I plug the charger in, the red charging light turns on but nothing comes up on screen still. I have to constantly attempt to hold/press the power button for over 5 minutes for the phone to turn on, and once it's turned on its fine to turn back on even when I restart/turn it off. This has happened EVERY time I flash a ROM and I need help as I really feel like I bricked my phone every time.
Does anyone know how to fix this problem? Thank you.
Click to expand...
Click to collapse
Can you check TWRP and disable screen timeout? Then reflash Rom and see if that fixes the problem
What are hboot and radio number? Either from hboot screen, or adb getvar all.
stathis95194 said:
Can you check TWRP and disable screen timeout? Then reflash Rom and see if that fixes the problem
Click to expand...
Click to collapse
Ok, I'm going to try that and let you know when ARHD 22.0 is released because I try to avoid flashing ROM's as much as possible now. Not a nice feeling when it happens..
redpoint73 said:
What are hboot and radio number? Either from hboot screen, or adb getvar all.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
oblivianz said:
Ok, I'm going to try that and let you know when ARHD 22.0 is released because I try to avoid flashing ROM's as much as possible now. Not a nice feeling when it happens..
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Please edit your post and remove imei and serialno. Posting them in public forums is a big no no
Please delete your IMEI and serial number from the above post. I only asked for hboot and radio number, but forget that folks here are sometimes over-achievers!
Moderator Information,
IMEI and Serial number have been removed. Please do not post this online. It is personal information.
Many thanks,
Stephen
Sorry about that guys, I didn't know. Thank you for removing.
oblivianz said:
Currently running:
Android Revolution HD 21.1
Firmware: 3.28.401.7
Recovery. TWRP 2.8.1.0
Bootloader unlocked
S-OFF
Super CID
Hi guys I need some help as I feel like I'm at risk of bricking my phone everytime I flash a ROM. Just got my M8 recently and everytime I flash a ROM, it is very difficult to turn the phone back on after flashing. This has happened for both ARHD 21.0 and 21.1 for me, they are the only ROM'S I have tried since having this phone. But after the ROM finishes flashing and I select "finish now", the phone shows a split second of the TWRP lock screen and then turns off. From there it is very difficult to turn on the phone no matter what I try. I have tried holding power button for more than 30 seconds, holding power button+down, and power button+up and still no luck.
Click to expand...
Click to collapse
Try turning off the screen timeout in twrp. That's a common problem with roms that use the aroma installer
Edit: sorry, I overlooked someone else who had the same answer

M8 stuck in bootloop(?)

Hey guys,
First off, any help here would be more than appreciated as I am at my wits' end.
So, i shall try and inform you guys as much as I can and hope it suffices. My M8 seems to be stuck in a bootloop. I can get to the bootloader (hboot & fastboot) and that's about it. I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Here is my oem info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA03_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.114.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB003
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS- It is also interesting to note that when my phone is stuck on the white HTC screen, i can hear message notifications and such implying that the phone is still running ( I even mirrored my phone to the pc using USB and I can see my home screen on my laptop but just the HTC screen on the phone.
Thanks a ton in advance
xyzzyx666 said:
I tried to flash a new recovery and kernel through fastboot but that doesn't seem to help either. My phone has been unlocked a long time ago but never had any problems until this suddenly happened.
Click to expand...
Click to collapse
Were you trying to flash anything (such as a custom ROM) to make this happen? If not, why would changing the recovery make a difference? If yes, what did you flash?
Phone was on stock or custom ROM when this started to happen?
Do you have a nandroid backup you can restore?
Also, newer versions of TWRP won't work with your (ancient) hboot, so depending on what TWRP build you flashed, you can just be adding to the problem.
No, I wasn't trying to flash anything which is what baffles me more. My phone just froze all of a sudden and I had to use Power+Volume Up to reboot and it hasn't been starting up ever since.
I'm current;y running a custom ROM (skydragon if I remember well).
The last significant change I remember making was giving the "Clean Master" app accessibility permissions through the settings. Idk why it didn't just ask me to do it through SuperUser there.
As I asked before:
Do you have a nandroid backup you can restore?
If so, try to restore that backup.
Otherwise, try to re-flash the custom ROM.
What version TWRP are you currently on?

Out of ideas so help needed

Hi
I have a problem with a UK M8 which originally had a cracked screen and I replaced it. All good except for some issue of which I cant remember what it was as it was a long time ago. I assumed a sw fault so did OTA update to Marshmallow. However I think it failed during install and then got stuck on htc logo. Factory resets etc had no effect.
So after doing extensive searching I decided to try other methods so unlocked the bootloader and tried to install a rom. To cut a long story short, I have tried everything that I can but I cannot get the phone to boot into OS. I can get it to do the optimizing apps and then it changes to starting apps but sticks on the starting apps screen even if I leave it all day. I have tried various methods but always end up with a phone which will not boot to OS. It did briefly boot into os (partly) butapart from the background and the battery info and couple of other top line details nothing else, then it rebooted itself and htc logo stuck again. I have over the course of time wiped everything from the phone so it has nothing original on it.
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I am now fed up and so need some help. I just want the bloody thing to work again.
Huge thanks in advance
Details as follows
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###########
(bootloader) imei: ############
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I am betting that I have made a schoolboy error. I am also suspecting a hardware fault.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Hazlo99 said:
The last thing I have done is flashed a signed firmware and have tried using ckpv5s nandroid backups on sd card and also the renaming to 0P6BIMG and sd card flash that way. Same result.
I have twrp 3.0.2.0 installed. Unlocked bootloader.
Click to expand...
Click to collapse
restoring nandroid backup is solve the issue of faulty OS if your device doesn't have an official RUU ( as your device )
so try to restore your devices backup ( again if you do it following OP instruction ) from ckpv5 thread i doubt it will fail if it's software issue
Good luck

stuck at bootloop and recovery shuts off

Hi all,
My HTC One M8 is rooted with TWRP. I was having issues with it, so I decided to wipe it to see if that would help . However, it's now stuck in a bootloop, and when i try to get to recovery it turns off, or get a computer to recognize it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA44NWM02554
(bootloader) imei: 352628060928852
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ayouuuuub said:
Hi all,
My HTC One M8 is rooted with TWRP. I was having issues with it, so I decided to wipe it to see if that would help . However, it's now stuck in a bootloop, and when i try to get to recovery it turns off, or get a computer to recognize it.
Click to expand...
Click to collapse
What problems were you having exactly (before you wiped)?
What partitions did you wipe?
The phone is not turning on, it boot for a 2-3 sec that the logo shows up then it turned off, i've tried Volume UP+Volume Down+power method , Volume UP+power,but that's not working,also i tried factory reset ,then flashed RUU, the phone turned on for few minutes, while i was plugging it then it turned off and back to the previous problem. I think it's a battery problem but i don't know cuz it showed that is charged +90% and still not turning on.
It does look like battery issue. And I believe you wiped the OS so it can't boot when connected to charger.
Had same experience on my M7, only can switch on when plugged to charger (I didn't wipe anything so OS was still there and able to boot).
ckpv5 said:
It does look like battery issue. And I believe you wiped the OS so it can't boot when connected to charger.
Had same experience on my M7, only can switch on when plugged to charger (I didn't wipe anything so OS was still there and able to boot).
Click to expand...
Click to collapse
I installed a RUU from HTC's website and it took a few minutes to turn off and not switching on again

Categories

Resources