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!
I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.
I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.
I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.
Hi all,
I once tried to update my rooted onePlus 5 (Magisk) to the latest oxygen os version, and lost everything. (with a corrupted Nandroid backup haha)
Since then, I've been pretty careful not to update anything, OTA isn't working anyway.
But now is about time to update it all.
I have flashfire, and Oxygen Updater (currently downloading OOS 5.1.4)
My question, before I go any further is:
If I download ALL the updates on Oxygen Updater and then flash them with flashfire (flash ZIP & OTA --> Select downloaded firmware --> proceed), I should be able to gradually flash all the new update until OOS 9.0.2, Keep root, and more importantly, Keep ALL my data, apps and all.
Is that correct? Does anyone have a proper flashfire walkthrough?
I'm a bit hesitant as someone seems to have had issues with Magisk as per below source's comment
source: https://forums.oneplus.com/threads/...with-flashfire-bonus-tip-oneplus-3-3t.621501/
Thanks!
To upgrade from Oreo non-treble to latest
- From TWRP, flash OxygenOS 5.1.4, Magisk and all the other mods and boot up once (to create vendor partition)
- From TWRP, flash OxygenOS 9.0.8, Magisk, all the other mods and a Pie-capable TWRP
PierreVicquery02 said:
To upgrade from Oreo non-treble to latest
- From TWRP, flash OxygenOS 5.1.4, Magisk and all the other mods and boot up once (to create vendor partition)
- From TWRP, flash OxygenOS 9.0.8, Magisk, all the other mods and a Pie-capable TWRP
Click to expand...
Click to collapse
And that will NOT erase any of my data?
Is it not possible to do it with flashfire? I don't have TWRP anymore I think..
Thanks!
mattou78400 said:
And that will NOT erase any of my data?
Is it not possible to do it with flashfire? I don't have TWRP anymore I think..
Thanks!
Click to expand...
Click to collapse
I actually don't know what flashfire is.
You will not lose data in theory, but it's a good thing to make a backup
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Tsunaimy said:
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Click to expand...
Click to collapse
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
zgfg said:
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
Click to expand...
Click to collapse
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Tsunaimy said:
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Click to expand...
Click to collapse
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read?
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
zgfg said:
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
Click to expand...
Click to collapse
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
By unlocking Xiaomi phone you won't lose anything but previous user data stored in phone, unlike ASUS phone losts OTA permanentry.
So make a backup, also I recommend you first picking your secondaly phone, not your daily using one.
Tsunaimy said:
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
Click to expand...
Click to collapse
As described, TWRP is optional, not needed for Magisk/root but it would be useful to have, so yes, install TWRP
Instructions for unlocking Bootloader say to do Backup. Copy photos and files from Internal memory to PC.
Export contacts to CVS file and also copy to PC.
Backup to Google your Google accounts, contacts, WhatsApp, etc.
Use Settings, Additional settings, Backup, and cooy to PC.
You can also use Settings, MIUI account to backup things
Installations of Magisk and TWRP will not erase data. Generally, they are not risky unless you make really stupid mistake like flashing TWRP img file to System partition instead of to Recovery partition and so - that's why you have instructions how to use Fastboot command to flash TWRP
It's more risky if you go to use e.g. MiFlash (you don't need for TWRP and Magisk), then people can screw up things and need authorized EDL support
I used Magisk to do an OTA update to Oxygen OS 12, but it feels like my root is gone because TWRP disappeared, the bootloader was locked after the update, and I had to unlock it. But when I do root check, it still says I'm rooted. Most of my Root access requiring apps don't work properly either like battery limiter and Adaway. But I check root status in Momo, and it says the environment is abnormal. Upon restart it doesn't pop up with TWRP as recovery; it goes to default OP recovery. Also, the warning at startup where it says the warning about the bootloader being unlocked is also gone, even after reunlocking my bootloader after the OTA update.
Also, slightly unrelated, but my fingerprint sensor has also stopped functioning completely. I couldn't use it to unlock my phone so I removed all fingerprint data and I tried adding it back and it wouldn't even detect my finger when I tried to add it back.
What is a true test to check if I need to wipe and reroot and install TWRP again?
How did TWRP just disappear?
Did I do the OTA wrong?
Why would my phone allow me to grant root access to root checker if I wasn't still rooted?
Would a simple fix be just reinstalling Magisk?
edit: So it seems that Adaway works, but battery limiter does not(I assume doing a fresh install of the APK might help). And my fingerprint sensor also does not work.
I am indeed rooted, but I am still wondering why TWRP just disappeared? And why does my fingerprint sensor not work at all?
I have the Oneplus 8 Pro American version.
Take a step back and read this.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
A12 is not in a good state anyway and most people use OOS11 or a custom rom.
IDK if battery limiter is a12 compatible but that does not matter.
You should NOT use TWRP with A12 and you should NOT do an OTA with magisk to a12.
What i would do now:
1. Read the thread i posted above carefully.
2. Backup all you data to a pc.
3. Backup persist image.
4. Use MSM Tool ro rollback to a clean state of OOS11.(https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
5. Flash latest A12 as local upgrade within the system updater twice (to ensure its on both slots)
6. Extract boot img with payload dumper and patch it via magisk.
7. Unlock bootloader
8. fastboot BOOT patched_boot_image.img
9. Start magisk and install
Enjoy rooted A12.
Or better simply stay on A11 its better anyway.