I checked Recovery mode and Download mode, and thats OK.
But i found information on Internet, and always the same: VOL UP/DOWN + HOME + POWER.
In some sites, somethind about Forced Upload (i've got one time only and i dont remember how it was.
The question: i called to technical support and asked for the way to get into fastboot mode, and the replay was the information is properly for samsung personal.
Then, i was tyred and bored.
Could anybody help me?
NOTE:
I know that download mode is enaugh, but booting directly from a recovery file in PC is good and quick, and flashing the recovery boot only.
Hey
Just played around with my Galaxy S and could retrieve the way to get into
Forced upload
I pressed Volume up and home until the black and whie Galaxy S boot Screen came
up and then right away volume up+home+powerbutton at the same time.
Hope it works for you as well and hope I remembered it correct because I am feeling
realy dizzy today paired with headaches :/
Is the forced upload mode same as fastboot? Because I am trying to install an other bootscreen as the
one from samsung is not my thing.
I have two phone, one with working 3 button hack, another one without recovery mode with 3 buttons.
on the later device i alway get the "forced upload" (whatever this is) while pressing home and vol up for 3 or more seconds when phone is of.
on the othe device (wirkoing three button mode) i did not manage to see "forced upload"
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Thread moved to Q&A.
jodue said:
a similar question has been asked somewhere before: fastboot is htc (ADP=android development phone) specific. fastboot does not (and never will) work with samsung handsets!
Click to expand...
Click to collapse
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Click to expand...
Click to collapse
hm. yeah looks like i was wrong there
scorpio16v said:
Fastboot is an utility from the Android SDK and normaly not made only for one brand.
Click to expand...
Click to collapse
of course it's a part of the aosp but i have (till today) never ever read anywhere that non htc devices support it ... my bad
if anyone finds out how to use fastboot with the galaxy s i will gladly buy 'em a couple of beers because i would love to have this functionality at my disposal!!!
if you simply want to reboot the phone quickly, there is an APP for that
you can choose normal reboot
reboot to Recovery Mode
reboot to Download Mode
look for Quick Boot
http://forum.xda-developers.com/showthread.php?t=765081
Click to expand...
Click to collapse
Doesn't this app solve the broken three button recovery problem?
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Tehpriest said:
Doesn't this app solve the broken three button recovery problem?
Click to expand...
Click to collapse
of course not
when you are bricked, how are you going to run a software on a dead phone?
the phone needs to be rooted for quick boot to work
if you do it via ADB when connected to PC
then you don't need to be rooted
mam999999 said:
Thats the thing i referred it. All people with Galaxy S work with REcovery and Download odes.
But anybody knows how the FastBoot Mode works in i9000, and it very important taking a native mode to change the Recovery Boot without flashing with ODIN or Rom Maneger utility (free at the moment).
I understand FAST BOOT is something in relation with android, but ¿is it posible that it need an especial recovery boot, like an intermediate, for passsing throw to FastBoot mode?
Click to expand...
Click to collapse
I explained more better.
If phone is bricked, it doesnt boots.
Then, ADB is worthy. For that reason, only two chioces:
1) FLASH with ODIN, if it posible with download mode
2) Samsung with JTAG ---> money!!!!
2) FastBoot Mode.
That is very important, and thats my interest
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
AllGamer said:
if the phone is bricked
only the 3 button Download Mode will work
JTAG, not many places have it, it's hard to find, the phone is still too new.
Fastboot mode will not work when bricked
ADB will not work when bricked
Click to expand...
Click to collapse
AllGamer, I think you should look up what fastboot actually is/does.
It's a way to flash the phone from a 3button style download mode. The thing is, you can use ADB from windows/Mac/Linux to flash it. (Yes, even when bricked, because you enter it with a different 3button combo)
All HTC Phones have the ability, as well as the Original Samsung Galaxy I7500 and I5700 phones.
People are on here wondering if there's a way to enable the function on the Galaxy S.
Responding in a thread where you have no idea what the topic at hand actually is just makes the thread harder to follow. Please refrain in the future.
Yes, i think FASTBOOT is another backdoor to revover the phone.
And, another advantage:
1) substituting the revovery boot partition (throw native flashing 3button mode) or
2) boot from PC with one recovery image without writing the recovery partion, making diagnostic and everyting like testing news images.
It is very important, and many people will be wondered to know this 3button mode.
Samsung, by call, admited to know the mode, but they dont wanto to say how to get in mode fastboot.
I'll continue to find it.
AllGamer:
How, then, do you overwrite the boot partition? With ADB? Then you need unbricked phone .....
Electroz said:
Want to explain why my old Galaxy I7500 had fastboot then?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Did samsung actualy make the phone and not just designed it? Ie the sony xperia x1 was a htc made phone but sony design. So maybe that's why u had fastboot in the 7500. Either way i have no idea on samsung phones as i never liked them
Sent from my GT-I9000 using Tapatalk
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
AllGamer said:
if the so call fastboot is actuall another hardware mode, and not the fastboot from ADB shell, then it'll have to be some sort of buttons to trigger it.
I know people that have posted they got into a Forced Upload mode, is that what you guys mean by fastboot mode?
However only people with the disabled 3 buttons download modes seems to have been able to get into this Forced Upload mode, problem is none of them knows exactly how they got into that mode
Click to expand...
Click to collapse
It IS fastboot from ADB.
You basically put the phone in fastboot mode (similar to 3 button download mode). You can then flash your phone (with the phone in fastboot mode[not booted into android]) with the fastboot command in the Android SDK Tools folder.
"fastboot flash recovery recovery.img" would flash a new recovery image to the phone, or "fastboot flash boot boot.img" would flash a new boot image to the phone.
All this can be done by entering a 3button combo to power on the phone directly into fastboot mode. (Android not required to boot, or even be functioning)
Related
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
xavipr69 said:
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
Click to expand...
Click to collapse
Search Google for adb commands to boot downloadmod or recovery I'll post some when I have acsess to computer.
xavipr69 said:
.....i have a Galaxy S I9000b, with a broken power button..... Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot?
Click to expand...
Click to collapse
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
tetakpatak said:
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
Click to expand...
Click to collapse
Hey, thanks for the help, but the thing is that i can't access the phone OS, so i can't enable USB debugging to start ADB, by the way i'm a little bit noob in this ADB thing, but i have installed android SDK, java and the drivers, i don't know if i need anything else. When in the command prompt i type "adb devices" but no device is recognized. Please help! Thanks beforehand
tetakpatak said:
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
Click to expand...
Click to collapse
Please check my last post! Thanks
xavipr69 said:
Please check my last post! Thanks
Click to expand...
Click to collapse
Ouch, you're really in uncomfortable situation
I consider as best you can do to try to flash a stock ROM with Odin. I don't know if it will work, as your USB debugging isn't enabled (I must admit that I've never disabled it). I hope it will work!
If it works, it will result in data loss. Your photos and music will probably remain, but SMS, calls, contacts and all else will be lost. If you flash the same ROM you've used before your system crashed, you may be able to restore with Titanium app all the backups you did.
You can inforce your phone to run in the download mode by connecting an USB jig, that can be bought on eBay for ca $2. I hope our forum mate @xsenman will post for you more usable info, he is an angel of helping in such situations and knows specific questions about i9000B better than me. I am more familiar with the i9000
xavipr69 said:
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
Click to expand...
Click to collapse
Basically, IF you cannot enter download mode because of power button, you can use other methods, look here in My Android Solutions for recovery / download mode solutions
You cannot use fastboot for Samsung galaxy phones, its all done by Odin3, heimdall or Mobile Odin , so go here and download the required files to flash. or i9000B Roms :- here & here or here for original stock ROM's
If you already had a ROM, and unable to boot you can flash a i9000B kernel to see IF it boots, from above link. For Normal Flash procedure look here
You only follow the procedure with the ROM's meant for i9000B, do not use other ROM's meant for other devices
Check this out! Links to useful Guides and " Banned " Documentaries
RESOLVED!
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
herrdrchili said:
so I just got my moto x dev edition, unlocked the bootloader, and then screwed it up...
i tried flashing the recovery as described here, http://forum.xda-developers.com/showthread.php?t=2458451 but didn't realize/understand that fastboot and mfastboot were not interchangeable. it looked like it went ok, but I wasn't able to reboot into recovery. so, now on boot to recovery i get the little android on his back with a red triangle. i'm pretty sure that the stock recovery is gone, but cwm is not installed either. which brings me to my next little problem...
so i did some reading and got mfastboot installed and thought ok I just need to reflash cwm on phone again. problem is, now the phone won't stay in usb debug mode so that i can see it when fastbooted. that is, when i reboot the phone into fastboot by holding the power/vol down I can't see the phone when doing 'adb devices', and whem I let it boot up i see usb debug is switched off. when i switch it on, then i can see the phone from adb again, but when i try to 'reboot bootloader' it gives me a not allowed error.
at this point i'm just sick and afraid i bricked it. i am coming from a galaxy nexus and never had anything like this happen before. i truly appreciate any help here, at this point i feel like puking and dreading telling the wife i just blew 450.... :-/
ps i'm on mac 10.7 so if i need rsd it will be via a virtual machine....
Click to expand...
Click to collapse
ok then - i guess rsd has potential?
xpsychox said:
so, if i understand you correctly, u've held down the volume down button and power button? becasue that's your fastboot. That's where you need to be to use RSD, and that's what i'd do.
Click to expand...
Click to collapse
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
herrdrchili said:
i can reboot into fastboot, but adb can't see the phone. I'll start trying to setup rsd and and see if it can do any better. any good links you know to get up to speed on that would be appreciated. if you know how to simply reflash the recovery via rsd that would be helpful too - thanks in advance!
Click to expand...
Click to collapse
the sites that I know of are for the device I have, a non devliper edition... I don't know if it makes a difference, I don't wanna make anything worse.
thanks for the sanity check,,,
btdonovan said:
ADB commands aren't used in fastboot mode. You should be able to see the device in fastboot mode with the command fastboot devices. Also, remember that the stock rom will try to restore the stock recovery when it is booted so if you flash recovery in fastboot mode then let the stock rom boot it will reflash the stock recovery which shows you the little droid and the red triangle.
You should still be okay though. Shut the phone off and boot into fastboot manually with power and volume down. Reflash the recovery. I know there are warnings about using mfastboot but I used standard fastboot before I saw those and didn't have an issue. From the fastboot screen after flashing the recovery, use volume down to get to highlight recovery and then press volume up to select, not power. Power will just do a standard reboot.
If you flashed twrp recovery then rebooting system will prompt you to install su. I think clockwork does the same thing. Letting the recovery install su will also prevent the stock recovery from getting restored and from there you should be good.
Click to expand...
Click to collapse
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
herrdrchili said:
THANKS! just needed another set of eyes - man i need to not try doing this after a long day again i really appreciate your help. i got it now!
Click to expand...
Click to collapse
Glad I could help!
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
umair shaikh said:
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
Click to expand...
Click to collapse
Have you tried it from your PC?
fastboot reboot-bootloader
How can you run fastboot commands if your not in fastbbot-bootloader?
"my phone doesn't enter into fast boot mode"
(General message - see what I did there? No need to repeat the entire post. Just the part I'm responding to.)
Does this mean that you can't get to bootloader? Is your bootloader unlocked? When you reboot do you see the open padlock symbol?
So what did you do to brick your device?
dahawthorne said:
"my phone doesn't enter into fast boot mode"
(General message - see what I did there? No need to repeat the entire post. Just the part I'm responding to.)
Does this mean that you can't get to bootloader? Is your bootloader unlocked? When you reboot do you see the open padlock symbol?
So what did you do to brick your device?
Click to expand...
Click to collapse
Yep my bootloader is unlocked i used to run custom rom it just stays on google logo thats it
holeindalip said:
How can you run fastboot commands if your not in fastbbot-bootloader?
Click to expand...
Click to collapse
With USB connected, from a cmd prompt I do:
adb devices (to load the drivers and make sure my phone is recognized)
adb reboot bootloader (this should put you in bootloader mode)
fastboot devices (just to be sure my phone is still recognized)
fastboot flash radio radio.img (or whatever image you want to flash)
fastboot reboot-bootloader (in between flashes, just to be safe)
I do so hate it when people don't bother to read my posts properly. It takes away my incentive to try to help them...
"No need to repeat the entire post. Just the part I'm responding to."
"So what did you do to brick your device?" Install the custom ROM you mention?
And a new question. You say "no matter wat buttons i press". Does that include the bootloader power & volume down simultaneous press for maybe 30 seconds?
So there are 3 items in this post. Can I have 3 responses please? The first will be not copying this entire post all over again, the other two will be answers to my questions.
umair shaikh said:
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
Click to expand...
Click to collapse
Do you have a working recovery you can access?
And stay away from toolkits. Learn to flash manually. It's easy and you know what part goes wrong. Tool kits are nice in automation, but when something happens ya don't have a decent idea where to start.
Sent from my Nexus 6 using XDA Free mobile app
@dahawthorne
1.lol fine i get it my bad ..
2.i was actually trying to install n preview. Actually i read somewhere we can flash adb file type by new twrp so i tried doing that n this happened..
3.i tried it a couple of times..but if i press them for longer time it just turns off n turn on again n gets stuck on logo
31ken31 said:
Do you have a working recovery you can access?
And stay away from toolkits. Learn to flash manually. It's easy and you know what part goes wrong. Tool kits are nice in automation, but when something happens ya don't have a decent idea where to start.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Nope...nothing
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
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
dulfried said:
(I couldn't find this exact problem on the forums, forgive me if I overlooked it)
I tried booting my mom's old phone, an HTC Desire 626G, but it is stuck in a bootloop. When I try to enter recovery mode (by pressing power + volume down), it just enters the loop again.
I can however enter what I think is the bootloader menu, giving me three options: recovery, fastboot or normal boot. Fastboot freezes the phone, the other two options just start the bootloop. I've never installed a custom ROM.
I disassembled the phone, un- and replugged the battery to no avail. I tried ADB but I never enabled USB debugging in the first place, so that doesn't work either.
Do you have another idea that might work?
Click to expand...
Click to collapse
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
brokenbrain939 said:
Bro You need to flash the factory firmware using a pc with that fastboot mode.....
The existing firmware might have been got corrupted or the storage might have been damaged, since its an old device(which is very rare),
To do so u can find many articles on the internet very easily,
Click to expand...
Click to collapse
Thanks a lot, I'm finally able to communicate with my phone via PC now. Booting still doesn't work but now I can at least format the storage and hopefully flash the factory ROM.