What is a stable lollipop ROM? I don't like the marshmallow SD card update. I have a 128gb and I like using it on my PC. I'm looking for a stable ROM that works with Magisk so I can play Pokémon go rooted. Should I just go back to stock lollipop rooted?
ive been rockin MOAR 7.0 for quite some time and i installed Magisk the other day. I flashed something in recovery that caused a bootloop and havent really messed with it since, but it worked before i likely did something wrong LOL
stock 5.0 pogo smg900p thoughts
i7vSa7vi7y said:
What is a stable lollipop ROM? I don't like the marshmallow SD card update. I have a 128gb and I like using it on my PC. I'm looking for a stable ROM that works with Magisk so I can play Pokémon go rooted. Should I just go back to stock lollipop rooted?
Click to expand...
Click to collapse
Stock rooted lp should* work. Rwilco12 has a few stock odexed and deodexed roms and I saw another 5.0 recently that all seem to be positive but I haven't tried.
Got pogo to work on my lgg2 with no network. Using blast gators mostly stock lp from somewhere on xda, uninstal supersu, twrp flashed unsu, used adb shell to remove bin and xbin su files. Flashed magisk v6, bumped my bootloader, flashed phh su, rebooted to system. Installed app side of phh, installed 1.2 magisk manager, installed newest pogo. Unmount root, worked fine when I had internet. Flashed stock 4.4.2, manual update to 4.4.4 and again to 5.0 and then installed blastgators mostly stock rom: worked again. Pdanet crashes on the phone and I still can't get my native Hotspot opened on my smg900p ok4 build, only my phone has net where I live :/ Even used paid fakegps moved to system on expert mode to spoof location on the lgg2. WORKED LIKE A CHARM.
However, on my smg900p ok4 build, last lollipop build, I can't get it to work. The methods were different. Prior to all of this I had flashed a sound mod that I never undid. I Uninstalled cf su from system, reboot, boot to twrp, flashed unsu, TERMINAL EMULATOR TO DELETE BIN AND XBIN SU FILES, LEFT ONE IN BIN, DELETED WITH ES AFTER FIRST POGO ATTEMPT. I then flashed magisk v7 and the phh magisk 7 su, manager 2.0. Didn't like the module mode, so I got rid of manager, flashed magisk Uninstall, flashed magisk v6, phh su for that, installed app side of phh and 1.2 magisk manager. Doesn't authenticate my login.
I want to try what you're talking about but I haven't done it to my s5 yet, it's my working phone and I'm a skid so I'm worried. 1. Does flashing a full tar/zip stock image in Odin replace the bootloader as well? 2. Should I take my SIM and SD card out? 3. Will I need to repatriation my miniSD ext2/4 memory after flashing stock ok4, 0g1, or one other I can't remember? 4. Which 5.0 build should I use
I want to try what you're talking about but I haven't done it to my s5 yet, it's my working phone and I'm a skid so I'm worried. 1. Does flashing a full tar/zip stock image in Odin replace the bootloader as well? 2. Should I take my SIM and SD card out? 3. Will I need to repatriation my miniSD ext2/4 memory after flashing stock ok4, 0g1, or one other I can't remember? 4. Which 5.0 build should I use
i think we covered a good deal of this in your other post, but for those looking still,
1: yes
2: nope, its just fine
3: nope (and its micro, not mini), and id go to OK4
4: MOAR 7.0 with the MOAR extras zip too. Its slick as hell
Hehe one answer in a thread is enough thanks bro
Related
(Not sure if it is better to make a new thread or ask in the SuperSU thread...)
Hey all. I had previously been running the 7.1 OTA build with SuperSU installed. It seemed fine and I had done OTA updates with it installed with little issue. This was pre-2.78 SR3 builds of SuperSU, so I was using the boot-to-root. One day, I inexplicably noticed that root was gone. App too. I was very confused because to the best of my knowledge no OTA updates or security updates happened since I last rooted.
With that, I decided to sideload update to NMF26Q, which apparently was released about 12 hours earlier, and install TWRP since it was needed for newer SuperSU. TWRP installed fine and worked, but SuperSU did not seem to work. In fact, every time I attempted to flash SuperSU 2.78 SR5, I noticed it would remove the SuperSU app if it was installed via the Play Store. Finally, I noticed that it was installing in System mode.
I attempted to override this by running `echo "SYSTEMLESS=true" >> /data/.supersu`, but nothing I did worked. It did the same exact thing. Looking through the shell script, I'm entirely unsure how it is possible that my override did not work. I also reflashed the stock boot image to both slots and then reinstalled TWRP. This had no effect on installing SuperSU.
I try to do due diligence before turning to the internet for help, but I don't have any clue what's going on here. Maybe it is best if i reflash the entire stock ROM, but I'd love to avoid that if possible, as everything else seems to work great, and I have no idea why this in particular would be an issue.
Use alpha 2 of twrp and ask will be well
Yep, that worked great. Cheers.
http://forum.xda-developers.com/showpost.php?p=69626115&postcount=2
Spend whole day browsing XDA, still can't get the thing done.
Running stock Nougat 39.2.A.0.361 with unlocked bootloaders and TWRP 3.0.2.0. Downloaded SuperSU 2.79, booted into recovery and flashed SuperSU. No errors, just a success message. However, after rebooting the phone, no sign of SuperSU exists. Flashtool also indicates root access is denied.
When installing custom ROM with SuperSU integrated ( http://forum.xda-developers.com/xperia-xz/development/rom-romaur-v1-0-fast-stable-t3486874 ) root works perfectly. Once custom ROM is installed, SuperSu icon is displayed and root access is OK.
I read that this problem might be because of incompatible kernel? I installed custom kernel (which was attached to RomAur - Stock_Kernel_f8331_fw.327-DRM FIX) before installing custom ROM, but I guess that re-flashing stock ROM later (using Flashtool) restored original kernel as well? If so, what exactly do I need to do in order to have rooted stock Nougat? Just flash some custom kernel (which one exactly?) and try flashing SuperSU again? Really don't want to brick anything.
P.S. Current kernel - 3.18.31-perf-g6af3ae9
if you are on stock nougat,
flash androplus kernel v18 from here:
https://kernel.andro.plus/tone2.html
after that,
flash supersu 2.78.
Thanks, will try. Is there any reason why using SuperSU 2.78 is needed? I see the latest one is 2.79?
manxp85 said:
Is there any reason why using SuperSU 2.78 is needed?
Click to expand...
Click to collapse
No - mine is running fine on 2.79SR1
BTW:
With stock kernel DM_Verity is ON
That detects any modification (e.g. installing SuperSU) in the non-USERDATA partitions via comparing signed checksums and if there is any modification found refuses to boot the device.
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
manxp85 said:
Well, my device boots perfectly, but SuperSu doesn't appear in apps list. Anyhow, I'll try with new kernel.
P.S. At the moment, phone runs androplus kernel v18 and custom ROM (Aura v4). After I will flash stock Nougat (using FTF file via Flashtool), will I need to re-flash androplus kernel v18 again?
Click to expand...
Click to collapse
Welcome to the quirks of RomAur
It lasted less than a day on my device. I find the claims a bit overblown (did not notice them) and there were minor quirks/annoyances.
It needs time I suppose. But without the SONY sources auras76 can't do magic.
On my SAMSUNG G S5 I am on ResurrectionRom. THAT is an improvement over stock for me with LOTS of stuff I use and appreciate.
My Xperia XZ runs on stock ROM with AndroPlus Kernel v18 now. Do not forget to flash the Recovery too.
I am not sure if the SuperSU app is within the zip-file (80% positive it is). If not install it via Appstore.
Replaced RomAur with stock - works so much better. For some reason, root access on RomAur was lost every time after device was encrypted. No such problem with stock ROM.
Greetings
Have problem rooting updated nougat for FRD-L09* 360
Have installed twrp 3.0.3 and patch the chainfire's latest root - su files or phh, but still no way to get it rooted.
Feedback if any1 else have the same symptoms and solution.
Thanks.
Regards.
Hi @StratOS_HTC
Nice to see you again (coming from the Core 2)
I have the B380 and rooted it with this prerooted image:
forum.xda-developers.com/honor-8/development/twrp-t3566563/post71274057
Try it with that prerooted boot-image. If it doesn't work try this older prerooted boot-image:
forum.xda-developers.com/honor-8/development/twrp-t3566563/post71272109
Regards,
AnDrOiiiD_YT
pHH's changed boot img and app works flawless ROOT
While CF's changed boot.img cause bootloops / system loops.
While changing the fastboot.img got bricked my phone - Were unable to turn it on, no USB connections possible, donno how the TWRP recovery accidently turned on ... No clue about it.
Got it back.
Need some feedback about CF's root. any1 has sent him a boot img's ?
Looking forward for cf's SU for HONOR ...
Is prerooted really the only way to go? I installed B380 today and thought there was a way to root with SuperSU. Must have misunderstood since the Emui5 version of SuperSU doesnt work for me. It installs just fine but then the app says "no binaries installled"..
It's not the pre-rooted, it's only modified boot image with changed security and other init stuff that the root app can use it.
PHH's is working great, CF's will go on ...
Ok. Which of the two links above did you use?
Edit:
If someone else out there had the same question, I followed the first link and downloaded the rooted boot img provided by @Atarii.
I was on B380, unlocked with TWRP 3.0.3 and flashed the rooted_b378_boot.img via adb. Worked like a charm. Then rooted with phhs superuser from Play store.
Stratos how do i check if my phone is model l09 or something else? My Honor 8 is dual sim that means its the version L19?
Do you know any way to install a working twrp + root l19 on nougat?
Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...
Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk
Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk
I remember that installing magisk caused a bootloop on my stock 7.0
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse
josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.
For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Try this, download flash tool, use Xperiafirm to ? get the latest firmware for your region which is currently 171, check all the wipes, flash, then look down a few post to YasaHamed thread, follow his instructions and make use you use the correct kernel..
madladfromhalifax said:
I'm trying to get Magisk installed on my phone, ...
Click to expand...
Click to collapse
I had no problems with a patched stock kernel as described in my [Guide].
Updates of kernels and Magisk, whatever ...
I used latest TWRP, several versions
The encryption only forces you to wipe data if you set up a patched kernel the first time.
I will see how this works with a XZ1 (no TA-backup) since my XZ got stolen last week.
use AdrianDC's twrp, not the twrp official one
madladfromhalifax said:
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Click to expand...
Click to collapse
simplyfied!!!! https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987