on 31 st december 2020 i kept my (rooted) phone for charging at night and went to sleep when i woke up in the morning i saw my phone was stuck in bootloader
tried RSD lite but phone is not visible in devices option
tried lmsa nothing happening
error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jugalparghi said:
on 31 st december 2020 i kept my (rooted) phone for charging at night and went to sleep when i woke up in the morning i saw my phone was stuck in bootloader
tried RSD lite but phone is not visible in devices option
tried lmsa nothing happening
error:
View attachment 5176509
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
this is what getvar say
jugalparghi said:
this is what getvar say
View attachment 5177145
Click to expand...
Click to collapse
You can try flashing with fastboot.exe but I suspect that flashing will fail.
If so you're only option maybe is force emergency download mode (edl)
Code:
fastboor oem blackflash
And use a blankflash to recover device.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
getting this error
jugalparghi said:
on 31 st december 2020 i kept my (rooted) phone for charging at night and went to sleep when i woke up in the morning i saw my phone was stuck in bootloader
tried RSD lite but phone is not visible in devices option
tried lmsa nothing happening
Click to expand...
Click to collapse
Don't waste your time, simply re-flash phone's Stock ROM
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.zip>
device not showing in adb devices command
device only visible in fastboot devices command
Have you USB-debugging enabled in device's Android Settings -> Developer options and rebooted device afterwards?
no i Recently disable usb debugging because i was not able to use wifi usb tethering
what should i do now ?
IDK
can anyone solve this problem on this entire forum
jwoegerbauer said:
Don't waste your time, simply re-flash phone's Stock ROM
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM.zip>
Click to expand...
Click to collapse
Adb sideload doesn't work when device is in fastboot mode
jugalparghi said:
getting this error
View attachment 5177393
Click to expand...
Click to collapse
You tried flashing firmware with fastboot.exe
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
no fastboot.exe is not opening on my system
jugalparghi said:
no fastboot.exe is not opening on my system
Click to expand...
Click to collapse
Fastboot.exe is a CLI, hence nothing gets opened. You run Fastboot commands either in Windows PowerShell or in Windows Command prompt.
To apply any Fastboot commands you typically run
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot <subcommand>
adb reboot
i thought i need to specifically open fastboot.exe but i have alread done in windows powershell and cmd but no response
adb devices show's no device
jugalparghi said:
adb devices show's no device
Click to expand...
Click to collapse
My bad: Haven't kept in mind that ADB got disabled by you.
The
Code:
fastboot reboot
command will help you to boot your device normally to OS. On entering the reboot command you’ll be booting the system partition of your device.
already done fastboot reboot device reboot's into fatboot mode again
Have neither experienced it, nor heard or read it, that
Code:
fastboot devices
fastboot reboot
doesn't work.
code:
1 fastboot devices
2 fastboot reboot
1 code works fine shows device
2 code also works fine but my device dosen't boot normally into os it takes me back to my first error image as shown in the thread
Related
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
bhushan46 said:
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
Click to expand...
Click to collapse
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Ghand0ur said:
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Click to expand...
Click to collapse
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
see that image.
bhushan46 said:
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.View attachment 3256147
see that image.
Click to expand...
Click to collapse
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Lloir said:
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Click to expand...
Click to collapse
Hahaahahhaa Perfect description.
@OP:
ADB and Fastboot are two different things.
You DO NOT NEED ADB.
DO NOT WRITE ADB
Write "fastboot devices" directly, and your device will show up.
And please do read all the links lloir provided.
Thank you so much guys.. @Lloir nd @Ghandour
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Texasblazed said:
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Click to expand...
Click to collapse
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
jwoegerbauer said:
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
Click to expand...
Click to collapse
wrong, its a qualcomm
So can this device be rooted or not? Correct replies only would be great.
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
like this?
krayzieiyian23 said:
View attachment 5351809like this?
Click to expand...
Click to collapse
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
(
I know little about Android development but I have the device it's not my daily driver so I can test stuff on it and if it goes south it's no big deal. Btw the revvl 4+ is the Qualcomm model, the 4 is the mediatek soc.
clintongsan said:
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
Click to expand...
Click to collapse
Have you had any luck on this yet???
I selected the first DSu , let it install and now the bootloader is corrupt. ( which im pretty sure means its inoperable) so the verity is definitly disabled. I can load into fastboot and baout to test the fastboot oem unlock.
clintongsan said:
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
Click to expand...
Click to collapse
I was bale to let it install. You gotta downgrade to the first firmware it came with and let the DSU install. My dm-verity is corrupted which is, Im pretty sure disabled, and im able to boot into fastboot
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Anyone found a stock firmware for this yet?
sketchscarz said:
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Click to expand...
Click to collapse
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
mfoster978 said:
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
Click to expand...
Click to collapse
when yourein fastboot d, in adb type fastboot reboot bootloader
sketchscarz said:
when yourein fastboot d, in adb type fastboot reboot bootloader
Click to expand...
Click to collapse
hmm this justs boots the phone back into the android os
then select reboot to bootloader when in fastbootd
or you can hold the volume up while plugging into your computer until you get fastboot mode at the bottom of the screen, you gotta select the dsu at least once to be able to enable orange state on tmobile boot screen
let it sit there forlike 20 minutes itll say android annd ot boot for a long time.... i let it sit there for about 15-20 minutes
im trying to figure out how to make a twrp for this device ow that the bootloader is unlocked
I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3.
You must unlock the bootloader and then follow this steps: https://topjohnwu.github.io/Magisk/install.html
I have check and my phone can be unlocked, i have downloaded fastboot but i do not understand what to do next. I got to step 8 https://www.xda-developers.com/install-adb-windows-macos-linux/ i can see my phone in the command line, what to do next?
I cannot find the fastboot icon under devices and printers
I got to https://mobilewithdrivers.com/unlock-bootloader/sony-xperia-l3-32gb-3gb-ram i got it into fastboot mode but no commands works, fastboot flashing unlock, fastboot oem unlock. Unknown command, command not allowed.
Should i have a unlock code? I only see Xpeira L2 on the site for getting a unlock code, no L3 https://www.getdroidtips.com/unlock-bootloader-xperia-device/
It seems to be something wrong in developer mode, oem do not turn on, no green, it is just off.
Oldschool297 said:
I have a Sony Xperia L3 and i have tried to root but it seems impossible. How can i do it? I have tried to root the phone with Sony Xperia C Root but it could not do it. Kingo Root is the same, fail. Also tried dr.fone but it did not support l3
Click to expand...
Click to collapse
What's phone's Android version? Android 8.1 ? If so, look inside here:
[HOW TO] Root Android 8.1 - DevPreview 1 - OPP5
There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time. 0: Yep, there is a step zero here. :good...
forum.xda-developers.com
Thanks. I cannot unlock the bootloader to try. I do not get the oem under development mode to work. It is only off. I can't get it on to unlock the bootloader.
Why not contact Sony ?
Sony Support Consumer Electronics
services.sony.co.uk
I tried the guide https://www.kingoapp.com/root-tutorials/how-to-unlock-bootloader-android-device.htm i get it to fastboot and the light is blue but i only get. Failed remote: Command not allowed, Finished. total times 0.045s.
What Fastboot command did you run?
BTW: Install the suitable Fastboot driver provided by Sony, if not already done yet.
I tried
Use the Command Prompt window to retrieve your unlock key as described by your manufacturer. If you own a Motorola device run the command: fastboot oem get_unlock_data, HTC run the command: fastboot oem get_identifier_token.
Select the token which is spit out by the Command Prompt window and copy and paste it into the applicable box of the form on your manufacturer's website without any spaces.
And: fastboot -i 0x0fce oem unlock 0x07B7BFEA7AC879F0 https://www.getdroidtips.com/unlock-bootloader-sony-xperia-x-f5121f5122/
I downloaded android_winusb.inf were should i add it?
Don't understand what you've downloaded. It's an ADB driver.
Contents of relevant ADB driver 's .ZIP-file is
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To install the suitable ADB driver:
Open the Device Manager. To do this, click Start and type Device Manager. Then click Device Manager.
In Device Manager, right-click the name of your computer at the top of the device list, and then click Add Legacy Hardware.
In the Welcome to the Add Legacy Hardware Wizard dialog box, click Next.
Select Select and install hardware manually from a list and click Next.
Select Show all devices and click Next.
Click Disk....
In the Disk... dialog box, click Browse... click Browse, and then select the driver file with the extension adb (written like this: xxxxxadb, where xxxxxx is the unique file name). Click Open.
In the Disk... dialog box, click... Click OK.
Highlight the Sony xxxxxx ADB Interface Driver file and then click Next twice. The installation starts.
Click Finish and restart the computer.
I get this.
I also tried https://techbeasts.com/how-to-unlock-bootloader-of-sony-xperia-devices-guide/ the problem in fastboot seems to be that i- becomes and unknown option
https://forums.androidcentral.com/t...tloader-fastboot-exe-unknown-option-i.895276/ fastboot R26 seems to work for the most i have the 34. platform-tools v 28.0.0 does not work with the provided command from the official manual.
Yes it was the version, it is the second time i try to mess with andriod phones. I learn more and more. I tried fastboot.exe i- 0x0fce getvar version and i got version 0.5, finished, total time 0.000s
I tried fastboot.exe -i 0x0fce oem unlock 0x and got FAILED, command not allowed. I did only find Sony L, L1 and L2 on sony oem https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code can it be that? I remeber i had a Sony Xperia X code.
I also tried fastboot flashing unlock, FAILED unknown command. with fastboot devices i got my phone visable.
I have two Huawei Mate 10 Pro (BLA-L29 / C432) bought new in 2018. The first one has EMUI 12 on it for about 6 months and works without problems, the second one does a boot loop ("Your device has failed verification ...") after the update from EMUI 9 to EMUI 10 few days ago. The update process brought no errors. Everything worked without problems until the final reboot after checking the flashed firmware. All attempts (eRecovery, HiSuite Recovery, etc.) without success. The phone can only be brought into Fastboot/Resque Mode and is recognized as a "HI3650" USB device by the PC. That's all.
Question: How can I mirror (in a image file) the partitions/firmware on the good phone and put them on the faulty one (ADB, Fastboot, /dload, etc.)? In short, how can I clone the first one firmware on the second one. Thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[GUIDE][HOW-TO] Fully duplicate a tablet to other tablets of the same model
Fully duplicating a tablet to many other tablets. This guide was used to clone several hundreds of Samsung Galaxy S2 tablets, model SM-T815Y. You will need: Linux computer for getting the master tablet image. Windows computer for flashing that...
forum.xda-developers.com
or look inside here:
https://praxistipps.chip.de/nandroid-komplettes-system-backup-von-android-machen_30258
jwoegerbauer said:
[GUIDE][HOW-TO] Fully duplicate a tablet to other tablets of the same model
Fully duplicating a tablet to many other tablets. This guide was used to clone several hundreds of Samsung Galaxy S2 tablets, model SM-T815Y. You will need: Linux computer for getting the master tablet image. Windows computer for flashing that...
forum.xda-developers.com
or look inside here:
https://praxistipps.chip.de/nandroid-komplettes-system-backup-von-android-machen_30258
Click to expand...
Click to collapse
jwoegerbauer said:
[GUIDE][HOW-TO] Fully duplicate a tablet to other tablets of the same model
Fully duplicating a tablet to many other tablets. This guide was used to clone several hundreds of Samsung Galaxy S2 tablets, model SM-T815Y. You will need: Linux computer for getting the master tablet image. Windows computer for flashing that...
forum.xda-developers.com
or look inside here:
https://praxistipps.chip.de/nandroid-komplettes-system-backup-von-android-machen_30258
Click to expand...
Click to collapse
Thanks for your answer but i don't want a full backup/image of the phone/system. I also don't want to flash a image file of the firmware from the net resp. downloaded from Huawei HiSuite repository. I want to make a firmware (only!) image file of the good one and put/flash this (with ADB or placing the file in /dload directory on one USB-Stick etc.) on the bad one. In Linux (i have Mint21/Win11 on the same Laptop) the problem is the same. I have no resp. less access to the faulty device (compared to Windows - that have the Huawei USB-drivers from HiSuite). I must install the (Linux) USB emulators/drivers to access the device (with ADB or Fastboot over the USB port) or insert a USB-Stick with the image file in /dload directory or ... try to boot from the Phone-USB with LinuxLive, Android and so on. That's all that i can imagine me at this moment. I wrote to Huawei about this incident too, because it's not normal to have such problems by upgrading. We will see what they do/propose.
My understanding of a firmware is that it consists of the 2 parts "kernel" and "system", that these 2 components get provided as a flashable .IMG-file, that these 2 .IMG-files typically get flashed via Fastboot what requires an unlocked bootloader.
Hence you as 1st step extract from working device both the boot and the system partition by means of ADB, then you as 2nd step flash the 2 IMG-files via Fastboot onto non-working device.
Code examples:
Code:
@echo off
echo connect working phone with PC
pause
adb devices
adb exec-out "cat <system partition> 2>/dev/null" > C:\system.img
echo connect not working phone with PC
pause
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flash system C:\system.img
fastboot reboot
exit
or
Code:
@echo off
echo connect working phone with PC
pause
adb devices
adb exec-out "dd if=<system partition> bs=64k 2>/dev/null" > C:\system.img
echo connect not working phone with PC
pause
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flash system C:\system.img
fastboot reboot
exit
Exact! That's the idea! Thanks for the examples! At the moment I am waiting for the reaction from Huawei and then I will try exactly what you wrote above. However, I don't have to save and flash all the partitions (also recovery, data, etc. too - in the order of the ROM xml-file, i.e. servicefile.xml flashfile.xml or so) to have a clone (of the device in its original state)? In addition, I have to see why "adb devices" doesn't show me anything (on both, Win11/Mint21) even though I installed android studio/sdk and the usb-drivers from the SDK. ADB starts the daemon, but after that (second "adb devices" command) it shows "List of devices..." and nothing below. I have to try this with the good phone to see if he does the same. Finally... when I know more I'll come back with feedback. Thanks again!