Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
You don't need to enable debugging, its just that latest cm12.1 build is broken, I just reflashed myself because of that systemui crash, you need to reflash too. You can use version with date 2015-04-16, and then update from the phone using cm integrated updater to version 2015-05-11, because version 2015-05-13 is broken.
Same thing happened to me this morning after I flashed the Nightly of 2015-05-13. I downloaded the Nightly with CyanDelta to reduce the download size and flashed in thorough recovery. After my device booted, I noticed my wallpaper changed and I kept getting "Unfortunately, SystemUI has stopped" error. But it kept showing up every 1-2 seconds making the device unusable. So I just flashed the Nightly of 2015-05-12 which was working and the error stopped showing. Thanks to CyanDelta that keeps a copy of the old Nightly after installing a new one.
I hope that you still have the "stable" Nightly on your device to roll back to the previous Nightly. If you have access to a computer, you might be able to download it directly from CM's website, transfer it thorough USB and flash it with Recovery. That would be the only solution I can come up with beside restoring a NANdroid Backup. But I'm no pro in Android stuff, maybe someone can come up with another solution.
ExcaliburUser said:
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
Click to expand...
Click to collapse
Thanks for the info bro. :good:
Related
Hi guys,
I've tried installing CM9 from this post (With OpenGL latest version). For some reason, the status bar is not there! The same thing happened with flashing CM7 and another version of CM9. When I return to rooted stock, the status bar is back. Help????
Also, a popup comes up very very very often that says the process com.android.media has stopped working. Again, this has happened with CM7 and the other CM9 release too. This is prbly because all of the roms I was flashing were update-xxxxxx.zip.
If anyone could just link to a complete 4.0 install that wipes your apps (as opposed to an update), that would be greatly appreciated too.
Thanks,
Mathew
Mkirsch72 said:
Hi guys,
I've tried installing CM9 from this post (With OpenGL latest version). For some reason, the status bar is not there! The same thing happened with flashing CM7 and another version of CM9. When I return to rooted stock, the status bar is back. Help????
Also, a popup comes up very very very often that says the process com.android.media has stopped working. Again, this has happened with CM7 and the other CM9 release too. This is prbly because all of the roms I was flashing were update-xxxxxx.zip.
If anyone could just link to a complete 4.0 install that wipes your apps (as opposed to an update), that would be greatly appreciated too.
Thanks,
Mathew
Click to expand...
Click to collapse
The update- does not mean it is not wiping system for you, because it does. That is just a generic name. But no ROM installer wipes your installed apps, or your system app settings. The only way to do that is with a factory reset. The problems you are having probably indicates you should do one. Back up your installed apps and data by doing a backup with Titanium Backup. Then you can restore them after the reset.
Hi friends, as you all know, the cm10.1 rc2 has just been released. I installed mine through the ROM manager premium app. After downloading the rom, there are options for me to choose such as wipe data and backup, i checked both and hit the install button. After the android recovery screen started up everything went smoothly. Once my N7 booted up, a message showed up saying that Setup wizard stopped. I then return its state to stock unlocked and then root again. After installing rom manager and installing again, i had the same problem. So far anyone has the same problem as me? Thanks for taking the time to look at this thread and answers will be appreciated.
you dont have gapps insstalled: download and install from here: http://goo.im/gapps
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon
I have ZUK Z1 and two days back i moved to latest CM 13 nightly. After CM 13 update my device is restarting frequently. Additionally, when i call my phone starts and when someone calls me it starts. At this stage i cant use the phone. I need to revert to stock CM 12.1.
I have downloaded stock CM 12.1 from Cyngn website. ABD and fastboot detects the phone. However, when i try to run first command "fastboot flash modem NON-HLOS.bin" i get a response as "waiting for device. I am stuck at this stage and need help to revert to CM 12.1..
Appreciate you assistance.
mahesm said:
I have ZUK Z1 and two days back i moved to latest CM 13 nightly. After CM 13 update my device is restarting frequently. Additionally, when i call my phone starts and when someone calls me it starts. At this stage i cant use the phone. I need to revert to stock CM 12.1.
I have downloaded stock CM 12.1 from Cyngn website. ABD and fastboot detects the phone. However, when i try to run first command "fastboot flash modem NON-HLOS.bin" i get a response as "waiting for device. I am stuck at this stage and need help to revert to CM 12.1..
Appreciate you assistance.
Click to expand...
Click to collapse
Consider this thread closed. I have fixed the issue and device is back on CM 12.1 .
mahesm said:
Consider this thread closed. I have fixed the issue and device is back on CM 12.1 .
Click to expand...
Click to collapse
dude,can you please tell me how to revert back to cm 12.1 stock zuk z1?
I have the same problems,first i install cm13 like a month ago,but now the fingerprint doesn't work..then i try to update to the latest cm13 nightly 20160523 but after updating my phone start to reboot and reboot again always "optimizing apps.." again and again,can't make it to the system..my computer won't recognized the phone since it won't boot up to the system,i really confused now,please help..
edit :
finally managed to revert back to 12.1 YOG4PAS3OH found the signed zip file,but unfortunately my fingerprint still not working...ups,try again..i wonder if this is the hardware problem?
Galon123 said:
dude,can you please tell me how to revert back to cm 12.1 stock zuk z1?
I have the same problems,first i install cm13 like a month ago,but now the fingerprint doesn't work..then i try to update to the latest cm13 nightly 20160523 but after updating my phone start to reboot and reboot again always "optimizing apps.." again and again,can't make it to the system..my computer won't recognized the phone since it won't boot up to the system,i really confused now,please help..
edit :
finally managed to revert back to 12.1 YOG4PAS3OH found the signed zip file,but unfortunately my fingerprint still not working...ups,try again..i wonder if this is the hardware problem?
Click to expand...
Click to collapse
I am using YOG4PAS3OH signed copy and it FP scanner works. It cloud be hardware issue.
mahesm said:
I am using YOG4PAS3OH signed copy and it FP scanner works. It cloud be hardware issue.
Click to expand...
Click to collapse
I try that YOG4PAS3OH and it's a clean flash from cm13 but not working,then I update to YOG4PAS7DF and do a factory reset after that,but still not working,when I add new fingerprint it said try again and nothing happens,but sometimes it says great,youre almost there,just few more times,keep go on and so on,and the phone just vibrating like crazy for almost a minute before the setting app force close...
yeah..looks like it's a hardware problem..
Kindly instruct me the complete guide of reverting back to stock. I installed cm13 but it have some issues.
Please provide me the link of stock rom of zuk z1...please its very urgent... I will b very thankful
Galon123 said:
dude,can you please tell me how to revert back to cm 12.1 stock zuk z1?
I have the same problems,first i install cm13 like a month ago,but now the fingerprint doesn't work..then i try to update to the latest cm13 nightly 20160523 but after updating my phone start to reboot and reboot again always "optimizing apps.." again and again,can't make it to the system..my computer won't recognized the phone since it won't boot up to the system,i really confused now,please help..
edit :
finally managed to revert back to 12.1 YOG4PAS3OH found the signed zip file,but unfortunately my fingerprint still not working...ups,try again..i wonder if this is the hardware problem?
Click to expand...
Click to collapse
yes same is happening to my zuk z1
its an hardware issue try to repair/replace it
---------- Post added at 04:37 AM ---------- Previous post was at 04:34 AM ----------
ank1705 said:
Please provide me the link of stock rom of zuk z1...please its very urgent... I will b very thankful
Click to expand...
Click to collapse
Official Cyanogen Recovery - http://goo.gl/awGr8O
Cyanogen OS 12.1 official firmware - https://cyngn.com/support
flash the official firmware with twrp recovery
then flash official cynogen recovery from pc
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
jam1445 said:
Kindly instruct me the complete guide of reverting back to stock. I installed cm13 but it have some issues.
Click to expand...
Click to collapse
https://youtu.be/261NdvyULeU
I can solve any problem as long as it's software problem.
I will connect your PC with remote connection and fix your phone.
And I will charge for it.
If you are interested, email me!
Email : [email protected]
Guys it's really simple...which ever rom you guys use...when you want to get back to stock...just simply the phone has to be rooted first..and you need to have the twrp for simple work...when the device is rooted, just install the twrp from play store, and grant it root access.. Through that flash twrp recovery., Download the 12.1 from cyanogen support for your DEVICE, there will be alot of devices over there..and remember..when you want to flash it through twrp, you need to download the middle zip file, which doesn't include fast boot in it's name...the fast boot file is when you get back through fast boot/bootloader... But let's keep it simple and commands free.. download that file and flash it. And your device will be stock. And you may have a doubt that the device will be rooted and the recovery will be twrp but no.. Everything changes including recovery., Device will be unrooted too. Hope this is helpful.
Hello Guys,
pls help me.. after flashing cm13 RR ... when i m installing watsapp .. bootloop occurs.. camera 360 as well, i flashed stock fimware and the flashed cm13 rr ..but no luck
same problem
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
DarudeNotSandstorm said:
I have pretty much the same issue but it's not exclusive to whatsapp, other apps send the phone into a bootloop as well, this started a while ago, I installed the cm12 last year or so and it worked great for a long time, then after a while I tried to install the spotify app and things went south, phone went into bootloop so I deleted it from recovery mode and just ignored the issue. Yesterday I installed the cm13 hoping I would get a clean slate, I did everything right, full wipe, flashed the rom, gapps, patch and front cam fix and although everything kept crashing at first ( google launcher and pixel launcher) I eventually got it working, I installed messenger, worked fine, then tried to install whatsapp and it went into a bootloop. Anyone please help us.
Click to expand...
Click to collapse
exactly.. we were on same page .. pls any one help us
I have the same issue on CM12. Phone get stuck in boot-loop after installing whatsapp latest version. I was able to get out of boot-loop after I deleted whatsapp app.
Its very important to use whatsapp. Please any fix for this?
I couldn't find a fix. The best you can do move to nougat ROMs like aicp or crdroid.
I installed crdroid and it's excellent
I too am now stuck on boot loop due to Whatsapp.
I do not need this app and will happily delete it, if this is what is causing the issues, but my problem is, how do I delete it now that I am stuck in a boot loop?
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
GalaxyNote2_ said:
Enter safe mode and delete the app.
It's better to remove cm12 and install new ROM crdriod
Click to expand...
Click to collapse
Thanks for the reply.
This may sound a bit noob, but how do I get it into safe mode?
I have an Xperia Mini Pro SK17i
I managed to get it into recovery mode earlier, but cannot seem to get into safe mode
Yeah!
It happens in 5.1 / 6 custom roms!
Can any body help ??!!!
You need to read this thread. Every CM rom compiled before 2018 will have this problem.
https://forum.xda-developers.com/showpost.php?p=75391884&postcount=18