Related
Hey,
i just wanted to flash the newest clockworkmod but my fastboot.exe does nothing.
Phone is in fastbootmode, please help
Windows 7 x64...but it worked the other day
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Fmbl said:
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Click to expand...
Click to collapse
i can flash the recovery fia ROMManager, and also can boot into it, but when i boot the phone into bootloader/fastboot mode i can't flash a new recovery, because when i hit enter after "fastboot" i get no output in cmd
If you don't get anything back on fastboot devices, then you either don't have the proper drivers installed, don't have the phone in fastboot mode, or don't have the phone connected via USB. Probably the first one.
Easiest way to get the fastboot drivers is to simply install PDA Net on your computer and follow the on screen prompts. It will automatically install the appropriate drivers for your device.
Sent from my Nexus S using XDA App
thanks, i will try when i am at home again
Sent from my Nexus S using XDA App
Check in device manager that the ADB Bootloader driver is installed.
zero383 said:
Check in device manager that the ADB Bootloader driver is installed.
Click to expand...
Click to collapse
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
eiabea said:
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
Click to expand...
Click to collapse
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
matt2053 said:
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it very carefully, but no success
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
ericshmerick said:
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
Click to expand...
Click to collapse
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
zero383 said:
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
Click to expand...
Click to collapse
Yes and yes.
May want to continue here:
http://forum.xda-developers.com/showthread.php?t=1303522
Had the same issues, although drivers were installed. After including "C:\android-sdk-windows\tools"
and "C:\android-sdk-windows\platform-tools"
in the path of win7 (systemvariables)
and a restart adb and fastboot worked.
Anyone knows the command in adb to boot the phone into download mode? I broke the volume flex cable and it's softbricked now
Sent from my MT11i using XDA
I'm pretty sure its "reboot download" just like through a terminal emulator from the phone (root required).
#su
#reboot download
adb shell
$ su
#reboot download
There is no need for su if you have a #
Montoyatok said:
Anyone knows the command in adb to boot the phone into download mode? I broke the volume flex cable and it's softbricked now
Sent from my MT11i using XDA
Click to expand...
Click to collapse
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Thanks guys
Sent from my MT11i using XDA
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
:victory: OMG!!! Bless You!!! :victory:
I knew there had to be a better way then pulling out the rest of my thinning hair!!!
Samsung Galaxy S II (SCH-R760) US Cellular
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
Sorry but it Reboot in Normal Mode
chlebta said:
Sorry but it Reboot in Normal Mode
Click to expand...
Click to collapse
I think I'm also experiencing the same thing, and could really use someone's help.
I have a Sprint Galaxy S3 and have rooted it. My display is broken, so would try to use the how-to to create a headless backup.
When I try to reboot it into download mode, it seems to never come back. I believe it's waiting for a keypress on the phone, or scrolling through a menu to select the right option so it can continue to boot. Can anyone with a working display confirm this for me?
I rooted it a while ago, so don't remember what's on the screen.
When I try to reboot in recovery mode, I'm also unable to select the proper menu option to continue to boot into recovery mode.
Is it always necessary to boot into download mode first, or only if you want to download something? In other words, if I only want to reboot into recovery, can I skip the download mode boot first?
Ideas greatly appreciated!
Thanks,
Alex
You don't need to enter download mode first. From command prompt enter adb reboot recovery and your good to go
thanks this saved a lot of hours
bsuhas said:
from computer,
adb reboot download
adb reboot recovery
works 100%, no TerminalE required.
Click to expand...
Click to collapse
can you help me too ?
even i broke my volume flex nd am hard bricked
so when i try to turn it on it just stays on google logo my device is nexus 6 ?
am not so familiar with adb so pls can you help me ?
Hi
My android screen lost it's touch and it's stuck waiting for "Enter"
So I'm trying to use ADB to get there
My question is how to enter the "Enter" command ?
EDIT:
TNX, no need to reply, the problem is solved
ggossamer said:
I think I'm also experiencing the same thing, and could really use someone's help.
I have a Sprint Galaxy S3 and have rooted it. My display is broken, so would try to use the how-to to create a headless backup.
When I try to reboot it into download mode, it seems to never come back. I believe it's waiting for a keypress on the phone, or scrolling through a menu to select the right option so it can continue to boot. Can anyone with a working display confirm this for me?
I rooted it a while ago, so don't remember what's on the screen.
When I try to reboot in recovery mode, I'm also unable to select the proper menu option to continue to boot into recovery mode.
Is it always necessary to boot into download mode first, or only if you want to download something? In other words, if I only want to reboot into recovery, can I skip the download mode boot first?
Ideas greatly appreciated!
Thanks,
Alex
Click to expand...
Click to collapse
I also installed custom rom AOSPrime. and then for going back to stock, i needed to enter download mode. None of the commands worked. i made a backup of everything in twrp except system and data. so i restored that back, and then voila, the LG logo was back but didnt boot(obvious). Now i could easily go by the vol up and then usb connection process to goto download mode.
the default stock settings enable the download mode to work.
if anyone needs the backup, mine may be of other region, but it could surely bring back the lg logo and stuff.
quote me and i will post the link
ggossamer : before download mode you need to confirm download mode with volume+ or you can cancel the thing with vol- , IIRC .
For your other questions, I think, recovery with a broken screen might be difficult, maybe use ADB
Samsung Grand prime download mode
I have a Samsung grand prime and I can not reach download mode to use the Odin 3.07 to flash the md5, even when I used adb services command "adb reboot download" it rebooted in normal mode. Any help please?
Thanks
Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
roniinn said:
Hi everyone,
after days of researching this issue I'm finally at wits end. After installing the Playstore version of ROM Manager, my Asus has been stuck in CWM recovery mode with the inability to mount any drives. When I re-boot the tablet gets stuck on the load screen. I have tried several methods to flash the tablet using:
- NVFLASH
- EASY FLASHER
- FASTBOOT
- ONE CLICK RECOVERY
- ADB PUSH
The recurring issue that I seem to be encountering using these methods is that my PC recognizes the tablet in APX mode (I have tried both naked & usbpcdrivers) but the utility software does not. When I boot into recovery mode ADB recognizes my device but does not in APX mode. When I run NVFLASH while in APX mode my tablet gets disconnected from the PC and I receive a USB write error from NVFLASH.
Prior to the failure I successfully rooted my device using Baidu Root. At this point I don't even know how to power off the device as the only way to exit the loop is to boot into recovery or APX mode.
Any help would be greatly appreciated, as my experience with these matters are limited.
Thanks
Click to expand...
Click to collapse
First recommendation, stay away from ROM Manager, our device doesn't like it. You need to try and uninstall all usb drivers associated with tf101 and start over. I used the drivers from BRK's v.8 Tool Kit. You may need to find some newer adb files to swap out with his, but try first. To clean all the drivers may require connecting the tab to pc in different modes to even see some of the drivers, but see what's in Programs & Features - Remove function in Windows. You will also need the stock ROM downloaded from Asus site before you start. If you can get into recovery, then you should have an option in there to power off the device. If you get that far, then his tool has the nvflash pieces to start from scratch and get rooted and install an older custom recovery. Go with the CWM version there and, ultimately, change it out to the latest TWRP as soon as possible. Getting the drivers for Windows working is the hardest part, assuming everything else works. Conflicting USB drivers will be nothing but headaches, as you've found out.
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
roniinn said:
Hi,
just to be clear, when the tablet is in APX mode, is ADB supposed to be able to detect it when the adb devices command is used?
Click to expand...
Click to collapse
I don't think so. It's like download mode on other Android devices. You should be able to access via adb in Android, with USB debugging enabled, or in some custom recoveries, my TWRP builds for one. I believe nvflash is the only method to communicate with APX mode.
Sent from my SM-N900T using XDA Premium HD app
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
roniinn said:
Hi,
I have re-installed drivers, but the PC still disconnects my tablet when running NVFLASH, I have read that a utility named WHEELIE might assist in unlocking the bootloader on my device allowing NVFLASH to run successfully. The problem is I can not locate the windows version of this file anywhere. All of the links point to a website named AndroidRoots, but the file seems to have been removed from the site.
Any Ideas where I can locate this program?
Thanks again.
Click to expand...
Click to collapse
BRK's version 8 tool I referenced uses wheelie to cover all possible skus of tf101 and works well for me. As far as drivers, you have to make sure there's only one set installed for tf101.
Sent from my SM-N900T using XDA Premium HD app
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
roniinn said:
Does the wheelie script run automatically when I invoke the rootkit app, or do I have to manually run it from a CMD window?
Thanks for all your help,
Click to expand...
Click to collapse
It runs it where needed within a windows app interface, completely transparent once you start the program executable by double clicking it. You'll see a command window, but it just shows you the progress.
Sent from my SM-N900T using XDA Premium HD app
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
roniinn said:
Thanks for your help,
I have finally got my device up and running again.
My next step is to flash the new KatKiss ROM, can I do this using BRK's toolkit by substituting my stock rom file with the new one, or is it to better to install the new rom from recovery and external SD card?
Click to expand...
Click to collapse
I would just install it from recovery and ext sdcard, easier if you've already cleaned and repartitioned, etc with a stock rom.
Sent from my SM-N900T using XDA Premium HD app
My Oneplus One - 64GB was running LiquidSmooth's Alpha ROM.
I hadn't used the phone in like a month. A couple of days ago i thought there'd be an updated version so i just downloaded a later version. I think I flashed the 01-22 Build.
I did not do a full wipe however. (I realize now that It would have been a good idea to do a full wipe before the flash. :s )
I assumed that since the base of the ROM was the same lollipop, all I had to do was wipe cache/dalvik and flash the update.
Installation proceeded as usual and I wiped cache/dalvik(I'm never sure when to do this so i do it before and after install) once more and then Reboot System.
But the phone went on a bootloop for like 10minutes or so.
I tried to get into Recovery but it just wouldn't. It would just show the 1+ Logo and Powered by android screen and then turn off..
I did however manage to get into the fastboot mode by pressing power +vol up.
Now the problem is, the device doesn't show up in the command prompt when i type
Code:
fastboot devices
I uninstalled all the usb drivers from my pc.
Installed the Universal ADB drivers from kouch's site but still no progress..
Device manager still shows the phone as an unknown device.
What am I doing wrong? What can i do to get the phone to be recognized so I can flash the recovery and flash a new ROM?
It's related of firmware change. After 01.17.2015 you must flash the latest CM12 rom and then flash the rom you want.
That's a known "issue". Hope it helps.
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
thetearer said:
Problem is:
1. I no longer have a working recovery(can't boot into recovery).
2. Rom doesn't boot, stuck in a bootloop.
3. Can get into fastboot mode, but pc doesn't recognize device and it doesn't show up when i type "fastboot devices".
I've already installed "Universal ADB Drivers from here -> http://www.koushikdutta.com/post/universal-adb-driver
What can i do to be able to access phone via fastboot?
Should i remove these drivers and try another driver? If so, which other driver should i install and test with?
I don't have any critical data on the phone, I just want to get it working again so my family members can decide who wants the phone.
Click to expand...
Click to collapse
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
timmaaa said:
Uninstall all drivers, reboot PC, install those universal drivers again, reboot PC, connect phone in fastboot mode, try fastboot again.
Click to expand...
Click to collapse
That's the order I did stuff in last time I believe. I'll try it again and report back
My home button has stopped working and was wondering how I would boot into odin mode (download mode) to flash twrp etc.
i am no expert but you can use adb to get into download mode !!
http://forum.xda-developers.com/showthread.php?t=1695552
likhon02 said:
i am no expert but you can use adb to get into download mode !!
http://forum.xda-developers.com/showthread.php?t=1695552
Click to expand...
Click to collapse
Thanks, but it didnt work. I think i need Root to do this no? But thank you for trying and looking ouut.
Cant get my phone to connect to my computer now.
to use adb you don't need root just read the entire thread carefully..if you are still having issues knock me facebook.com/abokashm.
likhon02 said:
to use adb you don't need root just read the entire thread carefully..if you are still having issues knock me facebook.com/abokashm.
Click to expand...
Click to collapse
Hello, I also cannot use adb to boot to download mode. To be honest, I am not quite sure what is download mode. Is it similar to fastboot mode? My S6 cannot boot, it just says that there is no home app available, and than just error after error. Cannot use it at all. So I tried to boot to download mode, no success with buttons combination (home+volume down+power). so I installed adb and fastboot. ADB doesnt see my phone, and fastboot does, but I do not know what is command for it. I would like to use Odin to flash new rom, maybe that will fix the phone, but cannot use it if I cannot go to download mode. So any help is welcome.
repair home button
http://www.etradesupply.com/blog/how-to-tear-down-samsung-galaxy-s6-in-10-steps/