Can ClockWorkMod be uninstalled? - Galaxy Ace S5830 General

I'm looking for a solution for rooting my GT-S5830L in another thread. But while I'm waiting on that, maybe someone could confirm this for me.
I've read that ClockWorkMod can be uninstalled, at least in Froyo, by doing the following:
Deleting: /system/bin/hijack and /system/bin/logwrapper
Then renaming: /system/bin/logwrapper.bin to /system/bin/logwrapper (<- No . at the end)
I've read that in several places, but haven't confirmed that it also applies to Gingerbread. I have 2.3.4.
Thanks folks.

http://forum.xda-developers.com/showthread.php?t=1437426

Well mine is S5830LUBKP7 GB 2.3.4.. and I've already lined up a procedure to flash a ROM of that I got from sammobile with Odin if needs be.
Are you suggesting that ClockWorkMod can't in fact be completely uninstalled without flashing a stock build?

must reflash with Odin
Sent from my GT-S5830 using XDA

2nd opinion suggesting just deleting and renaming files doesn't do the job. Hummm...

Any more votes?

there's a flashable stock recovery floating around somewhere in the forum, use the search, might work alright. Other than that, Odin.
It seems you're probably worried about warranty. If you ever need warranty for some reason reflash the stock rom from Odin and that's it, gone CWM, gone root, gone any reason to own an open source OS smartphone.
Otherwise, it's really not recomended to be flashing custom or stock modified roms without having the option to backup and restore your phone's system, which in my opinion is the most important asset of CWM.
Don't worry, you can always go back to stock with Odin. But once you root and start flashing, you WON'T GO BACK; there's really no other way to go beyond the factory issued limitations of the ACE.

try Odin

dxppxd said:
It seems you're probably worried about warranty. If you ever need warranty for some reason reflash the stock rom from Odin and that's it, gone CWM, gone root, gone any reason to own an open source OS smartphone.
Click to expand...
Click to collapse
I did check the ROM build on my Ace and found the factory backup on samfirmware. I read up on Odin at the same time, so I'm feeling better about going that route if needs be. I was just wondering if there might have been a quicker and less radical way to uninstall CWM and unroot... and still have have the phone at 99% of what it was rather than start from scratch.
Guess the only reason I'd go back would be to send it in for some reason under warranty. But who knows, at that point there's the chance it might be beyond flashing to factory.
Thanks for confirming that CWM and rooting will be gone if I ever flash back to factory. It's been a crash course in the past few days, going from knowing zip about all this to just staring to get a handle on it all.

Related

[Q] A new SGS2 user wanting to use a custom ROM

So hi all, I got my SGS2 about 2 weeks ago and so far am really liking it. I, however, am intrigued about the features that a custom ROM could provide.
Currently I'm looking at Cognition S2. I've read the installation instructions and browsed around the forums reading about this stuff. There are, however, a couple of questions that have risen.
1) Do I need to root my phone before being able to flash Cognition S2? If so, is the best way to do this by getting CF-Root?
2) If I flash said ROM, will I lose all applications and data? If so, is there a way to back them up first? I've read about people recommending Titanium Backup, but even that requires the phone to be rooted so this seems like an egg and a chicken -type of thing to me.
3) If I flash a custom ROM, is there a way to reset the phone back to it's "original" state so that, in case it dies during the warranty, Samsung won't just tell me to get lost because I've flashed it myself?
Basically I'd like to flash, but not if I jeopardize such an expensive toy.
zelectral said:
So hi all, I got my SGS2 about 2 weeks ago and so far am really liking it. I, however, am intrigued about the features that a custom ROM could provide.
Currently I'm looking at Cognition S2. I've read the installation instructions and browsed around the forums reading about this stuff. There are, however, a couple of questions that have risen.
1) Do I need to root my phone before being able to flash Cognition S2? If so, is the best way to do this by getting CF-Root?
2) If I flash said ROM, will I lose all applications and data? If so, is there a way to back them up first? I've read about people recommending Titanium Backup, but even that requires the phone to be rooted so this seems like an egg and a chicken -type of thing to me.
3) If I flash a custom ROM, is there a way to reset the phone back to it's "original" state so that, in case it dies during the warranty, Samsung won't just tell me to get lost because I've flashed it myself?
Basically I'd like to flash, but not if I jeopardize such an expensive toy.
Click to expand...
Click to collapse
1. Yes.
2. Yes but once you have root, install Titanium, do a back up and then flash Cognition rom.
3. Yes provided you find the correct version of your carrier's software. But beware : if you don't read carefully and screw your phone up with a bad flash, you might not be able to do it yourself.
Read more and then follow instructions exactly.
zelectral said:
1) Do I need to root my phone before being able to flash Cognition S2? If so, is the best way to do this by getting CF-Root?
Click to expand...
Click to collapse
Yes, your phone must be rooted before flashing (most ROMs). Simply flash CF-Root kernel via ODIN and you are done. Really easy.
zelectral said:
2) If I flash said ROM, will I lose all applications and data? If so, is there a way to back them up first?
Click to expand...
Click to collapse
Most likely all your apps and settings would remain, BUT. I would highly recommend to boot into CWM recovery (you'll get it by flashing CF-Root kernel), do full wipe and only then flash new ROM.
To backup your apps use AppAdmin/AntTek app Admin/Titanium Backup or some similar app. Titanium Backup has an option to backup app settings/data. Personaly i would NOT use it, but that's another story.
zelectral said:
I've read about people recommending Titanium Backup, but even that requires the phone to be rooted so this seems like an egg and a chicken -type of thing to me.
Click to expand...
Click to collapse
1. Flash CF-Root kernel.
2. Backup your apps/contacts/text messages and so on.
3. Boot into CWM recovery and backup your current ROM.
4. Wipe.
5. Flash new ROM
zelectral said:
3) If I flash a custom ROM, is there a way to reset the phone back to it's "original" state so that, in case it dies during the warranty, Samsung won't just tell me to get lost because I've flashed it myself?
Click to expand...
Click to collapse
And yes and no. you can restore phone firmware (if you made a backup on step3), you can flash back stock kernel, but SGS2 have two(?) hidden counters that shows how many times you have flashed custom kernels. If counter shows something else then 0 - your warranty is lost. At least it should be like that but friend of mine got repaired his SGS2 with no problems while his counter was showing "3". Perhaps it depends on person who work at repair center.

CAN I Recover to stock WITHOUT USB ACCESS

So Im probably ging o get flamed for this......but here goes.
I have searched and searched, ive put bits and pieces together, but still missing components,
So for some reason MY phone is not recognized on ANY PC, My phone with charge, but not recognizable. Yes I installed samsung drivers, fooled with phon usb settings, tied rebooting phone, removing battery, flashing other roms, no luck.
Currently Running the most recent version of the following ROM
http://forum.xda-developers.com/showthread.php?t=1676086
So to send my phone back to samsung(got them to agree to give me a free Galaxy S3), I need to do a full restore, however, I cannot find a way to flash to stock without Odin.
I have this theory, I want feed back to see if its possible.
1. Flash a stock ICS 4.0.3 ROM Back onto my phone via CWM\TWRP
2. Flash stock kernel
3. Reset flash counter
4. Push stock recovery though Terminal Emulator (heard this was possible but no experience)
5. Of course a full factory wipe\format.
Please if you think this can work and can help in any way please do.
The galaxy note everything thread has two methods too return to full stock ..
It is stickied at the top of the general section ....g
gregsarg said:
The galaxy note everything thread has two methods too return to full stock ..
It is stickied at the top of the general section ....g
Click to expand...
Click to collapse
If this is the link you are refering to, then please specifically point out the full sock recovery without using ODIN viaUSB cable.
http://forum.xda-developers.com/showthread.php?t=1586223
If you have CWM you can flash a stock gb or ics rom and modem easily enough. That gets you 75% of your goal. I think you can flash 3e recovery too with CWM.
To unroot maybe flash an unrooted rom like the original ULF6 as your first step.
For warranty return several have mentioned they didn't unroot and were able to send in phone and didn't get any charges.
P.S. this topic was covered in a thread about two weeks ago. Perhaps a google search will locate it for you to get all the links and details.
I sent in a rooted note directly to samsung and they didnt charge me for it. All i did was factory data reset and flash the stock rom. Oh yeah and i reset my flash counter
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The answer is no ...
You cannot fully recover to stock , unless you can find a factory GB or ICS rom, in a flashable form ..
But....for warranty purposes you don't need to ...
Just download a stock rooted rom to the device ...along with the flashable stock recovery and counter reset file.
It isn't perfect ...but close enough.
And try a few different roms ...as they may fix your connection issues.
I'm thinking you have a USB driver issue ....g
I didn't think you could either but take a look here.
http://forum.xda-developers.com/showthread.php?t=1800231
They won't care. Its going into the pile to be reflashed, boxed and sold as a refurb. No sweat off their back.
.muimerp adx gnisu 717I-HGS-GNUSMAS ym morf sdrawkcab tneS
Thanks for the help all, I Think its possible, will post results.
If you flash a stock rom then flash a stock recovery then delete all your apps, the only way they would know is to install a root check app, and I just don't think they would. Also, your rom and root habits didn't break the usb hardware.

Reverting to Stock Issue Inquiry

Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.

[Q] tried to root i777, now stuck at galaxy s2 with triangle and i900 screen

Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.

[Q] Upgraded to 2.3.6 Tried to unroot Ran Odin SOC doesn't work

Okay, before any of the regular contributors here say something nasty to me for asking a question that's been asked and answered, I want you to know that I have spent 2 days reading through -all- xda forums that might even -remotely- relate to my problem, without finding any answers. I also spent several hours searching all the common Android forums elsewhere, as well as, silly sites like Yahoo answers, etc., but have not been able to find the answer to my question. I'm the first to admit that reading the exorbitant amount of information in here causes my brain to short circuit due to all the numbers, versions, etc. It's like reading tax code; use C1.4.6 unless you've submitted b45.1. In that case, use d16.9, unless you've also filed a p32 in the last 2 years...if so, then....blah blah blah.
I love all you cell phone OS gurus and am quite envious of your ability to effortlessly wade through the technology involved in these phones. I wish, wholeheartedly, that I didn't have to ask any questions here because I know how irritated many of you become over people like me asking stupid questions, but I have no where else to turn. Believe me, if I could go elsewhere, I would, for your sake.
I was running 2.3.4, rooted, stock ROM. Froze the system with TB Pro to prevent the upgrade to 2.3.6. Unfroze it. Upgraded. Decided to unroot so I could sell my phone in favor of another. Ran Odin. Ran SuperOneClick. Ahhh...and there's the problem. SOC doesn't work with 2.3.6. So now, I don't know what to do. My phone is half rooted. I can't unroot and I can't reroot. I get the triangle, but TB Pro doesn't work because I'm not rooted, well. sort of not rooted. I guess I'm a little rooted. I don't know what to do next mainly because, every time I find what I think is a solution, I find another source that says, "DON'T DO IT! YOU'LL BRICK YOUR PHONE!" So, here I am, hoping someone will point me in the right direction without chastising me for asking a stupid question. I checked the solution in here and it's great, except, and I quote "Not working for KK6 2.3.6"
Thanks for any help....
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
tunie said:
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
Click to expand...
Click to collapse
You can't have a "half rooted" phone, and it wouldn't matter at all anyway since you're going to be booting into download mode in order to flash to stock.
Sent from my Zanpakuto using Getsuga Tensho!
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
When I rooted so very long ago, I used SGH-I777_ClockworkMod-Recovery_5.0.2.3 that I downloaded with su-3.0-efgh-signed. At the time, I didn't understand what this was. I only understood that this would root my phone. I didn't want to flash any custom ROM's because, to this day, I really don't understand what a ROM is. Yes, I've read about it. Still don't get it. So, did I flash a custom ROM? As far as I knew, all I did was root so I could use TBPro to backup and freeze, and use LBE to keep my information as private as possible.
<edit> So I've just reread many of your posts. You really are great at explaining this stuff and I thank you for that. It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Thank you, again. I swear I'll be out of everyone's hair in here as soon as is humanly possible.
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Pirateghost said:
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
Click to expand...
Click to collapse
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
tunie said:
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
Click to expand...
Click to collapse
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
tunie said:
It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Click to expand...
Click to collapse
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Pirateghost said:
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you. I give up. Really, I do.
creepyncrawly said:
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Click to expand...
Click to collapse
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
tunie said:
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
Click to expand...
Click to collapse
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Pirateghost said:
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Click to expand...
Click to collapse
Just want to insure that I've relayed all the necessary information, correctly. I guess I have. Thank you and I'm sorry I took anyone's time.
tunie said:
Well thank you. I give up. Really, I do.
Click to expand...
Click to collapse
That dreaded yellow triangle show up when you flash a custom (non-stock) kernel. When you flash a stock kernel, it will go away. So... if you flash back to stock like I suggested, it will go away.
Pm me if you need more assistance
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Thank you. It worked like a charm. Back to stock. Wonderful. Thank you so much. It wasn't as much a nail-biter as I thought it would be.

Categories

Resources