My Realme 6 is kept showing me:
The serial is not match
fastboot_unlock_verify fail
every time I tried to get into fastboot mode Using command adb reboot bootloader,
the bootloader is already unlocked, so I can't enter fastboot mode via the (In-depth Test) App.
It would be my pleasure if anyone got a fix for this problem,
regards
Do u have a solution for this? I was able to unlock but I want to relock and in I'm getting a similar window in fastboot, mine shows this :
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 12, after accidentally updating from rooted android 11 to android 12 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 12.
Any ideas??
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
soler37 said:
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
Click to expand...
Click to collapse
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Y-YoUsSef-F said:
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Click to expand...
Click to collapse
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
leopseft said:
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
Click to expand...
Click to collapse
Ok bro
leopseft said:
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
Click to expand...
Click to collapse
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Hi, but bro I am in android 12 (F.07) with magisk Root and google wallet (NFC) works great, I think for now not sure if I gonna upgrade to F.09 and losing root access
As my friend @leopseft described our situation, can't enter fastboot mode
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Actually you can pass the safetynet tests with Magisk modules and magisk hide. But this is another topic. I can help you if you decide to re unlock and root!!
But I have an idea which I wanna try first about the access to fastboot mode.
In the guide you posted there is a step in which you bypass mtk authentication.
(4. Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.))
Did you try to access into fastboot after this step or you continue to the flash process??
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
leopseft said:
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
Click to expand...
Click to collapse
Thank you bro for this solution and I'm so glad you replied to this thread,
but for me, I was able to get into fastboot without this problem after I installed A13 custom Rom (EvolutionX v7.2 UNOFFICIAL)
I used these commands:
adb devices
adb reboot bootloader
As a reminder, my problem was:
The serial is not match
fastboot_unlock_verify fail
Click to expand...
Click to collapse
Thanks again <3
Related
Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.
From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539.
But in all of these cases you still need a custom recovery.
At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)
So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html
This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!
Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.
..
cam30era said:
@Kyuubi10
Have you seen this thread > http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Kyuubi10 said:
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Click to expand...
Click to collapse
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
defmetal96 said:
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Click to expand...
Click to collapse
Thank you guys for your reply!!
Unfortunately as described in my signature my N9 was stolen.
But I'll change the title of this thread to [SOLVED] so that others know where to find an answer.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
For that a Moderator needs to be made aware ) Let's try do that!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
joeish said:
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
Click to expand...
Click to collapse
Hello,
I don't have this specific file anymore, but I think you can sideload the latest OTA from here:
Images OTA complètes pour les appareils Nexus et Pixel | Google Play services | Google for Developers
developers.google.com
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Morky001 said:
Hello! I can't seem to make TWRP Official app (from Google Playstore) and Magisk root to work.... so hacking game is still a distant possibility here. I downloaded both app, but couldn't get them to work, so now uninstalled both.
My phone is: Moto G7-Power with Android 9 (Pie), my questions are:
1. Which of these two should I install first on android without PC? Magisk or TWRP? Seem to get conflicting instruction from those tutorials on Youtube.
2. After downloaded "TWRP Official app" from Google Playstore, chose my phone from the list and downloaded the version for my phone. It said downloaded successful, but I can't flash TWRP, can't open it in recovery mode (hardreset), it wouldn't do anything!
3. As for Magisk apk... one of the two files won't install, the zip files.... it said "failed"... so what do I do then?
Can anyone please help me fix all these problems? Very frustrating right now.
Click to expand...
Click to collapse
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
x.ak**** said:
Hello, Morky.
I am afraid I don't understand what you really mean by your question above. You have not used a PC yet but tried to flash TWRP. Please give me more insight on what you are trying to do.
Click to expand...
Click to collapse
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Nivead said:
You have to unlock your bootloader first. It requires that you read out a encrypted code from the phone, via the USB port using ADB/Fastboot. The code is entered into a web page at Motorola, and if your phone can be unlocked, they will send you a unlock code. Then you fastboot the unlock code. then fastboot twrp. then flash magisk.
you may consider going to the forum page for your phone, it will have all the details.
https://forum.xda-developers.com/g7-power
look under the guides section
hope that helps
Click to expand...
Click to collapse
Nivead, I did unlocked the OEM before downloading that though, but still didn't work. The phone is an unlocked phone.
And, thank you for your help.
Morky001 said:
Kumar, I did unlocked the OEM before downloading that though, but still didn't work.
Click to expand...
Click to collapse
And.. thank you.
Morky001 said:
Thank you, Kumar for your response. First of, I'm NOT a techie like you. I just followed these tutorials on YouTube....
With TWRP app this is what happened (or not happened):
https://www.youtube.com/watch?v=RtvI2C9VrOY
Started having problem at the 3:00 min mark here as well... even with hardreset
https://www.youtube.com/watch?v=wEHChHcpZEI
I couldn't do what this guy did at the 3:00 min mark....
With Magisk Manager app.... what happened was just like at the 3:00 min mark on this video
https://www.youtube.com/watch?v=DvlLy42UtGg
I thought explaining what'd happened by referencing what I was doing per these tutorials would better answer your questions, since I don't know how else to say it, again not a techie person.
<Morky>
Click to expand...
Click to collapse
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Nivead said:
The phone has to be BOOTLOADER unlocked in order to install TWRP and Magisk. Turning on OEM unlock, is a step in unlocking the phone - but it does not unlock the bootloader.
When you are saying the phone is unlocked, I believe you mean the phone is unlocked so it will run on any cell phone carrier - a way the phone is sold. But its not bootloader unlocked.
Bootloader unlocked is different - Most phones are sold with the bootloader locked and because of that, you cannot modify the operating system. Unlocking the bootloader allows you to modify the the android operating system.
You will have to install Motorola USB drivers on your computer. Go to the Motorola page at: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and read about unlocking the bootloader. You will have to create a Motorola account to get an unlock code, if the bootloader can be unlocked. The pages will also have a link to obtain the Motorola USB drivers (MotorolaDeviceManager_2.5.4.exe).
You will need to install Minimal ADB Fastboot, a terminal program that allows you to push data/commands back and forth between the computer and your phone via the USB port. https://forum.xda-developers.com/showthread.php?t=2317790 You will use the FASTBOOT command to obtain the encrypted unlock code from the phone. You will also use FASTBOOT to install the unlock code that Motorola will send you,
After the bootloader is unlocked, you will use FASTBOOT to install TWRP into your phones recovery partition. TWRP info at https://www.xda-developers.com/how-to-install-twrp/ TWRP is a backup and recovery program that is used to install programs, etc,
After you install TWRP, you can install MAGISK, which will ROOT the phone. Magisk info at https://forum.xda-developers.com/apps/magisk.
Please go to the forum I told you about and under the guides section you will find documentation that explains how to root the phone and install custom ROMs.
https://forum.xda-developers.com/g7-power A guide will give you the finer details for your phone model.
Before you do any of the above, I advise you strongly to have a backup. Using FASTBOOT there is a command called "getvar all", it will return a long printout of info and it will include a readout of the original firmware installed on the phone. You will want to know this in case you brick the phone. Having this info will allow you to obtain the original firmware and be able to restore it via FASTBOOT. Firmwares at https://mirrors.lolinet.com/firmware/moto/ .l After installing TWRP, you should backup the phone to your SD card and then move the backup to your computer for future needs.
Good luck.
Click to expand...
Click to collapse
Deae Nivead,
..Oy! That sounds painful!! Guess, I have no business be doing this lock/unlock/rooting thing, huh?! Not a techie at all, this is very foreign to me! And those guys on YouTube... they lied then, said I could do all these without PC... Yeah, right! Turned out, it wasn't as easy as they were showing on videos. (((sigh))) Would be easier if I just send my phone to you?!?!!!
Thank yoooouuu soooo much for taking the time to write/tell me all this, truly appreciate your help and replies.
<Morky>
x.ak**** said:
Hello, Morky.
I do not understand how one can flash any image directly from the device without rooting it. Now, in order to root your device you will need either TWRP or flash SUPERSU or Magisk using fastboot. If you wish to root your device and install TWRP on it, you will require access to a computer.
Click to expand...
Click to collapse
Kumar,
I guess those YouTube tutorials omitted left out a lot of steps and not as easy nor simple as they made it to be.... "without PC" as they claimed. How would someone with no background in computer programing, nor a "techie" like you here at xda... like me would know that?! If you "don't understand how....." I wouldn't understand either!! More so than you. One thing I've learnt now, all those tutorials about rooting and TWRP. on YouTube... are crap.
I couldn't find any simple instructions for rooting so hopefully this helps someone.
I'm assuming you've already unlocked your bootloader. If not, download the deep testing app (there are various apks on xda e.g. from here). Then submit the application (it took me a few minutes to get approved) then use the app to reboot into the bootloader, then run command fastboot flashing unlock. I don't believe the deep testing app works on android 12 yet so you may have to downgrade to android 11 to unlock your bootloader.
If your bootloader is unlocked you can update to android 12 (though it isn't necessary to root). If your gt isn't offering you the latest version you can download a recent version on this thread and then use "local install" in the update menu.
Next, download twrp from:
https://github.com/qiurigao/RMX2202
The latest version is twrp-3.6.0-V2.img
And download magisk from:
https://github.com/topjohnwu/Magisk/releases
The latest version is Magisk-v24.3.apk
Put your gt into fastboot mode by powering off, then hold the power and volume down buttons together until you're in the fastboot screen.
Then run command:
fastboot boot "twrp-3.6.0-V2.img"
Do NOT try installing twrp as I've read it can cause issues.
This should boot twrp (it will be in chinese but it doesn't matter).
Rename the magisk apk to a zip e.g. Magisk-v24.3.zip
Now run:
adb push Magisk-v24.3.zip /data/Magisk-v24.3.zip
Then:
adb shell "twrp install /data/Magisk-v24.3.zip"
Now you can adb reboot and you should be rooted!
Good luck.
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Having the same issue. Unfortunately no banking apps working for me.
F0Xie said:
Having the same issue. Unfortunately no banking apps working for me.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Look in Magisk settings, enable Zygisk (beta), enable enforce denylist, add apps to the denylist then install universal safetynet fix module from github and reboot device.
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Unlocking bootloader and rooting the device will format data?
Unlocking bootloader - yes
Thanks, this worked!
Also, really DO NOT install Magisk by clicking on "Install" in the TWRP interface, it can brick the device. Just don't touch the phone while installing Magisk, only use the fastboot and adb commands.
F0Xie said:
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Click to expand...
Click to collapse
still working on last update?
robertaalves said:
still working on last update?
Click to expand...
Click to collapse
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Thanks man, it worked like a charm.
F0Xie said:
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Click to expand...
Click to collapse
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Hiiii, I'm thinking of buying this phone so I got 2 questions; 1) are there any custom roms available? From my little to none research, I've only found gsi, andd after my failed attempts, hearing the word gsi brings a bad taste, lol. Aanndd 2) is there any development/general discussion group about this device on telegram?
Gordin said:
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Click to expand...
Click to collapse
can you open the bootloader in a13? or you need to open it before update?
Hm, to unlock bootloader, you need the right deep testing apk for your system version. I haven't looked into if there exists one for Android 13, but I would just downgrade the phone to a patch that works. I think I unlocked mine by downgrading to stock, and then installing the latest system update that is still Android 11. Sounds like there is a working Android 12 too, but I haven't tested it. Having to downgrade doesn't really matter to me, because unlocking will wipe all user data anyway. (Of course if you find a deep testing apk that is meant for 13, you can also try that, I just don't know if one exists)
alex61194 said:
can you open the bootloader in a13? or you need to open it before update?
Click to expand...
Click to collapse