Clean Flash Marshmallow ROMs - stuck at "Android is starting... Starting apps"
Hi,
I just performed a clean flash of some of the Marshmallow ROMs and my stock unlocked 16GB maguro didn't take micro-gapps, had to flash only nano gapps. After flashing all the files, the device boots up and performs the 'optimizing apps x of x' but gets stuck at the starting apps. It doesn't go beyond that step even after a couple of hours.
I've tried the following ROMs
CM 13
zzpianoman 6.0.1 ROM
werty100 6.0.1 ROM
Can some one help me with this?
P.S. I have checked the thread here -http://forum.xda-developers.com/galaxy-nexus/help/stuck-android-upgrading-starting-apps-t2825113 and it didn't help
Thanks!
Related
Hi,
I was on the paranoid 4.4.4 rom on my I9300, everything worked fine.
I did the last update with paranoid 5.1.1 but it didn't worked well, i have multiple error and Google service won't work anymore.
The thing is, i can't do anything at all, like restore my last backup because i lost the root access with the update.
I can't load in recovery mode, i tried the HOME+VOLUME DOWN (or up) + POWER, it won't work.
I can't fine the debug mode on this version, so i really don't know how i can at least restore my last backup to go back to the 4.4.4 version.
Any help is appreciated, thaks for your time.
Root doesn't ship with any 5.x build of paranoid android. To reset you need to boot into recovery and restore your backup or flash a different ROM.
You don't need root access for that.
It sounds like you installed an incompatible gapps....
Thanks for your reply,
I managed to boot in recovery, using a method i found on the web, i pull the battery then hold the combination keys when i put it back, and it load in recovery just fine.
I think i couldn't install the proper gapps because i was in clockwork recovery, i installed the latest TWRP, but i still can't manage to install the latest paranoid rom prpoperly.
here's what i did so far:
- wipe all/ factory reset , install Paranoid5.1.1 + Gapps 5.1 mini => paranoid load but Black screen once it's loaded with the message "Android.phone interrupted" (gross traduction) popping every 2 sec, it disapear if i put the phone on airplane mode => make me think the Google service can't connect.
- Restore my last 4.4.4 backup then => wipe cache/dalvik=>install Paranoid 5.1.1 + gapps => same as the previous problem, but this time i have my old app and i can call and receive sms.
My guess so far is a problem with the Google service who can't synchronize, the Gapps i try to use are the pa_gapps-modular-pico-5.1-20150315-signed.zip
Any guess ?
Yeah. The problem is you are using old gapps. Use banks gapps
I had trouble with a clean install of PA 5.1 + Gapps on my S3 (i9300) and similar issues to yours, not sure why but I found that if I used th full fat "Stock" 5.1 Gapps the phone was fine and has been for a day or 2 now, the pico/mini/full seemed to be problematic (at least for me). Also moved to Philz Recovery using the "Rashr" app as my old CWM kept throwing an error of status 6 on any Gapps I downloaded... Must admit though that once stable PA Lollipop runs well on the S3 and battery seems better over the past couple of days too...
As title says when I flash or install a recovered LG based rom the handset gets into a bootloop. Lollipop or MM doesn't matter.
I see the BIOS type of screen for a few seconds then 3 seconds of boot animation and back to BIOS.
Cyanogenmod 13 based roms work just fine.
background: After receiving MM ota update rooted and downgraded to lollipop. Installed a modem file in the process as well.
Then I decided that I don't like it either. FLashed cyanogenmod straightaway.
Then flashed genesys rom which is LG based 6.0.1.
Still no problems.
Installed xposed framework and the bootloops started.
Then I run the xposed uninstall script, wipe everything and install LG MM rom. bootloop again.
Sorry for the long post. Didn't know which detail is relevant so wrote it all
Any help would be much appreciated as I am stuck with cyanogen...
Try to go back to stock with lgup
lgup doesn't recognize the handset when CM is installed.
Anyway finally found a solution after trying every trick in the book. Basically flashing modem, boot and bootloader solved the problem.
Now I need to find a way to flash xposed framework without bricking the phone.
Hi,
I'm completely new to customROMs at all, so please bear with me..
So, first I tried to flash Cyanogenmod 13 nightly on my G3 which failed with "system partition has unexpected contents after ota update". At this point I was unable to get past the "LG powered by Android" boot screen, but I figured that was okay, since the install failed. I was running Android 5.0 beforehand and after a quick Google search I decided to try CM 12.1 first.
So I started again with wiping the device and installing CM 12.1 which succeeded. However, I still couldn't get past the LG boot screen. I tried wiping and reinstalling CM 12.1 several times with no success.
I was following the official guide rooting my phone and using LG G3 AutoRec-Lollipop to install TWRP.
I don't really care about my data (it's all in the cloud anyway), but I'd like to get my phone to work again. Any ideas?
Thanks in advance!
what's your current twrp version?
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
Until now I used a LOS 14.1 with GApps and I decided now to upgrade to lineage-17.1-20200530-nightly-m8d-signed.zip by flashing TWRP 3.3.1-0 and install the rom afterwards.
Everything worked fine except of problems with SD card (Failed to initialize).
But after a several reboots my device got stuck in a bootloop I don't know what has gone wrong - I just have installed apps and customized some settings.
This problem also occurs every time I recover a backup with TWRP.
I did some trials with:
- Flashing 10 different recovery images from TWRP 2.8.1-0 to 3.3.1-0
- Installed Lineage 16.0 and 17.1. Could not find any downloads for 14.1!?
I have also tried installing multiple mokee builds: Same behavior! And other users have similar problems with their devices. So this does not belong to m8d devices only and also not only to lineage but maybe to AOSP!?
I have flashed only TWRP and lineage - not the firmware. And i have exactly done formating as described in the installing-instructions: Formating and wiping system and cache. But additionally I have tried many variants.
I'm not an expert, but I have a look in the dmesg.log and did not find anything interesting.
I have compared a log of a new and fresh installed LOS 17.1 (with NO bootloop) with a damaged (bootloop) LOS.
Info:
I've noticed a repeating and very quied sound like "knock, knock" while got stock in bootlop..!?
---
Now I have installed crDroidAndroid-9.0-20190315-m8d-v5.2 and this works well (e.g. recovering backups) except of smaller issues (as i found so far):
- can't get screen rotation working
---
What I don't understand:
Lineage 16 (based on Android 9) fails, but crDroid (based on Android 9, too) works!?
Is this a matter of a too old firmware? Can't find a new one for my S-ON device:
- modelid: 0P6B64000
- cidnum: HTC__102
Thanks,
Marco
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
raisonier said:
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
Click to expand...
Click to collapse
That TWRP is only for M8_Eye and not for regular M8 or M8 dual sim.
Which one do you have?