Develop Bugs

[Q] one x doesnt recognize usb in fastboot mode.

Hello,
ive been trying to change rom (not the first time),
and while in fastboot mode
any trying to burn boot.img, but in order to do that I must open the usb thruogh fastboot mode,
and my phone say it cant open the USB.
is it a problem with the sense 5?
ive downloaded again the htc sync manager.
and I can load the usb from the when the phone is on.
how can I fix it?
thanks for reading!

Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.

Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes

webpatrick said:
Download and unzip the attachement.
Open a command prompt to that folder.
Connect your device
Set it in fastboot mode
Type "fastboot devices"
Tell me what you see.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imageshack.us/f/811/wm6o.jpg/
nogotaclue said:
Actually sounds like you are referring to "failed to open usb master mode" and if that is the case it is simply because you have the cable plugged in when you are switching between hboot and fastboot. each time you want to switch, pull out the cable then reconnect when you have changed modes
Click to expand...
Click to collapse
It doesnt says now there is a problem with the usb, but it still wont load it on computer.

arnon124 said:
http://imageshack.us/f/811/wm6o.jpg/
It doesnt says now there is a problem with the usb, but it still wont load it on computer.
Click to expand...
Click to collapse
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.

webpatrick said:
Your device is recognized by fastboot, so you can flash a boot.img, the command is:
Code:
fastboot flash boot boot.img
Make sure you have copied the boot.img to the fastboot folder on your PC.
You cannot see your device in windows explorer when you are in fastboot.
Edit: You can in recovery when you mount your storage.
Click to expand...
Click to collapse
finished changing the rom, thanks alot for helping!

Fastbooting android whose recovery is not opening.

While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.

vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?

akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.

Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader

akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.

How do I sideload?

I have ADB installed, Android SDK.
I've tried to sideload and I get the error message "can't read".
Should I be changing the directory in terminal?
This is frustrating.
Thanks.

Anyone? Lol

koooba said:
Anyone? Lol
Click to expand...
Click to collapse
Is your phone coming up after using the command ADB devices?
What are you trying to sideload

No for whatever reason it's not.
I have the drivers installed, debugging on phone set.
Didn't list when I type advice devices.
What directory should terminal be in?
Wondering if I'm in the wrong directory perhaps?
Thanks

ADB could be anywhere and it'll work, double check the drivers and make sure the ADB drivers are installed and not just the MTP drivers.
What are you sideloading btw?

ADB can be anywhere, okay good to know. Thanks.
I'm trying to sideload Oxygen 3.2.1 since I'm having microphone issues - people can't hear me sometimes or my voice gets all messed up.
Apparently sideloading this update fixes this issue, at least for a few people it did.
When I connect the phone to the computer in regular mode, the device is listed.
When I go into RECOVERY mode with the phone, the computer doesn't find the device at all.
I'm going by the OnePlus instructions to turn it off and go into this mode.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.1/

unlock bootloader
install twrp
make Nandroid Backup
download FreedomOS 3.2.1
move to phone
Wipe Caches and system, no need to wipe data (in TWRP)
Install FreedomOS ( u may need to redownload SU and flash manually if not working in FreedomOS Aroma)
Done... If still issues do a clean flash, go to twrp and Advance Wipe (Caches, Data, System) DO NOT DO STORAGE!!!!
No this will not Void your warranty with OnePlus
Click here for better instructions

Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????

koooba said:
Thanks Brad, first I'd like to try sideload method first if at all possible.
I can't figure out why the computer won't recognize the device in RECOVERY MODE...? Tried everything, I have to be doing something wrong.
Drivers are okay when it's not in recovery mode
The weird thing is, when the phone is OFF and plugged into the computer, the computer recognizes the device when I type "adb devices".... WTH????
Click to expand...
Click to collapse
what drivers did u install, so when u type "adb devices" nothing at all comes up?

I installed the drivers that are on the phone when you plug it in.
When the phone is on and plugged into the computer, it recognizes it.
This is what I get -> http://imgur.com/B3a8AMg
When I turn it off and plug it in, it recognizes the device.
When I'm in recovery mode, it doesn't recognize it at all.

i am not sure how stock recovery works, but if u are in fastboot mode, does it recognize?
with it unathurized that means u did not check the box on the phone when plugged in to ur computer.... u should get this on your phone when booted into the OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i would try to boot into fastboot mode and push the file to ur phone and install via zip in stock recovery
and try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118

I checked that box off, yes.
I'm about to give up, now it's not even showing a "storage" folder at all when plugged in.
Cannot even copy files into the phone, no storage showing.
OP, so many problems and it's only 4 days old.

anyone, please

Question Booting GSI's

hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers

stevendeb25 said:
hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
Click to expand...
Click to collapse
I really don't know much about GSI's, but don't you have to disable AVB before flashing one? Basically disabling vbmeta verification and verity (which would require a factory reset afterwards)? Not sure if you've done or tried this, so just throwing it out there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com

Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com

Morgrain said:
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
The bootloader has nothing to do with the bootanimation. If you see the bootanimation, the bootloader has done it's work ages before.

From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Nothing data corrupted
Rebooted back to bootloader
Fastboot reboot recovery
Data reset
=Google logo
Fastboot reboot bootloader
Fastboot flash boot magisk_patched.img
Fastboot reboot
=Bootanimation
ADB ain't enabled in boot.imgs so can't pull logcats to try to see why no boot.
Tried lineage, octativeos, LeOS, phusson, same with all GSI's
P.s phone is intact and easily put back to stock

stevendeb25 said:
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Click to expand...
Click to collapse
As @Lughnasadh said, it looks like you're missing the disabling of AVB by flashing Google's custom vbmeta.img before installing the GSI image.
Note: If your device has adopted Android Verified Boot (AVB), download and flash the following image to disable AVB before flashing a GSI: vbmeta.img
Click to expand...
Click to collapse
As above, see here: https://developer.android.com/topic/generic-system-image#flash-gsi (blue box).

hi thanks for that, flash vbmeta
still stuck on bootanimation.
i have tried a number of gsi's does this error matter when flashing gsi? "Invalid sparse file format at header magic" still installs fine

Help "failed to write partition" error Redmi 5A (riva)

I had installed in this phone a custom rom a few months back for my friend. Yesterday he told me that the device froze when he was browsing the phone gallery app, and a few minutes later the phone rebooted and couldn't pass the mi logo (so the system wasn't loading I guessed, because the logo of the ROM wasn't showing). I tried to enter TWRP, but even there the phone would get stuck on the TWRP splash page and rebooted back to the MI logo. So I tried to reinstall TWRP (I have still access to fastboot mode) and, after, a newer version, but the problem was the same. I tried booting a recovery image without installing it (fastboot boot twrp.img) and the problem was similar, but instead of rebooting to the MI logo, the phone would get stuck on the TWRP logo. I tried with OrangeFox recovery too, but same problem. I read in another post that it may be a problem with the /data partition, so I (fastboot erase userdata) and tried again the above recovery installation, but it didn't work. I, then, tried to wipe all partion via fastboot, and tried the command "fastboot erase system -w", but it didn't work either. So I tried the way to restore the phone with MiFlash tool, I found the firmware I needed, I flashed it, and after ~4s it gave me the error "failed to write partiton" (see image).
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried with another firmware (this time based on Oreo instead of Nougat), same error. I searched a solution for this error, but I found nothing helpful. Now I have the phone working (=it can power on) and can access to fastboot, but don't know what to do. Can someone out there, with maybe a clearer idea of what's going on, help me? Thanks in advance

Update:
I found out that the problem is flashing this file "gpt_both0.bin" (which is the partition table). Every firmware that I tried failed to flash when trying to fastboot this file. So I tried to remove the line (
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash tz error" && exit /B 1
) from the flash_all.bat and everything was flashed without errors, but the phone won't start, so this file is necessary. Flashing it separately gave me the same error (failed to write partition). So, I ask again for help, hoping that someone will come to save me

I have same issue. Did you get any working method?

amitkr.xda said:
I have same issue. Did you get any working method?
Click to expand...
Click to collapse
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work

TheMagicWafer said:
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
Click to expand...
Click to collapse
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool

amitkr.xda said:
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
Click to expand...
Click to collapse
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar

TheMagicWafer said:
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
Click to expand...
Click to collapse
How can I boot in fastboot? It's not going in fastboot or anything

amitkr.xda said:
How can I boot in fastboot? It's not going in fastboot or anything
Click to expand...
Click to collapse
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo

TheMagicWafer said:
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
Click to expand...
Click to collapse
Nothing works, it's just blank screen, no vibrate, no logo nothing

amitkr.xda said:
Nothing works, it's just blank screen, no vibrate, no logo nothing
Click to expand...
Click to collapse
I'm sorry, but I'm not an expert and I can't help you any further. If one day I find a solution, be sure I'm going to write it here

have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died

Avisadius said:
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Click to expand...
Click to collapse
Already tried, and it gave me the same error. I really hope it's not a motherboard issue, because a replacement is not worth it. Thanks anyway