Related
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)
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!
I did root, installed custom recovery, factory reset, update ota to 10e, phone stuck in recovery mode any help
i am in the same boat and would love some help as well
Hi codemans I bought the OTG cable try to connect phone to a USB stick as it will let you know
i have been in getting help from an xda user named charlieb620. he gave me this link http://forum.xda-developers.com/showthread.php?t=2451696 to fix it i just need to get adb working because every time i press the terminal command in twrp it brings up the file manager.
edit also i seem to be having trouble getting the right drivers.
You fixed phone?
So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help
Good morning i just got my lg g4 yesterday i was able to root it and flash custom recovery twrp via adb yesturday i even flashed some roms but today no matter what i do i cant get adb to work i keep on getting unathorized. On adb im stuck i cant get to boot to twrp either every time i try to whit the buttons vol down power at factory resets im stuck on exorsism rom but because i factory reset it dont got super su i tried diffrent computers and i get same error i uninstall android sdk and install whit no luck i tried lg flash tool to flash KDZ file gives me error can't connect to network try again in a few minutes can some help is their away to boot to twrp whit out adb ? Or how can. I fix the unauthorized on adb i think the problem is in my phone i tried diffrent computers windows 7 and 10 any help will greatly appreciates thanks
Sent from my LG-H811 using XDA-Developers mobile app
Did you try USB 2.0, if you a have a USB3.0 port it causes problems,
does your G4 serial starts with serial 505 to 510 and harware 1.0 ? those seems affected by the hardware flaw that makes boot loops
I read somewhere in here that serials 601and upper have the bootloop flaw fixed
Anyway, if you have an SD card installed, with the phone off remove it
and try again without the SD card
sometimes that helps
looks like G4 is a unstable beast
I did the same thing, I still haven't gotten adb working again but you can boot into recovery via kernel auditor. Or do a factory reset via the hardware keys and it will take you to twrp.
Sent from my LG-H811 using Tapatalk
I'm stuck at pretty much the same juncture. Kernel Auditor requires root to function (which we both seem to have lost) and the hardware buttons/factory reset just do that then boot me back into the rom. I also assume it's something with the phone since it reads "unauthorized" on 3 separate machines. Any other thoughts guys?
Also it has become apparent that although I fastbooted into TWRP initially, it did not stick. Leaving me with stock recovery, and clueless how to flash a recovery without ADB access.
@oogsaggie this what i did to get it fixed just download LGUP, put it in download mode, download the 20i KDZ file, and go back to stock 20i. and then root again make sure you permanently flash twrp move the twrp. image to your phone and flash iy from twrp
Sent from my LG-H811 using XDA-Developers mobile app
COCODRILO45 said:
@oogsaggie this what i did to get it fixed just download LGUP, put it in download mode, download the 20i KDZ file, and go back to stock 20i. and then root again make sure you permanently flash twrp move the twrp. image to your phone and flash iy from twrp
Sent from my LG-H811 using XDA-Developers mobile app
Click to expand...
Click to collapse
@COCODRILO45 Ended up doing exactly that. Wish I had seen your post earlier, but regardless great minds and all that stuff. For future reference I think COCODRILO45's solution is the most painless way to go. Cheers!