So I decided to flash CM 10.2, following all the directions exactly. Got it to boot up once and now I can't get the "Bootloader unlocked screen."
I have tried wiping data, system, caches. Reinstalled CM 10.2 three times now. Still nothing.
Any suggestions?
Thanks
Which recovery are you using?
Resolved
Dilhrnhydramine said:
So I decided to flash CM 10.2, following all the directions exactly. Got it to boot up once and now I can't get the "Bootloader unlocked screen."
I have tried wiping data, system, caches. Reinstalled CM 10.2 three times now. Still nothing.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Pushed TWRP instead of CMW recovery and formatted, reinstalled and got it to boot. Someone else recommended getting SU app on before restarting. Second restart also took ~5 min but it did boot. All going smooth now.
Related
Tried this and rogue recovery, but I want to get up JB. So.. I used the easyoneclick and got rogue installed, then tried to flash the latest EOS4 at the time. That put me at the boot screen (4 color any boot animation) and never got any further.
So... I used the easy one click to restore stock, and that got me back to good for a few days, but still no JB.
So then I tried Goo manager and oddly enough it couldn't push the "recovery script" or what is actually twrp recovery. I was able to boot into recovery and push the GM downloaded twrp though.
So, now I have updated twrp (sort of through GM), and nightly EOS4 - but still stuck on boot animation - left it for 4 hours before I decided it wasnt' going to work. Any ideas? I was reading some about frameworks and I'm thinking that might be my problem, but I'm not finding any really good walkthroughs or advice. What can I try next? Any help greatly appreciated - Thanks!
Did you wipe the cache, Davlik, system and factory reset before flashing?
frederuco said:
Did you wipe the cache, Davlik, system and factory reset before flashing?
Click to expand...
Click to collapse
I did, but I can try again!
Bigscout79 said:
I did, but I can try again!
Click to expand...
Click to collapse
And... I'm very grateful! That seemed to work! I might not have been wiping the system.
Thanks!
Glad it is all sorted.
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
vargfloejt said:
Hi. Yesterday I succesdfully rooted my n8020 (galaxy note 10.1 LTE Swedish). Tho, when I tried to flash Sbiddens modded CM version, it failed. I wiped data/facto ry reset from CWM, wiped cache and Dalvik. Flashed CM and Gapps. Rebooted, only to get stuck at the blue-ring Cyanogenmod boot screen. Tried to redo all the steps in different orders, no succcess. Stillvstuck at boot.
Then came the puzzling part. I downloaded the original firmware from sammobile.com, and flashed it via Odin. It succeeded, bit whenbit booted in back to the standard rom, all my applications and all the data was intact! As I sevetal times wiped data/factory reset, I assumed thatevwrything would be gonw and that I'd have to install everythingnfrom scratch. Am I correct in assuming this, and may this be related to CM getting stuck at boot? Any hel greatly appreciated!
Click to expand...
Click to collapse
Bump
vargfloejt said:
Bump
Click to expand...
Click to collapse
I have seen something similar when I installed Cyanogenmod on a kindle fire, I had to do a factory reset after restoring back to stock firmware.
I would suggest that you try doing a factory reset after restoring factory firmware on your GNote.
Success with Philz recovery
Had the same problem loading onto my N8020.
In the end I used a different recovery and it worked first go.
Try using Phils recovery http://forum.xda-developers.com/showthread.php?t=2202714
I installed cyanogenmod a few days ago and it was working fine. I installed a font changing app, and it needed to reboot to work. When it tried to reboot, it got stuck on the cyanogenmod boot screen. I booted to recovery and did a factory reset, wiped dalvin cache to no avail. I found a stock Rom for my phone, but Odin doesn't seem to see it when I go into downloading mode. Am I doing something wrong? What should I do next?
Just reflash CM.
I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Narcotle said:
I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Mine did this once and what worked for me was fixing permissions.
DarkVanguard said:
Mine did this once and what worked for me was fixing permissions.
Click to expand...
Click to collapse
Tried fixing permissions before even installing any app. Rebooted, no luck. Still the same error without even a google account linked or app installed.
Narcotle said:
Do you remember which permissions exactly?
Click to expand...
Click to collapse
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
DarkVanguard said:
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
Click to expand...
Click to collapse
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Narcotle said:
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Click to expand...
Click to collapse
Try manually wiping system, data, cache, and dalvik. If that doesn't work, try a different gapps package. If it still gives the same error after that...then I don't know.
I had the same problem : I just flashed cm nighglies instead and waited for one enough stable...
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
kanjo said:
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
Click to expand...
Click to collapse
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
EDIT: Exactly which thread are you getting these instructions from? Neither of the PA threads that I'm aware of contain those instructions.
Heisenberg said:
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
Click to expand...
Click to collapse
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
kanjo said:
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
Click to expand...
Click to collapse
Just to be clear, you've wiped system, data, cache, and dalvik cache directly before flashing PA? No CM flashes since wiping all of those partitions?
Also, which thread are you getting those install instructions from? Neither of the PA threads that I'm aware of contain those instructions.
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
going to go back to twrp. wipe all data and flash PA again without gapps and without root. will report back in about 10 minutes. will flash by using TWRP and ADB sideload.
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom) at the moment i am trying to sideload PA rom after wiping data, system, cache and dalvik. is this why i am having the issue?
im dead tired so i admit i can be making mistakes though everything i have done seems to be what i am meant to do. flashed from cm11 to cm12, cleared all data, then flashed PA+gapps and root. = upgrading boot loop and errors mentioned above. tried flashing just PA and it booted with same errors, flashed gapps and errors.
all the files MD5s look good. not sure what is wrong.
--edit--
okay now i am at homescreen on PA.
when enabling/disabling adb in dev settings i get a reboot. is this normal now? does it need to reboot to mount the filesystem or something?
when it does boot after enabling adb i get "settings has stopped"
going to go to TWRP and flash GAPPS now and leave root not installed. will report back in a sec.
kanjo said:
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
Click to expand...
Click to collapse
Please define wiped all data.
kanjo said:
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom)?
Click to expand...
Click to collapse
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Heisenberg said:
Please define wiped all data.
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Click to expand...
Click to collapse
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
kanjo said:
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
Click to expand...
Click to collapse
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Heisenberg said:
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Click to expand...
Click to collapse
balls, was hoping to us PA, haven't used it since my old s3 and figured it was the rom for me again. will have to check the rom comparison spreadsheet and look into others.
right now i have sideloaded PA alone. will copy PA and gapps to the internal storage to make things easier.
but it doesnt look like it is going to work for me.
going to try it once more like you said but locally rather than through sideload. though the internal storage is deciding when it does and doesnt want to show up.
TWRP
wipe system, cache, dalvik cache, and data.
and flash them both in tandem.
and for the fun of it when it asks if i want to install root i will let it go right ahead.
maybe this time it will work. if not then its a different rom for me. sadly.
okay so now **** got retarded. TWRP has been replaced by the stock cm11 recovery and i am too pissed off to think straight and cannot remember how to get this son of a ***** rooted again let alone to flash TWRP. i dont want to use any toolkits they all seem broken as hell.
can anyone point me in the right direction because ive just about lost my **** and this phone is going to meet my fist head on very shortly...
**edit**
done. after all this i am now on cm11 stock rooted ....seriously. hours upon hours, just to get back to where i started.
man i love when things go smoothly. anyway cheers for your help @Heisenberg . n