[GUIDE][addison]RSD lite and adb - writing firmware to phone - Moto Z Play Guides, News, & Discussion

use with care...
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Firmware is a set of programs and files/data that, together, are the tools and support that a ROM (stock or custom) uses to run every aspect of your phone. It sits between your phone, and the ROM you have on it - stock or custom.
Wikipedia: firmware
Firmware varies widely from one phone to another, from one country/area/carrier to another, and from one ROM's releases to another.
- - - - - - -
You can use adb - see example in first post of
[GUIDE][addison] factory stock images
- - - - - - - - - - - -
OR you can use RSD lite:
RSD lite changes your phone's firmware. It can result in a bricked phone that needs to be sent to Moto for reblank/reflash. - be careful!
RSD lite is Motorola’s (windows) tool to install software or code onto an Android device.
info: http://rsdlite.com/
-- > Use the latest one 6.2.4 from here http://rsdlite.en.lo4d.com/
---> Everything will be lost except what is on SDcard and Internal Storage. <---
1) select the firmware you wish to put on your phone. That is no small task and requires much research.
I believe this is all of the firmwares:
[GUIDE][addison] factory stock images
Never never never downgrade your phone - eg NEVER go from Nougat to MM. It can result in a bricked phone that needs to be sent to Moto for reblank/reflash.
Download the firmware to your computer.
2) In win7 (I believe if you google you will find out how to run it on win 10)
start RSD lite by doing this:
in explorer go to C: /program files(86)/ Motorola/ RSDlite,
right click on SDL.exe and choose run as administrator. It takes easily 25 sec for the app to start!!!!
Then in the RSD lite window, choose the firmware you want to put on your phone (Everything will be lost except what is on SDcard and Internal Storage.)
by clicking on the 3 dot browser file button to the right of the "filename" box (pic 1).
3) tap "decompress only" (pic 2) and watch it do it's thing.
When it's done,
4) boot your phone to fastboot screen (hold power and vol-dn buttons until the fastboot screen pops up.)
5) connect a USB cable from computer to phone. Phone should now show as present in RSD lite window - line 1 will now say fastboot (pic 3).
If phone is not recognized, assure you are running 6.2.4 RSD lite. Then try different cables - In less than a week I heard of 2 cases where a different cable did the trick. New and expensive is not the point - I used an old micro male to A male and an 80 cent micro female to C male adapter (lot of 5 on ebay) to do mine.
6) tap start (pic 4) and the process will start - be patient: sparsechunks (the real "stuff") are big and there's 10 of them in the Moto z Play XT1635-02
When it completes, it reboots to the new rom and you will see your phone rebooting - LET IT!!! As I recall it stops when it gets to start screen.
Remember if you are going to use RSD lite, use the latest one 6.2.4 from here http://rsdlite.en.lo4d.com/ , and start it in admin mode. Earlier versions won't recognize your phone. (boot phone to fastboot screen and usb plug to PC)( do lots of googling if you're using win10.)

Great guide.
I m sure that will help us.
Tks

edit

Well, instead of just saying "do a lot of googling it you are on Windows 10" you should tell us how it works there since nobody can find anything about how to get it to work there

Artim_96 said:
Well, instead of just saying "do a lot of googling it you are on Windows 10" you should tell us how it works there since nobody can find anything about how to get it to work there
Click to expand...
Click to collapse
Lol, I have no idea. I avoid win10 like the plague! At the moment there are about 5 different releases/versions that MS is actively supporting!
Sent from my Motorola XT1635-02 using XDA Labs

One of the main headaches with Windows 10 (and 8.1 as well if I recall) is the introduction of driver signature enforcement - unsigned drivers (not WHQL signed) won't load. This may include the Motorola ADB drivers and the fastboot drivers (regardless of if you use RSDlite or the minimal ADB/fastboot or the SDK from Google), you may not see your device if you boot it to bootloader and attach it to your computer.
The workarounds have been to set your computer to testing mode or disable driver signature enforcement: https://www.addictivetips.com/windows-tips/disable-driver-signature-enforcement-in-windows-10/ Is one such guide to do so. However, be careful as this allows anyone (you or anyone else) to load unsigned drivers onto your computer, so be vigilant.

Related

[HowTo] use 3G Dongle on TF101 *UPDATED 04/13/2012*

Hello,
(First sorry for my very bad english. It's not my natural language but I do my best for sharing with you!)
04/13 - UPDATE: Now 3G works for ICS with some ROMs like Megatron.
Revolver will be based on TF101G ICS ROM soon.
09/17 - UPDATE:Roach2010 and gnufabio have developped an apk that enable Mobile Network settings (for 3G dongle).
Their APK change the bootloader. (Read more and download)
So maybe this thread has no purpose except for issues and for the list of compatible dongles. If you have a dongle which work and which is not in the list.....
11/08 - UPDATE: 3G dongle works too with Extension-Kit/TFUSB1 Asus P/N 90-XB2UOKEX00020
You can find it here: http://shop.asus.fr/shop/fr/fr-FR/Home/1-Produits/1500-Collection-ASUS/1936-Accessoires-Eee-Pad/1937-Accessoires-Transformer-Prime-TF201/90-XB2UOKEX00070-Adaptateur-USB-externe-pour-ASUS-Eee-Pad.aspx (Thanks to ValenteL for information)
************************************************************
Bellow you can find the first post
Thank you,
Regards.
FIRST POST:
There is probably other ways to make the 3G Dongle working on TF101 but here you can find how we have done.
The follow lines work to have Prime v1.5 installed on your Transformer (works with any version!)
Then you could upgrade to Revolver 2.1.
Otherwise you can directly nvflash your TF101 with the Revolver 2.5 NVFlashed version of cuckoopt.
You just have to follow instructions on this post.
Don't forget to thank him if it works for you
Note: SetCpu doesn't seem to work. I don't know if the issue is coming from Revolver or HC. By re-installing SetCpu, it works one time then crashes.
A. Prime V1.5 Installation:
1. You have to backup all your data/apk from your Internal SD Card because we will make a clean install. So use your backup software.
Becareful. if you project to use Titanium Backup, his backup files are on the internal SD Card so afterwards, you have to move it to your MicroSD (from /mnt/sdcard/Titatium Backup to /data/Removable/MicroSD)
2. Download NVFlash: http://www.filefactory.com/file/ccda97c/n/nvflash.zip then the NVFlash version of Prime v1.5: http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.5_nvflash.tar.bz2
Updated note: I am not able to activate the Mobile Network option with version 1.6 (even Zip version for ClockWorkMod nor NVFlash version).
But some people have succesfully activated it by flashing NetFinder 1.5 just after the fresh Install of Prime v1.6 and before rebooting the system ; it means in the same CWM
3. unpack NVFlash and Prime v1.5 in the same directory. The image files of Prime v1.5 should be unpacked into the NVFLashTF folder.
4. Connect your TF101 to your PC via USB. Then hold the volume UP and Power button until a NEW device named "APX" appears in the Device Manager. Note that the screen of the Transformer stays black.
5. Click on the APX to install drivers from directory USBPCDriver (included in NVFlash.zip)
info: I used Windows XP 32 bits.
6. Then run Download.bat if you are on Windows, download.sh for Linux users
7. When NVFlash is ended, reboot your TF101.
During boot, there is a setup wizard. Choose connection with "3G and Wifi", not "only Wifi"!!
At this step, you must have the Mobile Network option in Parameters.
8. Download Maxh2003 Script: http://android.modaco.com/index.php?act=attach&type=post&id=73836 (you need to be a register user on Modaco You could find another link some posts after!)
Download the Patch files for ACER A500 tab: http://forum.xda-developers.com/attachment.php?attachmentid=638588&d=1309189189
9. Unzip the script and the Patch file in the same directory.
If you want to upgrade to Revolver 2.1 version (HoneyComb 3.2), you must stop here and go to step B (chapter B).
Otherwise continue chapter A.
10. Connect your TF101 and run install-TF101.bat
11. Mobile Network option is here.
B. REVOLVER 2.1 Installation
1. Do a fresh install of Prime v1.5 NVFlsh version.
If it's not the case go back to the begin of this post and execute steps A.1 to A.9. then go back to B.2
2. Download this file
3. If you read this, Prime v1.5 NVFlash version is installed and you are in CWM Recovery screen.
Install the Recovery 2.1 version (Full). DON'T WIPE DATA
4. At the end, just reboot your system and verify that Mobile Network option is still here.
5. Then we have to install drivers for your dongle (see the list below for compatible dongles).
Let your TF101 on, connect it to your PC via USB cable and run install-TF101.bat via cmd.exe from Windows (tested under Windows XP x86 and Windows 7 x64)
C. List of COMPATIBLE DONGLES
Note: if your dongle is not in this list, but works with TF101, please tell me. It will be added to the list.
* ZTE MF 639 (might need roaming enabled to get data working)
* Alcatel X225L (thx to urko95)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E156G (thx to sh337 for testing)
* Huawei E160G (thx to htc-hd2. His post)
* Huawei E161 (thx to zumbik. His post)
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173 (ATTENTION: E173 EVO version NOT COMPATIBLE - thx to sronweb for his tests - Read more)
* Huawei E180 (thx to ValenteL. His post)
* Huawei E220 (thx to eyz. Connexion seems to be not stable. Read more)
* Huawei E270 (thx to eyz. His post)
* Huawei E1550
* Huawei E1552
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1762 (thx to bennyyen. His post)
* Huawei E1820
* Huawei E1823 (Thx to bswpt. His post)
* Huawei E2010 (Thx to madangryscientis. His post)
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Click to expand...
Click to collapse
D. About LED on HUAWEI 3G Dongle:[/B]
The LED indicator displays the current connection status of your Orange E1752 dongle, with each colour representing a different status:
When the LED displays green and is blinking twice every three seconds, this means that the dongle is powered on.
When the LED displays green and is blinking once every three seconds, this means that the dongle is attempting to register onto a 2G network.
When the LED displays blue and is blinking once every three seconds, this means that the dongle is attempting to register onto a 3G network.
When the LED displays solid green, this means that the dongle is connected onto a 2G network.
When the LED displays solid blue, this means that the dongle is connected onto a 3G network.
When the LED displays solid cyan, this means that the dongle is connected onto a 3G+ network
When the LED displays no colour, this means that the dongle is removed.
Click to expand...
Click to collapse
And dont forget to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco who wrote these lines):
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Click to expand...
Click to collapse
Remerciements/Thanks to AndroidRoot.mobi for NVFlash, Paul for Prime!, Maxh2003 for his script and help, Matchstick for his help, Dexter_nlb for his A500 patch and, of course, all our developers and users who help us.
Not sure why I've flashed several roms in APX from w7 64 bit just fine.
It seems that these drivers don't work for win7 64 and works for Vista 64.
Perhaps they are unsigned.... didn't know. I don't make more tests.
Regards.
Looking good. Now to get a 3G plan and dongle...
Anyone get this working?
to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks
nsec said:
to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks
Click to expand...
Click to collapse
Here the file.
Regards
insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP
dan-htc-touch said:
insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP
Click to expand...
Click to collapse
Hello it's not a theoretical WIP.
Look here
Can you give more details please?
Regards,
oh... I guess insmod won't work on the modules without a compatible modem plugged in then?
many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
dan-htc-touch said:
oh... I guess insmod won't work on the modules without a compatible modem plugged in then?
Click to expand...
Click to collapse
Probably. is you 3G Dongle in the "compatibility list".
If yes, you have to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco):
Code:
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatha...y/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Regards
brensim said:
many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
Click to expand...
Click to collapse
What kind of OTG adapter are you using for this?
Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks
I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?
At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)
acid12 said:
Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks
Click to expand...
Click to collapse
Is this similar to the huawei E367 ? As I'm looking at the E367 at the moment.
One easy(ish) way to check is to follow Steps 1-8 from post 12, then enter the command "AT^GETPORTMODE" (without the quotes)
If you get a response like
"^getportmode:type:WCDMA:Qualcomm,MDM:0,NDIS:1,DIAG:2,PCUI:3,CDROM:4"
then the E173u2 is using the new interface like the E367 and at the moment I can't get it to work.
It may be that the drivers aren't compatible (I'm not seeing ttyUSB0-ttyUSB2 devices appearing in /dev/) or it may just be that I haven't got the correct interfaces enabled.
There's information on the AT commands for the new-style Huawei modems here
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=618504
Matchstick said:
At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)
Click to expand...
Click to collapse
So i think that it is not only root needed but also something that in PRIME is present and that we can not add to stock rom.....
thanks
chrispazz said:
I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?
Click to expand...
Click to collapse
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data
Kasimodo said:
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data
Click to expand...
Click to collapse
Ok. I have to wait for my docking to come back from ASUS (RMA) and then I will try.
TY

Device stuck on "Sony" screen FIX

There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a functioning computer with ADB drivers installed (flashtool has a driver installer you can use), and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
arsradu said:
Or, you can do this:
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning on
reboot
install drivers. Agree to installing unsigned drivers when you see the pop-up. Drivers should be correctly installed now.
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning off
reboot
That's all.
Click to expand...
Click to collapse
I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.
mrrflagg said:
I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.
Click to expand...
Click to collapse
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files
nzzane said:
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files
Click to expand...
Click to collapse
Thank you!
For Windows, maybe it would be nice to mention that it's not gonna work (by default) in Windows 8, 8.1 and 10, so Windows 7 is recommended for this.
There is, however, a way (actually, there are 2, but I found one of them to be easier than the other) to get those drivers installed on Windows 8 and above.
You can find it here.
nzzane said:
There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a function computer with ADB drivers installed (flashtool has a driver installer you can use) and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
Click to expand...
Click to collapse
Thank you thank you thank you!!! I almost cried
Stupid me... After installing locked dual recorver, i wiped the system and switched the phone off... It game me a warning sign saying there was no OS, and I said yup, no worries (thought it was like PCs where boot OS has nothing to do with Android).
Phone got stuck on the Sony logo and the only way to do anything was to use the hard reset button!! YOU SAVED ME!
Bump
Many people still get themselves stuck in this issue :3
yep stuck on Sony screen
here what flash tool says;
12/048/2017 21:48:23 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.0.A.2.93. Customization : Customized CE1
12/048/2017 21:48:23 - INFO - Preparing files for flashing
12/048/2017 21:48:24 - INFO - Please connect your device into flashmode.
12/048/2017 21:48:32 - INFO - Device connected in flash mode
12/048/2017 21:48:32 - INFO - Opening device for R/W
12/048/2017 21:48:32 - INFO - Reading device information
12/048/2017 21:48:32 - INFO - Phone ready for flashmode operations.
12/048/2017 21:48:32 - INFO - Opening TA partition 2
12/048/2017 21:48:32 - INFO - Current device : D5803 - YT9115XKA6 - 1288-7915_R2D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
12/048/2017 21:48:32 - INFO - Closing TA partition
12/048/2017 21:48:32 - INFO - Start Flashing
12/048/2017 21:48:32 - INFO - Ending flash session
12/048/2017 21:48:32 - ERROR - Can't read a byte value
12/048/2017 21:48:32 - ERROR - Error flashing. Aborted
I was able to successfully apply erased firmware by following your instructions.....Thanks a ton

[HOW TO] Recover HARD BRICKED Nokia X2 : DOESN'T TURN ON, NO VIBRATION, NO LIGHT

So, Guys. Myself thought of writing this thread so that you can prevent yourselves from entering into danger as well as get rid of it even if you enter by mistake.
As you all know that, we are currently facing an issue of SIM offline, myself got into the trouble (as per me, when i insert a sim in sim 1, device recognizes the network provider but there is no signal. sim 2 is fine) and inorder to rectify that issue, i tried all possible ways like deleting IMEI and rewriting it, changing modem etc.
But nothing worked and so thought of using NOKIA CARE SUIT (NCS) >> Product Support Tool For Store 5
& change the firmware to Nokia X2DS RM-1013 059V782 v2.1.0.13 which was the biggest mistake which i ever committed and it resulted in hard brick.
I suggest everyone not to flash 2.1.0.13 version please
In my case, i was not even able to use the volume buttons and power button inorder to get to bootloader or custom recovery. Trust me, i'm not a noob but i do know the situation in which i'm and searched everywhere and took help of lots of guys and finally found the solution to it.
Just follow these steps:
A. Requirements:
1. Nokia Firmware - Thanks to Firmware27
2. QPST_2.7.422
3. QDLoader HS-USB Driver
B. Procedure:
1. Extract Requirement - 1, 2, 3 separately.
2. Now Install requirement - 2 & in Requirement - 3, just install Setup
3. Now connect USB to NOKIA X2 & Laptop/PC
4. Click on the start menu and type QFIL in search box and open it.
5. Under "SELECT PROGRAMMER", click on the browse button and
select "rm1013_2.1.0.13_user_prog_emmc_firehose_8x10. mbn" from the Requirement - 1
6. Under "DOWLOAD", you will find "LOAD XML" and now click on that and a window will appear infront you :silly:
7. Now in the window, type *.xml in the file name so that the xml files will show up.
8. Now select "rm1013_2.1.0.12_059V787_001_rawprogram_unsparse_ui"
9. Soon another window will show up automatically and now type *.xml in the file name so that the xml files will show up.
10. Now select "P12026702dpi600_label_layout"
11. Now Click on the "DOWNLOAD" just button below the Load XML button.
- Make sure your device is connected to the PC/lappy through cable :silly:
Everything is done. Now sit back and Relax.
Your NOKIA X2 will bootup and it looks exactly like device when you purchased except the scratches and all
Note:
I'm not responsible if your device is bricked. Ofcourse if you are doing this, it means that your device might have already been bricked and i guess there is no other way except this to make it right
This works with all the snapdragon chipset devices.
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
frnsl3 said:
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
Click to expand...
Click to collapse
The only prob is OS which you are using and Drivers..
Thx, its helped me
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Kuttappan555 said:
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Click to expand...
Click to collapse
if you are saying that you cannot download from the link i provided.....i just checked it. Itz working fine. i saved it in my g-drive and shared the link
Hi, I tried this and everything worked fine but phone didn't boot up. I mean the flashing worked but phone did not reboot. Screenshot attached. Do you know what is missing?
Is this method still working?
Hard Bricked
Still Working??
Can someone re-upload these files or point to the right direction?

Lumia 950XL Prototype

I have a Lumia 950XL prototype I got recently, but it's stuck on version 10586.164
When looking for updates says it is up to date, already tried it (WDRT) even if you messed up the product code
unsuccessfully
Can someone help me? He has the boot unlocked
(WDRT Error) PACKAGE NOT AVAILABLE FOR THIS PHONE With the original product code
Firmware: 01078.00048.16135.36002
Original product code: 059W5J6
PROTO
you tried Interop Unlock and registry change?
https://forum.xda-developers.com/showpost.php?p=71937591&postcount=323
3.Go to the app bar, then choose x50 series unlock. You will receive an error about the acer service not running. That's ok for now. Click step 1 and it will tell you to install the acer system service and copy some files. To install the acer system service, use iutool [rs and newer builds,this version is essential,old versions will probably not work] (can be found here. thanks @Wack0Distractor ).
iutool install https://forum.xda-developers.com/showpost.php?p=68459157&postcount=13
run this command as administrator
iutool -v -p "path to the file acer.service.acersystemservice.spkg"
if you receive error 0x80070490, disconnect your phone from usb, go to control panel on your pc, devices and printers, find your windows phone and remove device. reconnect the usb to your phone,and after it reinstalls the drivers automatically, run iutool command above again.
if you receive error 0x8024a110, your phone should reboot to the gears UI in a minute. if not, run the command again. if it still doesnt auto reboot, manually reboot your phone. It should reboot into the gears UI, then back into the OS. if it still fails and doest show gears, give you phone a rest for 5-10 minutes and retry(usually needed after a new rom flash).
4.When you're back in the phone OS, copy newndtksvc.dll and ndtksvc.dll to your documents folder on your phone through USB
5.Go to the app bar, then choose x50 series unlock. You should no longer receive the error about the acer service. Now click step 2 and follow the rest of the instructions from the app.
6.If you've taken the silent extras/advanced+info update, or updated that app manually, be sure to choose the option "Restore NDTK 950/XL" in the "x50 series unlock" page and reboot to regain access to the elevated features. It basically means if it suddenly stops working, apply this setting.
Click to expand...
Click to collapse
now you only need change registry
older version of Interop Tools for 10586
https://forum.xda-developers.com/showpost.php?p=68982441&postcount=284
hi, can you boot in masstoragemode and dump few partitions?
before update, make full dump via win32diskimager
If you can have your phone recognized by PC in any mode, there's a spark of hope, but be warned that I take no responsibility for any damage that may occur (and it may occur since you are installing a software that's made for final products on a prototype):
I strongly recommend you to perform a full ROM backup if possible to be able to get back to this version if things go horribly wrong. If you can't do this, you may consider enrolling in Windows Insider program (which may allow you to get new builds), or perform a software RM Code change - most recommended- (check here: thewincentral.com/get-windows-10-mobile-redstone-on-older-lumias-using-an-app-now-uses-same-mod/)
You might not find a ROM corresponding exactly to that product code (because it's a prototype) on the internet, but you can download any Lumia 950 XL Firmware you'd like (check this: www . lumiafirmware.com/ser/RM-1085).
Once you've downloaded all firmware files, use the following tool to flash the firmware onto your device: androidmtk.com / use-windows-phone-image-designer-tool
(remove spaces from urls)

Leeco Le Pro 3 X727 bricked

Greetings everyone,
Two days ago my Leeco x727 was bricked, The phone is in a bootloop, can't enter recovery and only fastboot is working.
I successfully did all the steps on this thread and still can't boot the phone or enter recovery :
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
In the latest version of Qfil, under the tools menu there's an option called "get flash information", I put the phone in EDL mode and click that option and in the output I can see these messages :
11:27:20: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
11:27:20: INFO: TARGET SAID: 'GetStorageInfo Failed - Hotplug's storage_device_get_info() returned FALSE'
11:27:20: INFO: TARGET SAID: 'ERROR 14: Line 1271: HANDLE_STORAGE_INFO_FAILURE'
This means that the phone storage is damaged?
First, what steps did you take to get into the situation?
Second, if you followed the OP of the QFIL MODE]Unbrick your Le Pro3, tested and working page, its out of date. Always go to the end of the thread and read back a few pages. That First page has not been updated and its hosting a corrupt Qfil. If you were bricked you would want to use : le_zl1_qfil_ufs_fix.zip Which I posted on that that thread along with several extensive post with all of the instructions you would ever need to repair a brick.
However, you are do not have a bricked phone. You loaded the wrong version of Twrp and do not have a recovery...right? Whas the full name of the Twrp file that you flashed?
The fact that you can get to fastboot means that you are not bricked, you need to flash the correct Twrp and Root ( Try installing these first, then see if you can boot to recovery before doing anything else.
TWRP: https://dl.twrp.me/zl1/twrp-3.2.3-0-zl1.img.html
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still having trouble, Try the All in One tool, to flash Twrp and Root, you can use it to fully restore phone.
TOOL ALL IN ONE
If your device not recognized is a usb driver issue, and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
Easy Way to do this with one tool
You have encrypted you drive. The best way to resolve this is to start over.
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great and will unencrypt your drive.
After you install it, make sure to check for AIT updates.
Get it here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le...auronofrio-t3580611/post71627491#post71627491
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
___________________ ___________________ ___________________ ___________________
TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
* If the issue is related to drivers or software on the windows side, this should resolve it.
* Make your that you give it Firewall privileges, so you can ensure its up to date.
* Try another USB C cable if you still have an issue
Worst Case : You are actually Bricked: ( Highly Unlikely)
Use this Qfil: https://androidfilehost.com/?w=files&flid=244213
I was playing a game on the phone, then it froze up and after a few seconds it rebooted itself and entered in a bootloop, adb and twrp
didn't work and I was using official lineage 15.1 and the phone was rooted.
I did read all the thread until the end and I used the file le_zl1_qfil_ufs_fix.zip that you referenced, also after the procedure I flashed the latest twrp that I downloaded from this page https://dl.twrp.me/zl1/ but still can't enter TWRP.
I followed your instructions and used the option "erase all data/decrypt internal storage" in tool all in one and after that I repeated the QFIL process successfully but still the same situation.
What else can I do?
tsongming said:
First, what steps did you take to get into the situation?
Second, if you followed the OP of the QFIL MODE]Unbrick your Le Pro3, tested and working page, its out of date. Always go to the end of the thread and read back a few pages. That First page has not been updated and its hosting a corrupt Qfil. If you were bricked you would want to use : le_zl1_qfil_ufs_fix.zip Which I posted on that that thread along with several extensive post with all of the instructions you would ever need to repair a brick.
However, you are do not have a bricked phone. You loaded the wrong version of Twrp and do not have a recovery...right? Whas the full name of the Twrp file that you flashed?
The fact that you can get to fastboot means that you are not bricked, you need to flash the correct Twrp and Root ( Try installing these first, then see if you can boot to recovery before doing anything else.
TWRP: https://dl.twrp.me/zl1/twrp-3.2.3-0-zl1.img.html
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Still having trouble, Try the All in One tool, to flash Twrp and Root, you can use it to fully restore phone.
TOOL ALL IN ONE
If your device not recognized is a usb driver issue, and You will need to reinstall the Google USB driver, and while you are at it check to make sure adb is up to date.
Easy Way to do this with one tool
You have encrypted you drive. The best way to resolve this is to start over.
@mauronofrio built an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool is called: "TOOL ALL IN ONE"" and it's great and will unencrypt your drive.
After you install it, make sure to check for AIT updates.
Get it here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le...auronofrio-t3580611/post71627491#post71627491
XDA Main Page:*https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
___________________ ___________________ ___________________ ___________________
TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
* If the issue is related to drivers or software on the windows side, this should resolve it.
* Make your that you give it Firewall privileges, so you can ensure its up to date.
* Try another USB C cable if you still have an issue
Worst Case : You are actually Bricked: ( Highly Unlikely)
Use this Qfil: https://androidfilehost.com/?w=files&flid=244213
Click to expand...
Click to collapse
antarusch said:
I was playing a game on the phone, then it froze up and after a few seconds it rebooted itself and entered in a bootloop, adb and twrp
didn't work and I was using official lineage 15.1 and the phone was rooted.
I did read all the thread until the end and I used the file le_zl1_qfil_ufs_fix.zip that you referenced, also after the procedure I flashed the latest twrp that I downloaded from this page https://dl.twrp.me/zl1/ but still can't enter TWRP.
I followed your instructions and used the option "erase all data/decrypt internal storage" in tool all in one and after that I repeated the QFIL process successfully but still the same situation.
What else can I do?
Click to expand...
Click to collapse
This is an issue probably being caused by Windows - Try turning off signed driver enforcement, then start completely over.
https://ph.answers.acer.com/app/ans...windows-10:-disable-signed-driver-enforcement
I copied pasted my previous instructions to some else that had a similar issue.
If you are on Windows 10,*
you may need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files by removing some files.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
Enable developer mode :*https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com
The full setup option, on this page will download all drivers ( download only if needed) its a list of software for all supported Leeco phones, with alternate repair tools. Ensure that any software downloaded matches the specs of your device.
Hopefully, this finally resolve it for you. I created a comprehensive list of instructions for every scenario Please let me know what works for you so we can post a set of instructions to help others with the same issue.
Ok, I disabled signed driver enforcement, turned off windows defender and repeated the Qfil procedure.
The Qfil completed successfully without errors but still the same issue,
I read somewhere that some people had success with Qualcomm devices using the Miflash tool, I tried to use this tool but it ask for a file called "provision_hynix.xml", that file is inside the file le_zl1_qfil_ufs_fix.zip but when I opened it there's a disclaimer that says "WARNING: PROVISIONING UFS IS A IRRECOVERABLE ONE TIME OPERATION SO EXTREME CARE MUST BE TAKEN TO ENSURE THE PARAMETERS IN THIS CONFIGURATION FILE MEETS THE END PRODUCT" so I got afraid and didn't proceed further.
tsongming said:
This is an issue probably being caused by Windows - Try turning off signed driver enforcement, then start completely over.
https://ph.answers.acer.com/app/ans...windows-10:-disable-signed-driver-enforcement
I copied pasted my previous instructions to some else that had a similar issue.
If you are on Windows 10,*
you may need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files by removing some files.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
Enable developer mode :*https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com
The full setup option, on this page will download all drivers ( download only if needed) its a list of software for all supported Leeco phones, with alternate repair tools. Ensure that any software downloaded matches the specs of your device.
Hopefully, this finally resolve it for you. I created a comprehensive list of instructions for every scenario Please let me know what works for you so we can post a set of instructions to help others with the same issue.
Click to expand...
Click to collapse
antarusch said:
Ok, I disabled signed driver enforcement, turned off windows defender and repeated the Qfil procedure.
The Qfil completed successfully without errors but still the same issue,
I read somewhere that some people had success with Qualcomm devices using the Miflash tool, I tried to use this tool but it ask for a file called "provision_hynix.xml", that file is inside the file le_zl1_qfil_ufs_fix.zip but when I opened it there's a disclaimer that says "WARNING: PROVISIONING UFS IS A IRRECOVERABLE ONE TIME OPERATION SO EXTREME CARE MUST BE TAKEN TO ENSURE THE PARAMETERS IN THIS CONFIGURATION FILE MEETS THE END PRODUCT" so I got afraid and didn't proceed further.
Click to expand...
Click to collapse
I haven't used it, and I a not sure how USF memory is configured on the Le Pro 3. You could try using the QPST tool. I have not used it either but I have read that its great for difficult to repair bricks..
You did try the QPST
https://mytabletguru.com/how-to-flash-qualcomm-cpu/
Using this version for Snapdragon
https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
Try one one thing first, before QPST:
Try using using the Flash 2.0 program to the official stock rom preferable Leeco 5.8.26s get it here: https://drive.google.com/file/d/0BwRnZl5YW8NmbEtjX2dOSUExWlk/view
If all else fails :
Here is a general guide from the 4PDA website: https://4pda.ru/forum/index.php?showtopic=643084&st=275
Use will need to use Google Chrome with the Translate program installed.
The 4PDA link has a section that covers the general repair of UFS corruption.
Again, something that I haven't dealt with. I would use this a worst case scenario.
Have you tried switching usb c cables?
Have you tried an edl cable?
You can find them on Amazon for cheap.

Categories

Resources