Hello everyone.
My good old Note7 N-930F threw a fit recently and rebooted to an FRP lock screen. :crying:
After a bit of panick I managed to restore it to original 6.0.1 firmware with original recovery, etc. Basically everything is stock with the exception of Knox (obviously).
I know how to root it (done it before) and only need it so that I can enable the SHealth (with buildProp edit). But then I'd like to un-root the phone since some of the apps won't work on a rooted device (GooglePay, some banking apps, etc.)
What do I need to do to remove root after editing the buildProp? Can the TWRP stay (and work) after the unroot?
Will the phone boot again or will I have to repeat the full wipe/recovery procedure?
Thanks in advance
Related
Hi,
This is a great site.
I am doing this cause I deleted some photos by accident and want to use one single program that needs the phone to be rooted. Because there is no mass storage connectivity you know how it goes.
I used Odin3 to install "CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5" to my Samsung Galaxy Note 2 with Android 4.3.
Odin says "PASS!". When I try to start the SuperSU (version 2.01, was installed by Odin and CANT BE UPDATED in the play store, not even removed only opened form play store. This was the most common fix that people are giving to this situation, but it does not work for me because there is no update possibility) Because KNOX says unauthorized attempt to access not accessible areas. SuperSU does not prompt the possibility to terminate KNOX like some people are advising to do, even tough the 2.01 version of SuperSU should be able to do this. Even the RootChecker says that my phone is not rooted.
So my assumption is that the Root has not worked on my phone even tough Odin says so. So I want to try some other approach to root this phone. I just would like to know should I do some check for what Odin HAS changed in my phone and to try to change them back so I can for example try Kingos root safely.
So the questions are:
Does some one have a possible fix to my problem without me having to re root?
How can and what should I check before trying another root?
If I have to go back with stuff that Odin did, without it doing the root properly how can I do that?
And one a bit different question:
If I factory reset my phone it will install the 4.1 I thin on it, has no KNOX, will it write that on the part that is empty and might include that data of my deleted pictures or does it write it on the area that has the previous data of the Android system?
Thanks for advance if there is any advises.
Partial answer:
I followed basicly this instruction,
http://forum.xda-developers.com/showthread.php?t=2538991
just needed to find the correct TWRP for my phone and used the older 1.65 SuperSU, there is something wrong with the 2.01 and it compatibility with my phone.
This video also helped cause the information was similar to the one in the link.
https://www.youtube.com/watch?v=ZQAkLgXjnCo
Installed the DiskDigger and got most of the photos, so now I need to find out how to convert it from root version to version so I can upgrade my phone.
Everything is really easy with Odin. If the packet that I installed with it first that does't istall the custom recovery system would have had some other KNOX combatible version of SuperSU I think it would have worked. No I just needed to use the KNOX remover to remove it from my phone.
Thanks for the form all the answers where her and it just took me some time.
Hey everyone,
I apologize in advance if this is breaking any forum rules or if it's a super noob question, but here goes.
I've got a stock AT&T V410 running Lollipop (had I known it would be such a hassle to root, I would've stayed on KitKat).
It's no longer under warranty so I'm thinking about rooting. Unfortunately, the only option that might work is KingRoot. Taking into consideration the possible "shadiness" of KingRoot, here is my idea:
1) Remove microSD and factory reset my V410. This is to have as little info on my V410 as possible before running KingRoot. If I can, I'll even skip adding my Google account.
2) Run KingRoot and see if the root is successful.
3) If successful, install Flashify and flash TWRP (which version should I flash?)
4) If not successful, do another factory reset and continue using my V410 like before.
5) After successfully flashing TWRP, I'll probably do another factory reset, if necessary, to have a clean OS without KingRoot.
6) With TWRP installed, I should be able to make a backup of my current V410 OS, right? I'd like to have this in case I try out CM and want to go back.
I think that's it. Assuming KingRoot can root my V410, does everything here seem viable? I know when I unlocked the bootloader on my OPO it basically did a factory reset anyway, but I want to be safe with KingRoot.
TL;DR
Will a factory reset remove KingRoot? Can I install TWRP and keep the original LG OS?
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
jason2678 said:
Won't work. The lollipop bootloader can't be unlocked, and I'm not aware of any exploits. TWRP won't boot. Stay on the lollipop bootloader and you're stuck with kingroot, stock rom, and stock recovery to the best of my knowledge.
I have heard of some methods to try to swap kingroot for supersu once you gain root, but I've also heard of that making a colossal mess with this tablet. Never dug into it, but I suspect supersu attempts to patch the boot image, messes up the signature, then the tab won't boot due to the locked bootloader.
The kitkat bootloader was locked too, but it was susceptible to the bump exploit that let us sign our own boot images.
If you're interested in TWRP and custom roms there is a route to downgrade back to the kitkat bootloader, but it sounds like a giant hassle.
Another random thought, there is a way to enable fastboot on this tablet (you would need root to do it). This method is for the LG G2, but it works fine on my V410. Maybe you could extract the partition images from the kdz in that thread linked above and flash them manually with fastboot instead of LG Flashtool, and get back to kitkat without making such a mess of the internal storage. Disclaimer: I haven't tried this and it could end poorly!!! :silly:
Click to expand...
Click to collapse
Thanks for the reply jason2678
Good to know that even if I could root my V410, I wouldn't be able to unlock the bootloader, which is my whole reason for rooting. And yeah, current methods to downgrade to KitKat seems like a real pain; for the time being it seems like I shouldn't mess with what works
Hello, fellow A720f owners. I messed up my Type-C port. While it can still definitely charge, still quite fast at that, the data transfer doesn't seem to work. So, no Odin for me.
Luckily, I've already rooted the phone and installed cmw as my custom recovery way before I messed the port up (submerged phone in a swimming pool for too long)
My phone went into a boot loop after I tried unrooting via SuperSu and rerooting via Kingroot (I was trying to see if I could really root my phone through Kingroot.) Because I saw that Kingroot was performing some shady actions (it installed itself as a system app for one), used root explorer to remove Kingroot from the systems folder.
I was planning on flashing a custom ROM via sd card, but I haven't seen any roms for the a7 2017 (6.0.1)
I failed to make a backup as well as I wasn't expecting things to go awry. (lesson learned)
So, I now have a question that you probably already know because of the title.
Inquiry: Is it possible to restore my phone using someone else's backup?
Request: If yes, is anyone of you willing to send me a backup so I can restore my phone? What other measures should I take to ensure that the procedure will succeed?
Some info I left out:
Model: SM-A720f (Open line, Philippines) [Surprise! I'm not Korean haha]
Build: A720FXXU1AQC5
Android Version: 6.0.1
Recovery: CWM
ROM: Stock
Thank you all in advance.
Hey Guys!
I just got an A5 (2017) that I'm trying to set it up with all the same apps as my old phone but I'm running into a couple problems. First of all I'm fairly new to Samsung; mostly used Motorola devices in the past but I did have an old SM-G386W that a relative let me use when my XT1032 was on the fritz. On that phone (which ran only 4.4.2) I was able to root with KingRoot and then use SuperSuMe to overwrite KingRoot. It worked great without tripping the Knox counter but after a lot of reading I see this method may not be possible on the newer A5.
I know I could most likely and very easily install root through Odin but since I just bought the phone (having got it as an upgrade through my carrier) I am reluctant to trip the Knox counter and void my warranty after only having it for 1 day. I believe the phone only has a 12 month warranty so I would at the very least like to keep my Knox at 0x0 until the warranty period expires.
Does anyone know of a way to root without tripping Knox or as an alternative; A way to restore app data without needing root privileges?
Thanks in advance for any help!
Well after posting I found Helium Backup & Restore which I just used and it appears to have restored everything properly. Now I just need a way to adblock.
.:Dark:. said:
Well after posting I found Helium Backup & Restore which I just used and it appears to have restored everything properly. Now I just need a way to adblock.
Click to expand...
Click to collapse
If your phone already rooted, you can try to use Moab that can be found in this forum, flash it using custom recovery and you are good to go
Sent from my SM-A520F using Tapatalk
Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!
I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.
Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!
Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.
So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .
Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .