My Issue:
No Simcard is found and the Wifi setting wont even show up any Wifi, only the loading bar. When i wait a few minutes my OP3 reboots and the rest works untill in reboots again after a few minutes.
My Story:
Yesterday i updated to 3.2.6 with magisk, phh systemless root and systemless xposed and everything went fine.
Today i did a backup (all partitions) and did a full wipe (except storage) and then flashed Resurrection Remix. I cant tell if the issue was already occuring at this time but i did a full wipe (except the internal storage partition, everything) again and recovered my backup. Definitely since then i am nolonger able to use my phone. I tried wiping everything (now even with storage) and flashing pure stock OOS (3.2.6) but nothing changed.
I am very desperate and dont know whats going on and how to fix it. Thanks to everyone who can help.
when you say you did a backup, exactly which partitions did you backup?
when you say full wipe, exactly which partitions did you wipe?
when you say then flashed OOS, exactly which version did you flash? And have you ever flashed the OOS CB 3.5.2?
Thanks for your fast answere i hope you can save my ass.
I went to Advanced wipe and selected everything except internal storage at the first time and the second time when i tried to clean flash oxygen os i wiped everything you can find there to be sure.
My Backup and the Clean Oxygen OS zip are both 3.2.6
In my Backup every partition is backed up except Cache.
No i never installed any CB.
Additional info: it was the unofficial [OxygenCam] Ressurection Remix and i did not flash Gapps over RR.
regardless of what you did, a clean flash should work if you're wiping /system + /data and then flashing a TWRP flashable version of OOS (since it includes gapps)
regarding RR, it probably requires gapps, but i could be wrong as i haven't used it (i know gapps were needed for sultan's CM which I used, for example)
2x4 said:
regardless of what you did, a clean flash should work if you're wiping /system + /data and then flashing a TWRP flashable version of OOS (since it includes gapps)
regarding RR, it probably requires gapps, but i could be wrong as i haven't used it (i know gapps were needed for sultan's CM which I used, for example)
Click to expand...
Click to collapse
Yes but my problem is that i wiped data and system a second time and tried flashing the clean 3.2.6 and after that in the first boot setup guide kinda thing it begins with my issue of no sim wifand random reboot, i my try with 3.2.4 now (sounds more stable)
Is there a downloadlink for full rom 3.2.4 at the op homepage?
I clean flashed oos 3.2.4 like you said but still the same error...
It seems like my efs is broken, i have no imei number anymore
Hi All!
First of all i would like to state i'm not a noob at all. I have tried clearing cache, dalvik, format system > full OOS zip > SuperSu > Reboot ? Xposed arm64 zip.
But for the life of me, i am not able to get it working. I'm using the alpha 4 app from original thread and it still shows xposed framework not installed. What step am i missing in TWRP during flashing the zip?
Again, i am using the xposed zip from the original thread for arm64 system.
I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.
extrem101 said:
I do it pretty much the same and had no problems so far. As TWRP I use the official: twrp-3.0.2-1-oneplus3
-flash full rom
-flash supersu (some beta-supersu-forced-systemless.zip file which is properly not the newest)
-flash xposed-v86-sdk23-arm64.zip
-wipe caches
-reboot
After the reboot I already get the update news from the market about supersu where I update to the lastest Version.
Click to expand...
Click to collapse
I am using the same recovery and the exact same zip file but i have no idea what the issue is. Are you also on OOS?
Yes OOS 3.2.7
Strange that it doesn't work on some devices like this. Unfortunately I don't know what you can make different.
Did you try to explicitely mount system in TWRP before flashing xposed?
groshnack said:
Did you try to explicitely mount system in TWRP before flashing xposed?
Click to expand...
Click to collapse
I haven't done this. But i can try after work hours and let you know once done.
I only had problems once with Xposed not working after a dirty ROM update (and then flashing Xposed). Clean install fixed that and since then I had no issues, doing very similar procedure as described above - I'm not even rebooting in between:
- wipe system, cache, dalvik, sometimes data
- flash ROM (FreedomOS, but that's still OOS)
- flash SuperSU (latest)
- flash kernel
- flash Xposed
- reboot
And it works ?
Sent from my OnePlus 3 using Tapatalk
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.
abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.
msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.
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.
Hi XDA!
I want to install this ROM: https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/
I did all the necessary steps:
Copy the ZIP onto my SD card
Boot into TWRP (already installed)
Wipe -> Advanced Wipe -> I wiped Dalvik/ART Cache, Cache, Data
Install -> select LineageOS ZIP
After install I went to Wipe -> Format Data
After data format I rebooted into system
After all these steps it just boots into recovery. I also tried with NikGapps, but that gave me error 255 when formatting Data so I will NOT install any GApps (I also don't need them).
What am I doing wrong here? I have already flashed LineageOS on my Redmi Note 7, so these steps should work.
Thanks for any help
Hackris said:
Hi XDA!
I want to install this ROM: https://forum.xda-developers.com/t/rom-unofficial-10-0-gauguin-lineageos-17-1.4224633/
I did all the necessary steps:
Copy the ZIP onto my SD card
Boot into TWRP (already installed)
Wipe -> Advanced Wipe -> I wiped Dalvik/ART Cache, Cache, Data
Install -> select LineageOS ZIP
After install I went to Wipe -> Format Data
After data format I rebooted into system
After all these steps it just boots into recovery. I also tried with NikGapps, but that gave me error 255 when formatting Data so I will NOT install any GApps (I also don't need them).
What am I doing wrong here? I have already flashed LineageOS on my Redmi Note 7, so these steps should work.
Thanks for any help
Click to expand...
Click to collapse
This rom requires you to be on android 10 stock MIUI firmware
Either flash that first or if you want to remain on stock MIUI android 11 firmware choose a different custom rom that is based on Android 11 stock firmware
Note an android 11 custom rom can still be based on stock MIUI android 10 firmware/vendor so don't get confused!
Read the first post fully and it will tell you what firmware is required
And if you want gapps I would use open gapps nano version
TheFixItMan said:
This rom requires you to be on android 10 stock MIUI firmware
Either flash that first or if you want to remain on stock MIUI android 11 firmware choose a different custom rom that is based on Android 11 stock firmware
Note an android 11 custom rom can still be based on stock MIUI android 10 firmware/vendor so don't get confused!
Read the first post fully and it will tell you what firmware is required
And if you want gapps I would use open gapps nano version
Click to expand...
Click to collapse
Thank you very much!