Hi guys.
I was on the latest MIUI OFFICIAL ROM.
So I installed the Hovac-OS ROM ->
[ROM][11][UNOFFICIAL] Havoc-OS 4.4 for Redmi 5 Plus/Note 5 (vince)
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy...
forum.xda-developers.com
This was my installation process:
1. Wipe System, Data, Dalvik, Cache.
2. Flash the ROM, GApps
3. Reboot
I restarted and everything works fine, hours later I decided to restart the phone, and then it went into bootloop.
I installed the OFFICIAL ROM again, and then I installed PIXEL EXTENDED ->
[ROM] [OFFICIAL] [11] [PIXEL EXTENDED 3.0] [VINCE] [18/08/2021]
supports dual sim/dual app?
forum.xda-developers.com
Same installation process as the previous one:
1. Wipe System, Data, Dalvik, Cache.
2. Flash the ROM
3. Reboot
As in the post.
And exactly the same error, the system starts beautifully everything works, but when i restart it bootloops again
what am I doing wrong?
Please help me.
ronaldo1337 said:
Hi guys.
I was on the latest MIUI OFFICIAL ROM.
So I installed the Hovac-OS ROM ->
[ROM][11][UNOFFICIAL] Havoc-OS 4.4 for Redmi 5 Plus/Note 5 (vince)
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy...
forum.xda-developers.com
This was my installation process:
1. Wipe System, Data, Dalvik, Cache.
2. Flash the ROM, GApps
3. Reboot
I restarted and everything works fine, hours later I decided to restart the phone, and then it went into bootloop.
I installed the OFFICIAL ROM again, and then I installed PIXEL EXTENDED ->
[ROM] [OFFICIAL] [11] [PIXEL EXTENDED 3.0] [VINCE] [18/08/2021]
supports dual sim/dual app?
forum.xda-developers.com
Same installation process as the previous one:
1. Wipe System, Data, Dalvik, Cache.
2. Flash the ROM
3. Reboot
As in the post.
And exactly the same error, the system starts beautifully everything works, but when i restart it bootloops again
what am I doing wrong?
Please help me.
Click to expand...
Click to collapse
Format your data not wipe after flashing your rom. Maybe last firmware chinese too...
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Related
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:
Does anyone else with a Verizon S4 Dev Edition have problem with no audio when installing AOSP based ROMs?
TW based ROMs seems to work fine but when I install *any* AOSP based roms it there is no sound from first boot.
Every Install follows the same procedure:
Clean to Install a New ROM
Wipe Dalvik
Install Zip (ROM)
Wipe Cache (if it says to in ROM Install Instructions)
Wipe Dalvik (if it says to in ROM Install Instructions)
Reboot For First Run (if it says to in ROM Install Instructions)
OR
Install GaApps (if needed)
Wipe Cache (if it says to in ROM Install Instructions)
Wipe Dalvik (if it says to in ROM Install Instructions)
Reboot For First Run (if it says to in ROM Install Instructions)
I'm not sure if I'm missing something. The Google Edition 4.4.4 works perfectly with no audio issues. On the other hand the fun stuff like:
SOKP
CarbonROM
Dirty Unicorns
Just has no audio from calls to Bluetooth Music.
Any Ideas?
Device:
Verizon S4 Developer Edition
Baseband: I545OYUEMJ7
Philz Touch Recovery 6.50.6
Just got a Developer Edition yesterday and have exactly this problem. Version here was I545OYUFNC5. Also using philz recovery, I was wondering if that might have something to do with it, though I was unable to get TWRP to open recovery once installed, so I'm not really sure where to go from here.
I was using Havoc OS 2.2 Pie Based Official Rom In My Mido (Redmi Note 4) Which Was Working Fine
Then I Clean Flashed The Dot OS 3.0
Followed All Steps For Flashing
Wiped Everything Except Internal Storage
After Flashing Dot OS 3.0 And Nano Gapps.
Started Getting Error Android Setup And Weather Provider Keeps Stopping.
Tried Flashing Many Times Getting Same Error
Then I Again Flashed The Havoc OS Now Getting Error Even With Havoc OS Which I Was Using Previously
Was Using Red Wolf Recovery
Now Orange Fox Recovery
Try to delete Android folder on your internal memory
Try to download latest gapps for PIE
Wipe vendor + data + system + cache + dalvik, flash rom + gapps, reboot
billouetaudrey said:
Try to delete Android folder on your internal memory
Try to download latest gapps for PIE
Wipe vendor + data + system + cache + dalvik, flash rom + gapps, reboot
Click to expand...
Click to collapse
The same problem persists with my device as well, the same redmi note 4. I installed pixel experience and then was facing some issue in the rom so thought to reinstall it and then the same problem aroused, i tried corvusOS and WaveOS but same, android setup keeps stopping. Mind it, all the roms I flashed were android 11.
Hi. I bought a Pocophone last February. Since then, the phone keeps randomly rebooting and shutting down. I have flashed EU roms, Global & Beta fastboot roms, OTA roms, custom roms etc. But the random reboot problem was persistent through out all roms.
I flashed the latest Pixel Experience CAF rom a few days ago, along with DFE and latest vendor. The phone has not been rebooting and the experience and smoothness was very good, apart from some force crashes in some apps. I flashed the EU rom after the random rebooting was stopped, thinking that may be the problem was solved in a vendor update. Sadly, the issue persists in MIUI rom. So I flashed back to PE.
Now my question is, why is my phone rebooting in MIUI? How was this solved in a PE build? Am I missing something, like a particular step, when flashing a rom? I have searched through a lot of XDA posts but can not find a proper solution. I would like to use eu versions of MIUI as I have been a Nexus and Android One user since Nexus 4 days and now crave something other than plain stock android.
Also, I bought the phone without warranty through an unofficial local store and returning the phone to Xiaomi for checking hardware defects is not possible.
The steps I follow in TWRP is usually:
1. format data, 2. reboot to recovery, 3. wipe cache, dalvik cache, system, data, 4. flash vendor, 5. flash rom, 6. flash DFE, 7. flash gapps, 8. flash magisk, 9. reboot to system
yowlzany said:
Hi. I bought a Pocophone last February. Since then, the phone keeps randomly rebooting and shutting down. I have flashed EU roms, Global & Beta fastboot roms, OTA roms, custom roms etc. But the random reboot problem was persistent through out all roms.
I flashed the latest Pixel Experience CAF rom a few days ago, along with DFE and latest vendor. The phone has not been rebooting and the experience and smoothness was very good, apart from some force crashes in some apps. I flashed the EU rom after the random rebooting was stopped, thinking that may be the problem was solved in a vendor update. Sadly, the issue persists in MIUI rom. So I flashed back to PE.
Now my question is, why is my phone rebooting in MIUI? How was this solved in a PE build? Am I missing something, like a particular step, when flashing a rom? I have searched through a lot of XDA posts but can not find a proper solution. I would like to use eu versions of MIUI as I have been a Nexus and Android One user since Nexus 4 days and now crave something other than plain stock android.
Also, I bought the phone without warranty through an unofficial local store and returning the phone to Xiaomi for checking hardware defects is not possible.
The steps I follow in TWRP is usually:
1. format data, 2. reboot to recovery, 3. wipe cache, dalvik cache, system, data, 4. flash vendor, 5. flash rom, 6. flash DFE, 7. flash gapps, 8. flash magisk, 9. reboot to system
Click to expand...
Click to collapse
If you really want a miui base I suggest following instructions on say how to install xiaomi.eu which says "FORMAT /data partition (NEVER wipe System or Persist!)"
Start of with a clean miui base installed using fastboot and after that do the following,
1.install twrp or orange fox (any that supports decryption)
2. format data
3. reboot to recovery
4. flash rom, reboot.
5. Setup device, reboot.
6. Flash magisk. Reboot
7. Never ever flash fde/fed just throw that zip in the trash.
8. Do what ever you like, miui is working for you
9. Buy me a beer.
Sent from my POCOPHONE F1 using Tapatalk
Hi!
I tried installing both the Nippon GSI version (Pixel 5) and the official Android 13 GSI on my A105FN, and no dice. Tried flashing the Eureka kernel as well, and nothing.
Also tried installing OctaviOS, then wiping System, Data, Cache, Dalvik then installing the GSI.
I've probably reinstalled the stock firmware like 15 times today, without any success.
Am I doing something wrong? Is there something I'm missing?
Here are my steps:
1. Reboot to TWRP
2. Format Data & reboot back to TWRP
3. Wipe Dalvik, Cache, Data, System
4. Flash DM Verity
4. Flash GSI (as System Image)
5. Flash Eureka kernel (tried both Enforcing and Permissive)
as from today, no more gsi thing. roms are released on telegram and sourcedorge by eureka team if anyone interested in instaibg android 13 in 2023