I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck
LBN said:
I have now spent several days in trying to root, boot unlock and every time I get that dreadful "permission denied", if you are on any build from 179 (I think) and upwards, no rooting or unlock tool will work here, you will end up going through all kinds of recovery and even xFSTK-Downloader, and simply waste your time.
I just went through the xFSTK-Downloader process in order to get my phone back to life, it was stuck in the Fastboot loop after trying to run the restore.bat to unlock it for M builds, so I thought I would create an entry here to warn people not to attempt any rooting or unlocking until you have downgraded your build.
Good luck
Click to expand...
Click to collapse
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you
tabletalker7 said:
I never had any problems with rooting or unlocking LP .184 and now there is even a guide to root and unlock the MM beta (and it works great too). Maybe if you tell us exactly what you are doing we can help you
Click to expand...
Click to collapse
did you perhaps root and unlock your device prior to upgrading to build 184 initially? I have simply followed the threads to root and boot unlock, I actually did manage to root it with one of the 180 builds, but I still got permission denied, boot unlocker never worked for me and gave me lots of problems as I mentioned. If you look at the permission denied threads, I was having the same problem.
I flashed the MM beta before shakalaca ame up with the downgrade method. When you wanted to go back to LP you had to use xFSTK and the Asus Flash Tool then. That locked you down. One click unlock and method 3 for root worked on my phone. My son recently wanted xposed for youtube adaway on his zenfone 2 and his was never rooted or unlocked and the same worked on his .184 LP. You still have not mentioned in this thread what model zenfone 2 you are having trouble with - my home has 3 ze551ml 4GB/64GB phones and all 3 rooted and unlocked with no problems.
Related
Hi, I got the lg g4 H-815 , android version 5.1 and v10c software. I want to root the phone because i want to flash roms and kernels to get a better performance.
, but im confused will all the guides, therefore i got some questions i would really appriciate if someone answers them.
1. Do i have to unlock bootloader in order to gain root access and flash roms etc?
2. What is the most easiest and reliable guide to root the phone?
Sorry for my English.
Root is not needed for flashing ROMs, what is needed is TWRP and unlocked bootloader, when the bootloader is locked it means that it will not boot up if it detects that you flashed 'stuff' unsigned by LG - custom ROMs! Anyway if you only want to root it and you don't mind of MM, you can root it on LP without unlocking the bootloader. Although, if I was on your place I would hold on a minute and checked my serial number first because it is more likely that your phone can die at any minute, independently of what you are actually doing on your phone... G4 is a ticking bomb, when mine fell into a bootloop (it's not like a bootloop when you flash something wrong, the phone is like dead ), since I have unlocked my bootloader LG refused to repair it so many times... They just gave my number to SBE and said that they will repair my phone if I pay, guess what, these idiots refused as well. About 3 times tho. So I was on my own, after a month I managed to make my phone work(ish). I'm not saying I fixed it because this is unfixable. I just made it work. Not fully functional tho, at least it will last I'll buy a new phone, and no more LG for me. And I would recommend you to have a think about doing this stuff. If you have warranty they will replace it immediately, but if not you'll need to fight them up, as I am going to. PSST, you can still root it on LP without losing the warranty, remember!!
So I have been trying for the last 3 days to get my 5.1.1 BPA1 to root and it will not go.
Now though I am no expert with phones I am very good at following directions and while following the [Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) and it constantly fails while running Kingroot (Step 6.5). makes it to 52%, Reboots the phone, I Unlock the screen and Kingroot opens again, goes to 52% and fails again.
I really just want to root and keep stock ROM just removing the bloatware but I can't seem to figure out why it is constantly failing.
Any suggestions?
panowolf said:
So I have been trying for the last 3 days to get my 5.1.1 BPA1 to root and it will not go.
Now though I am no expert with phones I am very good at following directions and while following the [Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) and it constantly fails while running Kingroot (Step 6.5). makes it to 52%, Reboots the phone, I Unlock the screen and Kingroot opens again, goes to 52% and fails again.
I really just want to root and keep stock ROM just removing the bloatware but I can't seem to figure out why it is constantly failing.
Any suggestions?
Click to expand...
Click to collapse
You have to gain root to push the exploit through ADB. Kingroot is one of the ways to do it. Kingoroot is another. Neither are particularly stable methods of root. Kingoroot seems to be a bit better. Both have the potential of calling home to their Chinese masters with your phone's data. I recall having to try four or five times to get root and get it long enough to push the ADB commands.
Try going into Application manager and clearing the cache. Try Kingoroot. My suggestion once you're rooted is to install a ROM like Jasmine which is largely stock. The reason being, it'll give you a chance to format your data partition, which might get rid of the Kingroot/Kingoroot cooties.
Keep trying. Follow the directions closely. It's worked for too many people. And if you think you've got it, do it one more time and get the Marshmallow bootloader on your phone, so you can enjoy the latest firmware.
KingoRoot fails also @ 92/93%. Tried several times using both KingRoot and KingoRoot.
Kingroot never worked for me. Kingoroot was hit or miss for me. Try the Kingoroot PC version, that seemed to work a lot better for me.
panowolf said:
So I have been trying for the last 3 days to get my 5.1.1 BPA1 to root and it will not go.
Now though I am no expert with phones I am very good at following directions and while following the [Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) and it constantly fails while running Kingroot (Step 6.5). makes it to 52%, Reboots the phone, I Unlock the screen and Kingroot opens again, goes to 52% and fails again.
I really just want to root and keep stock ROM just removing the bloatware but I can't seem to figure out why it is constantly failing.
Any suggestions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...bilized-process-to-unlock-bootloader-t3375527
This is the one that worked for me, I used Kingoroot and got it to work ( I was also getting stuck at 90%) the way this is done exactly is cut and dry and works. If you are just looking to debloat have you tried GatesJunior tool it great http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Kingoroot running on my laptop was the ONLY way I could get root on my N4. Kingroot failed 20+ times.
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?
douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.
You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse
For me, I had to run Kingoroot from my laptop, and Kingroot never worked.
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
assuming you are already on MM version ww4.21.10.233... if no update to this version and download the following tool..
https://drive.google.com/open?id=0B72QQTXqZSRwTDNtU1N6OEdMdmM
reboot phone in fastboot mode. now extract the downloaded zip and double click unlock.bat phone will reboot 2 times. then you will get white screen and stuck there. when you see white screen. simply turn off mobile. reboot in fastboot mode with volume plus and power button. and run restore.bat from extracted zip.
now download twrp from official twrp website version 3.1.1.0. and flash it in fastboot mode. hope you know how to ( place twrp image in adb fastboot tool and open command windows in same folder reboot phone in fastboot mode and connect to pc. run the following command
fastboot flash recovery twrp-3.1.1-0-Z00A.img
then use volume button to find recovery mode and click power button to boot into twrp.
now download super su from following link use this version only as i have just tested it few minutes ago.
https://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
place superuser zip on internal memory or sd card and click install in twrp and install super userzip. alternatively you can sideload supersu zip as well. then wipe cache and dalvik cache and reboot system. note phone may bootloop or restart 2,3 times. don't interrupt it. it will boot itself into system.
this is 100 percent safe way.
---------- Post added at 11:12 PM ---------- Previous post was at 11:05 PM ----------
x86fanboy said:
Hello,
I bought a Zenfone 2 in 2015 and have loved it ever since. Back then it was simple to root, unlock the bootloader, and neither required the other.
To root, just enable ADB and run this.
To unlock the bootloader, just download this from azus.
Now, buying a phone fresh, to remove all the bloat is becoming a challenge.
To root, you need an unlock the bootloader. To unlock the bootloader, you need to downgrade to an early 5.0 image.
So I downgrade, unlock the bootloader, and root. To get back on 6, I need to upgrade to a newer version of 5.0, so I do. Root gone, bootloader still unlocked, splash screen is normal. Fine, I root again.
Finally, after upgrading to 6.0 (using adb sideload) both root and the bootloader unlock are gone. So I have to start again, and either live with unbloated 5.0, or unrooted, bloated 6.0.
As far as I can tell the only way around this is downgrade to 5.0, unlock my bootloader, then flash a pre rooted unsigned system.img.
Sadly I cannot find a recent pre rooted unsigned system.img, and have no way of knowing how to create one. If someone could help me make one I would greatly appreciate it.
Am I doing this all wrong? Is there a better way?
Because now I have a phone that I'm either stuck with a buggy 5.0 or a bloated 6.0; and the original, two year old zenfone is stuck in the bootloader because I was experimenting with various tools from around here.
I am well aware that I could just nuke the old phone with xFSTK to get out, but I refuse to. I have no such problems nuking the new one though.
Any and all help would be greatly appreciated, the Zenfone 2 is still a great device and is fantastic value for money, so if I can sort out all this I will happily make a full, comprehensive guide with my new knowledge to replace the errors in the outdated one here, and to add far more comprehensive knowledge about unbricking:
https://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Thank you all for your time
Click to expand...
Click to collapse
do you state that you have an old device which you are unable to revive with xFSTK. what error do you get? put device on charge for 5,6 hours with original charger and use the following guide. use correct gp flag value use 4 zeros not 5
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
wow, no need to do all this... just use one of the available tool, my prefered one is this one:
https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293
very easy to use, to unlock, it will temporaly downgrade your boot to 5.0, unlock bootloader, then reflash boot 6.0.
Once there, just flash TWRP recovery and Magisk, from the tools.
I also had a locked ZF2 in MM 6.0 and using this tool it took less than 5 minutes to have an unlocked rooted phone, and I haven't wiped or lost anything.
I'd like to root my G710TM and run the Lineage OS, but predictably could not obtain an unlock key from LG for the bootloader. I find a bunch of threads from a couple years ago with people trying to root this model. I am wondering if anyone was successful and how they did it.
I'm still trying to root mine too. I want to update to custom android 11
One year later... I guess the G710TM will stay stock forever