Related
Hello All,
I got root with surdu_petru's modified firmware (Stock ICS w/ root) for my 80 G9 and have the following q's which I couldn't find answers to by searching:
1. I tried deleting different system apps with root explorer that I don't need (Email, Youtube) and get the "Failed to delete" message. Why is it not working?
2. Once rooted, how do you format/clear all data without losing root? I tried it once and got into a boot loop and had to reflash the stock firmware and then the rooted one once more...
3. Is it possible/safe to remove the bootanimation to speed up the booting process? The latest Cyanogen Mod version on my phone allows this...
Thanks!
YKBtpt said:
Hello All,
I got root with surdu_petru's modified firmware (Stock ICS w/ root) for my 80 G9 and have the following q's which I couldn't find answers to by searching:
1. I tried deleting different system apps with root explorer that I don't need (Email, Youtube) and get the "Failed to delete" message. Why is it not working?
2. Once rooted, how do you format/clear all data without losing root? I tried it once and got into a boot loop and had to reflash the stock firmware and then the rooted one once more...
3. Is it possible/safe to remove the bootanimation to speed up the booting process? The latest Cyanogen Mod version on my phone allows this...
Thanks!
Click to expand...
Click to collapse
1. Are you sure the app really has the permissions? Check that the root is working with root checker.
2. You can do this 2 different ways:
1. Delete all folders from /data except the folders where the ROM is.
2. Follow AOKP install guide, but instead of transferring aokp ROM, transfer the ROM you use , and change the location to transfer to correct for the ROM. No need to reflash kernel.
3. You can remove it in AOKP and CM, but removing it doesn't help in this tablet. I don't think it can be removed. It can only be replaced. Otherwise the ROM will recreate it.
Sent from my GT-I9100 using xda app-developers app
1. Which app has what permissions? Root Browser or the app I want to get rid of?
- When I long press an app and click properties, it says "Permissions: N/A"
- The Root Check Basic app says that I have root access.
2. /data is void of any files... What is AOKP?
Thanks!
YKBtpt said:
1. Which app has what permissions? Root Browser or the app I want to get rid of?
- When I long press an app and click properties, it says "Permissions: N/A"
- The Root Check Basic app says that I have root access.
2. /data is void of any files... What is AOKP?
Thanks!
Click to expand...
Click to collapse
1. Sorry, but i don't know whats wrong then. Maybe you can install ES file explorer, enable root from setting and try deleting the with it?
2. Aokp is a rom. Its install includes deleting files and moving the rom after that.
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Sent from my ARCHOS 101G9 using xda app-developers app
zROM+ 28.0.A.8.251 Android 5.0.2 - V1.1Sony Xperia Z3+ E6553
ROM Features
Based on Sony firmware 28.0.A.8.251 Generic Hong Kong
Aroma installer
Deodexed and zipaligned
Rooted with SuperSU preinstalled
Dual boot/ TWRP recovery environment
Custom kernel with runtime control of SELinux enforcing status and RIC disabled
Google apps updated and with customizable graphical installer for Gapps
Writeable external SD card
Xposed framework functional (in SELinux permissive mode)
Bloatware removed
The following apps and bloatware have been removed and can be installed directly from the Play store if desired. The first two are installable by selecting the appropriate option in the ROM installer
What's New
Xperia lounge
AVG Antivirus
AAStocks
Anonymous Data Collection
Facebook
Lifelog
Mobisystems File Commander
Mobisystems Office
MyXperia
Playstation App
Playstation Network Portal
Privilege Movies
Sketch
Socialife
Sony Movie Creator
Spotify
Trackid
Please hit the Thanks button if you use this ROM. Many downloads but few thanks....
Installation instructions
NOTE: You must perform a factory reset before install by wiping cache and data.
Click to expand...
Click to collapse
Step 1
Download the TWRP image for the Z3+ and unpack it
Download zROM+ and the zROM+ md5 file
Run a command shell
Code:
c:>adb reboot bootloader
c:>fastboot boot recovery.img
c:>adb push zrom-v1.1.zip /sdcard/zrom-v1.1.zip
c:>adb push zrom-v1.1.zip.md5 /sdcard/zrom-v1.1.zip.md5
The file is big, so it will take 5 or more minutes to complete the upload. If you're impatient put your external SD in a card reader and load it that way.
Step 2
In the interface for TWRP, navigate to Wipe and perform a factory reset
In the interface for TWRP, navigate to Install
Click install, select zrom-v1.1.zip from the internal storage
Swipe to flash
Read and follow the instructions
Reboot when complete
Click to expand...
Click to collapse
The first boot is painfully slow. It takes about 10 minutes, so just be patient. It will stay in the blue booting screen for a long time. This is normal. Do not reboot your phone. Just wait and it will eventually boot up. You can always rerun the installer to flash additional Google Apps. If you do so, be sure to deselect the install ROM option and do not do a factory reset.
Notes
This ROM has a kernel that supports runtime SELinux mode changes. The mode change is accomplished through a script /system/su.d/permissive.sh, which sets SELinux to permissive mode at boot time. If you wish to run Xposed, you must run SELinux in permissive mode. Failure to do so results in multiple system applications force closing at startup and a device that is locked up.
If you don't run Xposed I recommend that you keep SELinux in enforcing mode. To do so, go to Settings-->About and click multiple times on the Build number until it tells you that Developer mode is activated. When developer mode is activated, back out and select the Developer option and enable USB debugging. Now run an adb shell and remove the permissive mode script. Grant permission for USB debugging when the prompt comes up
Code:
c:>adb shell
[email protected]:/ $ su
Wait for the SuperSU prompt and grant permission to adb
Code:
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # rm -f /system/su.d/permissive.sh
[email protected]:/ # reboot
If you choose not to install any of the Google apps, a minimum core Google framework will be installed anyway. This includes Google framework, GmsCore, Google Play, Google Login Services, Google Contacts and Backup Sync, SteupWizard and OneTimeInitializer that runs after first boot. Apart from the Play store app and the first time setup apps, the rest of these apps are not visible in your app drawer.
While I have made every effort to test this ROM in a variety of different install scenarios, it is a beta ROM and you may experience some bugs. I make no warranty as to its fitness for purpose or its performance and you use it at your own risk.
PLEASE SEE NOTE BBELOW IN POST TWO ON USING XPOSED FRAMEWORK
This ROM now supports booting directly into TWRP recovery mode. To access recovery mode, power on the phone and when you see the yellow LED illuminate press the down volume button once or twice.
Downloads
TWRP v2.8.7.0 for Z3+
zROM+ v1.1 for Z3+ (md5: 999452b5ac29f92473b964af819a3cd6)
zROM+ v1.1 for Z3+ MD5
for GPL purposes, the kernel and associated dowloads
Changelog
Current changelog: -- 01 October 2015
01 October - Release v1.1
Add dual boot/recovery environment
Remove Android Pay due to Google restrictions on root
Update Google apps
19 September - Release v1 beta
Thanks To/Credits
amarullz for the Aroma graphical installer
The OpenGapps team at www.opengapps.org for the Gapps binaries for aarch64
osm0sis for some of the functions used in the installer script
XDA:DevDB Information
zROM+, ROM for the Sony Xperia Z4
Contributors
dl12345
ROM OS Version: 5.0.x Lollipop
Based On: 28.0.A.8.251
Version Information
Status: Beta
Current Beta Version: v1.1 beta
Beta Release Date: 2015-10-01
Created 2015-09-20
Last Updated 2015-09-19
Xposed framework v74 bootloops on Xperia Z3+. The reason for this is discussed in this post
To use Xposed on zROM+, please download the [UNOFFICIAL] xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929 for Xperia Z3+
You MUST do a wipe cache and dalvik after installation otherwise you will get errors including one that claims your storage space is full and another 504 error when installing anything from the Play Store
Please read the instructions in the referenced post
Have been waiting for this with baited breath. So far so good! Thanks for the great work!
Do need unlockbootloader to install rom?
manhhung1420 said:
Do need unlockbootloader to install rom?
Click to expand...
Click to collapse
Yes.
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Rookie123 said:
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Click to expand...
Click to collapse
Offhand, I'd say it's unlikely. Sony has a different firmware for this phone.
I'm unlikely to support a device I don't have access to. Apologies.
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
pikeylfc said:
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
Click to expand...
Click to collapse
There's probably something in the xposed repository for that....
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
lilloscar said:
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
Click to expand...
Click to collapse
Sorry to hear what?
dl12345 said:
Sorry to hear what?
Click to expand...
Click to collapse
That this rom wont support the dual version
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
chrisss5000 said:
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
Click to expand...
Click to collapse
No problem here accessing my external SD card in recovery mode and when booted in the ROM. Have you formatted your external card? In recovery mode, the path to the external SD card is /external_sd...
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
chrisss5000 said:
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
Click to expand...
Click to collapse
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
dl12345 said:
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
Click to expand...
Click to collapse
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
chrisss5000 said:
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
Click to expand...
Click to collapse
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
dl12345 said:
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
Click to expand...
Click to collapse
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Yes it is Xpera Z3+ E6553
Okay I will test it now! I will come back with results
big thanks!!
---------- Post added at 08:05 PM ---------- Previous post was at 08:00 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Uhm should the installing just take 15 sec? I nearly drop my finger from the screen and it is wiped....something is wrong...
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
it dosent work...it only get stuck at sony loggo
I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.
Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk
i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox
I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.
@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.
Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?
phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.
Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"
Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.
Model Device: XT1676
Yesterday I unlocked the bootloader, the message "ID: bad key" appeared when the phone was started. I ignored this, I flashed the 64bit twrp and here the problems start - I've tried many roms:
- FireHound v4.5,
- AospExtended v5.4,
- BootleggersROM 2.2,
- dotOS 2.1 and 2.2,
On all roms (except for dotOS 2.1) the same problem appears - the system itself works and starts correctly, but when I flash any version of Open Gapps the phone falls into the bootloop, the exception is dotOS 2.1, it works fine, but there are not many functions has dotOS 2.2, interestingly - when I flash dotOS 2.1, gapps, run the phone and then I do flash update to 2.2, everything works fine, but I would like to use another rom, but all have the same problem, does anyone know how I fix it?
And as for "ID: bad key" - I can not even relock the bootloader and unlock again (I read that helps), because the phone has a bootloader with the NPPS25.137-93-8 stock version, which even can not be downloaded anywhere, and the flash attempt of the older stock is canceled due to the older security patch.
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
TheFixItMan said:
The message bad key is normal - you can replace the splash screen if you want
Make sure you have formatted data
Some roms require a certain type of gapps - if it's a 64bit rom make sure you are using 64bit gapps
Check thread 1st post and user comments for any information on this
Some users have reported booting the rom first without gapps then Data wipe only then flash rom & gapps again
You can also try disabling the welcome screen on first launch
In twrp, mount /system, go to advanced, terminal and type
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
Click to expand...
Click to collapse
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Wanted_X2 said:
Booting the rom first without gapps then Data wipe only then flash rom & gapps again didn't help, I use the latest arm64 gapps but I still have a bootloop on almost all the latest roms, disabling setupwizard didn't work - The only roms that work for me are those from before April.
EDIT
I downloaded the build.prop through ADB, edited it over the computer and sent it back to the phone - it helped, thanks for the advice.
Thread to close.
Click to expand...
Click to collapse
how did you get build.prop by adb? in twrp? what commands? thanks
durc12 said:
how did you get build.prop by adb? in twrp? what commands? thanks
Click to expand...
Click to collapse
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Wanted_X2 said:
Yes, I used ADB, commands:
to download build.prop - adb pull /system/build.prop
after edit, to push file into device:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
There is full tutorial: www.ultimatetech.org/edit-build-prop-file-android-withwithout-root/
Click to expand...
Click to collapse
I install the rom, then the gapps, but it says to me that no build.prop is ther with the pull command, I don´t know why
EDIT: finally I did it, but it was neccesary to mount /system in twrp, to check the box in "mount". Thaks for all
You can find latest radio on lineage 15.1 thread
aljoscha81 said:
So here i post new radios when the stock 8.1 will be updated feel free to test.It is maybe not the fact that something is changed in new radio but in changelog it is also point out that not every change from build to build is written in so testing testing testing.............. :fingers-crossed::highfive:
Ps. Sorry for my bad english
Radio v:5.42:https://mega.nz/#!iq5xgSZZ!J6uTZQ39enNcrWrCGIKofVEzxKti75Myb_VhJJVxl0s
Click to expand...
Click to collapse
Android 9? How you did it?
Deleted
Pie
Deleted
Deleted
It was released a new radio update 5.50
Deleted
aljoscha81 said:
Yes i am on latest build arrow os 9 treble rom i got nearly everything working only nfc don't work for me you must be on mokee 81 rooted with magisk 17.1 installed total commander delete with total commander in system/vendor/ lib and lib64 vndk-sp folder with all in it then create in system/vendor a folder called overlay in the overlay folder copy and past the apk from this thred :https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965
Then from terminal run this command first:
mount -o remount,rw /vendor
Then the command from the thread you got the apk. From
Restart
Then you flash twrp 3.2.3-3 in this forum you can find it
Wipe in advanced wipe everything format data make factory reset restart to twrp
Use otg device with extracted img. Of arrow os and choose img. Install choose system for where to install
After image is installed boot to system
Now you must install open gapps in twrp
The system will run crazy while you are not got a registred device but you can install device id apk. In device id apk tab google service framework tab copy tab on the message your device is not registred on custoum rom link log in with your gmail email and password in the row to put in you past what you before copyed in the id apk. And tab register a few reboots and the messaging will stop now in settings you see you can set up your phone and voila you on android p
Ps for camera is also a fix out there so face unlock also works
Click to expand...
Click to collapse
please share step by step
Deleted
Deleted
aljoscha81 said:
New update
Click to expand...
Click to collapse
Thanks
This should be the last update to come, right? Nubia themselves said they stop developing Android 8+ for Z17. Any luck with GPS tracking on last update (taking ~2 minutes until it can track you properely)?
Deleted
Deleted
Any radio more than 5.52?
Deleted
Deleted