[Q] bootloop after reaching lockscreen - G2 and Desire Z Q&A, Help & Troubleshooting

Vision pvt ship s-off
Hboot-0.85.0005
microp-0425
Radio-26.03.02.18_m3
emmc-boot
Oct 11 2010, 20:10:38
Unrooted
Reboot upon load to lock screen.
Tried multiple roms.
Factory reset followed by cache wipe.
Then rom is installed, no gapp package was installed.
Permissions unfixed and phone was restarted.
*edit- tried restart after permissions fixed. Not working still
Could it be that it's overheating? Doesn't feel hot
Any experience or idea what is going on?

first try to get a logcat if possible then i would start by seeing which emmc i have.
then, either way, i would proceed to rooting the proper way as in following the xda wiki to root.
after this i would update my radio and recovery then flash a known stable rom
http://forum.xda-developers.com/showthread.php?t=1983163

demkantor said:
first try to get a logcat if possible then i would start by seeing which emmc i have.
then, either way, i would proceed to rooting the proper way as in following the xda wiki to root.
after this i would update my radio and recovery then flash a known stable rom
http://forum.xda-developers.com/showthread.php?t=1983163
Click to expand...
Click to collapse
It's impossible to pull a logcat without adb, everytime i get to lockscreen it just reboot.
could it be that I flashed a desire z rom and my g2 isn't compaitible with it?

you can have a logcat running while its booting until it restarts, or you can let it restart, boot to recovery and pull a last_kmsg
I also would recommend trying another rom

Related

[Q] Help, semi-bricked DZ

My Desire Z stopped working the other day when trying to update angry birds rio, my phone would just freeze everytime it tried to resume the download (stopped at 92%)
The only way I could use my phone was battery pulls, and disabling all data connections.
After a fair few battery pulls (trying to cancel the download and what not) my phone would stop booting up (stayed at splash screen for ages)
Clockworkmod recovery can't find/mount cache, and won't let me either restore a backup or flash a new rom (I used superwipe).
I've tried everything I can think of, installing different versions of clockworkmod, using RUU's, flashing RUU's via PC10IMG and nothing works.
I can't boot into android to use adb, and I don't think I have an eng hboot so all fastboot commands I've tried have failed.
Hboot:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
RADIO-26.08.04.30_M3
eMMC-boot
Oct 11 2010,20:10:38
I was running SenseGinger 3 with rmk's oc kernel when this first started.
Any help will be greatly appreciated as I'm onto my third day of not been able to use my phone.
-Nipqer
Do you have a warranty on your phone? If so we can all the way brick it using adb, and get it replaced.
Sent from my shiny metal G2 w/ meXdroid V3
If you can get into recovery you can do adb in there, there is something bout that error in recovery that can fix the error, I jus don't remember where, and purposly bricking phone nor gonna do much, try to fix it you can still get into hboot and recovery which is good, what you could do is downgrade phone and reroot, but that's another option after you try fixing recovery
Nipqer said:
My Desire Z stopped working the other day when trying to update angry birds rio, my phone would just freeze everytime it tried to resume the download (stopped at 92%)
The only way I could use my phone was battery pulls, and disabling all data connections.
After a fair few battery pulls (trying to cancel the download and what not) my phone would stop booting up (stayed at splash screen for ages)
Clockworkmod recovery can't find/mount cache, and won't let me either restore a backup or flash a new rom (I used superwipe).
I've tried everything I can think of, installing different versions of clockworkmod, using RUU's, flashing RUU's via PC10IMG and nothing works.
I can't boot into android to use adb, and I don't think I have an eng hboot so all fastboot commands I've tried have failed.
Hboot:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
RADIO-26.08.04.30_M3
eMMC-boot
Oct 11 2010,20:10:38
I was running SenseGinger 3 with rmk's oc kernel when this first started.
Any help will be greatly appreciated as I'm onto my third day of not been able to use my phone.
-Nipqer
Click to expand...
Click to collapse
1 no such thing as semi-brick
2 flash it ?
3 enjoy ?
I see you posted in the other thread that was started about the cache errors, so your best bet is to stick to that thread since it is directly about your issue. Random people coming into this thread will just throw suggestions out that won't work. Or hit the irc chat and see if someone is online that can help right away.
Sent from my T-Mobile G2 using XDA App

Bootloop of Death Without Recovery

Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.
Coldhands said:
Yes, it is another infinite boot loop thread. It was working fine this morning and I was reading a book with Aldiko, then I hit homescreen and locked. From that point it went into the loop.
Okay so I'm somewhat new to the modification scene i.e. I haven't worked with fastboot etc. but I have gathered from other threads some of the information you'll be needing.
Here is my info from the HBOOT screen
Code:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
So here are a couple of things I've tried already..
Using HBOOT to boot to recovery causes it to go back into the boot loop.
I originally had CWM Recovery, so I reflashed recovery (RA-supersonic-v4.3-smelkusMOD) successfully and attempted to then enter recovery mode with the same result - boot loop. I have not tried re-flashing CWM, but I would assume it would produce the same result.
I downloaded the RUU exe that corresponds to my radio, but when running the program it gives me a USB Connection Error code 170. It does mention that the phone has to be turned on, however in what capacity I can have it "turned on" I don't know.
Thank you in advance, please advise if there is any additional information needed.
Click to expand...
Click to collapse
It has to be booted up, being in bootloader won't allow ADB to connect to the device and thats why you're getting the error for the USB connection in the RUU
Try going into recovery (if you can) and clearing EVERYTHING
/data, /system, /cache, dalvik cache, /sd-ext (I would suggest multiple times, or superwipe it if you have that)
Sent from my PG06100 using xda premium
Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:
Coldhands said:
Thank you for the reply, CNexus.
I am unable to get into recovery, but I was able to obtain the rom.zip file that the RUU exe contained and flashed it by renaming it to PC36IMG.zip. The process of flashing was successful on all 6 parts, however, I still have the same issue unfortunately - infinite boot loop, and recovery still looping as well.
I think it may be time to throw in the towel with my Evo unfortunately, barring any information anyone else can provide.
I just am thankful that my upgrade is available on the 1st of the year - but due to extenuating circumstances I will make Sprint give it to me early :laugh:
Click to expand...
Click to collapse
Ah that was a good idea, it sucks that it didn't work though
Good luck then, sorry about your phone
Sent from my PG06100 using xda premium

[Q] Phone started randomly rebooting

HI all, Ive got a desire z and have been running mimicry 1.5.0 for the last month, its all been great, no major porblems and seemed stable. Yesterday voice search stopped working (wasnt picking up anything from the microphone), so I rebooted and it got stuck in a boot loop. It would get just past the animation then reboot back to the HTC screen. This morning I tried deleting caches and user data but that didnt help, so I re-installed mimicry and google apps.
That seemed to work, Id got apps installed again, it had been running for a couple of hours, then the gps stopped working - no satellites found. I did a reset again then it got stuck in another boot loop. Its now in a state where wiping data and re-installing wont fix it. Strangely after reinstalling the first boot will work for a few seconds, enough to select a country, then it just resets and then gets into a loop again, but now it wont get past the end of the animation.Ive just tried 'CM9.1-vision-3.0-Final' and that does the same. I guess this is about the time that its turning wifi on, so maybe its a radio problem?
According to power+vol down:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:38
Ive been trying a few things:
It doesnt matter if Ive got a SIM and/or microSD card in
Running off power or battery makes no difference
Ive flashed it back to mimicry 1.5.0 (its never rebooted in power+vol down or clockwork recovery) but there is some odd stuff:
Now even wiping everything and then installing mimicry, then google apps, I dont actually get maps etc.
It doesnt seem to want to power down, it says powering down, then reboots instead..
So Ive manged to get it back to a point where it will stay up for a minute or so, but trying to use the GPS / wifi seems to make it go back into a boot loop, although I did have it running for about an hour with wifi on without problems...
Ive captured some logs but none of them have anything that looks like major errors before they finish - none of them finish with similar entries anyway..
Any ideas what I can try to fix this?
https://www.dropbox.com/sh/w7im7e9v23tvm8y/IiSLtQmgF1
Copy the dz one to sdcard, rename PC10IMG.zip and flash through bootloader.
Remove image from SD and boot to recovery. Reformat all and flash ROM of choice (do a fresh download or check md5sum for match)
If it still has issues post a log cat so we can get an idea of issue better
More detailed info in post 30 in this thread:
http://forum.xda-developers.com/showthread.php?p=27796375
Sent from my Nexus 7 using xda premium
Thank you so much for the reply and advice. Ive just followed your instructions and it seems to be working!!!!
Im going to give it a good test for the rest of the day, so far it hasnt rebooted unexpectedly at all - thanks
Whats in that zip file thats had an effect? I notice its the 4ext recovery now, was it just that it needed a reformat?
My assumption is that you needed to do a cleaner wipe, usually a good idea between flashes, either a fastboot wipe, superwipe script or the aio tool. At the very least the format option in 4ext is good
But it could have been the radio as well, being you tried a bunch already I figure a start fresh scenario was best or at least simple
Sent from my Nexus 7 using xda premium
The help that I needed!
Thank you so much!
I have a HTC Desire Z since two years. After I read a lot about it the last months i finaly tried to root it and flash CyanogenMod 7.2
A little bit of work, but 6 days ago I did it. But after that I had several Bootloops, again and again. I tried everything, superwipe, different ROMs, searched every possible combination of words with google, asked for help at our german Android-Help site, nothing worked permanently! I could do superwipe and then restore a nandroid backup or flash a differen ROM. It worked only for a short time.
Then, after the last bootloop, I was in the Bootloader and looked at the information on the top.
I gave it a try and searched for "vision pvt eng s-off hboot-0.84.2000 (PC1011000) Microp-0425 RAdio-26.03.02.18_m3 emmc-boot sep 8 2010, 15:56:38"; I got 3 links, the first was this one.
All that I had to do was to flash the zip file you provided, restart and: NO BOOTLOOP!
I hope it works permanently and again:
Thank You!
Heiner

[Q] HELP!! Deleted OS!!

Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
clown6198 said:
Hi guys so I've managed to accidentally bricked my phone and I've been trying to find a way to fix it for days. It's driving me NUTS!!!
So I was trying to install the Harman Kardon feature on my phone buy unlocking it but failed to turn the S-Off. I was following a couple of youtube videos which told me to go to TWRP and wipe all my memory and forgetting to inform the viewers to back everything up until after the video. It's still my fault but my phone is stuck on the logo screen when I try to turn it on which means I deleted the OS. PLEASE HELP!!!
My phone is in this status right now
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1/19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Aug 2 2014,00:28:44.0
My computer won't even recognize my phone when its connected to my pc. I absolutely love this phone and if I can fix it, that'll be ****ing out of this world.
Click to expand...
Click to collapse
stathis95194 said:
Unlock bootloader using your Unlock_code.bin from htc.
Flash custom recovery
Root
Flash rom
Done!!
Click to expand...
Click to collapse
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
clown6198 said:
I got the code and everything but when I connect my phone to the pc. It just makes a noise saying it's connected but I can't do anything.
Click to expand...
Click to collapse
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Yet another user stuck because they followed a tutorial or video guide, instead of taking the time to learn, read, and really understand the steps and concepts. This is exactly why I discourage such tutorials or YouTube guides (and Toolkits as well), as they leave you completely unequipped to recover if you have a problem, leaving your buddies at XDA to clean up the mess.
YouTube video or not, you shouldn't be doing anything you don't understand, and you shouldn't be wiping anything if you don't understand what the result will be.
You will need to troubleshoot the USB connectivity issue first. From there, unlock the bootloader again, install custom recovery and flash a ROM (as stathis95194 has already stated).
stathis95194 said:
so what's the output of:
adb devices
Edit: You don't have an OS so adb won't work. Try fastboot devices
Click to expand...
Click to collapse
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
clown6198 said:
So I managed to Unlock my phone again through fastboot via cmd and I have twrp installed. I have no idea how to flash a ROM. If you can help me with that, I'll be forever in your dept
Click to expand...
Click to collapse
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
redpoint73 said:
Either adb push the desired ROM file to the phone's memory, or put a ROM on a removable SD using a card reader (connected to your computer). Then boot into TWRP, select Install, and find the ROM file and flash it.
Click to expand...
Click to collapse
will this work even with the S-ON?
clown6198 said:
will this work even with the S-ON?
Click to expand...
Click to collapse
Of course. I wouldn't be telling you to do it, otherwise.
redpoint73 said:
Of course. I wouldn't be telling you to do it, otherwise.
Click to expand...
Click to collapse
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Honestly, I would just install Philz recovery instead of TWRP and try to either install the ROM zip directly (after a full wipe), or sideload the ROM zip from your PC.
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time. Find a ROM for your device that is based off of the 1.x firmware and download that. To get your device out of the bootloop and back into boot loader/recovery, hold power and volume up for quite some time until the screen shuts off. Then, hold power down while the screen is black and you'll be in the boot loader. From there you can use the arrow keys to select recovery. Of it isn't there, first select fastboot or hboot and look for it there. You should be in recovery, now you can go ahead and push the file to your phone. Ensuring it is a sense ROM based off of the 1.x firmware, go to wipe and do the standard swipe to wipe (will erase app data not pictures or downloads), then go into install and select your ROM and swipe. Be patient while your device turns on for the initial boot, it might take a while but your phone should be functional after that.
wtoj34 said:
Hmm. It looks like you're on the old radio. If that's the case and you downloaded a ROM based off of the 2.x firmware, you'll get a solid 10 minute boot time.
Click to expand...
Click to collapse
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
clown6198 said:
sorry, so I did send you a message saying if fixed this problem but I guess it didnt. I managed to put a rom in my phone through cmd and I swiped install and goes through the whole installing process. But when I reboot my phone after the installation, it's still stuck in the HTC logo and when I go back to the bootloader, the OS is still empty. What do I do!!!
Click to expand...
Click to collapse
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
Hi so Im in TWRP. I pushed a ROM called Android_Revolution_HD-One_M8_11.1 which is supposedly the closest rom to a stock one. I tried flashing the ROM many times, Im in the process of flashing it again after whiping like you said. The result is the same. After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Thanks,
clown6198
clown6198 said:
After the installation, the phone goes back into TWRP for a slip second and the screen just phases out and turns off. After that, I have to reboot the phone into bootloader again. No luck in getting the OS started. If you guys can recommend me a ROM to try out that's based off of 1.x like the PHILZ one with a link. that'll be awesome
Click to expand...
Click to collapse
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
redpoint73 said:
That was my initial thought as well (long boot time due to outdated 1.xx firmware) but the hboot and radio number given in post #1 indicate that OP seems to be on 2.xx firmware.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
What ROM did you try?
How long did you wait for the phone to boot? First boot after flashing a ROM will take a while, maybe 5 minutes or so.
OS not indicated on the bootloader screen doesn't mean anything (doesn't necessarily indicate a problem with the OS not installed). Its a known bug, and might be blank even if the OS is present.
As previous replies suggest, try a different ROM or another recovery (Philz/CWM).
Also, make sure you do the default wipe in TWRP (which wipes Dalvik, cache, and data) before flashing any ROM (and likewise in CWM). Other partitions do not need to be wiped (in particular, don't wipe Internal Storage, as you will lose the ROM you just pushed to the phone), but failure to wipe data in itself can cause failure to boot.
Click to expand...
Click to collapse
redpoint73 said:
I don't think the ROM being 1.x based versus 2.x is your issue. The radio number and hboot number you listed in Post #1 indicate you are on firmware compatible with 2.x ROMs. Being on outdated firmware doesn't cause the issue you describe, anyway. With outdated firmware, the ROM will still boot but just stalls for a long time (10 minutes) on the HTC screen before booting properly.
PhilZ is a recovery, not a ROM. You can find it (and a great many other useful things) on this thread sticky at the top of the General section:
http://forum.xda-developers.com/showthread.php?t=2694600
I'd try adb wipe cache, then flash TWRP again, or install Philz CWM recovery. Then try to flash the ROM again.
You can also try to download the ROM again to make sure it wasn't corrupted during download. The adb push went okay with no errors?
You can also try one of the stock backups from the collection (adb push to phone and Restore using the appropriate recovery TWRP or PhilZ): http://forum.xda-developers.com/showthread.php?t=2701376
We're getting very close, hang in there.
Click to expand...
Click to collapse
ahahaha THANK you so much!!!! I got the phone to work but now the problem is, I cant get the sound to work when Im playing music. I installed the harman kardon software and I cant get the music to work at all
clown6198 said:
I installed the harman kardon software and I cant get the music to work at all
Click to expand...
Click to collapse
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
redpoint73 said:
I believe you need appropriate firmware in order to run the HK mod. Not sure where this is discussed, but I've seen it mentioned a few times. Try searching the thread where you go the HK mod.
Just curious, what steps did you take exactly, to get the booted?
Click to expand...
Click to collapse
Damn. Apparently I need to get s-off in order for the harman kardon to work. Just need to uninstall harman kardon now... But yea sorry all I needed was to flash the rom. I didn't know the booting was going to take 5 mins and over. I thought that I was just stuck on the HTC logo. all I needed was to be patient ahaha Thanks a lot guys

M8 appears bricked no rom or recovery menu

Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line, on powering on my phone it loads straight into the boot loader, navigating to >HBOOT then pressing >RECOVERY makes the HTC logo appear for a moment before returning to the first bootloader screen.
[software status modified, re locked, security warning, M8-UL PVT SHIP S-ON]
The rom has been deleted along with recovery, I am not an expert in using fastboot tried using it for a bit and had no success also tried installing htc sync manager to see if it would help but the installer for the sync manager would crash my computer every time (windows 10). Looking for some help as what to do not sure if it can be fixed or should I bin it thanks.
I would RUU if it was me in your position.
bigmacattack said:
Tried to remove cynagenmod from my htc and return to stock android settings and messed up somewhere along the line
Click to expand...
Click to collapse
To properly troubleshoot where you went wrong, and how to solve it, you will need to describe the exact steps of how you tried to return to stock.
It seems you wiped things in recovery, expecting that to return you to stock? If so, that isn't the case as you now know, without flashing a ROM, TWRP backup, etc.
Similarly, relocking the bootloader renders the phone unable to boot, and wipes the phone; as it expects RUU to be run. But you haven't explained if you were trying to run an RUU, which one, details of your phone version, etc.

Categories

Resources