Related
Hi guys,
So I have a lot of data problems with Nougat roms (7.0 and 7.1.1).
CM based roms don't work for me, no data at all.
Last week I tried CitrusCaf 3.0 and my data worked a day then disappeared...
So I tried CitrusCaf 2.2 and it worked great until a few hours ago, I rebooted on TWRP didn't flash or do anything then rebooted the system and no data ....
I backed up and tried fix contexts, still no data.
I am on TWRP 3.0.2-2.
Do you think TWRP did something? Is it possible? Can we fix it?
I got the same problem, but only in 7.1.1 roms. If the roms were 7.1.0 or lower, data was working fine. I tried several firmwares and nothing. Only in cm based roms.
I have my problem fixed now. I have flashed a miui rom with miflash via edl(my bootloader was locked), and applied to official bootloader unlock.
I already got the official unlock, and I tried cm 7.1.1 and data works.
So I just need to grab a rom from here https://forum.xda-developers.com/redmi-note-3/how-to/links-direct-official-download-links-t3449488, reboot into edl, flash with Miflash and reboot then fastboot twrp, rom, gapps....
My bootloader is already officialy unlocked.
Well, at least it worked for me. You can try. If your bootloader is unlocked, you don't need to go from edl. You can do it from fastboot. You might need to flash firmware after coming from miui.
Hi all,
After a few years with the O+1 here I am with the O+5 and I'm pretty happy with it !
But after a few days I already miss the root functionnality...
Could you please tell me what is my best option to get root and still pass Safety Net (yes I still play Pokemon Go) ?
I heard Magisk is my best option but it has been a long time since my last flash so I would really like some confirmations about real users like you guys !
PS: Can I flash the Magisk thing on OxygenOS right after unlocked the bootloader or do I need some extra steps like a custom recovery (TWRP ?) or anything else ?
Thanks !
I think you need TWRP first off all. Just flash TWRP recovery img via ADB. Once in TWRP move the stable version of Magisk( v14) to TWRP from PC. Flash Magisk in TWRP reboot device and your good to go.
Or do it my "complicated" way LoL:
1. Install TWRP via Fastboot/ADB
2. Wipe all and format data
3. Reboot in TWRP recovery
4. Move the "full" latest flashable stock OOS to TWRP via PC (can be found and downloaded from official OP5 site or here on XDA)
5. Move latest stable Magisk v14 to TWRP
6. Flash Firmware along with Magisk
7. When you finish the Tap and Go settings, reboot again to recovery
8. "Maybe" the TWRP recovery is replaced by stock recovery due to flashing official OOS
9. Just simply flash TWRP again via Fastboot ADB and Magisk and than you are "definitely" good to go!
I flashed xxxNo Limits ROM and used magisk and safety net is working
Use freedom os.
Freedom OS is much better xXx has too many bugs. Dont think the guy tuned anything
I tried Freedom and xXx No Limits and I prefer stock OOS with a custom kernel (Blu Spark) to either of them. I did read that there was a way to flash Magisk and keep the stock recovery (which allows you to install OTAs normally) but I didn't really understand it. Blu Spark TWRP actually works better than the official build and is updated far more often. I would recommend running stock with a good custom kernel for a little while before flashing a custom ROM. A lot of people flash a custom ROM as soon as they get the phone so they have no way to even judge if the ROM they are on performs as well as stock OOS. In terms of just performance I haven't found anything so far that beats stock OOS with the Blu Spark kernel.
Thanks for all replies !
I came from Resurection Remix on a O+1 but I want to give a try to OOS so I will only unlock the bootloader + flash TWRP + flash Magisk
I will see in a few weeks if I miss some functionnalities and need to flash a custom ROM
just flash magisk on top of OOS and install the magisk manager app, bypass safetynet and have root
Good morning all,
I tried 2 days ago to upgrade to Oreo and since then all my troubles began.
I have unlocked bootloader and encrypted device.
The problem is that in every reboot a stock recovery shows up ,while i have installed the latest blue spark or any other recovery.
Now i can only install stock rom with no root.
kimon60 said:
Good morning all,
I tried 2 days ago to upgrade to Oreo and since then all my troubles began.
I have unlocked bootloader and encrypted device.
The problem is that in every reboot a stock recovery shows up ,while i have installed the latest blue spark or any other recovery.
Now i can only install stock rom with no root.
Click to expand...
Click to collapse
Are you going for root? I think you have to flash Magisk (or other root-solution) in order for your custom recovery to stick.
Augustin79 said:
Are you going for root? I think you have to flash Magisk (or other root-solution) in order for your custom recovery to stick.
Click to expand...
Click to collapse
In Nougat that was not the case,maybe in Oreo there is something different?
I'm having a similar problem! I'm rooted, unlocked, and decrypted but I can't seem to install any Oreo Rom. Do I need to re-encrypt my rom??
WIMP35 said:
I'm having a similar problem! I'm rooted, unlocked, and decrypted but I can't seem to install any Oreo Rom. Do I need to re-encrypt my rom??
Click to expand...
Click to collapse
No, I managed to load the latest twrp recovery and without reboot I installed the xXx rom Oreo.
After that there was an App installed already called TWRP recovery. Since I flashed the recovery again through that app the problem is gone.
Now I have Oreo xXx rom and everything works fine.
After fastboot flash recovery, reboot into recovery and flash recovery IMG again. Then it will be there regardless of what ROM encrypted or not.
Hey, so I wanted to install a custom ROM (LineageOS 14.1) anyway, I found this site that was showing me how to but first i needed to unlock bootloader and install TWRP, i clicked on the steps for that and it brought me here:
https://devsjournal.com/how-to-root...to_unlock_Bootloader_of_Motorola_Moto_G4_Plus
I followed all the steps on that page, even installing the SuperSU, but this is where the problem began. After rebooting from installing SuperSU i was stuck on a black screen (not even backlight) and a white blinking LED light next to the fingerprint scanner. I began to look around for a fix and i found this site:
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
I followed the steps but nothing worked. Then i tried this:
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
but that still didn't work. Flashing a new ROM does not fix the problem, and it seems nothing will. I am able to get into the bootloader and I am also still able to get into TWRP but i can't boot into ROM. I need help.
I should have attached this before but here is a picture of the bootloader. After typing in all those command the only thing that changed was the yellow text that says Software status: Modified
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
echo92 said:
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
Click to expand...
Click to collapse
Yea i should have been more clear on what ROM i was trying to flash, i wanted to flash LineageOS but when i try to flash it and boot i still get the same problem, the led light just blinks over and over until i unplug the phone or go into the bootloader. Maybe i have the wrong version of something? All i know is that the phone was working perfectly fine before and it is the XT1644 model. It had all its updates up to date but i just wanted to install LineageOS, i do now realize that you don't need root to flash a custom ROM but also i don't know where to find files for the kernel you are talking about, I also did not make a backup (lets just say im pretty stupid and i know i should have). If you have any info or need any more to further assist me, let me know. Thank you for responding!
So i tried flashing the custom kernel and it looked like everything was working, but the phone still won't boot, it just flashes the LED light, also i reinstalled LineageOS after wiping all the cache and internal storage and stuff but it still hasn't worked.
Hey, i got good news, i was able to get the phone to boot by downloading and following these steps here: https://forum.xda-developers.com/mo...e-npj25-93-t3549369/post70843323#post70843323
The phone now is working and i will attempt to install LineageOS once more. Thank you for you help!
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
TheDarkLord098 said:
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Click to expand...
Click to collapse
IMO, if you want to update by "choose update package'", you should be also on stock recovery, not TWRP (but I'm not using eu weekly ROMs)
TheDarkLord098 said:
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Click to expand...
Click to collapse
You use "xiaomi.eu" custom ROM ; saying "Europe" could be confused with Official EEA ROM. ^^
You can use the Updater app in this custom ROM and update/flash ROM updates.
You don't say if you use Magisk or not. Magisk could be the raison of your issue after flashing new ROM version.