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.
Related
So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.
Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,
So im trying to root my oneplus 5 and i started off by using Lineage OS but i wasnt too happy with it and i liked Oxygen OS much better so i decided to go back to it and while doing so like an idiot i wiped everything in twrp including the storage with all my ROM files and the phone was bricked and after a long struggle i used the unbrick tool which is called MSM tool which installed oxygen 4.5.8 using some some Qualcomm mode or something and it booted and worked fine but ever since i wasnt able to download the oxygen 5.1.1 update through the phones update section, it reaches 100% and says signature verification failed and goes back to 5%. So i tried downloading the latest Open Beta from the OP site and tried local upgrade which said installation failed so i try installing it locally through the Oxygen Recovery but again Installation failed so i try unlocking the bootloader again and installing it through twrp and it just keeps showing the boot animation forever( i know people say be patient but i waited for 20 mins+). So i decided to use the unbrick tool again and now im stuck on the OOS 4.5.8 unable to update the phone.
I tried to flash the latest oreo through twrp several times and just tried flashing it through so many ways where none worked , even adb sideloading it worked till 47% and said installation failed and everytime this happens i have nothing left to do but use the tool and unbrick it again and this takes so much time as i have to unbrick and then do the first setup and then go to fastboot and unlock the bootloader and do the setup again and transfer the files and then install twrp and flash.
Nothing has worked so far
And now even when i go back to the 4.5.8 stock after unbricking for some reason it just doesnt connect to any wifi , it just says Connecting and then saved and then disabled and repeat, only my mobile data works.
I tried to flash lineage again but got an error 7 with it or something and im back to the stock unbricked state without wifi and all i can do is unlock bootloader and install twrp.
If anybody has any suggestions and can help me please do so immediately. I require my phone urgently and need to fix this fast.
Thank You !
(btw im in India and do local service centres fix such issues?)
Make sure you use newest twrp. And also flash firmware for 5.1.1
Vika__ said:
Make sure you use newest twrp. And also flash firmware for 5.1.1
Click to expand...
Click to collapse
i am using the latest codeworkx twrp 3.2.1 and when should i flash firmware? can you just give the process i should do? stuck at 4.5.8 without wifi with twrp and unlocked bootloader
Wipe everything except internal storage, after that click format data and type "yes" to accept. Then download oos 5.1.0 firmware from here https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/firmware/ and lineageos 15 (or any rom you want now), gapps and move all 3 packages to your phone. Flash firmware first and then reboot to recovery. Then flash rom or gapps and reboot
You have to flash the latest TWRP from twrp.me, then download the latest OxygenOS build. Reboot into TWRP, wipe data, cache, system and flash the latest build, then just go to wipe > format data, type "yes" and reboot
Lol man your OP5 is not bricked, if you can boot on TWRP, you can install all that you want
I advise to Format Data/Storage, Wipe everything and install xXx 10.7 (OOS Custom with a great Aroma installer), choose decrypted, it's better if you want swtich rom in the future AOSP > OOS > AOSP
bro i have same probleme after install any rom custom or official , always stuck on boot logo , any solution ?
no solution??
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 all,
So I am new to the game, I had an old(ish) phone and attempted to root the device. As some of you might have read on here before, I failed, I thought I had followed all the correct steps. I used the following steps as a guide: (from the unlockr). After attempting to install supersu I was left with a black screen. I can however access my recovery mode in bootloader, the thing is that bootloader is the only thing I can access. I cannot access my moto g4 plus via USB on windows, but for some reason I can access both internal and external memory on a mac. I can see the supersu version, my TWRP etc. I was wondering if someone could help me out, I know this has probably been posted before but I have not been able to find a possible solution as of yet. Thanks in advance
Is your device running stock Nougat (7.0) firmware? If so, then attempting to root on the stock Nougat Motorola kernel may result in a black screen and failure to boot, which appears to be what you've experienced. What those guides generally fail to mention (as they're quite old) is that rooting on the G4/Plus running Nougat requires flashing a custom kernel before you root. Failure to do so appears to trip the anti-rooting measures built into the stock kernel. A more recent guide that I've used for a stable root on a G4 Plus is this https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Bear in mind you do not need root to flash custom ROMs whatsoever, just TWRP.
If you can still access TWRP, you may have a way out. One thing to try is to flash a custom kernel onto your device - ElementalX is a good choice. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX v2.0.1 for stock . Download the kernel to your computer, ensure your device is connected to your computer and booted to TWRP, and copy the custom kernel to your device. Try to flash the kernel and then see if your device boots.
If your device still fails to boot, you could try flashing the stock kernel from your backup (you did make a backup before rooting?) or if you're running a more recent OS build, I've uploaded the Feb 2018 and April 2018 security patch stock kernels here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M To flash this in general:
a)Download the kernel boot.img to your device.
b)In TWRP, tap Install.
c)Tap Install image at the bottom of the screen.
d)Navigate to where you downloaded the boot.img and select the image file.
e)Target the image to boot (not recovery).
f)Flash, and wipe cache.
g)Reboot and see if that works.
If those don't work, restore your backup if you made one or you may have to re-flash your stock firmware - you do not have to re-lock your bootloader or wipe your device with this re-flash of the stock firmware.
Does your Windows computer have the correct Motorola USB drivers installed on it? https://support.motorola.com/uk/en/drivers
Hey! haven't seen anyone in this section for a while....
Why I am making this thread
So lately, I was looking through my old phones only only to find my old dusty Samsung Galaxy Note 2 lying around. It had already been rooted with kingroot... Needless to say, it's a spyware and my phone was drastically slow probably because of it.
Long story short, kingroot messed up all the files. Trying to install a working version of SuperSU gave me a headache. Finally, Magisk(v22.1) was supposed to work on the phone as it stated that it's the last version to support v4.4.2 but it doesn't actually work. It keeps on showing N/A whenever I launch it and a million different permutations that I had done in the process of rooting it using Magisk never worked.
This took me days, just jumping from one rabbit hole into another, finding old dead links which really made me so frustrated that at some point I wanted to throw the whole phone away.
That's why I'm creating this thread, so that I save the hassle for myself in the future and hopefully anyone who comes across this.
Updated rooting guide
This guide worked for my GT N7100 android version 4.4.2. It'd also probably work on other devices on other old phones which have an android version less than 5
Just make sure to backup everything before trying it.
Step 1. Flashing TWRP
Download the files from the following link
[TWRP]N7100 TWRP v3.3.1-0 ODIN FLASHABLE [23/05/2019]
Ok there we go this recovery is the latest 3.2.3-2 for t03g only don't flash this on t0lte(N7105). UPDATE: 12/04/2019: official support: https://dl.twrp.me/t03g TWRP 3.2.3-2 for N7100. Bugs: Format as F2FS doesn't work because the option isn't...
forum.xda-developers.com
Download ODIN
https://samfw.com/Odin/Odin3_v3.13.3.zip
Boot the phone into download mode(VOLUME DOWN + POWER KEY + HOME KEY)
Open ODIN and in BL choose the file that you've downloaded whose extension is or is similar to ".tar"
Click start
Step 2. Downloading and flashing Magisk
In here, you need to download a very specific version of Magisk, because anything above this version won't work.
NOTE: If you have installed any later versions of Magisk then make sure to uninstall them first, you can find out how to uninstall it from here(https://topjohnwu.github.io/Magisk/install.html#uninstallation)
Download THESE VERY SPECIFIC VERSIONS of Magisk and Magisk Manager from here
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Get into TWRP recovery mode and then flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
That's the end of it, your device is rooted now
HOWEVER, once MagiskManager has been installed, it would say that there's an update available(a newer version) available that you could upgrade to.
NEVER EVER UPDATE!! Updating your Magisk version to ANYTHING above v21.4 will cause it not to detect root. This is a bug with Magisk and it would probably never get fixed because support for android <5 had been discontinued a long time ago.
In case you ever do accidentally update Magisk, you will have to uninstall the Magisk app and then install MagiskManager-v8.0.7.apk again.
To uninstall and unroot your device, download this file and flash it with TWRP
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
Where I got the links above from
https://github.com/topjohnwu/Magisk/releases/download/v21.4/
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
ze7zez said:
Magisk v22.1
This release is focused on fixing regressions and bugs. Check the v22.0 release notes if coming from older releases.
Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 will only support Android 5.0 and higher.
Click to expand...
Click to collapse
Nope doesn't work as it wont be able to detect root at all, this is what had initially caused my headache to begin with
The last version of magisk that actually works on GT N7100 and probably any other old phone is the one that I linked in the thread
EDllT said:
(...)
Get into TWRP recovery mode and flash Magisk-v21.4.zip
Reboot back into the device and install MagiskManager-v8.0.7.apk
(...)
Click to expand...
Click to collapse
Thank you for the information.
I checked on Samsung Galaxy S4 Mini LTE i9195 (stock KK 4.4.2) and it works indeed at most version 21.4.
It is not possible to install MagiskManager-v8.0.7.apk because it is installed together with Magisk-v21.4.zip.