Here is what is happening: Adb and fastboot detect the device perfectly fine. Fastboot only *sometimes* works if I have the command waiting in the command prompt window saying *waiting for device* and then plug the USB cable in. Most of the time, ill get partial responses which render the command incomplete or incorrect. I have scoured the posts, the web, and although ive come up with similar issues, nothing quite exactly 100% the same.
Finally found someone on reddit under one of the two posts when searching for: fastboot receiving incomplete commands that is experiencing the same thing.
System specs: Windows 8.1 x64
Project Fi variant of moto x4 XT1900-1 32GB Lastest security patch, Oreo 8.1
Bootloader unlocked. (after trying the fastboot oem get_unlock_data command 50,000 times it seems like i got the data needed to get the unlock code off of the motorola website, but finally, flashing_unlocked shows in the bootloader)
YES im using the original cable that came with the device.
YES developer tools are enabled
YES USB debugging is enabled
YES Ive done the erase all data (factory reset) option in the reset options
YES the correct drivers are installed for adb/fastboot
NO i havent been able to flash anything because of this issue.
YES, ive tried flashing many different bootloaders, roms, etc, but cant do anything because the very fundamental step of flashing TWRP (or anything else for that matter) with fastboot fails repeatedly.
Example:
E:\lineage_x4>fastboot flash abl_a abl.img
(bootloader) max-download-sizel_a: not found
sending 'abl_a' (1024 KB)...
in the bootloader logs it says:
cmd: getvar: partition-type:abl_a
cmd: getvar: max-download-sizel_a
cmd: download: 00100000ad-size
Hopefully Ive provided enough info, and i hope someone knows what is causing this.
if the partition is flashing dont worry about the
(bootloader) max-download-sizel_a: not found
munchy_cool said:
if the partition is flashing dont worry about the
(bootloader) max-download-sizel_a: not found
Click to expand...
Click to collapse
That's just the thing, it's not flashing. Eventually, it times out.
what happens when you boot into twrp from fastboot?
fastboot boot twrp-name.img
munchy_cool said:
what happens when you boot into twrp from fastboot?
fastboot boot twrp-name.img
Click to expand...
Click to collapse
trying now to give you the exact messages / error, ill let it time out too, just for completeness.
mchamb said:
trying now to give you the exact messages / error, ill let it time out too, just for completeness.
Click to expand...
Click to collapse
E:\lineage_x4>fastboot boot twrp-x4-BOOTABLE.img
< waiting for device >
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 807.286s
bootloader log says
cmd: download:01533000
mchamb said:
E:\lineage_x4>fastboot boot twrp-x4-BOOTABLE.img
< waiting for device >
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 807.286s
bootloader log says
cmd: download:01533000
Click to expand...
Click to collapse
fastboot devices?
does your device show up?
munchy_cool said:
fastboot devices?
does your device show up?
Click to expand...
Click to collapse
Yes, shows up in adb as well.
mchamb said:
Yes, shows up in adb as well.
Click to expand...
Click to collapse
3 possibilities.
1. bad usb cable.
2. bad usb port.
3. both.
munchy_cool said:
3 possibilities.
1. bad usb cable.
2. bad usb port.
3. both.
Click to expand...
Click to collapse
I'd considered these things as well. However,
New cables,
tried all 4 ports, and can still flash my samsung w/ odin (yes ive removed all the drivers samsung related since trying)
Device is only a month old.
Any other possibilities?
I've got nothing. If the device wasn't showing up, you would have to install the device drivers from Motorola. Contact Fi, Motorola or both. Fi tends to have good customer support (but if we can't figure it out, then I'm not sure Fi will be able to either).
MisterFribble said:
I've got nothing. If the device wasn't showing up, you would have to install the device drivers from Motorola. Contact Fi, Motorola or both. Fi tends to have good customer support (but if we can't figure it out, then I'm not sure Fi will be able to either).
Click to expand...
Click to collapse
Yeah, my thoughts were along these lines as well. Im going to boot up a live copy of Ubuntu and try my luck flashing there. I suspect its something with the usb controller, windows 8.1 and win8.1 being 64 bit.
if your Samsung works fine. it's a bad usb port on the phone. does data transfer work to and from phone when connected as a storage device?
munchy_cool said:
if your Samsung works fine. it's a bad usb port on the phone. does data transfer work to and from phone when connected as a storage device?
Click to expand...
Click to collapse
Yes it does. Verified copying to and from works correctly. (had even verified checksums because i didnt think it would do it correctly)
mchamb said:
Yes it does. Verified copying to and from works correctly. (had even verified checksums because i didnt think it would do it correctly)
Click to expand...
Click to collapse
So, after booting up Ubuntu, Same thing happens.
I took the same cable and my external drive with all the images/zips on it over to my girlfriends Win10 pc, and bam everything worked first try.
If anyone wants to help me try and figure out what the deal is with my USB controller, by all means, i havent changed anything on it yet. Its the Intel eXtensible USB 3.0 Host controller that i suspect is the issue here.
Verified: fastboot only works smoothly in Windows 10, no idea why.
Related
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
I was on my phone and an app closed. Then it closed again when I tried to re-open it. Third time's the charm, it closed again and then google services stopped. Then my phone shut off. I wouldn't turn on, so I had to do the power button+volume down to get into the bootloader menu. I tried to boot up and was stuck with a bootloop. I downloaded a factory image and the latest android sdk.
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
melgibson666 said:
So here is where I hit the issue. No matter what command I issue "fastboot flash bootloader bootloader.img" or even "fastboot format cache" I get the same error "Failure <remote failure>".
I tried a different image to see if that was the issue and it didn't help. The device is being detected through fastboot. Any ideas?
Click to expand...
Click to collapse
My idea is that the bootloader is locked.
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
NLBeev said:
My idea is that the bootloader is locked.
Click to expand...
Click to collapse
It is not.
danarama said:
Bad cable or USB port perhaps or drivers not installed properly. The result of these can often be fastboot devices will show the device as connected yet be unable to flash.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
melgibson666 said:
It is not.
I uninstalled and reinstalled the drivers to be sure, used the original USB cable the phone came with, and tried 3 different USB ports. Still not working.
Click to expand...
Click to collapse
Please screenshot the error.
melgibson666 said:
. . .Bootloader unlocked
. . .reinstalled the drivers to be sure,
. . .used the original USB cable. . .
. . .tried 3 different USB ports . . .
. . .fastboot detected the device.
Still not working.
Click to expand...
Click to collapse
The quotes from you posts gave me the impression that the hardware is OK.
Probably the drivers on your PC are also OK.
I assume the command 'fastboot devices' responded a device ID.
Other issues could be:
- the dosbox and fastboot commands on the PC are not started as administrator;
- the driver on the pc is an adb-driver and not an adb combined driver;
- the version of fastboot is obsolete;
- images flashed before were corrupt;
Possible actions:
Make sure the fastboot and also adb files including the dll's are up to date.
Check if the command 'adb devices' works.
Try to adb sideload a (stock) rom.
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is going wrong here!
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
ptn107 said:
What's the file size of your boot.img? It should only be about 30 mb. It's not frozen it's still attempting to transfer the img to your device.
Click to expand...
Click to collapse
Thanks for your reply, the file sizes are correct, I tried these from twrp download page: twrp-3.2.3-1-payton.img (29.5M) and twrp-3.2.3-0-payton.img (25.9M) - same result.
Zokhii said:
Hi guys, I got a new XT1900-7 today, tried to install TWRP but I'm not able to boot it with "fastboot boot boot.img".. Yes the bootloader is unlocked, cmd is running as admin, adb and fastboot stuff is correctly installed, motorola drivers are installed, tried different cables and ports... I don't get it why it does not work and I'm absolutely NOT new to this business... Additional info: Running OPWS27.2.4, patch level August 1, 2018.
See the cmd screenshot below, it freezes there... Any help is much appreciated, absolutely don't know what is goind wrong here!
Click to expand...
Click to collapse
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
gee one said:
I have a laptop that doesn't work with fastboot, but adb is fine. Same cable and phone on a different computer and fastboot works. Maybe try a different computer?
Click to expand...
Click to collapse
Will give this a try tomorrow, thanks a lot!
Edit: Still no luck. Tried it with linux mint and even there the same sh!t... wtf
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Neffy27 said:
Ensure Motorola drivers are up to date and even try a different USB port.
With Windows, does it see the phone in device manager while in fastboot?
Click to expand...
Click to collapse
Latest drivers from Motorola Device Manager are installed and phone is properly recognized in device manager (used usb 2.0, 3.0 and 3.1 ports, nothing changes, same behavior). I tried it now with mfastboot but still nope..
Are you using minimal or full sdk (by Google) platform tools?
Neffy27 said:
Are you using minimal or full sdk (by Google) platform tools?
Click to expand...
Click to collapse
Minimal, I have also a Moto G5 and I don't face this kind of problems - only with Payton.
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Neffy27 said:
I recommend switching to full sdk. You don't have actually download all the packages, just the platform tools and it keeps itself updated. I stop encountering these random issues when I switched from minimal two phones ago. Issues like yours are; 9 out of 10, driver issues.
---------- Post added at 06:13 PM ---------- Previous post was at 06:13 PM ----------
The very next thing to try, would be reflash everything.
Good luck.
Click to expand...
Click to collapse
Unfortunately still no progress with full sdk and latest platform-tools, I'm giving up (for now).. I don't get it man, I'm not able to do anything in bootloader... for example when I try "fastboot flash partition gpt.bin" it freezes at sending OR it throws instant failed, the bootloader log menu shows that something is downloading but nothing happens... I relocked the bootloader (locking and unlocking is no problem) again and I am going to use it for a while... otherwise I will do a mistake somewhere and will brick it... Thanks for taking the time to help me haha
I'm having this same exact issue, just got this phone (XT1900-1) for my wife and she wants a custom rom, my own phone booted into twrp no problem.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Maybe try the fastboot in that link. I read through the thread and no specific reason why they suggest that version but it allowed people to flash back to stock. I used it last week to go back to stock before Lineage.
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Sorry, beyond my expertise. Maybe it's USB c port on the phone issue? Intermittently dropping the connection? Or have to tried flashing the 8.1 sick from the thread I posted? Maybe the factory ROM is messed up some how. I honestly don't know and those suggestions aren't based in any real knowledge.
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Slayer5934 said:
No effect still stuck on "downloading 'boot.img'..." but thank you, should I try flashing TWRP without booting? Would that even work?
or maybe an alternative way to get TWRP like a rooting method or the such?
Edit: Im going to try a factory reset, who knows maybe itll work?
^Nope
Edit 2: ERRR ota update is also failing to install, all I did was unlock the bootloader, havnt been able to do anything else.. wtf is going on.. What should I do from here, lock the bootloader and try ota again?
Edit 3: Something strange is going on, the fastboot commands are failing randomly I just noticed, see the attached image... Im spamming the same exact command once every second and it intermittently works.
Click to expand...
Click to collapse
Had exactly the same behavior like you (especially Edit 3), I tried it on a different computer from 2013 with usb 2.0 ports and it worked..
No other cable, no usb port, no adb and fastboot changes and no other drivers - just put all the stuff on a other computer and run the commands from there :good:
ptn107 said:
Code:
fastboot version 1:7.0.0+r33-2
Android Debug Bridge version 1.0.40
Version 4986621
In linux mint do you have the same versions of the tools as above?
Click to expand...
Click to collapse
Yeah, I'm on 1:7.0.0+r33-2 too.. I guess it has something to do with my mainboard or usb controller, weird weird weird
A different pc solved the issue.. wtf.. thank you..
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
dirktacular said:
I have the exact same issue, random commands are failing. I tried 2 different computers, Linux and Windows. It just hangs at downloading boot.img. Flashing either immediately fails or hangs and I can't ctrl-c to kill the process, have to disconnect my phone.
Click to expand...
Click to collapse
Yeah I wish we knew the exact problem and solution but you might just be stuck trying new computers for eternity sadly..
So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.
Take the Oreo .zip, unzip it, boot into bootloader, open up a Command Line/Terminal (depending on your OS), cd to the unzipped Oreo folder, type in fastboot flash-all, wait for that to end, then reboot into bootloader again and fastboot flash both boot and system (it should automatically flash it into the assigned partition)
I did this in order to update to MR1
downgrade issues
not what was being asked.
you need to use a 3rd party usbA to usbC cable (stock cable doesnt play well)
once thats done, test its connected using 'fastboot devices' you should see the serial number of your phone.
then run the flash_all command (remember to unlock bootloader and critical partition beforehand)
minimal adb and fastboot installer PLUS android bootloader interface driver is required if not installed already.
good luck
I just bought 4 micro USB to type c usb adapters from Walmart's website for 7 dollars. I can use all of my previous cables from my old phones. I haven't had one issue with them and my old fast charger from my Nexus 6 works and charges the phone rapidly. It's kinda clunky but beats spending 30 bucks on 1 cable.
It was a long night and I was on my 5th beer when I typed all that up!
My USB-C cable from OnePlus works fine with this phone on my laptop
I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
I'll give it a go, but I'm already using a 3rd party usb3 to typeC... I could try with the stock USBC cable as my desktop has one?
The phone is receiving the command from the PC because no matter what fastboot comment I type the second I hit enter it goes to this same screen.
ABD commands work perfectly though, just fastboot has this issue.
Can't wait for TWRP.
Click to expand...
Click to collapse
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.
jal3223 said:
I believe TWRP has already been released. Check the new kernel thread in the Development section. He states that by flashing his kernel, TWRP is also installed along side it. I haven't tested myself yet though.
Click to expand...
Click to collapse
Don't I need to use fastboot to flash the kernel :-/
Sent from my Phone 2 using Tapatalk
have you solved this problem?
Spunkybob said:
So ive upgraded to 9 but I dont like it... volume menus changed, wifi keeps dropping out (even after disabling auto turn on) etc. and I was very happy with 8.
I've been following the instructions from the Razor site to downgrade but whenever i run a fastboot command from the bootloader it just changes to the "powered by android" screen with a tiny "Press any key to shutdown" at the top.
Has anyone been able to do this successfully?
I've used fastboot and ADB a lot in the past so no idea why its doing this.
Click to expand...
Click to collapse
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
fastboot flashing unlock_critical doesn't work for you?
Ventigo said:
fastboot flashing unlock_critical doesn't work for you?
Click to expand...
Click to collapse
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day
capxcom said:
Finally it works!I tried handurds of times,every time I enter flash unlock critical the phone will show up that tiny message on the top left press any key to shut down.I was thinking about selling this phone,then I changed the USB a-c cable and tried with a different USB port,and suddenly it worked!
I flashed the latest stock firmware and the new customised kernel,now it works great! The battery draining is normal I only need to charge it once a day
Click to expand...
Click to collapse
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.
Lucifer6 said:
What did you do differently? I still get the same little text at the top which says press any key to shutdown after any fastboot command. Please help me because I'm so frustrated with this issue.
Click to expand...
Click to collapse
Change the USB cable and try a different USB port,I think that may work for you.good luck!
capxcom said:
Change the USB cable and try a different USB port,I think that may work for you.good luck!
Click to expand...
Click to collapse
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
I just use a different cable and a different USB port , which I did all this before and it didn't work,but I don't know why it worked this time.
I just use the command" xxx\fastboot flash unlock_critical"(hope I memories this right,better find it on the Razer website),the same command with the Razer phone 1 which is posted on Razer official website .You have to unlock the bootloader first just like the Razer phone 1, the only difference is you don't need to unlock the bootloader by typing unlock bootloader on the pc ,you can just operate on the phone to unlock bootloader by pressing the "unlock the bootloader "in the bootloader interface.
When you use the command to unlock the critical ,it might let you to select yes on the phone's bootloader interface ,you can also see it on the CMD of you pc,it say something like xxx success,and if you run the command again it will say something like " unlock failed (already unlocked)"
Then you can try with flashing the stock firmware to see if you unlock the critical successfully,if you can flash the stock firmware then you can use any fast boot command on this phone .I installed the costume kernel right after I flashed the stock firmware.it works like charm.:fingers-crossed:
now the phone never get over heating again and the battery can last a whole day under my havey use.
---------- Post added at 07:47 AM ---------- Previous post was at 07:35 AM ----------
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Maybe you can also try to install the right bootloader driver which can be found on Razer website ,just check the official tutorial about flashing the stock firmware for Razer phone 1.
The bootloader driver is different from the adb diver.Better do everything exactly the same as it says in that tutorial step by step.
capxcom said:
I am in the same ****.I think we not only need to unlock the bootloader but also need to unlock the critical.But none knows how to unlock the critical.I am stuck in here too.Hate this stupid phone.
Click to expand...
Click to collapse
Edit: my phone didn't load newer posts
For everyone else, I was able to do this at work yesterday and I'm back on 8 and loving it.
Edit 2: it was either the different cable (same one as at home just lives at work) or the laptop did something different.
Sent from my Phone 2 using Tapatalk
Lucifer6 said:
I've tried that with 3 different cables across 6 different usb ports on 2 diff computers and nothing seems to work.. which way worked for you? or what fastboot command did you do that was successful?
Click to expand...
Click to collapse
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
Hey mate, for me I think the issue was that first I installed the fastboot drivers on my desktop then when I changed her it to the bootloader driver it didn't take correctly.
I'll clear out my driver cache on the PC and try the correct driver and see if it fixs the issue there.
Click to expand...
Click to collapse
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
If you can install the stock firmware you should be able in use any fast boot command
capxcom said:
Just follow this instruction to install the driver .
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
Click to expand...
Click to collapse
I've already done it just saying what my issue was.
Sent from my Phone 2 using Tapatalk
Spunkybob said:
I've already done it just saying what my issue was.
Click to expand...
Click to collapse
Good for you!
I'm suggesting everyone to unlock the bootloader and the critical first before start to use it.My last RP2 can't start up ,it will freeze on the starting screen as I didn't do anything before using it,I can't do anything with it as the locked bootloader.Lucky for me,I returned it and then I bought a new one .I love this hardware but Razer's software team should be fired !Just hire someone from xda should work perfectly:laugh:
I've basically two questions: First my concrete problem and second "how can I debug problems with the horrible platformTools"? Maybe you can help me solve both.
1. fastboot fails with "unknown command"
I've sucessfully build AOSP Android 10 via the instructions from Sonys Open Devices. But I'm currently stuck at the last step - flashing the images on my phone. I've successfully put the device in fastboot mode (LED is glowing blue, and "fastboot devices" lists a connected device).
But sending the vendor image fails with an "unknown command"-error
Code:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Sending 'oem' (211868 KB) FAILED (remote: 'unknown command')
I'm using the newest platformTools on Ubuntu Linux 18.04. My bootloader is unlocked and I've already installed other Android Versions in the past on the phone. Any idea whats going on here and how to fix it?
2. How to debug it myself?
And as a more general approach, as some problems with fastboot/adb appear to occure almost everytime I try to use it: Any tipps on how to find the cause of the problem myself? Any logs which I should check? Any known problems which I should be aware of?
AllesMeins said:
./fastboot flash oem SW_binaries_for_Xperia_Android_10.0.7.1_r1_v3_yoshino.img
Click to expand...
Click to collapse
EDIT: Does THIS help?
SXUsr said:
EDIT: Does THIS help?
Click to expand...
Click to collapse
Unfortunaly not - I already had a pretty recent version, but did an update to the newest nevertheless. Problem stays the same.
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
AllesMeins said:
I'm thinking about trying to flash the other parts first but I'm still reluctant, because I'm afraid that I might end up without a way to go back, if fastboot doesn't work reliably.
Click to expand...
Click to collapse
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
SXUsr said:
Try it, you can always rely on EMMA to go back. I'll happily test if you want?
Click to expand...
Click to collapse
No luck... Tried it for boot, system, vendor and everytime the same error. But it seems to be a Linux-Problem. I tried it with my flatmates Windows 10 PC and there everything worked. But of cause this is no solution for the future. Any ideas why the phone doesn't understand the commands, when coming from my system?
AllesMeins said:
Any ideas why the phone doesn't understand the commands, when coming from my system?
Click to expand...
Click to collapse
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
SXUsr said:
I don't, but I assume you've set up everything properly. Can the PC see the phone under the adb devices command?
Click to expand...
Click to collapse
In normal mode: yes.
$ ./adb devices
List of devices attached
BH906VHH9E device
Click to expand...
Click to collapse
In fastboot mode no - but there it is listed under fastboot devices
I wish I could be of more help, I really want to see 10 on this phone.
I managed to flash it on Windows, but version is 5 , but got loopboot afte reinstalling PIxel Experience Plus.
https://forum.xda-developers.com/xperia-xz1-compact/help/pixel-experience-10-0-plus-how-to-t4077747