I have been trying to install a custom Rom because of SuperSU failing to update binarys and getting stuck on boot. I have tried two different Roms (BlissPop and DirtyUnicorns) and both have the same exact problem that i have found so far, the home button doesn't return home or do anything for that matter, and the notification bar will only fully extend once any time after that and it only half extends after that.
So I guess my question is this. Is there something that i can do to fix the problem with the Roms, or is there a way i can fix SuperSU trying to update its binarys.
Tablet/Software Info
Roms: BlissPop, DirtyUnicorn (The ones with the problems i tried)
Gapps:Banks Gapps
Tablet:Nvidia Shield Tablet LTE US
Related
Strange thing...
I successfully rooted with the Framaroot method.
I think it's one of the most discreet rooting method since it doesn't require to modify the recovery nor to flash anything with Odin.
I think it just uses the Exynos exploit in some way, and since my stock firmware JB 4.1.2 (N8000XXCLL3) is not one of the more recent ones (that probably fix the exploit) I could root with it.
After that I could happily see that my device status was still "Official".
I checked that well after rebooting more than one time. I also checked that the status was "Official" also in "Download mode".
Anyway, after a couple of days of normal usage (I didn't do anything strange with the root, apart from accessing some system file) I saw that my status had changed to "Custom" .
My suspect is that there's some Android service that periodically (yet infrequently) checks for a rooted device, changing the device status accordingly if it finds some trail of root.
Stranger yet is that, upon rebooting once again, my status has now come back to Official
So... does anyone knows better what triggers the device status from Official to Custom and back to Official when there's no modification in the stock Rom?
Exynos exploit changed mine to custom, tried 3 times to get rid of it, always went to modified then custom after a few minutes/ hours. I'm cool with it tho, doesn't hamper what I do with my note. I've seen others reporting similar scenarios
Hello all, I am relatively new to the android rooting scene. I have looked into it before but always became discouraged by the amount of different informaton from different sources. I am a little bit familiar with flashing processes as I used to install CFW onto Sony PSP and PS3 devices. However there's a lot of new terms that I am soaking in and trying to figure out what it all means when it comes to phone rooting. I am currently using a Sprint Galaxy S5 Sport running Lollipop 5.0, with build number, "LRX21T.PVPU2BOH1" and Kernel "3.4.0-4445742 August 6, 2015". I've been looking around and every time I think I find a reliable source for rooting I see a disclaimer saying only works with certain build numbers, and mine doesn't seem to be any of the builds I have seen. A Google search of my build brings a total of 5 searches wit no information regarding it. Anyways I am looking to successfully root my device, install a working recovery mode, and if possible, install a ROM. I have searched through threads and scrounge up some information about the SM-G860P but not enough for me to go through with the process with 100% certainty of success. I also hope that this thread can be useful to other SM-G860P users and a one stop shop for all the files needed to safely root, backup, and restore files. Basically, I know it can be rooted using Odin and CFAR on Lollipop 5.0. But the steps after that I am unsure. Do I install TWRP, CRM, what ROMS can I install, what kernel do I need. Thanks in advance to any developers or members who can provide all the proper links to attain my goal.
I have a very similar build. I have successfully put on root, and CWM recovery, but, any attempts at custom roms have failed (assuming due to kernel), and I am unable to get tethering working, despite having root.
Followed http://forum.xda-developers.com/sprint-galaxy-s5/development/recovery-cwm-s5-sport-sm-g680p-t2907945 for recovery.
I rooted following something like: http://www.android.gs/root-sprint-galaxy-s5-on-android-5-0-lollipop-os/. The key was using the auto root, then flashing the update via CWM. Had to make sure CWM was installed, as flashing using stock recovery caused issues.
Tried to flash CM12 from:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665
But ended up in a boot loop.
I'm also scared to put xposed framework on, since most saying need to use a custom rom or else phone will bootloop.
Using most of the methods to tether, (like adb settings global or sqlite), tether_dun_required keeps resetting back to 1 after turning on tethering, so, I still haven't found a solution to that. I'd love to hear from anyone who's got tethering working on SM-G860P with lollipop.
Hi Guys
After one of the custom 5.1 roms crashed and left me without the phone, I have decided that I will go live with Marshmallow.
I have installed the original stock 6.0 MRA58K which after booting quickly went into MRA58N with OTA update.
Once I have realised how many things I am missing in my phone, due to using the stock ROM, I was looking for a perfect solution and decided that I will no longer be flashing custom ROMs, but use XPOSED as a framework with additional modules.
I have installed the elementalx kernel and added the correct XPOSED framework.
Everything was working fine until yesterday, where I have received notification about OTA update to 6.0.1.
First I thought that I don't really care about emojis, however I do like the option of "Do not disturb until next alarm".
I know that I can achieved by some additional modules to the xposed, however the OTA update is quite annoying.
Because I was on TWRP as a recovery, I have also installed the BusyBox and SimpleRecoverySwitch hoping that this will resolve the issue. Quickly reflashed stock recovery (don't know why, but every time when I was using fastboot to flash recovery with stock recovery.img, TWRP was still there) and found that I still can't use OTA update to 6.0.1. due to error:
"app_process 32 has unexpected contents".
After googling I have found that this is because I have xposed up and running.
Googled than for "unistalling" xposed and found plenty of topics, however none of them have provided me clear answers, especially to the question of "how to uninstall xposed". I have not found any original.img, so I suppose xposed installer have not created any backup, also when I will open xposed Installer - options to "uninstall xposed" are greyed out.
So my question would be - how can I easily remove xposed (temporary) without loosing data/restarting fully the phone, because after 5 days of flashing/reflashing/factory resets I am slowly tired from setting up personal configuration on my phone (even when on Marshmallow is much more easier than on lollipop 5.1).
If this is not possible, how I could remove OTA update from not only notifying me all the time, but also not restarting the phone (wakelock?)
Once you root the phone, you will not be able to upgrade via OTA. Your choices are to follow the instructions on this thread or to completely go back to stock without root and do the OTA.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
Hi guys, I'm new here, I've searched forum similar posts but I couldn't find anything.
I rooted my Nuogat 7.0 device with the last versions of twrp recovery and SuperSu. (The device is unlocked and S-ON)
A couple days ago I decided ti flash LineageOS 14.1 ROM and the super Gapps package. At the beginning all' ok, but I noticed that the HTC sense interface was absent.
So I tried install the last versions of it but it gave me crash problems everytime I tried to interact with it (like when moving apps or installing themes). I Also noticed that the layout is smaller than the one I had before installing lineageOS(app icons are smaller, and apps layout too (this doesn't happen when I launch Google home Launcher)).
I've tried installing older versions found on apkmirror, but they all give me the same problems.
LineageOS ROM was the correct one for my phone and GApps pack was the correct one for my CPU. Please help I like too much Sense home