The firehose for the V35 has leaked and it is reported to allow unfettered partition access. That means unlock and root! Details in the TG forum. No intention to steal anyone's thunder just want to share the news.
Can you link the forum?
+1
What's exactly TG forum?
What exactly is firehose?
The G7 and V40 like the V35 are members of the LG Judy platform and can use the same qcom 845 firehose and 9008 flashing methods. Rather than duplicate I think it is best to visit and take advantage of the v40 forum. There are instructions for how to use the firehose with qpst and qfil to flash, unlock, and root at this link:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
That forum also provides links to download the needed files.
Happy 9008 mode flashing!
jwrezz said:
What exactly is firehose?
Click to expand...
Click to collapse
fpozar said:
What's exactly TG forum?
Click to expand...
Click to collapse
cmrntnnr said:
The G7 and V40 like the V35 are members of the LG Judy platform and can use the same qcom 845 firehose and 9008 flashing methods. Rather than duplicate I think it is best to visit and take advantage of the v40 forum. There are instructions for how to use the firehose with qpst and qfil to flash, unlock, and root at this link:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
That forum also provides links to download the needed files.
Happy 9008 mode flashing!
Click to expand...
Click to collapse
Interesting. This really is exciting news! Finally no need for an octoplus box. Thanks very much for sharing, will definitely give it a go in a few months when I find the time to setup my phone again.
Has anyone tried this yet
Flowtron3000 said:
Has anyone tried this yet
Click to expand...
Click to collapse
Yep, works exactly as advertised. I was just about ready to give up on this phone :victory:
I can also confirm it worked on my V35 but the OP poster's instructions assume that user following these instructions have a good know how about Qfil 9008 mode and associated processes. This is the first time i used Qfil. Qfil is very powerful tool and it is possible to delete one vital or all partitions on phone without any prompts or warnings. Please be careful following that guide to unlock bootloader on V35 or V40 and your very first step should be to use 'Partition Manager' --> 'Manager Partition Data' --> 'Read' on any partition especially 'abl_a' partition that you will be deleting following that guide. I personally just backed up some important partitions before proceeding. In my first try I was stuck with an error after flashing engineering bootloader onto abl_a and was stuck on boot screen. I reentered download mode after several failed tries and was able to use the Dev LGUP to flash the .kdz again. On my second try I was able to get to fastboot but 'fastboot oem unlock' kept failing until i disconnected the phone and reconnected it in a new powershell, tried 'fastboot flashing unlock' which gave error and said i was already unlocked, but i wasn't unlocked yet, tried 'fastboot oem unlock' and for some reason it worked this time . It worked after several tries so don't give up that easily. There is not custom recovery for the V35 that i could find so we are limited in what we can do even with root and Magisk but at least this is a start. Hopefully some devs now can get at least TWRP going for this phone.
****(Please read and do the second part in this post first)****
To add to my previous post, if anyone is going to unlock using this method, they need to keep a few things in mind. First, keep in mind that you can only access the fastboot menu when you have engineering bootloader flashed to abl_a partition but while you have that, you can't boot into system, only fastboot will work. In order to boot back into system, make a backup of your original abl_a partition and after unlocking bootloader, you can flash back original abl_a partition to boot normally. Also even before starting with abl_a partition (i haven't tried this part yet but am confident i will get it to work once i continue working with my V35 later tonight), while you have Qfil and phone in 9008 mode, you shouldbackup the stock bootloader image, reboot to system, install Magisk apk, then use the app to patch Magisk to it. Once you have patched bootloader image, put phone back in 9008 mode, replace abl_a with engineering bootloader, enter fastboot, unlock bootloader, try flashing patched boot image if it fails in fastboot, try flashing it using Qfil. If you try and it works please leave any feedback and tips here for others. Thanks.
It is great to hear that it worked out! The process was smoother for me. Possible reasons for the issues you encountered are in the specifics of your USB setup. The ideal situation for flashing on this phone and other LG V and G series models is a high quality, even LG-supplied, USB cable and a computer with USB 2.0 ports. There are dozens of reports in forum of diffulties with USB 3.0 hardware. If it is a laptop, it should be connect to mains, as well.
For anyone else contemplating this, the instructions in the V40 forum, link provided in a previous post above, are well-written, provide links to the needed files, and there is helpful discussion on troubleshooting problem.
Android# said:
****(Please read and do the second part in this post first)****
To add to my previous post, if anyone is going to unlock using this method, they need to keep a few things in mind. First, keep in mind that you can only access the fastboot menu when you have engineering bootloader flashed to abl_a partition but while you have that, you can't boot into system, only fastboot will work. In order to boot back into system, make a backup of your original abl_a partition and after unlocking bootloader, you can flash back original abl_a partition to boot normally. Also even before starting with abl_a partition (i haven't tried this part yet but am confident i will get it to work once i continue working with my V35 later tonight), while you have Qfil and phone in 9008 mode, you shouldbackup the stock bootloader image, reboot to system, install Magisk apk, then use the app to patch Magisk to it. Once you have patched bootloader image, put phone back in 9008 mode, replace abl_a with engineering bootloader, enter fastboot, unlock bootloader, try flashing patched boot image if it fails in fastboot, try flashing it using Qfil. If you try and it works please leave any feedback and tips here for others. Thanks.
Click to expand...
Click to collapse
cmrntnnr said:
It is great to hear that it worked out! The process was smoother for me. Possible reasons for the issues you encountered are in the specifics of your USB setup. The ideal situation for flashing on this phone and other LG V and G series models is a high quality, even LG-supplied, USB cable and a computer with USB 2.0 ports. There are dozens of reports in forum of diffulties with USB 3.0 hardware. If it is a laptop, it should be connect to mains, as well.
For anyone else contemplating this, the instructions in the V40 forum, link provided in a previous post above, are well-written, provide links to the needed files, and there is helpful discussion on troubleshooting problem.
Click to expand...
Click to collapse
Good to hear it was smoother process for you. How did you root after unlocking the bootloader? The original post in V40 forum doesn't deal with V35 and the method of erasing LAF doesn't apply to my phone because I am able to access fastboot, which in itself, even with failed tries wasn't an issue, the real issue for me is taking advantage of unlocking the bootloader otherwise what's the point of an unlocked bootloader.
I feel your pain. This phone isn't easy and most seem to have moved on. Like you said, there isn't much point to just unlocking the boot loader, root is the goal. In a nutshell, what you need to do to get root is:
1-Extract the boot_a image either directly from the phone or from the kdz. Place the image on your phone.
2-Install Magisk Manager apk on your phone. No root needed for that. I am on stable 7.5 branch.
3-Use Magisk Manager to patch the boot_a image file from 1, emphasis on file.
4-Copy the patched image to your computer.
5-Use 9008 mode to flash the patched image to boot_a and boot_b
6-Reboot, you should now have root.
Android# said:
Good to hear it was smoother process for you. How did you root after unlocking the bootloader? The original post in V40 forum doesn't deal with V35 and the method of erasing LAF doesn't apply to my phone because I am able to access fastboot, which in itself, even with failed tries wasn't an issue, the real issue for me is taking advantage of unlocking the bootloader otherwise what's the point of an unlocked bootloader.
Click to expand...
Click to collapse
cmrntnnr said:
I feel your pain. This phone isn't easy and most seem to have moved on. Like you said, there isn't much point to just unlocking the boot loader, root is the goal. In a nutshell, what you need to do to get root is:
1-Extract the boot_a image either directly from the phone or from the kdz. Place the image on your phone.
2-Install Magisk Manager apk on your phone. No root needed for that. I am on stable 7.5 branch.
3-Use Magisk Manager to patch the boot_a image file from 1, emphasis on file.
4-Copy the patched image to your computer.
5-Use 9008 mode to flash the patched image to boot_a and boot_b
6-Reboot, you should now have root.
Click to expand...
Click to collapse
Thank you for your help. I flashed it to both boot_a and boot_b but still phone reboots to fastboot only. No matter what I do or select in fastboot menu it just reboots back into fastboot. Thanks for your help.
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
Finally got it to work, used Qfil in 9008 mode to 'read' the boot_a partition to extract it but forgot to change it to .img from .bin prior to Magisk patch it. Renamed the extracted file with .img extension, patched it again, flashed it back on boot_a and boot_b partitions and this time i have full root. Thanks again for your help.
Great! A clear set of instructions like what @ChazzMatt wrote for unlock and root of the V30's would make everyone's life better.
With luck, this will kindle interest of some developers and modders.
Android# said:
Thank you for your help. I flashed it to both boot_a and boot_b but still phone reboots to fastboot only. No matter what I do or select in fastboot menu it just reboots back into fastboot. Thanks for your help.
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
Finally got it to work, used Qfil in 9008 mode to 'read' the boot_a partition to extract it but forgot to change it to .img from .bin prior to Magisk patch it. Renamed the extracted file with .img extension, patched it again, flashed it back on boot_a and boot_b partitions and this time i have full root. Thanks again for your help.
Click to expand...
Click to collapse
I tried that and got the red triangle with "all slots are unbootable!" after flashing the engineering bootloader. I simply followed the instructions, nothing more.
A clearer guide is needed, soon. I don't know why it was thought that just linking would be enough.
Sorry to hear that. There are at least two reasons to refer people to the V40 forum. One is that the V40, G7, and V35 phones are each Judy models. The instructions on the V40 are clearly written and work on each of these models.
As to why there are not V35 specific instructions or perhaps more fullproof instructions. Well, there are so many different variants of these phones, pc hadware, usb cables and the like. No one here is paid. Frankly, there is a fair bit of empiricism. You have to be willing to experiment and accept some risk.
With all of that said, the reason for your difficulties is not likely a problem with the instructions. People here would be happy to help you work through the process if you provide some details.
Iantuition said:
I tried that and got the red triangle with "all slots are unbootable!" after flashing the engineering bootloader. I simply followed the instructions, nothing more.
A clearer guide is needed, soon. I don't know why it was thought that just linking would be enough.
Click to expand...
Click to collapse
cmrntnnr said:
Sorry to hear that. There are at least two reasons to refer people to the V40 forum. One is that the V40, G7, and V35 phones are each Judy models. The instructions on the V40 are clearly written and work on each of these models.
As to why there are not V35 specific instructions or perhaps more fullproof instructions. Well, there are so many different variants of these phones, pc hadware, usb cables and the like. No one here is paid. Frankly, there is a fair bit of empiricism. You have to be willing to experiment and accept some risk.
With all of that said, the reason for your difficulties is not likely a problem with the instructions. People here would be happy to help you work through the process if you provide some details.
Click to expand...
Click to collapse
I just dropped in to see what condition my condition was in
Yeah, yeah, oh-yeah, what condition my condition was in
I appreciate your pleasant approach to mitigate folks phone problems.
It's just a darn nice effort, thank you.
Hello,
I follow this instractions:
1-Extract the boot_a image either directly from the phone or from the kdz. Place the image on your phone.
2-Install Magisk Manager apk on your phone. No root needed for that. I am on stable 7.5 branch.
3-Use Magisk Manager to patch the boot_a image file from 1, emphasis on file.
4-Copy the patched image to your computer.
5-Use 9008 mode to flash the patched image to boot_a and boot_b
6-Reboot, you should now have root.
and follow this too:
Finally got it to work, used Qfil in 9008 mode to 'read' the boot_a partition to extract it but forgot to change it to .img from .bin prior to Magisk patch it. Renamed the extracted file with .img extension, patched it again, flashed it back on boot_a and boot_b partitions and this time i have full root. Thanks again for your help.
But now I stuck with error:
all slots are unbootable!
tried to flash to boot_a and boot_b the original boot.bin without any luck.
please help, thanks.
Related
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
EdoIsa said:
I believe most of the programs there should also work for the ZF2. I would give this procedure a try, and I wish I could get my hands on a Bricked device to try this. But remember, DON'T use the ZF5/6 images!
Get the stock images for the ZF2 from: https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
Click to expand...
Click to collapse
What are FZ DnX, IFWI, FW DnX and OS images files ?
How to extract them from the site you mentioned?
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
I have no experience with FZ DnX, IFWI, FW DnX files, but the OS image file is on the site I posted.
Follow my link. Once there, expand the list 'Firmware' and download firmware Version WW_2.15.40.10. Once its downloaded, open the zip file. Inside should be a System.img file. Extract the System.img file into your Fastboot folder. This is the OS image the guide is referring to.
Ask around for the meaning of the other files. Meanwhile, I will research more about those files later tomorrow and get back with any info I can find. Good luck!
cde2006 said:
Another issue, is my PC refuses to regonise the ZF2 when connecting to USB, saying MTP Android USB driver failed to install....
Click to expand...
Click to collapse
install driver manually. see attachment.
When you plug your phone into the computer, does the phone show up in the device management? Typing devmgmt.msc into the windows 7 start menu or the start run menu on XP is the fastest way to get to Device Manager.
Is the device already known by your computer?
What does device manager think it is?
If its unknown, please let us know what the Hardware Ids and Compatible Ids for this device show up as. In device manageer, you can open the devices properties and under the details tab choose Hardware Ids and Compatible Ids. you could screen shot these with Alt + PrtScn and use mspaint to save them off. Otherwise you have to use Ctrl + C to copy them out . You can choose all lines by selecting the first and while holding Shift, select the last. Then you can Ctrl + C to copy all of them out.
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Chinaphonearena said:
Looks like you've flashed incorrectly.
Should be
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
What you've essentially done (or tried to do) is flashed over fastboot with 4 different images. Only the first line of commands you used is correct.
Click to expand...
Click to collapse
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
I think that avoiding flashing droidboot and recovery, and making sure file hashes match, everything should be fine.
Same issue
---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------
cde2006 said:
Dear All,
I hard bricked my ZE551ML 64GB by using the following sequence:
'fastboot flash fastboot droidboot.img'
'fastboot flash fastboot recovery.img'
'fastboot flash fastboot boot.img'
'fastboot flash fastboot system.img' <-- got error only at this stage
So don't do it it is totally wrong.
Now I got the usb logo when i go to fastboot, see attached image.
I can see a procedure for Zenfone 5 to recover from this error here:
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
My question is does the same procedure exists for Zenfone 2 and where to download all the files?
Thanks
Click to expand...
Click to collapse
I put my 64gb sd in my ZF2 that I originally partitioned for my LG Optimus Pro and I moved a bunch of apps to the SD with link2sd and the first time I rebooted, the same screen with the USB logo and a full progress bar showed up. It won't recognize any fastboot or adb commands even though the ASUS adb is showing up in device manager. Nothing else shows up. In devices and printers I get Moorefield. The phone randomly reboots and goes back to the same screen over and over and each time the asus adb disappears from device manager and then returns. I found a guide on the zenfone 5 that looks promising, using the intel flash tool, however it requires the ZenFone 2 raw firmware files and I can't find them... Hopefully someone could help me salvage my ZF2 cuz I was really beginning love the phone... Thanks ahead of time for anyone that looks into this for me!
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
sry, had only the files for V5. I will load down and put it here.
boot error and bricked zenfone 2
i have same problem with my phone please send moorefields or other intel based boot drivers.. tanks
please tutor how to fixed it, thanks for advice
cde2006 said:
Yes got this sequence from this forum,,, anyway I go the phone replaced now and all is fine.
Thanks people for the help.
I won't be rooting this phone until there is a more safe proven way to do it.
Click to expand...
Click to collapse
Lol @ "got sequence on this forum" and "more safe proven way."
You didn't read the instructions carefully enough and made a big mistake as a result. The correct sequence was given. You just didn't read it carefully. Lesson learned.
Hopefully you can unbrick it.
No offense, but this type of thing is what happens when people just copy/paste and don't understand what they're doing.
What you did was overwrite the fastboot partition each time you flashed. You flashed a 2GB system img on top of your fastboot partition. This probably seemed like it locked up and you either unplugged or turned it off. This likely caused a corrupt partition.
Reading is key when you do anything with your phone.
This is perfectly safe. This is the way it works for all devices. It has nothing to do with the files or the phone. This was 100% user error. Simple as that.
ze550ml hard brick
http://forum.xda-developers.com/zenfone2/help/zenfone2-ze550ml-hard-bricked-t3148174#post61657126
my ze550ml hard brick too. please help me
sorry for bad english.
hardbrick zenfone 2
konsolen said:
i can give you the files you look for. the easiest was is to flash with intel flash tool. Here you can read how th etool works and you found a link there.
I load your files up now here.
Click to expand...
Click to collapse
Hello, i have the same issue with my zenfone 2, I download the firmware files from Asus website, but the Intel flash tool can't found a flashable image file. My question is to, if you have the firmware files that send it to me?
same issues here please help,
same issues here please help,
Do you need to Upgrade or Refurbish in LGUP when moving to Pie?
X-Nemesis said:
I followed the instructions for updating via LGUP with the modded 1.14 version.
I placed the KDZ in the common folder and also extracted the .dll from that KDZ into the same folder, renaming it to LGUP_Common.dll, and replacing the version that was in there.
I then began the upgrade process which failed at 74%, and upon trying to load up LGUP again, I get the following error now.
DLL for 350AWM10i is invalid. Please, install valid DLL package(*.msi). for the model.
My phones screen says COM 10 and is stuck at 91%
Any suggestions?
Click to expand...
Click to collapse
Make sure you grant permissions to dll file you placed. Might be problem.
dave71670 said:
Make sure you grant permissions to dll file you placed. Might be problem.
Click to expand...
Click to collapse
Thanks, I'll try that out.
Another error I'm getting from LGUP at 74% failure is
Error: 0x2000, Invalid command response code = 0x80000001
X-Nemesis said:
Thanks, I'll try that out.
Another error I'm getting from LGUP at 74% failure is
Error: 0x2000, Invalid command response code = 0x80000001
Click to expand...
Click to collapse
Are you using the patched version of LGUP?
Shawnashley said:
Are you using the patched version of LGUP?
Click to expand...
Click to collapse
Yes, the latest development though is that I've lost download mode and the phone is stuck in fastboot. I'm now looking to see if there's a way to get download mode back using fastboot, but the V35 doesn't have root so not sure if that's a problem.
I found this thread, https://forum.xda-developers.com/android/general/unbrick-lg-model-download-recovery-t3060184
But since there is no AT&T KDZ available, can I use one of the Unlocked versions to restore download mode following that guide?
X-Nemesis said:
Yes, the latest development though is that I've lost download mode and the phone is stuck in fastboot. I'm now looking to see if there's a way to get download mode back using fastboot, but the V35 doesn't have root so not sure if that's a problem.
I found this thread, can I follow the instructions in this thread for restoring download mode using the Pie KDZ for Fi or Amazon?
https://forum.xda-developers.com/android/general/unbrick-lg-model-download-recovery-t3060184
Click to expand...
Click to collapse
I'm not ?% sure. I've never had to do that myself, so I have no first hand knowledge. Maybe someone else in the community has. Good luck though. If I find any info I'll surely pass it along.
Shawnashley said:
I'm not % sure. I've never had to do that myself, so I have no first hand knowledge. Maybe someone else in the community has. Good luck though. If I find any info I'll surely pass it along.
Click to expand...
Click to collapse
Thanks for that, this is a learning experience for sure.
X-Nemesis said:
Thanks for that, this is a learning experience for sure.
Click to expand...
Click to collapse
I'm assuming you have tried adb commands. There is a tool that may be of some assistance to you here:
http://forum.gsmhosting.com/vbb/f606/coming-android-multi-tools-v1-02b-special-gsmforum-1633070/
Hopefully, it helps. Good Luck.
Yeah I came across that program in my searches but didn't see any way to restore download mode. I'm still trying to locate how to restore download mode through ADB/fastboot. I'm definitely over my head in this one.
X-Nemesis said:
Yeah I came across that program in my searches but didn't see any way to restore download mode. I'm still trying to locate how to restore download mode through ADB/fastboot. I'm definitely over my head in this one.
Click to expand...
Click to collapse
Have you tried using Cmd prompts? Just a thought. You did say you are stuck in fastboot?
Yeah, it's stuck in Fastboot. From what I've read so far, the only way to get back into download mode is to reflash certain files, using ADB, from a partition file found in the KDZ but that's about as far as I've gotten. I'm also not sure if not having an AT&T KDZ is a problem and that I could use any of the other unlocked versions. But looking in the KDZ's I did download with the Extractor tool, I wasn't able to figure out which partition file I was supposed to extract the needed files from.
Need help
My lg v35 at&t stuck in fastboot mode
X-Nemesis said:
Yeah, it's stuck in Fastboot. From what I've read so far, the only way to get back into download mode is to reflash certain files, using ADB, from a partition file found in the KDZ but that's about as far as I've gotten. I'm also not sure if not having an AT&T KDZ is a problem and that I could use any of the other unlocked versions. But looking in the KDZ's I did download with the Extractor tool, I wasn't able to figure out which partition file I was supposed to extract the needed files from.
Click to expand...
Click to collapse
I believe it's the laf partition that contains download mode. I read somewhere around here that even a G7/V40 laf partition will work. Interesting that you can get into fastboot without getting someone with an Octoplus to flash the engineering boot partition. I wonder, if you had had the precognition to enable oem unlock, if you could unlock your bootloader now. That'd probably be too easy though.
Eric janaika said:
I believe it's the laf partition that contains download mode. I read somewhere around here that even a G7/V40 laf partition will work. Interesting that you can get into fastboot without getting someone with an Octoplus to flash the engineering boot partition. I wonder, if you had had the precognition to enable oem unlock, if you could unlock your bootloader now. That'd probably be too easy though.
Click to expand...
Click to collapse
I believe I did have that enabled yes, but as for how I'd unlock the bootloader I'm clueless. You've probably seen the big thread regarding unlocking the bootloader for the V35, and I seem to remember that nobody had had any luck yet. I'd probably blow the darn thing up lmao.
X-Nemesis said:
I believe I did have that enabled yes, but as for how I'd unlock the bootloader I'm clueless. You've probably seen the big thread regarding unlocking the bootloader for the V35, and I seem to remember that nobody had had any luck yet. I'd probably blow the darn thing up lmao.
Click to expand...
Click to collapse
Could it be as simple as fastboot oem unlock? It's not like people could even run that command since fastboot is normally disabled.
Eric janaika said:
Could it be as simple as fastboot oem unlock? It's not like people could even run that command since fastboot is normally disabled.
Click to expand...
Click to collapse
So I tried fastboot oem unlock but got the error 'FAILED (command write failed (Unknown error))'
X-Nemesis said:
So I tried fastboot oem unlock but got the error 'FAILED (command write failed (Unknown error))'
Click to expand...
Click to collapse
No such luck huh? I guess that would've been too easy. Can you try a different USB port, particularly a 2.0 (or 3.0 if you're already using 2.0)?
Eric janaika said:
No such luck huh? I guess that would've been too easy. Can you try a different USB port, particularly a 2.0 (or 3.0 if you're already using 2.0)?
Click to expand...
Click to collapse
Thanks for helping me out btw. Regarding this process, is it necessary when running fastboot commands that the phone is recognized in Device Manager (which it isn't)?
X-Nemesis said:
Thanks for helping me out btw. Regarding this process, is it necessary when running fastboot commands that the phone is recognized in Device Manager (which it isn't)?
Click to expand...
Click to collapse
When my V35 in fastboot is connected to my computer, it shows up under the category "Kedacom USB Device" as "Android Bootloader Interface". Is your phone recognized when you type "fastboot devices"? When I run that command, my output is "LMV350AWMb075fc5f fastboot".
I think I'm just spiraling down into a hole here. I was following some advice in another thread where I extracted the laf.img file and ran the fastboot boot laf.img And now the phone is displaying a 'Firmware Update' screen. The device still does not show up in my device manager.
But when I did type in fastboot devices it did show something similar to what you have there.
Hey all! Think I managed to bugger it nice and good this time. I have the verizon variant of this phone and recently unlocked its bootloader. I followed netookska5's guide to unlocked and ended up on G710VM20g with root. All seemed well so I went on to start playing with the firmware, specifically prodding at the way force encrypt is implemented. I found the contents of the ramdisk in boot_a were easy enough to modify and boot from temporarily using fastboot but then hit a bit of a roadblock.
After a reboot I found the bootloader played the verizon boot animation but didn't seem to have any incentive to continue past flashing the dots. I rebooted into download mode and reflashed the vm20g kdz in lgup, and still faced the same problem. I tried crossflashing to the ulm11g kdz I used to unlock the bootloader and faced the same issue there. Flashing back to vm20g yielded an odd result where the bootloader still doesn't make it into the initial setup but anytime when force reset with pwr + vol down the factory reset "erasing" animation plays before the bootloader tries to start again, regardless of if there is any data on the userdata partition. Flashing individual partition images extracted from the kdz over qfil doesn't provide any differing results.
I can't get any logs to see what's actually happening as enabling adb in the ramdisk doesn't do anything because the bootloader uses the usb port as "LGE AndroidNet USB Serial Port" in windows and is just as unhelpful under linux. I'm downloading another kdz to test as the other two were both android 9, but aside that I'm mostly out of ideas. It doesn't seem worth attempting to get the kernel to output the console over this serial port as from what documentation I've found its not likely the serial will even support console output. Anyone have any ideas? I can get into download mode, fastboot, twrp, and su shell through twrp.
So as a follow up to this, the vm10i kdz also doesn't work. Got a dmesg from twrp and the official laf in download mode, both boot without any issue so nothings really jumping out at me so far.
laf_a dmesg https: //pastebin .com/cbMxFGm8
twrp dmesg https: //pastebin .com/0mtq3jF2
The download mode serial only responds to the dmesg command and only serves its own log. Haven't found a way to communicate with the boot_a serial yet. Going to flash to em20b and give lineageOS a shot.
orbitalm99n said:
Hey all! Think I managed to bugger it nice and good this time. I have the verizon variant of this phone and recently unlocked its bootloader. I followed netookska5's guide to unlocked and ended up on G710VM20g with root. All seemed well so I went on to start playing with the firmware, specifically prodding at the way force encrypt is implemented. I found the contents of the ramdisk in boot_a were easy enough to modify and boot from temporarily using fastboot but then hit a bit of a roadblock.
After a reboot I found the bootloader played the verizon boot animation but didn't seem to have any incentive to continue past flashing the dots. I rebooted into download mode and reflashed the vm20g kdz in lgup, and still faced the same problem. I tried crossflashing to the ulm11g kdz I used to unlock the bootloader and faced the same issue there. Flashing back to vm20g yielded an odd result where the bootloader still doesn't make it into the initial setup but anytime when force reset with pwr + vol down the factory reset "erasing" animation plays before the bootloader tries to start again, regardless of if there is any data on the userdata partition. Flashing individual partition images extracted from the kdz over qfil doesn't provide any differing results.
I can't get any logs to see what's actually happening as enabling adb in the ramdisk doesn't do anything because the bootloader uses the usb port as "LGE AndroidNet USB Serial Port" in windows and is just as unhelpful under linux. I'm downloading another kdz to test as the other two were both android 9, but aside that I'm mostly out of ideas. It doesn't seem worth attempting to get the kernel to output the console over this serial port as from what documentation I've found its not likely the serial will even support console output. Anyone have any ideas? I can get into download mode, fastboot, twrp, and su shell through twrp.
Click to expand...
Click to collapse
the ramdisk in boot is not the os ramdisk its the recovery ramdisk the , ramdisk in root of the /system partition
J0SH1X said:
the ramdisk in boot is not the os ramdisk its the recovery ramdisk the , ramdisk in root of the /system partition
Click to expand...
Click to collapse
huh, actually thinking about it this makes a world and a half more sense. In my head I was thinking about a linux kernel using an initramfs on a shared boot partition and then only later switching roots. Since the system_a image doesn't have the usual kernel headings and is just an ext4 image, I have to assume the bootloader loads the kernel from boot_a and then decides which partition gets put on the root? Thanks for the tip off though!
Somewhere between vm11g, em20b, and vm20g with a little fumblery inbetween I ended up in the initial setup again. Don't know what survived flashing but got fixed by a certain crossflash, gremlins probably
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
durrant111 said:
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
Click to expand...
Click to collapse
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
you can fomat data : - and power before click power
durrant111 said:
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
Click to expand...
Click to collapse
Boot to EDL mode by holding the vol - and power button while your G8 is plugged in your computer, after you hear a disconnection sound immediately press the vol + until you hear a connection sound from your computer.
Now, open QFIL then look for the abl a and b then flash your backed up abl_a nd abl_b accordingly and reboot. And you're good to go again.
I can help you. Do you fix problem ???
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Anybody?
Ratty696 said:
Anybody?
Click to expand...
Click to collapse
.
Ratty696 said:
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Click to expand...
Click to collapse
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
Used method in beginning of this thread. Tried flashing backup
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Ratty696 said:
Used method in beginning of this thread. Tried flashing backup
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Click to expand...
Click to collapse
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
armodons said:
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
Click to expand...
Click to collapse
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Ratty696 said:
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Click to expand...
Click to collapse
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Nobody able to help me?
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
I'm new to the G8 (not LG), so just now browsing these posts.
First and foremost, this thread shouldn't be in this forum. This forum is for roms, kernels, recoveries and other development.
This thread is a question about a guide (which is in guides forum). This 'question' is not development of a rom, kernel or recovery, it's a question.
I'd suggest, if you want people to respond that can help, ask the question in it's individual guide thread, that's where the people that know the most about it will be. If you get no response in that thread, then maybe think about posting the question in the questions forum.
but here? in dev forum? absolutely the wrong place for a question about a guide.
cheers
Thread moved to Q&A section.
Thanks!
woodman
Senior Moderator
@durrant111
So to the original OP; 2 things; If your device isn't recognized when in fastboot mode, that's because you don't have the right driver installed in WinBlows.
You have to download the LG USB drivers, install them, then in device manager select the "! Android" and install the driver (usually says ADB) and then 'fastboot devices' will see the phone.
Second; if you ever get a message telling you that 'Data Overflow' then you are absolutely making a big mistake. When you did the backup of your abl(s) (and other partitions), you should have renamed then one by one, that way you don't make the mistake of naming the laf_a partition as the abl_a partition (or any name other than what ti should be). If you flash the wrong partition you run the risk of overwriting the nearby partition, which would make the device essentially unusable except only to qfil.
Lastly, yer lucky the device is VZW, as they make their kdz available and you can use use lg up to get back to stock. If it was Sprint or At&t you'd be scrambling to find a qfil or bkerler backup someone luckily made that you come across (a much more unlikely scenario).
Good luck, you've probably already moved on from this, but just in case, thought I'd mention the above.
cheers
Ratty696 said:
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Click to expand...
Click to collapse
Unfortunately at&t doesn't make their kdz available. You can be 99.9% positive the only thing this person that wants to charge you 30$ is going to give you is the partitions backed up by qfil or bkerler edl stuff.
With both at&t and sprint, because no kdz, you can only restore (if you didn't back up the files yourself originally), with someone elses backup, and then you have to use qfil or bkerler edl utilities to restore. If you look around in the G8 forums (or the tele group), there's a decent chance someone has already make their backup available.
cheers and good luck.
Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Yarib said:
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Click to expand...
Click to collapse
Lol no still haven't solved my problem. I need the abl_a and abl_b files for a lg g8 at&t. My phone only goes in fastboot or qfil and Fastboot says its a lmg850um because I tried using the files from my lg g8x and it didn't work. I have also now bricked my lg g8x it only boots into qfil. Any help would be great. My g8x is canada version
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro.
This message was removed on OOS 12 which was one great thing by OP other than the other broken parts.
So this guide is for OOS 13 not 12 as the message was removed on 12.
But OnePlus brought the message back on OOS 13.
IMPORTANT:
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested.
The methods have been tested
Prerequisities:
You need a unlocked bootloader
YOU NEED TO HAVE THE STOCK RECOVERY INSTALLED
If you're on a custom ROM that'll be the ROM recovery
This is XDA thread and abl.img is only for the OnePlus 8 Pro, but this method has worked for 8 series devices.
You need to be on OOS 13 and have your bootloader unlocked.
The abl.img doesn't rely on the region so it can be used on any OP8 Pro
The abl.img can be extracted using payload dumper, but download the full zip version.
I have added abl.img from OOS 13 F.10 as this is the newest abl.img that has the message removed and is from @bowow
It is recommended to backup your data before modifying anything on your system
Follow one method and stick to that method
Each method is different where one is for Stock OOS 13 and the other is for OOS 13 based Custom ROMs
Method:
Download the abl.img
Copy and paste the abl.img to platform-tools
If u don't have platform-tools, download the .zip file from download links and extract it
For Stock OOS 13
This method was tested and is from @MeHigh.G
This is for on Stock OOS 13 users
Reboot to bootloader
Type " fastboot devices " to check if your device is connected
Type " fastboot reboot fastboot "
Once booted into Fastbootd Mode, type " fastboot devices " to check if your device is connected
Then type " fastboot flash --slot=all abl abl_filename.img "
Now reboot device and done
For OOS 13 based Custom ROMs
This method was tested by me and it does work
This is for OOS 13 based ROM users
Reboot to recovery
Enter advanced
Enter fastboot
The recovery should now show fastbootd
Type " fastboot devices " to check if your device is connected
Type " fastboot flash --slot=all abl abl_filename.img
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
MSMDownloadTool for OP8Pro Here
Bowow's OnePlus Firmware Updates abl section Here
OrangeFox Recovery for OP8+OP8 Pro ext4 erofs
OFox Install instructions Here
OrangeFox Community Telegram
Credits:
@HELLBOY017 For the method and using abl.img to remove the bootloader unlocked message
@MeHigh.G For his method on flashing abl.img on stock OOS 13
@bowow For this F.10 abl.img for OP8 and 8 Pro
reserved
Updates
21/11/22 - Released the XDA thread as a guide to remove the ugly "Your device has been unlocked" message for the OP8 Pro
Not sure if this method does work, but I have contacted ROM developers and they say this is the way...
I'm currently not on OOS 13 based ROM, so I can't try and hopefully this does work
21/12/22 - It has been a month and after checking with devs + testers the method does work!
I have tested the method myself
I have updated the method as there's new steps you need like flashing abl.img in both slots
But the method does work on OOS 13 based ROMS! The message can be removed!
22/12/22 - I have found the method that works on Stock OOS 13 thanks to @MeHigh.G
Stock OOS 13 users should be able to remove the bootloader unlocked message
Added new OOS 13 F.10 abl.img file and removed OOS 12 C36 abl.img due to F.10 being newer to ensure users have a newer bootloader
Credited Bowow for giving the F.10 abl.img file for OP8/8 Pro
5/1/23 - Updated methods to flash abl.img in both slots easily instead of flashing abl.img in one slot
Changed "fastboot flash abl abl.img" to " fastboot flash --slot=all abl abl_filename.img " which will flash abl.img in both slots.
For custom ROM method, you will no longer need to reboot and switch slots with the new command
Nice!
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
gregpilot said:
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
Click to expand...
Click to collapse
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
ShadoV90 said:
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
Click to expand...
Click to collapse
That's for the OP9 Pro not the OP8 Pro...
I only learned about this from the dev @HELLBOY017 and it worked for him. He never stated u needed a data wipe.
So I did check that it was working otherwise I would never post something that wouldn't work and wasn't tested.
And I did say.... *I am not responsible for bricked devices, damage to your device* I am here to post my method for anyone who is interested.
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
We'll see how it goes as this is new for 8 Pro users and hopefully it does work
Thanks for the reminder of the missing info to include
Extreme_Ninja2099 said:
That's for the OP9 Pro not 8 Pro...
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
Click to expand...
Click to collapse
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
ShadoV90 said:
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
Click to expand...
Click to collapse
Never considered it as an attack, just posting to clarify where I got this info and everything from.
I only found out about this yesterday from Hellboy017 and it worked for him.
I would recommend this only for users on OOS 13 just to be safe
If something does go wrong, follow the link by @ShadoV90
Do a factory reset or use MSMDownload Tool
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Neil_Armstrong_ said:
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Click to expand...
Click to collapse
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
the flashing unlock_critical output is the fastboot help, i guess it's not working
I will try again saturday on Linux to see if it helps
ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
MeHigh.G said:
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
Click to expand...
Click to collapse
Nice feedback, can you share what custom recovery you use on OOS 13 ?
so this work or not?
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
There's no custom recovery currently for OOS 13... Only for custom ROMs
Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
I use oFox or the one provided with Flamingo OS or Pixel Blaster
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
STALKER18 said:
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
Click to expand...
Click to collapse
I've already extracted it for the 8 pro... Up to u
For step 4 it's fastboot flash abl abl.img
i'm unable to unlock bootloader says command not supported in default implementation.
IN2021 One plus 8 pro.