Develop Bugs

System corrupted, laf removed, fastboot doesnt work, stock recovery is useless.

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

Tied everything to root swift, cant get past initial fastboot stage

hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!

yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev

I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'

yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev

unlock error

hello
got the new version of Android (oreo).
I did the installation using adb. Once installed, the phone did not boot. Rebooted on the Google logo.
Now I can not do anything, Because it is not oem unlock and then I can not unlock the device, to flash again.
When using adb, I use adb devices, the device does not show me, but the fastboot devices I use show the serial device.
I searched and searched all the necessary possibilities in this case and did not know the driver, and apparently there was no problem.
Anything I want to do is require oem unlock and when I put this command in adb. It looks like:
FAILED (remote: oem unlock is not allowed).
And I can not do anything.

"Start Up Failed" after flash

Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of ​​what to do?
Tks!

riickseven said:
Hello friends
a friend brought me a Moto G7 Play (XT1952-2), and said he had forgotten the password, the email and all, to try to recover, he tried to flash, but did not unlock the bootloader, did not enable USB debugging and did not enable OEM unlock and yet downgraded on mobile.
The result is that the phone no longer leaves the Start Up Failed screen, it shows the following messages:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
I already tried to unlock the bootloader, but as the OEM unlock option is not enabled, I could not. I tried to flash with the same rom as before or with a more current one and it didn't change anything either. I've tried basically everything I found in the forums. Can someone give me an idea of ​​what to do?
Tks!
Click to expand...
Click to collapse
Download Your Latest ota zip from
https://mirrors.lolinet.com/firmware/moto/channel/official/
then flash via rsd lite that will fix your phone and reset it

Help download
motorola/aljeter/aljeter:9/PPPS29.55-35-12-3/a0b9b:user/release-keys

Bootloader problems

Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone

You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.

Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks

chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.

Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.

If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion

type fastboot devices and show me the result.
maybe you do not have correct fastboot driver

It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable

Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice