Related
Nothing
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
ponnuvelpandian said:
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
Click to expand...
Click to collapse
Yes you can just like that but you will need to be rooted before using dd command.
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
ImjuzCY said:
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
Click to expand...
Click to collapse
Sorry about that, found a better place. Go ahead and use the new link for the stock recovery.
how can i do this ?
gamsheer said:
how can i do this ?
Click to expand...
Click to collapse
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
gamsheer said:
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Click to expand...
Click to collapse
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
BobboVilla said:
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
Click to expand...
Click to collapse
This device you and all of choose only allows us to do find the vulnerability in the bootloader, and this is how it is packaged. Any other way would like a nexus or oneplus model is much easier. However asus choose to lock their bootloader and package their partitions. Now if you can rewrite their fasboot and that would be great. So root with a one click root. Then use the dd commands to package your stock recovery and life will go a lot easier, with future firmware updates, just remember to uninstall root for a ota and replace your custom recovery with your stock first before doing a adb sideload
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
thank you very much its work fine my pro
gamsheer said:
thank you very much its work fine my pro
Click to expand...
Click to collapse
Your welcome
Sent from my SM-T230NU using Tapatalk
Thanks a lot
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
NicoAu said:
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
Click to expand...
Click to collapse
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
mikerowes69 said:
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Can you tell me where I can find this build?!? On asus website, I only see "UL-Z00A-WW-2.20.40.164-user.zip" with boot.img and droidboot.img in the archive...
Thanks
mikerowes69 said:
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
i snort flour said:
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks guy for wasting my time as well as anyone else. If your on here you don't really care about warranty. You assume I don't know about unlocking or anything else. Please go bother someone else. Assuming makes an ass out of you.
Sent from my SM-T230NU using Tapatalk
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.
I'd like to know if there's a way to remove the 5 second "Your device has been unlocker and can't be trusted" message that started coming up every time I boot when I unlocked the bootloader on my A2017U.
If I understand correctly, this was added in B29 and I just need to flash the B27 boot sequence and then unlock it. Just not sure exactly how to do that, and what specific files I need.
Thanks
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
DrakenFX said:
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
Click to expand...
Click to collapse
Hi,
I unlocked my A2017G using controllerboy's method. I didn't get this message then. But after flashing the B11 full rom from ZTE's webstite (using the update.zip from my SDCard) I now also have this message. Since I'm on a A2017G I can't flash the B20 boot.img i guess. Can I flash the boot.img from controllerboys thread or will that brick my device because of the B11 ROM?
Side note: I didn't get offered the update to Nougat (even without root) now I'm on B11. Not sure if I want to switch no Nougat yet without xposed, but if I wanted, how would I proceed?
Many thanks in advance,
Cheers,
/Cacti
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Can you provide a quick tutorial for flashing aboot.img? Tried with fastboot flash and it failed.
Thanks!
Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
le_cactus said:
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
Click to expand...
Click to collapse
Thanks for the help. However, I get a permission denied error when I try to execute step 13. Not sure why. Device is rooted. Any suggestions?
Thanks!
I had the same. I opened a terminal window, gave the su command and then did the dd commmand. Hope I make sense.
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
Installation Procedure
To summarize the procedure:
First use adb to copy aboot and fbop (if you want to use the fastboot features) to your sdcard)
Then flash the aboot and fastboot(only needed if you want the fastboot lock/unlock options) images
Enjoy your unlocked phone
See B : https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Code:
#copy necessary files to internal sd card
adb push aboot.img /sdcard/
adb push fastboot_unlock.img /sdcard/
#make a backup to your internal sd of the partitions we are going to modify
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img
#copy them to your pc
adb pull /sdcard/fbop_lock.img
adb pull /sdcard/aboot_lock.img
#flash the proper fastboot and aboot file
adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop
adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot
I also added the old aboot and fastboot_unlock image. For me as a european user the fastboot unlock options was initally not available.
The bootloader message actually saved me from softbricks so I don't mind it being there
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.
Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess
wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.