After flashing the newest pre-release version of PixelExperience 13 GSI and having bluetooth stop working again I went back to the latest stable release of Pixel Experience 12 but after flashing I can't boot into system and get booted back to twrp, I have tried reflashing aswell as formatting data and erasing the system partition but every time I just get booted back to recovery, I can provide any logs needed just lmk what you need , any suggestions are appreciated.
Update: Tried flashing the pre-release version of pixel experience with the broken bluetooth again and it booted to system! Well at least it tried it's stuck in the animation and it is refusing to turn off, any suggestions?
Edit: Got it to turn off but after clearing cache its still stuck in the animation :/
Edit 2: Formatted data and it works fine now, does anyone know what I could of possibly ****ed up to cause this in the first place because I still want to roll back to last stable android 12 release as I do want bluetooth to work.
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.
Howdy.
I royally screwed up somehow and my G2 on Sprint is now soft bricked.
So here's what happened: I had been running an unofficial CM 10.2 ROM on my phone and I saw that the official nightlies were available and apparently pretty stable, so I decided to try that out. I backed up what I need and went into TWRP to wipe system and I flashed the original G2 ROM so that I could update PRL before I dove into CM 11. Well, when it booted into the stock ROM, it started to download a new update which I couldn't stop and it rebooted to install it. I figured there was no harm in that, but it turns out there was because it would not install and it was stuck at 0% for a good hour, so I decided to force it to shut down, wipe the system and re-flash the unofficial CM, but it wouldn't boot.
Everything I tried only went straight into TWRP and I have become stuck there. Well, I did the stupid thing and I advanced wiped my system and cleared the internal storage as well because I thought that might help. Now I have no backup, but it charges through the usb cable and I can ADB push files for installation. So far, all of my efforts to install and boot a ROM have not worked and I am currently in a state of TWRP limbo and can't get out.
Any suggestions as to what I can do? Thanks.
how did you solve it? I've the same problem
this way? adb sideload https://www.youtube.com/watch?v=CivvxcM1PCY
Hi there,
since I am not (yet) allowed to directly post into the developer fora I'll try my luck with this one here.
My first attempt was the installation from here. Everything worked fine but I got stuck within the cyanomod boot screen - nothing helped: No wiping with factory reset + wiping cache nor flashing twice afterwards. Also none of the tips mentioned elsewhere did work out.
Then I tried the files and installation from here. I strictly used the files for Badadroid (not the NAND-Version) but Badadroid got stuck within the XDA boot screen. After nearly 10 minutes of waiting I rebooted into recovery mode where I was presented with lots of error messages of missing files and mounts (I can retry and provide all of them). Installing the zip failed afterwards.
Now I tried boot files and FOTA from first attempt with zImage and zip of 2nd one. After flashing red output showed loadfile ERR (not found) and system did not even boot into XDA boot screen of Badadroid.
I always chose LSI + BOOT checked + Full Download checked and flashed both in combination.
Now even Bada 2.0 does not boot anymore and my Wave gets stuck in a reboot loop. After Wave startup screen only a scrambled screen is shown where nothing can be recognized! Will try to flash latest Bada Version on Phone again (while I do not know how to get the file on the phone!)!
Does anybody have a helpful hint on how to flash which combination of files in order to get a working Badadroid version with latest possible Android version?
Many thanks in advance!
Bye
Solved
Ok, finally got it to work. After reflashing a new Bada onto my no more working phone I downloaded and reinstalled everything from CM11 again.
Now Wave boots fine into both OS versions. Unfortunately CM11 seems to be little bit unstable since it often crashes for example when using the browser.
But so far it is really impressive and exciting! Thanks to all involved for that great work! Really awsome!
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!
Hi,
last week I successfully installed LineageOS as of March 15 on my OP6 and it worked perfectly.
This morning, I applied the system update to the latest version as of March 22. It took a long time to process (about 5 minutes), then rebooted as usual, but then surprisingly stuck in Crashdump mode.
After some switching off and on again with the same result, I found I still could boot into recovery by VolDown + Power (it’s the simple lineage recovery, not TWRP).
Since then, I tried several times to reinstall both Lineage versions as of 15th and 22nd the usual way, but the phone never would boot any system. The recovery works perfectly, system can be flashed by ADB sideload and reports success, but after rebooting from recovery into system, it either runs into Crashdump or back into fastboot.
Bootloader is unlocked.
I have applied the copy-partition tool to make sure there is no bad software in the other slot but that didnt help either.
I have done factory reset / format all and re-flashed Lineage (latest and older version) but same result - fastboot or Crashdump.
Any hints what I can try to get a working Lineage again?
--ks
Update: It was possible to flash OxygenOS by MsmDownload, which booted perfectly and is running through its setup procedure now. Though I prefer LineageOS by far, I won’t switch back unless I am sure this won’t happen again
Browsing a bit further through this forum, I got the impression this is quite common on OnePlus phones from OP6 on, and so might happen at random intervals even with the manufacturer’s OS. In other words, a built-in fault. I want my wonderful OP 5T back
--ks