This thread contains images made by ME personally with TWRP in various stages of installation (stock, root, root with permanent TWRP), and therefore is Android Development.
It also contains publicly released Motorola KitKat 4.4.4 and Lollipop 5.0.2 factory images, not subject to any confidentiality agreement, which are useful for people to flash to upgrade to Lollipop from KitKat or to convert a Moto Maxx XT1225 (Latin America) to Moto Turbo XT1225 (India). Why would you want to do that? Well, same exact hardware, same exact FCC ID, just a different model name for different market. In the Moto Turbo XT1225 , Motorola finally officially admits some bands which are also enabled in the Moto Maxx -- but which they did not list in the official specs for the Moto Maxx (even though they are there.) This is helpful to owners/prospective buyers in U.S. and Canada especially for LTE band 5 (used by AT&T in the U.S. and other carriers in Canada) and HSPA band 4 (used by T-mobile and other carriers in Canada). These bands are there in all the XT1225 images, but only OFFICIALLY listed in the Moto Turbo XT1225.
NOTE: the MediaFire mirror links seem to work better than the OneDrive links. Also have some Google Drive links.
________________
New Brazil Moto Maxx 5.0.2 factory image at bottom of post next to the India Moto Turbo 5.0.2 -- with MediaFire and Google Drive links. Scroll down!
The downloads in this post are divided into two sections:
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
You need TWRP to flash these. You can use a temporary installation of TWRP (one time, one off) if you do not wish to permanently install TWRP. Instruction in the post below
2) Straight Factory Images which you need RSD Lite to flash
These are
Puerto Rico 4.4.4
India 5.0.2
Brazil 5.0.2
They are under the "Non-TWRP" heading towards the bottom of the post.
For these, you will need RSDLite 6.2.4, found here:
https://www.dropbox.com/s/wnxtofd1hwxvokj/RSDLite 6.2.4 (1).zip?dl=0
OR you can unzip the image and use @Jaocagomez excellent instructions in this thread to flash all sections of the image using mfastboot.
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
__________________
I have two Moto Maxx (XT1225) phones, one from Mexico and one from Puerto Rico. This is the international version of the Droid Turbo (XT1254). They have identical hardware, but the XT1225 has unlockable bootloader, has root and we have TWRP recovery.
Assigned FCC ID IHDT56PK2, when it passed through the FCC. All phones sold in USA or U.S. territories need FCC certification. This phone is being sold in Puerto Rico, which is a U.S. territory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All Moto Maxx phones sold in Brazil, Mexico, Puerto Rico and Chile have this same FCC number. Therefore, all the Moto Maxx phones have identical hardware.
I made some TWRP backups on both my Mexico and Puerto Rico Moto Maxx phones in various states, so people can flash back to them while testing development on their phones. I posted these images elsewhere, over in a root thread, but I see people are posting images here also. Hope this helps someone.
________________________________
MOTO MAXX IMAGES (XT1225) - MEXICO
SYSTEM VERSION: 21.11.9.quark_retla.retla.en.01 retla
BASEBAND VERSION: MDM9625_104335.118.0254R, QUARK_SINGLELA_CUST
Flashed @respider new bootbin logo to remove the annoying warning on the unlocked Moto Maxx. Go there and thank him, please. It's awesome.
[Moto Maxx] Remove unlocked bootloader Warning
Here we go...
________________
TWRP BACKUPS!
________________
______________________________________________________________
1) Booted to ADB, booted TWRP using one-time method. Made a back-up.
MOTO_MAXX_XT1225_MEXICO_FACTORY_IMAGE
MIRROR: http://www.mediafire.com/download/nro3q9vdveb7k0z/MOTO_MAXX_XT1225_MEXICO_FACTORY_IMAGE.zip
This is pure Mexican Moto Maxx XT1225 Factory Image -- unrooted, no TWRP residing in recovery.
______________________________________________________________
2) Booted to ADB, booted TWRP using one-time method. Flashed SuperSU to root, made a back-up.
MOTO_MAXX_XT1225_MEXICO_FACTORY_IMAGE_ROOTED
MIRROR: http://www.mediafire.com/download/6...X_XT1225_MEXICO_FACTORY_IMAGE_ROOTED_TWRP.zip
This is Mexican Moto Maxx XT1225 Factory Image, rooted -- but no TWRP residing in recovery.
Rooting does NOT affect the ability to recieve OTA updates (like 5.0 Lollipop). Rooting just lets you removed apps you don't like, make changes, run apps like Titanium Backup, Root Browser, Xposed framework, Gravity Box, etc.
(On my daily phone, I'm running 4.4.4 from factory, but rooted and I have Gravity Box with lots of custom ROM features and I'm even running a Lollipop theme using Xthemes, which is an Xposed app. Can't do that without root.)
______________________________________________________________
3) Booted to ADB, flashed TWRP using permanent method. Already rooted, made a backup.
MOTO_MAXX_XT1225_MEXICO_FACTORY_IMAGE_ROOTED_TWRP
MIRROR: http://www.mediafire.com/download/kmn4dx68lu7y3p1/Moto-Maxx-XT1225-rooted-PR-image.zip
This is Mexican Moto Max XT1225 Factory Image, rooted with TWRP residing in recovery.
Having permanent TWRP lets you boot to recovery using the power menu (like in Gravity Box). You can easily flash zipped apps, make backups, restore backups, fix permissions, etc. Having custom recoery like TWRP does prevent OTA updates. But right now until we get some custom Lollipop ROMs for our Moto Maxx, I'm not giving up all the Gravity Box featues I have with Xposed in 4.4.4.
________________________________________________________
MOTO MAXX IMAGES (XT1225) - PUERTO RICO
SYSTEM VERSION: 21.11.9.quark_amxpr.amxpr.en.PR amxpr
BASEBAND VERSION: MDM9625_104335.118.0254R, QUARK_CLALASL_CUST
My first Moto Maxx is from Puerto Rico. Although sold by Claro, this image is unlocked and has ONLY Motorola software just like the Mexican Moto Maxx. So, there's nothing "retail" about it, it's factory. (The Moto Maxx sold by Claro has no bloatware). I posted these images before, nothing different, just putting them all in one post so they are easier to find.
1) MOTO_MAXX_XT1225_PR_FACTORY_IMAGE_ROOTED
MIRROR: http://www.mediafire.com/download/kmn4dx68lu7y3p1/Moto-Maxx-XT1225-rooted-PR-image.zip
This is Puerto Rico Moto Maxx XT1225 Factory Image, unlocked, rooted -- but no TWRP residing in recovery.
See my notes above about rooting and TWRP.
______________________________________________________________
2) MOTO_MAXX_XT1225_PR_FACTORY_IMAGE_ROOTED_TWRP
MIRROR: http://www.mediafire.com/download/9jk2k01r9dybn4g/Moto-Maxx-XT1225-rooted-PR-TWRP-image.zip
This is Puerto Rico Moto Max XT1225 Factory Image, unlocked, rooted with TWRP residing in recovery.
See my notes above about rooting and TWRP.
______________________________________________________________
"Android version", "Kernel version", "Build number" are identical on both Mexico and Puerto Rico models. Only the "System Version" and "Baseband Version" info differs. However, I cannot tell any difference between the two. Same apps out of the box, same behavior, same GSM/HSPA/LTE bands enabled.
______________________________________________________________
MORE INFO
]
hawkfx said:
Hi
Sorry for asking such noob question, how can i install root image?
Click to expand...
Click to collapse
Going to list the steps. If you have already done some of them, skip to the next.
1) Turn on phone and connect phone to computer via USB cable.
2) Download the factory recovery image you want from my links onto your phone, or drag the image over to your phone storage from computer.
3) Download and install ADB to your computer.
4) Unlock your bootloader. Get code from Motorola. Google unlock Motorola bootloader and click on link for the Motorola website. Follow the directions.
5) Download TWRP recovery from the OP post of this thread and extract files, preferably to your "platform-tools folder" where you installed ADB on your computer.
(In the screenshot below, I re-named TWRP to be "recovery.img" -- not to be confused with the factory recovery image made from TWRP that you are trying to flash. The recovery.img in the folder below is TWRP. I should have named it that. Sorry for any confusion.)
In that "platform-tools" folder, then hit "shift" key on your keyboard, right click in open space and choose "open command window here".
6) Follow instructions from the op post to use command window (via ADB) to boot phone to the bootloader, and then use the command window (via ADB) to flash the "one time" TWRP recovery boot file.
This will not install TWRP recovery permanently. (You can do that later if you wish.) But you need to at least boot into "temporary" TWRP recovery to install any of the images.
7) In TWRP, then choose "restore" and browse to the TWRP recovery image you put on the phone from step #2. Choose that, and restore.
8) Reboot phone.
________________
NON-TWRP BELOW!
________________
MOTO MAXX IMAGE (XT1225) - PUERTO RICO
SYSTEM VERSION: 21.11.9.quark_amxpr.amxpr.en.PR amxpr
BASEBAND VERSION: MDM9625_104335.118.0254R, QUARK_CLALASL_CUST
Pure factory image. 4.4.4 Stock. Need to use RSD Lite to flash.
OR you can unzip the image and use @Jaocagomez excellent instructions in this thread to flash all sections of the image using mfastboot.
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
AMXPR_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-CLALASL_CFC.xml.zip
MEDIA FIRE
http://www.mediafire.com/download/l..._KXG21.50-9_cid12_subsidy-CLALASL_CFC.xml.zip
GOOGLE DRIVE
http://goo.gl/FtTq7T
MOTO MAXX IMAGE (XT1225) - PUERTO RICO
XT1225_QUARK_AMXPR_5.0.2_LXG22.33-12.16_cid12_subsidy-CLALASL_CFC.xml.zip
Pure factory image. 5.0.2 Stock. Need to use RSD Lite to flash.
OR you can unzip the image and use @Jaocagomez excellent instructions in this thread to flash all sections of the image using mfastboot.
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
MEDIA FIRE
http://www.mediafire.com/download/t...22.33-12.16_cid12_subsidy-CLALASL_CFC.xml.zip
GOOGLE DRIVE
https://drive.google.com/file/d/0B8ENz9WTAsk_dlhTT2xobmYwNzg/view?usp=sharing
ONE DRIVE
http://1drv.ms/1MXeYOc
_____________________
MOTO TURBO IMAGE (XT1225) - INDIA
QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
This is the stock Lollipop 5.0.2 image that was released with the Moto Turbo XT1225, which is the same Quark device as the Moto Maxx XT1225. Just re-named for another market...
This is the firmware PUBLICLY released by Motorola on the Moto Turbo phones, bought by customers. It is NOT the subject of any confidential non-disclosure agreement. It is NOT any kind of soak test, beta test, whatever. It is FINAL factory software, shipped with the Moto Turbo XT1225.
This is my Moto Maxx XT1225 converted to India Moto Turbo XT1225 , flashing this image.
The advantage is Motorola lists all the current specs, including enabled bands for the Moto Turbo XT1225. Although the Moto Maxx XT1225 has the exact same bands (LTE and HSPA), on the Latin American Moto Maxx websites, Motorola does not admit all those bands are enabled, even though they are (like AT&T LTE band 5 and T-mobile HSPA band 4). By flashing the Moto Turbo Lollipop image, you can prove to other people you do indeed have all those bands, because it's on the Motorola Moto Turbo specs page.
http://www.motorola.in/consumers/mobile-phones-in/Moto-Turbo/moto-turbo-in.html#moto-turbo-specs
Pure factory image. 5.0.2 Stock. Need to use RSD Lite to flash.
OR you can unzip the image and use @Jaocagomez excellent instructions in this thread to flash all sections of the image using mfastboot.
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
MEDIA FIRE
http://www.mediafire.com/download/c...G22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
GOOGLE DRIVE
https://drive.google.com/file/d/0B8ENz9WTAsk_aVFGNFhkTW0tOXM/view?usp=sharing
_____________________
RETBR 5.0.2 FXZ
MOTO MAXX IMAGE (XT1225) - BRAZIL
QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
This is the stock Lollipop 5.0.2 image that was released for the Moto Maxx XT1225, in Brazil.
This is the firmware PUBLICLY released by Motorola for Moto Maxx phones in Brazil, bought by customers. It is NOT the subject of any confidential non-disclosure agreement. It is NOT any kind of soak test, beta test, whatever. It is FINAL factory software.
Pure factory image. 5.0.2 Stock. Need to use RSD Lite to flash.
OR you can unzip the image and use @Jaocagomez excellent instructions in this thread to flash all sections of the image using mfastboot.
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
MEDIA FIRE
http://www.mediafire.com/download/j...22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
GOOGLE DRIVE
https://drive.google.com/file/d/0B8ENz9WTAsk_WFprNVF1RFRFSUk/view?usp=sharing
Quark is Nexus 6 5.2" Shamu variant repurposed
As late as mid-August, Motorola/Google was testing a 5.2" version of "Shamu" to either be THE Nexus 6 -- or Google was considering pulling an Apple and releasing TWO Nexus 6 smartphones.
http://www.idigitaltimes.com/nexus-...-reveals-52-inch-1440p-display-and-snapdragon
Nexus 6 Specs Confirmed: Benchmark Leak For Motorola 'Shamu' Reveals 5.2-inch 1440p Display and Snapdragon 805
The existence of a Nexus 6 benchmark, which has confirmed leaked specs shows that the early rumors weren't entirely correct. A Motorola "Shamu" exists, but it won't be a massive phablet. Rather it will be a 5.2-inch 2560 x 1440 QHD device, powered by a quad-core Snapdragon 805 processor clocked at 2.6GHz with an Adreno 420 GPU, 3GB of RAM, a 12-megapixel rear camera with 4K UHD video recording capabilities and a 2-megapixel front facing camera. It will launch with Android L.
Click to expand...
Click to collapse
Well, Google did indeed choose the massive 5.96" version over the 5.2" version -- but they were TESTING the smaller version for several months. However, after mid-August, all evidence of a 5.2" Nexus 6 variant disappeared and only the 5.96" remained.
I think that was a mistake. To me, a 5.2" Nexus 6 phone would have been killer.
5.2" Moto Maxx vs massive 5.96" Nexus 6
Motorola obviously re-purposed the 5.2" "Shamu" variant as the Droid Turbo/Moto Maxx, and changed the camera. A lot of the hardware specs remains the same as the Nexus 6. But that doesn't mean you can flash a Nexus 6 image on it.
Same manufacturer (Motorola),
same CPU/GPU (Snapdragon 805),
same RAM (3GB),
same resolution (1440p),
same "turbo" charger
same Qi wireless charging.
Same 64GB internal storage as the 64GB version of the Nexus 6.
And then Motorola announced a 5.2" 1440p, Snapdragon 805, 3GB RAM phone -- codenamed Quark -- to be released in U.S. as Droid Turbo (XT1254) and Moto Maxx (XT1250) -- identical in every way to the Droid Turbo including FCC ID but with bootloader that can be unlocked -- as well as "internationally" as Moto Maxx (XT1225) and Moto Turbo (XT1225). The Moto Turbo (relelased in India) XT1225 and Moto Maxx XT1225 are identical in every aspect, but have different model names due to a "Maxx" carrier in India which is not affilated with this phone. Motorola changed the model name to avoid confusion. The Droid Turbo XT1254 and Moto Maxx XT1250 are identical and have the same FCC ID. The "international" Moto Maxx and Moto Turbo are identical to each other, and share the same FCC ID, but have a different FCC ID from the XT1254/XT1250.
ALL Quarks have the same hardware, except for internal memory. The U.S. models (XT1254/XT1250) come in 32GB and 64GB internal storage. The International models (XT1225) come with 64GB storage only. However all internal hardware, including modem, CPU, GPU are the same. With the Snapdragon 805 there are no longer any variants for different cell bands. Instead, the manufacturer decides which bands to enable and lock down. It's a firmware/software choice, not dependent on hardware like with past Snapdragons.
The modem chip in the Snapdragon 805 is truly a global all-in-one, which can be tailored by the manufacturer. All Quarks have identical hardware (except for internal storage).
___________
In another example, Motorola has also re-purposed the actual Nexus 6 as the Moto X Pro for China. Probably can't flash a NEXUS 6 image on it, either -- even though it's identical hardware.
"Moto X Pro" -- for China. 5.96" identical hardware version of the Nexus 6.
Do I need to have unlocked bootloader to flash using RSD LITE?
mirdones said:
Do I need to have unlocked bootloader to flash using RSD LITE?
Click to expand...
Click to collapse
Read these two messages and see if they apply to your situation.
http://forum.xda-developers.com/showpost.php?p=59881279&postcount=39
http://forum.xda-developers.com/showpost.php?p=59882453&postcount=40
If you are flashing an image that was made for your country, your phone, you can use RSD Lite without unlocking bootloader. But you are still doing so at your risk.
If you are flashing an image for another country (example: Puerto Rico KitKat 4.4.4 to Brazil or India Lollipop 5.0.2) and you do not unlock the bootloader, if something goes wrong you HAVE to wait until that 5.0.2 image is released for your phone and flash that instead. Whenever that is.
When I flashed my Mexico KitKat 4.4.4 to India Lollipop 5.02, I messed up first time and didn't flash the entire image. But it was OK, because my bootloader was unlocked.
@ChazzMatt I made a backup of clean install image from Brazil. I can post link here?
----
Moto Maxx - XT1225
Xposed Stock Android 5.0.2
ChazzMatt said:
As late as mid-August, Motorola/Google was testing a 5.2" version of "Shamu" to either be THE Nexus 6 -- or Google was considering pulling an Apple and releasing TWO Nexus 6 smartphones.
http://www.idigitaltimes.com/nexus-...-reveals-52-inch-1440p-display-and-snapdragon
Well, Google did indeed choose the massive 5.96" version over the 5.2" version -- but they were TESTING the smaller version for several months. However, after mid-August, all evidence of a 5.2" Nexus 6 variant disappeared and only the 5.96" remained.
I think that was a mistake. To me, a 5.2" Nexus 6 phone would have been killer.
5.2" Moto Maxx vs massive 5.96" Nexus 6
Motorola obviously re-purposed the 5.2" "Shamu" variant as the Droid Turbo/Moto Maxx, and changed the camera. A lot of the hardware specs remains the same as the Nexus 6. But that doesn't mean you can flash a Nexus 6 image on it.
Same manufacturer (Motorola),
same CPU/GPU (Snapdragon 805),
same RAM (3GB),
same resolution (1440p),
same "turbo" charger
same Qi wireless charging.
Same 64GB internal storage as the 64GB version of the Nexus 6.
And then Motorola announced a 5.2" 1440p, Snapdragon 805, 3GB RAM phone -- codenamed Quark -- to be released in U.S. as Droid Turbo (XT1254) and Moto Maxx (XT1250) -- identical in every way to the Droid Turbo including FCC ID but with bootloader that can be unlocked -- as well as "internationally" as Moto Maxx (XT1225) and Moto Turbo (XT1225). The Moto Turbo (relelased in India) XT1225 and Moto Maxx XT1225 are identical in every aspect, but have different model names due to a "Maxx" carrier in India which is not affilated with this phone. Motorola changed the model name to avoid confusion. The Droid Turbo XT1254 and Moto Maxx XT1250 are identical and have the same FCC ID. The "international" Moto Maxx and Moto Turbo are identical to each other, and share the same FCC ID, but have a different FCC ID from the XT1254/XT1250.
ALL Quarks have the same hardware, except for internal memory. The U.S. models (XT1254/XT1250) come in 32GB and 64GB internal storage. The International models (XT1225) come with 64GB storage only. However all internal hardware, including modem, CPU, GPU are the same. With the Snapdragon 805 there are no longer any variants for different cell bands. Instead, the manufacturer decides which bands to enable and lock down. It's a firmware/software choice, not dependent on hardware like with past Snapdragons.
The modem chip in the Snapdragon 805 is truly a global all-in-one, which can be tailored by the manufacturer. All Quarks have identical hardware (except for internal storage).
___________
In another example, Motorola has also re-purposed the actual Nexus 6 as the Moto X Pro for China. Probably can't flash a NEXUS 6 image on it, either -- even though it's identical hardware.
"Moto X Pro" -- for China. 5.96" identical hardware version of the Nexus 6.
Click to expand...
Click to collapse
excellent post and very well explained, Regards :good:
Shamu and quark are similar, i really want some devs port things to quark, like recovery ans kernels
RSDamasceno said:
@ChazzMatt I made a backup of clean install image from Brazil. I can post link here?
----
Moto Maxx - XT1225
Xposed Stock Android 5.0.2
Click to expand...
Click to collapse
Yes you can post here.
What format backup did you make, TWRP? It's Brazil 5.0.2? Just curious if you have tried to restore from that backup? Does it work?
I've only tried after hitting "fix permissions", and that messed everything up. The backup would not restore, but again that was AFTER I had tried to fix permissions... I have not tried to restore from a backup just to restore from a backup, if that makes sense.
I had hit "fix permissions" to try to get my TWRP folders to show up in the PC USB debugging view. After hitting "fix permissions", then the phone would never finish rebooting. So, I went into fastboot and tried to restore a backup. That didn't work either, but was after hitting "fix permissions". So, flashed the image to reinstall everything again!
I'm only using TWRP with 5.0.2 to install zip files, like to root and to install xposed/gravity box for Lollipop.
At this point, I'm a little leery of just trying to restore a TWRP backup when everything is working OK. Have you done it?
I made a clean TWRP backup after update of Brazil 5.0.2 OTA official.
----
Moto Maxx - XT1225
Xposed Stock Android 5.0.2
RSDamasceno said:
I made a clean TWRP backup after update of Brazil 5.0.2 OTA official.
----
Moto Maxx - XT1225
Xposed Stock Android 5.0.2
Click to expand...
Click to collapse
Cool, feel free to post it.
https://mega.co.nz/#!NFlkWZBL!AV9RmONHoxy7KXeFlMgci-SadUPZU_oNqzgkmaxP9Ws
TWRP backup of official stock Brazilian Lollipop 5.0.2 (version .13).
Without Root, with stock recovery.
----
Moto Maxx - XT1225
Xposed Stock Android 5.0.2
Here are some Fast mirrors on my server
http://storagecow.eu/index.php?dir=Xda/Motorola/Moto+Maxx/
I don't get it. I put the zip in the phone storage. When I go to restore on twrp nothing appears. If I go to install its right there.... So should I restore or instalaste in order to flash one of those twrp backups?
Dani01c said:
I don't get it. I put the zip in the phone storage. When I go to restore on twrp nothing appears. If I go to install its right there.... So should I restore or instalaste in order to flash one of those twrp backups?
Click to expand...
Click to collapse
You have to extract the files from the zipped folder, and move those to your TWRP recovery folder. The folder is zipped just to make sure you have all the files together when downloading them. You don't flash it (like an installation file), you have to use an extracted, unzipped version of the files to restore through TWRP.
ChazzMatt said:
You have to extract the files from the zipped folder, and move those to your TWRP recovery folder. The folder is zipped just to make sure you have all the files together when downloading them. You don't flash it (like an installation file), you have to use an extracted, unzipped version of the files to restore through TWRP.
Click to expand...
Click to collapse
I extracted them in the computer and passed them to the twrp folder and still nothing appears....
---------- Post added at 09:49 AM ---------- Previous post was at 09:27 AM ----------
Dani01c said:
I extracted them in the computer and passed them to the twrp folder and still nothing appears....
Click to expand...
Click to collapse
I'm starting to hate this phone. I'll never get rid of KitKat.
Dani01c said:
I extracted them in the computer and passed them to the twrp folder and still nothing appears....
---------- Post added at 09:49 AM ---------- Previous post was at 09:27 AM ----------
I'm starting to hate this phone. I'll never get rid of KitKat.
Click to expand...
Click to collapse
You can use ADB to flash the factory image, instead of using TWRP.
You probably can't use TRWP to upgrade from 4.4.4 to 5.0.2. But afterwards, you can possibly use TRWP to switch from one Lollipop to another. My guess, as I did not use TWRP to upgrade. I flashed both my Mexico Moto Maxx and Puerto Rico Moto Maxx from 4.4.4 to India 5.0.2. In the next few days will try out Brazil 5.0.2 and/or CM 12.1.
ChazzMatt said:
You can use ADB to flash the factory image, instead of using TWRP.
You probably can't use TRWP to upgrade from 4.4.4 to 5.0.2. But afterwards, you can possibly use TRWP to switch from one Lollipop to another. My guess, as I did not use TWRP to upgrade. I flashed both my Mexico Moto Maxx and Puerto Rico Moto Maxx from 4.4.4 to India 5.0.2. In the next few days will try out Brazil 5.0.2 and/or CM 12.1.
Click to expand...
Click to collapse
Which one would you suggest? I was going to install the mexico version with twrp and root to my Puerto Rico Moto maxx. I haven't tried the CM12 because it seems to have lots of bugs. For the flashing I have to flash the Zip just like I did for the recovery? If not which one of the MD5 files?
Dani01c said:
Which one would you suggest? I was going to install the mexico version with twrp and root to my Puerto Rico Moto maxx. I haven't tried the CM12 because it seems to have lots of bugs. For the flashing I have to flash the Zip just like I did for the recovery? If not which one of the MD5 files?
Click to expand...
Click to collapse
OK, so you were just trying to convert your Puerto Rico Moto Maxx (with 4.4.4) to Mexico 4.4.4? Then, flash the Mexicon 5.0.2 OTA over that?
If that's what you were trying to do, then I don't know why TWRP is not working for you... I thought you were trying to restore TWRP 5.0.2 image over 4.4.4.
ChazzMatt said:
OK, so you were just trying to convert your Puerto Rico Moto Maxx (with 4.4.4) to Mexico 4.4.4? Then, flash the Mexicon 5.0.2 OTA over that?
If that's what you were trying to do, then I don't know why TWRP is not working for you... I thought you were trying to restore TWRP 5.0.2 image over 4.4.4.
Click to expand...
Click to collapse
Yes, I have Puerto Rico 4.4.4 and I was trying to restore Mexico 5.0.2 rooted with twrp.
Dani01c said:
Yes, I have Puerto Rico 4.4.4 and I was trying to restore Mexico 5.0.2 rooted with twrp.
Click to expand...
Click to collapse
What should I do? Extract and flash via fastboot? Which file should I flash? There are like 3 MD5 files. I have recovery and everything flashed already. I have the zip and the extracted files in the twrp folder.
Related
H930DS20d_00_OPEN_CIS_DS_OP_0526.kdz
3.0GB
For H930DS or H930D.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 2f866e8987c91bda2085de2b10c3bd75
______________________________
PREVIOUS FIRMWARE
H930DS20c_00_OPEN_CIS_DS_OP_0419.kdz
3.0GB
For H930DS.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 4ed9198f17fdf51888b00be1bea14a68
Thanks to @crubbish for telling us about this!
HOW TO (temporarily) DOWNGRADE BACK TO OREO FOR BOOTLOADER UNLOCK
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install -- for bootloader unlock would be this CIS 20d. You can update to more current firmware AFTER unlocking bootloader on early Oreo.
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
0. Uninstall any prior LGUP you have. Uninstall anything like Uppercut, which no longer works and causes conflicts with this Dev Patched LGUP.
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut, NOT the Install folder shortcut.
Choose Process : PARTITION DL (all partitions)[/B]
----------------------------
3) DOWNGRADING/UPGRADING ANY LG V30/V30+/V30S TO EARLY OREO KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (post 101 of Frankenstein thread)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
REBOOT THE COMPUTER.
If you ask for help, that's the list of items we are going to give you anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER (with early Oreo), GO READ [URL="https://forum.xda-developers.com/showpos
IF you are using this for bootloader unlock purposes, then you probably want DL PARTITION mode and choose all partitions.
NOTE: @crubbish says he unlocked his bootloader on his H930DS using THIS Oreo. He says he did not flash the European open market H930. While the H930 Oreo KDZ will give H930DS users dual SIM functionality (at least a dozen users who unlocked their bootloaders and rooted say so) -- this definitely will also, as it's an H930DS Oreo KDZ.
I am only posting it due to @crubbish's statements. You can use this Oreo KDZ, and have fastboot flash commands which allow you to unlock your bootloader, install TWRP and root using the new_unlock.bin code from the WTF thread.
It's an alternative to the H930 Oreo KDZ in the instructions in that thread.
Any issues? As im a beginner nd these things r totally unknown to me
SRS84 said:
Any issues? As im a beginner nd these things r totally unknown to me
Click to expand...
Click to collapse
Issues with what?
This is stock LG Oreo KDZ from LG for CIS region H930DS.
The only reason you would use this would be to upgrade any H930DS from Nougat to Oreo (but you can also do that with European H930 Oreo KDZ) and/or to get fastboot commands to bootloader unlock, install TWRP and root any H930DS (which you can also do with European H930 Oreo KDZ).
Both will still give any H930DS the dual SIM functionality.
This is just an alternative KDZ for anyone who wants to use it. Some H930DS users don't trust single SIM KDZ, even though we've shown dual SIM functionality remains.
I dont know if im talking sensible or not but please tell me this rom for cis regions will work with indian lg v30+ variant and any issues in this rom beside jio volte not working.
Thanks
EDIT: If you want India Oreo KDZ with pre-July 2018 firmware so you can unlock bootloader, use this. Then after bootloader unlock you can safely update to latest India firmware. That will also give you Jio VoLTE.
____________
SRS84 said:
I dont know if im talking sensible or not but please tell me this rom for cis regions will work with indian lg v30+ variant and any issues in this rom beside jio volte not working.
Thanks
Click to expand...
Click to collapse
Yes, it will work for India H930DS V30+, except for Jio VoLTE (which is Jio fault).
It will also give you the same bootloader unlock capabilities (fastboot flash commands) as the European H930 Oreo KDZ, from what @crubbish says.
Just checked in the G6 forum and i heard that H870DS version has started its oreo roll out in Asia Pacific region, finally..
means, H930DS' turn will be next, just wait..
But, my question is, if we have updated using the LGUP, (no root etc) and some day there is an OTA update from the LG server, can we still see the notification and download the update over the air just like normal? It should be able, right?
ChazzMatt said:
H930DS20c_00_OPEN_CIS_DS_OP_0419.kdz
3.0GB
For H930DS.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 9f694d267886ef31c130ac5bb831915f
Click to expand...
Click to collapse
hi, just checked the download link. looks like the file is still H930DS20n_00_OPEN_HK_DS_OP_0416.kdz rather than the CIS version. is it the correct link or is it a different KDZ but under the same file name?
meanwhile, what's CIS? which region is it?
yohannes.panduputra said:
hi, just checked the download link. looks like the file is still H930DS20n_00_OPEN_HK_DS_OP_0416.kdz rather than the CIS version. is it the correct link or is it a different KDZ but under the same file name?
meanwhile, what's CIS? which region is it?
Click to expand...
Click to collapse
Thanks. Hold on let me correct the link. I also have the HK version in my Android Host files. That's really strange, but guess I copied and pasted the wrong URL.
EDIT: link corrected. Thanks again for letting me know.
From what I was told, CIS is a group of former Soviet/Russian republics.
The Commonwealth of Independent States (CIS) formed when the former Soviet Union (now called Russia) totally dissolved in 1991. At its conception it consisted of ten former Soviet Republics: Armenia, Belarus, Kazakhstan, Kyrgyzstan, Moldova, Russia, Tajikistan, Turkmenistan, Ukraine, and Uzbekistan.
Click to expand...
Click to collapse
ChazzMatt said:
Yes, it will work for India H930DS V30+, except for Jio VoLTE (which is Jio fault).
It should also give you the same bootloader unlock capabilities (fastboot flash commands) as the European H930 Oreo KDZ, from what @crubbish says.
Click to expand...
Click to collapse
Thanks for the info.. Highly appreciated
Hi! I wanna install this ROM through the recovery. Perhaps you have a zip package to install through TWRP? )))
Kleymor.Metal said:
Hi! I wanna install this ROM through the recovery. Perhaps you have a zip package to install through TWRP? )))
Click to expand...
Click to collapse
No. It's just LG stock Oreo for H939DS.
It has no advantages over any other H930DS Oreo KDZ (like Hong Kong).
I mean, if someone wants to create a full stock flashable zipped ROM, feel free. But when people do stock-based ROM they usually take stuff out or still make changes.
Edited to include information on July 2018 and later security patches.
_________
H930DS20d_00_OPEN_CIS_DS_OP_0526.kdz. Flash with LGUP attached to post #1. This is one V30/V30+ firmwares that have the necessary fastboot flash commands to unlock your bootloader, install TWRP and root with the WTF method.
Safe to flash if you have not yet unlocked your bootloader, as it has May 2018 security update, not yet the July 2018 security update (which will reportedly block the bootloader unlock exploit). You can tell by the date in file name 5/26 (2018) -- not when it was actually released to the public (early June 2018).
Previous firmware was H930DS20c_00_OPEN_CIS_DS_OP_0419.kdz, which was finalized on 4/19 (2018), even though it was released in early May 2018.
Any firmware updates with July 2018 dates or later, do NOT use until you have unlocked your bootloader!
If you have unlocked your bootloader, you can flash any firmware update and your bootloader will remain unlocked.
See here:
christopherrrg said:
Does this mean the CIS version has the bootloader exploit also?
Click to expand...
Click to collapse
Yes.
Rizal Lovins said:
Just to inform my LG V30+ H930DS has been successfully unlocked using firmware H930DS CIS KDZ
kudos @ChazzMatt :highfive:
Click to expand...
Click to collapse
EDIT: Actually the block to the bootloader unlock exploit was released with JULY 2018 security patch, even though it was listed for June 2018.
__________
FYI, for those who don't know what we are referring to in the "June 2018 security patch." But we are trying to warn people.
Android Security Bulletin: Everything you need to know!
https://www.androidcentral.com/android-security-bulletin
Highlights for June 2018
June 2018's update comes with two patch dates: 06/01/2018 and 06/05/2018.
LG, Qualcomm, MediaTek, and NVIDIA all provide important fixes for their assorted binaries across all devices, and critical issues with the bootloader were patched by Qualcomm and LG.
Click to expand...
Click to collapse
NOTE: "critical issues with the bootloader were patched by Qualcomm and LG." Qualcomm is even getting involved.
What does that sound like? Fixing the LG Oreo bootloader unlock exploit, where ANY unlock.bin command (even one for a Huawei phone) will unlock the bootloader, even if it says it FAILS?
Yes, @TxanMoe then created his own new_unlock.bin code which does not give a "FAIL" notice, and I also experimented with an "official" LG Developer website bootloader unlock code on one of my eBay LS998 V30+ which I converted to US998 V30+. It succeeded, but should not have since it was for a open market V30 with another IMEI and DeviceID. The current LG Oreo exploit something so wonderful you can only dream about it. But it's real. And it sounds like LG and Qualcomm are rushing to close it.
But anyone who ever wants root should unlock their bootloader now or risk forever that door being closed.
WTF V30/V30+/V30S Bootloader Unlock and Root (MOST VARIANTS)
Sorry to bother you ChazzMatt, im going to try download oreo on my v30, do you have detailed video how to flash oreo. It would be very helpful.
Thanks
hello
I've unlocked my h930DS with the "new_unlock.bin"
does that mean that I can now install any newer version than H930DS20d_00_OPEN_CIS_DS_OP_0526.kdz (if there's any) and still be unlocked?
thanks!
dave_id said:
hello
I've unlocked my h930DS with the "new_unlock.bin"
does that mean that I can now install any newer version than H930DS20d_00_OPEN_CIS_DS_OP_0526.kdz (if there's any) and still be unlocked?
thanks!
Click to expand...
Click to collapse
Yes.
k, I've read that h930 fw can be flashed on h930ds, for being able to use fastboot etc pp. but: how about the other way? flashing h930ds hk/ind/cis on h930 eu open?
it's 128gb for the h930ds vs. 64gb for the h930, so gpt shouldn't be flashed i assume would be interesting, just because of freakin' volte sh¡t...
ChazzMatt said:
Yes.
Click to expand...
Click to collapse
thanks a lot, I'm on the way to install the latest firmware...
as I understand I just need lgup and click the UPGRADE option, right?
my concern is do I have to reinstall "twrp", "magisk" and "no-verity-opt-encrypt-6.0" after that?
tried to flash the westwood24 zip but for some reason I'm still on the old rom (20D) when rebooting...
thanks a lot.
dave_id said:
thanks a lot, I'm on the way to install the latest firmware...
as I understand I just need lgup and click the UPGRADE option, right?
my concern is do I have to reinstall "twrp", "magisk" and "no-verity-opt-encrypt-6.0" after that?
tried to flash the westwood24 zip but for some reason I'm still on the old rom (20D) when rebooting...
thanks a lot.
Click to expand...
Click to collapse
If you install via upgrade it'll wipe your TWRP. Best to DL PARTITION, but Uncheck the recovery partitions. That will keep TWRP custom recovery. Boot to TWRP, flash those three files. With TWRP backup and Titanium Backup you can restore all data and apps.
Hello, my Moto g5 is having retin software channel which seems to be Moto g5 plus should have.is any one is having retin software channel in they Moto g5. If anyone is having please let me know as it seem to have Moto g5 plus software channel.
You can see in the screenshot which I have capture on both device's:-
riyan65 said:
Hello, my Moto g5 is having retin software channel which seems to be Moto g5 plus should have.is any one is having retin software channel in they Moto g5. If anyone is having please let me know as it seem to have Moto g5 plus software channel.
You can see in the screenshot which I have capture on both device's:-
Click to expand...
Click to collapse
I just need some clarification as I don't fully understand what are trying to say
retin just means I imagine you are a retail India software channel
If you own a moto g5 plus Potter you have posted in the wrong forum
TheFixItMan said:
I just need some clarification as I don't fully understand what are trying to say
retin just means I imagine you are a retail India software channel - are you saying that you own a moto g5 cedric & since updating to oreo with the soak test ota your device now displays as a moto g5 plus potter?
If that is the case then Motorola have just mucked up the build.prop - these are just text lines and can be changed to display anything you like in about phone
If you own a moto g5 plus Potter you have posted in the wrong forum
Click to expand...
Click to collapse
Thanks for replying,but I want to say that my Moto g5 has retin software channel which belongs to Moto g5 plus as I am having both the device I have put the screenshot of them.i just want to know that retin software channel is belong to Moto g5 or not, and other Moto g5 is having retin software channel or not.and I didn't register for Moto MFN.
riyan65 said:
Thanks for replying,but I want to say that my Moto g5 has retin software channel which belongs to Moto g5 plus as I am having both the device I have put the screenshot of them.i just want to know that retin software channel is belong to Moto g5 or not, and other Moto g5 is having retin software channel or not.and I didn't register for Moto MFN.
Click to expand...
Click to collapse
All moto devices will have a retin software channel (if sold in India)
Ret means it's a retail device (instead of an Amazon device)
in - means it's an Indian varient
So both moto g5 and g5 plus will have a retin software channel
TheFixItMan said:
All moto devices will have a retin software channel (if sold in India)
Ret means it's a retail device (instead of an Amazon device)
in - means it's an Indian varient
So both moto g5 and g5 plus will have a retin software channel
Click to expand...
Click to collapse
Thanks for clarifying,but my Moto g5 came with amazin. After replacement of motherboard my device is having retin so that I am having dought. And if I install Oreo soak test which is for amazin does my device again get bricked.
riyan65 said:
Thanks for clarifying,but my Moto g5 came with amazin. After replacement of motherboard my device is having retin so that I am having dought. And if I install Oreo soak test which is for amazin does my device again get bricked.
Click to expand...
Click to collapse
You can change the channel just by flashing a stock rom firmware from a different country
Obviously when you bought the phone from Amazon it came with Amazon firmware so it would display amazin
When your motherboard was replaced they flashed retail firmware on it so that's why it now shows retin
You can flash what ever firmware you like (assuming that there's no phone frequencies that are different or not compatible between countries)
As long as your phone is unmodified (no custom rom/recovery root etc) you will be able to ota update
TheFixItMan said:
You can change the channel just by flashing a stock rom firmware from a different country
Obviously when you bought the phone from Amazon it came with Amazon firmware so it would display amazin
When your motherboard was replaced they flashed retail firmware on it so that's why it now shows retin
You can flash what ever firmware you like (assuming that there's no phone frequencies that are different or not compatible between countries)
As long as your phone is unmodified (no custom rom/recovery root etc) you will be able to ota update
Click to expand...
Click to collapse
so I can use amazin OTA update for retin also???
riyan65 said:
so I can use amazin OTA update for retin also???
Click to expand...
Click to collapse
No - the ota looks for the build number of the current version installed - if the ota is for the Amazon varient you will need that firmware installed
You won't damage your device if you try & flash an ota in stock recovery that is for the wrong firmware - it simply won't flash and gives an error about the wrong firmware version detected
Unless the ota updates both Amazon & retail varients it won't work
TheFixItMan said:
No - the ota looks for the build number of the current version installed - if the ota is for the Amazon varient you will need that firmware installed
You won't damage your device if you try & flash an ota in stock recovery that is for the wrong firmware - it simply won't flash and gives an error about the wrong firmware version detected
Unless the ota updates both Amazon & retail varients it won't work
Click to expand...
Click to collapse
Can we flash stock rom with locked bootloader???
riyan65 said:
Can we flash stock rom with locked bootloader???
Click to expand...
Click to collapse
Yes
TheFixItMan said:
Yes
Click to expand...
Click to collapse
Is there changes of hard bricked??
riyan65 said:
Is there changes of hard bricked??
Click to expand...
Click to collapse
Only if you're flashing gpt or bootloader parts - unless you need to change these there's no need to flash them
There is always a risk in anything you do - if you don't know what you're doing use Google YouTube or just stay on stock unmodified
any link for amzin img ?
silent03 said:
any link for amzin img ?
Click to expand...
Click to collapse
All firmware can be found here
https://mirrors.lolinet.com/firmware/moto/cedric/official/
ROOT YOUR LG V3O!
Bootloader unlock, install TWRP, root any V30/V30+/V30S on the planet!
* WTF V30/V30+/V30S Bootloader Unlock, TWRP and Root INSTRUCTIONS
The WTF bootloader unlock, TWRP installation, root method (link above) works on EVERY V3O variant in existence -- EXCEPT for U.S. T-Mobile H932. Read the instructions in a web browser, not an app. Print out the instructions and read them thoroughly!
For U.S. T-Mobile H932, use this alternate method:
* U.S. T-Mobile H932 Bootloader Unlock, TWRP and Root INSTRUCTIONS
Print out the instructions and read them thoroughly!
____
When rooting your V30/V30+/V30S, you will TEMPORARILY downgrade to earlier stock firmware, unless you are already on that earlier firmware. After rooting, you should immediately upgrade back to at least most recent Oreo stock firmware via TWRP-flashable zips found in the forum. This is necessary to:
* have fixes/features on recent stock V30 updates -- like DTS 3D Surround Sound or better LG stock camera. These features/fixes were included in the latter Oreo update, with the last being most stable.
AND/OR
* install custom LOS-16 "Pie" ROMs. (ONLY upgrade to most recent Oreo firmware! Do NOT upgrade to LG stock Pie yet!) You need most recent LG Oreo as a foundation for LOS-16 custom ROMs to work right.
MORE INFORMATION:
IGNORE that V30 LOS-based ROMs are called "H930" ROMs.
They are "V30" ROMs. Do NOT try to flash stock H930* firmware over North American variants to run LOS-based "H930" ROMs!
Please ask any questions in those threads listed above.
POST #2:
FAQ ON AOSP/Lineage/LOS-16 & LOS 17.x CUSTOM ROMS
1) What's the deal? Why are V30 LOS-based ROMs called "H930" ROMs? Yet everyone says they work all other variants. Why not call them "V30" ROMs?
IGNORE that V30 LOS-based ROMs are called "H930" ROMs.
They are indeed "V30" ROMs. They are "Joan" (code name for LG V30) ROMs. Do NOT try to flash stock H930* firmware over North American variants to run LOS-based "H930" ROMs!
The "H930" label is sort of a "mistake" from the beginning which we can't go back and fix in the LOS tree. ("Mistake" isn't quite the right word but will do for now.)
* ALL LOS-16 based ROMs are compatible with ANY V30 variant, including T-Mobile H932.
* LOS-17 based ROMs are compatible with ANY V30 variant --EXCEPT for U.S. T-Mobile H932.
EDIT: As of October 2020, any LOS-based custom ROMS produced AFTER that are compatible with T-Mobile H932. Thanks to the efforts of @ShapeShifter499. To be safe, only install latest ROMs made well AFTER 2020.
See Question #4 below for more information about T-mobile H932 which ARE compatible with LOS-16 ROMs.
____________
2) Uh, so I've bootloader unlocked, installed TWRP and rooted and on Nougat/early Oreo. I don't plan on running stock firmware, so I can just go install an "Android 10" (LOS-17) ROM, right?
NO.
* You need to be on most recent OREO stock rooted firmware before attempting to install AOSP/LOS-16 Pie/Android 9 custom ROMs. V30 LOS-16 ROMs need LG stock Oreo/Android 8 blobs (drivers) and you need the most RECENT for everything to work right.
* You need to be on Pie/Android 9 stock rooted firmware before attempting to install V30 AOSP/LOS-17 "Android 10" custom ROMs. V30 LOS-17 ROMs need LG stock Pie/Android 9 blobs (drivers) for everything to work right.
In particular you can NOT be on LG early Oreo or Nougat, even though you needed to be on that initial bootloader unlock. There are TWRP-flashable zips (ROMs) based on stock Oreo/Android 8 KDZ or Pie/Android 9 KDZ to help you upgrade to later stock firmware. Links for stock firmware TWRP-flashable zips are posted in the Oreo/Android 8 and Pie/Android 9 KDZ threads for most major variants. Use these TWRP-flashable zips to update to most recent Oreo/Android 8 or Pie/Android 9 stock firmware before flashing any V30 AOSP/LOS-based custom ROMs.
When rooting your V30/V30+/V30S, you will TEMPORARILY downgrade to earlier LG stock firmware which can be exploited, unless you are already on that earlier firmware. After rooting, you should immediately upgrade back to most recent stock Oreo/Android 8 firmware via those TWRP-flashable zips or else things probably won't work right.
You do need to update to stock Pie first before trying to install "Android 10" LOS-17 custom ROMs.
____________
3) Hey, my AT&T H931/Canada H933 can't boot these LOS-based ROMs. What am I doing wrong?
FYI: AT&T H931 and Canada H933 V30 variants will need additional prep work before installing AOSP/LOS-based custom ROMs.
You can do it, there are dedicated threads for it. But just warning you -- it's many additional steps besides simple bootloader unlock, TWRP and root.
* Running any AOSP ROM on an US998 converted H931
* [GUIDE] Canadian H933 compatibility with AOSP ROMs
____________
4) Tell me again about T-Mobile H932 and LOS-ROMs?
As of October 2020, any LOS-based ROMS produced after that date should be compatible with T-Mobile H932. Thanks to @ShapeShifter499. BEFORE that date, the ROM had to be specifically made for T-Mobile H932. To be safe, only install latest ROMs made well after 2020.
AFTER October 2020, ALL LOS "H930" Pie LOS-based custom ROMs are compatible with ANY V30 variant.
For LOS-based custom ROMs, the "H930" description in the ROM title simply means ANY V30 variant can run it. "H930" is often the generic name for the V30 series. I could explain why, but it doesn't matter. The exception is if you are installing H930 stock ROMs. Do NOT try to do that with H932! You will brick your phone. That's just how it is.
NOTE: For LOS-16 you need most recent stock Oreo blobs (drivers), NOT stock Pie. You need to be on last stock Oreo firmware for LOS-16. THIS is last T-Mobile H932 Oreo:
[STOCK] [H932] [20s] [Oreo] T-Mobile LG V30 Stock Collection (Includes Debloated) by weakNPCdotCom
https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3917560
____________
5) I need VoLTE!
I have India Jio carrier and they only have LTE, with no 3G HSPA to temporarily drop down to for voice calls.
Also, in the U.S., Verizon, AT&T and T-Mobile are shutting down their 3G CDMA and HPSA in 2022.
I need VoLTE!
No VoLTE or VoWiFi on LOS-based ROMs. Stop asking. (Stock based ROMs like A.I.X. do have VoLTE.)
If you absolutely need VoLTE you need to flash back to stock firmware or possibly check out A.I.X. (But no promises about VoLTE on AIX for everyone. It also depends on the carrier.)
* Most Verizon users need Verizon VS996 firmware for VoLTE, but US998 can work.
* T-Mobile SIM card users can get VoLTE on both US998 firmware or T-Mobile H932 firmware
(WARNING: T-Mobile H932 firmware is only compatible with T-Mobile H932 phones. US998 firmware is NOT compatible with T-Mobile H932 phones, but can be flashed to any other North American V30 variant).
* India Jio users can use EAS (India) H930DS Pie firmware. Also, last Oreo EU H930 firmware has Jio VolTE, but not the EU H930 Pie firmware.
____________
6) What is this A.I.X. ROM I hear people talk about? I can't find it on XDA.
It's a Pie stock-based ROM. Like stock on steroids. Vast improvements in camera and battery usage. No, not found on XDA can be found elsewhere. Not for newbies, but users swear by it.
EDIT: The A.I.X. dev has pulled all files from public view.
____________
7) What if I don't like LOS-based custom ROMs? I hear there are bugs, we can't use LG camera, and there's no VoLTE.
Bugs in LOS-17 are slowly going away, but everything on stock rooted firmware does work just fine. I actually suggest you unlock bootloader, install TWRP and root and run rooted most-recent Oreo stock firmware -- with some Magisk mods -- for awhile before jumping into the custom LOS ROMs. (See point #1 about not updating to stock Pie until you are sure.) Read the various custom ROM threads -- see what works, what doesn't.
If you just want to run rooted stock firmware with Magisk and edXposed (to pass Safety Net) mods, last stock Oreo firmware is the most stable and stock Pie is not really an improvement.
____________
8) Why do I need TWRP? I just want ROOT!
PLEASE make TWRP backups, so you can restore back to rooted stock firmware in case you mess up something!
TWRP custom recovery is a magical time machine which can help you go back before you did something you shouldn't have. But it can only help you if you have a backup to restore. One of the best feelings in the world is when you done something idiotic on your rooted phone -- and then you remember you have a recent TWRP backup. You don't need to ask for help and no one even needs to know.
Also there are some mods you can only flash in TWRP.
____________
WARNING: Pedantic complaint ahead! TLDR: Calling a ROM by the letter Q is ignorant. I don't care who is doing it, it shows they don't understand the Android naming system.
9) What is the difference between Android "Q" ROMs and "Android 10" ROMs? I see both names, sometimes used interchangeably.
Please don't call Android 10 "Q". Q was the beta name. It's now graduated. It's no longer beta. It's "Android 10" -- and has the Android statue at Google HQ to prove it. LOS-17.x custom ROMs are based on Android 10 -- not made from beta "Q" (pre-Android 10) software.
If you are not aware...
With Google's long-time naming scheme for Android, first they released beta "alphabet letter", then revealed full name + statue at graduation from beta status. Final release name was based on a sweet snack/dessert. Many times over the years Google teased devs/users what the REAL name was going to be with false clues. If you keep using beta letter, you are REALLY referring to the old beta software, not current Android software. What confused some people with Android 10 is the escort dessert name never came. Instead of naming it after a dessert, Google decided beta Q would simply became Android 10. The statue at Google headquarters is "Android 10."
CONCLUSION:
No actual "Q" ROMs exist, to my knowledge or they are very outdated. "Q" was the beta letter for what became Android 10. Like a caterpillar vs butterfly. You don't keep calling it a caterpillar once it's turned into a butterfly!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Q" on the left, "Android 10" on the right
People who call Android 10 by beta letter "Q" are committing a faux pas -- or simply they have no clue what they are talking about. If they are too lazy to say "Android 10", then just call it "10". Like they will eventually do with "11" or "12". Regrettably this includes some younger users -- even some Devs -- who came along recently and don't understand Google's historical naming convention. Starting with 2020 "Android 11", Google is ditching the beta "alphabet letter" entirely. It's simply called "Android 11 Developer Preview", and will be called Android 11 upon release. Same with 2021 "Android 12"... No more beta letters! But also no more dessert names, which were fun.
____________
But for those of you who don't know how it all worked over the past decade, read on...
When Google graduated an OS from beta to official release, they give it FULL name and a statue on Google Headquarters. The Naming/Statue Ceremony is a BIG deal and no one uses the beta letter again -- because it's officially out of beta.
"K", "L", "M", "N", "O", "P", "Q" were merely the beta letters before release and Google officially named them. I could go all the way back to beta "C" which became "Cupcake" -- but you get the point.
In the past, the official name was always a full dessert/snack name based on the beta letter. What the official name was going to be was always a matter of intense speculation in the months prior to release/naming ceremony and Google would often put false clues in the beta "letter" firmware. Only when the statue was revealed would you know the official name.
Beta "K" became "Kitkat" (Android 4.4, 2013) and got Kitkat statue
Beta "L" became "Lollipop" (Android 5, 2014) and got Lollipop statue
Beta "M" became "Marshmallow" (Android 6, 2015) and got Marshmallow statue
Beta "N" became "Nougat" (Android 7, 2016) and got Nougat statue
Beta "O" became "Oreo" (Android 8, 2017) and got Oreo statue
Beta "P" became "Pie" (Android 9, 2018) and got Pie statue
However, for Beta "Q" graduation, Google jettisoned the dessert name and only went with the version NUMBER, Android 10.
Beta Q became "Android 10" (2019) and got Android 10 statue.
It's no longer Q, because it's no longer beta OS. It's officially Android 10 with statue to prove it. If you speak of Q, you are talking about the beta firmware that came prior to "Android 10".
____________
WARNING: Sarcastic question ahead!
10) When I want to ask a question, I just post in the nearest thread I can find. Even if sort of on topic, I don't bother reading anything in that thread. Because my question is unique. No one in the past 3 years could have ever had a similar situation with this phone. Right?
Actually would be good for you to search relevant threads. 50 other people probably had the same issue, same question last year. Quick keyword search in a thread can give you immediate answer, without even posting your question. Besides simple keyword search, read the last few posts of a thread. Don't be narcissistic and assume ONLY YOU have ever encountered this issue or have this question. This phone was released in 2017 and I bet there's NOTHING we haven't seen, many times.
But if you have a question you can't find an answer for, ASK first in the Q&A forum before you screw up your phone. Those of us who have gone through it multiple times can help! You really don't want to 9008 brick your awesome phone... There's some actions even TWRP can't help you recover from.
* You need to be on Pie/Android 9 stock rooted firmware before attempting to install V30 AOSP/LOS-17 "Android 10" custom ROMs. V30 LOS-17 ROMs need LG stock Pie/Android 9 blobs (drivers) for everything to work right.
Click to expand...
Click to collapse
Can I flash TWRP flashable version or I need to use LGUP to install first?
Hello, when you say North american version, do you include Canadian H933 as well?
BeatNoMoreYT said:
Hello, when you say North american version, do you include Canadian H933 as well?
Click to expand...
Click to collapse
Tell me the context. Canada is in North America, so it is a North American variant, yes. Are you asking about this:
(WARNING: T-mobile H932 firmware is only compatible with T-mobile H932 phones. US998 firmware is NOT compatible with T-mobile H932 phones, but can be flashed to any other North American V30 variant).
Click to expand...
Click to collapse
ChazzMatt said:
Tell me the context. Canada is in North America, so it is a North American variant, yes. Are you asking about this:
Click to expand...
Click to collapse
Sorry for the late reply. I'm a Canadian and I got my h933 from Bell Mobility. It's currently on Android 9 and I'm not sure what to do.
BeatNoMoreYT said:
Sorry for the late reply. I'm a Canadian and I got my h933 from Bell Mobility. It's currently on Android 9 and I'm not sure what to do.
Click to expand...
Click to collapse
The reason I specifically say "North America" is to include Canada. Otherwise I would say U.S. The European and Asian V30 have some differences, but also use the WTF bootloader unlock method. However, the North American versions have to either be US998 or temporarily convert to US998 firmware because of the North American versions, only the US998 has the necessary fastboot flash commands. (The only North American variant which can NOT use WTF exploit is the T-Mobile H932, which has to use another method. Trying WTF on T-Mobile H932 will brick it.)
This sticky thread was locked as it's not meant for Q&A. I'm not sure why mods unlocked it. It's merely to inform people and point them to the OTHER relevant threads. If you have Canad H9333, then yu need to go to the WTF Instructions and follow those.
Rooting my phone wouLd make my phone exceedingly fast and it would
Take the phone to the next lev
ismazaki said:
Rooting my phone wouLd make my phone exceedingly fast and it would
Take the phone to the next lev
Click to expand...
Click to collapse
No. Wrong. Obtaining root privileges gives you the ability to modify the way the hardware and software interface and communicate. Many people 'break' or brick their smartphone because they want to 'make their phone faster.' Often root is more about a user (or customer) being given the ability and freedom to edit the hardware/software code exchange at various levels of Android OS architecture (code)
I have a lgv30 Verizon variant and I'd like to return it to stock and remove TWRP and relock the bootloader I'm trying to see if anyone can point me in the right direction its been a long time thank you.
DroidForLife33 said:
I have a lgv30 Verizon variant and I'd like to return it to stock and remove TWRP and relock the bootloader I'm trying to see if anyone can point me in the right direction its been a long time thank you.
Click to expand...
Click to collapse
I just answered you in the WTF thread. See my reply there.
As I mentioned to someone above, this sticky thread was locked as it's not meant for Q&A. I'm not sure how it got unlocked. It's merely to inform people and point them to the OTHER relevant threads.
I have Motorola Moto G7 Play XT1952-1 version
I discover my device have 32bit os version.
Stock 9.0 and 64bit ARMv8-A CPU.
I cant install cintra and Dolphin newest version.
Is there any chance to reflash stock moto g7 play dual 64bit rom?
All Moto G7 Play stock ROMs, including the stock ROM for the 3GB model, are 32bit. You will have to go the custom ROM route to get 64bit.
xtermmin said:
All Moto G7 Play stock ROMs, including the stock ROM for the 3GB model, are 32bit. You will have to go the custom ROM route to get 64bit.
Click to expand...
Click to collapse
Then i need to wait for any stable custom rom. Or sell this device and buy Moto G7 Power
Morricorne said:
Then i need to wait for any stable custom rom. Or sell this device and buy Moto G7 Power
Click to expand...
Click to collapse
Likelihood of a 64-bit ROM coming to this device is slim to none. Simply does not attract developer attention given modest specs (which another reason 64 bit makes little sense).
After scattering through a tonne of content on the internet and flashing multiple ROMs on my moto z2 play, I found AOSP extended GSI of android PIE and I am using it right now as my daily driver. It works 9/10 Anyone can daily drive it as long as you are not concerned about passing SafetyNet. However, while I was digging for some ROM that would officially support my z2 play(albus), I noticed one thing that Motorola Moto G5 Plus has a lot of support amongst custom roms. I may be missing some points cause I haven't been into flashing roms since some years now and I recently came back to the whole scene but is there a way that I can run a Custom rom (like Evolution X) on my albus using the build meant for Motorola Moto G5 Plus? Both of these phones have extremely similar specs and dimensions. z2 play was launched on 2017 June and Motorola Moto G5 Plus was launched on 2017 Feb.
Nick_101d said:
After scattering through a tonne of content on the internet and flashing multiple ROMs on my moto z2 play, I found AOSP extended GSI of android PIE and I am using it right now as my daily driver. It works 9/10 Anyone can daily drive it as long as you are not concerned about passing SafetyNet. However, while I was digging for some ROM that would officially support my z2 play(albus), I noticed one thing that Motorola Moto G5 Plus has a lot of support amongst custom roms. I may be missing some points cause I haven't been into flashing roms since some years now and I recently came back to the whole scene but is there a way that I can run a Custom rom (like Evolution X) on my albus using the build meant for Motorola Moto G5 Plus? Both of these phones have extremely similar specs and dimensions. z2 play was launched on 2017 June and Motorola Moto G5 Plus was launched on 2017 Feb.
Click to expand...
Click to collapse
According to this guide https://forum.xda-developers.com/z2-play/how-to/updated-guide-project-treble-gsi-t4063193
you can flash ANY GSI into the Z2 Play as long as they met these requirements:
1. Rom arch is arm64
2. Rom partition scheme is aonly
Most custom roms do not specify which partition scheme uses, in this post https://forum.xda-developers.com/z2...droid-q-gsi-moto-z2-play-albus-t4066945/page2 the user @saibharath1319 mentions he succesfully installed Pixel Experience Plus Android 10 GSI with KVT 2.4 "without any major issues besides ambient display not working.
????
leodexe said:
According to this guide https://forum.xda-developers.com/z2-play/how-to/updated-guide-project-treble-gsi-t4063193
you can flash ANY GSI into the Z2 Play as long as they met these requirements:
1. Rom arch is arm64
2. Rom partition scheme is aonly
Most custom roms do not specify which partition scheme uses, in this post https://forum.xda-developers.com/z2...droid-q-gsi-moto-z2-play-albus-t4066945/page2 the user @saibharath1319 mentions he succesfully installed Pixel Experience Plus Android 10 GSI with KVT 2.4 "without any major issues besides ambient display not working.
Click to expand...
Click to collapse
What he is asking and what your telling mate?? even i was searching for the same question moto g5 plus has tremendous support and both the devices are totally identical ? can someone give it a try?
Bro do you even read? The short answer is no, you can't simply flash sanders ROMs or any other, to albus. Unless they are GSI's.
If you don't have any idea what I'm talking about. Then google it.
If you are coming from Stock Pie Update make sure you use the modem file (non-HLOS.bin) from Stock Oreo because the modem from Stock Pie has audio issues with custom ROMs.