Sorry if this is a noob question but I want to root my device but all the tutorials I found on rooting here are based on when the phone was on android 9. My phone recently updated to android 10 and I'm wondering if using the process and resources found in https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751 would be safe to use. I've rooted a couple phones before but the android versions were all the same and I just followed the instructions to a T but I'm since I'm not sure how the underlying processes work I'm scared to do it and I end up messing up my phone. Thanks for your help in advance!!
Unlock your bootloader and your data partition will be erased, flash a twrp recovery like orangefox and flash the last magisk zip. Finish
Sent from my Mi Note 10 using XDA Labs
Same as Pie
jsonfile said:
Sorry if this is a noob question but I want to root my device but all the tutorials I found on rooting here are based on when the phone was on android 9. My phone recently updated to android 10 and I'm wondering if using the process and resources found in https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751 would be safe to use. I've rooted a couple phones before but the android versions were all the same and I just followed the instructions to a T but I'm since I'm not sure how the underlying processes work I'm scared to do it and I end up messing up my phone. Thanks for your help in advance!!
Click to expand...
Click to collapse
It's still the same procedure as Android 9 AFAIK. Nothing has changed, because I also rooted my RN7, for the first time, after updating to Android 10. I used OrangeFox throughout, though, not TWRP: I extracted the Orangefox recovery image from the flashable zip archive, flashed it through fastboot, then flashed the OrangeFox zip file through the recovery, then the bundled Magisk add-on.
I'd suggest to remove every security lock on your phone before doing that, however, to prevent being locked out and having to format data. Happy flashing!
Related
I am not a programmer and have little knowledge about flashing the ROM so to make sure I understand what I need to do and the order it needs to be done.
My Nexus 10 works great still, I have not had a security update for 2 some years and am concerned about this. Last October I tried to upgrade to 6.0 but it would not recognize the new rom and I ended up going back to the original 5.1 rom.
What I need to know is how to do it in a way I can understand. I have seen a utube video of someone that has been able to do it. So I know it can be done. Just need to know how.
Thanks,
Mike B.
Assuming you have a PC use this tool to unlock then root and install a custom recovery
Next download a Nougat rom like Lineage
Also download gapps and SuperSU
Copy the rom, gapps, and supersu into a folder on your tablet
Now reboot the tablet into recovery and do a full wipe then from recovery
Flash the rom
Flash gapps
Flash SuperSu
Reboot to system and give it a few minutes on the first boot
Hey there,
I need help, hope you have some for me . I want to use the 6.0.1. OpenKirin OmniROM on my phone and struggle even figuring out a way to get there.
I just bought a used ALE-L21 DualSIM phone with the B602 Build and EMUI 4.0.3 installed. The device is not rooted, nor has its bootloader been unlocked. The EMUI update service does not offer me any patches.
Could someone please line out to me which steps I have to take in order to root my ALE-L21 and get this ROM to work?
Disclaimer: No, I'm not just a lazy moron who does not want to read other topics on this forum - I'm a mere user with less-than-average knowledge of Android development or stuff like that. And I just can't make complete sense of the various posts I've found, since English is not my mother tongue and there seems to be a whole bunch of ways to do certain things with a phone. Well, since obviously I don't want to brick my new phone, I'm not too sure how to best puzzle together the pieces this Forum offers me. It would be insanely helpful if I could get a list that reads out something like:
1. Action - Source (for needed files, e.g.) - Result, on to step 2
2. Action - Source (for needed files, e.g.) - Result, on to step 3
3. ... and so on...
Okay, just so you see that I'm not entirely lost, I'm gonna show you the picture which is currently in my mind.
From what I understand so far, there's the following steps to get there (please rectify or rearrange steps as far as needed):
1. Update the device to Vanilla EMUI 4.1, Build B895 or B896 (I am currently downloading the B896 Build from this forum - which one is recommended? My phone is DualSIM)
2. Unlock Bootloader (What's the best way to do it? Huawei CS? Heard it's not even sure you get an answer. DCUnlocker? Wants money... Please help me clarify)
3. get TWRP 3.1.1.0 (I already have the IMG file, how do I get it to run on my phone?)
4. Root the device (I'd like to go with MAGISK, does anyone have a link for a MAGISK build confirmedly working on ALE-L21?)
5. Do some magic with TWRP (Which steps exactly?)
6. Flash the ROM Zip file via TWRP
7. Flash Gapps via TWRP
Is that about it?
As I said, please feel free to add to/adjust my list!
Thanks in advance,
Pako
If you haven't already install minimal adb tools on computer (windows) found here :
http://bit.ly/2jxX4ya
You then need to unlock bootloader using minimal adb tools and the unlock code
Unlock Code:
http://bit.ly/2z9EFhV
Unlock Bootloader Method in this thread here:
http://bit.ly/2oIASBs
After you are done unlocking the bootloader
Install twrp find that here :
http://bit.ly/2ok9BTi
There was a tool that was here somewhere to install twrp but I will link to my copy here
http://bit.ly/2ATBgRP
What you do is put the twrp image file in data folder
then change the name of the twrp file to TWRP_3.1.1-0_ALICE.img or
edit the install.bat file line data\fastboot.exe flash recovery data\TWRP_3.1.1-0_ALICE.img to the name of your twrp file
Once twrp is installed then you can pick which rom you want
The 6.0 roms arent going to be supported anymore so i suggest going for 7.0 ROM
I'm on AOSPA which is the cleanest and has good battery life
To install 7.0 rom you need B895 or B896 found here on the first post:
http://bit.ly/2jypIij
this is installed through twrp (which is accessed when Phone is off by holding volume up + power then let go once it vibrates or connect the phone to the computer and then type adb devices then adb reboot recovery in minimal adb tool)
once in twrp you need to install the B895.zip or B896.zip file then reboot your phone will boot into emui
you need to install twrp again as B895 or B896 wipes it
After installing twrp you can then install any custom rom of your choice
let the rom boot and then go back into twrp and install gapps found here: "http://bit.ly/1JOWjUqi recommend nano or even pico pick am64 7.1
I would also recommend installing Galactic forced deepsleep http://bit.ly/2ANVdbS
Hey there,
thank you very, very much for your comprehensive walkthrough! (Almost*) everything worked to perfection and I am now a happy user of OpenKirin's OmniROM 6.0.3. mod! Yeah, no 7.x... but I'd prefer to wait with that until the "issues" section of AOSPA does not contain any relevant things anymore. OmniROM seems to have no issues anymore, so I'm content with my choice. I will now follow your last advice and flash the Deep Sleep Mod to improve my device's battery life, and then I'm just happy.
* = The only issue I encountered was when having flashed TWRP, the device booted to the crappy EMUI eRecovery instead of TWRP. I solved this issue using this advice from another thread.
So, once again, thank you! All you xdaDevs, keep on developing ways to improve people's lives with their android devices!
Cheers,
Pako
First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days
Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8
xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?
xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img
magisk 24 is ****, it's bricking MediaTek powered Samsung phones
Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.
I bought a refurbed S8 for some Euros to have something to play with (before I brick a more expensive phone).
I thought a decent first step would be to root stock rom and see what can be done with it.
On the magisk webpage the installation guide says:
Installing Magisk through custom recoveries on modern devices is no longer recommended.
Click to expand...
Click to collapse
This installation method is deprecated and is maintained with minimum effort. YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
So I did it the hard way and patched stock-rom image as decribed and recommended there and flashed the patched rom via Odin.
After rebooting I got into the newly installed rom, didn't find the OEM unlock option any more but didn't care. Mistake? After trying to reboot I was in the
Only official released binaries are allowed to be flashed
Click to expand...
Click to collapse
trap. The former sentence was shown in small red letters and the device keeps rebooting again and again.
Now, I am back to stock image, twrp or the patched image couldn't be flashed stating the "Ony offici...." as desribed in this forum at many places.
What could I have missed?
Shouldn't this work without twrp and the "no-verity-opt-encrypt-6.1.zip" and "RMM_Bypass_v3_corsicanu.zip"
I gave up to do it the way magisk's manual suggests doing. .
Firstly, the manual says that in the Download Mode (Power + Bixby + Volume Down) to
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Click to expand...
Click to collapse
But no wiping and reboot happened to me. So I guess no unlock of the Bootloader as desired, and I guess that is why I ran into the issues described above.
So Plan B to run the latest stock Android Pie on Galaxy S8 G9 SM-G950F with twrp and rooted:
I mainly followed the guide to install twrp here, but:
a)
I stick to TWRP-23.0. It seems to me that the new features introduced don't help on Android 9?
b)
I found the rmm-patch here
c)
the no-verity-opt patch with current version 6.1 wasn't installable. I downgraded twrp and tried other versions, but I always ran into "ERROR1" as described here.
I used this script as a replacement, as suggested. And then finally the last of dozens of reinstalls of the stock firmware booted after twrp was installed.
Hints and comments if I lost the right path are welcome!