Hi there.
I just wanted to know does anyone tested flashfire app to work with our device
(Moto g 2015 8/16gb)
I have used the app on amazon fire 7 2015 (ford) device and it's working like charm.
Wonder if anyone tried be brave enough to have a go.
For those who don't know this app let's you install custom ROMs without recovery. Only thing required is root.
No not yet because a tried it with my nvidia k1 tablet and almost bricked the damn thing
flashfire is working
it has been a while since i asked this question and because there was not answer i give it a go.
recently i installed cyanogenmod 13 on my device, because i converted my sdcard as internal storage i couldn't flash ota updates with cyanogenmod recovery. so i decided to come back to twrp which was working fine.
however twrp was for some unknown reason booting only to splash screen and then hang for ages without response. i've tried many tricks but nothing worked. after few attempts of flashing twrp again and again with many build numbers and no success i looked on my fire 7 tablet and there was my answer.
Flashfire app.
http://flashfireapk.com/
Unfortunately because of cyanogenmod os selinux is set to enforcing which is not letting flashfire app to operate.
Good old Google search send me to app that can change this setting to permissive.
https://f-droid.org/repository/browse/?fdfilter=selinux&fdid=com.mrbimc.selinux -
This app after acquiring root permission gave me option to change it. After that i was able to use flashfire app properly
I will not get into details how to use this app as there are many tutorials how to do it
here https://youtu.be/p0q0ytHkzoI - to point one
Anyway i was able to flash cyanogenmod 13 without recovery.
now i don't know if it will work on all devices my one is xt1542 uk model.
please let me know if you managed to succeed too. - we need to let people know it is much simpler than using recovery, it can even flash ota's.
Here is a proof
View attachment 3786839
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.
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.
hi everyone, I am new to this forum.
i've been interested in rooting / mods for my old Samsung s9 to give it a new life.
I did so by rooting it using the TWRP app in combination with the Magisk V23.0
now what happened was that i was downloading some random apps yesterday and for some reason the phone went on bootloop...
i accidentally deleted the system without making a backup lol... a little stupid of me...
now it keeps telling me that i've no OS on my phone. i was thinking that i could easily find the ''un-edited'' or simple version of my original OS. but i've looked through many sites without succes.. either looks 2 good to be true or just fake...
is there anyone who can advise me on what to do? i just want my phone to work with any OS right now... but which one is the cleanest or best to use? i do prefer a newer os like 10
thanks in advance!
If you still have access to recovery mode, your best choice would probably be installing LineageOS. It's the most lightweight ROM and many ROMs are based on Lineage. From what i can see, your phone is no longer officially supported.
I found this one based on Lineage 18.1 (Android 11). Before installing, take a look at the bugs, working, and installing sections.
And don't forget to install the Google Apps after installing the system and before rebooting.
that looks crispy. i appreciate your quick & good advise. can you tell me wether i can still run Magisk on it?
Yes, you can still flash Magisk or any type of root with both the OS and the GApps.
what i'm consider about is, wether a region code CRC matters?
The 2117 model is not mentioned in official compatibility, but all the others are. Any Tmobile users running Lineage or know if it works?
I used it for a bit. Works good as any other device IMO.
Follow This guide on the official page.
Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.
TimmyP said:
Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.
Click to expand...
Click to collapse
Lineage updates the firmware as part of the install.
Ah thank you! Ill prolly do it after some time. I'm completely happy on 11 for now. Have it debloated and set up with xposed modules and everything.
I've used lineage before on the le2117 but decided to switch to evolution x since it's packed with features
What the battery life like between the two? I dont necessarily need features since I add everything I need with magisk\lsposed. This stock rooted rom Im on now is getting great battery life.
On both installation pages for this and EvoX, it says you need to be on A13 firmware. Is this a hard requirement? Or can I truly just flash my phone as it is currently? Stock root, A11, OOS11?
I cant do OTA updates, nor can I install downloaded updates (via the settings app) either because I converted, or its Magisk or something...
How did you get you Tmos to 13? Were you already updated before rooting? Did the OTA work after root for you? I just get install failed immediately with the downloaded package.
Any input would be appreciated Im in no rush, and I already have a backup setup for after conversion (assuming Migrate works on this phone, seems to so far).