[Q] rooting thedigiland DL701Q, version 4.4.0 - Android Q&A, Help & Troubleshooting

hi, i have a digiland tablet that i have tried rooting without success. its model is DL701Q, version 4.4.0. i have tried all of the rooting methods that i could find. from my investigation, there appears to be no specific rooting method for the version and model.
has anyone with this tablet successfully rooted it yet?

I find root genius to work on it.

wkLeon said:
I find root genius to work on it.
Click to expand...
Click to collapse
Thanks! It worked. The root program took a little while to do it, but it worked.

Failed
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).

stock recovery and fastboot access
ndrsconschrtysvcs said:
Root Genius rebooted the device several times, then showed failure in rooting. Nothing critical - it did not work however.
This is AFTER there was a 130MB OTA update "Wireless Update" that 'fixed some security issues' and I had already applied it wondering what it would do.
Go into About Phone and you will see Wireless Update as the second option below System Update. Hold off on applying it if you want root. As you will also lose root when applying it.
Off-the-shelf:
>adb shell
produces a $ prompt instead of a # prompt like it used to.
These devices are rootable off-the-shelf. Once the OTA has been applied, not at this time.
See also:
http://forum.xda-developers.com/chef-central/android/help-rooting-digiland-tablet-dl701q-t2960712
http://forum.xda-developers.com/android/general/digiland-dl700d-tips-tricks-t2867764
http://forum.xda-developers.com/android/general/digiland-dl700d-tablet-kit-kat-t2851783
http://forum.xda-developers.com/android/help/digiland-android-tablet-root-t2816435 (four pages)
In short, -and I read all the prior threads, so this is a summary to-date-, if you accept the update OTA, you will lose adb shell root access, and Root Genius will no longer work.
It does seem to work on the device off-the-shelf (without applying the OTA).
Click to expand...
Click to collapse
Opps, meant to reply in the this thread. See my other post:
forum.xda-developers.com/showpost.php?p=57557683&postcount=35

Related

ATT 2.3.6 OTA failed

I finally gave in to the update nagging screen and tried to update.
My phone was rooted with preinstall method, nothing else.
I was on 2.3.4 (4.5.91).
I installed RootKeeper and unrooted before the update (kept root backup).
The phone downloaded the update, restarted, and I saw the Android Icon and an "unpacking" progress bar. The bar stopped about half way and the icon turned into an exclamation point. I thought I was toast....
The phone rebooted fine, everything still there. I got a message box "Update failed" once I got on my home screen. The phone is still 2.3.4. The update nagging is gone.
I have pretty rare reboots, maybe 2 a month. I am quite happy with it.
Anyone had the same issue? Should I even bother going to 2.3.6?
The only thing I am really missing on the Atrix is HDMI mirroring option with 720p or 1080p up-conversion.
How can I get the cause for the "fail"? Should I use the Moto USB method?
I wouldnt mind going to CM9 but I want the Finger Sensor, Camera etc all to work. I dont want to loose any current functionality going to CM9 and its not there yet, correct?
Thanks!
I would just stay where you are at. Unless you really want the mirroring. You seem to not mind stock so I would wait for Moto to release ICS for the Atrix. They put it on the list.
if you only rooted, did nothing else that requires root (freeze apps, put files in /system, etc) and did not unlock the bootloader, just unroot and then apply the 2.3.6. update.
Code:
1. Open Android Terminal Emulator (ADB)
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
spacev said:
thx guys,
so you are saying that it failed because the unroot in rootkeeper did not do it right?
so with the manual unroot it should work? is there anyway to see why the update failed? log file or smth?
Thanks
Click to expand...
Click to collapse
There have been posts in various 2.3.6 threads where rootkeeper did not work if you used the fastboot preinstall method.
It should work if you manually unroot as long as everything else is stock.
for seeing why the update failed, hold the Volume up and power button when the error appears and you should see some sort of error msg...never tried it myself though.
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
otter9309 said:
I have the same issue. I used the preinstall root as well as unroot. I have not found a way to install the update. I tried OTA (I am locked) and I also tried to install from SD.
No dice
Click to expand...
Click to collapse
Did you undo everything that requires root access prior to applying the OTA? I usually do the following prior to an OTA (and redo once the OTA is applied):
uninstall Swype beta, restore stock Swype files (the so and apk files)
move ringtones out of /system/media
Help Needed
Hi All,
I am a newbie here and I am not sure if my question makes any sense. Couple weeks back, I bought an Atrix 4g (US version), an unlocked version (the seller told me that this phone is unlocked using AT&T code) and I am using it with Vodafone (India) sim. It works perfectly and so far I didnt face any problems with this phone. But last week, I got an alert in phone saying that software update (2.3.4.5.141) is available for AT&T users and enable wifi to download. However, I didnt download and install the update as I was not sure why is it saying the update is available only for AT&T users. Also wherever I read about this software udpate, the name 'AT&T users' come along with that.
So my doubt here is, what will happen if I, who is not an AT&T user, download and install the software update in my phone ? will it cause any issues in the phone (like getting locked again or bricking the phone)
I have not done any modification like rooting or installing custom ROM and things like that and I am using the phone as I recieved it.
Thanks in advance for your help.
-Qaddaffi

[Q] Unable to write to /system

HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?

Fire OS 5.0.0 Help?

Hello, I have a Fire HD6 Running Fire OS 5.0.0. I am trying to use the file for 5.2.2u2 to update. When I go to settings>>device options>>system updates>>check now, it says there are no updates. If I put the file at /sdcard using a computer and turn on airplane mode, I can hit the update button and it looks like it is going to update, but when it reboots, it says i am still on 5.0.0. ADB works, but adb reboot recovery just boots normally. I had TWRP until I updated to 5.0.0. I really need help. Thanks in advance.
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
DoLooper said:
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
Click to expand...
Click to collapse
Is there any way to get TWRP and Root at 5.2.2u2 and get play store, or am I doomed to have an unrooted device forever? Will update in a few minutes about things you said to try.
Update: adb push 5.2.2u2file /cache results in permission denied. Trying to enable packages via adb also results in permission denied. Debloater says no packages are blocked. I would really appreciate it if I could get root and playstore on this thing. Thanks in advance.
Well, since you're unrooted without recovery you may have to go the replacement route. But first see if @bibikalka has an alternative.

Kindle Fire HD 7 (4th) Root Issue (?)

I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
doobius said:
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
Click to expand...
Click to collapse
If you are on 4.5.3 bootloader you can easily boot to unsigned recovery images. So install flashify and download the twrp for ariel and flash it:
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
So here you can install any zip, but when you finish, restore the correct recovery.img. For example: If you update to 5.3.6 with TWRP, then flash the 5.3.6 recovery.
But be careful of what you do, you can brick the tablet by flashing wrong bootloaders.
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
doobius said:
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
Click to expand...
Click to collapse
Wow very nice. You can use this toolbox in the next version since the dev will add support for ariel for debloat and do more things without root:
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
doobius said:
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
Click to expand...
Click to collapse
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Rortiz2 said:
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Click to expand...
Click to collapse
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
doobius said:
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
Click to expand...
Click to collapse
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Rortiz2 said:
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Click to expand...
Click to collapse
PS \ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb shell
[email protected]:/ $ su
1|[email protected]:/ $
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
doobius said:
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
Click to expand...
Click to collapse
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Rortiz2 said:
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Click to expand...
Click to collapse
good idea. but that failed too.
doobius said:
good idea. but that failed too.
Click to expand...
Click to collapse
So then try installing google play as in Fire 7 2015/2017.
You have two methods:
- Manual: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
- Automated tool: https://forum.xda-developers.com/amazon-fire/general/tool-amazon-fire-7-7gen-fire-os-5-6-x-t3815112
(Use install google play option).
When you logged in and setup it correctly, proceed to update supersu installer tought Play Store.
ok sir, you are on to something...
i downloaded the playstore stuff via that link you sent.
i logged in to playstore and went back to the supersu installer i already had.
i clicked play.
it took me to the same playstore suspersu program and it says it is currently unavailable.
i searched supersu and found the main updated download.
i hit open and it took me back to the installer i already have.
i went back and noticed the update option in the playstore and selected that.
it updated and is now saying that the su binary needs to be updated and is asking me to continue.
awaiting your godlike instructions.
the next screen says, "if you have a custom recovery like twrp or cwm, that can be used to (try to) install the SU binary. this is recommended for HTC devices. how would you like to install the SU binary.
normal or twrp/cwm?"
normal, right?
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
doobius said:
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
Click to expand...
Click to collapse
Yay!! You have root!! Now that you have root. I will recommend you to flash a working recovery.
Pinging some people that may help creating the stock recovery: @k4y0z @bibikalka
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
doobius said:
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
Click to expand...
Click to collapse
Ok. DON'T DO ANYTHING UNTIL YOU RESTORE WORKING RECOVERY.
First we need to create a working recovery image. Can you check if there's install-recovery.sh in system/etc and in system/bin please?
i dont see that, but i'm probably not looking in the right spot then. how do you suggest i check for this?

Root and software update

Hi guys, my questions would refer to root privileges with regard to OTA software update...
But firstly...
Do you think that KingoRoot apk constitutes a reliable root service? Do you think one can root his/her device just by installing the app via browser in the phone and launching the root process?
And now the initial question:
Do you think that OTA software update can remove root from the device? Or, does the fact that one can perform OTA software update indicate that there is acutally no root on the phone?
(Device: Samsung Galaxy J5 2016)
Thanks!
Yannikk said:
Hi guys, my questions would refer to root privileges with regard to OTA software update...
But firstly...
Do you think that KingoRoot apk constitutes a reliable root service? Do you think one can root his/her device just by installing the app via browser in the phone and launching the root process?
Click to expand...
Click to collapse
Generally no - Android functions such as Verified Boot and dm-verity are supposed to prevent persistent rootkits, unless the bootloader is unlocked. Yes, there are some exploits, but usually these only provide temporary root.
As a general rule I advise against using closed source software, simply because you don't know if there's anything malicious going on under the hood. A safe alternative is Magisk, although this does not utilize any exploits, so you would have to unlock your bootloader and root the "right" way.
Yannikk said:
And now the initial question:
Do you think that OTA software update can remove root from the device?
Click to expand...
Click to collapse
Yes - in most cases, a OTA update overwrites several partitions on the device, including /boot and /system. This means that after rebooting from an OTA update, root would no longer be available. The workaround for this is the "Patch to inactive slot" function in Magisk on A/B devices - once the update is complete and the device is ready for a reboot, Magisk uses root privileges to patch the new boot image, so that root persists after reboot.
For A only devices such as Samsung, it's a bit more tricky...you'd need to flash a custom recovery after the update and flash Magisk from there.
Yannikk said:
Or, does the fact that one can perform OTA software update indicate that there is acutally no root on the phone?
Click to expand...
Click to collapse
Not always. In most cases, update_engine conducts various checks to determine whether critical partitons such as /system and /boot are intact and untampered; if they are, the update will fail. This is why Magisk has the "Restore images" function for systemless root - Magisk restores the unpatched boot image written to flash, so that the device may pass these checks. It doesn't always work, and on the opposite end of things, there are some devices that will happily install an OTA update even with modified binaries present on the device.
Thanks for you answer, V0latyle.
Now, I would present a broader picture of an issue that gains my attention...
It happend some time ago, on an older device (Galaxy J5 2016, as mentioned)...
I installed KingoRoot apk (directly via browser in the phone) and launched rooting process... The app signalized that the rooting process has been successful... I did not install any custom ROMs or apps... The phone functioned pretty normally then... However, after few months, out of the blue, my device started behaving strangely... Videos on YT took a great amount of time to load or they lagged after some time... Newsfeed on IG did not work, nor instastories... Browsers were also considerably slower... Approx. 2 months later, when Nougat 7.1.1 came out and after I downloaded this software update (OTA), the phone got somehow faster - YT videos loaded faster or did not lag, IG newsfeed got updated regularly, browsers were not so slow either... On the other hand, yes, some apps still behaved in an unusual way...
Do you have any idea what might have happened in this case?
Thank you very much for any suggestions!

Categories

Resources