Related
Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?
bryant_16 said:
Hi guys, I'm using Motorola Milestone and my bootloader is 90.78. I opened RSDLite and plug in the phone in bootloader mode but my RSDLite is unable to detect my device.
I have already installed the motorola drivers. Anyone has any ideas?
Click to expand...
Click to collapse
Same issue here. I have bootloader 90.74. On my Windows 7 there's no way...
Drivers 4.1 and 4.6 tested...but no way...
Anyone has any ideas about this issue?
Weird problem :s Works fine on my Win 7 VM. You could maybe try to uninstall and reinstall the driver :/
Some people have issues with RSDLite on Windows 7 64 bits.
I used to have the same problem and finally I had to install it on my netbook which has W7 32 bits and it worked fine.
Did you managed to install it in an other computer ?
The latest RSDLite versions didn't worked for either but version 4.5.3 works good under Windows 7 for me!
I found a solution
Like the rest, I too had the same problem. Then I found out how to make it work by accident.
I am using RSDlite version 4.5.7 on Windows 7 (32-bit version).
This is what you must do.
Step 1:
Download Open Recovery Version 1.46 for Milestone from http://www.modmymobile.com/forums/downloads.php?do=file&id=28089
Step 2:
It is a rar file, so use any free software to extract out the contents of this OpenRecovery_v1_46_SHOLS.rar file to a new folder on your desktop.
After u have extracted it, look for a file called vulnerable_recovery.sbf. Copy out this vulnerable_recovery.sbf file to somewhere on your pc for example to the root of your C drive on your PC.
Step 3:
Download from this script to disable the recovery check for signed recovery menu (so that we can apply update.zip later) from
http://modmymobile.com/forums/attac...le-recovery-disable_recovery_check_by_ota.zip.
Unzip the file and there should be a file called Disable_recovery_check_by_OTA.sh
Step 4:
Copy the Disable_recovery_check_by_OTA.sh file to a sub folder called scripts that is within the OpenRecovery folder (which we have already extracted earlier) (eg. OpenRecovery\scripts).
Step 5:
Boot up the phone as per normal and then connect the phone to PC via USB cable
Step 6:
Change the USB Connection to Memory Card Accessl
Step 7:
Go to the desktop of your PC and open up the folder where the contents of the extracted OpenRecovery_v1_46_SHOLS.rar file is. You should then copy the update.zip to the root of your phone's SD card (eg. SDcard\update.zip).
Also copy the whole OpenRecovery folder also to the root level of your SD card (eg. SDcard\OpenRecovery)
Step 8:
Change the USB Connection to Portal & Tool. This is the trick that will allow RSDLite to detect your phone.
Step 9:
Launch RSDLite ver.4.5.7
Step 10:
It will take a few seconds for your phone to appear in the device list of RSDLite
Step 11:
Click on the "..." button and locate and open the vulnerable_recovery.sbf file which we have extracted earlier and had copied out to somewhere (eg. root of C drive).
Step 12:
Click on the "Start" button.
Step 13:
Immediately you would see something in the status progress of RSDlite. RSDlite will switch your phone to the Bootloader mode by itself.
Step 14: - Very Important Step
Pay attention to the status of the Bootloader on your phone. Halfway thru the progress of flashing the vulnerable_recovery.sbf, RSDlite will initiate a reboot of your phone.
When that happens, you must prevent the phone from rebooting into the normal Android mode and get it to boot into the Bootloader mode by quickly pressing & holding up on your D-pad in horizontal (landscape) position.
I would suggest that b4 RSDlite initiate the reboot, you should be prepared for it by sliding out the keyboard first and hold it in the horizontal (landscape) position and get ready to press up on the D-Pad.
by quickly turning your phone to the horizontal position (landscape) and press and hold up on the D-Pad of your phone. Hold the up key of your D-pad for about 3 to 4 seconds before release it and it should be now back in the bootloader mode.
Do not do anything yet. You will know when the flashing of the vulnerable_recovery.sbf is completed and successful when the result in RSDLite device list window says "PASS".
Step 15: - Also very important step
Once the flashing of the vulnerable_recovery.sbf is complete (after you see "PASS" in RSDlite), you may close RSDlite and then unplug the phone from the USB cable.
The phone is still in the bootloader mode. Now be prepared to boot into the recovery mode. This is very important. If you fail to boot into the recovery mode then you will have to repeat from Step 8
The technique that I use on my Motorola Milestone to boot into the recovery mode is by using the 3 button technique. I press the "x" key + power button + camera button together at the same time and hold it until the recovery mode icon appears which is a an exclamation mark within a triangle.
Step 16:
While in the recovery mode, slide the keyboard back in. Then press and hold the volume up button first and then press the camera button once and when you see the recovery menu you can quickly release the volume up button.
Step 17:
Slide the keyboard out. Use the D-pad to navigate. If you are holding the phone in vertical position, then to navigate up and down the recovery menu, just press up or down on the D-pad. To confirm your selection, press down on the middle of your D-Pad.
Using your D-Pad, scroll down to the part it says "apply sdcard:update.zip" and press the middle of your D-Pad to select it.
You should see something packages being downloaded to your phone which is part of the installation process of the Motorola Milestone Open Recovery Menu which is not the stock Recovery Menu.
Step 18:
Once you are in the Motorola Milestone Open Recovery Menu, scroll down to the option that says "Run Script". Select that option.
Step 19:
Then you should be able to see a list of scripts and one of them should be "Disable_recovery_check_by_OTA.sh". Select that script.
Step 20:
Once that "Disable_recovery_check_by_OTA.sh" has been applied, the phone will no longer check for signed recovery menus like this Motorola Milestone Open Recovery Menu when ever you go into the stock recovery menu to "apply sdcard:update.zip". This means you can install different types of "Open Recovery Menu" for different custom roms for Motorola Milestone.
Besides using this Motorola Milestone Open Recovery Menu, I have also tried the following 2 "Open Recovery Menu" on my Milestone:
1) Androidiani OpenRecovery 3.3 - http://forum.xda-developers.com/showthread.php?t=796679
2) G.O.T OpenRecovery (for installing G.O.T custom FROYO rom) - http://groupoften.wordpress.com/g-o-t-s-openrecovery/
Important Note:
Before you start to install custom roms please do a Nandroid back up of your phone in case something goes wrong during the installation of the custom rom, you can restore your phone back to stock rom.
The Nandroid back up and restore option is available within all 3 "Open Recovery Menu" mentioned above.
I have Windows 7 Ultimate 64-bit and I use Motorola USB Drivers 4.7.1 and RSD Lite 4.9. So it would be good to download these versions, which are the latest. If this wont work, do a factory reset on your Milestone.
Ok this is taken from the HTC SPAIN site (Im only translating it)
1.- Download both files at the bottom:
2.-You will need to install the OMAP4430 drivers (they are inside the file you just download)
a) open device manager
b) Connect the phone to usb with out the battery,
c) you will see "omap4430 device" appearing and disappearing
d) as soon as you see it right click on it and chose proprieties
e) click on the drivers tab and select update driver
f) select the driver on the folder "usb_drv_windows" from the file you downloaded and install them
g) wait till it finish installing them
[Edited by pete3000 to make the process more understandable]
3.- now run the file "Instalar Recovery ICS Europeo.bat" then:
a) Connect the USB cable from the phone to the PC without the battery
b) Wait until the message "Wait 5-Seconds...", then put the battery in.
c) Wait until installation is complete and you see the green screen and the message.
------------------------------
Installed recovery!
Please remove the USB cable
------------------------------
d)Now you can disconnect the cable USB, remove the battery, return the battery, and boot the phone.
4.- Copy the "Su_Bbox_1.20.2_gazhead_signed.zip" file to memory (either internal or external SD card) and install it with in CWM
5. to boot into Clockwork Mod, shut the phone down all the way
a) hold down the 3D button, the VOL DOWN and POWER at the same time. (some say hit vol up but this didn't work for me)
b) when the backlight comes on the screen, let go of the power and vol DOWN ONLY, keeping the 3D held down until you see the clockworkmod touch interface come up.
c) choose install zip from sdcard
find the Su_Bbox_1.20.2_gazhead_signed.zip file using the vol + and - keys.. then scroll downpast the No's to the YES and tap it on the screen.
And you will have a rooted ISC V30B
Enjoy!
http://www.htcspain.com/links.php?u...om/?http://www.mediafire.com/?t2tz6xp7zfwqldo
http://www.htcspain.com/links.php?u...om/?http://www.mediafire.com/?5io5b2r98nt28bb
i followed this quide but now when i boot up i have greyd in lg logo is there a way to get rid of this or?
I wish this was as easy as you make it sound. When i plug my phone into the computer with no battery in, device manager takes 5 seconds or so to load the devices again, and by that time, there is no omap option to select. Is the omap driver messed up, maybe we could modify it to work without the device manager work around
Sent from my LG-P925 using xda app-developers app
got it working but would have liked to see it in english
Finally got it to work!
Notes that should be added. Before Step 3, Take the "leeme.txt" file and throw it into Bing Translate you will see this (rearranged/edited to help from the sequence above):
3.- now run the file "Instalar Recovery ICS Europeo.bat" then:
a) Connect the USB cable from the phone to the PC without the battery
b) Wait until the message "Wait 5-Seconds...", then put the battery in.
c) Wait until installation is complete and you see the green screen and the message.
------------------------------
Installed recovery!
Please remove the USB cable
------------------------------
d)Now you can disconnect the cable USB, remove the battery, return the battery, and boot the phone.
4.- Copy the "Su_Bbox_1.20.2_gazhead_signed.zip" file to memory (either internal or external SD card) and install it with in CWM
5. to boot into Clockwork Mod, shut the phone down all the way
a) hold down the 3D button, the VOL DOWN and POWER at the same time. (some say hit vol up but this didn't work for me)
b) when the backlight comes on the screen, let go of the power and vol DOWN ONLY, keeping the 3D held down until you see the clockworkmod touch interface come up.
c) choose install zip from sdcard
find the Su_Bbox_1.20.2_gazhead_signed.zip file using the vol + and - keys.. then scroll downpast the No's to the YES and tap it on the screen.
pete3000 said:
Finally got it to work!
Notes that should be added. Before Step 3, Take the "leeme.txt" file and throw it into Bing Translate you will see this (rearranged/edited to help from the sequence above):
3.- now run the file "Instalar Recovery ICS Europeo.bat" then:
a) Connect the USB cable from the phone to the PC without the battery
b) Wait until the message "Wait 5-Seconds...", then put the battery in.
c) Wait until installation is complete and you see the green screen and the message.
------------------------------
Installed recovery!
Please remove the USB cable
------------------------------
d)Now you can disconnect the cable USB, remove the battery, return the battery, and boot the phone.
4.- Copy the "Su_Bbox_1.20.2_gazhead_signed.zip" file to memory (either internal or external SD card) and install it with in CWM
5. to boot into Clockwork Mod, shut the phone down all the way
a) hold down the 3D button, the VOL DOWN and POWER at the same time. (some say hit vol up but this didn't work for me)
b) when the backlight comes on the screen, let go of the power and vol DOWN ONLY, keeping the 3D held down until you see the clockworkmod touch interface come up.
c) choose install zip from sdcard
find the Su_Bbox_1.20.2_gazhead_signed.zip file using the vol + and - keys.. then scroll downpast the No's to the YES and tap it on the screen.
Click to expand...
Click to collapse
did you need to have the normal lg drivers installed also, mine stays at the grey lg logo, and the pc seem to be finding all the other device that need drivers.
Omap4boot stays at a blue screen " waiting for device "never turns green, does it normally complete everything at the grey lg logo?
---------- Post added at 12:24 AM ---------- Previous post was at 12:02 AM ----------
ok got it working there was a 2nd device in device manager i had to manually direct to the same driver folder....
Again, it would have been easier if the BAT file was written in English. maybe some dev on here can update it. I would also like to see them use the adb capabilities and install the su, so you dont have to go into CWM to install it.
Now we need an update to WIFI Tether, unless someone finds a successful combination in the program for setting it up. it had settings for the thrill 4g running froyo and gingerbread.
Thanks all this worked great. I'm also looking for a tehering hotspot fix.
ROOT LG THRILL ICS P92530b AT&T
3.- now run the file "Instalar Recovery ICS Europeo.bat" then:
a) Connect the USB cable from the phone to the PC without the battery
b) Wait until the message "Wait 5-Seconds...", then put the battery in.
c) if it won't boot up select the driver on the folder "usb_drv_windows" from the file you downloaded and install them again
d) Wait until installation is complete and you see the green screen and the message.
------------------------------
Installed recovery!
Please remove the USB cable
!! IMPORTANT!! be careful using ROM MANAGER with rooting your phone w/this method
The Clockworkmod recovery this bat file uses is a little bit old and has a "reboot" bug. To avoid it, Do not install the ROM MANAGER on google play and immediately boot to the CWM. ROM MANAGER sets a trigger that keeps rebooting into the old CWM and never back to the regular OS. It's officially called the Clockworkmod reboot loop
To fix this, I used this tool which launches a .BAT file http://forum.xda-developers.com/showthread.php?t=2144738 similar to the one you rooted with above. you will need to update the clockwork mode to version 6.0.1.9 (option 5). i also flashed the ICS boot loaders too (option 8).
when i rebooted the phone a new version of CWM showed up and all i had to do was reboot thru CWM. And i was back to the at&t boot screen.
pete3000 said:
The Clockworkmod recovery this bat file uses is a little bit old and has a "reboot" bug. To avoid it, Do not install the ROM MANAGER on google play and immediately boot to the CWM. ROM MANAGER sets a trigger that keeps rebooting into the old CWM and never back to the regular OS. It's officially called the Clockworkmod reboot loop
To fix this, I used this tool which launches a .BAT file http://forum.xda-developers.com/showthread.php?t=2144738 similar to the one you rooted with above. you will need to update the clockwork mode to version 6.0.1.9 (option 5). i also flashed the ICS boot loaders too (option 8).
when i rebooted the phone a new version of CWM showed up and all i had to do was reboot thru CWM. And i was back to the at&t boot screen.
Click to expand...
Click to collapse
So are you running ICS or GB? Option 5 is for GB. Just double checking before I follow your lead.
Nevermind... I did the update with ICS and it worked fine. The only difference I see is you will need to hold down the power button and vol down longer when you boot it into CWM. If you release the power button and vol down button as soon as you see the back light it shuts down instead of boot.
I made an attempt to edit the settings.db , hoping to regain my hotspot functionality.. No luck the phone hung during boot. So I decide to factory reset it. Now there is no entitlement entries in the settings.db. The file is much smaller. I'm guessing the carrier has moved the wifi entitlement to another db.
i found a wifi tether post for ICS in the O3D area, but it didnt work either..
i saw this http://forum.xda-developers.com/showthread.php?t=2181555 but his settings didn't work. I hope someone can help us with it soon. i filed a bug report to the actual wifi router site.
I got hotspot working. I'll send details after I get home this evening.
ICS Rooted LG Thrill AT&T Tethering
I put the instruction on the tethering thread.
http://forum.xda-developers.com/showthread.php?p=39824110#post39824110
Can i use this tool with a stock ICS Rom?
pete3000 said:
The Clockworkmod recovery this bat file uses is a little bit old and has a "reboot" bug. To avoid it, Do not install the ROM MANAGER on google play and immediately boot to the CWM. ROM MANAGER sets a trigger that keeps rebooting into the old CWM and never back to the regular OS. It's officially called the Clockworkmod reboot loop
To fix this, I used this tool which launches a .BAT file http://forum.xda-developers.com/showthread.php?t=2144738 similar to the one you rooted with above. you will need to update the clockwork mode to version 6.0.1.9 (option 5). i also flashed the ICS boot loaders too (option 8).
when i rebooted the phone a new version of CWM showed up and all i had to do was reboot thru CWM. And i was back to the at&t boot screen.
Click to expand...
Click to collapse
Hi Pete. Personally i had a problem with the easy form of rooting the stock ICS, because i got the clockwork mod loop when i tried to go back into a factory reset.
Can i Use your method with a stock ICS in my thrill?
Another question is, Have any body fix the movie player missed function in ICS? because in GB i can play any 3D movie, whatever the format and can change it.
Thanks for your time
yes. I used it with stock ICS from AT&T/LG.
for 3D movies, open the movie in the stock player. you will see a side by side version of the movie. Hit the 3D button then hit the the settings button to choose side-by-side.
hotdog32836 said:
I wish this was as easy as you make it sound. When i plug my phone into the computer with no battery in, device manager takes 5 seconds or so to load the devices again, and by that time, there is no omap option to select. Is the omap driver messed up, maybe we could modify it to work without the device manager work around
Sent from my LG-P925 using xda app-developers app
Click to expand...
Click to collapse
Please hold Vol - while you're plugging the phone in, hold it down whilst you are in Device Manager, something should pop up stating OMAP-344 Or whatever the number shows up as.
Sent from my HTC One VX using xda app-developers app
Help?
My phone rebooted after updating with the folder. Still no green message.
there are too many reply's. which issue were you having problems with.
First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).
C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.
D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.
E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.
F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).
Great tutorial, but I did not get 4g in any of the roms, only 3g
Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration
Hello everyone,
I've bought my phone second hand and the sellor didn't tell me the bootloader was unlocked... I feel screwed, I can't take any pictures.
From what I've learned with some search, I need to get the drm keys back, with this software XperiFix. Does the latest version work with my build? I see nowhere if it's compatible or not, and I don't have 20€ to lose...
Thanks for your time
PoloB49 said:
Hello everyone,
I've bought my phone second hand and the sellor didn't tell me the bootloader was unlocked... I feel screwed, I can't take any pictures.
From what I've learned with some search, I need to get the drm keys back, with this software XperiFix. Does the latest version work with my build? I see nowhere if it's compatible or not, and I don't have 20€ to lose...
Thanks for your time
Click to expand...
Click to collapse
Sony have become wise to Xperiafix and if you use an old vesrion on new firmware it'll bork your phone. I know you want the 'free' version, but seriously, is peace of mind worth $20. Pay it once and you'll get fix updates for forever.
sToRm// is still in development with his fix and I'm pretty sure he supports all the latest builds. The 3.1 version I used connects online to get the latest TWRP and fix versions.
Drop him a line on his support page at and ask him.
Didgesteve said:
Sony have become wise to Xperiafix and if you use an old vesrion on new firmware it'll bork your phone. I know you want the 'free' version, but seriously, is peace of mind worth $20. Pay it once and you'll get fix updates for forever.
sToRm// is still in development with his fix and I'm pretty sure he supports all the latest builds. The 3.1 version I used connects online to get the latest TWRP and fix versions.
Drop him a line on his support page at Xperiafix and ask him.
Click to expand...
Click to collapse
Thanks, I want to buy the soft, I meant that I want to be sure it'll work if I buy it because I can't afford to spend 20€ for nothing.
I've seen him replying to someone with the same question
Where he says "It does! You have to use the manual mode in XperiFIX and select the related TWRP and Magisk, then start the fix."
But honestly I have no idea what that means and I'm a huge noob, without any guide with pictures I won't be able to do anything...
Bonus question : Is there a way to make mobile payment work again or did I lose that forever?
Thanks
Omg are you really pay for free drmfix :laugh:
What's wrong with you.
This is latest twrp from @modpunk only this man make it for our phone https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
This is latest firmware with drmfix, deodexed, superusermod and other. You can find fix for xposed of you use it.
https://forum.xda-developers.com/xperia-xz1-compact/how-to/fulldeodex12-75-t3750620
Deleted
Didgesteve said:
Sony have become wise to Xperiafix and if you use an old vesrion on new firmware it'll bork your phone. I know you want the 'free' version, but seriously, is peace of mind worth $20. Pay it once and you'll get fix updates for forever.
sToRm// is still in development with his fix and I'm pretty sure he supports all the latest builds. The 3.1 version I used connects online to get the latest TWRP and fix versions.
Drop him a line on his support page at and ask him.
Click to expand...
Click to collapse
russel5 said:
Omg are you really pay for free drmfix :laugh:
What's wrong with you.
This is latest twrp from @modpunk only this man make it for our phone https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
This is latest firmware with drmfix, deodexed, superusermod and other. You can find fix for xposed of you use it.
https://forum.xda-developers.com/xperia-xz1-compact/how-to/fulldeodex12-75-t3750620
Click to expand...
Click to collapse
I would like to get the phone as stock as possible. Do the links you provided allow me to use mobile payment applications?
I'm sorry I'm a noob and I have no idea what to do to get the phone as close as possible as brand new
You have unlocked bootloader, payments won't work without magisk
russel5 said:
You have unlocked bootloader, payments won't work without magisk
Click to expand...
Click to collapse
So that means it's possible to make it work? Very nice.
Let's say I've found 3.1 xiperifix for free, but it doesn't detect my phone (blue led, sony drivers installed) and I have nothing as such as "manual mode". Do you know why?
I haven't flashed anything yet, do I need to flash TWRP? How/when do I install Magisk? Can you please be explicit in what to do, if you have time of course. Thank you!
1. Download flashtool
2. Open Flashtool install latest available software which ends "20" via Xperifirm which is inside of Flashtool
3. Press vol down key and insert usb-c cable to your computer
4. if you see green notification light then your device is ready to flash
5. After flashing is done you need next step
6. pull cable out and press vol up key and insert cable
7. now if you see a blue light your ready to flash twrp recovery
8. Download twrp recovery name it twrp.img and copy it to "C:/adb" folder
9. install adb & fastboot installer from xda "look google" and get fastboot drivers ready
10. open cmd, write " cd C:/adb" write "fastboot devices" if you see your device in the list then your ready to flash twrp
11. flash twrp "fastboot flash recovery twrp.img"
12. pull cable out
13. download tweaked and drm fix included kernel from development forum
14. press vol down and power on your device (cable not plugged in)
15. in twrp recovery format your internal storage and boot againt to twrp
16. now you're able to copy downloaded kernel to your storage
17. copy 3 zip files inside of "Patching-Magisk-Module-Permissive.zip" to your phone storage but dont flash anything yet
18. Turn off the device. Press vol up key and insert cable. blue notification light there then you are ready to flash kernel
19. extract from Kernel "Xperia XZ1 Compact (G8441).zip" and open Flash-boot.bat
20. when thats done, unplug cable, press vol down and power key, after display shows something release power key
21. booted into twrp now flash 2-Patching.zip and 3-Magisk.zip then boot your phone.
22. open magisk manager and go to "Modules" and press "+" key under the modules list and choose 4-kernel_permissive.zip after it is done reboot your phone and you should be fine.
proxuser said:
1. Download flashtool
2. Open Flashtool install latest available software which ends "20" via Xperifirm which is inside of Flashtool
3. Press vol down key and insert usb-c cable to your computer
4. if you see green notification light then your device is ready to flash
5. After flashing is done you need next step
6. pull cable out and press vol up key and insert cable
7. now if you see a blue light your ready to flash twrp recovery
8. Download twrp recovery name it twrp.img and copy it to "C:/adb" folder
9. install adb & fastboot installer from xda "look google" and get fastboot drivers ready
10. open cmd, write " cd C:/adb" write "fastboot devices" if you see your device in the list then your ready to flash twrp
11. flash twrp "fastboot flash recovery twrp.img"
12. pull cable out
13. download tweaked and drm fix included kernel from development forum
14. press vol down and power on your device (cable not plugged in)
15. in twrp recovery format your internal storage and boot againt to twrp
16. now you're able to copy downloaded kernel to your storage
17. copy 3 zip files inside of "Patching-Magisk-Module-Permissive.zip" to your phone storage but dont flash anything yet
18. Turn off the device. Press vol up key and insert cable. blue notification light there then you are ready to flash kernel
19. extract from Kernel "Xperia XZ1 Compact (G8441).zip" and open Flash-boot.bat
20. when thats done, unplug cable, press vol down and power key, after display shows something release power key
21. booted into twrp now flash 2-Patching.zip and 3-Magisk.zip then boot your phone.
22. open magisk manager and go to "Modules" and press "+" key under the modules list and choose 4-kernel_permissive.zip after it is done reboot your phone and you should be fine.
Click to expand...
Click to collapse
Thank you so much for your time and dedication for a random dude online, I'm gonna try that as soon as I get access to my computer
proxuser said:
1. Download flashtool
2. Open Flashtool install latest available software which ends "20" via Xperifirm which is inside of Flashtool
3. Press vol down key and insert usb-c cable to your computer
4. if you see green notification light then your device is ready to flash
5. After flashing is done you need next step
6. pull cable out and press vol up key and insert cable
7. now if you see a blue light your ready to flash twrp recovery
8. Download twrp recovery name it twrp.img and copy it to "C:/adb" folder
9. install adb & fastboot installer from xda "look google" and get fastboot drivers ready
10. open cmd, write " cd C:/adb" write "fastboot devices" if you see your device in the list then your ready to flash twrp
11. flash twrp "fastboot flash recovery twrp.img"
12. pull cable out
13. download tweaked and drm fix included kernel from development forum
14. press vol down and power on your device (cable not plugged in)
15. in twrp recovery format your internal storage and boot againt to twrp
16. now you're able to copy downloaded kernel to your storage
17. copy 3 zip files inside of "Patching-Magisk-Module-Permissive.zip" to your phone storage but dont flash anything yet
18. Turn off the device. Press vol up key and insert cable. blue notification light there then you are ready to flash kernel
19. extract from Kernel "Xperia XZ1 Compact (G8441).zip" and open Flash-boot.bat
20. when thats done, unplug cable, press vol down and power key, after display shows something release power key
21. booted into twrp now flash 2-Patching.zip and 3-Magisk.zip then boot your phone.
22. open magisk manager and go to "Modules" and press "+" key under the modules list and choose 4-kernel_permissive.zip after it is done reboot your phone and you should be fine.
Click to expand...
Click to collapse
I've done steps 1 to 9 but adb fastboot devices doesn't detect my phone... The led is blue
PoloB49 said:
I've done steps 1 to 9 but adb fastboot devices doesn't detect my phone... The led is blue
Click to expand...
Click to collapse
You need atleast the two following Drivers from Flashtool Driver Setup:
Raz0Rfail said:
You need atleast the two following Drivers from Flashtool Driver Setup:
Click to expand...
Click to collapse
I can't seem to find the software you've captured. Only v1.8 not v1.9. Would the 1.8 work though?
For now I have installed 3 drivers :
The 15 seconds installer https://forum.xda-developers.com/showthread.php?t=2588979
The google driver from android studio
The official sony driver https://developer.sony.com/develop/drivers/
I have also disabled the Windows 10 thing regarding drivers about signature enforcement
Also I'm using USB 2.0
PoloB49 said:
I can't seem to find the software you've captured. Only v1.8 not v1.9. Would the 1.8 work though?
For now I have installed 3 drivers :
The 15 seconds installer https://forum.xda-developers.com/showthread.php?t=2588979
The google driver from android studio
The official sony driver https://developer.sony.com/develop/drivers/
I have also disabled the Windows 10 thing regarding drivers about signature enforcement
Also I'm using USB 2.0
Click to expand...
Click to collapse
You need FlashTool:
http://www.flashtool.net/downloads.php
I uploaded the driver package, so you don't have to download the entire package:
https://www6.zippyshare.com/v/lNT3x7mv/file.html
You should install the usb driver for xz1C:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If you have windows 8 or newer you have to boot into unsigned driver install mode:
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
If you start the installer, select the two drivers and then click on install.
You will see a new driver install window. Don't click on next.
Move into the following folder %temp%/flashtool and copy your xz1c driver into it.
Now move back to the driver install click on next and click trough the unsigned error messages.
After that you have installed the needed drivers and you can go further with fastboot mode.
Raz0Rfail said:
You need FlashTool:
http://www.flashtool.net/downloads.php
I uploaded the driver package, so you don't have to download the entire package:
https://www6.zippyshare.com/v/lNT3x7mv/file.html
You should install the usb driver for xz1C:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If you have windows 8 or newer you have to boot into unsigned driver install mode:
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
If you start the installer, select the two drivers and then click on install.
You will see a new driver install window. Don't click on next.
Move into the following folder %temp%/flashtool and copy your xz1c driver into it.
Now move back to the driver install click on next and click trough the unsigned error messages.
After that you have installed the needed drivers and you can go further with fastboot mode.
Click to expand...
Click to collapse
Thank you! That worked. I'm going to go further with the steps now
Edit : I'm not able to put any data into the phone (windows explorer freezes) and I can't use adb push because my device is not found
Fastboot devices finds my phone, but adb devices doesn't
deleted
PoloB49 said:
Thank you! That worked. I'm going to go further with the steps now
Edit : I'm not able to put any data into the phone (windows explorer freezes) and I can't use adb push because my device is not found
Fastboot devices finds my phone, but adb devices doesn't
Click to expand...
Click to collapse
you need to go twrp recovery and format data not wipe data & cache, format data will ask you to type "yes" after that reboot twrp again and now you can move files to twrp.
---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------
boot in to twrp recovery and go to "Wipe" then "Format Data" then type yes and after that is done, reboot again to twrp and you can now copy files to device.
Alright so I did everything, flashed everything said in the 22 steps, and I can take pictures but still can't pay with my mobile. I got an error message from PayLib because I am root or I have an application that allows root or something
I think I'll live without mobile payment... That's a shame but well, that's what I got for not checking properly a second hand device.
Quick and last question : Can I reset the phone in the settings without losing anything I've just done? Or will I lose the different zip flash I did? I want to be able to sell my phone without screwing the next buyer
Also, thanks everyone for you time and patience with me! You were amazing
PoloB49 said:
I think I'll live without mobile payment... That's a shame but well, that's what I got for not checking properly a second hand device.
Quick and last question : Can I reset the phone in the settings without losing anything I've just done? Or will I lose the different zip flash I did? I want to be able to sell my phone without screwing the next buyer
Also, thanks everyone for you time and patience with me! You were amazing
Click to expand...
Click to collapse
if you tell next buyer about activate the (4. zip file) a module in magisk, you can wipe your data. just remove your google account before sell because even rooted wiped phones asks previous owners account to login.
just because of drm keys for camera get wiped, i will also not sell my xz1 compact and use it as long it works.
If you are having trouble with the google play store "Rom manager" app installing CWM recovery on your L3 then hopefully following this guide will help you.
Around 2019 the servers for the rom manager app were still working for the l3, I know this because I actually installed CWM on my l3 that year without issues concerning the server connections. After 2019 though I think that the servers got shut down at least for the l3. I remember vaguely that in 2020 I tried the app and couldn't get it to work to install CWM. The method that I will describe below includes a CWM img that was backed up when I needed to restore my phone back in 2019. Idk though, I might be wrong about the whole thing and you can still use the app.
This should also work if you aren't rooted and this guide assumes that you are on stock.
Prerequisites:
Make sure that your phone is charged and you have a usb cable.
--------
Installing CWM recovery for LG l3
1. Download and install the LG drivers for this phone here (drive link). If you already have drivers for this phone then skip this step.
2. Download Android AIO Flasher here (XDA post)
3. Download the CWM img file here (drive link)
4. Connect up phone to the PC using the USB cable.
4. Enable USB debugging on your phone. This can be done by opening:
Settings --> Applications --> Development --> USB debugging
5. Extract and open up the Android AIO flasher tool and click on the dropdown menu in the center that says "Reboot Menu".
6. Select "Fastboot mode' under the dropdown menu and click on "Reboot".
7. The phone should now boot into Fastboot mode. The fastboot screen should have a bunch of white text on black background.
8. In the Android AIO Flasher tool, select "Recovery" under the "Fastboot flasher" section at the top left of the screen.
9. Click on "Select file" under the "Fastboot flasher section and find the CWM recovery file that you downloaded earlier. Select the file and click "Open".
10. Finally, click on the big "Flash" button in the Fastboot flasher section. Everything is good once the box at the bottom of the tool says "OKAY xxx sec".
11. Unplug your phone and take out the battery (don't worry this won't harm anything in my personal experience).
You are now done installing!
Booting into CWM recovery
1. Turn off device
2. Hold buttons:
Home - Volume up - Power
3. Once the phone vibrates, release all buttons. Your L3 should now boot into CWM recovery
--------------
Note: If you know the commands for the adb fastboot command line then you can use that rather than using the AIO tool
Please tell me if there is anything that I could improve with the guide
Credits:
fonehacker (for tool) profile link
its just stuck ran it for 15m
C:\Users\admin\Downloads\Android_AIO_Flasher\tools>fastboot flash recovery "C:\Users\admin\Downloads\recovery (LG L3) (CWM 5.8.4.5).img"