Database Develop

[Q] A few Q's about factory cable & un-soft-bricking.

Hey all,
So I have few questions about using the factory cable to fix my soft-bricked KFHD. If you want to read what I did to mess it up and what I've tried so far that's here in this thread but the TLDR is that I messed up my rooted kindle, won't boot, won't show up when plugged in (presumably ADB is off now) and so I ordered a factory cable from SkOpRn. I should get my cable today/tomorrow and I had a few questions before I start blundering about like a bull in a china shop. I've tried to read all the relevant threads here but some of the information seems conflicting/unclear. Here are my two clarification questions:
1) As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
2) I was running 7.2.3 before things got messed up, so once I am able to get it to accept fastboot commands do I use kffirstaide to actually do the restore (Option 4: Completely Restore the KFHD 7.2.3)? I'm thinking along the lines of this guide here and using "Option 4" in "Step 16".
I'm probably over-complicating things but I hate to make things any worse by doing something wrong.
Thanks!

MightyBraeburn said:
As I understand it, by plugging the device in with the factory cable I should be able to force it into a fastboot mode that allows me to issue commands. Assuming this works, do I continue to use the factory cable for the restore process or is the cable just a one-time "plug in" after which I use the standard cable to restore?
Click to expand...
Click to collapse
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).

With standard cable.If the device is recognized by adb then you can use this command:
Code:
adb shell su -c "reboot bootloader"
See the status kfHD have fastboot and you can go from there .

psych0phobia said:
The fastboot cable is just a trigger. It tells the device to start up differently by powering a pin that does not normally have power. Once you see the fastboot screen, I recommend changing back to a normal cable. You really don't want that extra power hanging out ready to wreak havoc if there's any unexpected fault in the cable (especially if you got one from a random person on eBay).
Click to expand...
Click to collapse
Agreed once in fastboot u can user standard kindle micro USB cable also if your kindle is recognised in any way by your PC in device manger even if its an unions p unknown device u should be able to voice force install the drivers for it if u need help and this is the case pm me
Sent from my KFTT

I don't know about kffaide but the restore tool in the dev section claims it replaces the boot loader when you flash 7.2.3
Sent from my GT-P3110 using xda app-developers app

Thanks everyone all for the help! In case anyone else stumbles across this thread with a similar problem, let me summarize what I did to fix my KFHD7:
1. I used SkOrPn's factory cable to get the device into fastboot mode (I just plugged it in for a few seconds until fastboot came up and then switched to the standard USB cable).
2. Once in fastboot mode it was detected by my computer with no problems and I could issue fastboot commands.
3. As soon as I could issue commands I took no chances and used kffirstaide to flash 7.2.3. kffirstaide must provide the stock image because it installed and rebooted fine except without root. I do remember seeing somewhere in a dev forum an image of 7.2.3 that came pre-rooted but I couldn't find it easily. Since I had already rooted it once before it was no big deal to root again.
I can't believe I went from a soft-brick (not even being detected via usb) back to normal so easily! Thanks again for all the help and suggestions!

Cant`t boot, blinking led.?

Hello.
I`m new to this development world, so i`ll try to describe what i did(P7-L10, EMUI 3.0):
1. I rooted the phonewith RootGenius, RootChecker confirmed.
2. I tried to unlock the bootloader with "EZ UNLOCkER", the status remained unknown, but it said(in the middle of the screen, small note) that the "device is now unloced" or something like that.
3. Then I tried to enter recovery mode (switched the device off, then pushed volume up, volume down and power button together, but it didn`t even show the Huawei logo or vibrate, the only thing it did: it blinked its led: red, green, green, red, green, green etc.)
What have I done and how can i get it back working?
Best wishes,
Uku.

Well, didn't you bother that EZ unlock is for Galaxy S3 phone???
You have bricked your device. Bring it to service. I presume, they will offer replace of system board, I hope warranty is not over yet? Otherwise the repair price will be comparable to device cost.

oh well, thank you. Took it to warranty and told them i have no idea what happened (update failed ors.) They accepted it even though there was crack on the back side. Lets see

Its not briked..
Try to put it via USB cable on a PC. Then wait......after 15min disconnect it. Then try to bring it up into fastboot mode and flash bootloader.img via fastboot.

87insane said:
Its not briked..
Try to put it via USB cable on a PC. Then wait......after 15min disconnect it. Then try to bring it up into fastboot mode and flash bootloader.img via fastboot.
Click to expand...
Click to collapse
It won't help.

It would...i had the same after an failed flash.

In case of boot image, yes it would, but not in case of other. But I doubt very much that EZ lock touches boot.

He can try it... Better than a new phone. I dont know what EZ does in detail. But if he can put the phone on, he can reflash it and all will be good. If not and the phone still not show anything - bye bye p7.

Need help to relock the Razer Phone 2 bootloader.

Hi, Im kinda new to this bootloader thingy. What happen is, i updated the razer phone 2 to Pie, but notice wifi and sim card cant be detect. Even factory reset fails. So i thought of flashing new image on it. KINDA easy on my oneplus, but im not sure where I gone wrong on this razer phone 2, i accidentally unlock the bootloader. NOW the problem is HOW to relock it back? i been follow all youtube and guides all over the place but still fails.
The state of device atm, cannot be boot into Download Mode. Everytime I plug in usb c from Windows, it will boot into unlock bootloader warning page, and continue boot into the homescreen. testing the adbtools, fastboot also to no avail. Can anyone help and guide me how to relocking it back? Maybe i type wrongly on cmd or maybe other android steps not similar to razer one etc....:crying:help much appreciated.

Hold volume down while turning on. Then fastboot flashing lock.

the stock usb doesnt send things correctly in BL mode, https://www.amazon.com/Blackweb-3-Foot-Charge-Cable-Connector/dp/B07SG7P3KZ/ worked for me. with the correct usb cable you should be able to perform the lock commands correctly. can you give us more detail of what you tried on this phone so we know if we need to provide you additional information?

https://developer.razer.com/razer-phone-dev-tools/general-instructions/
"Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot."

I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.

The_Vinlander said:
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
Click to expand...
Click to collapse
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.

Reznor7 said:
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Click to expand...
Click to collapse
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical

The_Vinlander said:
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
Click to expand...
Click to collapse
You need to go into your device manager and select [ android bootloader interface ] while in fastboot

Fastboot - waiting for any device

I'm a newbie at this but managed to stumble through installing CM 14.1 on my LG G2.
Phone: LG G2 VS980
CyanogenMod version: 14.1-20161207-unofficial-phoenix-vs980
Kernel version 3.4.0-crdroid-g0f70b4b
TWRP v2.8.6.3 (I don't know how this version got installed, I started out with a 2.7 version and upgraded to a later version but this is the version I see after I got CM installed).
Latest version of ADB and Fastboot from the platform-tools download.
I'm trying to make the phone automatically turn on when plugged into a charger using the " fastboot oem off-mode-charge 0" command .
ADB commands work fine.
If I issue the command "adb reboot bootloader" when the device is booted in CM I get rebooted into a black screen with the following:
"Firmware Update Do not unplug the USB connection until the process is complete." There is a progress bar that remains at 0%.
Any fastboot command I issue returns "waiting for any device". I have to hold down the phone power button for several seconds to exit this screen and then the phone reboots normally.
If I issue the "adb reboot bootloader" command when the phone is in TWRP or I select Reboot - Bootloader from TWRP the phone just reboots into CM.
What am I doing wrong?
Thanks

I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.

NTGDeveloper said:
I'm not too familiar with this phone, but all that I know is that it is in download mode, which is not the same as a bootloader. As a lot of android phones aren't the same as each other, I am not aware of how to boot into a bootloader of this phone.
I will say though, if it is anything like a Samsung phone, then it probably does not have a bootloader and the only way to interface with this mode is through the LG Flash tool found here: https://lgflash.com/LGUP/
Don't take my word for it, but it is possible that this is the case. Again, I don't have any idea how the phone works or anything, but this is possibly the solution.
Click to expand...
Click to collapse
I believe I'm in download mode when I'm seeing the black Firmware Update screen. I'm not trying to flash a ROM at this point so I don't think the LGUP program will be helpful.
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.

RKCRLR said:
If there is a another way to get my phone to turn on when power is applied to the USB cord I'm open to it.
Click to expand...
Click to collapse
Perhaps by modifying whatever starts when it's charging.
Charging animation for example...

The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.

Any fastboot command I issue returns "waiting for any device".
Click to expand...
Click to collapse
1st thing of all things in order to run Fastboot commands is you have to run command
Code:
fastboot devices
what establishes the USB connection. As long as the connection isn't established Fastboot throws message "waiting for any device".
BTW:
Booting into device's bootloader ( FYI: each device has a bootloader ) requires in addition to the well-known Fastboot driver the Android USB Driver got installed, too. This driver is OEM ( brand/model ) specific, you have it to obtain from OEM - mostly offered on their website.

jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...

jwoegerbauer said:
The meaning and purpose of Download mode, Bootloader mode and Fastboot mode are same.
Click to expand...
Click to collapse
The way I get into download mode is to hold the volume up button and plug in the USB cable with the phone off. When I do this I briefly see a screen that says Download with a blue hashmarked bar below it. It then goes to a screen that says "Firmware Update Do not unplug the USB connection until the process is complete." with zero percent progress.
Should I be able to issue fastboot commands when the phone is at that screen?

RKCRLR said:
Should I be able to issue fastboot commands when the phone is at that screen?
Click to expand...
Click to collapse
Nope.

CXZa said:
Not the same really - and LGs aren't Samsungs, or whatever either...
One maybe could try emptying LAF partition ("nuking"). Some more drastic ways also suggest it for boot as well. But IDK, is it worth the trouble really? And even if one could get into the fastboot, that command might not work after all...
Click to expand...
Click to collapse
I'm trying to repurpose the phone as a dedicated Android Auto "server" and would like to be able to leave it connected to my car. It would be really useful to have the phone turn off when there is no USB poser and turn on when there is USB power.
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?

RKCRLR said:
to have the phone turn off
If I make a backup of the Boot and System partitions within TWRP would that allow me to restore my LAF if I nuke the LAF and something goes awry?
Click to expand...
Click to collapse
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.

CXZa said:
>to have the phone turn off
Could it be there some app for such? IDK, maybe...
>If I make a backup
Nope again, The LAF has a partition of it's own. To backup use lglaf.py or LGUP having the dump option enabled or extract it from kdz if available.
Click to expand...
Click to collapse
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?

RKCRLR said:
This is probably a bridge too far for my skill level.
Is there a work around like putting it into a deep sleep that will let the battery to last for days or weeks but wake up when the USB has power?
Click to expand...
Click to collapse
There's probably a way to do this via root and there will probably be some app that lets you do this. Other than that, you'll have to dig around and see what you can find.

Thread cleaned and moved to Verizon LG G2 section

[FIXED] Fastboot? Recovery bootlooping, but never getting there

Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?

you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock

The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(

frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.

hey guys follow this youtube
managed to unbrick my phone

smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..

This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!

the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus