I tried to install Lineage 18.0 ( lineage-18.0-20201109-UNOFFICIAL-m8.zip ) on my old HTC m8.
I had previously installed CyanogenMod on it 6(?) years ago, so it was rooted, unlocked, and already had an old TWRP.
I updated TWRP to twrp-3.5.2_9-0-m8.img and got an unofficial lineage 18.0 zip
TWRP installed this fine, I went through the Lineage setup - wifi, time zone etc. It seemed to be working fine. I wanted to sideload an APK from TWRP so restarted the whole phone.
Now there are two problems that prevent me using the phone, and fixing either one of them should be enough for me to fix things.
1) TWRP seems to have disappeared to be replaced with nothing interactive. If I hold power+vol down to get to the menu that le5ts me choose RECOVERY and select RECOVERY it will do one of two things, unpredictably - (1) stay on the white 'entering recovery' 6 seconds, then black 2 seconds then back to 'entering recovery' in a loop, OR (2) it will move onto the Lineage OS boot screen (black with a little animation), get to the home screen and crash back to the Lineage OS loading screen then loop through this continuously.
I see from the Lineage official site that the m8 is only up to 17.1, and they have their own Recovery (I didn't install Lineage's recovery). So this is perhaps mostly my own fault, but I'd like to get back control of the phone and try an official ROM.
Some questions:
1) How do I tell if I still have TWRP somewhere? Can I get back into it to load up a more stable older Lineage OS?
2) Is there any recovery at all? I assume there must be to get the Lineage OS loader started. There's nothing interactive or message about what recovery is running.
3) As I can't get to a functional normal working phone I can't do USB debugging. Can I use the adb commands against the phone if I have it connected by USB and sitting on the FASTBOOT screen from the boot loader? (not sure if I've got the right terminology there, this is the white screen with the two or three bootup items that you navigate with vol up / down and power).
4) Is there anything I can do with the Lineage OS startup so it doesn't just loop upon showing the home screen? Some sort of safe boot mode? I saw an older post saying to hold vol down once the OS boot animation screen starts, but that doesn't seem to do anything for me.
5) Complication - ADB didn't seem to work with this phone any more, even before I got it into this state, perhaps because of age, but it did work many years ago (different PC, USB cable). I think the only way I can get any new content onto the phone is through the external SD card, but even then I need to get to TWRP or something interactive to do anything with the card content.
Thanks for any advice you can offer.
My recommendation:
Take it to authorized service center and let them try to fix it.
jwoegerbauer said:
My recommendation:
Take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
Ebay has them from something like $30 - $60 used, so I don't think its going to be worth paying for a fix. Given that it's rooted and about 7 years old I strongly suspect that it is no longer covered by the warranty (is HTC still in business?). Still a very nice phone for its time - brushed metal body, solid, great stereo speakers, reasonable screen, in 'near new' condition even now. In a few ways better than my S8.
I suspect it will be going for recycling or an aggressive 'ifixit teardown' style post mortem if nothing comes up here.
Related
Hi,
I will prefix this (as there are a few people around with this problem who can get into recovery mode) with the fact that holding down Vol- on boot is not getting me to the recovery / bootloader screen.
I have a rooted HTC Desire S (rooted it nearly a year ago, so info about the hboot etc is a distant memory).
Anyhoo, I decided to have a play about with one of the ICS roms but it was a bit buggy and the camera drivers still aren't working for video so I decided to go back to Endymion V3.4 - http://forum.xda-developers.com/showthread.php?t=1310845
I did a full wipe, installed base rom, installed optional addons and then upgraded to 3.4 - booted fine into the OS so set about getting my system set up the way I like it.
I noticed that endy came with a theme installer so clicked on one of them to have a look, it asked for root, said it was installed and would need to reboot to take effect...
SO
the problem is, it now won't boot and is stuck on the white HTC boot screen.
Holding vol+/- and power buttons reset it but it just ends up back hanging on the boot screen.
Have tried pulling battery and trying again.
Holding Volume Down when powering up is no longer doing anything
So, I either need a saviour to point me in the direction of a fix.. or a kindly sould to break it to me gently when they tell me my phone has gone to the USB Dock in the sky..
Any help will be greatly appreciated.
Thanks
update:
After pulling battery again, pulling out sim and sd cards, booting with vol- held down, i got into recovery. Am going to try and flash a different rom after doing a full wipe, I'll update once it's done but any insights in the meanwhile will still be appreciated
Sorted, cleared the thing out, stuck reaper CM rom on it, rebooted and everything is peachy for now.
Thanks me
Curious if anyone knows why this might have happened?
because you didnt flash the addon zip which was released alongside endymon and then tried to use the addons,it does say on the screen do not use these unless you have installed the addons
I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
Hi guys,
New to flashing custom ROMS. Good news - flashed CM12, then LiquidSmooth and I'm learning a lot after having soft bricked my phone a few times. Bad news - After trying to get back to Stock I'm not able to get out of this LG Logo bootloop. The LG logo will flash, screen will go black and the whole process starts again. It doesn’t progress past that. I'm unable to get to TWRP recovery or download mode.
My idiotic move:
Iffy stability with camera and mobile data with CM and LiquidSmooth. Decided to go back to Stock.
I flashed my nandroid backup, which I believe led to a bootloop (can’t remember). Was able to boot to TWRP and get back to CM12. Then I had the genius idea of using AutoREC and selecting the “Go Back to Stock” option. Yes, it’s already sounding like a bad, and nonsensical idea as I say it now. Can't remember exactly what I did next - I either flashed my nandroid backup or did a factory reset through CM settings. Threw me into this bootloop.
The details:
Model - D800 - Am sure of this.
Stock software before flashing CM12 was Lollipop 5.0.2 via OTA.
TWRP Recovery 2.8x something or other. Used AutoRec to flash.
I can interrupt the bootloop and access Factory Hard Reset through Power + Volume Down
Had to go to JB Bootloader in order to Flash ROMs. Errors returned otherwise.
Roadblocks:
No download mode. Holding Volume Up & Inserting USB cable doesn't work. Although am able to get bootloop to include a blank screen with red flashing LED through this method from time to time.
Phone boots up, and goes directly into bootloop when plugging USB cable into phone. This happens both when plugging into a wall charger or into a computer. I think this is probably the biggest pain and is holding up things from progressing. Can turn off phone by holding down power for a few seconds, BUT if the phone is plugged in it will continue to boot on its own.
Phone not recognized by computer & ADB However, was at times able to get Device Manager to recognize the phone as an "Unknown Device" after going to the Factory Hard Reset screen. This is no longer working after trying different drivers. I’ve went through LG Mobile Universal Driver as well as the Koush driver.
Going through Factory Hard Reset via hardware buttons only throws phone back into BootLoop
Can’t boot into TWRP
Any insight or help guys? Thanks in advance. I think getting into Download Mode will be a quiet victory. I’d like to try to use Supersports guide once I get there to go back to stock.
I was having issues with my Motorola Photon Q LTE with the Stock ROM (it has bootloader unlocked and Rooted), but the problem was, when running apps that play video, they wouldn't work (it would just show a white screen with a film icon). Other phones work, just the Motorola Photon Q LTE was having issues with it. So, I figured i'd try another ROM....I had one problem after another with getting ROMs to work. Carbon ROM would install but would force close FaceBook (which is needed), another ROM gave an encryption error. I went between 2 or 3 recoveries and then found someone that said they had a "stock JB" ROM....I was tired and frustrated and wound up just clicking things b/c at this point, I was ready to toss the phone on the ground so hard that it would make it's way to the center of the earth! But, now i'm stuck on the FastBoot screen with it saying "Battery Low" so I can't flash a recovery onto it again. The battery was at 70% when I was in TWRP before that happened....now I can't get even get into Recovery or anything...
Okay, I think I got it fixed now......I managed to get it to take a charge. I had to plug it in, let it get to FastBoot and then push the Power Button....NOT hold it...just push it and it would turn the display off and start charging....its at TWRP now and installing a ROM...HOPEFULLY I can get passed the "Encryption Error" issue...
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.