I just got my 3740 a few days ago and decided to root it. I found this tethered rooting method here and failed so I followed another method, provided by Dell.
I noticed that some other members on XDA have followed Dell's instruction but at that time Dell classified WiFi version as A150 and WiFi/LTE version as A195. But now when I come back there are A195-WiFi and A195-LTE.
I followed the instruction for Flashing A195 Image to my 3740 due to my Build Number is different from those two in the instruction. I've enabled Fastboot but when I open the .bat file like instruction said, nothing happened. It keeps saying <waiting for device> and on my 3740 it said "WAITING FASTBOOT CMD"
After 15 minutes with nothing I turned it off and now it only displays the USB logo with the loading bar below each time I turn on. So now is there anyway for me to roll back or try to go through of this and get the 3740 rooted?
Hope you guys will help me quick because next week I need to use it for my trip.
After some digging and experiments I've figured out how to get over the "waiting for device" error on the .bat file and flash A195 Image for my 3740. The problem here is that Windows 7 refused to use ADB Interface Driver because "Windows cannot verify the digital signature for the drivers required for this device" or Code:52 if you choose Properties in Device Manager. So no matter how you try to install it manually or trick it to believe the driver is "digitally verified", it's still not work.
Did some Google search and I realized this happens because of Microsoft's ridiculous policy to make all drivers to be verified if they want to work normally on Windows Vista and Windows 7. So I think if I roll back to a Windows version before Vista then I'll be able to install ADB Interface Driver properly. And fortunately, I have a laptop runs on Windows XP (LOL) so I gave it a try.
I installed all the software like the instruction Dell provided said and boom, ADB Interface is installed and working properly. Since my 3740 has already in Fastboot so I quickly open the .bat file in the Image Folder, it's no longer said <waiting for device> but there is new problem. All the command lines in the .bat file did not working. They all came with the error "Fastboot is not a command" or something like that. Felt that something missing so I tried to flash image from another tool. This tool on Windows XP managed to run Fastboot commands and even successfully executed "fastboot oem start_partitioning" but failed at "fastboot flash /tmp/partition.tbl partition.tbl". Thinking for a while, I decided to take all the files in the Image Folder, put it in the Minimal ADB and Fastboot folder and just like I expected, the .bat file has surpassed the "Fastboot is not a command" error and begin to flash the A195-WiFi Image to my 3740.
Now my 3740 has working normally with a new Build Number. I'll begin to update all the OTA Updates and the Root it as soon as I finished. Thank you everyone for taking your time to read this. Have a nice day
I had the same troubles, Windows 8.1 wouldn't recognize my 3740 and even though all the drivers installed it still showed up with an error in device manager. Couldn't get FSTK working, just a crazy mess regarding the iSoc drivers. Another thing, the images for the A150 wifi-only were taken down but luckily I still have mine, haven't tried the other images. I don't have a clue why they did that though
NozomiHareshon said:
After some digging and experiments I've figured out how to get over the "waiting for device" error on the .bat file and flash A195 Image for my 3740. The problem here is that Windows 7 refused to use ADB Interface Driver because "Windows cannot verify the digital signature for the drivers required for this device" or Code:52 if you choose Properties in Device Manager. So no matter how you try to install it manually or trick it to believe the driver is "digitally verified", it's still not work.
Did some Google search and I realized this happens because of Microsoft's ridiculous policy to make all drivers to be verified if they want to work normally on Windows Vista and Windows 7. So I think if I roll back to a Windows version before Vista then I'll be able to install ADB Interface Driver properly. And fortunately, I have a laptop runs on Windows XP (LOL) so I gave it a try.
I installed all the software like the instruction Dell provided said and boom, ADB Interface is installed and working properly. Since my 3740 has already in Fastboot so I quickly open the .bat file in the Image Folder, it's no longer said <waiting for device> but there is new problem. All the command lines in the .bat file did not working. They all came with the error "Fastboot is not a command" or something like that. Felt that something missing so I tried to flash image from another tool. This tool on Windows XP managed to run Fastboot commands and even successfully executed "fastboot oem start_partitioning" but failed at "fastboot flash /tmp/partition.tbl partition.tbl". Thinking for a while, I decided to take all the files in the Image Folder, put it in the Minimal ADB and Fastboot folder and just like I expected, the .bat file has surpassed the "Fastboot is not a command" error and begin to flash the A195-WiFi Image to my 3740.
Now my 3740 has working normally with a new Build Number. I'll begin to update all the OTA Updates and the Root it as soon as I finished. Thank you everyone for taking your time to read this. Have a nice day
Click to expand...
Click to collapse
pls. help me ... i have the same problem on my dell venue 7 LTE , my device stops while installing the upgrade and it stocks on the dell logo... i have read the unbrick process and followed it but when i started the bat file for my device it shows "failed_"nvm" in red...
very well buddy
I have a 3740-A150 and I can't root
prolem to write system.img
As explained in dell manual OSS195 I have done all 11 steps successfully. For step 12 I have to copy all fastboot files to image folder than clicking that .bat file starts writing files. But it can't write system.img
Tab Screen shows E:failed to mount /cache (Block device required)
{
"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"
}
Please help.
Finally, after a lot of testing ... and tired and suffering .. thankfully I found the solution
Just place the files in a minimal_adb_fastboot_1.4.1_portable .....
And select the files to tool xFSTK_downloader_1.5.1 from minimal_adb_fastboot_1.4.1_portable
start FLASHING
Download
https://www.androidfilehost.com/?fid=457095661767103465
mafiachat007 said:
Finally, after a lot of testing ... and tired and suffering .. thankfully I found the solution
Just place the files in a minimal_adb_fastboot_1.4.1_portable .....
And select the files to tool xFSTK_downloader_1.5.1 from minimal_adb_fastboot_1.4.1_portable
start FLASHING
Download
https://www.androidfilehost.com/?fid=457095661767103465
Click to expand...
Click to collapse
Does this file and the entire flashing procedure work on win7? Or do I need to look for a Windows specific machine?
I have win 10, so found a win7 machine but fastboot does not detect connected device though drivers seems to have been installed properly.
I will try it again today on win7 with minimal adb files
Not sure what you meant by "And select the files to tool xFSTK_downloader_1.5.1 from minimal_adb_fastboot_1.4.1_portable", please clarify
Thanks in advance
Related
Hello xda people . i can't install anything or boot in recovery via fastboot. at the first times it worked but now i can't install anything.it stucks on "sending boot" . how can i fix this problem?
{
"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"
}
Fastboot help
Which OS you are using ... just keep the windows update on the drivers will be downloaded automatically .. Get some more details of your computer
It seems you have driver problem.
try 'fastboot.exe -i 0x0fce getvar version'
if it returns something like 0,3 it means drivers are installed correctly.
if stucks on waiting for device, reinstall drivers =)
Ok thanks I have Windows ultimate 7 32bit
Sent from my MT11i using Tapatalk
hm... try to reinstall drivers from flashtool folder.
Or this drivers: ht tp: / /narod.ru/disk/41611663001.12211e20e6329016ba9f418a88544664/fastboot_ADB_drivers.zip.html
sorru for russian uploader
Works on my win7 x64 PC and 7 x86 notebook
I have same problem, looks like I have problem with drivers, can some1 upload drivers for 64bit Win7? I can't download drivers from this russian server don't know why.
dalany said:
It seems you have driver problem.
try 'fastboot.exe -i 0x0fce getvar version'
if it returns something like 0,3 it means drivers are installed correctly.
if stucks on waiting for device, reinstall drivers =)
Click to expand...
Click to collapse
see my friend . the first stuck and the second send it with very poor speed
Replace USB cable
May work
Qwerty123 \m/ said:
Replace USB cable
May work
Click to expand...
Click to collapse
i don't think that is the problem , because on my sis laptop it works normally. anyway i will try a format and install new windows to see.
Thanks all ppl for answers
sspoko said:
I have same problem, looks like I have problem with drivers, can some1 upload drivers for 64bit Win7? I can't download drivers from this russian server don't know why.
Click to expand...
Click to collapse
Hi buddy
Here U R
the link you want it
as I'm new I cant send link in form of Url
follow this ht tp://w w w.mediafire.com/download.php?y89fff6mc8hblia
I had a similiar problem, though not the same. It was fixed after a reboot of my Windows 7 x64. I think my computer had problems dealing with the USB being connected and disconnected an awful lot. I have no idea if this is where your problem comes from, but it might help if you're like me and prefer leaving your computer on at all times.
Also, if you're quite new to rooting and flashing, and aren't that interested in learning the ins and outs of it, I recomend using Flashtool [1] for flashing to an earlier version of stock Android, rooting your Android, easy booting in fastmode and flashing your kernel. The only use I've found for fastboot.exe is to unlock your bootloader [2] (official guide by Sony Mobile), though I might be missing out on something (while I actually do not believe I have).
Please keep us posted.
As I'm a new member, I can't link directly to outside sites, but I'm going to break that rule to try and help you even further (ie. I did the Googling for you). Replace the spaces below with periods. Links:
1: androxyde github com/Flashtool/
2: unlockbootloader sonymobile com/
Markussssss said:
I had a similiar problem, though not the same. It was fixed after a reboot of my Windows 7 x64. I think my computer had problems dealing with the USB being connected and disconnected an awful lot. I have no idea if this is where your problem comes from, but it might help if you're like me and prefer leaving your computer on at all times.
Also, if you're quite new to rooting and flashing, and aren't that interested in learning the ins and outs of it, I recomend using Flashtool [1] for flashing to an earlier version of stock Android, rooting your Android, easy booting in fastmode and flashing your kernel. The only use I've found for fastboot.exe is to unlock your bootloader [2] (official guide by Sony Mobile), though I might be missing out on something (while I actually do not believe I have).
Please keep us posted.
As I'm a new member, I can't link directly to outside sites, but I'm going to break that rule to try and help you even further (ie. I did the Googling for you). Replace the spaces below with periods. Links:
1: androxyde github com/Flashtool/
2: unlockbootloader sonymobile com/
Click to expand...
Click to collapse
thanks but actually i have unlocked bootloader.. and i have some xperience because i had x8 and i have tweaked it full
Had similar problem!
First couldn't get into fastboot, had problem installing S1 driver. Changed the USB port on my PC and it asked to install the S1 again. Chose the directory where it was and voila.
Now I have to use 2 different USB port for fast boot and flashmode. Little annoying but I got used to it.
Try it, it may work for you.
Reinstalling Windows should be your last step, especially a stable OS as Win 7!
P.s. Why don't you use Flashtool? In it's newer version there's a *.exe (under drivers folder) file that automatically install all needed drivers.
DNDimitrov said:
Had similar problem!
First couldn't get into fastboot, had problem installing S1 driver. Changed the USB port on my PC and it asked to install the S1 again. Chose the directory where it was and voila.
Now I have to use 2 different USB port for fast boot and flashmode. Little annoying but I got used to it.
Try it, it may work for you.
Reinstalling Windows should be your last step, especially a stable OS as Win 7!
P.s. Why don't you use Flashtool? In it's newer version there's a *.exe (under drivers folder) file that automatically install all needed drivers.
Click to expand...
Click to collapse
i will try
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
edit:
The driver that was install for my device is from microsoft. (see pictures below)
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
GalosSide said:
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
Click to expand...
Click to collapse
Are you using Windows 8?
cpumaster said:
Are you using Windows 8?
Click to expand...
Click to collapse
im using windows 7 sp1
also I just realize that i cannot use Sony PC Companion to do anything with my device it said that internet connection is required, but I am already connected.
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
hush66 said:
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
I'm still getting the same problem with the driver install.
I think i know what the problem is right now. The driver that was install for my device is from microsoft. (see pictures 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"
}
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
hush66 said:
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
GalosSide said:
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
Click to expand...
Click to collapse
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Frantiic87a said:
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Click to expand...
Click to collapse
I did and it said "insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)"
edit:
I restart my phone and root again. It's finally rooted.
Thank you every one for helping me.
Thank you!
sorry we facing the same problem so please tell me if found a solution
ADB FASTBOOT Drivers
Nothing worked for me accept this one.
I went there downloaded this driver installed it and it did its magic.
https://www.driveridentifier.com/sc...14379&scanid=92D42FEE7DDD4826835F8C3C3611A400
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.
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
{
"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"
}
StanYz said:
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
Click to expand...
Click to collapse
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
TheExploitedOne said:
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
Click to expand...
Click to collapse
I've attatched 4 screenshots in my OP, thats all I see, it doesn't actually state what the error is, just that it didn't finish.
Will it go through with win7? Actually that aside, is there a way to force a new os onto the phone via the flashtool to begin with?
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
jwoegerbauer said:
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
Click to expand...
Click to collapse
---
My carrier doesn't offer any drivers whatsoever.
But all of that aside, even if I do get fastboot running, is there even a way to force a new OS onto the phone via some tool?
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!