[Q] What is the Best App or Way to Keep Root after Flashing Zip? - Nexus 5 Q&A, Help & Troubleshooting

I love Custom ROMs and Kernels and I'm sure you all do too. It seems that every time I flash my favorite CM ROM which has a built in CM SuperUser found within Settings and then after flashing my favorite kernel, I simply lose root for the ROM and the SuperUser stops working. I want to know how to get the CM SuperUser working again after flashing the zip in recovery.
Here is where my problem seems to be different than others. I can get root back by installing SuperSU and then going to settings and telling it to "Ignore CM Root Settings" and then rebooting, then root access works with SuperSU and the system thinks its doing its job too...but then when I uninstall SuperSU the entire problem comes back.
So my question is, is there a solid method to keeping the built in CM SuperUser found in Settings working as it did before flashing that zip that broke the ROMs root in the first place?
Any help is greatly appreciated! Thanks so much in advance!

I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/showthread.php?t=2602670 ). Am I right?
My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.
My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.

Cloonix said:
I think you are experiencing a similar problem like I did ( http://forum.xda-developers.com/showthread.php?t=2602670 ). Am I right?
My root in CM11 is not working properly. So every time I flash CM11 with TWRP, I have to flash SuperSU right after CM11 and my kernel.
My personal explanation is, that SELinux (enforcing) doesn't work well with CM11 yet.
Click to expand...
Click to collapse
Yeah, I'm pretty sure we are having the exact same problem seeing that it's CM and you flashed a kernel which broke your built-in root.
Isn't there an update for the built-in SuperUser or something? CM is really popular so I know some people have liked it enough to want to keep the built in SuperUser and not use a halfa$$ workaround. Don't get me wrong, SuperSU is LEGIT, but I want the built-in SuperUser this time because I don't want it sitting in the Settings for no purpose.
Anyone? Thank you in advance!

superuser updated today and fixed the CM breaking root deal.
What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014

I think the latest version of SuperSU (1.91) is supposed to fix that.

mistahseller said:
superuser updated today and fixed the CM breaking root deal.
What's New
- New -cn/--context parameter for su binary (devs: see How-To SU update)
- Handle mksh being switched out for sh
- Daemon forces new session immediately at launch (moved up)
- Fixed reading dynamic properties on 4.4 (update ASAP if 4.4 user)
- Fixed issue where root wasn't granted on CM
- Add support for Samsung 4.4
- Update copyright notices to 2014
- Updated language files
Additional information
Updated
January 20, 2014
Click to expand...
Click to collapse
The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/details?id=com.noshufou.android.su&hl=en or https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.

Cloonix said:
The problem is imho the built-in superuser by CM (https://play.google.com/store/apps/details?id=com.noshufou.android.su&hl=en or https://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en) not SuperSU. Actually I'm not really sure which one is used in CM.
Click to expand...
Click to collapse
cm uses superuser. flashing supersu fixes the issue and rids cm of everything superuser related.

It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.
If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.
CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Screenshot of SuperUser found on Google Play:
{
"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"
}
I will report back if I can find a solution or fix!

xnickfx said:
It looks like, at least from all the research I did today, that there actually might be a fix for all this by possibly updating the actual ROMs built-in version of SuperUser.
If you look at this version of the SuperUser app by ClockworkMod on Google Play, you can see in one of the screenshots it shows an app requesting permission from what looks like the exact UI as the built-in SuperUser we see in our CM-based ROMs.
CM Built-In SuperUser App on Google Play:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Screenshot of SuperUser found on Google Play:
I will report back if I can find a solution or fix!
Click to expand...
Click to collapse
You could try to get the .apk of SuperSU or CM's superuser and put it in the "app" or "priv-app" folder of your CM-ROM .zip-file.
I tried to simply replace the su-binary in the xbin folder... Stupid idea though. Didn't work out

Bummer, so I didn't find a solution / fix, but I did find some possibly helpful links.
These are options that I researched very deeply in any and every way possible. Notes for found possibilities are noted below the option, if any.
Opt-1 .) Locate where the files or code for the built-in SuperUser are located within ROM and update / replace them with newest version of SuperUser, and also gain root when re-root is needed.
Opt-2 .) Replace SuperUser found in CM-based ROM's Settings with newest version of SuperSU by either deleting from ROM's Settings somehow or keep it and have SuperSU built in ROM's Settings same as current SuperUser.
I do believe that somewhat of Option #2 might be possible. I don't really know for sure yet, but I found these other 2 links that look pretty interesting.
http://forum.xda-developers.com/showthread.php?t=2033590
http://forum.xda-developers.com/showthread.php?t=1539711
I know you can install SuperSU and pretty much ditch SuperUser for good, but then you still have it sitting in the ROMs settings for no reason at all.
You can remove and hide SuperUser from the ROMs settings but in order to do that you have to completely disable root. You can remove it by going to Developer Options or SuperUser settings and choosing "disable" for SuperUser Access. Unfortunately when doing this SuperSU immediately stops working even when open and closes the first chance it gets.
If anyone else can shed any light at all on the subject, it would be VERY MUCH appreciated! Thank you!

Related

[ROM][06 May 2012] Flytouch 3 Superpad 2 TolgaMOD_FT3_v1.0

Hello,
This ROM is based on Tim6a and www_apad_tv-ibex-Flytouch-3-Firmware-V8.
I started customizing Tim's 6a ROM for my own use, basically since I wanted to see all apps compatible with FT3 on Google Play and I wanted to use ADW Launcher. Now that my customization is complete, I wanted to share it with the xda-developers community
The ROM is built to mimic a Samsung Galaxy GIO device. This device has a much smaller screen but has an ARMv6 processor like the FT3. So all apps downloaded from Google Play should work, and with good performance since it will be the app's QVGA version. Gameloft games also recognize this device, so for example you can download and play Ice Age Village.
Credits go to Tim for his great custom ROM, Apad.tv for firmware-V8, Axlien for the build.prop ideas, chairshot215 for performance tweaks. Thank you guys!
mod edit
I hope you enjoy this release!
Tolga
INSTALLATION:
Unzip the contents of mod edit] to the root folder of your SDcard, and reboot FT3. When the installation is complete, don't forget to take out the SDcard and remove the installation files.
If Wi-fi is grayed out after installation, it means that your wifi card is not 0803 v1. (default) Try enabling old FT3 or 0803 v2 using Tim's scripts in Gscript Lite.
To view all apps on Google Play, follow these steps after installation:
1. Open Google Play, accept the upgrade and accept TOS.
2. Go to Settings>Applications>Manage Applications and select ALL tab.
3. Go to Google Play, clear cache and force stop (DO NOT CLEAR DATA)
4. Go to Google Services framework, clear data and force stop
5. Open Google Play, and you should get a server error. (This is normal)
6. Restart FT3 and all compatible apps should be visible on Google Play!
mod edit
SCREENSHOTS:
{
"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"
}
FEATURES:
ADW Launcher (InfoTM Home is also included)
Rooted, superuser
Google Play Store v3.5 (Android Market latest version)
Dolphin Browser, Gmail, Youtube, Terminal Emulator, Root Explorer
Development app for enabling USB debugging
Adobe Flash plug-in 10.1
Tim6a scripts for old FT3 wifi fix, 2MP camera fix etc.
Google Play Store fix and Performance tweaks in build.prop
Minimum apps included for smaller download size and performance
KNOWN ISSUES:
Market fix needs to be applied manually after installation.
TO-DO-LIST:
Custom Kernel to enable HDMI Mirroring and Overclocking (Investigating Stragulus FT Kernel Source atm)
CHANGELOG:
v1.0
Initial Release
Click to expand...
Click to collapse
DISCLAIMER: Please use this mod at your own risk, rooting your device and installing custom ROMs may render your device unusable and VOIDS THE WARRANTY.
I will try to ensure that all info about TolgaMOD_FT3 is up to date here, and will do my best to help in case of problems. It's best to report problems by replying to this thread rather than PM, so that the solution can be viewed by all users.
Hmmm.
I'm useing one of Tim's Roms... not sure wich one. The one where the screen is always dark. I tried dling your fixed stuff put it on my sd card it said it updated took out the sd card than turned it back on, but nothing had changed, everything was still the same? I have tryed the Power button+menu+front button to factory reset it, and still tims rom is still there with no changes. I just am at a loss now... really pissed to be honest. I cant even get the thing back to it's original original settings... I want to use your packet, any suggestions?
Anyone? I have just about tried everything and I'm on my last leg. I'm about ready to just rip the case open and K.O. the battery~
Hi billypaul69,
On my FT3, I just push menu+power to do a factory reset. Perhaps you could try that button combination to do a factory reset.
About flashing my ROM: Apparently the update somehow did not complete for you. I suggest you check out this excellent video tutorial from Axlien to flash a ROM to FT3, and see if it helps: http://www.youtube.com/watch?v=w7xdpnoHLeg
Make sure you don't turn off your device, before you see the following message on the screen:
Updating system firmware completed.
Please shutdown your device and remove the installation card!
Automatic shutdown in 1 minute.
Click to expand...
Click to collapse
If you see any other messages such as "not complete", "wrong system file" etc. and not the one above, please report them here. It's possible that either the .zip file you downloaded got somehow corrupted or the SDcard you are using for the update is faulty. In that case try re-downloading TolgaMOD, or formatting your SDcard and try again.
I hope that my suggestions work for you! Thanks for checking out my ROM!
Regards,
Tolga
Thanks soo much i'm going to try all the steps asap.
\billy
Hi
I just installed your new rom file and everything went Ok. The only problem is that my wifi network is not working. I can activate the wifi but it cannot find any network.
I tried using gscript to install on of the wifi patches but I get the following error message
"stderrermission denide" when I run the script.
Any idea as to why this is happening ? Apart from that, you rom is very snappy in operation.
Hi jammertn,
I'm glad you like the speed of my ROM, that was one of my goals indeed. I'm pretty sure one of the wifi scripts will correct the problem. For example my tablet's wifi works with the "old FT3" fix.
The reason you are getting the "permission denied" error is because gscript was not given superuser permissions.
The first time you run gscript, there should be a pop-up screen from superuser application asking for root rights. You should select "Allow" on this window. If you don't allow it or deny root access, the scripts won't work. If you denied root access and selected "remember" the first time, please launch superuser application from the app drawer and change the status of Gscript Lite to "Allow".
Since you have wifi not grayed out I guess your wifi is 0803 v2. Please try running the "Wifi fix:0803 version2" script and then reboot your tablet.
I hope that helps!
Hi and thanks for the quick reply.
From where do I launch superuser?
Click the middle button (the one with white squares) on the dock, you will have access to all installed apps including superuser.
OK I found the application.
One more question, Something happened and now gscript only sees 3 scripts. How can I make it show all the scripts like before.
Excuse all my dumb questions but I'm new at this.
No problem mate, I think the best way is to simply re-install the ROM You can backup your current apps with Titanium Backup.
Nice, thanks a million
I got it working now.
I'll be watching this thread closely.
Keep up to great work
Yay! I'm glad it worked, c ya around.
Hi Tolga
Is there anyway to activate bluetooth on this tablet? I tried using the gscript but cannnot get is to work. Any ideas ?
Hi jammertn,
This tablet doesn't have a bluetooth chip onboard. Tim's scripts are for driving usb bluetooth dongles. I'm not sure which ones work, but maybe the thread below could have more info.
http://www.apad.tv/apadforum/showthread.php?1358-Flytouch-3-Bluetooth-USB-dongle-testing-thread
Hi Tolga
Thanks for the reply, I have seen that thread but it does not have have any useful info in it. I tried it with an external usb/bluetootyh dongle but still no operation.
Hi,
I ran a quick web search and I haven't seen anyone successfully making a USB bluetooth dongle work on FT3. I think Tim included some kernel modules with the firmware for devs and testing purposes. So please don't assume it will work when you simply plug in any USB BT dongle.
Here's the support thread for Tim6a, there might be more info there:
http://www.apad.tv/apadforum/showthread.php?416-Flytouch-3-Hybrid-ROM-(rooted)&highlight=bluetooth
I think I have a USB BT dongle somewhere, I will take a look if I can find it
Regards,
Tolga
has this been posted on Apad.tv or tested on the iBex Flytouch 3 by people on there?
Do you mean if this ROM has been tested or if USB bluetooth dongle has been tested? I'm pretty sure TolgaMOD runs on Ibex Flytouch 3, since it's basically a modified version of Tim6a.
Here is my ROM's thread on apad.tv:
http://www.apad.tv/apadforum/showthread.php?2675-ROM-06-May-2012-TolgaMOD_FT3_v1.0
i installed rom over Tim 6a rom but still nothing changed,, MENU+power reset also tried.. currently my Huawei data stick does not work since some weeks, thats why i need to install a fresh firmware..
merhaba, yükleme yaptim fakat yine eski tim 6a rom yüklü yani hicbir sey degismedi, hard reset yaptim yine ayni.. ayrica önceden calisan Huawei data stick bi süredir calismiyor, birseyler silinmis olmali diyerek yeni rom yüklemek istiyordum, acaba neden calismiyordur data stick?

[ROM] [FLO] Bad Boyz Nexus 7 Stock Rooted | MOB30X | 6.0.1 | Updated 8.1.16

Here is a stock rooted MOB30X 6.0.1 ROM!!!....includes SuperSU v2.76 & BusyBox only...
DOWNLOAD​
*note* due to the size of /system I removed the GooglePinyinIME & KoreanIME
See attached script to clean system apps, it will free up 224mb
*make sure you run the cleaner AFTER all apps have been updated from Play Store (assuming you want to keep these apps, if not, run the script right after flashing ROM)
**Bootloader has been updated to 4.08 as of MOB30X**
Here is a twrp flashable to update bootloader, credit to @TheC92 , thx!
Bootloader v04.08
*credit to @Chainfire for SuperSU, thx!
*credit to @osm0sis for Busybox, thx!
Changelog:
4.4.16
-updated to MOB30D
-updated to SuperSU v2.71
3.8.16
-updated to MMB29V
-updated to SuperSU v2.68
2.1.16
-updated to MMB29Q
-updated to SuperSU v2.67
1.5.16
-updated to MMB29O
-updated to SuperSU v2.66
12.07.15
-updated to MMB29K
-updated to SuperSU v2.60
11.03.15
-updated to MRA58V
-added systemless root version
10.28.15
-updated to MRA58U
v4 - 10.16.15
-updated to SuperSU v2.52
-fixed lockscreen freezing (updated updater-script, thx to .MoHaMaD)
v3 - 10.9.15
-updated to SuperSU v2.51
-changed ROM from flashing system.img to conventional /system files
v2 - 10.7.15
-updated to SuperSU v2.50
-switched to Chainfires modified boot.img
v1 - 10.6.15
-initial release
Mine...Why ? Who knows
OMJ said:
This is not a typical zip you flash in TWRP...this is a stock rooted system.img & modified boot.img, flashed just like the stock images from Google. I've removed the uneeded images & edited the flash script to only flash system & boot. Actually it will also flash the included bootloader, but it appears it is not updated from 5.1.1....as it's still 4.05.
Click to expand...
Click to collapse
Just to be clear (it seems like it), flashing this won't touch Recovery/wipe the device, correct?
Downloading anyway, great work!
Nice, what I've been looking for.
Hope enforcing SELinux can be achieved sometime with SuperSU. Using permissive SELinux is a must for now, i've read https://twitter.com/ChainfireXDA/status/604443705806848001?ref_src=twsrc but i do hope enforcing will happen someday soon as source rolls out
Cryptecks said:
Just to be clear (it seems like it), flashing this won't touch Recovery/wipe the device, correct?
Downloading anyway, great work!
Click to expand...
Click to collapse
Correct, it will not flash recovery or wipe data
Sent from my 0PJA2 using XDA Premium 4 mobile app
OMJ long time no see glad your back cooking been a fan since day one.
Sent from my SM-N900P using Tapatalk
can u put the kernel seprately?
Downloading...[emoji4]
.MoHaMaD said:
can u put the kernel seprately?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63158038&postcount=210
If anyone else, like myself, has an issue with the Home button and Notification Shade not working after flashing this (everything else works properly), be sure to do two things:
Clear out a couple of Google's pre-loaded apps from /system/app, there is almost NO free space there. Then install them from the Play Store instead.
Run the command in this old AP story: http://www.androidpolice.com/2014/0...at-refuses-to-pull-down-after-android-update/
I've done those things, and now I have a basically 'updated' N7 from 5.1.1 to 6.0.0 without losing a thing, and still some space in /system/ to flash an adblocker, etc.
Just trying to help a bit.
OMJ said:
I built a stock rooted 6.0.0 ROM if anyone is interested....includes SuperSU & BusyBox only.
This is not a typical zip you flash in TWRP...this is a stock rooted system.img & modified boot.img, flashed just like the stock images from Google. I've removed the uneeded images & edited the flash script to only flash system & boot. Actually it will also flash the included bootloader, but it appears it is not updated from 5.1.1....as it's still 4.05.
Click to expand...
Click to collapse
Didn't even know you had an N7! Thanks OMJ!
Cryptecks said:
If anyone else, like myself, has an issue with the Home button and Notification Shade not working after flashing this (everything else works properly), be sure to do two things:
Clear out a couple of Google's pre-loaded apps from /system/apps, there is almost NO free space there. Then install them from the Play Store instead.
Run the command in this old AP story: http://www.androidpolice.com/2014/0...at-refuses-to-pull-down-after-android-update/
I've done those things, and now I have a basically 'updated' N7 from 5.1.1 to 6.0.0 without losing a thing, and still some space in /system/ to flash an adblocker, etc.
Just trying to help a bit.
Click to expand...
Click to collapse
thx...wow, u weren't joking...968k available lol
{
"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"
}
henderjr said:
Didn't even know you had an N7! Thanks OMJ!
Click to expand...
Click to collapse
I actually won it during the kitkat candy promo...just haven't done much dev on it
Less than 1MB?!
That's going to make installing Xposed Framework (when available) difficult!
m+a+r+k said:
Less than 1MB?!
That's going to make installing Xposed Framework (when available) difficult!
Click to expand...
Click to collapse
right...but as @Cryptecks said, remove some junk in /system to free up space
Why isn't there a single twrp flashable rom in the entire nexus 7 section?just seems weird.
Thankyou very much....
Not really sure if that's correct.
I'm on LP and system size is 1,15Gb... used 1,16Gb lol
|Logic| said:
Why isn't there a single twrp flashable rom in the entire nexus 7 section?just seems weird.
Click to expand...
Click to collapse
I agree, by now there was usually at least 2 or 3 of them rooted with busybox. Don't know why isn't happening with M. A little harder to make a flashable zip for some reason ?
MidnightDevil said:
I agree, by now there was usually at least 2 or 3 of them rooted with busybox. Don't know why isn't happening with M. A little harder to make a flashable zip for some reason ?
Click to expand...
Click to collapse
I will say this... I initially extracted the system img & built a twrp flashable zip but kept getting errors.
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 5X Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Reserved
*I am big fan of this device. Looking forward to using it as my daily driver, and very happy to extend NRT support*
just added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Nice to see you here WugFresh!
Good to see you, glad you've joined us :thumbup:
Hi! Very nice to see you here! You're always been my backup when I screw up something in the past with my nexus devices. I'm know I can always get back to stock with NRT
Verstuurd vanaf mijn Nexus 5X met Tapatalk
@WugFresh
Love your NRT on the Nmmexus 6. Glad you're here. Makes life a lot easier
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
imadiu said:
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
Click to expand...
Click to collapse
I am having BusyBox issues also.
mmartenn said:
I am having BusyBox issues also.
Click to expand...
Click to collapse
If you tried to install busybox right after you root your phone, as what the Root toolkit tells you to, it will not work like mine. That's because it's outdated. So just go to play store and update that app first before you reinstall any other app. I presume you rooted your device right after you unlock your bootloader which factory resets your device.
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
coolineho said:
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
Click to expand...
Click to collapse
Same problem here. Any solutions?
riceknight said:
Same problem here. Any solutions?
Click to expand...
Click to collapse
Not yet, still waiting ;(
I'm also facing the same issue, can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.
I also can't reboot into TWRP, unless I reboot through the NRT updater.
If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.
I'm running MDB08L
What I'm doing wrong?
Thanks
Sent from my Nexus 5X using Tapatalk
Install notes:
In options menu disable installing busybox, install busybox from play store after root process.
After root, Flashboot Flash Recovery in Advanced Utilities.
I have had no problems after using these steps.
I followed the steps above and busybox still wouldn't install so I found a 1.24.1 flashable zip flashed it and it worked . just another option to try if all others are not working
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Tank87 said:
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Click to expand...
Click to collapse
Yup, just did mine to send it back to google for warranty replacement of intermittent power button.
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
skulldreamz said:
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried flashing this file (through twrp right?). It doesn't look like it worked through TWRP I got an "Updated process ended with error=1, error flashing 1.24.1.zip", and busybox is still not present on the phone when I restarted it. I tried downloading it from the play store directly and it still gives me the "it looks like it was not installed successfully" error message. Should I be flashing this file some other way? Thanks in advance!

[OOS][Oreo] Enable Google Daydream VR Support

For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"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"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏
Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?
lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!
CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.
I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..
Anybody got it working? I saw the set today at a store and thought about buying it...
This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.
OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?
EDIT: see post #19
I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.
Updated for Oxygen OS 5.1.3
Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.
M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.

[KFHD10] Any Demand for an AIO Root/Mod Tool?

Hello all! Apologies ahead of time if this post is in the wrong area or breaks any rules!
I currently have a short batch script that can offline root/unroot (including SuperSU install), install GAPPS, toggle Lockscreen ads, and perform many other tweaks in a few short motions. I've tested it on several HD 10 tablets that I own and it has made life easy. After doing a bit of searching I noticed that most of the root guides use Kingoroot (which does some shady operations) or are instructions that I've automated to increase speed and decrease typos / errors.
Would anyone be interested in a polished version of my KFHD10 Multitool? I will gladly release my tools if there is demand for them! I just wanted to ask before I spent the time making a nice interface and adding options to my existing script.
iamz3r0 said:
Hello all! Apologies ahead of time if this post is in the wrong area or breaks any rules!
I currently have a short batch script that can offline root/unroot (including SuperSU install), install GAPPS, toggle Lockscreen ads, and perform many other tweaks in a few short motions. I've tested it on several HD 10 tablets that I own and it has made life easy. After doing a bit of searching I noticed that most of the root guides use Kingoroot (which does some shady operations) or are instructions that I've automated to increase speed and decrease typos / errors.
Would anyone be interested in a polished version of my KFHD10 Multitool? I will gladly release my tools if there is demand for them! I just wanted to ask before I spent the time making a nice interface and adding options to my existing script.
Click to expand...
Click to collapse
I've been working on a similar zip. A tool would probably be easier. Has activating location services been a problem? I've found it to be less of an issue if flashing a zip because Amazon removed com.google.android.gms from the framework. The zip I made replaces the framework with my modded one, that replaces com.google.android.gms.
I haven't played with Location Services just yet. The script I have can root, unroot, install Play Store/Services, swap the launcher, and toggle lockscreen ads. I plan on adding more tweaks as I go.
I've spent the last hour or so rooting and unrooting just to test the success rate, and it's doing very well!
iamz3r0 said:
I haven't played with Location Services just yet. The script I have can root, unroot, install Play Store/Services, swap the launcher, and toggle lockscreen ads. I plan on adding more tweaks as I go.
I've spent the last hour or so rooting and unrooting just to test the success rate, and it's doing very well!
Click to expand...
Click to collapse
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Hey! If you're offering to add some functionality and collaborate, I'm 100% down with that. Send me a PM with the details of what you have and I'll see how I can fit it into the AIO utility. I'm sure I'm missing some neat options.
Yes, please!
Ill test it please
DragonFire1024 said:
I have a fix or two to do in my framework mod. It's version specific, but I can make one for a few versions. If it's a root tool, it would be useful to add and be installed after the play store etc. It just requires location services be turned on before either the play store apps or framework is installed.
Click to expand...
Click to collapse
Yes this is the problem. I tried to install framework and it bootlooped. Had to side load factory.bin
gerryl432 said:
Yes this is the problem. I tried to install framework and it bootlooped. Had to side load factory.bin
Click to expand...
Click to collapse
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
iamz3r0 said:
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
Click to expand...
Click to collapse
What version?
Sent from my Amazon KFSUWI using XDA Labs
iamz3r0 said:
Is this a modded framework or the unmodified version? The version I have is older and unmodified but installs and works just fine. I haven't played with all of the settings yet, though.
Click to expand...
Click to collapse
i honestly cant remember. but i assume it was the wrong one
{
"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"
}
I'd gladly let everyone test it out but I'm trying to perfect the auto-root script. I can easily root - that isn't the issue. The issue is the way that the Kindle doesn't prompt for SU requests. You can work around this by changing the default setting in SuperSU to "Grant" but I'm attempting to automate this process. I've gotten it automated by sending touch commands to the device to change the prompt setting but I'd much rather just change the setting manually.
I'm not 100% sure if this will work but I'm trying to:
1. Root using the exploit script (here, thanks retyre)
This works fine. 80% of the time, it quickly roots the device and I can get the SU prompt just fine. I'm able to run about one or two SU commands before anything stops working. Root + SuperSU + Manually setting the prompt config to "Grant" works 100% - obtaining root isn't the issue.
2. Upload a pre-modified SuperSU preferences file
Instead of editing the settings - we might be able to just upload the preferences XML file to the SuperSU data folder before installing SuperSU itself. That way we already have the "Prompt" setting switched to "Grant". We then change the permissions so that SuperSU doesn't modify this file when it is installed.
3. Revert permissions so that edits can be made to the settings in the SuperSU app
I would of course need to change the permissions of the SuperSU preferences XML back to the normal settings so that SuperSU can make changes to it again. This way adjustments in the app actually stick.
----
After running the root exploit script I can get a SU prompt (#) and run a command. I'm not installing SuperSU until the script makes the modification to the preferences file, but as soon as I try to run another SU command after the first - it hangs and everything stops working . I end up having to restart the tablet by holding the power button and I'm unable to get a SU prompt again without installing SuperSU and changing the setting to "Grant".
I think there is a way to make it work but I'm still digging into it. If anyone has any ideas, I'm open to listen!

Categories

Resources