Accidently deleted Android OS on HTC One M8 - One (M8) Q&A, Help & Troubleshooting

I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc. I can't send ADB commands to it, it won't show up on windows file explorer, I can't even turn it off. As is said this is an old phone so I am not worried about losing data, which is probably just as well at this stage!
Any advice would be appreciated!

Kieran C said:
I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc.
Click to expand...
Click to collapse
The physical buttons will respond, but you need to hold them for a pretty long time in the current "stuck" state. Do this:
1) Hold vol up button and power button, until the phone restarts (may take about a minute in the current stuck state).
2) Once the screen goes dark to reboot (but before the HTC logo screen appears again - I think you have 5 seconds or so), let go of the buttons, and only hold the vol down button. Do not let go of vol down, until you see the bootloader screen.
3) If you fail to get to bootloader, you simply got the timing wrong. Either started pressing vol down too late, or you let go of it too early. Simply repeat steps 1 and 2, until you get to bootloader.
4) Once in bootloader, simply select recovery, which will boot TWRP. And flash Lineage as you originally intended.
A note on wiping system when flashing a ROM: I know some folks will swear by this, and some guides will tell you to do it. But it is not necessary, and as you've seen can cause some complications. Nothing that isn't easily solved, but may give you headache nonetheless (like this case here).
The ROM install script will wipe system before it installs the custom ROM. So doing it yourself is redundant. And in the case of the ROM fails to install (it happens) you are stuck without a working OS. My recommendation is only to wipe cache, Dalvik and data when flashing a custom ROM (the default wipe in TWRP).
Any perceived "benefit" from wiping system is usually a placebo. In the rare event that the custom ROM fails to boot (or some other issue), you can always go back and flash again, wiping system (as a troubleshooting measure, etc.). Of the years of flashing ROMs (dozens and dozens of times) on various Android devices, I can count maybe 2 times where I felt I needed to wipe system when flashing a custom ROM.
Kieran C said:
I can't send ADB commands to it, it won't show up on windows file explorer
Click to expand...
Click to collapse
This can be expected when "stuck" on the logo screen. adb will only work when booted to a working OS, or alternately when booted to TWRP. Same thing with MTP access (File Explorer).

Related

Mate suddenly stuck in bootloop

After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
SvenHee said:
After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
Click to expand...
Click to collapse
Usualy for the fastboot output that you got it means you need to reinstall the drivers.
Sent from my SM-G850F
Reinstalling drivers if for windows is it not?
Until now I found that linux is super easy in installing adb and fastboot, and previously, during instalation of the phone, installing adb and fastboot was all I did.
Assuming that the 10.1 ROM still is present on your SD card try to reinstall it dirty. Just wipe cache and dalvik cache before rebooting into the system. Only the rom.
Got it working again with just a factory reset, but off course, all data and settings were gone.
I did try to put (partial) backups back but that broke the system again.
It is a shame that all my texts are gone, but I'll get over it.
Thanks for the help guys!

can't exit from recovery menu - xpopC9

IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Wow
Wow, no reply. Is it there someone hereeeeeeeee?
gaucho1978 said:
IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Click to expand...
Click to collapse
Just discovered your post. Have you solved the issue?
First of all, the recovery image is not stored in the bootloader...whatever you meant by that. It is stored in the recovery partition. The boot.img is NOT the bootloader. It is the kernel. And it is stored in the boot partition. Those questions simply sound like you are trying to figure out why your phone is booting into recovery. Even after you have restored the STOCK ROM using Alcatel's Mobile Upgrade S.
My first thought was that you have no system image or that your custpack partition is corrupted. But those issues would lead to a boot loop or you would just hang on the boot logo and not move forward. Plus you restored the stock ROM. So that's really strange that you're booting only into recovery each time.
However what is more likely is that you are not starting your phone correctly. I once had a lady with the exact same issue. Her phone developed this strange problem where it would only boot into recovery. Her phone was completely stock. She never did anything with her phone except use it like a non-techie would use their phone. She didn't even know what recovery meant. All she knew was this strange menu always appeared when she started her phone.
BUT, when I booted her phone...guess what? It booted up just fine! But with her, her phone would always boot into recovery. You know why? I watched her boot her phone. She had developed a new habit every time she started her phone of inadvertently applying pressure on the Volume UP button while she was turning on her phone...because it was on the opposite side of the phone from the power button.
It's really weird that the problem persists even after you flashed back to stock. If that's the case, my only other guess is that your motherboard is damaged, or perhaps it's not you who is holding down the vol+ button...maybe it's just stuck.

Stuck on load screen, unabled to enter recovery, adb erase cache has no effect

So my second zenfone is dead.
Like many others, it gets stuck at the asus loading screen with the spinning wheel.
This did not happen after any obvious action, like an update - it was just turned off when i woke up, and wont load beyond the spinning wheel of death.
I have booted into fast boot mode (power and vol +), selected [recover mode] and got the broken android logo.
I then hit power and vol+, then release vol+ as suggested, but instead of a menu, i get a bunch of yellow console output, 3rd line of which is:
E: failed to mount /cache (invalid argument)
This appears for less than a second, then back to flashing broken android logo.
Repeating ( power and vol+, then release vol+) results in the same briefly visible console output
I turn off, and reboot into fast boot mode, and try using adb.
I enter the command 'fastboot erase cache' and it completes in 0.4 seconds, no errors. Has no effect on phone (reboot stuck loading, recovery mode same error as above).
Next i try 'fastboot format cache' - the command appears to work, but again completes in just over a second, and has no effect on the phone.
The only info i could find directly relating to this error is on a random .info website, so im reluctant to follow the steps:
http://mobilecon.info/fix-asus-zenf...-into-recovery-mode.html#sthash.slqGoK95.dpbs
Anyone here solved this issue? Or is it time for a warranty claim?
Thanks
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
azthemansays said:
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
Click to expand...
Click to collapse
Thanks for the link - it looks much the same as the one i posted, with the addition of flashing the system image.
Do you know if there is any danger in trying without flashing system 1st?
Also, have you used or seen this method used specifically to fix the mount failure i have described, or its just a general 'de-bricking' guide?
Finally, do you or anyone else have any insight into why this might have happened in the 1st place - as i mention, i did not do anything beyond normal use prior to the issue.
thanks
Sounds like the recovery corrupted... could be a range of things from improper shutdown to an improperly coded app that caused the error. If you want to flash just the recovery and see if that fixes it, go right ahead, but don't forget to erase your cache after you flash recovery.
Whenever I get stuck in a bootloop, the steps I follow are:
1) clear the cache and see if it fixes it, as something might be there that's preventing you from booting
2) flash the most current firmware to see if it fixes it, as something might have modified a section of one of the partitions that's preventing you from booting (make sure to clear cache after flashing)
3) contact support because it's more likely hardware failure
There's no danger in flashing any of those partitions, at most you'd lose the Xposed framework, root and busybox - which are easy to reinstall. It doesn't affect much else, and your info should be intact. I would advise getting the firmware from a reputable source though... I just get it off the Asus website, then root the phone after.
Try reinstall recovery
Download stock recovery(there is download link from zenfone2 index)>go fastboot mode>then flash recovery using command :
fastboot flash recovery (recovery image name).img
>Reboot to recovery>adb sideload full firmware

Weirdest issue ever seen - endless reboot to "OTA updating", stuck at 53%

I'm a computer science student, so assume me with required ability.
Also I've searched this issue for a whole afternoon, I'll list the methods that I tried below.
Environment:
M8 android 6.0, s-off, unlocked bootloader, rooted, twrp recovery
Some modification to system partition(hosts, busybox, bloatware removed)
Set-up before applying an small ota(~89mb):
Since it's a trivial update, I didn't bother reflash all the system image - and I can't find one for my country(TW)either.
I documented every change in system partition, so I did the following steps to prepare.
1. removed xposed framework
2. unrooted by supersu built-in function.
3. put deleted bloatware back to /system/app, /system/priv-app .
libRSSupport.so and librsjni.so under /system/lib/ have been modified and I don't know why - whatever, I replaced them with the stock one.
4. reflashed stock recovery
I DID NOT(forgot to) uninstall busybox and revert the changes of hosts file, if this matters.
/system/bin/app_process32, boot partion and Supersu modified files are "likely" to be restored to stock.(I have no way to confirm.)
Problem:
Applied OTA, it rebooted to a green spinning circle with progression bar- regular OTA procedure.
But, it stuck at 25% for seconds(guess it's system partition integrity check), and progressed to 53%, stuck at 53% for about 10s.
And then it rebooted, entered OTA update mode again, and so on. I STUCKED AT OTA LOOP.
Methods that I've tried:
Pressed pwr+up under light for 10+ seconds - phone won't accept power button input during OTAs.
Pressed pwr+down / down only when reboot - can't enter fastboot, still OTA updating.
Connected to PC - adb devices not found, fastboot reboot recovery no response.
The current method that I figured out:
I'd like to wait until it drained out, check if charging it shows the normal charging mini kernel.
If so, try button combination into fastboot.
Guess if xda can't help, I'll have to ask for htc... : (
Unrooting the ROM doesn't work; you need full stock ROM to OTA.
But having a non-stock (unrooted) ROM will usually result in an error, and no OTA installation. So I agree this is a big weird.
29988122 said:
Pressed pwr+up under light for 10+ seconds - phone won't accept power button input during OTAs.
Click to expand...
Click to collapse
Try holding power + vol up for 30 seconds or more; even up to a minute (if there is no change). I'm not sure if updating OTA will impact this, but that button combo will force a reboot in every other situation I've seen when the screen is on.
Quick followup:
After battery depleted and complete shut off, I tried reboot to fastboot(by pushing power+down / down only)
No avail.
Even by charging only, it would immediately enter OTA.
I guess htc's OTA would write itself into bootloader, and thus I WON'T be able to enter the normal bootloader/recovery until OTA's completed.
But in my case, OTA's got error so....I got stuck at OTA loop!
The encryption key of my sdcard(adopted storage) was still inside phone's data partition....
Do I really need to give up?
: ( ....
29988122 said:
I guess htc's OTA would write itself into bootloader, and thus I WON'T be able to enter the normal bootloader/recovery until OTA's completed.
Click to expand...
Click to collapse
What is happening, is that the bootloader is designed to automatically look for an update file and install it, before it gives you the other bootloader options.
I've seen another with the similar problem. I couldn't think of anything in that case either. You really can't do much if you can't get to fastboot or delete the OTA file (and I can't think of any way you would do either of those, that hasn't already been tried).
What happens if you remove the SD card? Does it still try to install OTA?
redpoint73 said:
What is happening, is that the bootloader is designed to automatically look for an update file and install it, before it gives you the other bootloader options.
I've seen another with the similar problem. I couldn't think of anything in that case either. You really can't do much if you can't get to fastboot or delete the OTA file (and I can't think of any way you would do either of those, that hasn't already been tried).
What happens if you remove the SD card? Does it still try to install OTA?
Click to expand...
Click to collapse
Ya, still installing OTA.
Someone has told me a way to bypass OTA, somehow it worked. I'll post it here in case someone faced the same situation as I did.
1. let it do the OTA loop until power automatically shut down.
2. take out both sim and sdcard.
3. MANUALLY boot, let it auto shut down, repeat until it can only boot for few seconds or less.
4. plug in charger, check if charging mini kernel appeared or not. If not, repeat step 3.
5. it is told that the bootloader has some kind of low battery protection mechanism that it would skip OTA's under extremely low battery condition. Therefore after 30s or a little bit more charging, pull the plug(essentially shut it down), then magically you can now boot into bootloader via pwr+down.
Of course you'll wanna charge until about 30% or more, then reflash twrp and system partition... : p
Thank you xda and redpoint73, you just made my day!

XTC 2CLiP required for One Time use

I upgraded my HTC Desire 820 to Marshmallow, and now it has been restarting every few minutes and also it heats up more than before. I tried installing roms given on this forum, rooting the phone, adb sideloading roms, restoring third party backups, etc. but I have not been able to find a solution. I think s-off and then installing lollipop might save the phone.
Can anyone from Mumbai lend me an XTC2Clip and can help me to turn off the security for the phone? I am willing to pay a small fee if required.
Interestingly, while playing multimedia on the phone, the phone never hangs up and restarts even if you play for a long time.
atlas94 said:
I upgraded my HTC Desire 820 to Marshmallow, and now it has been restarting every few minutes and also it heats up more than before. I tried installing roms given on this forum, rooting the phone, adb sideloading roms, restoring third party backups, etc. but I have not been able to find a solution. I think s-off and then installing lollipop might save the phone.
Can anyone from Mumbai lend me an XTC2Clip and can help me to turn off the security for the phone? I am willing to pay a small fee if required.
Maybe help:
Interestingly, while playing multimedia on the phone, the phone never hangs up and restarts even if you play for a long time.
Click to expand...
Click to collapse
It is necessary to go to TWRP recovery: 1.turn off the phone. 2. press and hold the volume- button and the power button(the phone should go into bootloader)3.at the boot menu, select the press recovery(If you have installed TWRP recovery)4.То TWRP recovery choose Wipe,Format Data,virtual keyboard will appear,to print text Yes (to confirm Format Data in phone)
vuk1963 said:
It is necessary to go to TWRP recovery: 1.turn off the phone. 2. press and hold the volume- button and the power button(the phone should go into bootloader)3.at the boot menu, select the press recovery(If you have installed TWRP recovery)4.То TWRP recovery choose Wipe,Format Data,virtual keyboard will appear,to print text Yes (to confirm Format Data in phone)
Click to expand...
Click to collapse
I have installed TWRP recovery before installing the rom, did factory reset and wipe cache, format data, everything, but the problem still persists.
atlas94 said:
I have installed TWRP recovery before installing the rom, did factory reset and wipe cache, format data, everything, but the problem still persists.
Click to expand...
Click to collapse
Make that way !!! То TWRP recovery choose Wipe,Format Data,virtual keyboard will appear,to print text Yes (to confirm Format Data in phone)
vuk1963 said:
Make that way !!! То TWRP recovery choose Wipe,Format Data,virtual keyboard will appear,to print text Yes (to confirm Format Data in phone)
Click to expand...
Click to collapse
I did not understand.
If I format data on phone, there wont be any os on the phone, right?
What about the XTC2Clip? Will downgrading to Lollipop solve the problem?

Categories

Resources