Related
So i recently got hold of a job lot of streaks, managed to resurrect a couple by running the qdl tool (older streakflash version) and one worked with the latest qdl tool ('repairtool' as the folder is named). These have now gone to friends and family and are all working fine so a sucess story there.
I now have the 3 'faulty' devices left, none of whice turn on show any signs of life BUT 2 were detected through volume up + usb and i ran qdl on both of them, both suceeded (see log below) but still show no signs of life and are now no longer detected through volume up + usb.
Just thought id post here before going down the JTAG route to see if anyone had any ideas first.
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Tue Nov 02 15:53:54 2010
Check image DBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: B:\dell\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: AUS_100908_01_BOSS_EVT3_FROYO_RE
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
fastboot download: userdata, checksum: 0xfe9ef69a ...
erasing 'logfilter'... OKAY
fastboot download: recovery, checksum: 0x8872a076 ...
fastboot download: rcfile, checksum: 0x77fbeecc ...
fastboot download: osbl_bak, checksum: 0x29dcffb8 ...
fastboot download: amss_bak, checksum: 0x8bcb76e2 ...
fastboot download: dsp1_bak, checksum: 0x29ca9e8d ...
fastboot download: dt_bak, checksum: 0xce136d64 ...
fastboot download: appsboot_bak, checksum: 0xf55e1594 ...
fastboot download: recovery_bak, checksum: 0x8872a076 ...
fastboot download: logfilter, checksum: 0x1bad7a9c ...
.......Download android successed.
Download success - 2010/11/02 15:56:51
Elapsed Time: 177.40 sec
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Thu Oct 28 14:53:36 2010
Check image DBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\DS22OFW\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A120621
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
fastboot download: userdata, checksum: 0xfe9ef69a ...
erasing 'logfilter'... OKAY
fastboot download: recovery, checksum: 0x8872a076 ...
fastboot download: rcfile, checksum: 0x77fbeecc ...
fastboot download: osbl_bak, checksum: 0x29dcffb8 ...
fastboot download: amss_bak, checksum: 0x8bcb76e2 ...
fastboot download: dsp1_bak, checksum: 0x29ca9e8d ...
fastboot download: dt_bak, checksum: 0xce136d64 ...
fastboot download: appsboot_bak, checksum: 0xf55e1594 ...
fastboot download: recovery_bak, checksum: 0x8872a076 ...
fastboot download: logfilter, checksum: 0x1bad7a9c ...
.......Download android successed.
Download success - 2010/10/28 14:57:26
Elapsed Time: 229.76 sec
EDIT: I would just like to add that during the sucessfull qdl runs above neither of the devices actually powered up and went into fastboot mode as they usually would.
I've since opened these streaks up to check the internals, on looking everything looks intact so i think i can rule out an internal hardware fault. The internal sd cards however i removed and inserted into a windows 7 machine at which point i was asked to format, both are wanting to format at 244 mb so it seems the qdl tool has wiped them both clean. I've never seen this behaviour before running the qdl tool so i have no idea whats happened any thoughts anyone ? also what could have caused the streak to be no longer recognised after running qdl on them ?
p.s. i've been on the streaks irc channel a few times but no ones seems to be around.
drkdeath5000 said:
I've since opened these streaks up to check the internals, on looking everything looks intact so i think i can rule out an internal hardware fault. The internal sd cards however i removed and inserted into a windows 7 machine at which point i was asked to format, both are wanting to format at 244 mb so it seems the qdl tool has wiped them both clean. I've never seen this behaviour before running the qdl tool so i have no idea whats happened any thoughts anyone ? also what could have caused the streak to be no longer recognised after running qdl on them ?
p.s. i've been on the streaks irc channel a few times but no ones seems to be around.
Click to expand...
Click to collapse
you really dont know how internal sd partition works do you?
internal sd using ext2 partition.. therefore it is not working in windows environment and thats why windows suggest to format ...
internal sd is partitioned to 2 split... 244mb and the rest...
the reason that it shows 244mb is because windows unable to recognize any partition more than 1 for anything similar to thumbdrives...
and for qdl.. sorry i cant answer because i never used it even once...
deysmacro said:
you really dont know how internal sd partition works do you?
internal sd using ext2 partition.. therefore it is not working in windows environment and thats why windows suggest to format ...
internal sd is partitioned to 2 split... 244mb and the rest...
the reason that it shows 244mb is because windows unable to recognize any partition more than 1 for anything similar to thumbdrives...
and for qdl.. sorry i cant answer because i never used it even once...
Click to expand...
Click to collapse
Thanks for taking the time to reply i have no idea how the internal sd card partition works but i have loaded up my linux virtual machine and can see the partitions so it seems qdl has done its work after all. So something else must be preventing it from booting up.
Im considering the JTAG route but im not convinced even that would fix them. Considering the QDL (streakflash) tool bricked them in the first place whats the chances of it working the next run ? I may end up paying for the JTAG only to find that QDL bricks them again so im wondering what to do. The problem is i have no history of these devices so it could be anything really, unless i can be certain of what caused it well its not really worth the risk is it...
drkdeath5000 said:
Im considering the JTAG route but im not convinced even that would fix them. Considering the QDL (streakflash) tool bricked them in the first place whats the chances of it working the next run ? I may end up paying for the JTAG only to find that QDL bricks them again so im wondering what to do. The problem is i have no history of these devices so it could be anything really, unless i can be certain of what caused it well its not really worth the risk is it...
Click to expand...
Click to collapse
if you are using jtag route... most probably the streak could only be used as wifi tablet... no more phone function anymore... that is what being reported though...
deysmacro said:
if you are using jtag route... most probably the streak could only be used as wifi tablet... no more phone function anymore... that is what being reported though...
Click to expand...
Click to collapse
Think I had a kind of breakthrough here - I've been scratching my head considering sending my Streak off to one of those jtag places to get it working again. But alas! No need.
I've tried the QDL tool maybe 25 times and though it says success, I still couldn't boot or get into fastboot by any combinations of keys.
But tonight I successfully booted into the stock rom - this is how:
Make sure all your drivers are there. I used Win7 x64 so I know it can be done. Then get your hands on the QDL tool. Start the QDL.exe. Plug your bricked Streak in with the usb cable. Hold the volume up button (or whatever the button closest to the headphone jack is) until you see your Qualcomm HS-USB Diagnostics 9002 port in the QDL application. Click "Run". Let the application do its thing for a few seconds until the moment you see "DT is in fastboot mode" (I think it said) on your device with white text on an otherwise black screen. Yank your usb cable out! If you see the "Fastboot mode" you waited too long. In that case, pull your battery and start again. Then start a command window where you have your fastboot.exe and recovery.img. Mine was in C:\Fastboot. I then ran fastboot flash recovery recovery.img. After a few seconds the device reported success. Then I ran fastboot reboot. I then waited maybe 20 seconds. Nothing happened. So I tried the power button. Holy fark a Dell logo! I don't know why, but it worked.
So maybe you could give this a try before jtagging your Streak and reportedly risking losing all GSM functionality. If this helped you out, make sure to thank and share your success story. Peace.
I havent done that,but i will remember. . . . . But i like the way your thinking. . . . . Good job
posted from my Pimped out Dell
sturmavik said:
Think I had a kind of breakthrough here - I've been scratching my head considering sending my Streak off to one of those jtag places to get it working again. But alas! No need.
I've tried the QDL tool maybe 25 times and though it says success, I still couldn't boot or get into fastboot by any combinations of keys.
But tonight I successfully booted into the stock rom - this is how:
Make sure all your drivers are there. I used Win7 x64 so I know it can be done. Then get your hands on the QDL tool. Start the QDL.exe. Plug your bricked Streak in with the usb cable. Hold the volume up button (or whatever the button closest to the headphone jack is) until you see your Qualcomm HS-USB Diagnostics 9002 port in the QDL application. Click "Run". Let the application do its thing for a few seconds until the moment you see "DT is in fastboot mode" (I think it said) on your device with white text on an otherwise black screen. Yank your usb cable out! If you see the "Fastboot mode" you waited too long. In that case, pull your battery and start again. Then start a command window where you have your fastboot.exe and recovery.img. Mine was in C:\Fastboot. I then ran fastboot flash recovery recovery.img. After a few seconds the device reported success. Then I ran fastboot reboot. I then waited maybe 20 seconds. Nothing happened. So I tried the power button. Holy fark a Dell logo! I don't know why, but it worked.
So maybe you could give this a try before jtagging your Streak and reportedly risking losing all GSM functionality. If this helped you out, make sure to thank and share your success story. Peace.
Click to expand...
Click to collapse
Ive been pretty much having the same issue as you. My streak was completely dead showing no signs of life, however it was being detected by QDL tool. Unfortunately before i could do anything to get the streak working, i know can no longer get the device to be detected by device manager or QDL tool. All the necessary drivers are installed as the device was previously being detected. Any idea as to what may have happened?
Thanks
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Strephon Alkhalikoi said:
TheManii has had the flashing tools available for some time, but the link has admittedly been difficult to find. Not having an alternate link to download the files from will lead to disaster if the site ever permanently goes down, so keep your links up and running as long as you can. Pinning this thread would be useful.
Dell Streak Flashing Tools
Click to expand...
Click to collapse
Thanks mate! I will do my best.
baba_baba said:
This should help a lot of people if their Streak is in a bricked/non functional state or if you want to reset everything to stock 2.2. QDL Tool will Unbrick/Repair your phone and install Froyo 2.2 on it from the image. You should then be able to root /install custom ROMs or simply update it with stock 2.3.3.
QDL Repair Tool: https://www.dropbox.com/sh/zafy2mn4ygcflez/k_NG62Q1MI
ADB Driver: ftp://ftp.dell.com/Handheld/R288920.exe
Here's what you need to do:
Download the QLD Tool folder from the Dropbox as a zip file.
Unzip the contents in C:
1. Press the volume up button and keep holding it after five seconds(approx) connect the USB cable(The other end should always be connected to the computer) while holding the volume up button until you hear a ding sound from your windows pc. Now open device manager and check for driver listing in the "Unknown" section named "Qualcomm CDMA Technologies MSM".
If the device is listed as “Qualcomm CDMA Technologies MSM” under “Other Devices”…
a.Right-click on it and select “Update Driver Software”.
b.Select “Browse my computer for driver software”.
c.Select “Let me pick from a list of device drivers on my computer”.
d.Click “Show All Devices” and then click “Next”.
e.Select “Have Disk”.
f.Select “Browse”.
g.Select the folder containing the drivers. For us, the drivers will be located somewhere like “C:\Streak\repairtool\QDLTool…\Drivers\Driver_2.067\Win32”. (Without the quotes, of course.)
h.Select “qcser.inf”, and hit “OK”.
i.Under “Manufacturer”, select “Qualcomm Incorporated”.
j.Under “Model”, select “Qualcomm HS-USB Diagnostics 9002”. Select “Next”.
k.You may get a warning. Hit “Yes” if you do.
l.Once Windows installs those drivers, hit “Close”.
m.Your Streak should now be listed as “Qualcomm HS-USB Diagnostics 9002”, under “Ports”.
2. Download the adb driver and install it. To check whether the driver has installed properly. power on the dell streak holding the camera button simultaneously. streak will give a white screen with fastboot on the right most corner. Enter fast boot mode by tapping on it and the screen will tell that it is waiting for a usb connection. Now connect the streak to the PC. You should hear a ding and the device manager will show "Android 1.0" if the drivers are installed correctly.
Now we have the pre-requisites for the diagnostic mode and fast boot mode.
Run the QDL tool. Now press and hold the volume button while connecting the computer. If the qualcomm drivers were correctly installed you will see that name(qualcomm …) in the port setion.
Click Run. This tool is going to take a lot of time. Here we are carrying out diagnostics and also installing Froyo with BB 306.
It will reboot several times since it has to enter fast boot mode to install recovery and flash the rom. If at the end, all the logs turn out green, Congrats, you have repaired your device. Exit the tool, unplug the device and reboot.
I successfully revived my Streak using this method. Wish you all good luck.
Click to expand...
Click to collapse
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
nsrpani said:
Hi I have Windows 7 with 64 bit. I have tried with above drivers as mentioned but due to OS version problem I couldn't follow the steps. Is there any solution for this?
Click to expand...
Click to collapse
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
baba_baba said:
The following drivers should work for Windows 7 64 bit:
http://www-307.ibm.com/pc/support/site.wss/MIGR-69999.html
If not, you may need to install more drivers. Please follow the post
http://anomaloushacker.blogspot.com.au/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html
It is a bit complicated and over detailed but the drivers should work
Cheers
Click to expand...
Click to collapse
Thanks for your quick response. While clicking on first link, it is going to Lenovo site - http://support.lenovo.com/en_ZA/ . Suggest me on this.
Update
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
baba_baba said:
Hi
As we all know Dell Streak is a tricky phone to work with and if this process doesn't work for you or f you get stuck somewhere, please try and repeat the process from the beginning. This has worked for many of us.
I apologize if the links get broken in time. I had to spend hours and hours to locate the drivers/links. If they get deleted, I am happy to send the files to you if required.
Cheers
Baba
Click to expand...
Click to collapse
Driver
jakmal said:
hi can you post the driver for win 7 64 bit?
the links r dead
thanks
Click to expand...
Click to collapse
Please try the following:
http://www.driverscape.com/download/qualcomm-cdma-technologies-msm
i got stuck here after following every single steps........
Code:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Jan 27 10:09:21 2014
Check image DBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A1355B00
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
ERROR[DA1]: download AMSS Fail!
whalesplaho said:
i got stuck here after following every single steps........
Code:
................
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
[color=red]sending 'AMSS' (15708 KB)... FAILED (data transfer failure (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...[/color]
Click to expand...
Click to collapse
same happen to me
is there any body ???
HELPPP !!!
After installing right ADB driver now another error
......................
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A140614
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
sending 'AMSS' (15708 KB)... FAILED (status read failed (Too many links))
ERROR[DA1]: download AMSS Fail!
fastboot download: boot, checksum: 0x22a73395 ...
sending 'boot' (3180 KB)... FAILED (command write failed (Too many links))
ERROR[DA1]: download boot Fail!
Best of luck!! There are tons of info for Streak. I switch between moto x and streak.
Sent from my XT1053 using xda app-developers app
Did someone have same problem as me ?
My Dell was keep restarting on Dell logo and there was no access to recovery and fastboot.
I tried with QDL and everything went good , but still no access to fastboot and recovery.
Only change is that Dell is no more restarting , only stays on Dell logo.
Please help
Streak 5 - Cannot copy system via QDL
Dear all,
I have a DELL streak 5 and having already stoned at DELL logo.
I tried QDL yet it ends like below:
HW:
Board ID:
Comment:
--
LOG
--
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sat Aug 08 07:49:43 2015
Check image DBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: D:\DELL\TOOL1\QDL Tool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device ......... Okay
Check version ... DT:y3.752
version-baseband: GAUSB1A130500
fastboot mode vid: 0x413c
Disable DT write check... ok
fastboot download: AMSS, checksum: 0x8bcb76e2 ...
fastboot download: DSP1, checksum: 0x29ca9e8d ...
fastboot download: DT, checksum: 0xce136d64 ...
fastboot download: APPSBL, checksum: 0xf55e1594 ...
fastboot download: boot, checksum: 0x22a73395 ...
INFO: download system would take more than 1 minute, please wait ...
fastboot download: system, checksum: 0x28ea5dd5 ...
sending 'system' (212695 KB)... FAILED (unknown status code)
ERROR[DA1]: download system Fail!
Download Fail! - 2015/08/08 07:52:14
Elapsed Time: 151.30 sec
Please tell me what to do.
thank you.
@jayanthap: http://forum.xda-developers.com/showpost.php?p=62244448&postcount=3
Hi,
I'm new here so I'll make it the most clear I can.
Device: LG P760
Date of production: on battery it is 02.2013 but it was in repair back in the middle of 2014 and god knows what it has been done there. Probably change of whole mainboard
Soft: Stock 10(someting) on Android 4.0.4 -Branded > Update to 20h JellyBean - Branded >>service>> not branded 20h > Flashed manually 20b Europe Open
EDIT: AP Bootloader Version: LK May-2012 (From hidden menu)
Target: Unlock bootloader
What have I done so far:
Windows 7
1. Standard console
Code:
adb reboot oem-unlock
2. RomToolkit 2
3. LGL9Toolkit
4. Bunch of scripts found here
5. Omap4boot
Result: Pretty much reboot of system without any effects
Linux Ubuntu 14.10
1. Standard console
Code:
adb reboot oem-unlock
Result: reboot of phone without any effects
2. Connecting via fastboot and
Code:
fastboot oem unlock
using modified by myself script found somewhere
Code:
#!/bin/sh
which fastboot || echo install fastbooot first, e.g. on ubuntu sudo apt-get install android-tools-fastboot
which fastboot || exit
echo 'Connect LG L9 *without battery* to PC using data cable'
sudo ./usbboot p940-aboot.2nd p940-u-boot_fastboot.bin && echo usbboot ok || exit
echo 'DO NOT disconnect usb cable. Insert battery, then press enter'
read x
sleep 10
echo fastboot devices:
sudo fastboot devices
echo 'UNLOCK'
sudo fastboot oem unlock
which resulted in:
Code:
/usr/bin/fastboot
/usr/bin/fastboot
Connect LG L9 *without battery* to PC using data cable
waiting for OMAP44xx device...
reading ASIC ID
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: de1584c8b14d699fb234d5c31e2cdd6a9932669d
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
[*] msg size = 4
[*] data size = 21552
waiting for 2ndstage response...
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
** Done **
usbboot ok
DO NOT disconnect usb cable. Insert battery, then press enter
fastboot devices:
0A3F08331801D013 fastboot
UNLOCK
...
FAILED (remote failure)
finished. total time: 0.000s
That is pretty much everything. I've read about some magic cable and something about encrypted bootloader but I'm more than confused now. Am I doing someting wrong, especially on Linux (more acquainted in this type of system)? On Windows I have to exclude drivers problems, tried on 3 different machines, waited long before unlocking
Well, I'm in your same situation, but mine has been produced the 31/5/2013, so it have an encrypted bootloader.
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
ChaseRxx said:
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
Click to expand...
Click to collapse
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
ikolbyi said:
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
Click to expand...
Click to collapse
GL!
Enviado de meu BLA-L29 usando o Tapatalk
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
LLoTE said:
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
Click to expand...
Click to collapse
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
LLoTE said:
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
Click to expand...
Click to collapse
okay - steps?
ikolbyi said:
okay - steps?
Click to expand...
Click to collapse
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
LLoTE said:
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
Click to expand...
Click to collapse
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
LLoTE said:
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
Click to expand...
Click to collapse
Thank you. I'm new at this and learning.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
look at this one
Toggling OEM unlocking in developer options is not enough, as that simply enables the ability to unlock your bootloader within fastboot. You need to retrieve a bootloader unlock code either directly from Huawei or a third party. I believe there is a guide for it in the guides sub-forum.
LLoTE said:
look at this one
Click to expand...
Click to collapse
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
ikolbyi said:
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
Click to expand...
Click to collapse
And how will you edit it? You'll root the phone or?
LLoTE said:
And how will you edit it? You'll root the phone or?
Click to expand...
Click to collapse
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
ikolbyi said:
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
Click to expand...
Click to collapse
No problem man
Need advice. My goal is to flash GSI ROM onto this thing. The treble app says it is supported. (type A)
However, the usual commands for unlocking bootloader seem to indicate it is either already unlocked but not telling me or locked and not unlockable..?
This is a unisoc SC9863a
baseband: FM_BASE_18B_W19.08.1_P11 | SC9863a_modem | 04-26-2019 MARLIN2_17A_RLS1_W19.17.7 | sharkl3_cm4 | 04-28-2019
kernel: 4.4.147+ (20190703)
build number: PPR1 180610.011
android: 9 pie
WIKO/W-V800-EEA/W-V800
9/PPR1.180610.011/08018
unrooted > MTK-su and several oneroot options not working (although they might on oreo if I can find the factory rom)
OEM unlocking enabled in developer options
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
I tried following this process: (from here (Mod Edit: Link removed)
./fastboot oem get_identifier_token
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
./fastboot flashing unlock_bootloader signature.bin
last command returns with: "downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.104s"
additional questions:
Can I just flash a certain recovery somehow?
Do I have to try something complicated like this: (Mod Edit: Link removed)
Have you got root on your view 3 lite?
go0 said:
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
Click to expand...
Click to collapse
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
anonym6x6 said:
Have you got root on your view 3 lite?
Click to expand...
Click to collapse
If oreo exists for this and you know where to get it, let me know and I'll try.
If I can get root, what would you recommend trying to unlock bootloader?
jwoegerbauer said:
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
Click to expand...
Click to collapse
OK...