Related
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I can add any info you find to the device index in the general section for the 500CL.
Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.
any news update in our bootloader? hope someone could work for that..
How to get rid off couldn't add widget?
crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.
Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.
Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now
I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk
Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:
@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk
Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:
Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk
I recently installed TWRP's custom recovery on my V495 AT&T but trying to boot into recovery gives me an error and not being familiar with Flashify I missed the step to backup the stock recovery.
Can someone be kind enough to please send me the stock recovery for the AT&T V495 that is made and Flash able through Flashify? Thank you all!!
PS> Warning for others with V495 that want custom Recovery. = Once rooted you can install flashify and the instructions for V496 custom recovery all work without errors but once you try to install TWRP and reboot things may go wrong.
Can someone please upload the stock (v495) recovery created by or flashible through flashify?
I have a new/ rooted v495 that I have not messed with the boot loader. If you can point me in the right direction on getting you a copy of the stock boot loader I would certainly be happy to.
---------- Post added at 07:39 AM ---------- Previous post was at 06:57 AM ----------
I figured it out. I sent you a message with the link. You can repost it if you would like. I still do not have my 10 post quota yet to be able to provide external links.
ksimmons1571 said:
I have a new/ rooted v495 that I have not messed with the boot loader. If you can point me in the right direction on getting you a copy of the stock boot loader I would certainly be happy to.
---------- Post added at 07:39 AM ---------- Previous post was at 06:57 AM ----------
I figured it out. I sent you a message with the link. You can repost it if you would like. I still do not have my 10 post quota yet to be able to provide external links.
Click to expand...
Click to collapse
do you mind sending a copy my way. My stock recovery is also broken TIA
https://www.dropbox.com/s/xjtxfcc9f3t23k4/v495 Stock Recovery?dl=0 Courtesy of ksimmons1571 --- Thanks Buddy..
I have not tested it yet as I just saw it today and I'm at work. If you get it going please let us know. Thanks.
soft bricked v495 on stock recovery
I'm soft bricked on 5.0.2 lg support tool says I'm not in need of update at this time.so I can wait for next update but who knows when that will be lol. Will I be able to flash this stock recovery if I'm on stock recovery. ? I dont think I can thow. I'm thinking I'm going to have to extract my kdz file n use flash tools 2014. Unless I can get on twrp well I'm soft bricked n flash a ROM. But I don't see any Roms for device. Well any help will be much appreciated. Thanks in advance also if I figure it out I'll post back.
can anybody extract kdz or tot file like @Player1211 said or can anybody extract their system folder?
m_reyna_16 said:
can anybody extract kdz or tot file like @Player1211 said or can anybody extract their system folder?
Click to expand...
Click to collapse
If there's a KDZ or TOT available, you can extract it on Windows with WindowsLGFirmwareExtract-ver.1.2.5.0, available at http://forum.xda-developers.com/showthread.php?t=2600575.
My tablet is messed up, stays stuck on att logo after I manually tried extracting and installing xposed framework files. I cannot extract anything on mine.... Unless ure telling me the tot file is on that other forum? Sorry I'm on my phone and driving, can't check in detail
EDIT: read your post right this time, like I said I was driving... No, there's no tot or kde file for my tablet
Hi my friends, I am looking for a STOCK RECOVERY for my LG G Pad F 8.0 AT&T (V495). I was trying to do an OTA upgrade to 6 but after the Download and restart the installation is giving me an error because i am ROOTED. I need to flash stock recovery to be able to install new OTA upgrade to Marshmallow 6. Is someone have a 5.0.2 STOCK Recovery or maybe another idea on how can I do and upgrade to Marshmallow 6 I will appreciate any help. Thanks
Anyone leak a V495 KDZ yet? Mine is toast without a way to flash stock recovery. Bootloop of death.
Tikerz said:
Anyone leak a V495 KDZ yet? Mine is toast without a way to flash stock recovery. Bootloop of death.
Click to expand...
Click to collapse
Haven't seen one. Just the TOT without the necessary .DLL.
roirraW "edor" ehT said:
Haven't seen one. Just the TOT without the necessary .DLL.
Click to expand...
Click to collapse
Arghghghhg
Tikerz said:
Arghghghhg
Click to expand...
Click to collapse
I understand. Although there were at least KDZs for my VK810, we didn't have a known tested TOT until a few months back when a fellow user was nice enough to purchase, test and share the TOT for the VK810 from this site http://www.lgbbs.com:41/thread-838-1-1.html. Since we had KDZs available, we were able to extract the necessary .DLL from one of them.
I know someone else recently looked on that site for V495 stuff but you might want to look again and/or use Google Chrome to translate the site (slow but effective enough), and maybe even there's a section to put a request or a bounty up for a .DLL or at least KDZ, which you'd be able to extract the .DLL from. It appears the standard prices of items is $10 U.S., from what I could tell.
Not advocating the site or the fact that they sell the stuff, but when there's no other option, and at least it's not an arm and a leg.
suspected root.
trying to update after root, what exactly do we need to do to get this Update going? btw i only have a little experience rooting. and that was an HTC about 4 years ago. So far i have Flashfire installed which says can Flash OTA updates but LG is untested. im not going down that road without unlocked bootloader and a rom to pull my ass out of the bricks, unless someones has success already.
So far i haven't heard of an unlocked bootloader for The V495, can we do that yet?
i'm hearing about flashify, never used it, what does it do, how does it work?
Is there a way to remove root evidence with Android studio?
Why don't penguins Fly, do you suppose they miss it?
Sleeper0013 said:
trying to update after root, what exactly do we need to do to get this Update going? btw i only have a little experience rooting. and that was an HTC about 4 years ago. So far i have Flashfire installed which says can Flash OTA updates but LG is untested. im not going down that road without unlocked bootloader and a rom to pull my ass out of the bricks, unless someones has success already.
So far i haven't heard of an unlocked bootloader for The V495, can we do that yet?
i'm hearing about flashify, never used it, what does it do, how does it work?
Is there a way to remove root evidence with Android studio?
Why don't penguins Fly, do you suppose they miss it?
Click to expand...
Click to collapse
I can only address some of your questions.
Flashify simply flashes stuff like kernels and recoveries, but it's limited as to what it can flash and I doubt if you'd be able to flash an OTA with it. There are other apps that do the same thing with the same limitations. Also, just because it can flash something doesn't mean that's all that's required to get it to work. What I mean is, to use an example that doesn't necessarily apply to you or the V495, some LG devices require a certain older version of the bootloader (aboot) in order to be able to get into TWRP, so if you're rooted on a later release of the stock ROM (with newer bootloader) you could flash TWRP with Flashify, but you either still won't be able to actually get into it, or you might not even be able to boot at all after.
Flashfire is reasonably early in its development - having only yesterday been updated to v0.51. I've only tested a little bit. On the Verizon LG G Pad 8.3 VK810, backups seemed to work okay, but I haven't tested restoring through Flashfire. I was able to successfully flash a ROM made from the stock tablet ROM but no matter what it doesn't keep root, even when the ROM includes the necessary SuperSU.zip and flashes/roots fine in TWRP. Flashfire's Everroot option, or having Flashfire flash SuperSU.zip separately didn't work on that device either. @Chainfire said there were segfaults in the log and has no way of determining what's causing them.
I would say you are wise not to try to flash anything without having a way to recover - there are enough people on here with broken V495s with no recovery option already.
Regarding removing root evidence: From Lollipop on (at least on LG), OTAs check to see if your system (and possibly other not normally modifiable) partitions have ever been modified. It doesn't explicitly check for root, but rooting your device usually modifies the system partition. Before Lollipop, OTAs commonly only checked if the files the OTA would update have been modified from their original. OTAs don't normally contain copies of the entire files that will get updated - it contains a "delta", which is basically a list of "change this into that", as quite often files don't need to change completely - only be modifed to be up to date.
You can't reasonably "unmodify" your system manually. Only by flashing a 100% stock unrooted ROM.
*If* or when Flashfire works, it could conceivably get around a modified system partition, but it'll be challenging and might take some time for @Chainfire to support all or most OEMs/models working as smoothly as it does for the #1 primary devices he's testing it on, which I believe are Nexus devices.
I talk to penguins all the time and they do miss flying, especially when they're the prey.
roirraW "edor" ehT said:
You can't reasonably "unmodify" your system manually. Only by flashing a 100% stock unrooted ROM.
I talk to penguins all the time and they do miss flying, especially when they're the prey.
Click to expand...
Click to collapse
Ok so where do we look about getting stock rom?
And poor penguins and all their bricked devices. :crying:
Sleeper0013 said:
Ok so where do we look about getting stock rom?
And poor penguins and all their bricked devices. :crying:
Click to expand...
Click to collapse
LOL re: penguins!
I have a link for where to keep an eye out or possibly request in the post right above yours. tl;dr There's only a TOT available for the V495 that anyone's found so far. It's available in one of these threads in these G Pad 8.3 sections and I've even uploaded it elsewhere just in case the only source I noticed for the link goes down. The bad news is that there's no .DLL available to use with it, which makes it at minimum partially or mostly, at maximum fully useless.
It's fully useless without the .DLL because you can't use the normal TOT flashing software to flash it to your V495 - you need the .DLL (as I've recently written somewhere, maybe above in the post I reference or nearby), the .DLL that's necessary would probably be able to be extracted from the KDZ for the V495 - but there's no KDZs that've been made available. KDZs include the .DLL necessary, TOT's require an external .DLL.
It's partially or mostly useless in that the TOT can still be extracted to obtain the individual partitions. It's conceivable that Flashfire might be able to flash either those partitions or a flashable zip made out of them as long as you're successfully rooted, although I have no idea if Flashfire works with anything but SuperSU - I believe it specifies that SuperSU is required but there's a chance it'll work with Kingroot or another root app.
I'm fully willing to make a flashable zip out of the TOT for anyone who wants to test it - just be aware of the dangers that you might end up with a brick with no way to recover since I'm guessing that there's no TWRP for the V495 and I don't even know the root capability since I don't have that device and I only follow the threads regarding it just to help where I can. If you do have root it's at least somewhat comforting that Flashfire worked fine for flashing the stock ROM on the LG G Pad 8.3 VK810, albeit without being able to re-root it as part of the process. Let me know if you're rooted and want to test such a flashable zip with Flashfire (which would probably be the safest/most trustworthy app that has capability of flashing zips).
I don't have enough knowledge to know how to figure out how to root any device that there's no established method for, nor have I ever made TWRP for any device.
I do know that Kingroot is very invasive and is sometimes only a temporary root, requiring re-rooting every time you reboot. It puts things on the system partition that run in the background - all sorts of things not necessary for simply rooting or keeping root, so who knows what kind of calls home it makes and with what data. I've only used it before as a temporary root in order to establish an alternate way to get TWRP installed on the Verizon G3 VS985 without fully downgrading the stock ROM to a more easily rootable/TWRPable version, and ultimately my method leads you to flash a ROM that uses SuperSU so that Kingroot is completely gone anyway.
roirraW "edor" ehT said:
I understand. Although there were at least KDZs for my VK810, we didn't have a known tested TOT until a few months back when a fellow user was nice enough to purchase, test and share the TOT for the VK810 from this site http://www.lgbbs.com:41/thread-838-1-1.html. Since we had KDZs available, we were able to extract the necessary .DLL from one of them.
I know someone else recently looked on that site for V495 stuff but you might want to look again and/or use Google Chrome to translate the site (slow but effective enough), and maybe even there's a section to put a request or a bounty up for a .DLL or at least KDZ, which you'd be able to extract the .DLL from. It appears the standard prices of items is $10 U.S., from what I could tell.
Not advocating the site or the fact that they sell the stuff, but when there's no other option, and at least it's not an arm and a leg.
Click to expand...
Click to collapse
If I buy another V495 do you think I could use the KDZ/TOT extractor here to fix our V495s?
http://forum.xda-developers.com/showthread.php?t=2600575
Or maybe someone with functioning V495 could extract the KDZ/TOT or DLL for us?
Tikerz said:
If I buy another V495 do you think I could use the KDZ/TOT extractor here to fix our V495s?
Or maybe someone with functioning V495 could extract the KDZ/TOT or DLL for us?
Click to expand...
Click to collapse
Having another V495 wouldn't get you a KDZ or TOT. The KDZ/TOT extractor takes an existing KDZ or TOT file and extracts it into the separate partitions - it has nothing to do with making a KDZ or TOT out of an existing device. There's currently no way to do that. And the .DLL isn't available except inside a KDZ, it's not on anyone's running V495.
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
petar_markovic said:
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
Click to expand...
Click to collapse
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even want be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
ninjakira said:
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even wont be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
Click to expand...
Click to collapse
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
ninjakira said:
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
Click to expand...
Click to collapse
Ok, i will post an update on how it went if i actually decide to root.
madbat99 said:
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
Click to expand...
Click to collapse
Got it.
Build Number: Oxygen OS 11.IN11AA
Model IN2025
This is my first time messing around with this kind of stuff, so please bear that in mind when responding. I may not understand certain terminology, but I know how to follow instructions.
Trying to get access to Magisk root, I've watched tons of videos but had no success. Bricked my phone multiple times and had to use MSMDownloadTool to fix it.
Right now I have my device with an unlocked bootloader, and I tried downloading a OS11 OP8 img, patching it with Magisk, then fastboot flash boot'ing it from my PC. But no root... I also tried to get TWRP on my device with no luck. Can someone walk me through the exact steps with the correct files? I've been at this for like 6 hours and have gotten nowhere. I followed tutorials, but I cant find anyone with a OnePlus 8 Pro on OS 11. If I have to rollback, that's fine, I'll need some help there though.
Thank you! I'll respond ASAP to any questions for me if you need them.
HawksNestYT said:
Build Number: Oxygen OS 11.IN11AA
Model IN2025
This is my first time messing around with this kind of stuff, so please bear that in mind when responding. I may not understand certain terminology, but I know how to follow instructions.
Trying to get access to Magisk root, I've watched tons of videos but had no success. Bricked my phone multiple times and had to use MSMDownloadTool to fix it.
Right now I have my device with an unlocked bootloader, and I tried downloading a OS11 OP8 img, patching it with Magisk, then fastboot flash boot'ing it from my PC. But no root... I also tried to get TWRP on my device with no luck. Can someone walk me through the exact steps with the correct files? I've been at this for like 6 hours and have gotten nowhere. I followed tutorials, but I cant find anyone with a OnePlus 8 Pro on OS 11. If I have to rollback, that's fine, I'll need some help there though.
Thank you! I'll respond ASAP to any questions for me if you need them.
Click to expand...
Click to collapse
First thing is first TWRP is not A11 compatible. Been mentioned lots . You may have already looked in the thread I will be posting, but people have followed it and have working root on A11. The fellow that started the thread is very helpful as well.
https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
Download this version of magisk, make sure it has permission and you can patch a file, if not, then update it.
https://mega.nz/file/LU9U3aSC#EFJTOKaJ5CN4oXeAa2LzBBUIoY1wqejzi-VyUa3nQq8
Then follow these instructions, originally from my other thread here:
https://forum.xda-developers.com/on...k-boot-img-t4175033/post83680733#post83680733
1. Obtain a patched boot img for your device variant preferably using payload dumper, copy this file to your fastboot folder on your computer
NOTE- If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
3. Boot the magisk img
fastboot boot magisk_patched (or name of your patched boot img
4. Reboot your phone, your phone should now boot and you should now be rooted but we need to make this permanent.
5. Open magisk manager and click install/update
6. Select Direct install (recommended)
7. Allow magisk to permanently root your device then click reboot.
If you need to obtain your own boot img then please open the top link and go through the payload dumper guide, then the patching guide, then the above.
Good morning and welcome to XDA! However we appreciate you creating an account for seeking assistance, please note that in a lot of cases you will already find answers readily available on our forum. In your case these are some of the threads that may provide them:
[GUIDE] How to Root OnePlus 8 Pro without TWRP
(ROOT) Android 11 / payload dumper / magisk_patched guides
[ROOT] Patched boot.img for Android 11 (Both OP8 and OP8P)
And likely more in the section you posted in: OnePlus 8 Pro Guides, News, & Discussion (also note that questions should be posted in Q&A)
I warmly invite you to read our Forum Rules. Among other things, it states:
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
Therefore I'm locking this thread but feel free to continue posting in one the threads mentioned above. Enjoy your stay on XDA!
Kind regards and stay safe
Timmy
PS. Here's another useful thread: [GUIDE] - XDA New User Guide - Getting started on XDA
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
RushPL said:
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
Click to expand...
Click to collapse
Sadly, that's the way XDA developed in the most recent years. A lot of developers have become "impatient", they rarely tolerate questions (which they consider unnecessary for reasons of their own) or consider everything that is not in their concise jargon offtopic and either ignore, flame or delete those.
The basics are not explained anymore, they expect everyone to work naturally with the tools at hand, most often or not "small" steps are left out (like clicking on something, or changing a menu), or they refer to "go look at that guide" - only then - that guide tells you (aswell) "for step 3, go look at that guide", because "everyone should know" - that way the rooting community is quite small and elitist; and it's hard for outsiders to come in (and potentially add something to the pool of stuff) simply because it's not a pleasant experience to "dive" into the world of Android customization. It's a sad development and only very few seem to be intend on breaking it.
Then we also have the problem of manufacturers trying to make this communities life harder, just take a look at Google and the constant war to have safetynet NOT trip, to give people the chance to use banking apps or GPay. It's a constant struggle and many "guides" get out of date pretty quickly - and most often or not, those are not kept up to date, or getting demolished by a mod team, so that also adds to the whole confusion, when people try to work with guides / community fixes that won't even work anymore.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...irmware-sd1a-210817-036.4353807/post-85857811
I followed the instruction from this post to restore my P6P to preinstalled October firmware, then updated with November firmware OTA, then unlocked bootloader and root again. My phone works much better now.
I made a mistake of flashing the vbmeta and boot imgs of October firmware for rooting after updating November firmware OTA. I experienced some strange issues with my phone until I restored it with Official Google Android Flash Tool and start the whole rooting process again with the correct version of vbmeta and boot imgs.
Pekempy said:
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
RushPL said:
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
Click to expand...
Click to collapse
No need but thank you for offering.
The vbmeta is also new to me. I want to be clear, I've mostly compiled others' instructions (credited in the post) with my own experience, and tried to make it as easy to follow as I can
I was able to root successfully with working Safety Net! Thank you @Pekempy