Hi,
Title says it all.
But basically, I'm selling this tablet to a friend, and he's worried about the fact that I rooted it once upon a time.
I have used WugFresh's toolkit to restore back to stock (4.2.2) and have also locked the bootloader (no unlock icon during boot splashscreen).
Is this enough to 'restore' warranty, or is there a root counter (akin to Samsung Galaxys phones) that Google can check?
Thanks for any replies in advance.
01alim said:
Hi,
Title says it all.
But basically, I'm selling this tablet to a friend, and he's worried about the fact that I rooted it once upon a time.
I have used WugFresh's toolkit to restore back to stock (4.2.2) and have also locked the bootloader (no unlock icon during boot splashscreen).
Is this enough to 'restore' warranty, or is there a root counter (akin to Samsung Galaxys phones) that Google can check?
Thanks for any replies in advance.
Click to expand...
Click to collapse
You would be fine w/ warranty.
Related
I had to submit an RMA to get a new device and return this one. I haven't unlocked/rooted yet, and don't want to return it with an unlocked bootloader.
Will I be able to "fastboot oem unlock" then get Root on the device (WITHOUT CWM), backup with Titanium, then "fastboot oem lock"
Can I get root on the device without putting CWM on there?
Unlocking the bootloader wipes the data partition, including the virtual SD
And AFAIK, there's no way to root without unlocking the bootloader for the N4
Your best bet would be ADB backup I think
http://www.thesuperusersguide.com/adb-backup--restore.html
Ah, ADB Backup - that's a new one to me. Thank you!
Given his original question, will relocking leave any traces? I.E. can it go back for warranty if it's been previously unlocked?
Fmstrat said:
Given his original question, will relocking leave any traces? I.E. can it go back for warranty if it's been previously unlocked?
Click to expand...
Click to collapse
Even if it did leave any traces, I doubt you would ever have an issue from it. I've warranty returned a few rooted/unlocked phones including a Galaxy Nexus and a Nexus One and never had an issue with the warranty. Hell, I even sent one Nexus One back to Google still fully rooted and unlocked and never heard anything.
adb backup works well for me. I don't even need root anymore actually! When I upgraded from my stock gnex, I just backed up the few apps that I wanted to preserve data and restored it directly to the N4.
Through the many android devices I've owned, I've gone from flashing roms/modems every other day to leaving the device absolutely stock! With that thought, why am I still on XDA?
My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?
scmagee said:
My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?
Click to expand...
Click to collapse
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.
reset system status on AT&T GS4
Plexicle said:
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.
Click to expand...
Click to collapse
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.
scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
Using the search function and doing some reading would have revealed that this subject is being or has been discussed in several places in the AT&T S4 forum already. I mention this in case you are interested in reading about what has already been discussed about the issue. However, this thread goes a lot more in depth about the issue...
http://forum.xda-developers.com/showthread.php?t=2303022
It is just a beginning but if you have any knowledge to contribute to that thread or if you know anyone that can help it would help greatly.
In short, an APK named Sysscope scans the phone at bootup. There are a few other processes that support sysscope as well. Sysscope uses several methods of checking the phone to see if certain parameters have been changed, deleted, or modified. If it shows that they have, the next boot will show "custom" status and the unlock icon. It appears that a method was found to keep the Verizon S3 Official, but the method needs to be figured out and implemented on the AT&T S4. That is beyond my capabilities. The thread I posted and the threads linked in that post describe this all more in detail.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
Plexicle said:
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.
Click to expand...
Click to collapse
The bootloader remains locked (unfortunately). Dan's exploit sidesteps the bootloader to allow for custom recoveries and kernels but the bootloader itself remains locked. The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.
scott14719 said:
The bootloader remains locked (unfortunately). The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.
Click to expand...
Click to collapse
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.
Plexicle said:
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.
Click to expand...
Click to collapse
Thank you.
The custom status seems to be a scan at the moment. If you Odin back to stock firmware and start from scratch, you will be back to Official status. AOKP doesn't run this check so as long as you Official you can flash AOSP and AOKP freely I'm pretty sure and be safe from the ugly custom status.
Try this:
http://forum.xda-developers.com/showthread.php?p=41955085#post41955085
My Galaxy S4 stopped working and I'm planning to send it back to get a replacement. However, I rooted my phone before this happened and I'm planning to un-root it before sending it back. I was planning on using the Triangle Away app as well to reset the flash counter but apparently I need to unlock the bootloader first. I read in this thread that you can flash a recovery and root the phone at the same time.
Would using that tool help me in unlocking the bootloader so that I can use the Triangle Away app to reset the counter and un-root my phone using Odin afterwards? The topic creator mentioned that TWRP will auto-lok anything you flash and works as a bootloader unlock but can anyone confirm this? I bricked my Galaxy S3 two weeks ago and don't want to face the same problems with this newly aquired Galaxy S4.
Is it worth it to go through all the trouble to just reset the flash counter or would un-rooting the phone be enough to send the phone back for a replacement?
http://forum.xda-developers.com/showpost.php?p=42320414&postcount=2
Thanks, that guide looks really helpful. I do have one question though, it seems the Triangle Away app needs the boot loader unlocked in order to run successfully on the AT&T Galaxy S4 so what would be a good and simple way to unlock the bootloader and is there a way to check whether or not mine is unlocked? Would running the CASUAL tool take care of this (even if my device is already rooted)?
What guide/method did you use to root? Did you not use the bootloader exploit at that time?
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Un-Rooting
Zernell said:
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Click to expand...
Click to collapse
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
pharrisworth said:
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
Click to expand...
Click to collapse
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Un-Rooting
Zernell said:
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Click to expand...
Click to collapse
Well if all you did was ROOT the flash counter shouldn't be affected. Iused the same tool. I took the additional step of replacing Superuser with SU user. to rid myself of the "custom" unlocked symbolon boot up. However, the phone was NEVER really unlocked.
Thanks for the replies! I managed to un-root the phone by just flashing the AT&T stock firmware using Odin. Hopefully the binary counter won't be an issue.
Hey XDA-folks!
I will most likely be sending my Nexus 4 device in for replenishment/repair service.
I know that I lost the warranty by flashing my device & rooting it.
Is there a way to completely restore the phone to the factory state?
Do I just need to flash back to stock, unroot and lock bootloader? That would be it?
Thanks for your help! :highfive:
chrisyouu said:
Hey XDA-folks!
I will most likely be sending my Nexus 4 device in for replenishment/repair service.
I know that I lost the warranty by flashing my device & rooting it.
Is there a way to completely restore the phone to the factory state?
Do I just need to flash back to stock, unroot and lock bootloader? That would be it?
Thanks for your help! :highfive:
Click to expand...
Click to collapse
Tutorials for this is all over the forum and google but its simple just flash factory images and send it in. Or your method will work
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
McXred said:
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
Click to expand...
Click to collapse
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Lawlrus said:
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Click to expand...
Click to collapse
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
McXred said:
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
Click to expand...
Click to collapse
Right, it shows that message when the BL is unlocked, once you relock your BL that *should* go away, never tried it because I don't plan on even being back on stock with no root.
If you do any modifications to the device even root, or using a stock custom ROM like we have, it is suggested to NOT relock your BL, while on it. Keep that in mind.
You want to go back to full stock to lock it, then reflash the factory image