Database Users

Can't us with the Brazilian dual sim version of the XT1572 have Marshmallow and ROOT?

First, sorry for the weird question format. The space for the question is too limited IMO.
Why can't we get ROOT + Marshmallow on the brazilian dual sim version of the XT1572?
I tried:
1 - AOSP updating to Marshmallow, flashing newest twrp, flashing some boot_root.img and then flashing beta supersu. Issue: No carrier data (No phone, no 3g/4g).....
2 - Tried flashing different ROMs made for XT1572 (didn't specify dual sim, though, except for one) and XT1757, but... Issue: either it would not flash for some weird reason or I would have no WiFi/carrier data......
3 - Followed this guide ( http://forum.xda-developers.com/moto-x-style/general/how-to-flash-marshmallow-european-moto-t3253343 ) to go back to Lollipop and flash MM from the update provided, reflash twrp and supersu and ... Issue: No Wifi.........
Please shed some light on this dark path I've been in...

Bootloop on all nougat roms with moto x pure

Bootloop on all nougat roms with stock marshmallow rooted with TWRP . Every nougat rom I try to use I get a bootloop and I have no idea what to do to make them work. I'm using a moto x pure.
Sent from my XT1575 using XDA Premium HD app

A few things to check. What bootloader version are you on? It will show on the screen when you're booted to bootloader mode for fastboot flashing, and the date that shows up there can be useful for identifying which one it is. Or you can enter this in a terminal:
Code:
getprop ro.bootloader
, but it won't show the date.
What version of TWRP are you using?
Have you tried formatting internal storage? (obviously do appropriate backups off device first) Just a thought. I've had some roms fail to boot due to files and permissions problems leftover after a standard wipe for a clean flash, but that has always been on other devices. I've never run into it on a moto.

Same here Upgraded my Moto XT1752 to nugat, then unlocked bootloader, installed twrp, then rooted, and in the end only custom rom (tried only nugat based, except for flyme) working for me was flymeos based on android 6.x.x (it is for moto XT1750) and ofc recovery options :/ Tried different gapps and different approach to wiping (wipe all, then reset, wipe again and then install rom etc.)
Can it be baseband issue ? mine is M8992_1255331.29.01.88.07R_Clark_EMEA_CUST ?
edit:
My TWRP version is 3.1.1.0
edit2: k already found solution for the issue https://forum.xda-developers.com/moto-x-style/help/flash-android-7-x-x-based-custom-roms-t3633582

hm2014811 <-> wt88047 - I don't understand it

Hi,
I already read multiple threads which are somehow related to this issue, but I still don't really understand it:
What is hm2014811 and what is wt88047? Where is the difference? Really different devices? Or somehow Android 4 and 5? It would be great if someone could explain all the details (or direct me to some page/thread where it is explained). Is it important which TWRP version to use?
Here someone asks I have a HM2014811 does exist a way to install a WT88047 rom?
But I got a used Redmi 2 2014811 with 1 GB RAM, too, and can only install wt88047 roms, as it seems. Previously I had some MIUI 8.3 and it was too slow. Currently I'm trying Lineage OS 14.1. Could it be that all of them are designed for 2 GB RAM?
I have TWRP 3.0.2 from here.
I'd like to go back to Android 4, to see if the device gets faster. However, it tells me that the ROMs are for hm2014811 and I have a wt88047!
Since some threads seem to tell me that installing a different TWRP would change the device type, I tried to install this older TWRP 2.8.7.2. However, it doesn't boot. It stays at the "MI" in the center, and while that's still shown, I can access fastboot and install the above 3.0.2 again, which works.
Any explanations, suggestions? What clean and fast Rom should I install on my 1 GB device, and how?
Thanks a lot,
Alex

[SOLUTION] - for error hm2014811
Hello,
Here is how it works:
Use this TWRP image: twrp-3.3.1-0-wt88047.img
Flash the recovery image like so:
1. fastboot devices
2. fastboot flash recovery twrp-3.3.1-0-wt88047.img
3. fastboot boot twrp-3.3.1-0-wt88047.img
4. Wait as the phone reboots into the newly flashed TWRP recovery
5. in TWRP recovery on the phone go to Advanced -> ADB sideload and enable it
on the PC run:
adb sideload lineage-15.1-20200119-nightly-wt88047-signed.zip
Good luck!

Alex1a said:
Hi,
I already read multiple threads which are somehow related to this issue, but I still don't really understand it:
What is hm2014811 and what is wt88047? Where is the difference? Really different devices? Or somehow Android 4 and 5? It would be great if someone could explain all the details (or direct me to some page/thread where it is explained). Is it important which TWRP version to use?
Here someone asks I have a HM2014811 does exist a way to install a WT88047 rom?
But I got a used Redmi 2 2014811 with 1 GB RAM, too, and can only install wt88047 roms, as it seems. Previously I had some MIUI 8.3 and it was too slow. Currently I'm trying Lineage OS 14.1. Could it be that all of them are designed for 2 GB RAM?
I have TWRP 3.0.2 from here.
I'd like to go back to Android 4, to see if the device gets faster. However, it tells me that the ROMs are for hm2014811 and I have a wt88047!
Since some threads seem to tell me that installing a different TWRP would change the device type, I tried to install this older TWRP 2.8.7.2. However, it doesn't boot. It stays at the "MI" in the center, and while that's still shown, I can access fastboot and install the above 3.0.2 again, which works.
Any explanations, suggestions? What clean and fast Rom should I install on my 1 GB device, and how?
Thanks a lot,
Alex
Click to expand...
Click to collapse
Here's the answer for "What is hm2014811 and what is wt88047? Where is the difference? Really different devices? Or somehow Android 4 and 5?"
HM2014811 is the model of the 2014811 Xiaomi Redmi 2 variant. wt88047 is the codename of Redmi 2.

LineageOS on a vzw Galaxy S5?

Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.

androidman807 said:
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
Click to expand...
Click to collapse
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.

I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
KazuDante said:
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
Click to expand...
Click to collapse

androidman807 said:
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
Click to expand...
Click to collapse
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3

Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
KazuDante said:
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse

androidman807 said:
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
Click to expand...
Click to collapse
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.

A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
KazuDante said:
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
Click to expand...
Click to collapse

androidman807 said:
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
Click to expand...
Click to collapse
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap

Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
KazuDante said:
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Click to expand...
Click to collapse

androidman807 said:
Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
Click to expand...
Click to collapse
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.

Thanks anyway. It seems it should work, since safestrap won't disappear. Maybe I should post a new thread. Thank you again for all your time.
KazuDante said:
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Click to expand...
Click to collapse

I am also essentially looking to install LineageOS on my Galaxy S5, but before proceeding, I just wanted to make sure that what I'm looking to do is correct. Currently I am running an old version of PhoenixROM with an old unlocked bootloader. I know that I will need to update the bootloader in order to prevent issues, such as wifi not working.
Should all I need to do is follow JKruse's instructions here, flashing LineageOS as the last and final step? I'm hoping that it is this easy, but I do have my doubts and that is why I am asking on here for advice.
Thank you to all in advance!

LG G4 [H815] with LineageOS 15.1 [Unofficial]

Hello my Friends
I have a LG G4 H815 with LineageOS 15.1 ROM. Sometimes it happens that my smartphone crashes and a blue screen appears. I can not reproduce this error because it just happens sporadically and I do not know the cause. I flashed LineageOS 15.1 UsU and wanted to ask if that was related to it. I did not flash a UsU kernel.

alexejalexej said:
Hello my Friends
I have a LG G4 H815 with LineageOS 15.1 ROM. Sometimes it happens that my smartphone crashes and a blue screen appears. I can not reproduce this error because it just happens sporadically and I do not know the cause. I flashed LineageOS 15.1 UsU and wanted to ask if that was related to it. I did not flash a UsU kernel.
Click to expand...
Click to collapse
If you installed the LineageOS 15.1 UsU version of the rom, you shouldn't need to flash the kernel as it is built-in to the rom. If you flashed the non-UsU version, then you will have to flash the kernel.
Check FAQ # 5a) - 5e) in the UsU thread for some additional solutions.

sdembiske said:
If you installed the LineageOS 15.1 UsU version of the rom, you shouldn't need to flash the kernel as it is built-in to the rom. If you flashed the non-UsU version, then you will have to flash the kernel.
Check FAQ # 5a) - 5e) in the UsU thread for some additional solutions.
Click to expand...
Click to collapse
Thanks for this information but what could it be that my system sometimes crashes? By the flashing process, everything worked fine. :\

alexejalexej said:
Thanks for this information but what could it be that my system sometimes crashes? By the flashing process, everything worked fine. :\
Click to expand...
Click to collapse
There are a lot of regional variations in the H815 - you use the H815 UsU rom if you had to unlock unofficially with steadfasterX\s UsU method but if you unlocked officially through the LG Development site you use the H815 non-UsU rom version.
The reasons listed in the FAQ I referred you to in the UsU thread are the main potential causes of what you are experiencing, provided you are not beginning to see the initial signs of the G4 ILAPO (you can search for it on XDA or google it) hardware issue if on an earlier G4 model.
That said, I would do the flashing process again EXACTLY as follows (i.e., a clean flash):
- remove your lock screen password.
- boot into the latest preview TWRP O version (install it if you haven't already): wipe Cache, Dalvik cache, System and importantly , format data > Yes (make sure you have backed up your data first & copied your SD data - pictures, videos, etc. to your PC).
- flash the appropriate H815 rom (UsU or non-UsU)
- flash OpenGapps (arm64)
- reboot to the bootloader/fastboot screen and flash the Marshmallow (MM) modem.bin file from your SALT backup (if you don't have a backup, get/download a copy of your original rom and extract it using only SALT.
Reboot again and test.
Note: Don't forget to click the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.

sdembiske said:
alexejalexej said:
Thanks for this information but what could it be that my system sometimes crashes? By the flashing process, everything worked fine. :
Click to expand...
Click to collapse
There are a lot of regional variations in the H815 - you use the H815 UsU rom if you had to unlock unofficially with steadfasterX\s UsU method but if you unlocked officially through the LG Development site you use the H815 non-UsU rom version.
The reasons listed in the FAQ I referred you to in the UsU thread are the main potential causes of what you are experiencing, provided you are not beginning to see the initial signs of the G4 ILAPO (you can search for it on XDA or google it) hardware issue if on an earlier G4 model.
That said, I would do the flashing process again EXACTLY as follows (i.e., a clean flash):
- remove your lock screen password.
- boot into the latest preview TWRP O version (install it if you haven't already): wipe Cache, Dalvik cache, System and importantly , format data > Yes (make sure you have backed up your data first & copied your SD data (pictures, videos, etc.) to your PC.
- flash the appropriate H815 rom (UsU or non-UsU)
- flash OpenGapps (arm64)
- reboot to the bootloader/fastboot screen and flash the Marshmallow (MM) modem.bin file from your SALT backup (if you don't have a backup, get/download a copy of your original rom and extract it using only SALT.
Reboot again and test.
Note: Don't forget to click the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Wow! Thank you for your detailed explanation. I will try what you have described. FYI: I have unlocked my LG G4 official, via the lg developer page. Afterwards I received the unlock.bin file by e-mail and was able to unlock the bootloader without any problems.