Hi Folks,
i want to update von archidroid 2.1.4.1 to 2.5.1. my problem is, the installer stucks on 8,00%. so i wipe dalvik/cache and do a factory reset but the problem still exists.
i also letting me time to click "next" on the installation settings.
My CWM version is v5.5.0.4 :: CF-v1.5.
Any Ideas?
EDIT: Problem solved after writing the thread -_- ... i tried it this time to dont change any standart settings during the installtion settings.
hello,
i never posted here before but i am following this site for a while and flashed lots of roms using the data here.
i got into a problem trying to flash the kitkat on my HTC sensation 4G.
i am using ATM the android 4.2.2 CM 10.1 albinoman887 rom.
i tried installing the android 4.4.1 according the instructions posted by android1234567 here:
http://forum.xda-developers.com/showthread.php?t=2530073
i did factory factory reset, cache wipe, and davlik wipe
after that flashed the Kernel Aroma installer, the rom and the gapps from this link.
after i flashed them i rebooted and the phone doesnt pass the reboot screen, got stuck on it for few seconds and then restart and stuck again.
could anyone help me resolve this?
thanks ahead.
Dan
ok
if mean bootloop then again do the same step but wipe the dalvik cache,data,cache means clean your phone and then install the rom u will out of boot loop
tried it, it didnt work, still bootlooping.
when i install the gapps file it says it detects 4.4 rom.
any other ideas?
thanks for the help
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, I have problem with "com.android.systemui has stopped" everytime when I flashed RR ROM since Aroma installer. Please I need help, I use p760 v20o baseband and Arthas Recovery. I tryed wipe and format everything and it still doing FC.
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