I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping .. And I need to add virtual navigation buttons because the capacitive navigation buttons are failing and I need add in the build.prop.
I would be really happy if someone help me with a flashable [slim] stock rom or in any other way.
Thank you in advance for the help.
I'm using bhb27's CrDroid and it comes rooted and has on-screen navigation buttons in the CrDroid settings. Just follow the directions here: (https://forum.xda-developers.com/mo...crdroid-android-t3491257/page144#post71458779).
Guth13 said:
I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping.
Click to expand...
Click to collapse
Are you using the correct SuperSu? You're using my guide?
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
If so, then you know with stock Marshmallow from Motorola you NEED a specific beta version of SuperSu for initial root. AFTER that, then you can update to newer versions of SuperSu. Go read that guide if you haven't. It was updated when Motorola released Marshmallow last July (2016).
I do have images with very old TWRP in another thread, but they're 4.4.4 Kitkat images from 2 years ago...
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
Be better if you flashed newer TWRP and used the correct SuperSu.
I use this method but I can not understand why infinite looping.
Do you have the rom 6.0.1 with patch of January (2017) ??
Would you like to do something like that in a ROM compatible with our device ??
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
Guth13 said:
I can not install twrp recovery and make root (supersu) in the marhsmallow rom stock of my xt1225, when I install twrp and do root I have an eternal looping ..
Click to expand...
Click to collapse
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Also post a screenshot of the TWRP version you are using, please.
Guth13 said:
And I need to add virtual navigation buttons because the capacitive navigation buttons are failing and I need add in the build.prop.
I would be really happy if someone help me with a flashable [slim] stock rom or in any other way.
Click to expand...
Click to collapse
2) If you want virtual navigation buttons, the easiest way is to install a custom ROM like RR 6.X or even a Nougat custom ROM -- not a stock-based ROM. Virtual buttons are an option in many, if not all the Quark custom ROMs.
3) Right now with TWRP you can flash any of the custom ROMs. You don't need to flash SuperSu. In fact on the RR 7.X, @bhb27 doesn't like SuperSu. You can get root from within the ROM if you want it on 6.X or 7.X ROMs.
4) Tell me why you think a slim stock ROM is what you need. Everything you have said so far points to a custom ROM.
Flashable stock ROMs are mostly for people who either get a custom ROM (LG devices where the bootloader is locked, but they can still get root and flash "images") or stock has some feature like VoLTE that can''t be ported over to custom ROMs (yet). That's the reason for the Verizon stock based ROM you mention below. Even then, many Droid Turbo users are still flocking to the custom ROMs because custom ROMs offer more features than stock -- even Verizon customers who could use VoLTE.
Why do you think there are SIX custom Nougat ROMs for the Quark? And in this forum there are NO "stock-based" ROMs? The only reason there's stock-based ROM over in the Droid Turbo section is because of Verizon VoLTE.
Back in late 2014 and early 2015 I had rooted stock ROM only because there were no custom ROMs. I ran xposed with Gravity Box to emulate a ROM.
I even flashed my Puerto Rico XT1225 and Mexico XT1225 to India Moto Turbo firmware so I could get 5.0.2. Motorola didn't release 5.0.2 until later for the Latin America XT1225, but it launched on Moto Turbo XT1225 in March 2015.
We then got CM12, and CM12.1. When CM12.1 was stable enough, I switched over and stayed on it for well over a year.
I wouldn't go back to stock if you paid me.
Guth13 said:
Would you like to do something like that in a ROM compatible with our device ??
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
Click to expand...
Click to collapse
Because custom ROMs are much better.
Do what I said up top, post the screenshots -- let's figure out your Supersu issues if you want, but it's not necessary to have root before flashing a custom ROM. And once a custom ROM is flashed, there's a root switch built in to most.
ChazzMatt said:
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Also post a screenshot of the TWRP version you are using, please.
2) If you want virtual navigation buttons, the easiest way is to install a custom ROM like RR 6.X or even a Nougat custom ROM -- not a stock-based ROM. Virtual buttons are an option in many, if not all the Quark custom ROMs.
3) Right now with TWRP you can flash any of the custom ROMs. You don't need to flash SuperSu. In fact on the RR 7.X, @bhb27 doesn't like SuperSu. You can get root from within the ROM if you want it on 6.X or 7.X ROMs.
4) Tell me why you think a slim stock ROM is what you need. Everything you have said so far points to a custom ROM.
Flashable stock ROMs are mostly for people who either get a custom ROM (LG devices where the bootloader is locked, but they can still get root and flash "images") or stock has some feature like VoLTE that can''t be ported over to custom ROMs (yet). That's the reason for the Verizon stock based ROM you mention below. Even then, many Droid Turbo users are still flocking to the custom ROMs because custom ROMs offer more features than stock -- even Verizon customers who could use VoLTE.
Why do you think there are SIX custom Nougat ROMs for the Quark? And in this forum there are NO "stock-based" ROMs? The only reason there's stock-based ROM over in the Droid Turbo section is because of Verizon VoLTE.
Back in late 2014 and early 2015 I had rooted stock ROM only because there were no custom ROMs. I ran xposed with Gravity Box to emulate a ROM.
I even flashed my Puerto Rico XT1225 and Mexico XT1225 to India Moto Turbo firmware so I could get 5.0.2. Motorola didn't release 5.0.2 until later for the Latin America XT1225, but it launched on Moto Turbo XT1225 in March 2015.
We then got CM12, and CM12.1. When CM12.1 was stable enough, I switched over and stayed on it for well over a year.
I wouldn't go back to stock if you paid me.
Because custom ROMs are much better.
Do what I said up top, post the screenshots -- let's figure out your Supersu issues if you want, but it's not necessary to have root before flashing a custom ROM. And once a custom ROM is flashed, there's a root switch built in to most.
Click to expand...
Click to collapse
I use RR 5.7.4 based on android 6.0.1 but I'm going to give this device to my mother because I bought a LTE MI4. And a slim rom stock I would add a navbar using a tutorial I saw on youtube. She already used and complained that the custom rom unloads very fast and takes time to load but her main complaint was of force closed. I can not report the closed forces because I use themes and applications with root access as well as I already got to use xposed in a RR (I am not currently using and I still suffer enough closed forces and other bugs). And I also believe that a slim rom stock would be very useful for a lot of us users. I've had several devices and have always seen a flashable rom stock and sometimes with a slim version.
I know how to install twrp, do root and use xposed but I can not do such thing in rom stock since its version with pacth of September 2016 (recently released with patch in January 2017) and in turn I could not do in previous version of android 6.0 .1. And my device has problems with the capacitive buttons.
I also tried copying the build.prop edit (added the capacitive buttons) and flashing via twrp but with no success. I've always used the official twrp. Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Guth13 said:
I use RR 5.7.4 based on android 6.0.1 but I'm going to give this device to my mother because I bought a LTE MI4. And a slim rom stock I would add a navbar using a tutorial I saw on youtube. She already used and complained that the custom rom unloads very fast and takes time to load but her main complaint was of force closed. I can not report the closed forces because I use themes and applications with root access as well as I already got to use xposed in a RR (I am not currently using and I still suffer enough closed forces and other bugs).
Click to expand...
Click to collapse
Sounds like you need to do a clean install of the ROM? My wife and I are using RR 6.X Marshmallow on two XT1225 and we don't have any force closed apps. In fact it's so stable that's why I don't want to go to Nougat right now and I hope @bhb27 does at least one more update of that ROM.
In TWRP, you can clear all caches and reboot and that may help your issue, but since you are giving the phone to your mother, just do a clean install.
That RR 6.X ROM also lets you do virtual buttons. Have you tried using that feature?
Guth13 said:
I know how to install twrp, do root and use xposed but I can not do such thing in rom stock since its version with pacth of September 2016 (recently released with patch in January 2017) and in turn I could not do in previous version of android 6.0 .1.
And my device has problems with the capacitive buttons.
I also tried copying the build.prop edit (added the capacitive buttons) and flashing via twrp but with no success. I've always used the official twrp. Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
I'm a little confused here. Are you saying you want to go to a previous version of Marshmallow but can't? You obviously have an unlocked bootloader. You can even flash Kitkat if you wish, just omit gpt.bin.
Some patch from Motorola means nothing. You have an unlocked bootloader. You have god powers. I'm not sure why you are blaming some patch on not being able to root an unlocked bootloader phone. No one else has this issue.
You say you know how to root, but I have my doubts since you are having trouble flashing the version of SuperSu which is needed. Have you ever rooted stock Marshmallow on this Motorola device? When you unlocked your bootloader, what version of stock firmware were you on? Lollipop? The procedure has changed. That's why I want to see a screenshot of the version of SuperSu in your download folder you are trying to flash over your stock Marshmallow ROM. You can only root with ONE specific SuperSu version and you haven't convinced me you are using that version.
Guth13 said:
Do you think that if I use a twrp mod (has topic here in xda) can solve my problems ??
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
Modded TWRP is always better than "official" TWRP. Until the recent 3.1 update, the official version was almost a year behind the modded versions. Even now, the modded version can do more stuff.
This is the most recent version as of the date I type this:
twrp-3.1.0-MOD_1-quark.img
https://www.androidfilehost.com/?fid=457095661767143958
This is the SuperSu version you should be using and ONLY this version until you achieve initial root. After you have initial root and reboot back and verify, then you can update to newer versions of SuperSu.
Download
BETA-SuperSU-v2.62-3-20151211162651.zip
Guth13 said:
Do you disagree that a flash rom [slim] stock would be a way to reinstall the original rom even faster ??
Click to expand...
Click to collapse
Why is how fast you install a ROM the question? How about how the ROM runs, what features it has?
Then why not flash @iiWoodstocK's stock ROM in TWRP? It's based on Brazil stock Marshmallow, but he adapted it so it would install/run on all Quarks, including the Droid Turbo.
[ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable]
Stock 6.0.1 MPG24.107-70.2 (Brazil) for Verizon XT1254
http://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
You keep the radio you already have, but in TWRP you can flash that ROM and have stock Marshmallow Motorola firmware.
That ROM will work on all Quarks (XT1254/XT1250/XT1225). It has a custom kernel, and uses whatever radio you already have. But @iiWoodstocK made it specifically to work on the XT1254, since at that time Verizon had not yet released stock Motorola Marshmallow for the Verizon Droid Turbo.
He includes a script to run which debloats the ROM somewhat to remove apps most people don't need. Go to the thread and read. He obviously directed it to Droid Turbo users, to give them "stock" Marshmallow since it was MONTHS before Verizon did, but it will also work on XT1225.
However, it won't help you use virtual buttons instead of capacitive buttons like a custom ROM will, unless you install something yourself that does that. Custom ROMs like RR already have that functionality built in.
But it's a TWRP flashable stock ROM, which is what you seem to want for reasons I don't understand.
Now you may have solved the problem, I did not know there was a specific version of the supersu. The supersu I wore was the "SuperSU-v2.79-201612051815". I will now test this supersu that indicated me and I will come back to give the feedback. I always do a clean flash of rom marking all the sections restarting recovery, avoiding and doing rom flash, gapps and any necessary file after ..
Guth13 said:
Now you may have solved the problem, I did not know there was a specific version of the supersu. The supersu I wore was the "SuperSU-v2.79-201612051815". I will now test this supersu that indicated me and I will come back to give the feedback. I always do a clean flash of rom marking all the sections restarting recovery, avoiding and doing rom flash, gapps and any necessary file after ..
Click to expand...
Click to collapse
I said it many times. You aren't listening. That's why i asked to see screenshot for you to prove to me you were using the right version!
This was my original post to you and even the follow-up:
ChazzMatt said:
Are you using the correct SuperSu? You're using my guide?
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
If so, then you know with stock Marshmallow from Motorola you NEED a specific beta version of SuperSu for initial root. AFTER that, then you can update to newer versions of SuperSu. Go read that guide if you haven't. It was updated when Motorola released Marshmallow last July (2016).
Be better if you flashed newer TWRP and used the correct SuperSu.
Click to expand...
Click to collapse
Yes, all that important stuff was bolded and capitalized on that day.
You replied YES, you were using that.
ChazzMatt said:
1) But you can install TWRP recovery, right?
It's just the SuperSu you are having trouble flashing? Please post a screenshot of the SuperSu file you are trying to flash. It should be in your Download folder. This would be the SuperSu file you are trying to "install" in TWRP.
Click to expand...
Click to collapse
But I didn't believe you so I asked for a screenshot of the SuperSu you were using -- and you still said you knew what you were doing. And you wouldn't provide the screenshot, which made me very suspicious.
ChazzMatt said:
I said it many times. You aren't listening. That's why i asked to see screenshot for you to prove to me you were using the right version!
This was my original post to you and even the follow-up:
You said YES, you were using that.
But I didn't believe you so I asked for a screenshot, and you still said you knew what you were doing.
Click to expand...
Click to collapse
Congratulations my friend!! You solved my root problem. But
Why only this supersu version compatible?
And why can not I make any changes to build.pop?
Example:
Change DPI - ro.sf.lcd_density = 550
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
rooting Motorola Marshmallow 6.0.1 firmware
Guth13 said:
Congratulations my friend!! You solved my root problem.
But why only this supersu version compatible?
Click to expand...
Click to collapse
Well, I solved it April 7, the very day you posted. It just took until April 12 for me to repeat it two more times for you to actually listen.
Using so-called stable or even newer SuperSu for initial root will cause bootloops for Motorola Marshmallow 6.0.1. Only that older beta SuperSu works on many Motorola Marshmallow firmware. I'm not going to say "all" Motorola Marshmallow firmware -- but many, many, many. AFTER you get initial root and confirm that status (after reboot), then you can update to newest SuperSu. It's only an problem on initial (first) root.
We discovered it in the Moto Quark (Moto Maxx/Moto Turbo/Droid Turbo) phones, as well as Moto Kinzie (Moto X Force), and here's even a thread for 2015 Moto G3 with the same issue:
How to get root 2015 Moto G3 With Stock Android Marshmallow 6.0 (XT1541)
https://forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113
I wrote the bootloader unlock and rooting guide for the 2014 Moto XT1225 and Moto XT1250 (Moto Turbo/Moto Maxx) and it's in there.
UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root
https://forum.xda-developers.com/showthread.php?t=3455341
Months later when the sibling Quark Droid Turbo XT1254 was updated to Marshmallow, that beta SuperSu requirement still applied.
[GUIDE] How to unlock your Droid Turbo bootloader, install TWRP and gain root access
https://forum.xda-developers.com/showthread.php?t=3292684
Also applies for 2015 Kinzie, the Moto X Force (sibling to the Droid Turbo 2)...
[ROOT][INFO][MARSHMALLOW] How to Root Moto X Force 6.0 [TESTED]
https://forum.xda-developers.com/droid-turbo-2/general/root-how-to-root-moto-x-force-6-0-t3282151
and probably many other Motorola phones.
With the Quark phones, we first discovered it with Moto Maxx/Moto Turbo XT1225 in July 2016. I updated my bootloader unlock/TWRP/root GUIDE for the XT1225 to include that information specific to stock Motorola Marshmallow firmware. The XT1250 Moto Maxx has still not received official Marshmallow but it will apply to them also if/when it happens.
THEN, in December 2016 when the Droid Turbo XT1254 got Marshmallow they ran into the same problem -- but the XT1225 is identical Quark phone except for radio (and the Droid Turbo has a Verizon-mandated locked-down bootloader which has to be jimmied with Sunshine). We XT1225 owners already knew what to do and told them! So, @TheSt33v updated his Droid Turbo guide to convey the same information.
It was the first thing I told you if you look back up the this post thread. I asked if you were using the correct SuperSu for Motorola Marshmallow and that the procedure had changed, so my guide was updated in July 2016 to reflect that. That's why I even put "UPDATED" in my guide title. And I also said after you get initial root (and confirm), then you can update the SuperSu to newest if you wish.
_____________
Guth13 said:
And why can not I make any changes to build.pop?
Example:
Change DPI - ro.sf.lcd_density = 550
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
Click to expand...
Click to collapse
What build prop editor are you using? I use this one:
BuildProp Editor
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en
You also have to give your build prop editor app root privileges in SuperSu. Go into the SuperSu settings and see all the apps which have root approval. In the SuperSu logs you can also see the apps which had been denied root privileges. In the SuperSu app settings, I always change the pop up root request to "30 seconds" so I am sure to see the root request.
Do NOT try to do both build prop changes at the same time. Let's keep it simple. Do the DPI change first, reboot, see if it took effect, then do the other. You can easily mess up your phone trying to do too many changes at the same time.
Make sure you have a TWRP backup before doing any build prop changes. It might be the ONLY way to recover from a disaster.
1) DPI
Be careful about messing up your display. For instance Motorola stock Quark DPI is 640, which I actually prefer. But @bhb27 and other ROM developers make the DPI smaller to a default 560 DPI. For instance, in Resurrection Remix in Settings/Display here's the choice to go larger and smaller, if you wish.
{
"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"
}
But 550 is NOT one of those choices. Maybe that's a strange DPI our 1440p AMOLED displays can't handle? Try 560 and see what happens. If it still doesn't change, we'll discuss further.
2) VIRTUAL KEYS
Guth13 said:
And why can not I make any changes to build.pop?
Adding virtual navigation buttons - qemu.hw.mainkeys = 0
Click to expand...
Click to collapse
You are SURE this is the correct command for our Quarks? There's TWO different commands for virtual button prop edits for Android phones all over the internet:
http://forums.androidcentral.com/showthread.php?t=390680&p=5262529&viewfull=1#post5262529
qemu.hw.mainkeys=0
if this doesn't work for you,
try this one :
same thing do this at the end of your build prop.
"ro.show.navigationbar=yes"
(without the quotes)
save changes, before you close.
Reboot.
to disable, just type "no" in stead of yes.
(without the quotes, again.)
Click to expand...
Click to collapse
Which one works with our Quarks? I don't know. Also mentioned in this article:
Disable or Enable The On-screen / Virtual Software keys In Android!
http://www.gizbeat.com/2021/disable-or-enable-the-on-screen-virtual-software-keys-in-android/
I haven't found either command in my build prop editor on Resurrection Remix -- a ROM which allows virtual buttons to be enabled. Maybe because I haven't actually enabled virtual buttons and the ROM would add those commands when I did so? Anyway try BOTH commands -- but not at the same time! Try one, reboot. If it doesn't work, try the other. You may have to add the lines manually in edit mode, but again make a TWRP backup first before making any changes.
If neither command works, then you'll have to ask one of the Quark ROM devs what command they use to permit virtual buttons to be enabled.
ChazzMatt said:
But 550 is NOT one of those choices. Maybe that's a strange DPI our 1440p AMOLED displays can't handle?
Click to expand...
Click to collapse
Android and our display will probably use anything (well, within reason, someone should try 100) we throw at it...a perk of having pixels for days.
Insistence on increments of 40 could be a scaling thing for touch detection. I was trying to use odd numbers between 480 and 520 in 7.1 to start with, and it badly screwed up DPI-specific apps (most notably Moto Camera's touch regions were off enough that the tutorials couldn't all be skipped). I finally stopped trying to be a rebel and settled on 480, and while the touch regions are still very slightly off, they're close enough to use without any difficulty.
Related
General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
LastStandingDroid said:
General Lollipop Information Thread​
Since many users asking the same questions over and over again i'm going to start with many "basics" answers for you
Why? because you guys won't use the search button :silly:
Can i revert back to kitkat safely?
Yes And No, If you have upgraded the bootloader.
If you have upgraded with Bootloader you might have some IMEI issues, And afaik there is none that has fixed this. Thus who hasn't updated the booloader can still revert back.
I got no baseband or WIFI
Go to More > About Device
Scroll down until you see baseband. if you don't have HOA7 in the end that means you're wifi won't work with stock kernel
Make sure that you always read the OP and if OP hasn't stated it, you need to update your modem and NON-HLOS.bin
Make sure to uncheck auto reboot before flashing!
Battery life is terrible
Yeah ofc you haven't had the rom for more than x days so it hasn't been fully set.
Can i use CF-Auto Root
NO! People who used this also flashed update-su in recovery, however flashing CF-Auto root isn't needed and it will not work due to old binaries.
How can i root?
http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
Why does X And Y FC
because you didn't provide logcat.
Why does it takes 2x minutes for it to boot first time?
because samsung made some changes which i can't tell, i've never seen such a slow upgrading screen on lollipop neither on stock versions.
Click to expand...
Click to collapse
Can u port soundcamp to s4 ?
i've flashed cf autoroot and it works perfectly
i did a completly downgrade,also bootloader and no issues
Sent from my GT-I9505 using XDA Free mobile app
i have installed official lollipop 5.0.1. If I root my phone, I will be able to flash official updates from samsung in the future? or I won't because of triggered knox
ViPER4Android
I managed to install Viper as system app but problem is How do I Activate it? In Sound settings there is No Music fx, (although it's installed), so I don't have the option switch Viper on, let only see Adapted Sound and in custom profile doesn't select it either. Am I missing something or is it because this update is so terrible
great info Droid! saw this thread in your signature
Revert from LL 5.0.1 to KK 4.4.2 is possible even if you flashed the Bootloader!
Personaly tested and working like charm!
No IMEI lost, no issues soo far found....
re
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Xain47 said:
Is it possible to flash i9506 lollipop ROM on E330S?........... They are same hardware wise?
Click to expand...
Click to collapse
yeah..they are the same but i don t know if modems are diferent. i think you should not flash i9506 on E330s
Hi my friend has un-locked his phone (Moto g 2015 XT1451) and installed Resurrection Remix rom (Not sure which version number) and cannot get pokemon go to work. I believe this is due to android safety net.
Is there a custom rom that will work with pokemon go?
He is not fussed about having root.
The RR rom is on android 6.0.1.
Has TWRP for recovery.
Looked into flashing stock image but he has had his screen changed and there are some posts advising they had problems due to not having the original screen fitted.
Any suggestions of roms that will work on the newest pokemon go would be much appreciated
Thanks in advance
ugg
uggitt said:
Hi my friend has un-locked his phone (Moto g 2015 XT1451) and installed Resurrection Remix rom (Not sure which version number) and cannot get pokemon go to work. I believe this is due to android safety net.
Is there a custom rom that will work with pokemon go?
He is not fussed about having root.
The RR rom is on android 6.0.1.
Has TWRP for recovery.
Looked into flashing stock image but he has had his screen changed and there are some posts advising they had problems due to not having the original screen fitted.
Any suggestions of roms that will work on the newest pokemon go would be much appreciated
Thanks in advance
ugg
Click to expand...
Click to collapse
Stock... and not rooted unless rooted with the Magisk systemless root and root is hidden from Pokemon Go.
The problem is Niantic restricted rooted devices from playing Pokemon Go, most ROMs have root baked in and flashing a new one doesn't hide the existing one, so for the most part stock is the only ROM that works.
When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..
All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.
Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.
Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.
I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.
Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.
I figured out a way to get Android 7.0 on my Moto X Pure XT1575. These are the steps I did to get it working. I restored my moto x pure to stock android 5.1.1 then took all the OTA updates to the latest OTA version to Android 6.0. After I reinstalled TWRP and Installed the Moto X Style OTA update extracted from the XT1572 version. It worked perfectly fine except for dialing out in the U.S. I fixed this by installing the Band 12 OTA Modem update for the Moto X Pure. After that everything worked fine and everything is really fast compared to other roms. The only thing that does not work is Android Pay because I unlocked my bootloader but you could fix this buy just installing the stock bootloader and locking it. If you go to about device it says it is a Moto X Style but that is because you're basically running Moto X Style 7.0 OTA update. I made a TWRP backup of it and you can download and restore the backup to your device. This is meant for the Moto X Pure XT1575. This will work! This is my first ROM/Back Up post and I hope this works if it does not please leave a comment. I highly recommend to make a backup before you try this.
Make sure to fully wipe wipe your device before you restore the backup. Make Sure to rename the "Your Serial Number Here" folder to the Serial number of your Moto X Pure into the TWRP backup file you downloaded. Put the Backup folder into your TWRP folder on your device the directory should be this: TWRP/BACKUPS/YOUR SERIAL NUMBER/1970-01-02-06-22-57_NPH25.200-15. Then go to TWRP on your device and tap restore then the "1970-01-02-06-22-57_NPH25.200-15" restore this and it should work. It also will use the Pixel bootup screen instead of the moto boot screen. Feel free to flash your own boot screen.
Download the backup here:
drive.google.com/open?id=0B23tafesCDLcRDN6SWRHeE9xWWM
Sooo... basically you are telling us you have done what dozens of other users have done, except you went through an unnecessary OTA chain process prior to doing it and then flashing an older modem firmware?
Not trying to burst your bubble here, and I mean no offense, but did you read any of the Nougat threads here? Pure users have been doing this, and telling others how to do it, since the first Latin America OTA's were released a month or so ago.
Unless I am missing some secret nugget of info here, which is possible I suppose.
Apart from creating more than one thread and abandoning one ("Test" - now magically evaporated) and then deciding to use a ridiculous font size (now corrected) you also post about something that is old news.
Closed to preserve the sanity of many.
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631
wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.
Awesome work! I've finally got me a full featured daily driver
I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...
After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.
Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk
I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..
This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.
I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.
Any update?
pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.
won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.
Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.