Hi,
Long story short I was on Pie (30b) on a US988 (TWRP and Bootloader unlocked) device and it appeared that the MVNO I was on started doing stuff with HD Voice/Advanced calling aka making phone calls no longer worked. I followed the instructions to go back to Oreo 20h and was successfully able to do so (phone works fine, just no recovery/root). I am now trying to get TWRP/recovery back on my phone but failing to do so. My issues:
adb devices works fine
if I try any fastboot commands it always says waiting for device
If I put the phone into fastboot (volume down & usb) fastboot commands work.
in fastboot - fastboot devices list my device
if I run (in fastboot mode on my phone) - Fastboot flash recovery TWRP.img (for the renamed twrp.image file) I get:
Waiting for any device
Sending 'recovery' (33324 KB)
FAILED (Write to device failed (Invalid argument))
fastboot:error Command failed
my phone then says in very small letters at the top press any key to reboot
Sometimes when I try i just get a "FAILED (Write to device failed (Unknown error))
If i just put my phone back into fastboot mode it fails again, but this time with error "FAILED (Write to device failed in SendBuffer() (Too many links))
Any help would be greatly appreciated.
jjppott said:
I am now trying to get TWRP/recovery back on my phone but failing to do so. My issues:
adb devices works fine
if I try any fastboot commands it always says waiting for device
If I put the phone into fastboot (volume down & usb) fastboot commands work.
in fastboot - fastboot devices list my device
if I run (in fastboot mode on my phone) - Fastboot flash recovery TWRP.img (for the renamed twrp.image file) I get:
Waiting for any device
Sending 'recovery' (33324 KB)
FAILED (Write to device failed (Invalid argument))
fastboot:error Command failed
my phone then says in very small letters at the top press any key to reboot
Sometimes when I try i just get a "FAILED (Write to device failed (Unknown error))
If i just put my phone back into fastboot mode it fails again, but this time with error "FAILED (Write to device failed in SendBuffer() (Too many links))
Any help would be greatly appreciated.
Click to expand...
Click to collapse
See WTF Section 7 Troubleshooting Tips. Everything you are describing -- especially "too many links" is an ADB/fastboot communication issue. Don't care if ADB "sees" your device. It's still not talking to it.
There's a dozen Section 7 Troubleshooting Tips. Except for Tip #1, the remaining 11 are to solve this V3O ADB/fastboot communication issue. Go through them one by one.
ChazzMatt said:
See WTF Section 7 Troubleshooting Tips. Everything you are describing -- especially "too many links" is an ADB/fastboot communication issue. Don't care if ADB "sees" your device. It's still not talking to it.
There's a dozen Section 7 Troubleshooting Tips. Except for Tip #1, the remaining 11 are to solve this V3O ADB/fastboot communication issue. Go through them one by one.
Click to expand...
Click to collapse
Thanks Chazz. Ultimately it took trying it on another computer, but I was able to get it TWRP flashed.
jjppott said:
Thanks Chazz. Ultimately it took trying it on another computer, but I was able to get it TWRP flashed.
Click to expand...
Click to collapse
Glad you got it working. Yeah, different computer often does the trick.
Related
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.
Hi,
I've now spent quite a few frustrating hours trying to root my Alcatel 1c (model 5003D, running Android 8.1 Go) and nothing seems to work. A short overview of some of the rabbit holes I've gone down:
Root tools
Started with the obvious: root tools. In short, none that I ran work. There's a couple I haven't tried because the instructions were mostly in Russian and some googling turned up quite a few mentions of them containing malware, but other than that I've pretty much tried all the major ones.
Flashing images via fastboot
Naturally, the next place I turned was the awesome resource that is this forum. This thread gave me plenty of hope, but I was soon flummoxed by my device's fastboot mode for which a bunch of the normal features are either broken or are simply not implemented. Some examples of things that should work (and indeed work on other Alcatel phones, notably, it seems, ones that are not based on Spreadtrum) but didn't:
Code:
~/D/platform-tools > ./fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot oem unlock-go --wipe
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
Code:
~/D/platform-tools > ./fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
(note the spelling error in the error message...)
Code:
~/D/platform-tools > ./fastboot flash recovery ../recovery.img
Sending 'recovery' (28266 KB) OKAY [ 1.582s]
Writing 'recovery' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
That last one was particularly intriguing, as it suggests there is a Flashing Lock Flag that can be unlocked. I tried all of the fastboot commands that seemed relevant but couldn't find any way of setting that flag or even figuring out if it actually exists. I even rand the boot.img through strings to see if I could find something interesting, but didn't turn up anything.
Just to be clear, before doing all this I set the phone to Developer Mode and checked the "OEM unlocking" feature.
Flashing tools
I tried various tools with which it's possible to flash phones. A lot of them use fastboot under the covers which doesn't work (see above). Some of them don't but didn't work on my phone all the same, for various reasons:
SPD flash tool - After yet more Googling I stumbled upon the SPD flash tool,built specifically to flash Spreadtrum-based devices. I downloaded the latest version, installed all of the necessary USB drivers and tried to flash the phone with the stock ROM. No dice. The tool fails to connect to the device via the USB2Serial thing that it uses to communicate. No idea what's going on or why it won't work, and haven't yet mustered the courage to dive into the source code. Of course, if I do get it to work, then I have to figure out how to actually root the device using this tool. I'm guessing it will involve unpacking the ROM (a PAC file), modifying the recovery.img to a TWRP (or similar), repacking it and flashing the result. I've only managed the unpacking so far, no clue as to the other 2 steps. BTW, the SPD flash tool site als has a "factory" and a "research" tool, besides the "upgrade" tool that I tried. Unless I'm missing something, all three seem to be exactly the same (save for the color scheme).
Alcatel Mobile Upgrade S - Installs just fine and then allows you to choose your phone out of a dropdown... that doesn't include my model.
Sugar MTK/QCT - Installed it and the necessary drivers but it can't find my phone, no matter what I try. Also, I keep reading that it needs login credentials (wut?)
Conclusion: argh!
So, nothing so far. Since it's a Spreadtrum phone it has an engineering mode that can be explored with an APK I found in this thread. Nothing in the settings it reveals appears to be of any help though. I also contacted the makers of the AIO Alcatel toolkit to see if they had any ideas, but after I explained the situation one of them concluded "Hmmm. New one on me". Needless to say I also tried searching this forum for more tips, but googling 'site:forum.xda-developers.com "5003D"' returns no hits.
For now, I'm forced to conclude that there is a lot of really awesome tooling out there created by some very talented people, but none of it works on my phone. As of yet the 5003D appears pretty unrootable. If anyone has any tips to help me along or point me in the right direction, I would be very appreciative.
bump
bump
Then type the command to show the device
fastboot -i 0x1bbb devices
Execute the next command which will show device info including bootloader status (e.g. locked).
fastboot -i 0x1bbb oem device-info
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Repeat Step and you should see “Device unlocked: true”
To reboot normally type:
fastboot -i 0x1bbb reboot
Done
This command is to unlock the bootloader on Alcatel device
fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
lotus118 said:
I've tried that a bunch of times in an bunch of different ways, and unfortunately that doesn't work for this particular phone.
Click to expand...
Click to collapse
Rooting your phone's Android does NOT require you fiddle around with its boot-loader. Forget trying to make use of Fastboot.
So how would I go about this without using fastboot?
lotus118 said:
So how would I go about this without using fastboot?
Click to expand...
Click to collapse
1. Open Windows command prompt and input the following comand
Code:
adb devices
2. Start the ADB sideload in your phone's recovery
3. Then input the following command in the Windows command prompt
Code:
adb sideload <filename.Zip>
where <filename.zip> must of course be the real full filepathname of ZIP to get flashed
Hi guys.
New to the forums. I know that there are three threads that already detail what I am asking for. I just don't get it. I try to follow one of them and it says "run Qfil; install QPst." I would be happy to do that, but I just do not know where they are or how to run them.
Then one of the twrp files (whatever that is) has been taken down because of "gross violations." I cannot figure out how to do what the threads say to do.
Can someone please tell me how to root this thing? Step-by-step. With all the downloads. Thanks for your help.
Feel free to close this thread when a response appears.
Can someone please respond to this now that it is in the correct forum?
@wsmyth
May be this detailled guide helps you: https://www.getdroidtips.com/twrp-recovery-unimax-umx-u683cl-root/
Good luck.
Thank you
Thank you very much. I am starting there!
Help
I followed all instructions. I cannot get a twrp to load.
Good instructions, but I had these problems.
1. There is no link to a TWRP file. I use the link shown, and I get "Stock April Patch" from mediafire. None of the files here have TWRP in the filename.
2. I did go to https://rootmygalaxy.net/root-twrp-umx-u673c, a similar site. It did have a link to a TWRP file to use. Your instructions are identical.
So I turn off the device. I turn it on with power and volume-up button. The device goes to Mr. Android lying down with the message "No Command." I look at some other sites, and it tells me to hold power, and press power-up.
This takes me to Android Recovery menu. On Windows cmd line (ADB and Fastboot folder), I type adb reboot bootloader. The Windows screen responds no device/emulators found.
So I select option on the Android to Reboot to Bootloader. The device boots into FASTBOOT MODE with START at the top. I imagine that this is what the above command is intended to do. For fun, I type the same command above in Windows, and I get the same response. But when I type fastboot devices , I get the device serial number (as shown on the START screen) and the word fastboot.
I imagine the device is ready to install TWRP. I use the TWRP file that I downloaded from the other page (remember, yours and their instructions are identical). I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Any help is GREATLY APPRECIATED.
wsmyth said:
I type fastboot flash recovery twrpname.img in Windows, and I get this set of messages:
target reported max download size 26214400
sending 'recovery' (20220 KB)...
OKAY [ 0.650s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.668s
Click to expand...
Click to collapse
IMO you didn't do anything wrong.
To me it seems that OEM/Carrier did not put the typical Fastboot commands into the boot-loader.
BTW:
To test the TWRP recovery without permanently flashing, run the following:
Code:
fastboot devices
fastboot boot twrpname.img
Follow up
Thanks. When I type that code, I get...
downloading 'boot.img'...
OKAY [ 0.640s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.646s
Thanks again
Does it matter that I have no SIM card in this device. on the START screen, I have this...
Press volume key to select, and press power key to select
FASTBOOT MODE (in red)
PRODUCT_NAME - MSM8909
VARIANT - QRD eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - a10b7526
SECURE BOOT - disabled
DEVICE STATE - unlocked (in red)
Is there anyone that can help me on this? Should I take a magnet to the back of the device? Would that help?
UMX U683CL root?
hey guys, when it comes to all of this i would say i am beyond a newb. so if i violate any protocol i plead ignorance and hope that you will bear with me. i have my disable sister who lives with me and i am responsible for who has had a...
forum.xda-developers.com
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
kmkzboi said:
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
Click to expand...
Click to collapse
Use the latest Official TWRP since the one you have now is outdated and do clean install according the guide at POCO F1 Ultimate Collection & Guides. (You need to format data not just wipe) You can find everything you need there.
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
kmkzboi said:
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Check AMD Ryzen Fastboot Fix at the thread I posted above. If you have Intel system just install the Fastboot Drivers which is there (at the thread) and check.
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient