Related
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
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
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html
UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you
clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you
clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.
ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.
UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards
X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs