Is there a "fastboot oem ..." command to programmatically reboot XA2 in flash mode (e.g. to run newflasher afterwards)? Something like "fastboot oem rebootRUU" of HTC?
I'm aware that I could reboot and hold Volume-Down, but I'm looking for an automated, scriptable way to do this.
As a side question, is there any place where the "fastboot oem" subcommands of XA2 are documented?
v0g said:
Is there a "fastboot oem ..." command to programmatically reboot XA2 in flash mode (e.g. to run newflasher afterwards)? Something like "fastboot oem rebootRUU" of HTC?
I'm aware that I could reboot and hold Volume-Down, but I'm looking for an automated, scriptable way to do this.
As a side question, is there any place where the "fastboot oem" subcommands of XA2 are documented?
Click to expand...
Click to collapse
use Minimal ADB and Fastboot
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
adb reboot recovery (for recovery)
adb reboot bootloader (for fastboot)
Related
Edited OP to be shorter to the point:
I am stuck in fastboot but can not establish an adb connection to set the boot mode back to 4000.
Xplorer4x4 said:
I was tired and trying to update my KF to FFF1.3 and TWRP 2.1.0. I am now stuck at the new FFF boot logo(green android guy with KF text under neath). The update to FFF1.3 went smooth. Then I moved on to TWRP. So I tried flashing the img file via terminal emulator rather then using ADB over my computer. So first I set the boot mode to 4002. Success! Then I tried to flash the img file, but was getting errors(I think it was because I forgot to cd in to the downloads folder so Terminal Emulator knew where the file was). Well Due to not being able to flash I had to set up my PC again for the KF to use ADB as I had a system crash since then. So I got hung up with not being bale to use ADB and decided to reboot the KF, thinking it needed a reboot before the PC would recognize it. After rebooting I for stuck on the FFF 1.3 logo. I know ADB is fully functional now(forgot to install an API) but the KF Utility will not recognize the device to be able to reset the boot mode to 4000.
Any suggestions?
Click to expand...
Click to collapse
can't use term to flash like adb, gotta use the dd if= method.
might be I'm fastboot if its stuck at the startup logo.
Sent from my HTC Glacier using xda premium
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
DeadChex said:
Looks like your stuck in fast boot mode... Issue "Fastboot idme bootmode 4000"
I think thats right... not 100%
Should be in normal boot mode now =D
Click to expand...
Click to collapse
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Xplorer4x4 said:
You are right. This was stated in the OP. The problem is getting ADB to initilize to reset the bootmode.
Click to expand...
Click to collapse
opps, I lied... you cant issue idme from fastboot.... nor can you issue fastboot shell...
so, no adb at the very beginning of the KF boot? Does fastboot notice it
Try "Fastboot Reboot" if fast boot works... or 'Fastboot continue"
DeadChex said:
so, no adb at the very beginning of the KF boot?
Click to expand...
Click to collapse
Nope, not at all.
Does fastboot notice it?
Click to expand...
Click to collapse
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Xplorer4x4 said:
Nope, not at all.
If I understand you correctly, then no. As soon as the KF turns on I start taping up+enter(to renter the adb devices command in cmd) and never get it listed.
One thing that should probably be mentioned that I forgot, the power button lights up green as soon as the KF is turned on and the light dims. I assume this is an indication that fastboot is taking over?
Click to expand...
Click to collapse
the boot process goes... Bright LED (first turning on) > Dim LED (Fastboot and Button input) > Bright LED (Normal Boot)
Where is it stuck?
Use "fastboot devices" to see if its listed in the beggining (when bright green)
but, if its going Bright, that means its not trapped in fast boot
(Fastboot is a diffrent program from ADB completly, just throwing that out there, I've attached it if you need it)
Something very enlightening I found somewhere around this great place:
"
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
"
Edit: You do need the file in the above post when doing this over usb.
Sent from my Amazon Kindle Fire using XDA
freefaling said:
Something very enlightening I found somewhere around this great place:
Click to expand...
Click to collapse
This is great information but totally useless with out a working ADB.
DeadChex said:
(Fastboot is a diffrent program from ADB completly, just throwing that out there)
Click to expand...
Click to collapse
I am aware, but thanks anyways.
fastboot devices does give an out put after the dim. Did not test before the dim.
Good News: I tried the "fastboot -i 0×1949 oem idme bootmode 4000" command again and got an unrecognized vendor ID. So despite following the instructions to modify the 2 .ini files, and accept the install driver warning, and selecting the location for the ini manually as you should, I realized something was wrong with adb. So I used the install driver bat from the KF Utility zip,and got adb working. Issued the 4000 boot command and back in business.
Thanks for all the help guys! I think you guys managed to provide the fastest responses to help I have ever needed, and it is rare I ask for help, so that makes the experience that much better.
I'm not responsible for anything going bad, if you dont know what this command is used for dont use it.
For those who can not boot into current ROM, or have troubles using adb; to use this command "adb reboot oem-78" after locking their devices, you can simply use "fastboot oem rebootRUU" to get into the black-bootloader screen to be able to update hboot/firmware(from bootloader screen).
Cheers.
thanks
I tried install a cm11 but in the process i brick the kindle fire hd, but now with the fastboot cable, i can enter on fastboot mode, but i used "KFHD_SRTv1.3.5" option 1, 3 and 6 to restart, in the kindle see "done" but when kindle restart is again in "fastboot mode" screen...
Please, help i read a lot but no solutions for me.
Thanks for advance and sorry for my english.
jassker said:
I tried install a cm11 but in the process i brick the kindle fire hd, but now with the fastboot cable, i can enter on fastboot mode, but i used "KFHD_SRTv1.3.5" option 1, 3 and 6 to restart, in the kindle see "done" but when kindle restart is again in "fastboot mode" screen...
Please, help i read a lot but no solutions for me.
Thanks for advance and sorry for my english.
Click to expand...
Click to collapse
That tool is for the 7" KFHD. Don't use that one or you will hard brick that tablet. Use this one http://forum.xda-developers.com/showthread.php?t=2011126 You just use your USB cord if you have the 8.9 KFHD
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a command prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Jem-xxx-xxx. If you don't get that response, do not move forward.
Now use the tool per the instructions in the tutorial or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
LinearEquation said:
That tool is for the 7" KFHD. Don't use that one or you will hard brick that tablet. Use this one http://forum.xda-developers.com/showthread.php?t=2011126 You just use your USB cord if you have the 8.9 KFHD
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a command prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Jem-xxx-xxx. If you don't get that response, do not move forward.
Now use the tool per the instructions in the tutorial or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Click to expand...
Click to collapse
wow!!youre the best!!, thanks a lot, my kindle is now working normaly...
Do you know a manual to put cm11 in my kindle 8.9?
thanks again for your fast help!
jassker said:
wow!!youre the best!!, thanks a lot, my kindle is now working normaly...
Do you know a manual to put cm11 in my kindle 8.9?
thanks again for your fast help!
Click to expand...
Click to collapse
You can download the zip, check the md5sum, now drag and drop the ROM onto the internal SD card, boot into TWRP, "swipe" to factory reset, flash zip, wipe dalvik and CACHE only, reboot system, profit.
Sent from Nexus 7 flo running SinLess ROM 4.4.2 with ElementalX kernel using xda app-developers app
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.
I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
It says "Waiting for any device" the problem is that it's not recognized by the computer.
Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...
EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.
Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots