Related
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
BigBoy275 said:
Anyone else have problems flashing to a 4.3 ROM? (I know some people do because I've searched.)
No matter what ROM it is, if it is 4.3 it will always fail to reboot a second time after it has been flashed.
Currently on CleanROM ACE 4.9 (4.1.2) with TWRP 2.6.0.1
I've tried to go to CM10.2 and it would reboot initially but then hang on the Note II logo if I tried to reboot.
I've tried to go to Paranoid Android.. same thing.
I've tried to go to PAC-man.. same thing.
I've tried flashing from the stock 4.1.2 ROM and the same thing happens.
I've followed every instruction I could find including this: http://forum.xda-developers.com/showthread.php?t=2423057
I do a factory reset, format data, flash ROM, wipe caches, flash gapps, wipe caches, reboot. It will boot fine from TWRP and load everything normally. Then, if I reboot or power off the device, it will hang on the Note II screen and I have to nandroid back to my previous ROM.
Any insight as to why this is happening? I haven't been able to find anything besides some random instructions for wiping/flashing (which I've linked). These ROMs look great and I'd really like to move to 4.3, but I cannot figure out what the problem is.
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note 2 I605, or coming from another ROM:
- Read known issues ans FAQs
- Flash the latest official ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
read the OP for CM 10.2 next time....
First - clockworkmod not twrp for 4.3 usually fixes things
Second - do a factory reset AFTER installing
Third - Dont restore apps with TiBu going to 4.3
Next time be truthful when you say you read and searched.
Hi All,
after about 8 months of purchase my first smartphone, I decided to go to the modding with the Resurrection Remix Westcrip. In recent updates I have several problems:
1) Unfortunaly, com.androidsistemui the process has stopped. I tried to reinstall the ROM and Gapps Light-I checked again the warning. This time the message after pressing the ok button is gone and the phone is not locked but I did do an update to the patch Google service and I believe that we have solved the problem but after going on settings, about phone and having looked at the version of the Resurrection Remix is the previous version. Why?
2) Settings / Tools Resurrection / Resurrection Remix Update / Install App and I understand this (see photo of the screenshots).
I solved the first point .. but what can you tell me about the screenshots I posted?
with the installation of the latest release I have the same problem again. Why?
Hi all,
I have updated to version 5.0.8 and RR reboot gets me off the window with words com.androidsistemui has stopped.
I've tried using the GS2ROMNuke but the result has not changed the same window, I tried to make several times a Deep Clean but nothing to make the problem remained. I wanted to download the firmware for the Italian Jelly Bean XWLS and I reinstalled using Odin. Once this is done, I installed the latest version of the RR and restart interlock no window. But is it possible that every time I have to upgrade to the latest version I have to start again from the Jelly Bean using Odin and then repeat the procedure for installing the updated RR? Could someone kindly explain why? Thanks in advance.
lucasscott2872 said:
Hi all,
I have updated to version 5.0.8 and RR reboot gets me off the window with words com.androidsistemui has stopped.
I've tried using the GS2ROMNuke but the result has not changed the same window, I tried to make several times a Deep Clean but nothing to make the problem remained. I wanted to download the firmware for the Italian Jelly Bean XWLS and I reinstalled using Odin. Once this is done, I installed the latest version of the RR and restart interlock no window. But is it possible that every time I have to upgrade to the latest version I have to start again from the Jelly Bean using Odin and then repeat the procedure for installing the updated RR? Could someone kindly explain why? Thanks in advance.
Click to expand...
Click to collapse
Did you flash RR 5.0.8 on top of stock 4.1.2?
lucasscott2872 said:
Hi all,
I have updated to version 5.0.8 and RR reboot gets me off the window with words com.androidsistemui has stopped.
I've tried using the GS2ROMNuke but the result has not changed the same window, I tried to make several times a Deep Clean but nothing to make the problem remained. I wanted to download the firmware for the Italian Jelly Bean XWLS and I reinstalled using Odin. Once this is done, I installed the latest version of the RR and restart interlock no window. But is it possible that every time I have to upgrade to the latest version I have to start again from the Jelly Bean using Odin and then repeat the procedure for installing the updated RR? Could someone kindly explain why? Thanks in advance.
Click to expand...
Click to collapse
when i update my RR rom to 5.0.8 from 5.0.7 i will gt the same com.androidsistemui has stopped....
but if i do clean installation(wipe data)....those com.androidsistemui working fine.....
i believe that is RR rom update issue...hope they will fix it soon...
April 24, 2014
"Due to continuous com.android.sistemui has stopped I decided to abandon the Resurrection Remix and install a new Rom. I chose the MIUI and I can tell you that I do not hateful window is checked .. It 'was great to be of your .. shame because I liked so much this Rom"
Today
The saying that it is said that the first love you never forget it ... I went back to the RR with version 5.1.2 and I was happy because that hateful com.android.sistemui window has stopped no longer appeared even with version 5.1 .3
But when I decided to upgrade to version 5.1.4 variants 20140602 and 20140603 my worst nightmare has reappeared. As in the Changelog there is no record regarding the installation I did not do any full wipe.
How do I have to do?
Looks like whenever you update, a clean install is not happening. When you tried gs2romnuke, did you also flash gs2romwipe?
I will update when I have the Rom I always look before the Changelog to see if there is any directive then step to install the Rom behaving accordingly:
If required a full wipe / wipe :
I go into Recovery Mode
I make wide data, wipe cache, advanced> Dalvik Cache
Mount and Storage> Format System
Flash Rom
Flash Gapps
Reboot
If you do not need a full wipe / wipe :
I go into Recovery Mode
Flash Rom and / or Gapps (in practice only what is updated)
I make Wipe Cache
I make Dalvik Cache
Reboot
Something wrong?
------ April 03, 2014---------
I updated to the latest version of the problem is repeated .... I made a GS2Nuke but to no avail .... I tried again to start from the Samsung Custom Rom and then upgrade to the latest version but nothing to make me appear more com . androidsistemui has stopped ...... I'm pissed off .. someone could help me?
-------April 04, 2014---------------------
I downloaded the firmware XWLS and I installed it by performing a "Deep Clean". Then I reinstalled the RR (as if for the first time) and odious window does not appeared to me .. I hope now to enjoy the RR
And 'it possible that with each update I have to start from scratch by installing the version of Jb then move on to the latest version of RR?
---------------April 24, 2014-----------------------
Due to continuous com.android.sistemui has stopped I decided to abandon the Resurrection Remix and install a new Rom. I chose the MIUI and I can tell you that I do not hateful window is checked .. It 'was great to be of your .. shame because I liked so much this Rom
I don't think it was rom's problem. There are a lot of happy users, including me.
Can't blame rom just coz we can't pinpoint the issue.
Some time ago I tried the GS2RomNuke not getting the expected results ........ at this time in desperation I tried it with GS2RomWipe and it seems that everything has gone for good ...... I'm restarting .... at the first reboot is coming out the window .. I'm trying again with another restart .... this time no window ...
I do not want to denigrate this Rom. However, or the fault of the ROM or my Samsung does not own the digests. But do you think it is possible?
Did you try nuke and wipe scripts at separate flashes?
I read it in the op of that thread that flash nuke first, then wipe script and then the rom.
I have difficulty understanding what you're telling me ... Could you tell me in detail the steps to be carried out? Thanks in advance..
Your post gave me an understanding that you flashed nuke script once and then the rom. When that didn't work out,next time, you tried wipe script and then the rom. However the correct process would be..
1. Nuke script
2. Wipe script
3. Rom
Wipe script would be the set of wipe data / factory reset, wipe cache and wipe Dalvik cache?
I wanted to ask one more thing and covers the proper way to flash a rom.Te I ask because I have come to doubt ... I knew that this was the order of execution to start with a clean (full wipe) :
Get into Recovery Mode
Perform wipe data / factory reset, wipe cache and advanced> Wipe Dalvik Cache
Mount and Storage> Format System
Flash Rom
Flash Gapps
reboot
Then a moderator Italian guide told me that this was incorrect and that I should do so:
Get into Recovery Mode
wipe cache, wipe Dalvik, wipe data (factory reset) with this order
install rom
install gapps
wipe cache, wipe Dalvik
reboot
I'm confused ......
I don't remember exactly what else the wipe scripts wipes apart from the things you mentioned. Still it's better to follow the op written by the script creator. You can open those scripts with notepad and check.
About the order of wipes you got from the Italian guy, I am not very sure. My wipes are usually in random order and I never had unclean flash problems.
Thank you guys for trying to help me .... but after the shock announcement of the team to abandon the development Resurrection Remix I hope that with the search for a new Rom is more lucky ...
Carry the shock announcement:
This is it!
Resurrection Remix v5.1.5 will be last version in Resurrection Remix Kitkat ROM series. It will be android 4.4.2 based ROM. This last version is our way of saying goodbye and bidding farewell to an amazing journey we had with everyone.
Resurrection Remix team is thankful to all its users, supporters, fans and contributors for making Resurrection Remix such a successful aftermarket custom android ROM.
:crying::crying::crying::crying:
Hi;
So i recently installed CyanogenMod 13.0 on to my Samsung S4 GT-I9505 using the first download link on:
https://download.cyanogenmod.org/?device=jfltexx --> cm-13.0-20160102-NIGHTLY-jfltexx.zip
That all installed fine, but i wanted to get the Google apps installed aswell, which is where i am having some issues.
I have been trying to install the following package:
http://opengapps.org/?api=6.0&variant=nano
but have also tried to install quite a few others as well, and all have exactly the same issue. Basically after the apps have been installed and i boot the device up, i get various error messages like:
unfortunately, Setup Wizard has stopped
unfortunately, google play services has stopped
Any help on fixing this would be much appreciated, as nothing seems to download from the play store thats included in Cyanogen, they just say "your download will begin shortly" but never does.
Thanks in advance
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
audacityandrouge said:
I am a total noob, but I had exactly this problem. The issue appears to be that you have to flash gapps *before* rebooting after flashing CM. In my case since I had already flashed CM before I flashed gapps I had to put the gapps file on the phone (I did this by push with adb, you might find an easier way), re-flash CM, wipe cache/dalvik, flash gapps, wipe cache/dalvik, reboot. It worked.
The easiest guide I found was on androiding.how, called "how to install cm13 (cyanogenmod13)." (The forum won't let me post a link, just google it, it should come up).
Hope that helps. I'm on a galaxy s5 and used twrp recovery if that matters.
Click to expand...
Click to collapse
Thanks for the reply, i gave that a try and it seems to be stuck on a loop now with "installing app # of 22" . it completes the installation and then reboots, after about 5 minutes on the Cyanogen boot screen, it goes back to installing apps again.
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
audacityandrouge said:
Hm, did you do a factory reset in your recovery before re-flashing CM and gapps? If not, that might be necessary.
Click to expand...
Click to collapse
Yeah, i did. Tried it multiple times now
That's about the limit of my ability right there, hopefully someone with more experience than me can point you in the right direction. Good luck.
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
es0tericcha0s said:
Boot to recovery (preferably TWRP)
Wipe cache / dalvik cache / data / system
Flash CM13 and the gapps you were trying first
Reboot
Profit!
Since you keep flashing different gapps on top of the system, this is probably causing some issues. Once you fully wipe and reflash everything, it should work.
Click to expand...
Click to collapse
Ive tried that multiple times using twrp (i always wipe everything before i flash CM13 and gapps), i still get the exact same issue. The second the phone boots, i get all these "unfortunately ******** has stopped".
Perhaps try installing 12.1 with gapps, get it all updated then upgrade to 13. I did the accidental upgrade to 13 but have had no issues whatsoever.
I had Unofficial 5.1.1 installed on my Samsung Galaxy S3 GT-i9300. I updated my device via CM Updater to CM13 6.0.1 Marshmallow. After updating, I am getting an error Google Play services has stopped, unfortunately. I cannot access any Google App.
I've flashed the GApps through OpenGapps. But after flashing GApps, phone stucks on Bootloop. I've tried many variants (pico, nano, stock) but none of them worked. I am still stucked at boot screen.
HELP!
zackygaurav said:
I had Unofficial 5.1.1 installed on my Samsung Galaxy S3 GT-i9300. I updated my device via CM Updater to CM13 6.0.1 Marshmallow. After updating, I am getting an error Google Play services has stopped, unfortunately. I cannot access any Google App.
I've flashed the GApps through OpenGapps. But after flashing GApps, phone stucks on Bootloop. I've tried many variants (pico, nano, stock) but none of them worked. I am still stucked at boot screen.
HELP!
Click to expand...
Click to collapse
Definitely Gapps problem.
1) Backup your data.
2) clean install Marshmallow rom (wipe data/ factory reset & install)
3) look for the correct Gapps (slim zero Gapps work for me)
You might know, but just telling - make sure the Gapps is for Android 6.0
P.S: don't panic and flash several things at once. Maybe you haven't clean flashed the CM 13, that might be the reason.
Clean flash 13.0 and don't boot yet after and go back to recovery, instead flash gapps immediately after flashing the rom. If you dont then you're going to have a bad time. Hope I helped
Done. Flash CWM and Boom
Thank You @sashankps. Slim Zero Gapps worked for me.
What I did?
1. Installed CWM Recovery.
2. Wiped everything.
3. Installed CM 13 (6.0.1)
4. Flashed Slim Zero Gapps.
5. Done.
PS: For future readers, please note that do not wipe cache/data after installing Gapps. After finishing above steps directly Reboot your system.
zackygaurav said:
Thank You @sashankps. Slim Zero Gapps worked for me.
What I did?
1. Installed CWM Recovery.
2. Wiped everything.
3. Installed CM 13 (6.0.1)
4. Flashed Slim Zero Gapps.
5. Done.
PS: For future readers, please note that do not wipe cache/data after installing Gapps. After finishing above steps directly Reboot your system.
Click to expand...
Click to collapse
Glad it helped.
I was a CWM recovery user myself, but the development is static, I would suggest you move on to TWRP - chances of you encountering flashing problems is less.
Next Time.
sashankps said:
Glad it helped.
I was a CWM recovery user myself, but the development is static, I would suggest you move on to TWRP - chances of you encountering flashing problems is less.
Click to expand...
Click to collapse
I don't like the UI of TWRP but Next time I'll surely try TWRP. Maybe while flashing Android N
Thanks a lot! Reply via Samsung Galaxy S3 running 6.0.1
So this is my first post, but whatever.
So it's safe to say I screwed up, I accidentally deleted my stock (rooted) Samsung OS. I somehow managed to download Paranoid Android 6.0.1 onto the Samsung Galaxy S3 GT-I9300 I received. I heavily dislike Paranoid Android, and I would like to give Cyanogen 14.1 a shot. The problem is since I wiped everything, every time I do a factory reset for my device, it goes into a bootloop, even if I flashed CM 14.1.
I have TWRP installed, if that helps, and all files (that I know of) are installed on my computer (Odin, CM14.1 ZIP, and Paranoid is backed up).
I'd like to thank everyone who even comes and reads this thread, and I'd be very grateful if I managed to get CM 14.1 on the Samsung Galaxy S3 GT-I9300.
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Hi bro
I am agree with the first reply to you.
All You need the official CM14.1 ROM
Download here https://download.cyanogenmod.org/?device=i9300
And then download Gapps for android 7.1 pico
Download here http://opengapps.org/
If yoy havn't twrp recovery ! Download it from here
https://dl.twrp.me/i9300/
The file end with (tar) it flashing with Odin.
And the file end with (img) it is update from other version to new with Flashify app (you can find the app in playstore free)
Now You have all requirements files
Let's flashing Your device:
Move the files to Ext.sdcard
Make sure you have 80% battery charge
Then reboot your device to (recovery mode)
Turn off your device and Push (Power+home+volume up) keys at the same time for 5 sec untill u see the recovery icon
Now go to wipe your phone choose advance wipe check the dalvilk + cache + system + data + inernal storage ,, done
Now go back and choose install
Search to your Ext.sdcard then choose the CM14.1 at the same time click on Add more zips
And choose Gapps 7.1 pico
Now swipe to flash
Wait to flash finish and then click on Reboot system
Done
Good luck
audit13 said:
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Click to expand...
Click to collapse
I'm using the latest TWRP, I made sure to install the latest one, and I'm performing a full data and system wipe before I install CM14.1. My question is does it HAVE to be on an external SD card, because I just port it over to a folder in my internal SD card.
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
audit13 said:
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
Click to expand...
Click to collapse
I've tried to do that multiple times, but everytime I try it, the S3 goes into a bootloop.
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
audit13 said:
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
Click to expand...
Click to collapse
Yeah, I managed to install the stock OS. I also tried to install CM14.1 again, following the instructions to the letter, but still no CM build. I have no idea what I'm doing wrong, since I've read multiple threads on XDA and the CM site.
Not exactly sure what you mean by in download mode, since I'm new to all this rooting business.
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
audit13 said:
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
Click to expand...
Click to collapse
Oh if that's the case, then yes. I put it in Odin mode to flash the stock ROM.
Okay, just to confirm but these are the major steps you took:
flashed the latest stock ROM to the phone;
flashed the latest tar version of TWRP using Odin;
booted into TWRP and copied CM14 to the internal memory or an SD card;
wipe data, system, and cache in TWRP;
flash CM14 in TWRP and rebooted.
Yup, those are the exact steps I took. I think I'm just going to tinker around with the Samsung a little longer, until I manage to brick it, or I'll just continue doing research. I'm already happy I managed to get out of a boot loop on my own, with and without OS.
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
audit13 said:
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
Click to expand...
Click to collapse
My dad got it for his work during his visit in Turkey, is that a factor during flashing of new OS's? What surprises me is that I could install Paranoid Android 6.0.1 onto it without an OS with little or no problem.
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
audit13 said:
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
Click to expand...
Click to collapse
I made sure it was for the i9300. I'm confused to where it doesn't work because I would see the CM battery charging logo, but when I wanted it to boot, it kept bootlooping for 10 minutes on end. The longest I've let it run was whilst I was sleeping, 8 hours, still nothing.
Maybe try a different version of CM14.1 or a different version of TWRP.
audit13 said:
Maybe try a different version of CM14.1 or a different version of TWRP.
Click to expand...
Click to collapse
I'll give those options a shot. I'll try out clockwork and see. I guess I'll keep going until I brick it. Thanks for aiding me, and enjoy having a happy new year.