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
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,
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Screen right after fastboot boot:
[500] Fastboot mode started
[600] -- reset --
[610] -- portchange --
[710] fastboot: processing commands
fastboot erase aboot brings:
erasing 'aboot' ... on command prompt
and
[346290] fastboot: getvarartition-type:aboot
[346350] fastboot: erase:aboot
after those appear it just hangs like that
unplugging it after that command gives me:
FAILED (status read failed (Too many links))
finished. total time: 164.350s
on cmd
and
[514820] -- reset --
[514820] EP1/out FAIL nfo=40 p0=f90bao0
[514830] -- portchange --
[514840] usb_read(0) transaction failed
[514890] fastboot: oops!
[514940] fastboot: processing commands
Click to expand...
Click to collapse
Did you ever find a fix for this?
No, its either professional jtag, or maybe the MM stock ota update zip will fix it if it includes the linker. i havent found this ota on the Internets yet though.
i just had the same problem. any fixes?
flash laf via fastboot
sirbow2 said:
Alright here's the story. I was trying to put CM on this rooted LP 5.0.1 tmobile d851 (20e i think). I backed up and removed the LAF in order to access fastboot so i could flash the custom recovery. fastboot would send the recovery, but the phone would never actually flash the img to the device and report done. Even "fastboot reboot" did nothing. "fastboot devices" reported the serial as "?" and no driver or Arch/CentOS/other windows installs would get fastboot working. fastboot showed up as Marshal london bootloader in device manager.
So then i tried using flash_image from inside of rooted LP to flash the recovery however i ran into PIE errors that could be fixed by replacing /usr/bin/linker. So I found a patched version, rm -rf the old one and tried to cp in the new one. This seemed like a totally valid idea from my linux experience. Buuuut crap. Nothing works. No commands are accepted because I deleted linker. I rebooted cause I had no better alternative and i get a dead android "no command".... Looks like I found the single best way to kill an android installation.
Now im really stuck because i cant use download mode (LAF) to restore because it has been deleted to access fastboot and fastboot wont actually do anything so I can't restore the laf. There is no custom recovery. The stock recovery adb sideload will only let me install OTAs and far as i know there isn't a FULL OTA that will restore the entire system. I even tried the qualcomm 9008 hard brick method with boardDiag, but that doesnt work on tmobile.
I see a few options:
Somehow get fastboot and then download mode working
Wait for a 6.0 OTA and hope it updates the linker bin
advise?
also, the LG logo appears on screen and the LG serial port (the one used for the LG flasher tool) is present in my device manager for a good 15secs before the no command android shows up. I tried lg flasher tool with this time window but it always cut out before the tool could get anywhere.
Edit: This is what the fastboot process would look like:
Click to expand...
Click to collapse
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
thanks for the reply, but as i mentioned in my post, fastboot commands don't work. i wish it was that easy.
nibedankaran said:
download laf file for your model and flash it....
"fastboot erase laf" then
"fastboot flash laf laf.img"
"fastboot reboot"
Then try to put your phone into download mode.
Click to expand...
Click to collapse
I think you have a serious problem
You have to see google fix lg g3 on Qualcomm mode...I mean hard brick fix....
Download as instructed
I think it will be fixed
Recently I fixed lg g3 from only led blink no signal to pc and only vibrate and others
That doesn't work on tmobile G3s, thanks though. I did try it anyways btw.
Getting the update.zip from a friend. its in the SD card but its not showing up in MTP so were trying to figure that out. once i have the zip ill try flashing it. if it doesnt work, itll get a octoplus jtag flash.
Well the update did not like the fact that this phone was missing the linker bin or the previous root because it fails when checking the current system. Looks like octoplus is the only way cause i'm an idiot.
Anyone know where i can send this to get it done? i thought some people on ebay did it but i cant find them.
I have same problem, no download mode, system corrupted and recovery is useless.
mysteryjeans said:
I have same problem, no download mode, system corrupted and recovery is useless.
Click to expand...
Click to collapse
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
sirbow2 said:
If it's a tmobile G3 (d851) you have no choice but send it to someone for an octoplus jtag service because the DIY jtag method doesn't work. Got mine done for $42 after shipping from an ebay service.
Click to expand...
Click to collapse
Finally I recovered it, I have to short testpoint then connect cable to PC, my device is dual sim therefore different logic board, see this http://forum.xda-developers.com/lg-g3/help/lg-d858-qualcomm-test-location-t3293440 for D856/7/8 testpoint to get device into Qualcomm 9008 mode, then I had flash F400K (yes korean rom) tot from thread http://forum.xda-developers.com/showthread.php?t=2785089 using BoardDiagv2.99 http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 to get it live and get into download mode.
Now finally flashed stock KDZ using this post http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
If I knew there is new tool to flash MM stock, I wouldn't brick my device. :silly:
Thats exactly what i tried but didn't work because D851
Good day mate. My brick phone is F460S variant. I got this error when I tried to go back to Lollipop using Lg flash tool 2014, it got stuck on 5% and remove usb cable and start again, after that I got this error Secure Booting Error! Cause: boot certification verify.
No download mode
No recovery
anyone can help me please?:crying:
anyone?
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
西村大一 said:
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
Click to expand...
Click to collapse
What does QFUSE mean?
anmino said:
What does QFUSE mean?
Click to expand...
Click to collapse
I second you on this. I just uninstalled MultiROM and got the secure booting error. Depending on the ROM you have, find a bumped kernel and flash it. Most of the kernels on XDA are pre-bumped unless the developer states so. Boot into recovery, tutorials on the internet, then flash the kernel and voila.
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
HardStyl3r said:
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
Click to expand...
Click to collapse
Yes, no DOWNLOAD mode and RECOVERY mode.. Anyone have an idea how to fix this?
anyone?
Hello, i got the same probleme and i've trying a lot of things but not resolved..
My phone is a LG G3 Beat F470s..
Please help us..
Dowblnload adb and fastboot drivers
Download laf.img for your device
Download LG Drivers
Get you G3 to fastboot mode. Hold volume up and connect it to PC
Open fastboot and adb folder in PC, ctrl+shift+right click and open cmd. Type fastboot devices...if ur device is listen then proceed, if not u did not do something cotrectly...if yes just flash laf img to your G3 and voila
I remember me that I was in the same situation:
No TWRP, no download mode, so i have use in pat this thread:
https://forum.xda-developers.com/showthread.php?t=1752270
And an other that i haven't found again (xda thread), in some lines:
=> download the last img file from: https://eu.dl.twrp.me/d855/
=> no download mode available so no possibility to flash manually twrp file from an LG Flash Tool
==> so setup an adb connexion to the phone, cp command to copy the img file on the sdcard or where you want
=> command: "flash recovery twrp-2.8.x.x-xxx.img" (https://www.xda-developers.com/how-to-install-twrp/
=> if it's as worked, you could reboot manually in twrp, make again the partitions if needed and flash any ROM.
Mine motog5s updated to stock fw and root uninstalled after it it hangs on boot screen. I flashed stock fw again with fastboot but after restart mobile didn't display anything not even vibrate just blinking notification when connect usb wire . how to unbrick only shows qualcomm hs dloader 9008 what to do, pls. reply.
You cannot log into fastboot mode?
qualcomm hs dloader 9008 = EDL mode, you should be able to restore with QFIL: https://forums.lenovo.com/t5/MOTO-E-1st-Gen/Moto-E-Not-Boot-Up/td-p/3231144 but it looks like motorola doesn't provide the files ... most likely you'll need a service center
Do not use QFIL. To unbrick, we need the blankflash file for G5S. And it is not on the Internet yet. Do not use the blankflash of any other models. Your best bet is to take the phone to a service center.
---------- Post added at 11:46 AM ---------- Previous post was at 11:46 AM ----------
Did you try holding the power down button and turning on the phone to enter bootloader?
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
ASHDCBZ said:
Thanks for the reply the service center guys sayin as bootloader is unlocked out of warranty. They said mobile is rooted without checking the mobile as its not turning on, how they can say that its rooted . They just talking on phone with other persons but cant provide any solution what can be done.
Please provide any other solution.
Click to expand...
Click to collapse
You downloaded the unlock key from Moto website by giving them your device serial number. That's how they know you unlocked bootloader. Service center won't help you. But fortunately, there is a way to revive your phone. But I'm not getting the blankflash file anywhere.
Tell me what exactly did you do to your phone.
Thank you,
Ok I just flahsed & tried stock roms, root & custom roms. Then I flashed stock rom of mine region firmware npp26.102.19 then motorola gave the updates to npp26.102.55-1 Dec. patch. Then next day new update came Feb patch npp26.102.55-4 just after it mobile started hanging & when restart it stuck on boot, not booting just stuck on boot animation. I tried TWRP recovery it said encrypted then I entered the unlock pin then it shows all the folders. Then I again fastboot npp26.102.19 to solve the issue but after flashing & restart it did not boot nor screen on no vibration tried several times but no response, when connect with pc or charger a white notification light blinking only & it detected as QHUSB_BULK something like that then I searched for it & install driver then shows as qualcomm dloader 9008.
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
ShattrdChain said:
Ok you should never flash an older bootloader over never one. It's a classic mistake that you made. I suppose we need the blankflash file to repair your phone. Let's wait to see what senior devs say.
Click to expand...
Click to collapse
Hmmmmmmmm
Please provide blankflash soon file I'll try.
there is no notification light on my g5s. what is blinking on yours?
Andrew Joseph said:
there is no notification light on my g5s. what is blinking on yours?
Click to expand...
Click to collapse
Next to front flash right side a white light is blinking. Try pressing power button then it will show.
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Andrew Joseph said:
nope. can't find it. the g5s plus has a 'secret' notification light. can't find anything about the g5s having the same.
what phone do you have?
Click to expand...
Click to collapse
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
does this only happen when you root your phone?
Can someone Help Us?
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
brunovsc said:
Hey, i have unlock the bootloader of my phone and flash the updated rom in my device. After that my phone is just off, i press the power button but it don't turn on, connect do pc or chargers but it not turn on, that is the hard brick, can i have a solution to this?
I have this:
"The Hardbrick tutorial you always craved for
Let's get some things straight
Forget flashing stock firmware anymore this makes permanent changes to your phone's firmware but this is the only thing that will resurrect the fallen lad
Requirements
Albus blankflash
Qualcomm drivers
Adb and fastboot
Bootloader from Albus
Steps
Get the Qualcomm drivers installed… make sure you disable Driver Signature Enforcement for your windows version
Run the script in albus blankflash to get into a dummy bootloader
Now flash bootloader and partition files and recovery from addison2potter.zip
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash recovery recovery.img
Now try flashing a stock firmware it will flash but you will not be able to boot right now
Now flash or boot TWRP recovery
fastboot flash recovery TWRP.img
fastboot boot TWRP.img
Now flash the debloated stock ROM or the TWRP Flashable stock build by Gtrcraft
(This is needed to get RIL back )
You should be able to boot into the stock ROM now
Now you can go back to TWRP and flash any ROM of your choice ".
But i don't know if it will work, because i don't know if this files can match my model: moto g5s xt1792
And sorry but i can't post links yet.
Please Help Us.
Click to expand...
Click to collapse
Yes tried this & other blank flash it show only this-----
Failed identify board. Wrong package?
ERROR: error loading package
FAILED: qb_flash_singleimage()->error loading package
other tried this also----------
Found this can anyone try
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
qfil also not flashing sahara error.
I have tried this but there's an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
ASHDCBZ said:
Its Moto G5s XT1795.
when you connect your device with PC what driver it shows fastboot, ADB or mtp or else QHUSB_BULK qualcomm dloader 9008.
Click to expand...
Click to collapse
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
brunovsc said:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
em QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
em QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Same error shows in Qfil.
Andrew Joseph said:
i haven't tried to root or connect via adb or anything else. my phone is just plain stock from factory.
Click to expand...
Click to collapse
So is it not switch on or displaying anything.
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.