When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Boxa786 said:
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Click to expand...
Click to collapse
You in the right thread?
Sent from my SPH-L710 using xda premium
Related
Hello everyone, first off, I read these two posts in their entirety:
http://forum.xda-developers.com/showthread.php?t=1009969
and
http://forum.xda-developers.com/announcement.php?f=943
I apologize if this might not be the best forum to post in, but as I just signed up I didn't have enough posts to post in the first thread like other people.
So I kinda have a good understanding of what I need to do with my phone, but need someone to recommend the best thing for me to do to change my firmware to 6.05.6 or 6.05.9, so allow me to share my rooting experience:
First off, I am running Windows 7 64-bit and I have never rooted a phone before and my Thunderbolt was my first droid device that I got 5 days ago on April 2nd, but I have plenty experience with flashing firmware for other devices such as routers, DVD drives etc. Initially I was not going to bother rooting my phone because of how complicated it looked, but then I found the one-click method and was becoming increasingly annoyed by not being able to get rid of the bloatware such as the Blockbuster app, Bitbop, Lets Golf 2, Rockband, Peep, and a couple others, so I decided to give the one-click method a shot.
Initially I had an issue with the ADB driver as Windows failed to install it successfully, after many agonizing minutes and a couple forums later, I installed HTC Sync and that fixed the issue, so now my batch file was working thus far. My second problem was the hbooteng.nb0 file. I had extracted the files from the exploits.zip correctly to the platform-tools folder, but my mistake was that instead of using the RUU filed and renaming it for the first flash, I initially flashed it with the one that was already name PG05IMG, so basically I thought I had done it correctly until I ran into the hbooteng.nb0 issue and realized I had flashed with the wrong file, leaving my phone basically unchanged and unrooted, but working perfectly fine.
Sooo I started over, this time knowing for sure I was using the correct files, and the process went pretty smoothly and the oneclick method told me my phone was rooted and to install the SU and ROM Manager so I did. Also did the clockworkmod thing as well.
But here is where my current problem is: My firmware is the 605.10 version and I would like it to either be back at the stock 605.6 or the newer 605.9. My phone works modestly well with the 605.10 so far EXCEPT it isn't correctly detecting my location. I live in Indiana, but the clock keeps setting itself to Rio de Janeiro. Also if I try to use Google Earth and do "find my location" with the GPS enabled, it takes me to Rio de Janeiro!
So here is my question: Which method of getting to the 605.6 or 605.9 firmware is the safest for me to use? And will using the one-click batch file to flash to either of those firmwares be safe since in the beginning it says that method does not work unless it is already at 605.6 or 605.9? Or should I attempt to do the option of factory resetting my phone through the SDcard settings, and what will I lose, and will I be back at 605.6, OR am I somehow supposed to use the ROM Manager app to flash to 605.6 or 605.9?
Many thanks in advance!
Ok so I ended up using ROM Manager and flashed to the 1.12.605.06 and it worked successfully but now my phone is no longer rooted since the ShootMe app doesn't work.
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
First of all, yes, I am an idiot, and yes, I have looked through the forums but just have to make sure I am downloading the correct thing.
So, a while ago, I rooted my t-mobile galaxy s3.
Today, I wanted to download a root-compatible app, it didn't work, turns out that my root somehow became disabled ( I might have accidentally wiped the superuser binaries)
So, I try to re-root my phone...several times. I finally think I have it rooted (using the official xda guide on how to root), and everything was fine, until i try to use superuser and it turns out that I am not rooted...for whatever reason. I do a hard reset a couple of times, it still shows that I am running alternate software and cannot update. I try to flash a stock rom to my phone, and that just simply fails on odin.
Now, I have completely formatted the SD and internal storage (probably very stupid), and I am just wondering how I could possibly flash a stock rom onto my phone, and if you could please link one because I believe the one I tried was not for my device.
If not, please provide some suggestions on what I should do. My device works, so it's not really time-sensitive, but I do want to re-root my android after I revert to stock roms, properly this time.
Thank you for your time and help!
Fixed
Fixed the problem, will be posting tutorial in the morning for anyone who might have the same issues!
Waiting for u!!
Hello all, my First post so please bear with me, Been using these forums for quite a while and all answers have been allready given, so no need to post... till now.
I have a Samsung Galaxy s3 i747 running android 4.1.2 OTA update and used CF-Autoroot. No problems there,
installed Rom manager, and cwm recovery touch. no problem
When I restart in recovery mode, also everything seems fine...
When I try to backup the phone however using cwm recovery it starts backing up everything including system but the just as it starts data the phone restarts.
Tried reinstalling cwm over and over different versions.. nada same result..
went into the settings to mount the various options as suggested to another user. same problem nada...
To be completely clear, I am trying to make a backup of my stock / rooted only Galaxy s3 i747 onto it's own storage NOT SDcard.
as I also could not figure that out either.
Any help would be greatly appreciated. -Erdericks1976
Sorry about misleading Subject. This is about making my first backup successfully..
Followup.
Well seems there are/were more problems here than I thought, it has begun randomly? restarting,..
Well. not Ramdomly. Whem specific apps are run it would restart.
I did a titanium backup and it would backup alot of the apps. but them would restart the phone when it got to 1 specific app.
I think I figured out what I did wrong here.
I have a Galaxy Note 2, and I may have flashed something from it by mistake......
so I have restarted my Gs3 From scratch Re-Following all instructions.. waiting to test and see if CWM works to back it up now..
It sure was faster with the Note2 rooted Kernel though. (if that was in fact what happend)
I'll update soon as its done..
Followup 2
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Erdericks1976 said:
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Click to expand...
Click to collapse
good for you, yu got it solved fast and easier than expected, XDA is your place for Android and root but also every kind of OS there is
anywz am not that old in XDA i joined in April and officially started rooting and modifying my phone since May and it has been great, bricked my phone 1st time but all in all i got the S3 in case for the loss. yu'll get used to this place and ROOT/custom roms
I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik
metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.
I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.