Related
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
Your computer must not be properly communicating with your device, Have you tried ANY other fastboot commands other then what you mentioned?
Can you provide a screenshot of your fastboot commands failing? Perhaps something else is going on other then what you've provided. You never know.
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
tywinlannister said:
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
Click to expand...
Click to collapse
Thanks for the reply. I picked up a new cable today just to be absolutely sure that wasn't the cause of my problems. I've tried several already, but most of those were dollar store cables and iffy at best. No luck though, even with a brand new semi-good quality cable (Duracell) it still doesn't work.
I followed all the above steps. First I made sure the correct OEM drivers were installed. Device manager shows "Android phone: Coolpad Android ADB Interface" when I plug the phone in. I'm not 100% sure that this is the correct driver for my phone, though it is a Coolpad, and I know there is some universality between drivers. I've used both ADB and fastboot commands on my Kindle fire many times with only the generic Google ADB / fastboot driver and never had a problem. Also, the Coolpad driver I found was on a Chinese file sharing website (Baidu) listed under the Coolpad section and was just titled phone driver.rar so i'm guessing it's universal for Coolpads. That, and the fact that the phone does respond to some commands makes me think that the driver isn't the issue either. Next, I followed the posted link and downloaded the latest ADB and fastboot files and installed them. I then moved my recovery.img and my 801es.img (nandroid backup) to the ADB / fastboot folder and opened an admin command window. Here are the results:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
1edf2f7a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Program Files (x86)\Minimal ADB and Fastboot>
These would seem to indicate that fastboot is working properly, but upon trying your suggestions I don't get past the second command.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
Then nothing. I've waited 10 minutes and no change. I get similar results trying to erase recovery, boot the recovery.img, and flash the recovery.img.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10240 KB)...
All these net a similar response. Waiting 10 to 15 minutes after each command and still no activity.
I'm stumped.
Just a minor update. I got a second-hand Kindle fire for my son. I thought it was one of the 50 dollar ones they're selling now since it was in plastic behind glass in a locked case and all it said was Kindle fire 7 inch. Dated 1-3-17. For 20 bucks I thought what the heck. Well, upon getting it home and tinkering with it, I quickly discovered it was a Kindle fire 2nd gen from 2012. Still not bad for 20 bucks as the thing was pristine, but I hated the UI. After a little bit of digging, I discovered that you could easily install TWRP, Gapps, and Cyanogenmod 11 on it. All info I found here (surprise surprise, I love this site.) Now that's done and my son loves his tablet. It's just like a proper Android tab.
Anyway, anyone who's tinkered with older Kindle devices knows about fastboot cables (and yes, I did need one, dang bootloops!). I thought I would try the fastboot cable on the stubborn Coolpad. Still no go. So at this point, either the images I have are invalid and I can't get new ones (weeks of Google searches have turned up zip as far as a stock rom for this phone), or the phone is locking me out due to some non-standard security feature. I'm thinking the second. I can understand if the images I have are bad, but that shouldn't affect things like querying the lock status of the bootloader, or trying to erase the boot partition and not getting a response.
I'm out of ideas. If anyone knows anything about this, specifically if this is unique to Coolpads, please let me know. Otherwise, the phone is going to end up in a drawer, probably forever. Thanks.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Iamst.ralph said:
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Click to expand...
Click to collapse
The phone is a Yulong Coolpad model 801 ES. I was running stock 4.1.2 JB ROM rooted with Kingroot. Developer options were unlocked and allow ADB debugging was checked. ADB and Fastboot drivers were installed and working properly as I was able to make a backup of my recovery partition and a "Nandroid" image. Note, the Nandroid image wasn't made using a custom recovery, it was made using DFS Evolution phone tools. It said Nandroid backup, and it did generate a file named 801es.img that's roughly 248 mb. I can't tell what partition it is since it has a non-standard header. Every image kitchen I've tried to use tells me bootmagic is missing when it tries to unpack.
The phone was working fine until I flashed an incompatible TWRP recovery. Now I'm stuck in a bootloop. I can get into fastboot mode, but every command I send other than fastboot devices and fastboot reboot ( like fastboot boot recovery.img, fastboot flash recovery recovery.img, fastboot erase recovery, fastboot flashing unlock, ...) just hang. I've waited for over an hour on some and they still didn't complete. I've tried every USB port on my PC, 6 different cables, three different OS's (Win 8, WIn 8.1, and Ubuntu), and a second PC (my laptop) to try and eliminate all possible problems. All that and still no luck. This phone just will not respond to fastboot commands like it should and I have no idea why.
Hopefully that answers all your questions. Maybe you have some ideas.
Your phone is obviously a MTK phone hence fastboot commands get stuck. Search for the firmware of your phone on Google and download it, download Sp flashtool. When you're done downloading, post here
I have similar issues with a Coolpad Defiant 3632A. All commands except for [fastboot devices] and [fastboot getvar] everything else returns - "FAILED (remote: unknown command)".
My fastboot has a Secure Phone text in white at the bottom left of the screen when im in the bootloader. Not long back this was not the case and i'm not sure what is causing it.
GETVAR Results
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5_emmccid_secureboot
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4082000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x10dffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) serialno:1f59cc3d
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.100s
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
Dear all,
I have made numerous attempts to unlock the bootloader of my Wiko U Feel Prime, but to no avail.
(My goal is to flash TWRP, root with Magisk and install LineageOS.)
USB debugging and OEM unlocking are enabled in the developer settings.
ADB recognises the device. When I execute adb reboot bootloader, the device reboots, and doesn't get past the "powered by Android" screen – but is nonetheless found by fastboot when I run fastboot devices. Seems like the USB drivers are functioning properly, correct?
Now, when I run fastboot oem unlock, I get the following response:
Code:
...
FAILED (remote: unknown command)
finished. total time: -0.000s
The command fastboot flashing unlock gives the same result.
Moreover, fastboot getvar all displays no unlocked variable. The command fastboot getvar unlocked yields
Code:
unlocked:
By the way, this phone was shipped SIM unlocked.
I've spent hours looking around the web for solutions, but everyone (including guides specifically written for Wiko U Feel Prime) simply says "unlock the bootloader" as if it's a trivial task. And I've run out of ideas. Could anyone help?
Thank you very much.
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
zhekozhekov said:
Hi. Has anyone managed to root Ulefone Armor X5?
The phone is based on MediaTek Helio P23 MT6763, 64-bit Processor.
Baseband: MOLY.LR12A.R2.MP.V91.7.P4
Kernel: 4.4.146#2 wed Sep 25 16:10:16 CST 2019
Build Nr: Armor_X5_MH1_EEA_V01
I have installed the drivers uploaded onto Mega by the Ulefone company here:
https://mega.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!03YnGSYa
I have created the patched boot.img by Magisk Manager 7.5.0.
Enabled the OEM Unlock and USB Debugging thru the Developer options.
Thru ADB, successfully reboots to fastboot by "adb reboot bootloader". The PC recognizes it as typing "adb devices" gives the serial number.
And so far that's all.
Typing "fastboot oem unlock" or "fastboot flashing unlock" gives no result on the phone screen. The ADB says: waiting for device.
I am following most of the steps explained here:
https://forum.xda-developers.com/android/general/root-ulefone-armor-6-tutorial-t3948089
Any advice on what I am doing wrong?
Is it possible to brick it or bootloop by flashing the patched boot.img directly?
Many thanks.
Click to expand...
Click to collapse
If your PC Is not seeing device in fastboot. It may be you need to update your fastboot.exe
In my case there was two possibilities. In Windows 10 I gave myself higher
admin rights clicking right in the folder of my fastboot programm. I tried a little bit, but there is no big thing to get a positive answer writing (before of course I switch on under developer settings usb debugging and gave answer in phone screen) :
fastboot devices
Better and easier is it on Linux, because writing sudo in front of fastboot and ready is it:
sudo fastboot devices
sudo fastboot flashing unlock
or
sudo fastboot flashing unlock_critical
:good:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I am still waiting for someone to give detailed instructions of rooting it.
Did you flash and use TWRP or flashed the patched boot.img straight? Cheers.
waldem88 said:
Hi,
Recently rooted mine Armor X5 (with some pains) so remember mistakes I did and you might be doing.
First, confirm that fastboot sees your device ("fastboot devices") . If you get "waiting for device" then
try different ADB & fastboot installers (e.g. 15 seconds ADB Installer 1.4.3 or ADB installer v1.3
Good luck
Click to expand...
Click to collapse
just got my phone bro. would you be kind in sharing the method you used to root your armor x5.. thanks.
I have the some problem.
In other device, fastboot are work alright.
I try to edit (repack) Zip Rom with replace boot_verified.img with img from magisk, and instal with SP multi port from official site, its error' on boot.img....
Any idea to verify signature boot_verified.img from magisk.???
Sorry for my bad English..
A Solution
Hi, popping in to say I had the same exact problem. After you enter fastboot through the command "adb reboot bootloader", go into device manager and look for Armor X5, right-click update drivers, and then select search for drivers online. It should automatically update with the adb driver.
( I also found the code at the end of the romprovider tutorial titled "How to create a prerooted patched boot.img with magisk" useful, although fair warning it did wipe my device clean )
My input
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Hi, on my side I am stuck in the same way because I found several versions:
- mt6762
- mt6763
i feel all twrp and magisk are for 6763.
Can you confirm which version you have?
Sorry but I'm stuck months too and I really need to root my phone ;-(
Pachacouti said:
I'll say this: There is 2, yes, two fastboot 'modes' in this fone, and is provable thus: adb reboot bootloader - shows a black screen with the tiniest of writing, and...
adb reboot recovery - boots us into (origional) recovery, where we can choose to boot into fastboot, however, when booting into this mode, at the top of the screen we see fastbootd - note the 'd' at the end? fastboot commands work, but dont stick, appear to write succesfully.
So when people say they cant use fastboot commands, this is why!
I got as far as:
adb reboot fastboot
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock <-success - bootloader unlocked, and can be relocked.
fastboot -i 0x0E8D flash boot boot.img <- magisk_patched.img (did not show anything to say it worked)
fastboot -i 0x0E8D flash recovery twrp.img <- twrp (tried all available twrp versions, none worked so far, reckon we need a twrp built for this particular fone)
After reflashing the boot, fone bootlooped.
After flashing recovery, fone bootlooped.
So hopefully someone will chip in, because it's not normal that we can apparently flash anything with bootloader unlocked, but now we cant.. I'll point out my fone is an android 10, probably the reason no other twrp's will work, most likely being made on android 9
I have 30 years programming experience, just getting old and cranky...
Seems my thread starter was moved to god knows where, (bang go donations until I see something worth donating to lol), I AM a developer, who buys toys just to hack them!! So may threads in dev section have ZERO useable information, 'scuse the coment :/
Click to expand...
Click to collapse
error for me too
you are win?
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Pachacouti said:
Using win 7 x64,
Phone is on Android 10_Q
Mtk 6765
This is an aarm64, meaning a 64-bit fone, no instructions available so far work, because they are all for android 9, lot's of 'Q' root's, but not for what they call 'A' only boot, which is not the same as A/B partitioning.
All I'm reading now is the same tut's on hundreds of websites giving the same old information... and the fact root is gone. From what I read, My fone is so up to date that I'm where most will be shortly, and with root devs too busy keeping old hat alive... Figure it out: TWRP is actually dead, now. This is why they no longer accept requests here. Twrp cannot be loaded in a dynamic partition setup, (so far) it wont even fastboot boot twrp.img, not happening with ANY twrp. So forget TWRP. Twrp is old hat to my fone.
Magisk, haha, not one version works for true 64bit, (Not implemented yet), and prob never will be, say tata magisk and say tata su, cause we cant write to the deduped ext4 system, root is kinda pointless now, cause if we cant read/write... Overlayfs is the fix I read, in about 5 years...
So its writing custom kernels for the A only tat's the way I read...
Wake up, it's time to experience the cave in to google domination... their AI patc things much quicker than waiting on devs working on what used to work...
Fingers crossed they get round to the new updates instead of concentrating on what works for ONE fone...
Click to expand...
Click to collapse
Hello, I have the same phone, any news about rooting etc.. ?
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
bjlabuk said:
Hi,
I got my Armor X5 P22 Mediatek MT6762, Android 10 phone a couple of days ago to replace an ageing Moto G5S. I have unlocked the bootloader on several previous Android phones, but found doing so on this X5 a bit harder.
Assuming you have enabled 'Developer Options' etc on the phone and installed the Mediatek drivers and 'Minimal ADB and Fastboot' on your PC/laptop, I would suggest that once you are in Fastboot mode and have confirmed that Fastboot recognises your device with the command "Fastboot devices", that you next enter the command
Fastboot /?
This will bring up all the Fastboot commands and options installed on your phone. I then used
Fastboot flashing get_unlock_ability which returned an 8 digit number:-
D:\Minimal ADB and Fastboot>fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.015s]
finished. total time: 0.015s
I have no idea what the 8 digit number means, as I thought it would return '1' or '0' .
However I then did the following:
D:\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: GetVar Variable Not found)
finished. total time: 6.704s
D:\Minimal ADB and Fastboot>fastboot reboot
(bootloader) Start unlock flow
rebooting...
On rebooting the phone, a warning appeared on the Home Screen for 5 seconds stating that the bootloader was unlocked, the phone could not be trusted and my warranty was void. The phone was factory reset.
On re-enabling 'Developer Options' and checking the 'OEM unlocking' option the phone confirms that 'Bootloader is already unlocked'
Don't know whether this helps anyone else struggling to unlock their phone.
The 'fastboot flashing unlock' command might be unnecesary.
regards
Click to expand...
Click to collapse
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Deleted link to unofficial twrp site
maxxvd said:
Hello, could you flash twrp on this phone? I have the same one (mt6762, Android 10) and couldnt find a working twrp Port...
Click to expand...
Click to collapse
You dont have same fone, you have mt6762, I have mt6765
This worked for me (am using a mac so my terminal lingo may be different)
Device: Ulefone X5 2019
Chipset MT6763
Processor: arm64-v8a, A-only system partition
Reset device
Enable developer options, USB debugging, and OEM unlock, then in terminal, do:
adb device
adb reboot bootloader
fastboot flashing unlock_critical
Device is now unlocked and reboots (unlocked warning now appears on reboot screen)
——
Then I installed TWRP & Magisk:
Re-enable developer options, USB debugging, and OEM unlock
To flash the TWRP recovery.img: Copy the TWRP recovery.img into the platform-tools folder, and from that folder, do:
adb reboot bootloader
fastboot flash recovery recovery.img
Then once finished, hold down the power and volume up buttons until it shuts down and restarts (restarts in TWRP recovery)
——
• Download the latest Magisk installer file and put it in the ADB (platform-tools) tools folder (or in your device storage)
• Inside TWRP, go to Advanced > ADB Sideload, then do adb sideload Magisk.zip (replace Magisk.zip with the Magisk zip filename )
Swipe the slider to install Magisk
Tap Reboot System
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