Related
so this is my problem. Im having some issues with my phone and I want it to be changed. The issues really dont matter. In order for my provider to send me another phone they want me to do a master reset. This of course will delete all my apps and settings. As far as I know there is not a backup app that once you restore the phone and apps the restored phone will have all it's app data in place, the icons will be where you want them, etc, just like you would from when you clone or make an image from a Hard Drive from pc... Or is there and application that will do this? My only other option (i believe) is to root the phone to then use an app to do a real backup, then unroot the phone, root the new phone and do the restore. I also have to remove the root from the old phone but can that be done without increasing the counter? This is all a big hassle. I cant believe you can do a real backup/restore on a phone nowadays....
If there is any other way to do it I will appreciate the help. I will have to do this in the next days since my warranty expires in a bit over a month...
Thanks!
You are correct ....
Rooting of the device is needed, then the unroot.
It's the only method I'm aware of in getting a full nandroid backup ..g
Sarge has it right if you want to use backup apps.
If you don't want to root, you will need to flash TWRP or CWR to get the custom recovery and backup. Then make a backup to your external SD card. Use recovery to factory reset. Send the phone away after removing SD card and sim card. The backup is called a nandroid and it is basically an image of the phone.
On new phone flash same recovery then restore the backup. When you start the phone it will be as the broken one was.
You can remove the recovery from the broken phone, but I never heard of anyone getting problems from the warranty people for that.
Thanks both of you guys for the information. I am getting ready to do the root not only for the backup but there are quite a few apps that I want to use that require root that I am going to have to do it.
Now, I started reading tonight and the more I read the more I get confused. Is there an official guide to root the note (specifically AT&T running ICS 4.0.4 if there is a difference) in a way that I can unroot it in the future avoiding tripping any counters?
I have read so many different threads about rooting, they tend to be different so I am looking for the "current" accepted "method" to do this with decent steps if possible. Thanks much!
Whoa whoa, are we forgetting about ADB Backup?
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Fernandq said:
What do you mean CPA?
BTW, I want to root the stock att ics, I am not interested into flashing another rom.
Click to expand...
Click to collapse
Yeah I understand, you're wanting to do a full backup of your phone before you turn it in right? Or, at the very least, your apps and settings?
Welp, here you go: no root required.
A quick google search for "ADB backup" should get you the info you need as well.
Also looks like there's an XDA dev who came up with a much easier interface (as opposed to doing everything via command-line, which still isn't that difficult). Might be worth checking:
http://forum.xda-developers.com/showthread.php?p=36499906
Edit: Read your second post, and it looks like you're interested in rooting...I guess I was confused as to your intentions after reading you first post, which just sounded like you didn't want to lose your info after doing a factory reset. Regardless, it is HIGHLY advised before doing any sort of root-related activity to do an ADB backup. That way, if anything goes wrong in the rooting process itself, or if you later decide you want to go back to stock and/or all of your original apps and settings from before the root, you can literally be back with a clean slate within a matter of minutes.
Thanks very much for the link. I have swapped phones already but it will be helpful before I root. THANKS!
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Fernandq said:
after looking at adb I see it would not work for my initial needs as it only can be restored to the same device. I wanted something I could do a backup in the old one and restore that backup in the new one. Anyway, since I am past that anyway I am going to give it a try in theold device.... thanks!
Click to expand...
Click to collapse
The full backup, yes (regarding being able to only restore to the same device) but you could literally extract whatever data you want from the ADB backup using WinRar, then manually push it to your new device.
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Fernandq said:
Apparently ADB backup is broke, it does not respect the -noshared flag and the resulting file is corrupted requiring more processing on the file for it to work... dang it! Seems it has been fixed in JB...
http://code.google.com/p/android/issues/detail?id=28303
http://www.acertabletforum.com/foru...stem-backup-ics-only-root-not-required-2.html
and there is more if you search the net.... Now, why will they not fix it is beyond me. Ok, so the command does not respect -noshared, that is easy to fix, I can just pull my sd card out but making an otherwise broken and unusable file giving the user the false sense of security and not fixing the bug is plain wrong... The only option will be to upgrade to JB but the official upgrade is not out and knowing at&t I wont be for a bit... I am not much into flashing leaked rom although that might change in the near future...
Thanks.
Click to expand...
Click to collapse
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
CPA Poke said:
Well crap man, that sucks - sorry! I'm not gonna lie, I didn't read the link you posted as I'm pulling all nighters about 3 times a week during for the busy season of my profession (see my user name lol)...but you're saying that something actually went WRONG with the SDK on ICS firmware - and Google isn't fixing it?? That can't be right...right?
I can personally couch for this method, as I used it to make a full unrooted backup - of stock 4.0.4 ICS - back in October when I rooted my Note for the first time. And the first thing I did (per the rooting tutorial I was following) was verify the backup by doing a restore via ADB before I rooted - and everything worked fine. Like I said, sorry it's not working for you! Have you considered rooting, installing a custom recovery, doing a nandroid backup (and saving it someplace safe of course), then doing a full unroot back to stock + reset your flash counter? There are some great tutorials to walk you through all of that on the Galaxy Note Everything Thread in the General forum, in case that's an option.
Click to expand...
Click to collapse
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
gregsarg said:
As mentioned in my post....
Root, full backup, and unroot is the fastest method......g
Click to expand...
Click to collapse
But what's the point in putting things simply like that when I can write an entire paragraph saying the same thing, but more confusing??
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This Limited Warranty does not cover: ...
(g) defects or damage resulting from improper testing, operation, maintenance, installation, service, or adjustment not furnished or approved by SAMSUNG, including but not limited to installation of unauthorized software and unauthorized root access, both of which shall void this limited warranty
Click to expand...
Click to collapse
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
topherk said:
The sure-fire way of rooting is by using this method. That being said, this will trip your KNOX Counter.
Now, onto Voiding Warranty vs. Tripping KNOX Counter.
Official Samsung Warranty. This document is obviously written in a legalese manner. I am not a lawyer, but have read through the warranty very carefully and feel like I have a grasp on what it covers/doesn't cover.
In my opinion, the most critical part of the warranty (as it applies to our conversation) is the following:
This clearly states that rooting the phone will void your warranty. Please note that this is regardless of whether KNOX is tripped. Using Towelroot (on previous versions) to gain root access technically would void your warranty just as much as using other methods. The issue is whether Samsung knows about it. That's where KNOX comes in.
KNOX is primarily Samsungs way of knowing if you've modified the software on the phone (root access or some other tampering). At startup, KNOX checks for custom low-level operating system components (bootloader, recovery, kernal, etc.). If any of these are custom, it'll trip KNOX. TowelRoot had exploited a way to obtain root access without modifying any of those items, but as you mentioned, it no longer works in 4.4.4. As far as I'm aware, all other rooting methods include using ODIN to briefly modify one of the low-level operating system components, which invariably trips KNOX.
Now, back to the main point of your questions: will voiding the warranty (by obtaining root access) screw me over? The answer is: probably not. Samsung has been known to not really care about KNOX being tripped when servicing phones. This especially is true in cases where you are claiming someone not software related. From a common-sense perspective, having root access would in no way affect the performance of the power button, so if you're claiming issues with the power button, having a tripped KNOX shouldn't affect your claim status. Although, legally, they have covered this by saying the warranty is completely voided by having root access (not just the software part of the warranty).
I would recommend, however, that before sending any phone in, that you use ODIN to revert back to the stock android. KNOX will still be tripped, but it won't technically have root access anymore.
I hope this answers your questions.
-Topher
Click to expand...
Click to collapse
Thank you! It does, so essentially rooting period will void the warranty (as seen in the legal jargon) whether you trip the counter or not, and you can always restore it to stock if you need to turn it back in. I was wondering the same thing, we took my gf's S4 in yesterday, and all they did was run a Sprint diagnostic and then replace the hardware, not sure if they even checked to see what she was running (although it is stock).
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
TheNewGuy14 said:
Any other threads you recommend, I'm still fairly new to it, been reading up on it since I had the Transformer that wouldn't update to Froyo ha, but back then there was too much coding involved, I didn't want a bricked phone because I forgot a "/" in the code somewhere. Almost everyone I know uses Cyanogenmod, also what's the deal with Titanium Backup and Safestrap?
Click to expand...
Click to collapse
Thankfully, it's not nearly as easy to brick a Note 3 (at least compared to the S3... man it was tough helping people with that phone, so many bricks!).
It's considered bad form to link specific ROMs in a Q&A thread, since each ROM is catered to a different demographic (and some people might get in a huff if you neglect their favorite ROM). What I will do, however, is let you know the steps I've taken whenever I root and install a new ROM.
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Topherk,
Thanks for the reply, and sorry about the bad Juju for mentioning a specific ROM. In other news, I am probably going to re-read your article step by step, and it really puts things in perspective. I have that same build, and I also have Sprint like the video, which I didn't know that the carrier made such a big difference. I'm glad I asked before I started! I will keep you updated on what I decide to do, appreciate the help!
TheNewGuy14
:good:
*new question*
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
TheNewGuy14 said:
I don't remember where I read this, and I found the option on my phone. If I uninstall KNOX will that eliminate the counter, and other minor issues with KNOX?
Click to expand...
Click to collapse
No worries about the mention of CyanogenMod (I myself am running a ROM based off of it)... I was talking from the perspective of someone giving advice. If I give you advice towards a specific ROM or two (or even a list of ROMs), it could be considered a slight towards the excluded ones.
As far as I'm aware, there are two aspects of KNOX: The low-level trigger and the system app. The low-level trigger works like I described in my previous post. I honestly don't know how the system app works, but I believe it only affects Enterprise users whose corporations require secure phones (and have their own systems in place which interact with KNOX). I beleive it was Samsung's way of trying to secure some of Blackberry's business-class users. I may be way off on this, but that's what I understand about KNOX.
Cheers!
-Topher
I think you're right they want to maintain they are the most secure phone.
Check out their official statement for Towelroot, although I can't post the link because I'm still a n00b quick Google search will bring it up though.
Sent from my SM-N900P using XDA Free mobile app
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Yes, if you root 4.4.4 NH7 at this time with the available rooting formats, you will trip Samsung's KNOX Counter, and void the device's warranty with Samsung. So, are you going to send the device directly back to Samsung ? No, you are going to take it to a sprint service center, or ship it in to sprint. Sprint handles the warranty ? KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. Check this out http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
TheNewGuy14 said:
There's probably other threads on this somewhere, but how do you root a N3 with 4.4.4, from what I gather the newest updated fixed TowelRoot's crash exploit. Also can someone explain exactly the difference between voiding the warranty and the Knox Counter?
Thanks!
Click to expand...
Click to collapse
Hey OP, I have rooted my N3 using CF-Auto Root on NH7 without any problems.
It should be a walk in the park, and yes you will trip knox, but It's all good.
Now proceed with your rooting
Hello everyone,
Can someone please tell me how to undelete pictures on this device. Im sure I only chose to delete one camera folder but they all deleted!
I have not rooted my phone and prefer not to unless it can be done without adding to knox counter. I have also turned off data so that the chances of file overwriting from now is limited.
I have activated developer mode with USB debugging but the MTP or PTP options will not mount either internal or external memory to Windows or Mac for me to do try recover tools.
Please please can someone help. The pictures are very important to me.
search for Dumpster Image & Video Restore
Did not work
diego1810 said:
search for Dumpster Image & Video Restore
Click to expand...
Click to collapse
This only works if I had deleted the items after installation. Any other ideas?
Is there a way to root without knox or counter trip on 850F ?
Please help!:crying:
I Don't know about any such tools but if the pictures are really that important then do not worry about knox, this phone already has a low resale value so a tripped knox wont have an impact on anything but the warranty (if you still have it) whenever you plan to get rid of it just flash stock firmware and sell it. I have the at&t version which is (probably will always be) unrootable and i am looking to exchange it with a F model
dork997 said:
I Don't know about any such tools but if the pictures are really that important then do not worry about knox, this phone already has a low resale value so a tripped knox wont have an impact on anything but the warranty (if you still have it) whenever you plan to get rid of it just flash stock firmware and sell it. I have the at&t version which is (probably will always be) unrootable and i am looking to exchange it with a F model
Click to expand...
Click to collapse
Thanks, I was thinking the same ..I only worry that the phone doesn't develop a hardware fault because this phone is hard to take apart!
Ok so once I have rooted is there any better ROM than the stock which still gives clear call quality. I also want all the hardware features to work including finger print and airtouch; and also I like the power saving software and screen-mirroring to work. Is there a reliable better rom than stock for this?
if you do decide to root
DiskDigger Pro from the playstore works extremely well!! :good:
Wondershare
Alpha1BA said:
DiskDigger Pro from the playstore works extremely well!! :good:
Click to expand...
Click to collapse
Thanks for the tip. I just looked at Wondershare Recovery and it says their standard 1-click-root will not void the warranty since its a temporary superuser access. They claim this but would that not still trip the knox counter?
As some of you may have seen, I've found a root method that seems to work and be stable. I just unrooted, tried it again and failed once, tried it immediately after and it was successful. I think I may have found out the glitch why it's not working for some of you. During the root process, you absolutely can NOT let the screen go blank, timeout, or change. Mine has failed every time doing that, when I keep it on and uninterrupted, I've had success with it in about a minute.
Secondly, I know a lot of you want to make custom roms and complain about the bootloader being locked. That's true, but mine is unlocked, even though I did trip the Knox warranty counter. From the testing I've done so far, I've made a backup from the Online Nandroid backup app. I have learned that it is impossible to restart the phone in recovery in any way, shape or form without triggering the *Unauthorized software found, return to AT&T* error message. However, what I've been doing there to get my phone back is going into download mode, using Odin 3.07 and flashing the bootloader from the stock NE7 firmware. That can be found here: http://www.mediafire.com/download/9...711751_REV01_user_low_ship_MULTI_CERT.tar.md5 None of my stuff is lost, phone will reboot normally, everything looks good.
Now, as far as custom roms are concerned, since I have no idea about how to do that, I do have a custom recovery image saved through the other thing, but I don't know how to restore it through Odin. I do get kernel fail message if I try to enter recovery mode still, generally, all I have to do is power off and restart, it should work fine. If not, I load the bootloader image.
Having said that, it has me thinking. Since I'm basically using a custom rom already, I uninstalled the bundled bloatware and I *think* that's why I'm getting the error when I try, it may be possible to build around all of that and simply reflash the bootloader. I admit at this point, I'm in totally uncharted territory for myself and I'm not really even sure what trying to do a factory restore might do, but I do know I can recover using the stock firmware and then hopefully getting root access back to reload everything from Titanium Backup.
Until I get some sleep and enough nerve plus free time to try the factory restore to see if that is causing the issue, it's all theoretical. The point I'm getting at, and wanting to ask since I don't really know how it works, is if I can take the total stock rom as it is, root it without removing anything, and get it to boot into recovery from the phone or even through Odin, would that help the developers out there be able to come up with a workaround solution for this? I know I'm onto something, but I don't have the experience to proceed.
Since this phone has been dead and most of you have relegated it to a drawer or something, if you still have it, I'm guessing the Knox warranty 0x1 won't really mean a whole lot, so testing can be done. I'm trying my best with the total lack of knowledge I have and looking through different forums, but as I said, its beyond my experience level. I've cracked open the door folks, I can tell you absolutely, even if it does go into a bootloop or AT&T error, that bootloader will work without any loss except for the time it takes to get it done. I'm a bit brain fried right now, so if anyone has any suggestions, ideas, or whatever please comment. I believe this can be done, it was only a short time ago everyone said Root would never be on here, and now here it is. I also read in the Note 4 threads that once root access is gained, custom roms and things aren't going to be far behind.
Maybe there is a way to integrate that stock bootloader into a custom image without having to go around like I'm doing. I don't know programming very well. I'm sure that some of you folks with more experience and better minds than mine can come up with something based on my initial findings.
just used this on my i527 running i527UCUBNJ1.
ran root check and all good..tested romtool box,backed up some app s,all good..over clocked cpu no problem..awsome wrk.
now for kernels and roms..
Sent from my SAMSUNG-SGH-I527 using xda premium
Nice detailed post. Thank you.
I wish I had I527 to help out. (I have 527M and R960). I do care about Knox on my 527M but I don't care much about R960 as it's already Knoxed-out. So I might be able to help, but I ask all members who have I527 to chip in.
I have opened 527M and hardware-wise it's same as 527 (it even says 527 on my 527M board), so theoretically it should be same. But as I said in thee other thread, even KingRoot.apk fails to root it!!! ???
I didn't do anything to it. I unrooted last night and had it fail, but it worked again after.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
If anyone is interested, I successfully completed root process again with the kingo root app which allowed me to install and update SuperSU. Not sure if it will work for everyone, but it will work if you've already gained root access and want to change super user programs and had trouble previously.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
KingRoot not KingoRoot right?
Does anyone know how KingRoot achieves rooting? I want to know the actual mechanism of it.
Yes, kingroot. No idea how it works.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Good News and Bad News
I just tried to a factory reset without deleting my SDcard data. The bad news is, it went to the unauthorized error screen again. Good news is, the bootloader flash worked and I still haven't lost anything. Even if/when I unroot, it still says custom. Perhaps if I enable Knox before unrooting, I can restore the official version.
Wow, this phone is so stubborn! Goddamnit Samsung! What the hell...
idoit said:
Wow, this phone is so stubborn! Goddamnit Samsung! What the hell...
Click to expand...
Click to collapse
I'm thinking more AT&T than Samsung. There are so many of their apps embedded in the OS as well. Not sure which direction to take, I've frozen a few of them too.
You guys in the south should stop buying phones from AT&T. I'm sure you know they have been fined for millions of dollars to FCA for misleading advertisement (read = cheating).
Good News and Bad News
It is possible to go back to the stock image of NE7. I did it, I'm waiting on the update to NJ1 now. I was unable to do a straight factory reset from the phone, I got the same error, I even tried it again through Odin and it left everything as I had it. I unrooted, did everything I could then used all the firmware from the stock image to reload. I haven't been able to test the backups I made, they keep crashing in Odin. When I get updated and hopefully regain root access, I'll try to use the images I made to restore. If not, I still have everything backed up from Titanium. I don't know if this will work yet. I also don't know why Knox has been tripped on others devices. I didn't have a problem with restarting or anything until I tried a custom recovery. I guess that's just the nature of the beast. I'm planning on trying to make a totally stock image with root backup once I get this finished, if possible.
NE7 is Android 4.4.2 and NJ1 is ???
It's the latest update of 4.4.2.
Any progress in getting a working recovery for this monster?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
does anyone know about or have a working recovery?
I've asked....no response yet.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
txnolesfan93 said:
I've asked....no response yet.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
no working recovery as of yet
Sent from my SAMSUNG-SGH-I527 using XDA Forums Pro.
Has anyone tried exposed?
Sent from my SAMSUNG-SGH-I527 using Tapatalk
Same result. So far. I'm using exposed now and get some random app errors. I think it's from lucky patcher though.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I'll preface this by saying I have ZERO technical background. I'm here looking for help. My S9 Plus was factory reset recently, and I lost all of my data. The phone was not backed up to any clouds. All the recovery programs that I found online say the*phone*has to be rooted to recover the*data, but I do NOT have the skills to*root*it. I had read that my version of the S9+ was not rootable, but then saw Dr. Ketan's post on rooting at https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974 However, he states that the rooting process "...will erase all data including Int SD storage from device," which sounds like a Catch-22 (wiping the data that I'm trying to recover). So first question, is there a way to recover the data? Second question, is there someone trustworthy here who can help me recover it, either remotely or in person? I'm in southern California. Thanks guys.
prometheusrising said:
I'll preface this by saying I have ZERO technical background. I'm here looking for help. My S9 Plus was factory reset recently, and I lost all of my data. The phone was not backed up to any clouds. All the recovery programs that I found online say the*phone*has to be rooted to recover the*data, but I do NOT have the skills to*root*it. I had read that my version of the S9+ was not rootable, but then saw Dr. Ketan's post on rooting at https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974 However, he states that the rooting process "...will erase all data including Int SD storage from device," which sounds like a Catch-22 (wiping the data that I'm trying to recover). So first question, is there a way to recover the data? Second question, is there someone trustworthy here who can help me recover it, either remotely or in person? I'm in southern California. Thanks guys.
Click to expand...
Click to collapse
Currently, the Snapdragon (US) variant of the S9+ is not rootable. If happen to backup with Smart Switch, that might be your best option.
Cyclone Emperor said:
Currently, the Snapdragon (US) variant of the S9+ is not rootable. If happen to backup with Smart Switch, that might be your best option.
Click to expand...
Click to collapse
Thanks Cyclone, mine is the SM-G965U. I thought @dr.ketan had solved the rooting problem for this model, but maybe I was mistaken. If that's the case I guess the only thing I can do is wait until someone comes up with a rooting solution. I stopped using the phone right away so I don't overwrite the old data (assuming it's still in the phone somewhere).
prometheusrising said:
Thanks Cyclone, mine is the SM-G965U. I thought @dr.ketan had solved the rooting problem for this model, but maybe I was mistaken. If that's the case I guess the only thing I can do is wait until someone comes up with a rooting solution. I stopped using the phone right away so I don't overwrite the old data (assuming it's still in the phone somewhere).
Click to expand...
Click to collapse
If I remember correctly, a possible root method has been discovered for the Note 9.
As for old data still being there, I'd say it's unlikely but I can't be 100% sure.