Related
As the title suggest, does anyone else having such (one, more or all) issues on Nexus 5 after root?
1. Kitkat kinda initializes after every reboot. Not like the very first time starting the device (setup assistent) but installing/updating apps (which) are already on the device (same Verstion) and re-setting configuration to what it already should be.
2. Always showing H (internet connection) and at least two bars on signal strength even when there is no signal (accourding to chrome and (stock) dialer app.
3. Loss of signal but pretending there is one (like in 2.) and only regaining signal after reboot.
4. Loss of distance between apps within the appdrawer (more apps per page) until uninstallation of an app (remains normal after reinstall)
5. many app crashes (before and after rooting)
6. sometimes notification led keeps blinking after notification was dismissed, sometimes the notification led blinks very fast.
I rooted my device with cf auto root.
Except for 4 &5, yes.
I am glad that I am not alone but does anyone know whats the source of this strange behaviour or how this can be fixed?
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
Wugfresh's toolkit is imho the best and safest way to root and do most changes to all nexus devices. About the only difficult you may experience is usb driver/connectivity issues. The usb driver guides are well documented and easy to follow. It's no different than the standard adb usb drivers. Most have no issues, but that is the only thing that can cause problems with adb or Wugfresh's toolkit.
Read through Wugfresh's forum topic to acquaint yourself with mtp/ptp and driver installation and you should breeze through using his toolkit.
Sent from my Apple ] [e using ProTERM 2.2
Nik_B said:
Is there a good low-risk way (manual/tutorial) to manually root without a custom rom and custom recovery (CWM/TWRP) ?
Because besides root access I want to stay as close as possible to stock.
Click to expand...
Click to collapse
custom recoveries do not prevent the OTA.. plus you can just fastboot boot recovery whateverrecovery.img
i blame your problems on the CF-autoroot as i have none of the symptoms you describe.
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Nik_B said:
Looking into the script chainfire offers shows me that there are only 2 commands executed.
the
fastboot oem unlock - command is clear to me that it unlocks the bootloader
but i have some questions about the second one: fastboot boot image\CF-Auto-Root-hammerhead... ...nexus5.img
Am I correct assuming that this command tells the bootloader to start this image instead of the regular android (once?)
which modifies "something" within the "original" android os (image)?
If yes, can somebody tell me?
Is the only modification made there the mount configuration of the system partition and/or user settings?
Is a documentation for such internal matters of rooting somewhere out there?
yeah I know I have lots of questions and yes I am very curious.
Thanks in advance
Click to expand...
Click to collapse
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
DreamLinker said:
In a case like this i would go back to stock, make a factory reset and then rooting the N5 again, manually, without using cf auto root.
Rooting manually it's just a good way to understand the android OS, and how it's made, imho.
Click to expand...
Click to collapse
Go with this guy.
As soon as I read your thread title, I knew you rooted using an "auto root". Rooting a device is actually very simple, just takes a few minutes of your time to research the steps. As long as you have 10 minutes, a USB cable and a Windows Computer, it should be easy and result in a errorless experience.
Zepius said:
unless someone looks into the boot image CF has setup, there's no way to tell what his image does.
thats why its easiest to just boot a custom recovery and then flash supersu.zip, yet a lot of people want to just use toolkits cause "its easier" but when you do use a toolkit, you end up with issues.
Click to expand...
Click to collapse
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Nik_B said:
I already know that. Maybe my question was not correct.
What I wanna know is what happens when i flash a custom recovery, root my device and so on in the background
and what are necessary steps to such actions?
Because I would like to do all those actions on my own. (for example make my own image to boot for rooting)
But I won't unless I know exactly WHAT I am doing.
Hope this for wording made my intentions clearer. (Sorry I am not that good in English)
Click to expand...
Click to collapse
fastboot boot recovery recovery.img - this just boots into the recovery once, but leaves the stock recovery as the recovery that is written to the device
when you flash supersu.zip what it does is execute a script that places the su binary in /data/xbin i believe and gives it the proper permissions, and also places supersu app on your phone.
you do not need to make your own boot image, or anything of the sort.
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
joshnichols189 said:
The root process is not capable of causing any of these issues. Root using wugfresh is the exact same as using auto root and both of these are the same as manually doing it yourself. None of them can cause visual changes or signal loss alone, and the only reason we don't recommend toolkits or auto root is so people don't get comfortable with the idea that they don't need to know fastboot commands in the event that they boot loop, etc.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do I understand you correctly that neither wugfresh nor auto root are causing the problems in your eyes. I´m just curious because many people including me used Chainfire´s auto root but not all of them are reporting problems. In my case the Nex5 seems to forget already set default apps e.g. for tapatalk links, urls etc.
Cheers, T.
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!
xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!
Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!
KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!
KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?
I will take delivery of a new Pixel 3a later this week. I will thoroughly read through “How to root the Pixel 3a with or without twrp & take OTA updates once rooted” and “How to Root Your Pixel 3a and Install Magisk (on Pie & Q) with or without TWRP”. But before unlocking bootloader and rooting should I accept all updates first during the initial setup?
MrTooPhone said:
I will take delivery of a new Pixel 3a later this week. I will thoroughly read through “How to root the Pixel 3a with or without twrp & take OTA updates once rooted” and “How to Root Your Pixel 3a and Install Magisk (on Pie & Q) with or without TWRP”. But before unlocking bootloader and rooting should I accept all updates first during the initial setup?
Click to expand...
Click to collapse
Yes
bejunk said:
Yes
Click to expand...
Click to collapse
Thanks. The little reading I have done so far, it sounds like you can not flash or boot TWRP in Android 10. Won't all the updates take me to 10? I will want to back up my ROMs.
MrTooPhone said:
Thanks. The little reading I have done so far, it sounds like you can not flash or boot TWRP in Android 10. Won't all the updates take me to 10? I will want to back up my ROMs.
Click to expand...
Click to collapse
Oh, i forgot as i dont use TWRP anymore.
Yes TWRP only works on Android 9.
However you can't install it like in the past time. You can only boot it via fastboot. You need to do this everytime you want to use TWRP. However when i tried it in past times it did not work well afaik, a full backup did not work at all.
So yeah try it with Android 9 first.
But with all the google backups nowadays i dont have the need for a nandroid (twrp backup)...
Especially as you can just reflash the stock image with deleting /data.
Here is the main thread, i think it will be more helpfull than i am https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413
The very first thing to do is minimal setup so you can enable developer settings and allow bootloader unlocking. That's a sticky setting, so then you can update, factory reset, etc. before actually unlocking the bootloader and rooting. Especially important if you're US/Verizon (don't put your SIM in until bootloader unlocking is enabled).
mike.s said:
The very first thing to do is minimal setup so you can enable developer settings and allow bootloader unlocking. That's a sticky setting, so then you can update, factory reset, etc. before actually unlocking the bootloader and rooting. Especially important if you're US/Verizon (don't put your SIM in until bootloader unlocking is enabled).
Click to expand...
Click to collapse
Thanks. So I read the two rooting threads I referenced above. I have always used TWRP in the past, but seeing it not supported in Android 10, I am considering skipping that. Do you think TWRP will support Android 10 in the future? I am a little nervous making changes without a backup. My plan would be to stick with a rooted stock at first than consider migrating to a custom ROM. Any recommendations are appreciated. Phone will be delivered tomorrow.
bejunk said:
But with all the google backups nowadays i dont have the need for a nandroid (twrp backup)...
Click to expand...
Click to collapse
I am not sure what you mean by "google backups nowadays". Is it the availability of stock ROMs?
MrTooPhone said:
I am not sure what you mean by "google backups nowadays". Is it the availability of stock ROMs?
Click to expand...
Click to collapse
No , I think most people use a TWRP backup because it restores you to a specifiic point with all your apps, user settings and your data in those apps.
Thats why i used it in the past times. Setiing up a phone in the past could be really time consuming and frustrating.
But nowadays, if you use the google backup (in Settings > System > Backup) (and the whatsapp one for messages - thtas the only messenger i use, but every other popular messager has a backup feature now) setting up the phone takes maybe 10 mins when i flash the factory image, it even gets my homescreen layout and my wallpaper back, also my settings. Apps which support that also keep their settings.
In the past i allways had a custom rom, because stock rom sucked. But with the Pixel theres no reason for me to use a custom rom anymore.
About root, i rooted my phone since i first used android, ca. 2010. But now I really dont need it anymore, so i just keep things stock.
---------- Post added at 16:03 ---------- Previous post was at 15:50 ----------
MrTooPhone said:
Thanks. So I read the two rooting threads I referenced above. I have always used TWRP in the past, but seeing it not supported in Android 10, I am considering skipping that. Do you think TWRP will support Android 10 in the future? I am a little nervous making changes without a backup. My plan would be to stick with a rooted stock at first than consider migrating to a custom ROM. Any recommendations are appreciated. Phone will be delivered tomorrow.
Click to expand...
Click to collapse
I dont think TWRP will be supported in the futur on A10. Google locked up /system and some other partitions the TWRP team needs to find new solutions but there id not much hope.
Did you buy your phone unlocked? If yes, the worst part you should be worried about is losing you app data from some apps. You cant really brick your phone. In the worst case you just need to flash a factory image.
You should know that rooting your phone will probably break google pay and banking apps. May i ask what did you want use root for?
I dunno, I really like Lineage OS, but it just feels like a downgraded stock rom.. (I used it before all the time on all phones before getting a pixel).
Also, for every update (monthly) you need to patch your boot.img, flash it, and the apply the update. Its some work which i dont think is worth it anymore.
bejunk said:
May i ask what did you want use root for?
Click to expand...
Click to collapse
Thanks for the detailed reply. I am coming from a MotoG3 (rooted stock), a 2015 era phone. So a lot has changed. I really have not seen a mid range phone I really liked, so I jumped on the P3a when I heard the news they were being discontinued.
I use root mainly for Adfree, SD-Maid, and Titanium Backup. I used to use Cerberus until the developer reneged on a lifetime subscription. I don't mess with the system apps much, but I do keep a few apps frozen except for the times when I seldom need them.
Magisk is the best way to root your phone as it still passes the SafetyNet check and google pay and banking apps continue to work. There is an excellent thread here on how to do it.
[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted
Every month, I "uninstall" magisk (which really just restores the original boot files) and sideload the latest update, then I install the magisk-patched boot.img and my phone is rooted again.
To be honest, I don't miss twrp at all. adb and fastboot are all that's needed. The backup in android 10 is perfectly sufficient.
This phone is practically impossible to brick. I love my Pixel 3a, except for the one problem I had when the bottom speaker died and I had to have it repaired under warranty at the local ubreakifix in less than an hour.
MrTooPhone said:
Thanks for the detailed reply. I am coming from a MotoG3 (rooted stock), a 2015 era phone. So a lot has changed. I really have not seen a mid range phone I really liked, so I jumped on the P3a when I heard the news they were being discontinued.
I use root mainly for Adfree, SD-Maid, and Titanium Backup. I used to use Cerberus until the developer reneged on a lifetime subscription. I don't mess with the system apps much, but I do keep a few apps frozen except for the times when I seldom need them.
Click to expand...
Click to collapse
Yeah, I had that phone too It was pretty good for its time. I even replaced the screen once, but its really complicated on that phone... To your needs:
Adfree: you can setup a custom DNS server (i think it was adguards one) in the settings menu which will block all ads, so no real need anymore for adaway or root for this. Just google a bit.
Titanium backup: I does not work so well is what i heard and like said nowadays most apps backup over Google backup. With Android11 it will get even harder as /data partition is even more protected now. Not really worth it imho.
Froze system apps: Pixel Android is really barebones. The few apps which i dont need (like Google Music/Video PixelBuds app etc) you can just disable them in the settings. This will freeze them, its like uninstalling them, they wont show up at all.
SD Maid is great but only rooting it for using it, is not worth it. You can clear the cache of the apps which hoard a lot of data by yourself. Also, when you uninatll an app, it asks you if you want to delete your userdata as well. The phone takes care of the rest.
Cerberus: If you keep your bootloader locked, when your phone gets stolen, nobody can access your phone. Even if they reflash it, on first boot it will ask to login to the gmail last time set up. Theres no workaroud. Google aslo has a find my device thingy, wher you can track or delete your device remotly.
I would suggest to use your phone unrooted for some time, and if you really need to root it for something, you can still do it.
Welcome to team Pixel, mate!
(sorry my grammer im to lazy to double check it...)
@bejunk Just a not to say thanks again. I took your advice and did not root. However, I did flash with GrapheneOS and then re-locked the bootloader. Time will tell if I like it.
I installed new soft to my phone and i lost some of photos, screenshot
If I rooted my phone, can I recover my data that was lost after the software update? Can I unroot it later without any effects or issues with banking apps and financial services?
Also, I hope there is a way to retrieve photos and files without rooting the phone because I have tried several methods on both the phone and PC, but they are not recognizing the device even though it appears on the Explorer.
Short answer:
1. A stable wired / wíreless ADB must be given
2. The partition that holds the data in question must be decrypted
3. The phone must be rooted
4. The partition in question must get dumped to PC
5. An external forensic software is needed to read the dumped partition / fles in question
shadyhoo said:
If I rooted my phone, can I recover my data that was lost after the software update?
Click to expand...
Click to collapse
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
What are the uses of temporary root?
This post says it is not possible in Android 6 and newer.
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
Can you provide more information on this? Even links to existing posts would also do fine.
I'm interested to know if it can be used to debloat the system without tripping Knox or other disadvantages of an unlocked bootloader.
TheMystic said:
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
Click to expand...
Click to collapse
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
shadyhoo said:
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
Click to expand...
Click to collapse
Activating that option is just the first step. There are other things to do to unlock the bootloader.
Since your bootloader is locked as I expected, rooting to recover files is out of question now. That's because if you follow steps to unlock the bootloader, it will wipe everything on your phone. The question of recovery won't arise.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
My phone is sony xperia xz1 compact
If you root the phone, will this cause a problem with banking financial applications?
is it possible to completely remove the root after that without any problem or I will need to make a new software?
As I can see you've no idea what rooting Android means: it's simply spoken adding SU binary to Android's
filesystem - preferredly put it into RW-mounted /data/local/tmp directory. My recommendation: Become familiar with this, e.g. look inside here.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
alecxs said:
get yourself a smartphone and learn the basics. I will pay $ 100 if you show any proof of your magic temporary root.
Click to expand...
Click to collapse
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
alecxs said:
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
Click to expand...
Click to collapse
That's what happened to me an error occurred and the phone froze and then rebooted continuously, it never works, I tried to turn it on for a whole day uselessly bootloop continuously ,
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
through Google backup downloaded applications, messages, etc.,
but personal photos and files do not exist, and this is what I'm looking for
Do I have any chance to get my photos back or is there no chance ?
shadyhoo said:
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
Click to expand...
Click to collapse
This counts as factory reset, therefore no chance sorry.
I'm sad to see so many people get into this position.
Backing up the data to MyMegaApp can be complicated because some of that is stored in /data/data/com.mymegaapp/...
Some of that is stored in /sdcard/Android/data/com.mymegaapp/...
Photos are generally stored in /sdcard/DCIM/Camera and that is trivial to backup.
Photos are probably the most valuable thing you have on your phone.
For Windows user, you can use my adbsync.exe in my sig.
Here is one line out of my "sync" script (actually a makefile):
Code:
adbsync /hscu /s C:\Handy\MotoG storage/emulated/0/DCIM/Camera
So at the same time I make sure that all my books and guitar transcriptions are on my device I also backup all the photos.
This probably happens multiple times a week.
And of course I backup my desktop too.
Renate said:
This probably happens multiple times a week.
And of course I backup my desktop too.
Click to expand...
Click to collapse
This. Or just do not care attitude. I still had that when the 1st mSD died. 2nd was bad, about half year of photos and such went. Still hoping to recover it somehow. Then 3rd one went not so long ago. Windows "fixed" it, but now it has some folder added, with files that I don't what they all are... less than a month of damage this time...
So, like Renate said, take backups and take them often.
Adbsync is really good indeed.
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
edit a typo
CXZa said:
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
Click to expand...
Click to collapse
Mmm, probably guilty. You can always ask though.
I always say that I wouldn't cry if a truck ran over my Android.
That is, as long as at the time the device wasn't in my pocket.
Renate said:
You can always ask though.
Click to expand...
Click to collapse
That's not how it works... people just don't realize the potential of your programs that way..
Probably i'm not any better in that though.. lol.
CXZa said:
That's not how it works... people just don't realize the potential of your programs that way..
Click to expand...
Click to collapse
Yeah, I probably should add some examples to some things.
Edit: I added some examples and stuff. Happy(er)?
http://www.temblast.com/adbsync.htm
I was looking in the previous days to recover data from the phone and found a lot of programs, most of which require root for mobile and are not free, meaning that if I want to restore some files, I have to root and also format the phone!! And you all say that it is almost impossible to return files after formatting, so what do all these programs that require rooting the phone do?! I do not understand the usefulness of such programs