Develop Bugs

ZE500CL Rooting and other related stuff

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

Newbie Questions

Hey Guys,
Im new to the Android community coming across from an iPhone. I have landed myself an HTC One M8 but have no idea what to do next! (Ask me how to "Jailbreak" iPhones and I'm your guy) but the whole root process and custom ROMs are confusing me.
Basically I'm in Australia on the Telstra network (that seems to matter with rooting) and have the M8 on Android 6.0
Where is my next step? Im keen to learn but there are 100s of threads on this question and I simply don't know where to start, so for that I apologise.
Thanks in advance,
The "ConfusedOl1ve"
UnrealOl1ve

Since you're new to the forum, I'll give some (hopefully) friendly advice on posting: There is a thread sticky at the top of this section, and it says clearly "Please Read before posting" and describes what belong in this section, and questions/help requests is not one of them.
http://forum.xda-developers.com/htc-dream-g1/general/guide-to-htc-device-forums-please-read-t3234095
No need to try to change or move this thread (you can't). So I'll request to the mods to have it moved.
Now on to the real stuff. The exact process depends on what you want to do precisely, root or flash a custom ROM. Since on this device, you do not actually need to root before flashing a ROM. But some folks may want to stay on the stock ROM, but with root.
And the process for one versus the other will have some differences.

UnrealOl1ve said:
Hey Guys,
Im new to the Android community coming across from an iPhone. I have landed myself an HTC One M8 but have no idea what to do next! (Ask me how to "Jailbreak" iPhones and I'm your guy) but the whole root process and custom ROMs are confusing me.
Basically I'm in Australia on the Telstra network (that seems to matter with rooting) and have the M8 on Android 6.0
Where is my next step? Im keen to learn but there are 100s of threads on this question and I simply don't know where to start, so for that I apologise.
Thanks in advance,
The "ConfusedOl1ve"
UnrealOl1ve
Click to expand...
Click to collapse
Read these thread carefully andFollow steps to unlock your bootloader and install twrp http://forum.xda-developers.com/showthread.php?t=2699065

sayad1 said:
Read these thread carefully andFollow steps to unlock your bootloader and install twrp http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
Toolkit hasn't been updated in over a year and a half. It contains an extremely obsolete version of TWRP, which will cause issues with the OP's Marshmallow device.
Further, IMO the toolkit seeks to provide a solution for a problem which doesn't exist. The steps to unlock the bootloader, and flash custom recovery are easy to do "manually" without the toolkit. And learning to do so (for those that don't already know these skills) should be mandatory for anyone wishing to mods this phone.
Most of what the OP would need to know, is contained in Vomer's excellent guide here. Although the guide hasn't been kept up to date, so I'll provide the following caveats:
1) Follow Sections 0 and 1, to unlock the bootloader.
2) Use current version TWRP 3.0.2 from here, instead of the old version listed(and linked) in the guide. Somewhat obviously, the fastboot command used to flash TWRP will need to be changed to contain the proper file name (newer version number). Alternately, just rename the file something like twrp.img, and use that in the fastboot command.
3) Do not follow Sections 2 (S-off, SuperCID) or 3. They aren't needed for root or flashing ROMs, and the info is no longer accurate.
After that, the way to proceed depends on the 2 different paths I stated in my last post: stock ROM with root; or flash custom ROM.
Stock ROM with root: Make a TWRP backup of the stock (unrooted) ROM, then flash SuperSU. Vomer's guide automatically links to the latest stable version. But it should be noted, that the latest is SuperSU 2.78. Many folks make the mistake of using old versions SuperSU (<2.52 or thereabouts) which won't work on Marshmallow, and will result in being stuck in a bootloop.
Flash custom ROM: No need to root before flashing a custom ROM. What you do in this case:
a) Make a TWRP backup of your stock ROM
b) Backup anything you want to keep, by your method of choice (copy to computer, Titanium Backup, cloud, etc.)
c) Put the ROM on the phone
d) Boot into TWRP, select Wipe, and do the default wipe (Dalvik, Cache, and Data)
e) Select Install in TWRP, and choose the ROM to flash it.
f) Reboot and drink beer, you're done

Question Struggling to root...

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

Question Rooting with Magisk

Hello, i have seen some of you rooted your G30 with Magisk and i have some questions since i just got this phone and i want to make sure i dont brick it.
I havent been active in the modding scene in a few years so bear with me here:
To my understanding this is an A/B device and that means i should flash two boot images, is that right?
How would i go about obtaining the boot images? I just assumed i would be able to pull them from the device but i think i need to download them and then patch them, and if that is correct is there a trusted source for that?
And finally i am assuming i can flash them with fastboot and i dont need a flashing utility do i?
Thanks in advance to anyone willing to spend time educating me! Much love!

KAN7A said:
Hello, i have seen some of you rooted your G30 with Magisk and i have some questions since i just got this phone and i want to make sure i dont brick it.
I havent been active in the modding scene in a few years so bear with me here:
To my understanding this is an A/B device and that means i should flash two boot images, is that right?
How would i go about obtaining the boot images? I just assumed i would be able to pull them from the device but i think i need to download them and then patch them, and if that is correct is there a trusted source for that?
And finally i am assuming i can flash them with fastboot and i dont need a flashing utility do i?
Thanks in advance to anyone willing to spend time educating me! Much love!
Click to expand...
Click to collapse
[Guide] Update Rooted (Magisk) Motorola Device
[Guide] Update Rooted (Magisk) Motorola Device This is a General Motorola Guide If you need more help Please create a thread in your device's forum. Mention me by Posting "@sd_shadow" I'll help you as much as I can... Required Android SDK...
forum.xda-developers.com

sd_shadow said:
[Guide] Update Rooted (Magisk) Motorola Device
[Guide] Update Rooted (Magisk) Motorola Device This is a General Motorola Guide If you need more help Please create a thread in your device's forum. Mention me by Posting "@sd_shadow" I'll help you as much as I can... Required Android SDK...
forum.xda-developers.com
Click to expand...
Click to collapse
Wow thanks. You compiling all this information is nothing short of amazing.

Question Revert to A06 on 2451 via download mode

I updated to A10 on my 2451 and cannot root any longer. I had root on A06 so I am trying to go back. I have been trying a bunch of flashing methods and can not get anything to work.
It seems that any tutorials on flashing from download mode are not quite accurate. It seems like the current tutorials are previous tutorials that have been reposted to apply to a new device.
Does anyone have any tools / links to tutorials and or images that are tired and true.
The other option of course would be to get root on A10 which I am totally open to. The problem I had with that is that I could not extract the files from payload.bin they all ended up zero file length. Therefore I could not patch int_boot.img.
Thanks

beatified said:
I updated to A10 on my 2451 and cannot root any longer. I had root on A06 so I am trying to go back. I have been trying a bunch of flashing methods and can not get anything to work.
It seems that any tutorials on flashing from download mode are not quite accurate. It seems like the current tutorials are previous tutorials that have been reposted to apply to a new device.
Does anyone have any tools / links to tutorials and or images that are tired and true.
The other option of course would be to get root on A10 which I am totally open to. The problem I had with that is that I could not extract the files from payload.bin they all ended up zero file length. Therefore I could not patch int_boot.img.
Thanks
Click to expand...
Click to collapse
Extract Boot Image (for Root) - the DSU-Sideloader Method (and Other Tutorials)
Very nice to see Y700 get it's own place on XDA! I myself had just bought the 12GB version and have been very satisfied. The tutorials and info related to this model had been very difficult to come by and mostly in other languages, so I had to do...
forum.xda-developers.com
Hi
have you tried this method?

beatified said:
I updated to A10 on my 2451 and cannot root any longer. I had root on A06 so I am trying to go back. I have been trying a bunch of flashing methods and can not get anything to work.
It seems that any tutorials on flashing from download mode are not quite accurate. It seems like the current tutorials are previous tutorials that have been reposted to apply to a new device.
Does anyone have any tools / links to tutorials and or images that are tired and true.
The other option of course would be to get root on A10 which I am totally open to. The problem I had with that is that I could not extract the files from payload.bin they all ended up zero file length. Therefore I could not patch int_boot.img.
Thanks
Click to expand...
Click to collapse
Just temp root your phone using KernelSU and get the boot img you want or just after getting temp root, just goto Magisk and direct install to get permanent root.

surajpai524 said:
Just temp root your phone using KernelSU and get the boot img you want or just after getting temp root, just goto Magisk and direct install to get permanent root.
Click to expand...
Click to collapse
X2
@beatified listen to the partner. We have our 1+ like this and no problem so far

[CLOSED] [GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13-A.10
This tutorial will : Provide you with all the steps to unlock your Oneplus 11 bootloader Provide you with all the steps to root your Oneplus 11 (with your bootloader already unlocked) Provide you with all the steps to keep root during/after an...
forum.xda-developers.com