Related
So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.
tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.
Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.
So any luck to boot this sucker ? Don't even have stock recovery ..
have you tried "fastboot boot boot.img" from the correct factory image ?
Boot loop plus no recovery equals BLOD. Sorry but likely you are done.
[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!
^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.
bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )
Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system
bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?
Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.
bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU
bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65
Ladies & Gents, please buckle up for liftoff.
Code:
[COLOR="Red"][B]/* Disclaimer
* You are choosing to test this software as-is & accept full responsibility in case
* it will not work as expected. Or for WW3. Or dead kittens, whichever is worse.
*/[/B][/COLOR]
Instructions 1/2 = Bootloader Unlock:
Code:
[b]1: DOWNLOAD[/b] the [URL="https://drive.google.com/file/d/0B8rpJsF4EG0YUHh4UEo5ZExHWjg"]> prerequisites <[/URL]
[b]2: UNZIP[/b]
You will have 3 folders for zs550kl, zs570kl & zs570klpro containing:
UL-Z016-WW-4.12.40.9999-user.zip -> unlock-capable firmware update
UL-Z016_1-WW-4.12.40.9999-user.zip -> unlock-capable firmware update for the zs570kl PRO variant (in its own folder)
UnlockTool.apk -> unlock app, needed for the actual operation
PDF with Instructions in CN & EN (for zs570kl/pro only)
- bootroot.img - rooted boot image (bootrootn.img for ZS550KL Nougat)
- bootstock.img - stock boot image, if you want to return to stock or if something went wrong (bootstockn.img for ZS550KL Nougat)
- Superuser.apk - superuser app
[b]3: FACTORY RESET[/b] via Settings -> Backup & Reset
This usually solves the issue with not being able to unlock due to a "missing PIN"
Do through initial setup - no need to configure anything as the following factory reset will erase everything again.
Just click through the options to access the app drawer asap.
[b]4: COPY Files:[/b]
ZS570KL - Copy UL-Z016-WW-4.12.40.9999-user.zip to your internal storage
ZS570KLpro - Copy UL-Z016_1-WW-4.12.40.9999-user.zip to your internal storage
[COLOR="DarkOrchid"]ZS550KL - no files needed at this stage. Just ensure you are on the latest firmware: (Marshmallow: v12.40.108.29; Nougat: v22.40.26.43); update otherwise.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-12.40.108.29-user.zip"]> latest MM firmware <[/URL] put it in the root of your internal storage.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-22.40.26.43-user.zip"]> latest N firmware <[/URL] put it in the root of your internal storage.[/COLOR]
Copy & install UnlockTool.apk
[b]5: REBOOT[/b]; You should have a notification about a new firmware.
No notification for ZS550KL if you were already on the latest firmware.
Install & reboot again.
[b]6: Run the UNLOCK[/b] App
It should do another factory reset on success.
Instructions 2/2 = ROOTING:
Code:
[b]7:[/b] Copy/install Superuser.apk
[b]9:REBOOT into BOOTLOADER[/b]; either holding volume up + power from a powered down state or typing the following in a console (assuming you have ADB enabled in developer options)
adb reboot bootloader
[b]9: FLASH[/b] bootroot.img via fastboot
fastboot flash boot bootroot.img (you can also do a fastboot boot bootroot.img without flashing to check if the boot image works for you)
fastboot reboot
note: change the filename to bootrootn.img if you want to test the ZS550KL Nougat version.
[b]10:[/b] Check for root via adb shell; su or via any app requiring root, on device (terminal, titanium backup, etc...)
- in case something goes wrong, flash the stock boot via fastboot.
- report success/failure in this thread.
[b]11:[/b] BUSYBOX (Optional):
I've bundled busybox with the boot image; follow the commands below to install (in an adb shell or terminal session):
mount -o remount,rw /system
busybox --install -s /system/xbin/
[b]12: RECOVERY[/b] (Optional):
[URL="https://drive.google.com/file/d/0B8rpJsF4EG0YZ1FQSkUxRW9TdWs"]> stock dump <[/URL]
> twrp < / WIP
What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka
squo_85 said:
What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka
Click to expand...
Click to collapse
It means we have the bootloader unlock.
The tutorial/instructions are contained in a PDF in the zip.
English instructions at the end of the PDF.
Three is one more question?
Hot to root it?
Like for 520kl with changed according to 570kl files
Spoiler
https://youtu.be/hg77b8o8Jk4
Or just use universal tool e.g. Autoroot tool?
Spoiler
https://youtu.be/UYTCRhg0SCw
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?
adwinp said:
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?
Click to expand...
Click to collapse
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!
Chaosruler said:
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!
Click to expand...
Click to collapse
Great, thank you for the confirmation & enjoy ;]
Let the fun begin ^^
Do you think I can flash with fastboot flash instead of running it with fastboot boot? The latter let's me have root until I restart my device( temp root)...
Maybe fastboot flash will perma root it
Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.
jmoricone said:
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.
Click to expand...
Click to collapse
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image
Chaosruler said:
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image
Click to expand...
Click to collapse
Wow, i guess i am a newbie here.. I have heard adb but dont remember what where or how i got it fo rmy zen2. can you provide instructions how how to check, access, use adb to confirm unlocked bootloader. Also can you provide instructions on to to run the boot image for rooting.
thanks
For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.
Darkdragontc said:
For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.
Click to expand...
Click to collapse
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.
adwinp said:
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.
Click to expand...
Click to collapse
Yup Confirmed Working, no more problems. Thank you! Now i hope we can make some custom roms and get twrp on here when we can. (820 that what i have)
Just to be clear, on the SD821 variant is this a permanent root or just a temp root?
ultramag69 said:
Just to be clear, on the SD821 variant is this a permanent root or just a temp root?
Click to expand...
Click to collapse
temp root if you use fastboot boot command
Perma root of you use fastboot flash boot command
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I can confirm it with my device...
pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I used a SD820 boot image as base & don't have a SD821 variant to test on thus didn't want to mislead the community.
But @Chaosruler tested & it seems to work.
On my ZF3, I'm on Nougat with the bootloader unlocked and I've confirmed that.
Followed instructions on the XDA ZF3 ROOTING GUIDE thread & ZF3 Toolkit, I can't seem to flash TWRP due to an error.
"
sending 'recovery' (26636 KB)...
OKAY [ 0.912s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.075s
"
I've enabled USB debugging and even restarted, redownloaded drivers, changed USB ports and re did again but still the same error.
Any tips and solution?
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
sensi277 said:
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
Click to expand...
Click to collapse
Just tried right now, did the command but its stuck at booting. My zf3 didn't boot the .img
Prev was too blurry
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
wang1chung said:
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
Click to expand...
Click to collapse
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
TiTAN-O-One said:
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
Click to expand...
Click to collapse
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
wang1chung said:
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
Click to expand...
Click to collapse
I unlocked my ZF3 via the "0.unlock_ze522kl.bat" way. Some people complained that the official way of unlocking frm the Asus website broke their devices or smth.
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
TiTAN-O-One said:
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
Click to expand...
Click to collapse
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
wang1chung said:
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
Click to expand...
Click to collapse
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
TiTAN-O-One said:
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
Click to expand...
Click to collapse
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
wang1chung said:
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
Click to expand...
Click to collapse
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Found a thread here and a user says
"The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM"
I had this annoying "reboot and type my pin password" whenever I restart my phone.
Any idea how to remove or decrypt this? I believe this is the issue to all the failed and permission denied errors i guess.
TiTAN-O-One said:
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Click to expand...
Click to collapse
That "FAILED (remote: Partition flashing is not allowed)" error means you're bootloader isn't unlocked. I believe that is the root cause of your issue.
Use the official unlock, works every time.
The pin at the beginning bootup is a security setting. I believe there was a thread where someone said to disable security lock and then reenable it but chose "no" when it asks to use pin to start device. Give that a shot first and see.
For the official bootloader unlock, is it compatible with Nougat?
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
TiTAN-O-One said:
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
Click to expand...
Click to collapse
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
wang1chung said:
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
Click to expand...
Click to collapse
Great! Everything is settled and Im unlocked and rooted successfully too. Thanks for the help.
Glad you got it sorted, now make a TWRP backup of all your partitions and go crazy flashing lol
Ok so.....
Was unlocked with dirtysanta and istalled stocK_ls997 ..
long story short , friend had this phone, got ota and installed (don't ask me why) , so now phone stuck in twrp
seems like bootloader is locked out , can't access adb to unlock it again as i only have access to twrp and fastboot...
Can't boot to OS because of locked booloader...
Had similar situation before and managed to unlock bootloader again , but don;t remember how...
Can you guys help me with that?
++++++++++++++++++++ FIX ++++++++++++++++++++++
jkjambo said:
Finally !!!
Was able to boot to system.
Reinstalled TWRP , but not the one in dirtysanta thread, installed beta twrp for sprint version from this thread and then wipe/format and then installed deoxeded rom from same thread...
http://www.androidinfotech.com/2016/11/root-lg-v20-sprint-ls997-nougat-install-twrp.html
twrp link
http://redirect.viglink.com/?format... Install TWRP - Android Infotech&txt=Download
Click to expand...
Click to collapse
You're in luck
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
The problem is that there is no kdz or tot file for sprint version
wow.. you just need to delete the fota, misc, and caches.
its a common issues with attempting a ota on non oem firmware.
delete the update package from misc and ur good.
Team DevDigitel said:
wow.. you just need to delete the fota, misc, and caches.
its a common issues with attempting a ota on non oem firmware.
delete the update package from misc and ur good.
Click to expand...
Click to collapse
No , seems like update locked bootloader..
I can access twrp and install any rom, but can't boot to the rom , because of locked bootloader....
twrp unmounts system parition itself.....
any more advices?????
If you are able to boot into TWRP you can easily flash the unlocked dirtysanta aboot.img through an adb shell with the dd commands
Hmm, nice catch...
Can you let me know dd command?
i've installed aboot.img with twrp img installer in boot partition, but still same
jkjambo said:
Hmm, nice catch...
Can you let me know dd command?
i've installed aboot.img with twrp img installer in boot partition, but still same
Click to expand...
Click to collapse
Copy the dirtysanta aboot.img into your adb folder & rename it to aboot-dv.img (just to avoid confusion)
Code:
adb push aboot-dv.img /
adb shell
dd if=aboot-dv.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
You might need to repeat step3 of the dirtysanta root method (depending on your variant & if boot needs patching)
Prowler_gr said:
Copy the dirtysanta aboot.img into your adb folder & rename it to aboot-dv.img (just to avoid confusion)
Code:
adb push aboot-dv.img /
adb shell
dd if=aboot-dv.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
You might need to repeat step3 of the dirtysanta root method (depending on your variant & if boot needs patching)
Click to expand...
Click to collapse
Thanks for help, but it's still same.
still locked bootloader and can't boot to os
jkjambo said:
Thanks for help, but it's still same.
still locked bootloader and can't boot to os
Click to expand...
Click to collapse
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Prowler_gr said:
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
I've wiped everything and formated data.
Will add your steps after that and will let you know
Prowler_gr said:
Your OTA may be over-writing the aboot when booting...
You may need to format everything (system, data, cache) & flash stock by @me2151 with TWRP
https://www.androidfilehost.com/?fid=385035244224409782
After flashing (without rebooting) repeat the procedure with the aboot-dv.img as per my previous post
Refer to the dirtysanta thread
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
still same....
twrp unmounts system partition .....
I've tried bootloader unlock with manual but i'm getting stuck on this step
adb shell chmod 0777 /data/local/tmp/*
it says not a directory
jkjambo said:
still same....
twrp unmounts system partition .....
I've tried bootloader unlock with manual but i'm getting stuck on this step
adb shell chmod 0777 /data/local/tmp/*
it says not a directory
Click to expand...
Click to collapse
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Prowler_gr said:
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Click to expand...
Click to collapse
I'm not running exploit because of recovery, but for bootloader unlock. i think it causes twrp bootloop , as twrp isn't able to mount system partition after restart.
Maybe i'm wrong .. will give few more tries
Prowler_gr said:
No need to run the full dirtysanta exploit, you've already got TWRP. Just wipe/format, flash stock rom, install aboot-dv.img, re-format data, flash su & you should be done.
Click to expand...
Click to collapse
No joy ... still same ....
Don't know what to do
isn't there any fastboot flashable system or boot image or anything?
Finally !!!
Was able to boot to system.
Reinstalled TWRP , but not the one in dirtysanta thread, installed beta twrp for sprint version from this thread and then wipe/format and then installed deoxeded rom from same thread...
http://www.androidinfotech.com/2016/11/root-lg-v20-sprint-ls997-nougat-install-twrp.html
twrp link
http://redirect.viglink.com/?format... Install TWRP - Android Infotech&txt=Download
jkjambo said:
No joy ... still same ....
Don't know what to do
isn't there any fastboot flashable system or boot image or anything?
Click to expand...
Click to collapse
But that's what the aboot-dv.img is: an unlocked fastboot enabled bootloader.
Are you absolutely sure that you are using the aboot.img from dirtysanta??? If in any doubt re-download the dirtysanta zip, extract the aboot.img rename it to aboot-dv.img & re-follow my instructions.
[edit:] Happy you were able to resolve your issue!
You just need to do the vol down power button factory reset procedure to break the twrp bootloop.
Search it. The update didn't do anything to your phone but trigger the recovery boot switch. Factory reset will stop this and will not modify anything on your phone as it needs stock recovery and doesn't work with twrp.
Prowler_gr said:
But that's what the aboot-dv.img is: an unlocked fastboot enabled bootloader.
Are you absolutely sure that you are using the aboot.img from dirtysanta??? If in any doubt re-download the dirtysanta zip, extract the aboot.img rename it to aboot-dv.img & re-follow my instructions.
[edit:] Happy you were able to resolve your issue!
Click to expand...
Click to collapse
I downloaded it 2 or 3 times , even when i was 100% sure on first time
fastboot and twrp was working, but bootloader still says it's not unlocked.
Seems like problem was twrp itself.. i knew it had some problems because it wasn't for this specific model, but i was using it before for flashing same zip over and over... not quite sure why it stopped working (i've reflashed it also few times)
@midmadn
I've reflashed roms like 10 times with no luck , so factory reset was not a solution in my case . seems like update messed up someting in recovery .
Anyway solution is in the first post if anyone needs it