• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root lost root access to my Galaxy S3 i9305.

Blu8 said:
No no, custom recoveries don't need root to do a proper factory reset. Or I'm pretty sure they don't. It also wouldn't lock your device (brick?). I made a nandroid backup using a custom recovery before I was rooted, nothing went wrong. I would expect a factory reset should be fine as well
Click to expand...
So the question is, is CWM working properly.

If it is, not such a big problem (check xda, I saw a thread for this phone there about backing up the IMEI and NV stuff).

But if CWM is not working properly, and you start the rom install with a full wipe, you've got nothing.

If you start with a factory data reset, you'll only wipe /data and /cache, not /system.

/data you don't care about if back up everything with Titanium Backup.

/system you do care about - you want to wipe that before installing a rom (roms contain at most /system and the boot image). Otherwise, you're going to have an unhealthy combination of old and new in /system.

And if CWM is broken, then you'll have a phone with no operating system.

I get it.

And if this were an HTC, I could get you around that in a snap. But it ain't so I can't. :(
 
If you had access to a windows pc we could get you fixed in no time. Just flash firmware, flash cwm and then the supersu.zip.
 
mikebellamy2k said:
Would a factory rest not relock my phone sim to t mobile then?
Click to expand...
Nope.

A proper sim unlock affects a deeper part of the NV storage - once unlocked, a factory data reset can't touch it.

The factory data reset doesn't restore original firmware or conditions.

It simply erases the /data and /cache areas - where your apps, all app updates and all app private data are, along with any shadows in cache.

The name assumes that nothing was done besides manufacturer updates, so just erasing those two areas would equal the factory condition of whatever the last Samsung update was that you got.

Factory data reset doesn't erase root or fix the /system either - that's out of scope for the assumption that only the manufacturer and carrier has /system access.

As I mentioned earlier, if anything, I'd be paying attention to an NV/IMEI backup, so here's that info -

http://forum.xda-developers.com/gal...warning-guide-backup-restore-imei-nv-t1946915

But - that seems to require a pc, so... :(
 
If you are refering to the open padlock in the upper left of phone I would say no. Factory reset should not and didnot change unlocked status of last S3 I worked on and was ATT phone on Straight Talk
 
Wow it's all sounding too much of a nightmare now. Probably wouldn't have been if I'd rooted with a PC and custom rom from the start but probably learnt some in not doing so. I have looked into using a windows emulator and might do with Odin if I get it working. Probably best to wait till I get my new s5 in the autumn tho. Thanks for all the help and support. I couldn't have not not done it without you's!
 
I would advise against using wine or another windows emulator, people usually get driver issues when trying to use odin like that. Up to you though. Good luck with your device [emoji106]
 
Would aroma file manager allow you access to the system/xbin file to clean up all kingusers files since kinguser write protects the xbin folder. Im curious to see if accessing it through recovery would fix it. Not sure what all files it installs.
 
Screenshot_2015-08-10-02-36-28.png
Screenshot_2015-08-10-02-36-28.png
Screenshot_2015-08-10-02-35-52.png
hackingsomething said:
Would aroma file manager allow you access to the system/xbin file to clean up all kingusers files since kinguser write protects the xbin folder. Im curious to see if accessing it through recovery would fix it. Not sure what all files it installs.
Click to expand...

I've tried to delete the Su and kinguser bin files and apk but they just come straight back. Kinguser has locked permissions on it's as well.
 
mikebellamy2k said:
I've tried to delete the Su and kinguser bin files and apk but they just come straight back. Kinguser has locked permissions on it's as well.
Click to expand...

Wow, damn didnt know a root app could be so bad. Need a security specialist or advanced technology support member to come up with a removal method for everyone. Im sure your not the only person who has this problem.
 
Kingroot team modified their stuff a few months ago. Posted a link earlier to a statement they made on XDA . They not happy with Chainfire and SUme .
 
By what flashing the stock rom and resetting the system that doesn't really help the thousands of users who have this problem and no stock firmware to flash.
 
Well that's not Google's problem, at all. There's a reason rooting breaks your warranty, and if anything Samsung would be the ones you hit up. If you install malware on your computer you don't go to Microsoft and say okay you fix this. That's not how it works.
 
You must log in or register to reply here.
Back
Top Bottom