Hello Everyone,
I own a Motorola quark XT1225 64GB indian version. I had earlier rooted it and installed Lineage OS 14.1 (Unofficial) in it. The installation was without any issues and worked for few months then one day i pressed the power button to turn on the phone and it went into a boot loop and nothing would work. i gave it to a repair shop and he installed android 6.0.1 in it and gave me back. But my phone wont connect to WIFI and later i found out that there was no IMEI or any network related information left in it. only the OS booted and nothing else was working. Even the Developer options were not available as for some reason tapping the build number was not giving any result. he refused to fix it. I tried a factory reset from the settings menu with no result. even the recovery was not available any more in the phone. I tried installing new android stock images both for android 5 and 6 first from RSD lite and fast boot mode which kept failing and then i tried it using the command promt. After installation was complete the phone rebooted and android appeared with erasing written under it but then it went into boot loop and would keep restarting every time android appeared. I tried installing TWRP recovery from the command promt the initial image of the recovery appears but then next second it says unable to mount data and keeps rebooting again and again. Kindly suggest ways to fix my OS as well as have my IMEI restored.
Really need help.
Thanks a lot.
Related
2 days ago my phone went from running perfectly to turning off and getting stuck in a boot loop, I'm assuming it had something to do with supersu updating because i noticed a popup about the binaries needing updating before the crash. I couldn't load recovery (would show team win logo then reboot) but i could load safe mode, i tried downgrading to lower versions of su ( i tried 2.13, 1.8 and 2.01) but that didn't work my phone would boot normally, i could access it for about a minute then it would reboot and do it all over again. i had originally followed this guide (URL at the bottom as i can't post links) so last night i attempted to just re do it all following the same guide. I got the recovery mode to boot and wiped the cache but i still had the same issue where i could access my phone for a minute before crashing. Now when i try to enter recovery it shows the htc logo and immediately reopens boot loader on the fast boot option. I rurally don't want to go out and buy a new phone so any help is appreciated. My current PC access is fairly limited but i can use one if i have to.
Also when i launched safe mode i noticed id get an error report after a few minutes, not sure if thats relevant but it never showed up when i booted normally.
android forums(.)com/desire-601-all-things-root/817068-root-unlock-bootlader-install-recovery-guide-htc-desire-601-zara.html
(remove the brackets)
*edit* i have tried searching for similar threads but i think i will have a better result if the replies are directed towards me directly
Thats weird. Ive never seen this issue before
Try this steps : http://forum.xda-developers.com/and...1-zaraul-s-t2893035/post56365857#post56365857
It works for me.
Hello,
Yesterday I downloaded the beta of marshmallows for my honor 7 European version PLK-L01. But, foolishly, I started the phone while pressing the volume up and volume down power button (download mode ??) and, once finished the update, the phone went bootloop, rebooting. Then I tried to do a reset from recovery and install the rom stock (b100), but without success as the phone continued to go bootloop. So this morning I decided to unlock the bootloader and let the phone into fastboot mode; then with Huawei extractor tool, I extracted the various image file from stock rom to flash them via fastboot and the program Minimal fastboot to ADB. I flashed the various image files (system, boot, recovery, etc.) but only the three image files listed first and with another 2-3, the process has been successful. So I restarted the phone and it worked. But there a problem, in fact, before starting the system the phone will restart 4-5 times; also no longer recognizes the boot-sim and gives me the error that the program system stopped working. Can someone help me ??? I'd be eternally grateful
Matthew
Hello!
I'm one of the folks who did OTA update on my Motorola Moto E (1st gen) and after that the phone became unusable due to lacking internal space. After that my phone started to restart randomly on daily basis (according to other posts it was caused by almost no free internal memory).
I was so tired of not being able to install apps that I decided to root my phone, I've never done it before but somehow I managed to root it, unlock the bootloader, install twrp, su and then downgraded my phone to 4.4.4, I'm not sure but most likely from there:
https://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
Anyway it's been working perfectly fine but the phone was still reseting itself (which was odd, having over 500 MB of free internal memory). About 4 months passed by and I'm unable to turn on the phone, it's stuck on logo. Pressing power and volume down gives me access to factory and recovery options but factory worked only once and now doesn't work and when I try to do recovery I'm getting red triangle with Android robot on his back.
How do I fix that? Recovery is unusable. I've got https://dl.twrp.me/condor/twrp-2.7.1.0-condor.img, did
HTML:
fastboot boot recovery-twrp.img
but still recovery doesn't work.
Any hints?
[edit]
I managed to install twrp using "fastboot flash recovery recovery-twrp.img", installed latest Linage OS from official thread on our forums, did everything as in: https://www.youtube.com/watch?v=9esNxdH8-eA and I was stuck on loading screen (blue swiping dot along a curved line), but after like 10 minutes the OS finally booted. Not sure what caused my problems, but they seem to be resolved.
[edit 2]
The OS reseted itself right after booting. I guess I might have some hardware issue after all Can I somehow find out what's the state of my internal memory? I think it might be corrupted. Damn.
So I got myself a cheap TF201 tablet and decided to put Android 7.1 on it using this guide. I followed the instructions completely and everything went perfectly well.
Had TWRP 3.2.3.0 installed, Android 7.1 installed and it was working great. Rebooted a few times, set up my Google account in Android, started installing a few usual apps such as Chrome, etc. when suddenly the Pad completely locked up. It then rebooted and went straight to the TWRP logo screen, sat there for 10-20 seconds then rebooted. And now that is all it does - ASUS screen comes up for a couple of seconds with "This device is unlocked" in the upper left, then tries to go into recovery but it reboots instead.
I cannot access fastboot mode at all - holding PWR + Vol DN does nothing. I can access APX mode and I can briefly use ADB while the TWRP is up.
I have backups of all blobs and I have nvflash installed - I got through the whole guide step by step without a single problem.
Any help would be hugely appreciated!
I got quite the same issue here, I also flashed 7.1.2 yesterday and installed some stuff. Then today I wanted to install Magisk to root it. After the installation (I can't remember that it was successful but I think it wasn't because there was no Magisk app to find) I wanted to boot another time to the recovery and went into a bootloop. When I'm trying to boot to TWRP it stucks at the teamwin logo. Sadly I have no cable here at the moment to maybe reflash the recovery or try some other stuff.
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Whether it can enter REC？
cyclo111 said:
My wifes Pixel 6 was recently updated to Android 13. From what I can gather the update was not sucessful - The process got stuck on the 'G' screen with the scrolling bar undernath for several hours before my wife gave up and forced the phone to reboot. She has since managed to perform a factory reset from recovery mode but the phone constantly reboots during the android setup screens. I'm now in posession of her phone to try and fix the issue mysef, however recovery and rescue modes both display the 'no command' screen.
I have tried to reflash a stock rom using ADB but this does not work as 'OEM unlocking' is not enabled, nor can it be enabled as the OS refuses to load all the way before a random reboot occurs.
I'm really hoping someone can tell me how to get around the device lock so I can flash this thing!
Thanks
Click to expand...
Click to collapse
You can try sideloading the full OTA. That doesn't require an unlocked bootloader.