Related
My Xperia ZL won't allow me to install a custom ROM.
Here are the steps I've taken.
1. Updated to 10.6.... (Lollipop fw) via Flashtool
2. Boots correctly, everything seems to work.
3. Flashed boot.img from Paranoid Android and went into TWRP to flash the ROM zip (wiped cache, system and data before).
Did step 3 to test the same for OmniRom too.
4. Phone boots, shows Bootanimation, shows Optimizing apps, then hangs after finish and does step 4 again.
Please help me, I could install custom ROMs on the device before, suddenly it does not work anymore.
Note: EVERYTHING works fine with Stock. Flashed stock ftf multiple times and tried these steps.
Thanks for your help
It seems to be a Bootloop. Try below steps;
1. Through TWRP wipe (system+cache+dalvic cache+data+android secure)
2. Install ROM.zip
3. Wipe cache+dalvic cache+data
4. Reboot
Hope the above steps helps you
Regards,
hitman-xda
@hitman-xda I've tried these steps, except for android secure.
What is that partition and what does it do?
Cannot find it in Advanced Wipe of TWRP.
Thanks
It is the mysterious part. Actually no one knows about it. Some says, it contains secured links/data of some apps.
If you are clean flashing ROM, that's means you have to wipe everything except storage part. That's the reason I mentioned it.
If you can't find it, just leave it
@hitman-xda So I've already done what you suggested, with no luck.
Guess I'm stuck on stock till someone helps me
Thanks for your reply
did you install de correct kernel?
maybe you should wipe everything, install the correct kernel and after that, install the custom ROM
i don't now if it will work, but at least try
I did fastboot flash boot boot.img (got it from ROM zip)
Then erased everything and flashed ROM.
No luck
Does that Paranoid Android was built for your phone?
Your phone loops from 'optimizing apps' , that means your phone is unable to load dalvic/art for the apps.
Also check weather PA ROM can be flashed over lollipop, if not then you have to downgrade an then try the same procedure.
Also you can download stock kernel with recovery, flash it and then directly try to flash your respective ROM.
Usually ROM.zip contains kernel and get flashed during installation of zip, just the thing is they can be flashable over some selective android versions.
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes
Wow, that is poor. You aren't having this problem with stock OS?
Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
I have the same problem
Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank
Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.
So i rooted my phone sometimes ago, and it worked fine at first but after some reboots it is now stuck at Redmi logo and would boot to fastboot mode after a while. Now i want to share my experience so people can be more careful, i may be a newbie but i do want to help people too.
So here's what my phone is using, CorvusOS 7.0 and SiLonT kernel and no more modifications other than that. Now i have read stuff online that some people have experienced bootloops and some can't boot to the OS they rooted their device with magisk. I have also read that dirty flash may solve the problem. But if you're already facing this problem maybe you can try these methods below:
Method 1: probably the easiest one, wipe the Dalvik and the cache
1. Reboot to your custom recovery
2. Go to advanced wipe (location and UI may differs between custom recoveries)
3. Simply tick Dalvik and cache and untick anything else
4. Reboot
Method 2: uninstalling magisk (this will unroot your device)
1. Download magisk uninstaller.zip (if you didn't downloaded it already from the start. Also make sure the uninstaller is the same version as your magisk version, idk what will happen if you do it with a different version but just in case )
2. Reboot to your custom recovery
3. And simply just flash/install the magisk uninstaller.zip, this will delete all magisk's files
4. Wipe Dalvik and cache (just in case)
5. Reboot
Method 3: dirty flash (for custom ROMs)
1. Uninstall magisk (follow method 2)
2. Get/download your custom ROM you are using (make sure it's the same ROM and version as the ROM you're using rn)
3. Flash it without wiping anything
4. Wipe Dalvik and cache (just in case, again)
5. Reboot
Method 4: reinstall/install your ROM, for custom ROMs users (I'm sorry i am not experienced with XiaomiFlashTool so i can't tell you how to flash stock ROM)
1. Backup all data cause this will erase all your data
2. Reboot to recovery
3. Uninstall magisk (follow method 2)
4. Wipe system, data, cache, Dalvik (the usual stuff you would wipe before installing a custom a ROM)
5. Install your chosen ROM
6. Wipe Dalvik and cache (just in case)
7. Reboot
If those methods above doesn't work you can try searching a tutorial on flashing the stock ROM on the internet, but if you still didn't manage to get your phone boot to the OS again then i am sorry to say that you have to take your phone to the nearest repair center.
So, what's the cause of this problem?
Well, it's simple, every human make mistakes, At least once. So it is normal to make mistakes. The developers are humans too so it is normal for them to make mistakes too, so instead blaming them we should support them and give them advice. But on the other side you may did a mistake too, probably a similar mistake that i did. Like maybe you did something wrong according to the tutorial, or you flashed an incompatible version of magisk, and etc. So from now on always ask if it's compatible, whether it's about magisk versions, ROM compatibility, kernel compatibility, recovery compatibility, and etc. And always double check just in case.
If i did something wrong tell me down below and I'll fix it as soon as possible.
Peace.
One quick little note: i fixed my device by doing a dirty flash (method 3) just to let you know
Edit: Phone won't boot after uninstalling magisk*, that was supposed to be title. Sorry I just realized sometimes ago
This happens to me all the time when flashing Android 11 ROMS. Curiously this doesn't happen when flashing Android 10 ROMs. I also never had this issue with TWRP, only OrangeFox.
But it could be other things too. For example, Xiaomi.eu 12.5 always go into a bootloop here, and trying to go back to any other ROM after flashing it leads to a boot loop. The fix is to flash disabled vbmeta if you're flashing xiaomi.eu 12.5. That might be the fix for A11 roms too but I never tried.
More than once it happened to me too that no matter what I did the phone would be stuck in bootloops with any ROM, any recovery. In that case, flashing stock rom via fastboot fixed the issue.