Hi, I've rooted and had a custom recovery on my MotoG. It was on 5.0.2 (still is) and since it keeps bugging me about updating to 5.1 I decided to give it a go.
Obviously that wasn't going to work and well it kept rebooting. So I got the MotoToolAioV3, got my USB debugging on and well tried to flash the stock recovery (JellyBean). I got a few lines of text and everything seemed fine. Then I decided to boot and download the update. Once downloaded it told me it would need to reboot and it might take 30 minutes for everything to be done. So I let it do it's thing and after about 5 minutes my phone was booted again. And then it began it's endless cycle of rebooting.
So since that wasn't quite what I had in mind I tried to go into my recovery again (I think I wiped my cache last time that happened), but instead of going into recovery it just booted into well normal boot. I tried flashing a custom twrp2.6.3.3 recovery and from there on I don't remember what I exactly did anymore. I flashed both the normal and the custom rom a couple of times and every time I tried to enter the recovery it would just boot normally. Also my phone is still on 5.0.2. But the endless rebooting has stopped and the phone seems to be working like before any fiddling with it today. Except that I can't go into my recovery anymore since it'll just boot.
Anyone know how I can get into my recovery and how what I should do to get to 5.1?
Related
Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
Every 30 seconds or so, right as the phone seems to be fully loaded, I get the powering down message and it reboots. Every time like clock work.
Tries booting into recovery but every time I select Recovery from Fastboot it just does a normal boot.
I am rooted and haven't installed the newest OTA yet.
Sounds like a hardware problem. I suggest to take it to a Verizon store.
My guess is that the OTA update got pushed to your phone and you inadvertently took it, which is causing a boot loop.
There's no recovery if you rooted; the phone just boots with read/write access.
Look at the HouseOfMoto thread for info on flashing back to stock (images for 12.15.15 are now available), then re-root.
I'm still on 12.7.7 so it shouldn't be the OTA
Yes it should/would. You don't have a recovery, therefore you CAN'T upgrade, which is the reason you are still on older firmware
Sent from Droid Maxx
rmoney said:
Every 30 seconds or so, right as the phone seems to be fully loaded, I get the powering down message and it reboots. Every time like clock work.
Tries booting into recovery but every time I select Recovery from Fastboot it just does a normal boot.
I am rooted and haven't installed the newest OTA yet.
Click to expand...
Click to collapse
The same thing happens to me, have you found a solution?
Dudes,
I was running CM 0701 nightly fine and decided to boot to CWM-based recovery and flash latest nightly from 0703. It got about 2/3 the way through updating apps after boot and froze. Then screen stayed black, but would backlight. Was unresponsive to touch, but I could get it to take screenshots (at least I could hear the sound made by triggering one). I longpressed the power button to force reboot and entered bootloader. Finally I could see the screen again. I thought all was better and it just needed a reboot so I reboot again and let it boot. Still no screen. So I longpressed to reboot, got into bootloader, then revovery... and tryed to reflash nightly from 0701 but it won't access my "/sdcard" because it won't mount. Same error ("Error mounting /data!) when I try to fatory reset or mount/unmount.
WTH?!
Anybody have any ideas what broke this? What it a change in last two nightlies? A change to the recovery?
I'm going to try http://forum.xda-developers.com/google-nexus-5/help/help-e-mount-sdcard-cwm-6-0-4-5-trying-t2802715 when I get home... in way too many hours. Sadface.
I also posted this in CM Forums: http://forum.cyanogenmod.com/topic/...cant-mount-data-after-0703-nightly-boot-fail/
Firstly try and fastboot flash a stock cache.img
rootSU said:
Firstly try and fastboot flash a stock cache.img
Click to expand...
Click to collapse
Thanks @rootSU. Ultimately and unexpectedly the phone came back to life before I could get to a computer with adb access. I had tried rebooting several times before, but magically after about 6 hours of downtime (no charge or anything) it rebooted up fine. It was a little shaky and slow at first, and ran the update apps process again on the next boot but has since be stable. No flashing. A couple reboots. All fine.
Thanks to the XDA community for existing and providing such a reassuring resource for knowledge and problem solving!
Hi, last week my phone started behaving very weird, out of nothing the phone freeze and stopped working and reboots itself and then got stuck on the boot logo, I tried to go to recovery via bootloader, but it didn't work, I tried everythging but it the only thing useful was connecting it to the pc and wiping cache via fastboot. This happened like 3 times a day. Now I have reflashed the stock firmware, installed some apps, xposed and other things, and when my device was ready, started behaving the same way like before, I don't know what to do now. please help.
Im using retail us 4.4.3 firmare.
this never happened with 4.4.2, is there any way to downgrade?
I followed this guide to restore stock firm: http://forum.xda-developers.com/showthread.php?t=2542219
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!