Hi, after installing this framework (xposed-v80-sdk22-arm64), my HTC one M8s is stuck in a boot loop. Strange detail: The startup screen, you see the moment your device turns on, is the one I only see for the recovery mode. Besides this, it starts up normal, just never reaches a normal state (or fastboot state). I installed the framework in recovery mode. I also (re)installed SuperSu beta (BETA-SuperSU-v2.56-20151030013730) but this version was allready installed, so it shouldn't have anything to do with this problem. Right now it keeps on trying to boot. Can't even shut the phone down. Plz Help!!!!
HermanBurgers said:
Hi, after installing this framework (xposed-v80-sdk22-arm64), my HTC one M8s is stuck in a boot loop. Strange detail: The startup screen, you see the moment your device turns on, is the one I only see for the recovery mode. Besides this, it starts up normal, just never reaches a normal state (or fastboot state). I installed the framework in recovery mode. I also (re)installed SuperSu beta (BETA-SuperSU-v2.56-20151030013730) but this version was allready installed, so it shouldn't have anything to do with this problem. Right now it keeps on trying to boot. Can't even shut the phone down. Plz Help!!!!
Click to expand...
Click to collapse
It is always recommended to wipe cache&dalvik from recovery after flashing Xposed. Try wiping cache&dalvik and report back. If the bootloop still occurs, grab a log file via ADB and post it in the corresponding Xposed for Lollipop thread (I assume you are using it because you use SDK22 = Android 5.1.1).
By the way, there is a newer version of the framework available: v81.
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
Hello,
So guys, I have been stuck at this for a while now, it happened when I unlocked bootloader and installed a custom recovery (TWRP) and after that I went ahead wiped the data through recovery. (Reason: I was going to install aroma file manager.) since then I cant boot into OS. Thought maybe I accidentally wiped all the data including OS but then through this link http://forum.xda-developers.com/showthread.php?t=3375203 I reinstalled the rom through that "system.img" he provided although it didn't work, my phone surely isn't bricked cause my pc recognizes it and I can boot into recovery,bootloader,download mode.
I still get stuck at the HTC LOGO.
What might be causing it, please help.
PS: Also TWRP says "No OS Installed", if anyone can find me a rom other than those he provided please do.
Jam3sgotya said:
Hello,
So guys, I have been stuck at this for a while now, it happened when I unlocked bootloader and installed a custom recovery (TWRP) and after that I went ahead wiped the data through recovery. (Reason: I was going to install aroma file manager.) since then I cant boot into OS. Thought maybe I accidentally wiped all the data including OS but then through this link http://forum.xda-developers.com/showthread.php?t=3375203 I reinstalled the rom through that "system.img" he provided although it didn't work, my phone surely isn't bricked cause my pc recognizes it and I can boot into recovery,bootloader,download mode.
I still get stuck at the HTC LOGO.
What might be causing it, please help.
PS: Also TWRP says "No OS Installed", if anyone can find me a rom other than those he provided please do.
Click to expand...
Click to collapse
Ok, so I finally managed to boot into OS but it is Chinese.. zzz and when I slide unlock my screen it gives a weird a message in Chinese and then reboots. Once it gets back into OS same thing again. What now guys?
this should help
http://forum.xda-developers.com/one-x9/development/rom-balla241-e56ml-dtul-2-17-400-1-twrp-t3497861
use this and you shall have you phone fixed
Hello, I rooted my device (HTC Desire 626g+ Dual Sim) using kingoroot, then i downloaded twrp recovery img. file from the internet, then using Rashr (an android app) i flashed the recovery in my device, then it prompted to reboot in recovery, i selected yes.
after this my phone wouldnt start it got stuck in boot process, it neither shuts down completely, nor it fully boots, it keeps on restarting till the battery drains out.
Ive tried getting into the recovery mode, fastboot mode, normal boot mode...but nothing works it still stuck in the bootloop.
When i connect it to my PC it doesnt recognises it.
Im stuck please help me out here !!
I don't think it's bootlooping, it just sits on the splash screen. I can still go to the bootloader and TWRP recovery. What's the best course of action?
I'm also seeing this behavior I think. I did:
1) ./flash-all with Android 9 factory image.
2) Reboot, turn on ADB access etc.
3) Install MagiskManager, latest version 6.0.0
4) Reboot into recovery, and install Magisk v17.2, everything seems okay.
5) Reboot system
After the reboot, it gets stuck on the Google logo and then eventually reboots into recovery...
Anyone else seeing something like this?
So I tried updating my M7 to TWRP 3.2.1-0 by flashing the img file using a slightly older version of TWRP
After installing, wiping cache & rebooting, my phone only gets to the HTC logo, with "Entering Recovery..." message at the top. It doesn't get any further than that. Even more annoying, my ADB has stopped detecting my phone so I can't flash anything else right now
Any help or advice?
Okay after leaving it alone for a while it's suddenly started to work perfectly and boot as normal again...!
Uhhh, I guess mods are free to delete/lock this thread?