I give up. Somehow I do not have the right tools to do this. I've run Linux exclusively for 22 years, and this unlocking does not work. I've done it before with my Moto X, and before that with my Razr, but I can not unlock this X4 nor Z2.
I went to this website: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
It refers me for fastboot to this site: http://developer.android.com/sdk/index.html
I go to the bottom of the page and download this since I run CentOS7.4: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
I dearchive, put it in /usr/local/share (where it belongs under Posix standards), and symlink to it in /usr/local/boot. I set the two Dev-Mode switches, and turn off the phone. Hold vol-down and power until it comes on in "AP Fastboot Flash Mode (Secure)". I connect the phone to the laptop and at the bottom the phone says in green: "Transfer Mode: USB Connected"
Then on the laptop:
Code:
# fastboot devices
ZY224CRZNN fastboot
# fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
# fastboot oem get_unlock_data
(bootloader) slot-countta: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.001s
# fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.000s
# fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
...
... and then it's hung forever. Both the X4 and Z2 behave exactly this way no matter which cable or how I wave my arms.
So I figured the factory cable must be the problem (even though I could see the device) and I ordered a high quality one from Monoprice. Same behavior. So I said to myself, well maybe the Linux fastboot is busted, or doesn't do large blocks or something, so I downloaded the Windows Android SDK and tried to install it in a virtual machine. But there's no fastboot, no install file, and no fscking instructions!
This is actually when I bought the Z2, because Motorola told me the X4 is -not- unlockable. So now I'm seeing the exact same behavior on the Z2.
In desperation I downloaded their whole goddamn Android Studio, which is about a half-a billion files, but that fastboot did exactly the same thing.
There must be some kind of secret that no one is telling. I've used Motorola phones and installed hacked firmware since cellphones began, but this now is intolerable. I must have root, on whatever phone I use.
Erm. What OS are you using? The fastboot package you are using isn't recognizing that oem command. Best to try a different fastboot package. Try the minimal one in joemossjr's flashall zips. Try a different operating system. I see Lenovo suggests Mac or Windows and nothing about Linux.
Yes I run CentOS7.4, as above. And I have tried Windows fastboot (as above) but failed in the way described above.
I would love to try joemossjr's minimal flashall, but downloading this:
https://drive.google.com/file/d/1MW4JWa8Zij36hsO0u41Zf-9a6OT3FpbA/view?usp=drivesdk
... it is now at 1.7GB and there's no clue as to how large it is in total.
Edit: 2.1GB and counting... Seriously what is this? The firmware shouldn't be larger than 400MB or so. Is flashall going to be a terabyte?
So it came in at 2.3GB. Using his fastboot in Windows10 it goes to
Code:
...
... and stays there forever.
I dug up an 8 year old moto-fastboot which does 4k blocks and worked on my much older phones. Trying to get the unlock data with it:
Code:
...
... and stays there forever.
Ok, I can sell this phone just like the X4. I paid $285 so should make some from it.
There are other good phones out there that are unlockable.
Quantumstate said:
Ok, I can sell this phone just like the X4. I paid $285 so should make some from it.
There are other good phones out there that are unlockable.
Click to expand...
Click to collapse
did you check out this thread?
https://forum.xda-developers.com/z2-force/how-to/how-to-unlock-bootloader-t-mobile-t3654657
***EDIT my bad, your not even the device id
i used the minimal fastboot app which is an older version of fastboot and adb for windows. i did not do mine on linux
So the final answer is Linux fastboot is BUSTED.
I had to actually install Windows on an old drive to make this work. Trying to unlock, running Windows in a virtual machine, does not work. My Z2 is now unlocked.
..
Quantumstate said:
So the final answer is Linux fastboot is BUSTED.
I had to actually install Windows on an old drive to make this work. Trying to unlock, running Windows in a virtual machine, does not work. My Z2 is now unlocked.
Click to expand...
Click to collapse
I use Linux to fastboot to my Z2 all the time. I use the Android studio told as the Debian database for adb and fastboot is old.
Uzephi said:
I use the Android studio told as the Debian database for adb and fastboot is old.
Click to expand...
Click to collapse
This sentence doesn't make sense.
You are not using the current Android fastboot for Linux, because it doesn't work. Normally I wouldn't bother, but maybe this will save someone else the days I lost.
Quantumstate said:
This sentence doesn't make sense.
You are not using the current Android fastboot for Linux, because it doesn't work. Normally I wouldn't bother, but maybe this will save someone else the days I lost.
Click to expand...
Click to collapse
Odd, because I, and many others have it working fine.
Well, it's a Festivus Miracle.
I am facing this problem right now with my nash... My bootloader is already unlocked. I've already installed custom roms many time on this phone (AOSiP and DU) as well as TWRP.
I went back to stock last Friday, and today when I was going to boot TWRP to install latest DU I get this error...
I have my Moto Z Play here as well and fastboot works on it just fine.
Could it be that my nash bootloader got locked again?! I'm going to try on another laptop at home (both with Windows 10).
And yes, I've already run fastboot commands on my nash on this laptop last week.
Just confirming that when I tried on my home laptop it worked, so it's definitely related to local installation of drivers most likely, because this morning I removed the drivers from my work laptop and reinstall them (https://androidfilehost.com/?fid=24269982087010424) and then it started working again on my work laptop.
Should anyone face this again, try to uninstall the Motorola drivers and reinstall them.
I can confirm that I'm having the same problems with the Linux version of fastboot with the Moto X4, but when I use the Windows version it works OK (though only if I manually run the Motorola Device Manager first, otherwise it also has this issue, which confirms it's something about the drivers).
This is really frustrating because I don't have a Windows computer, and had to ask a friend to use theirs just to test if this was the issue. I don't even own a license to any version of Windows more recent than Windows 2000, and I am definitely not going to buy one just for this damn phone.
And just to be clear, we're not suggesting that Linux fastboot is broken in general -- it works fine on my Pixel devices and Samsung devices -- but for at least some Motorola devices it appears to have problems with certain commands. I am also unable to boot to TWRP, for example, and it gives an "unknown command" error for that, too.
wemil said:
I can confirm that I'm having the same problems with the Linux version of fastboot with the Moto X4, but when I use the Windows version it works OK (though only if I manually run the Motorola Device Manager first, otherwise it also has this issue, which confirms it's something about the drivers).
This is really frustrating because I don't have a Windows computer, and had to ask a friend to use theirs just to test if this was the issue. I don't even own a license to any version of Windows more recent than Windows 2000, and I am definitely not going to buy one just for this damn phone.
And just to be clear, we're not suggesting that Linux fastboot is broken in general -- it works fine on my Pixel devices and Samsung devices -- but for at least some Motorola devices it appears to have problems with certain commands. I am also unable to boot to TWRP, for example, and it gives an "unknown command" error for that, too.
Click to expand...
Click to collapse
Update your fastboot and adb package. I am running the latest and have no issues.
Related
I am wondering if all the Fire Phones have the same output for the command:
sudo fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
When I run this, I get the output:
product: URSA
finished. total time: 0.019s
Click to expand...
Click to collapse
If someone from a different region (wie Deutchland, or the UK) could compare their output with mine, that'd be great. And if you happen to NOT get "product: URSA", I'd be ever so grateful if you could upload a copy of your bootloader for examination. :fingers-crossed: Na und mein Deutsch ist okej fuer ein Amerikan. So PM me if you have anymore information on the topic!
I have got a german fire phone with fire os 3.6.2. I'd like to contribute on this but i can't get fastboot to recognize my device.
First of all details on my setup:
- Windows 8.1 64bit
- Fire Phone 32gb (not rooted: factory default)
- Adb drivers downloaded with the sdk manager (followed the guide here on xda)
Steps accomplished:
- Connection with Fire Phone via adb - can browse the phones filesystem
- rebooted to bootloader via adb command "adb reboot bootloader" (then i should be in fastboot mode right?)
Problems:
- fastboot does not recognize the phone when booted in fire os, is it the normal behavior?
- fastboot, adb not working when in bootloader, or recovery sideload mode
- when in recovery sideload or bootloader my Windows device manager neither shows the android device, nor an unrecognized device for which no drivers were found
If you can guide me through the setup for fastboot i can post you my product strings and can try to copy the bootloader for you
You can use my guide for look and feel... To my mind your windows don't use the correct driver... You need to reboot and deactivate only signed drivers. Then you can choose the correct one and it should work
Which guide are you referring to? Used the sticky by SafinWasi.
Now i got it so far that a device called fastboot without a driver is shown in device manager while the fire phone is connected and staying in bootloader. But trying the drivers out of the sdk (downloaded the fire ones) the system always says that I need drivers for 64bit even booted my system allowing unsigned drivers.
I think I will try to use my hackintosh or a linux live distro next.
EDIT:
got it working with my hackintosh:
ran:
sudo fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
my output is the same one
product: URSA
finished. total time: 0.019s
Click to expand...
Click to collapse
If it helps you and can be done without rooting I can still try to get a copy of my bootloader if you tell me how to get it. I'll try to find out via google now, but i don't know if i'll succeed
kanyb said:
Which guide are you referring to? Used the sticky by SafinWasi.
Now i got it so far that a device called fastboot without a driver is shown in device manager while the fire phone is connected and staying in bootloader. But trying the drivers out of the sdk (downloaded the fire ones) the system always says that I need drivers for 64bit even booted my system allowing unsigned drivers.
I think I will try to use my hackintosh or a linux live distro next.
EDIT:
got it working with my hackintosh:
ran:
my output is the same one
If it helps you and can be done without rooting I can still try to get a copy of my bootloader if you tell me how to get it. I'll try to find out via google now, but i don't know if i'll succeed
Click to expand...
Click to collapse
Hmm....it seems that Amazon has changed the way it uses build props for fastboot variables. At first I thought it was Kodiak but now I see it's Ursa. Now I gotta rename ALL my device specific files...
I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.
I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. But i ended up getting them from googles platform-tools. Fastboot flashing unlock always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google
Different and and fastboot...
Just to confirm:
Is this a Verizon version?
Have you followed all of the steps for flashing a system image from https://developers.google.com/android/images
adb otherwise works (e.g., adb devices lists the phone)
fastboot otherwise works
I realize you already covered some of this. Unlocking will wipe anyway, so factory reset can't hurt.
foosion said:
Just to confirm:
Is this a Verizon version?
Have you followed all of the steps for flashing a system image from https://developers.google.com/android/images
adb otherwise works (e.g., adb devices lists the phone)
fastboot otherwise works
I realize you already covered some of this. Unlocking will wipe anyway, so factory reset can't hurt.
Click to expand...
Click to collapse
This is not a Verizon version. ADB is working and ADB devices works correct. Fastboot devices respond with the device serial number so it appears to be working properly. I've never had issues like this, don't know why flashing a factory would do anything but I probably will. And maybe fastboot flashing unlock from a 'fresh' device as I have my apps on it from a Google restore.
dontbeweakvato said:
I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. He called me I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. It always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google
Click to expand...
Click to collapse
It's one command. Did you get it?
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
It's one command. Did you get it?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
fastboot flashing unlock
C:\Users\Robert\Downloads\platform-tools>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
Im using the latest platform-tools from google, developer settings is ticked along with oem unlocking and usb debugging.
this is super frustrating
dontbeweakvato said:
fastboot flashing unlock
C:\Users\Robert\Downloads\platform-tools>fastboot flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
Im using the latest platform-tools from googles.
this is super frustrating
Click to expand...
Click to collapse
The latest minimal adb/fastboot work fine. Is usb debugging turned on? When you type fastboot devices do you see your phone?
The easiest way would be to re install minimal adb. At the end it ask do you want to re it. Say yes and it starts in the correct command prompt. Type fastboot reboot bootloader just to make sure it's communicating. If it doesn't reboot try another cable.
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
The latest minimal adb/fastboot work fine. Is usb debugging turned on? When you type fastboot devices do you see your phone?
The easiest way would be to re install minimal adb. At the end it ask do you want to re it. Say yes and it starts in the correct command prompt. Type fastboot reboot bootloader just to make sure it's communicating. If it doesn't reboot try another cable.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
usb debugging is on and fastboot devices returns correct with the serial number. guess ill reinstall tomorrow. im running command prompt and directing it to platform-tools folder that has adb.exe and fastboot.exe. It doesnt make sense. when in doubt redo EVERYTHING
did you enable OEM unlock from Developers Options ?
make sure you are using the latest ADB & fastboot
dontbeweakvato said:
I've tried fastboot flashing unlock, fastboot OEM unlock and a couple others All In bootloader mode. I've used a couple different versions ADB fastboot. A lot of people have been using the minimal ADB 1.4.2 which is the most current. But i ended up getting them from googles platform-tools. Fastboot flashing unlock always responds with
FAILED (command write failed (no error))
Then the device reboots.
Developer settings is on OEM unlocking is checked and USB debugging is also checked.
I don't know what else to do other than start from scratch entirely including deleting all ADB and fastboot files and maybe factory resetting the device although I've only had it for a day. It's amazing sitting at my home with my computer and a phone and being pissed off for 3 hours no one understands this unlike us. I know a lot of other people had the same issue. Anyone have any ideas they would be greatly appreciated. This is a pixel XL 2 from Google
Click to expand...
Click to collapse
I had the same problem as you. I kept trying for about 2 hours over and over. I was about to throw the phone against the wall when it finally just worked. I didn't do anything different when it worked than the previous 200 times it didn't.
awe.. never mind...
murphyjasonc said:
I had the same problem as you. I kept trying for about 2 hours over and over. I was about to throw the phone against the wall when it finally just worked. I didn't do anything different when it worked than the previous 200 times it didn't.
Click to expand...
Click to collapse
I've tried with maybe three or four different fast boots like minimal ADB a couple different versions and also Google on platforms-tools. I unchecked and rechecked developer options and oem unlocking and USB debugging. It's kind of pissing me off because last night I spent a good four hours trying every possible configuration. And I've never had this much problem on any phone ever it usually works the first time or second if I made an easy mistake but not after multiple hours and multiple command prompt checks and fastboot ADB checks. Yes I was about ready to throw this phone against the wall and return it which is unheard of in my world of Google perfection.
I was thinking "Fu***************************k!!"
It took me about 8 tries before I had success.
Just got mine. Not gonna unlock yet. Want to keep Android Pay for now. Actually if AdClear and Fake GPS work, I may stay stock unrooted.
Default backups seem to work good these days, even remembering passwords for apps.
Glad I didn't waste 4 hours trying to unlock. I spend way too much time flashing, updated and trying to trick SafetyNet. But it's all working great now with Magisk 14.3 on OG Pixel.
Can't wait to get the OTA notification and not start stressing out about ADB and fastboot....
Sent from my marlin using XDA Labs
akenis said:
Just got mine. Not gonna unlock yet. Want to keep Android Pay for now. Actually if AdClear and Fake GPS work, I may stay stock unrooted.
Default backups seem to work good these days, even remembering passwords for apps.
Glad I didn't waste 4 hours trying to unlock. I spend way too much time flashing, updated and trying to trick SafetyNet. But it's all working great now with Magisk 14.3 on OG Pixel.
Can't wait to get the OTA notification and not start stressing out about ADB and fastboot....
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I've honestly never stressed about anything going back to Nexus 4 on launch day. But this...... Fuuuuuuuccccckkkkk
dontbeweakvato said:
I've honestly never stressed about anything going back to Nexus 4 on launch day. But this...... Fuuuuuuuccccckkkkk
Click to expand...
Click to collapse
Feel your pain. Wasted a whole day a few weeks ago trying to switch from Super Su to Magisk and get Oct updates. Wound up trying to flash factory in ages using Crouton in a Chromebook.
Just saw that custom kernel is avail....so we can unlock and pass safety net. So TEMPTING. Just say NO. Gonna drink wine and watch Orville till these evil thoughts disperse.
Sent from my marlin using XDA Labs
I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >
dyingearth said:
I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >
Click to expand...
Click to collapse
Restart the phone and hold Volume down. Then run the fastboot command again if it doesn't work right away.
Sent from my Pixel 2 XL using Tapatalk
First of all, thanks Deuces and Northmendo for the idea to help people.
I have created a pretty easy all in one that will install the lasted adb and fastboot system wide and fastboot flash unlock and unlock_critical. It will install the latest 8.1 developer preview for the Pixel 2 XL for you as well with all the necessary files included. I did not inlcude the lock and lock_critical function as most do not use it.
As the instructions state, please use a usb 2.0 port and and usb-c to usb-a cable that supports data. Also enabling debugging and oem unlock is a must.
It includes a menu driven batch file that is super easy to use.
For those that want to use this same batch file on the pixel 2 itself, please extract the zip from google and then extract the zip within the zip. Next pull the bootloader and radio img file from the root of the zip to the FILES folder included in this program. Then copy all the contents from the zip within the zip to the same FILES folder. It should contain about 22 files in total. We really don't need the android-info.txt file.
I will also be including a batch file with a semi empty FILES folder that does not include any Google related 8.1 files for those that want to download it quicker and copy their own contents to it for flashing. Like Pixel 2 owners that already have the 8.1 preview downloaded.
If anyone needs any help please feel free to ask. This post was rushed so please excuse my grammatical errors.
FOR PIXEL 2 and PIXEL???? ----NO IMG's inlcuded
http://www.mediafire.com/file/eksn04aiaeqvvia/PXEL_2_&_PIXEL_SAUCE_NO-IMGS.zip
FOR PIXEL 2 XL ---- IMG's included
http://www.mediafire.com/file/1wde39mj7ssbxb3/PIXEL_2_XL_SAUCE_V1.zip
dontbeweakvato said:
usb debugging is on and fastboot devices returns correct with the serial number. guess ill reinstall tomorrow. im running command prompt and directing it to platform-tools folder that has adb.exe and fastboot.exe. It doesnt make sense. when in doubt redo EVERYTHING
Click to expand...
Click to collapse
dyingearth said:
I download the latest version of minimum tool from https://developer.android.com/studio/releases/platform-tools.html. That one has stamp date of 05/12/2017, which I'm not sure if it supports Pixel 2 XL yet. adb devices does see the phone.
adb devices
List of devices attached
710KPCA0237899 device
doing fastboot flashing unlock just yields nothing.
fastboot flashing unlock
< waiting for any device >
Click to expand...
Click to collapse
danon.brown said:
Restart the phone and hold Volume down. Then run the fastboot command again if it doesn't work right away.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
OK that works.
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Jpdel said:
I am unable to reload the system. I always get the message “Your device is corrupt. It can’t be trusted and may not work properly.”
Click to expand...
Click to collapse
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
5.1 said:
Hi,
How did you end up in this situation?
Is your bootloader unlocked?
Sébastien.
Click to expand...
Click to collapse
Jpdel said:
Thanks @Sébastien! Yes the bootloader is unlocked.
I was flashing using this site flash-dot-android-dotcom, because of the fact the the phone's software support will end this year.
Then I had a power outage around 90% in because of a storm in our country.
Now I am unable to flash the phone. The Smartboot commands work, but the adb commands doesn't.
I download multiple adb drivers, tried them all, still doesn't work.
Click to expand...
Click to collapse
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
5.1 said:
Hi,
Download latest factory image for taimen if you want Android 11: https://dl.google.com/dl/android/aosp/taimen-rp1a.201005.004-factory-f797c86c.zip
If you prefer latest taimen for Android 10: https://dl.google.com/dl/android/aosp/taimen-qq3a.200805.001-factory-305df20c.zip
Extract the one you want to install and locate Flash-all.bat
If you want to keep your device data's, you'll want to edit the file and remove -w. (Search Google or XDA for further infos).
Detailed flashing guide here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Boot your phone in bootloader: power + volume down.
Plug your USB cord and double click Flash-all.bat. Let it do it's job. Reboot afterward.
You'll keep getting a warning, which is normal, since your bootloader is unlocked. If you want to get rid of it, install the firmware and relock the bootloader. Disable OEM unlocking in developer options. Be careful, it will "again" wipe your datas...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Jpdel said:
Thanks so much for the fast help Sébastien!
When I do this procedure, and I have like around 7 or 8x already, I always end up with this message:
Sending 'vendor_a' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
JarMagic said:
Hello all, I was trying to update to Android 11, from my rooted Pixel 2xl from Android 10. Long story short, I got in a boot loop, so I used Dueces' fix, and now I have the corrupted message when turning it on. I have tried to return to stock, but I get this error message on the last reboot: target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate -1848340176 bytes
error: update package missing system.img
Anyone know how to fix?
Thank you!
Click to expand...
Click to collapse
Hi,
This is not a "shime in if you have a similar issue" thread. You may open your own thread. But well, do you have the proper factory image for taimen? Is your USB cable ok? Is your ADB / Fastboot up to date? In the message above yours i posted a link with the latest version. Try this...
Sébastien.
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
JarMagic said:
I appreciate your help, even though I have posed my question in the wrong place. To answer, yes, I have everything updated, and downloaded, still I keep getting the same error message.
Click to expand...
Click to collapse
Hello,
Do you have acces to recovery? Tried to sideload: https://dl.google.com/dl/android/aosp/taimen-ota-rp1a.201005.004-b5dff51e.zip
Good luck...
Sébastien.
5.1 said:
Hello,
Got your ADB / fastboot up to date? Here is the latest package:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Hopefully it'll work! :good:
Good luck...
Sébastien.
Click to expand...
Click to collapse
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Jpdel said:
Many thanks @Sébastien!
Yes I download the latest DB version. Tried using "Android ADB Interface" and "Android ADB Composite Interface" but nothing appears whenever I do a CMD ADB Devices command
I also tried the sideload option you sent below.
This was the result from the Device Message:
E: Signature Verification Failed
E: Error 2
Click to expand...
Click to collapse
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
5.1 said:
Hi,
If you want to tag an user, tag his/her username. Me > 5.1.
Ex: @5.1
Ok! Well, you can't issue ADB commands while you're in the bootloader. Only fastboot commands work!
A bit of reading here: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Good luck...
Sébastien.
Click to expand...
Click to collapse
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Jpdel said:
Hi Sebastien, thanks again for your reply. I was on tje Recovery > ADB sideload screen when I activated the cmd command above.
Click to expand...
Click to collapse
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
5.1 said:
Hello,
Did you try to format data and reinstall? Since install doesn't go past vendor, it never gets a chance to format data. Maybe it was corrupted during your online adventure...
Did you try to switch slot and try to install factory image from here?
Try to download the zip again and retry once you switched slot:
fastboot --set-active=a or fastboot --set-active=b
Whichever is not active at the moment. Then reboot to bootloader and proceed.
Did you try to reinstall bootloader.img, boot.img, system.img to both slot?
fastboot --slot all flash
Format data and reinstall?
Well, since I don't have the device, it's a bit hard to troubleshoot further...
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Jpdel said:
Super thanks for al your patience @5.1 Sébastien !
I think the issue must be that none of all the ADB drivers work.
I tried those under "ClockworkMod" and "Google, Inc." and all are updated, I also went to get the USB drivers from the Android SDKs.
Somehow I am unable to make ADB work. Whenever I do CMD "ADB Device" to list things... Nothing shows on the list..... I can only show the Decvice if I do "fastboot devices"
I ran the "flash-all.bat"... and I also used the "deuce-flash-all-v5.0.bat", and OTA
It looks like, the unresolved ADB Plugin is the mailn block to get thing going.
Click to expand...
Click to collapse
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
5.1 said:
Hi,
I haven't used clockwork stuff since 10 years, so I bet it's pretty much outdated.... Google Inc? Which ones?
Check this guide: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
And install as per the above guide.
Than once you're done, open a simple cmd window, plug your phone in bootloader and issue:
fastboot devices
No need to be in the same folder as ADB.exe or fastboot, you should see your device.
Then re-run the flash-all.bat from your factory image.
Good luck...
Sébastien.
Click to expand...
Click to collapse
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Jpdel said:
Super thanks for the follow-up solution Sébastien @5.1 !
I tried the above and this is the result"
Sending 'vendor_b' (333468 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
And the ADB command: ADB devices still gives me this result below
C:\Users\delro>adb devices
List of devices attached
It's still blank.
I used the 3 drivers from Google Inc
1. Android ADB Interfacer
2. AndroidComposite ADB Interface
3. Android Bootloader Interface.
All of these drivers still doesn't show anything when I do "ADB Devices" and displays as blank.
The ADB.exe is accessible, it's just not able to see the device, hence might this be a diver incompatibility issue. But I already tried the latest drivers above and none of them work.
Click to expand...
Click to collapse
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
5.1 said:
Hello,
You know ADB is not available in bootloader right? Where do you try to use it?
To be honest, If you tried all I wrote since yesterday, I don't know what else I can advise you. I'm sorry...
Good luck.
Sébastien.
PS: if you quote someone's message, you don't have to tag him/her (@...). It's either one or the other. :good:
Click to expand...
Click to collapse
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Jpdel said:
Thanks so much for your efforts in assisting me (and for all the @ and quotes usage LoL)!
As I have done all the items in the list, the only thing I am looking to have work is Pushing a Flash file using "ADB Push" from PC to phone. But none of my ADB drivers even though they are the latest ones don't work. Sideload didn't work also as this might be the same issue too.
Really am super grateful for your kindness helping me all this time, you are awesome bro!
I will go search to more channel how to rectify this thing.
Take care and hope I can repay you in the future!
Click to expand...
Click to collapse
Update: I finally was able to make the phone work!!!
In a last-ditch effort, I wiped the device, ran the Deuce Script, Reboot, Ran the flash-all.bat, Reboot, went to Recovery Mode > Enable ADB Update > Tried Sideload again of the OTA file, and there you go, I now again have a working device!!!
Thank you Sebastien @5.1 again for all your super kind support and knowledge! Truly am really grateful for your helpfulness!
Surprised that I haven't come across too much regarding this tablet. It's relatively cheap, but has a wonderful screen, with cel data and SD card support. And not a bad resolution. (Not 4K, but ALMOST 2k...) This device seems to be running a SpreadTrun / SPD system under the hood.
Having issues getting it rooted and bootloader unlocked.
First, Rooting via boot.img and Magisk -
I am able to get the boot.img file and have Magisk patch it fine. However, when I go to re-write the boot.img file, fastboot gives me the following:
C:\>fastboot flash boot_a magisk_patched-22100_2U5Ga.img
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 67108864).
Sending 'boot_a' (65536 KB) OKAY [ 2.422s]
Writing 'boot_a' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
SPD's UpgradeFlash won't let me select JUST to flash the boot file - it forces everything to be flashed, which resets the device. Because of that, when I insert the patched boot.img in, it causes the tablet to bootloop.
Trying to unlock bootloader -
Reading through different methods for SPD devices, I'm running into deadends. With both ADB Debug and OEM Unlock enabled, running the following commands don't work:
C:\>fastboot flashing unlock
FAILED (remote: 'unknown cmd.')
C:\>fastboot oem unlock
FAILED (remote: 'Unlock bootloader fail.')
I thought that perhaps the method of flashing the signature (signature.pim file) was needed. However, following that attempt, the command yields:
C:\>fastboot flashing unlock signature.bin
fastboot: usage: unknown 'flashing' command unlock
(Same error is given for 'unlock_critical' and 'unlock_bootloader'.)
Anyone know of an alternate way to flash JUST the boot.img files to an SPD device?
Quick bump!
One interesting thing I have noticed - every time after I run the second command ('oen unlock'), any command sent AFTER that will hang. As if the tablet's expecting something else.
Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
1) You absolutely need the signature file. I got mine by installing an app "spreatrum tools" on the tablet.
2) It only works with a specific version of fastboot.
3) According to my terminal history, the command to unlock could be "fastboot.exe flashing unlock_bootloader signature.bin" or the one posted by OP: "fastboot flashing unlock signature.bin". At least one of these works but I don't remember which since I used them both.
Pretty sure I got both the working version of fastboot (windows version, not linux) and the app here on the forum. Whoever posted those files originally deserves the credits but, again, I don't remember who or where so... Luckily I still have both files on my NAS so I'm attaching them.
Anyway, there, have fun.
So this can also work, nice!
troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Anyway, there, have fun.
Click to expand...
Click to collapse
Thanks so much, already unlocked my BL (through modified adb via Linux) but can't proceed to root it, have you rooted yours?
Nope. My plan was to unlock in order to install a custom recovery as I thought there's a good chance the one for iplay40 might work. Turns out I ended up with a brick so I went back to stock.
My immediate concern was to get rid of system apps but adb shell works well enough for that so...
Actually, I'm more interested in running generic GSI if at all possible, considering alldocube is unlikely to ever update the stock rom.
troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Click to expand...
Click to collapse
Vvtaewoo12 said:
Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools
Click to expand...
Click to collapse
Sorry for the silence guys, had a death in the family that took me away from playing with this tablet for a while.
Glad you both got it - I actually was able to get in touch with someone AT AlldoCube, and they replied saying that the bootloader IS UNLOCKED in the same fashion that the iPlay40 is. (Which isn't too much of a surprise - the back cover of my kPad actually has the iPlay 40 model number on it. Heh.) I followed the instructions in the iPlay 40 thread exactly (including the one command that's run that the output seems to not be used), and it worked.
Like you both, though, I haven't been able to root - Because of the family issues, I haven't tried in a while, but I remember getting as far as trying to flash a modified Magisk boot.img - at which point, the tablet goes into bootloop. I blieve that we need a signed vbmeta file, though I have no idea yet how to generate/flash that.
I have NOT tried the iPlay40 rooting instructions in one post, and I'm admittedly not even sure that I'm using the Spedtrum flashing applications correctly.
Help me unlock bootloader ipay 40
U have trailer video URL/??
U use Ubuntu linux but do not!!
Taoismixi said:
U use Ubuntu linux but do not!!
Click to expand...
Click to collapse
Wrong thread. This is not about the iPlay 40.