Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
residentorca said:
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
Click to expand...
Click to collapse
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
dary1361 said:
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
Click to expand...
Click to collapse
You can root it and use Magisk to clean things up but no de-Googling. Check out the thread.
Any device that launched with Android 8 or newer is compatible with GSIs. Any device that launched with Android 10 or newer use super.img, which require the extra step of repacking rather than flashing directly. This is what I would recommend if you want ROM support on a brand new device.
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
I have a TWP I ported it from the stock recovery and one from Guamp which is the G9
svoc said:
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
Click to expand...
Click to collapse
Hey I can’t access the file for some reason. Care to reupload? I’m trying to get a port started but I can’t find the device tree anywhere and can’t find a good guide to make one myself.
Hey you go I got a few more errors fixed but don't have time I'm on a new phone right now sorry hope you get it working by the way look at the trwp it will have some device trees you can use to get started
I want to know if there's a custom ROM for this device.
Hold on, there is a custom ROM for this device.
[ROM][13][guamna] AOSP 13 [Monthly Builds]
AOSP 13 This is a moto-common project release under the codename guamna /* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some...
forum.xda-developers.com
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
WolfHunter16 said:
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Click to expand...
Click to collapse
Now, if I were to download a rom from the site, would it be A only? B? A/B?
They are all A/B, just check the filenames. If you read the release notes, they state there is no A-only build yet.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
I haven't been able to get my sim card to be detected, is this a known issue or am I missing something?
Download your stock rom and flash radio.img to restore cell signal
svoc said:
Download your stock rom and flash radio.img to restore cell signal
Click to expand...
Click to collapse
Thanks for the tip! I knew I was missing a detail.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
It works! This has been kicking my butt left right and sideways for weeks but this worked. Thanks!
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
stoag said:
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
Click to expand...
Click to collapse
Make sure you have the current version of fastboot, AND that it's the one that you're using. Ran into that problem mysself, updated my PATH incorrectly and had it pointing to the wrong fastboot.exe.
Related
I'm sadly unable to fastboot my Moto G on an alternative image, without the need to flash it to the device, though it seems to me that the procedure bellow was woking a few months ago:
Code:
# 1: reboot in bootloader mode
adb reboot-bootloader
# wait the device for bootloader screen, where I can see "Device is UNLOCKED. Status Code: 3", and then
fastboot boot boot.img
Today, the above steps produce what looks like a correct output:
Code:
downloading 'boot.img'...
OKAY [ 0.490s]
booting...
OKAY [ 0.243s]
finished. total time: 0.734s
, then the device shutdowns, restarts, but gets stucked at the initial splashscreen, even before the "Unlocked device" warning screen: I have to press the power button for 7-10 seconds to trigger a hard reboot, but then using the device boot image.
So, why does this fastboot fail ? I suspect a few kind of causes:
The fastboot parameter image file is anapropriate: I've downloaded the firmware from sbf.droid-developers.org, and extracted boot.img from the xml.zip file; and as far as I can remember, this boot.img contains both the kernel and intiial ramdisk, like the one I've successfully used before
I use the wrong tool: it seems that the SDK provided fastboot util may misbehave with a Motorola device/firmware, but I've also tried the mfastboot-v2.zip recommended variant, with no more luck
The procedure I've used a few months ago does no longer apply, consequently to some SDK update (SDK Tools 23.0.2) or device firmware update (KitKat 4.4.4)
BTW, there's another thing I don't understand at this point: when I have to hard reboot the device after the fastboot failure, an "Application optimization" step occurs, involving at most 44 applications (when I wait long time before the hard reboot), and less applications when I don't wait enough.
Can someone tell me what's happening ?
Thank you for any idea or pointer.
Hello
My xperia Tablet Z 32GB WiFi has cm 12 and cm recovery.
I would like to upgrade to Lineage OS but install TWRP Recovery first.
The boot loader is open but every time I want to flash the img via fastboot I get the error message:
sending 'recovery' (11764 KB) ...
OK [0.378s]
writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. total time: 0.387s
Per app it is also not possible because every time I download an app (to flash the recovery), CM12 crashing (the Tabled freezd)...
In the settings I activated ROOT via ADB + APPs and CM Recovery Update too ....
What can I have forgotten you have an idea ??
Please help
Thank you
--------------------------------------------------------------------------
I found a way !
1. Donwload the TWRP for your device. And copy it next to ADB.exe and Fastboot.exe.
2. Enable in settings: Root for APP+ADB
3. open adb in a cmd
4. Chef if your decice is shown up with: "adb devices"
4a. maybe you must acept it per OK Button on your device
5. boot in Bottloader: " adb reboot bootloader"
6. check if fastboot show your device: "fastboot device"
7. now : "fastboot flash boot ******TWRP.IMG NAME***** "
8. w8 a short time unplugg the usb cable.
9. Press the PowerButton.
Grauer_Star said:
Hello
My xperia Tablet Z 32GB WiFi has cm 12 and cm recovery.
I would like to upgrade to Lineage OS but install TWRP Recovery first.
The boot loader is open but every time I want to flash the img via fastboot I get the error message:
sending 'recovery' (11764 KB) ...
OK [0.378s]
writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. total time: 0.387s
Per app it is also not possible because every time I download an app (to flash the recovery), CM12 crashing (the Tabled freezd)...
In the settings I activated ROOT via ADB + APPs and CM Recovery Update too ....
What can I have forgotten you have an idea ??
Please help
Thank you
--------------------------------------------------------------------------
I found a way !
1. Donwload the TWRP for your device. And copy it next to ADB.exe and Fastboot.exe.
2. Enable in settings: Root for APP+ADB
3. open adb in a cmd
4. Chef if your decice is shown up with: "adb devices"
4a. maybe you must acept it per OK Button on your device
5. boot in Bottloader: " adb reboot bootloader"
6. check if fastboot show your device: "fastboot device"
7. now : "fastboot flash boot ******TWRP.IMG NAME***** "
8. w8 a short time unplugg the usb cable.
9. Press the PowerButton.
Click to expand...
Click to collapse
The first attempt was unsuccessful, because Sony devices until recent, don't have recovery partition.
So trying "fastboot flash recovery TWRP.IMG NAME" will result in error, mentioned by you.
You can use Rashr to flash recovery from working android. No need to mess with adb/fastboot.
I had no root (stock 5.1.1.) but could flash twrp with flashtool
lkjsoiuew said:
I had no root (stock 5.1.1.) but could flash twrp with flashtool
Click to expand...
Click to collapse
With Lineage OS 14.1 the official twrp App works great. I think the cm12 has some bugs...
but now i am Happy.
THX 4 your help
Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
First and foremost, please install ZenFone 3 Deluxe Drivers via Device Manager (Download drivers on ASUS Support Website)
1)Download the Factory RAW ROM here:
ZS570KL:
ZS570KL Pro:
2) Download ASUS Flash Tool here:
3) Flash the firmware via ASUS Flash Tool by entering FASTBOOT MODE (Power Button + Volume Up) & DO NOT WIPE DATA!
Note: If you flash RAW firmware via ASUS Flash Tool and received an error (FRP request error), just IGNORE the error.
4) Enter FASTBOOT mode (Power Off + Volume Up)
UNLOCKING
5)
• Open Command Prompt/Windows Powershell
• Now copy and paste this: fastboot devices
• If it shows serial number of your ZenFone 3 Deluxe, you are good to go
• Now copy and paste this: fastboot oem unlock-go
• After that, re-enter FASTBOOT mode and paste this: fastboot oem device-info
Congratulations, your device has been unlocked unofficially. (You can see the "Device State: unlocked" on Command Prompt/Windows Powershell)
RELOCKING
5)
• Open Command Prompt/Windows Powershell
• Now copy and paste this: fastboot devices
• If it shows serial number of your ZenFone 3 Deluxe, you are good to go
• Now copy and paste this: fastboot flashing lock
• After that, re-enter FASTBOOT mode and paste this: fastboot oem device-info
Congratulations, your device has been locked (You can see the "Device State: locked" on Command Prompt/Windows Powershell)
P.S: If you unlocked officially and you want to relock your bootloader, OTA does not work because your Serial Number has been recorded by ASUS.
6) After that, download the stock RAW ROM here and flash it via ASUS Flash Tool (FASTBOOT Mode) (Turn on WIPE DATA):
ZS570KL:
ZS570KL Pro:
If anything, contact me via Telegram
Note: If you flash RAW firmware via ASUS Flash Tool and received an error (FRP request error), just IGNORE the error.
Note: If it asks for PIN after booting up, just wipe data & cache via Recovery Mode (Power Button + Volume Down).
So if i unlocked officially and relock with this method i can't get ota updates anyway?
Ryder. said:
So if i unlocked officially and relock with this method i can't get ota updates anyway?
Click to expand...
Click to collapse
You won't get any OTA updates.
This is what I've been looking for for ages. Thank you Saktis_STi !
I have zs570kl. I donload all aplications.
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.005s
JaskoPtaszek said:
I have zs570kl. I donload all aplications.
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Click to expand...
Click to collapse
Did you flash Factory RAW at the 1st place?
Will relock work for zs550kl ?
Chiko-HH said:
Will relock work for zs550kl ?
Click to expand...
Click to collapse
No
Thanks for the tutorial!! I've got a question: Where can I find the firmware's raw version? (Other's than the one you shared)
sebastiandg7 said:
Thanks for the tutorial!! I've got a question: Where can I find the firmware's raw version? (Other's than the one you shared)
Click to expand...
Click to collapse
Well, I got it from my friend of mine.
Maybe you can try downloading from here:
www.beritahuaja.com
.
Quote:
Originally Posted by JaskoPtaszek
I have zs570kl. I donload all aplications.
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Did you flash Factory RAW at the 1st place?
Hello. You're right I did not do exactly point 1. Thanks for the quote. I have unlocked zs570kl.
Thank you very much.
Saktis_STi said:
Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
First and foremost, please install ZenFone 3 Deluxe Drivers via Device Manager (Download drivers on ASUS Support Website)
1)Download the Factory RAW ROM here:
ZS570KL: Link
ZS570KL Pro: Link
2) Download ASUS Flash Tool here: Link
3) Flash the firmware via ASUS Flash Tool by entering FASTBOOT MODE (Power Button + Volume Up) & DO NOT WIPE DATA!
Note: If you flash RAW firmware via ASUS Flash Tool and received an error (FRP request error), just IGNORE the error.
4) Enter FASTBOOT mode (Power Off + Volume Up)
UNLOCKING
5)
• Open Command Prompt/Windows Powershell
• Now copy and paste this: fastboot devices
• If it shows serial number of your ZenFone 3 Deluxe, you are good to go
• Now copy and paste this: fastboot oem unlock-go
• After that, re-enter FASTBOOT mode and paste this: fastboot oem device-info
Congratulations, your device has been unlocked unofficially. (You can see the "Device State: unlocked" on Command Prompt/Windows Powershell)
RELOCKING
5)
• Open Command Prompt/Windows Powershell
• Now copy and paste this: fastboot devices
• If it shows serial number of your ZenFone 3 Deluxe, you are good to go
• Now copy and paste this: fastboot flashing lock
Click to expand...
Click to collapse
Everything work, but in fastboot flashing lock do not work. Help me I think this command is not right
tecnicopascoal said:
Everything work, but in fastboot flashing lock do not work. Help me I think this command is not right
Click to expand...
Click to collapse
Try reinstalling drivers.
Please follow my instructions carefully.
Saktis_STi said:
Try reinstalling drivers.
Please follow my instructions carefully.
Click to expand...
Click to collapse
How I "Reinstall the drivers"?
I will Flash downgrade stock files like modem, and reinstall UL-STOCK-UPDATE in stock_recovery to be reinstalled?
@Saktis_STi you have the best asus model snapdragons, why we have so poor development to custom rom in this magnific devices?
Per the forum rules, posting pay-per-click links on XDA is not allowed:
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links, all forms of crypto-mining and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Click to expand...
Click to collapse
LINKS REMOVED AND THREAD CLOSED
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
Hello.
I requested help on wrong forum, first person that responded redirected me here.
Here's the copy-pasted contents of that post.
I have a Motorola. I typically leave my cellphone attached to my computer with USB so it can charge, slowly but surely.
When I wanted to get on my way I noticed my phone wouldn't start which I found interesting.
I left it on a charger for some time and when I held the power button to power up, I noticed it got stuck at boot.
What it typically does is open boot screen with Motorola logo, vibrate, start an animation and after mid-boot say "halo Moto" and then leave me at home screen.
But this time, it just get stuck on a boot screen. It shows the boot screen with Motorola logo, vibrates and then does nothing (until battery dies, I left it for an hour?)
I pressed the volume down and power button to enable debugging.
I get a "FastBoot AP Flash Mode" menu.
The options are:
Start (which puts me back into stuck boot)
Restart Bootloader (which restarts the FastBoot)
Recovery Mode (which gives me this: "No Command" with an Android icon, does nothing more]
Power Off (which powers off the phone)
Bootloader Logs (which changes some text to: "Fastboot Reason: Reboot mode set to FastBoot" or "Volume button down")
Switch Tools Mode (which toggles text between Tools Mode Config: DISABLED and ENABLED, no idea of other effects)
BARCODES (which probably shows scannable code so that professionals needn't type the ID)
I wanted to send it back to the seller, but they claim that they take no responsibility for loss of information, all my data is stuck on 128GB on the internal memory.
I would like to go to service for data recovery, but I due to COVID-19 everything's closed.
What could I potentially do to restore my phone? And if I can't, I can send it back, but how do I backup my data?
It's Motorola One Zoom.
Click to expand...
Click to collapse
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
ilia3367 said:
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
Click to expand...
Click to collapse
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
yeetusAAA said:
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
Click to expand...
Click to collapse
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The situation changed slightly since I came back from work.
Previously device appeared as unknown device.
With name "fastboot parker S", I have it in search history.
After rebooting (and installing 50 drivers) my device appears as "Motorola ADB Interface", however execution of commands don't end successfully.
Code:
X:\Applications\MinimalADBFB>fastboot -help
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw <bootable-partition> <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader|emergency] Reboot device [into bootloader or emergency mode].
reboot-bootloader Reboot device into bootloader.
oem <parameter1> ... <parameterN> Executes oem specific command.
stage <infile> Sends contents of <infile> to stage for
the next command. Supported only on
Android Things devices.
get_staged <outfile> Receives data to <outfile> staged by the
last command. Supported only on Android
Things devices.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the
form <protocol>:<hostname>[:port] where
<protocol> is either tcp or udp.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all slots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--skip-reboot Will not reboot the device when
performing commands that normally
trigger a reboot.
--disable-verity Set the disable-verity flag in the
the vbmeta image being flashed.
--disable-verification Set the disable-verification flag in the vbmeta image being flashed.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
X:\Applications\MinimalADBFB>fastboot -getvar current-slot
fastboot: unknown option -- g
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot reboot bootloader
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.016s
X:\Applications\MinimalADBFB>
About all those "remote" failures, the commands do appear in "Bootloader Logs", and the text is something like:
"cmd: getvar:slot-count" and "cmd: set_active:a". As someone with Android unrelated programming background I see nothing that would indicate an error on the phone.
Manually rebooting to fastboot doesn't change anything, rebooting the device in general doesn't solve the issue.
After rebooting I redid my steps:
Code:
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.004s
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (status read failed (Too many links))
finished. total time: 0.005s
X:\Applications\MinimalADBFB>
Too many links? Corrupted file system?
Try to update the adb & fastboot drivers.
Phone is downloading into Recovery?
Ejects from the attached archive adb folder to the root of the C:\ drive.
I didn't have a problem with these drivers.
ilia3367 said:
Try to update the adb & fastboot drivers.
Click to expand...
Click to collapse
How? There doesn't seem to be official link to fastboot, every next website I visited has different edition. Half of links are dead, others have viruses. Even manufacturers of phones seem to have different drivers.
Phone is downloading into Recovery?
Click to expand...
Click to collapse
No, the phone is stuck at boot. It doesn't automatically fallback into Recovery, nothing changed since last time I entered "Recovery Mode".
Ejects from the attached archive adb folder to the root of the C:\ drive.
Click to expand...
Click to collapse
I placed the files in plain C:\, executing your commands invoked following response:
Code:
C:\>fastboot getvar current-slot
< waiting for any device >
current-slot: a
Finished. Total time: 0.001s
C:\>fastboot --set-active=a
fastboot: error: Device does not support slots
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
ilia3367 said:
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
Click to expand...
Click to collapse
Device Manager calls my phone "Motorola ADB Interface".
fastboot devices says:
Code:
C:\>fastboot devices
ZY226KZGT5 fastboot
"Your phone is in the correct boot Slot A, where you should install the firmware."
Is there a way to recover data first?
"Is the bootloader locked?"
I have no idea.
Screen mentions:
"oem_locked"
"AP Fastboot Flash Mode (Secure)"
Code:
C:\>fastboot flashing get_unlock_ability
(bootloader) use "oem get_unlock_data" and web portal
(bootloader) http://motorola.com/unlockbootloader
OKAY [ 0.005s]
Finished. Total time: 0.008s
"Is there a way to recover data first?" - Are you sure there's something left? Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
ilia3367 said:
"Is there a way to recover data first?" - Are you sure there's something left?
Click to expand...
Click to collapse
I had 120GB of data on it, before it crapped out on me.
Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
Click to expand...
Click to collapse
Which file? Tehre's no bat file in the zip you provided.
yeetusAAA said:
I had 120GB of data on it, before it crapped out on me.
Which file? Tehre's no bat file in the zip you provided.
Click to expand...
Click to collapse
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
yeetusAAA said:
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Code:
C:\>fastboot getvar all
getvar:all FAILED (Status read failed (Too many links))
Finished. Total time: 0.005s
yeetusAAA said:
What does getvar all say?
Click to expand...
Click to collapse
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
sd_shadow said:
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I see. Thanks.
bricked phone
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
death1426 said:
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
Click to expand...
Click to collapse
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
does not show up in device manager
sd_shadow said:
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
no unfortunately it does not already tried placing it in edl mode with a cable but no to avail also installed Qualcomm drivers just to be sure uncertain what i can do at this point