When trying to install TWRP most guides show that you have to switch partitions before flashing TWRP but when I try using
--set-active-=b
It returns white an unknown option error
"unknown option -- set-active=b"
The device can still boot properly and I am using the platform tools r 29.0.6
On another note do I actually have to switch partitions? And is there another way to install TWRP?
Edit:
I have also tried using "set_active b" powershell doesn't recognize this command
Edit 2:
Problem solved, thanks _mysiak_
Remove/uninstall fastboot.exe from all locations on your PC and then try to use the latest platform tools again.
He never put fastboot before the command
He put "--set-active=b"
It must be "fastboot --set-active=b"
garylawwd said:
He never put fastboot before the command
He put "--set-active=b"
It must be "fastboot --set-active=b"
Click to expand...
Click to collapse
I guess (and hope) that he used also fastboot command, otherwise the first error would be "unknown command" as well, and not "unknown option". Hopefully OP will let us know. [emoji846]
garylawwd said:
He never put fastboot before the command
He put "--set-active=b"
It must be "fastboot --set-active=b"
Click to expand...
Click to collapse
Sorry about not clarifying this but yes, I did place the fastboot command
_mysiak_ said:
Remove/uninstall fastboot.exe from all locations on your PC and then try to use the latest platform tools again.
Click to expand...
Click to collapse
Just tried it and now and it seems to be working, I'll try to see if I can flash TWRP
Related
I tried to upgrade my recovery image to RA-hero-v1.6.2.
However I got a problem
I use adb shell method to flash the new recovery image.
when I type mount -a it show four lines of fails. and then I type flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img. After that I press reboot. My phone is now keep stay in HERO BOOT SCREEN. nothing happen. please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
For adb + fastboot method
I type adb shell reboot bootloader, it success.
but when I type fastboot boot recovery-RA-hero-v1.6.2.img it said recovery-RA-hero-v1.6.2.img cannot be load. Please help.
Can you boot your phone normal now at all or not?
If you can, use BTDAG's guide in my signature and install the custom recovery using the flashrec method.
I cannot it stuck at the "HERO" boot screen :'(
what I can do is that I can use the adb shell the browser the files inside the phone.
try flashing it via android commander mate i had that problem my self once and that fixed it
skedone said:
try flashing it via android commander mate i had that problem my self once and that fixed it
Click to expand...
Click to collapse
He can flash the recovery through Android Commander? .... Interesting.
skedone said:
try flashing it via android commander mate i had that problem my self once and that fixed it
Click to expand...
Click to collapse
Can you provide me steps?
animation said:
Can you provide me steps?
Click to expand...
Click to collapse
http://tinyurl.com/232pnzr
Have a go,.... then report back.
ddotpatel said:
http://tinyurl.com/232pnzr
Have a go,.... then report back.
Click to expand...
Click to collapse
the link is just link to google?
Its for Android Commander. Either try that,... Or see if you can get into the recovery you currently have,.... wipe what you can, then flash another rom.
ddotpatel said:
Its for Android Commander. Either try that,... Or see if you can get into the recovery you currently have,.... wipe what you can, then flash another rom.
Click to expand...
Click to collapse
I can't go into the recovery mode.
I can only go into the fastboot mode.
Try this,... Go into fastboot.
Hit BACK to enter the fastboot bit.
I should now say FASTBOOT USB or something similar.
Then you need to cd into the right directory using CMD.
example,... I have to type...
cd c:\sdk\tools ................But it might be different on yours.
then type
fastboot devices
It should bring up your device serial number.
Then type
fastboot oem rebootRUU
fastboot erase cache
Then reboot.
ddotpatel said:
Try this,... Go into fastboot.
Hit BACK to enter the fastboot bit.
I should now say FASTBOOT USB or something similar.
Then you need to cd into the right directory using CMD.
example,... I have to type...
cd c:\sdk\tools ................But it might be different on yours.
then type
fastboot devices
It should bring up your device serial number.
Then type
fastboot oem rebootRUU
fastboot erase cache
Then reboot.
Click to expand...
Click to collapse
What are these two lines did? fastboot oem rebootRUU
fastboot erase cache
I think it erases old data?
animation said:
ddotpatel said:
animation said:
After reboot? what should I do?
when I type fastboot boot recovery-RA-hero-v1.6.2.img it always said
downloading 'boot.img' ... FAILED <remote: not allow>
Click to expand...
Click to collapse
I didn't say that?.... Try what I said to erase cache,... then see if it boots.
Click to expand...
Click to collapse
I tried, but it also stuck at the boot screen.
Click to expand...
Click to collapse
The only other thing I can suggest is go into fastboot,...
then run,...
fastboot oem rebootRUU
fastboot erase cache
Keep it plugged in, then run an RUU .exe.
,... Then start from scratch again,...
sorry its droid explorer and here is link to info about program and its pritty easy to use
http://de.codeplex.com/wikipage?title=Features&referringTitle=Home
try the HEROIMG.zip method
Hello,
just another idea:
- download an original RUU.exe (preferably of an older version, rootable) and extract rom.zip (a lot of guides in the forums)
- rename to HEROIMG.ZIP and put in sdcard root
- restart hero with volume down pressed
- normally it should find the heroimg.zip and flash it and you are back to normal
OK so for reasons beyond me, I can't flash any sense 4.0 roms due to constant boot up as if kernel is not installing, even tho sense 3.6 kernels and roms install just fine. Also I can lock and unlock bootloader thru ADB and well and flash recovery, but if I try flashing bootimg I get an error "device not found" message??? I am s-on, on global firmware and prior to this problem was running cm9. I've RUUed back to stock several times with the problem still continuing. ALL, and I do all help is appreciated.
You try adb devices?
Did you try to fastboot flash boot nameofimage.img?
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
You try adb devices?
Did you try to fastboot flash boot nameofimage.img?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You cant do it in adb. You must be in fastboot. Make sure the device is seen by typing "fastboot devices" while in fastboot. Then flash the boot.img with "fastboot flash boot boot.img"
cslingerland said:
You cant do it in adb. You must be in fastboot. Make sure the device is seen by typing "fastboot devices" while in fastboot. Then flash the boot.img with "fastboot flash boot boot.img"
Click to expand...
Click to collapse
I'll try that and report back. Still what could have cause the problem I wonder
Sent from my ADR6425LVW using xda premium
ghostt021 said:
I'll try that and report back. Still what could have cause the problem I wonder
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Not sure... boot your phone to bootloader by using "adb reboot bootloader" then see if it shows up when you type "fastboot devices". if it does then you should be good to go
cslingerland said:
Not sure... boot your phone to bootloader by using "adb reboot bootloader" then see if it shows up when you type "fastboot devices". if it does then you should be good to go
Click to expand...
Click to collapse
Got " fastboot devices" is not recognized as an internal or external command, operable program or batch file.
Sent from my ADR6425LVW using xda premium
ghostt021 said:
Got " fastboot devices" is not recognized as an internal or external command, operable program or batch file.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You have to download it seperately... I cant look right now but a quick google search on rezound fastboot should do it. It isnt included with adb
Edit: got a chance to look it up. here you go. put the boot.img file in the same directory that this is installed and then do the previously mentioned steps.
http://www.mediafire.com/?4dx982z93w8z7wk
cslingerland said:
You have to download it seperately... I cant look right now but a quick google search on rezound fastboot should do it. It isnt included with adb
Edit: got a chance to look it up. here you go. put the boot.img file in the same directory that this is installed and then do the previously mentioned steps.
http://www.mediafire.com/?4dx982z93w8z7wk
Click to expand...
Click to collapse
Easiest way I find to get the right directory is to browse on your computer to the folder where fastboot.exe is located. For me it's C:\Android SDK\platform-tools
In other words when I open that platform tools folder the contents are adb.exe, fastboot.exe, good stuff like that.
So my exact steps are press start button in windows, choose "computer" from the start menu. Double click the C driver, double click Android SDK and then I'll see platform tools.
**Here's the important part**
Hold down shift, right click on "platform tools" and then choose the option "Open Command Window Here" from the right click dialog box. Holding shift gives you those extra options. I would have my boot.img file inside the platform tools folder because that's where fastboot.exe is located.
So shift and right click on platform tools, then click on "Open Command Window Here" and then make sure the phone is in fastboot-usb mode (boot to hboot and if it doesn't say fastboot USB at the top in bright red, you need to select fastboot from the list), and type the command "fastboot flash boot boot.img" without the quotes and press enter. When It's done writing use the command fastboot reboot or manually reboot and you should be good to go.
CharliesTheMan said:
Easiest way I find to get the right directory is to browse on your computer to the folder where fastboot.exe is located. For me it's C:\Android SDK\platform-tools
In other words when I open that platform tools folder the contents are adb.exe, fastboot.exe, good stuff like that.
So my exact steps are press start button in windows, choose "computer" from the start menu. Double click the C driver, double click Android SDK and then I'll see platform tools.
**Here's the important part**
Hold down shift, right click on "platform tools" and then choose the option "Open Command Window Here" from the right click dialog box. Holding shift gives you those extra options. I would have my boot.img file inside the platform tools folder because that's where fastboot.exe is located.
So shift and right click on platform tools, then click on "Open Command Window Here" and then make sure the phone is in fastboot-usb mode (boot to hboot and if it doesn't say fastboot USB at the top in bright red, you need to select fastboot from the list), and type the command "fastboot flash boot boot.img" without the quotes and press enter. When It's done writing use the command fastboot reboot or manually reboot and you should be good to go.
Click to expand...
Click to collapse
Think I've figured out the problem. It's not fastboot, but somewhere in the installation of the kernel. Kernel installs but the only kernels that will boot are 3.6 ones. All others regardless of kernel or Rom combo simply continuously boots or bootloops. Also computer see device in fastboot.... I'm clueless at this point.
Sent from my ADR6425LVW using xda premium
Hi everyone,
So after deciding whether to do it or not, i finally unlocked my BL yesterday. At least when i dial the secret number and look at BL info, it says "UNLOCK".
But I've been trying to flash cwm and rooting but it seems my device is not being recognised in cmd.
And i am having difficulties to install fastboot drivers again because my device is not showing up at all in device manager.
If you could kindly list some simple instructions on how to flash cwm and rooting on unlocked BL (Before you ask, yes i went through all the guides with no avail) or help me to install flashboot drivers properly, it would be appreciated.
Thank you and good day.
EDIT 1: I can boot in fastboot mode, But when i do adb devices, driver installation fails and thus the command for flashing cwm says "waiting for device" and never flashes.
EDIT 2: From what i have searched from previous posts , i need to wait 30mins, I will do that and report.... Hopefully it will work
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
EpicLordPhone said:
If you can boot into fastboot then do fastboot devices, adb devices are commands in adb mode, not fastboot mode, instead of flashing through adb use fastboot flash , hope I help!
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Sorry,
I actually did what u said.
But when i type the command (in cmd) : C:\Android>fastboot devices ---> The command is accepted and there is a driver installation which fails.
Even then i continued and typed : C:\Android>fastboot flash recovery recovery-clockwork-touch-6.0.3.1-p760.img
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
kirakun said:
But with the second command, it simply says "waiting for device" in the command window, but nothing happens.
Click to expand...
Click to collapse
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Lgeob said:
Put recovery.img on sdcard
Using Android Terminal Emulator:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
P.S Sorry my ENG
Click to expand...
Click to collapse
But I only have an unlocked BL and I do NOT have root either :/
kirakun said:
But I only have an unlocked BL and I do NOT have root either :/
Click to expand...
Click to collapse
What prevents get root?
Lgeob said:
What prevents get root?
Click to expand...
Click to collapse
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
kirakun said:
When i enter fastboot mode, pc installs drivers but driver installation fails. Cannot use fastboot commands. I try to re-install fastboot drivers (omap4boot drivers) but i cannot find device in device manager
Click to expand...
Click to collapse
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
okay ill try this
Lgeob said:
BL unlocked?
Get root with LGPwn.apk.
Thru Terminal put recovery.img
Click to expand...
Click to collapse
I don't have spritebud, so LGPwn.apk does not work
kirakun said:
I don't have spritebud, so LGPwn.apk does not work
Click to expand...
Click to collapse
Try this method.
Casserole said:
Try this method.
Click to expand...
Click to collapse
Thanks for the reply ^^ I was planning to use this as last resort XD Do u think its reliable o-o?
And also after installing this i can flash cwm ?
kirakun said:
And also after installing this i can flash cwm ?
Click to expand...
Click to collapse
Do it.Не ссы :good:
I can't seem to unlock bootloader on mi a3 on android 10 i get a lot of things on the powershell but nothing happens on the device.
Thank you in advance
Which commands do you use? Locking and unlocking the bootloader should have nothing to do with the version of Android you have installed
TheVow said:
I can't seem to unlock bootloader on mi a3 on android 10 i get a lot of things on the powershell but nothing happens on the device.
Thank you in advance
Click to expand...
Click to collapse
I keep getting commands in the power shell like
Press w for
Press E for
Etc
TheVow said:
I keep getting commands in the power shell like
Press w for
Press E for
Etc
Click to expand...
Click to collapse
Probably you installed an old version of the adb/fastboot drivers.
Download the sdk from here https://developer.android.com/studio/releases/platform-tools and extract the files in the adb folder in the volume (C
Phil_gloves said:
Probably you installed an old version of the adb/fastboot drivers.
Download the sdk from here https://developer.android.com/studio/releases/platform-tools and extract the files in the adb folder in the volume (C
Click to expand...
Click to collapse
well i did this but the same results
Here is what it looks like.
https://imgur.com/a/6x33Qfq
TheVow said:
well i did this but the same results
Here is what it looks like.
https://imgur.com/a/6x33Qfq
Click to expand...
Click to collapse
You are still using old version of fastboot. Either search&replace fastboot.exe in all locations on your hard drive, or remove fastboot folder from Windows PATHS.
_mysiak_ said:
You are still using old version of fastboot. Either search&replace fastboot.exe in all locations on your hard drive, or remove fastboot folder from Windows PATHS.
Click to expand...
Click to collapse
Thank you that Worked ! but now when i flash twrp and try to boot to it it always boots to fastboot. anyidea how to force twrp boot even tho i keep pressing Vol up when i try to boot to it.
thank you in advance
TheVow said:
Thank you that Worked ! but now when i flash twrp and try to boot to it it always boots to fastboot. anyidea how to force twrp boot even tho i keep pressing Vol up when i try to boot to it.
thank you in advance
Click to expand...
Click to collapse
Use the proper twrp built for Android 10 from here https://forum.xda-developers.com/mi...y-unoffical-twrp-xiaomi-mi-a3-t3987759/page16
The twrp.img you used only works on Android 9.
Twrp.zip will work on any Android version so once you flash the correct .img then you can reboot recovery and if you want install twrp by flashing twrp.zip
garylawwd said:
Use the proper twrp built for Android 10 from here https://forum.xda-developers.com/mi...y-unoffical-twrp-xiaomi-mi-a3-t3987759/page16
The twrp.img you used only works on Android 9.
Twrp.zip will work on any Android version so once you flash the correct .img then you can reboot recovery and if you want install twrp by flashing twrp.zip
Click to expand...
Click to collapse
Thank you this worked! time to install custom roms
To unlock bootloader of Mi A3
What are all the softwares we need for Windows 8.1??? I tried one mi flashing tool softwere but when I tried command 'fastboot devices:,, pc is not detecting my phone
You will need mi usb drivers for detecting your phone in fastboot mode
aslamzbr said:
What are all the softwares we need for Windows 8.1??? I tried one mi flashing tool softwere but when I tried command 'fastboot devices:,, pc is not detecting my phone
Click to expand...
Click to collapse
Use this
https://androidfilehost.com/?fid=24269982087012538
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!