I was just wonderin i got a fastboot cable comin in in a week for my kindle hdx. To twrp and root it. Just wonderin if anybodies tried one on the g4 yet
Android does not require a special cable to enter fastboot.
I've personally never heard of anything called a fastboot cable, a quick google search shows a kindle factory cable... obviously amazon have done something to prevent fastboot over a standard microusb.
Fastboot on G4 is easy to access by enabling OEM Unlock in the developer options and then rebooting into the bootloader. Doing anthing with fastboot however depends on the unlock status of your bootloader. A Locked bootloader will simply reject any useful fastboot commands.
OllieD said:
Android does not require a special cable to enter fastboot.
I've personally never heard of anything called a fastboot cable, a quick google search shows a kindle factory cable... obviously amazon have done something to prevent fastboot over a standard microusb.
Fastboot on G4 is easy to access by enabling OEM Unlock in the developer options and then rebooting into the bootloader. Doing anthing with fastboot however depends on the unlock status of your bootloader. A Locked bootloader will simply reject any useful fastboot commands.
Click to expand...
Click to collapse
There's a particular dongle that you plug in to the MicroUSB socket and when you turn on the phone it's supposed to boot straight into fastboot mode.
Not sure whether these boot the G4 into Fastboot mode - being able to boot straight into fastboot without having an OS installed would be a real boon.
Does the device not already boot straight to the bootloader when there is no OS installed. i would have thought the boot process would get stuck in the bootloader with no OS.
dontpannic said:
There's a particular dongle that you plug in to the MicroUSB socket and when you turn on the phone it's supposed to boot straight into fastboot mode.
Not sure whether these boot the G4 into Fastboot mode - being able to boot straight into fastboot without having an OS installed would be a real boon.
Click to expand...
Click to collapse
OllieD said:
Does the device not already boot straight to the bootloader when there is no OS installed. i would have thought the boot process would get stuck in the bootloader with no OS.
Click to expand...
Click to collapse
OllieD said:
Android does not require a special cable to enter fastboot.
I've personally never heard of anything called a fastboot cable, a quick google search shows a kindle factory cable... obviously amazon have done something to prevent fastboot over a standard microusb.
Fastboot on G4 is easy to access by enabling OEM Unlock in the developer options and then rebooting into the bootloader. Doing anthing with fastboot however depends on the unlock status of your bootloader. A Locked bootloader will simply reject any useful fastboot commands.
Click to expand...
Click to collapse
First one there are gastboot cables and there are many devices that use them to get into fastboot some times manifactuer locks down acsess to fastboot.
I gues i shoulda give more info.
Im on sprint varient. Ls991. No fastboot
Im trying to see if i can get to castboot without nukeing the system or laf partitions.
OllieD said:
Android does not require a special cable to enter fastboot.
I've personally never heard of anything called a fastboot cable, a quick google search shows a kindle factory cable... obviously amazon have done something to prevent fastboot over a standard microusb.
Fastboot on G4 is easy to access by enabling OEM Unlock in the developer options and then rebooting into the bootloader. Doing anthing with fastboot however depends on the unlock status of your bootloader. A Locked bootloader will simply reject any useful fastboot commands.
Click to expand...
Click to collapse
A fastboot cable has a wire grounded out and commands fastboot. kindle uses them and a few other comps used them too
Im just testing stuff out.
OllieD said:
Does the device not already boot straight to the bootloader when there is no OS installed. i would have thought the boot process would get stuck in the bootloader with no OS.
Click to expand...
Click to collapse
Bootloader mode - yes. Fastboot mode - no.
Bootloader allows you to flash stock KDZ or TOT files, fastboot allows you to install custom recoveries, modems, kernels, ROM's from ZIP or IMG.
Related
I have a really strange problem here. I've flashed my radio in the past using fastboot. My config hasn't changed.
When I go into the android sdk and run adb devices. I get one device.
When I go to run any fastboot command it hangs at 'waiting for device'
When I put fastboot devices, nothing comes up.
I'd appreciate any help
Hi DarkShadowAy
You plug in the device and go to fastboot?
If yes, then try going into fastboot FIRST. Then only plug in your cable. You will see Fastboot change to Fastboot USB.
From there, flash your desired radio version.
Hi superstick,
I typed in:
PHP:
fastboot flash radio radio.img
Got the prompt 'waiting for device' and I then plugged in the USB. Nothing changed unfortunately.
Just to make sure, did you boot into the bootloader and does it show "FASTBOOT USB"?
Yes that error mostly means that you haven't selected the fastboot option in the bootloader. You have to select the fastboot option before flashing.
frosty_ice said:
Just to make sure, did you boot into the bootloader and does it show "FASTBOOT USB"?
Click to expand...
Click to collapse
I'll take the noob award of 2011 please.
I was baffled as I was in fastboot. When you posted that I thought why doesn't it say USB? It doesn't say USB because the cable wasn't plugged in
My desk's quite messy and I didn't realise the ipod data cable was in.
Thanks
Hi,
I am stuck in the bootloader and no input with the volume rocker is possible anymore.
How to reset it? Pull out the battery? I cannot find a reset button somehow..
Cheers
Try disconnecting the battery. I assume that you are not midway flashing some OS or ROM, in which case you should probably wait.
s1977 said:
Try disconnecting the battery. I assume that you are not midway flashing some OS or ROM, in which case you should probably wait.
Click to expand...
Click to collapse
No...i wanted to flash the stock rom of google but my device was not found by fastboot. I restarted my pc with the device still in bootloader and whilst being connected to the pc.
Pc didnt want to start up properly so i had to disconnect the USB connection.
Think my pc wanted to read from the internal memory of the phone or something.
Does this change your advice ? (hopefully not..)
Resetting the phone by taking out the battery shouldn't be a problem if you havent started flashing the new rom. I would try again after confirming that the fastboot and usb drivers can see the device before proceeding any further.
You can use fastboot devices to list attached devices. Only progress further once you can see your phone using the above command.
I did the same today a few hours ago and in my case, I started the phone in bootloader mode via Volume up + down + power button or via adb reboot bootloader. Then with fastboot, issue the fastboot oem unlock command to unlock the bootloader first. Once done, then you can flash the stock image (bootloader, radio and rom) with the following commands.
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
Don't forget to lock the bootloader once done using fastboot oem lock
Just to clarify, depending on the version of the OS on your client PC/Mac/Linux, there are variants of fastboot. I use fastboot-mac from my mac.
Hi thanks for the post s1977. One thing I would like to clarify. I am currently on a yakjuzs build. I am going to move over to a "pure" yakju build (currently on yakjuzs 4.0.1, new build will be yakju 4.0.2). I have already unlocked bootloader and rooted phone. If I were to perform this update, I know I do not need to perform fastboot oem unlock (which I know wipes the internal storage) but will the flashing of the new bootloader wipe the storage as well, or will it just update it?
Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!
cricket62 said:
Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!
Click to expand...
Click to collapse
Did you enable adb debugging, in dev options before bootloop?
Did you enable adb debugging, in dev options before bootloop?
Click to expand...
Click to collapse
Hi unfortunately not, I only enabled "developer mode" but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.
cricket62 said:
Hi unfortunately not, I only enabled developer mode but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.
Click to expand...
Click to collapse
Is the Bootloader unlocked?
Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
Is the Bootloader unlocked?
Click to expand...
Click to collapse
No, reason is since Lineage OS or TWRP are not yet build for G30 I wanted to keep the fully functional stock.
sd_shadow said:
Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks so much!! I will try that and write results when I get to it! Have a good healthy day!
Hi Just wanted to update: I still need to set up the USB redirect of the fastboot device to the Windows virtual machine. So may take a bit longer for me to get to it.
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
I restarted my phone after being prompted to by a recent update. For a while the phone was stuck in a loop of booting to the android screen followed by the magenta tmobile screen before starting the process again over the course of 5 min.
Now the phone only boots into the recovery mode menu(?). The black screen with the oneplus logo that prompts you to pick a language before giving you the options of "view boot reason", "wipe data and cache", "advanced", and "exit" on the next screen.
View boot reason just says init_user0 failed.
I have wiped the cache and restarted, still boots into the recovery menu regardless.
I can boot into fastboot, but I do not have the bootloader unlocked. With the bootloader locked that means I cannot boot twrp recovery image from what I understand? And then unlocking the bootloader wipes the data.
I have managed to boot into EDL mode as well and the phone will show up as connected in the MSMDownload tool.
ADB does not work as far as I know since my phone no longer boots into android. (It displays the qualcomm snapdragon logo briefly before showing the aforementioned recovery menu).
Is there anything I can do recover my data given the above information? I have reached out to oneplus support as well and they said they'd get a more specialized person to reply to my case in 6-7 hours. Thanks for any help.
Corick said:
With the bootloader locked that means I cannot boot twrp recovery image from what I understand? And then unlocking the bootloader wipes the data.
Click to expand...
Click to collapse
Correct.
Also from what I understand, you cannot 'pull' files from internal storage from Fastboot mode, contrary to ADB mode (unless I am wrong).
Maybe you could try switching 'Active Slots' in Fastboot mode? With a little luck the other slot may still be bootable. It is not clear if this command will be permitted with stock ROM. You can do a little research but the fastboot commands should be:
fastboot getvar current-slot
fastboot set_active a (or b depending)
fastboot reboot
Robinlong said:
Correct.
Also from what I understand, you cannot 'pull' files from internal storage from Fastboot mode, contrary to ADB mode (unless I am wrong).
Maybe you could try switching 'Active Slots' in Fastboot mode? With a little luck the other slot may still be bootable. It is not clear if this command will be permitted with stock ROM. You can do a little research but the fastboot commands should be:
fastboot getvar current-slot
fastboot set_active a (or b depending)
fastboot reboot
Click to expand...
Click to collapse
Thanks for the info. I gave that a shot after and unfortunately it said Slot change is not allowed in lock state. Oneplus support did get back to me and said I'd have to send the phone in for repair. They said the device data is likely lost though so I'm not sure if it's worth sending it in vs just wiping and all that myself.