I'm needing to know how to get rid of clockwork mod. If theres a one click, it would be the best for me? I rooted my samsung epic but I'm now wanting to do the 2.2 update, so I unrooted it, all with one click methods. I'm thinking the clockwork is holding me back. When I go to apply the update and start the phone, its obviously in clockwork mode. It gives me an error and aborts. The OTA didn't work either so I'm trying the manual method. Thanks much
Ok, so I've tracked down the cause but still help. When I did the one click root it deleted asphalt 5. So now when I try to do the 2.2 update it comes up with an error saying something about the stupid asphalt 5. Is there a way around this or can someone please help me get my phone back to just the way it was before the root?
I guess I just need a link to get back to 100% stock. Every single one I find is a dead end/deleted file..
Never mind, I flashed it with odin and all is well now.
my phone is rooted but I tried to put a another rom on my phone to replace one I already had because I was having problems with it but my clockwork is not working so I want to unroot my phone and reroot it or is it an easier way?
Which CWM are you installing, and what approach do you use to access it?
Greetings,
I'm trying to root a U Prepaid Samsung Repp (SCH-R680). This phone is reportedly a rebadged Samsung GIO sold to US Cellular.
The unit is running Android 2.3.5 and kernel 2.65.37
Z4root, SoC, and gingerbreak all fail.
And If i try using the updater with a Samsung GIO update file it fails at signature verification.
I attempted to update the zip file for the universal Gingerbread root ( by stoneboy tony) by adding SCH-R680 in the assertions:
Code:
getprop("ro.product.device") == "SCH-R680" ||
getprop("ro.build.product") == "SCH-R680" ||
but am still experiencing signature verification issues. I attempted to self sign using the signing.zip utility found here on XDA but apparently that is not sufficient when using the android update <3e> utility on the phone.
I'm fairly computer literate and have access to both windows and Linux machines so any tips on what to try next are appreciated. This has become an obsession and I "must" root this phone
You could try this: http://forum.xda-developers.com/showthread.php?t=1321582.
I'll take a look at it. I think that SoC uses the same zerg rush script but it is definitely worth a try.
Do you have any idea why I get the signature verification problems and how to work around that? It seems odd to me that a rooting method would only work on rooted devices
oldsoldier2003 said:
I'll take a look at it. I think that SoC uses the same zerg rush script but it is definitely worth a try.
DO you have any idea why I get the signature verification problems and how to work around that? It seems odd to me that a rooting method would only work on rooted devices
Click to expand...
Click to collapse
It's your bootloader/recovery (being stock/locked) which may be causing that problem (not the fact that you don't have root). The only way around that would be to use a custom recovery to flash the file (with signature verification turned off).
Theonew said:
It's your bootloader/recovery (being stock/locked) which may be causing that problem (not the fact that you don't have root). The only way around that would be to use a custom recovery to flash the file (with signature verification turned off).
Click to expand...
Click to collapse
This idea sounds interesting but help me get my head around this (I'm a newbie to androids). In order to use a custom recovery to bypass the verification I would need to root the phone in order to install the recovery, correct?
oldsoldier2003 said:
This idea sounds interesting but help me get my head around this (I'm a newbie to androids). In order to use a custom recovery to bypass the verification I would need to root the phone in order to install the recovery, correct?
Click to expand...
Click to collapse
No, your device does not need to be rooted to install a custom recovery. All you'd need is an unlocked bootloader.
thanks! It is starting to sink in now. I'll do some more research and look into installing an unlocked bootloader. You've been extremely helpful and I think you have probably pointed me in the direction I needed to go with this
Cheers!
Theonew said:
You could try this: http://forum.xda-developers.com/showthread.php?t=1321582.
Click to expand...
Click to collapse
Just for the record, this exploit does not work on Android 2.3.5 on Samsung devices. The script runs and the device reboots without being rooted.
Update:
Still no luck with this one. The new universal gingerbread root by StoneboyTony gives a whole file signature error. I'm at a loss as how to replace the bootloader with a custom recovery that doesn't do signature verification.
1) youd need to build a custom recovery for teh device and flash it using odin.
2) flashing any old recovery could cause bricks
3) best way to build one? getting root and getting the files off the device to build with
4) sorry i should have publicly posted it sooner, samsung repp is rooted :/ when i get the time ill upload the files etc
shabbypenguin said:
1) youd need to build a custom recovery for teh device and flash it using odin.
2) flashing any old recovery could cause bricks
3) best way to build one? getting root and getting the files off the device to build with
4) sorry i should have publicly posted it sooner, samsung repp is rooted :/ when i get the time ill upload the files etc
Click to expand...
Click to collapse
Looking forward to when you get a chance. I've tried several methods but this sucker is just not rooting for me. When I get a chance I'll try to manually root it over ADB but I think that my biggest issue is going to be that zerg rush may have been patched in this version of gingerbread so manually rooting it may not have any better results than the methods I've tried so far.
@shabbypenguin:
I found your thread dated august 2nd - http://forum.xda-developers.com/showthread.php?t=1812177 But it doesn't have a link for the rooted kernel. I'll subscribe and keep checking the thread to see if a new link shows up.
Awesome job and thank you.
rooted evo
i learned how to evo
Samsung repp root
Now its been a while,but i have 2 rooted samsung repp phones
and im pretty sure this is how i did it.please do it at your own risk.
Even though im pretty sure this is how i did both of mine.
Samsung repp clockwork mod recovery install
Actually,heres the files to install clockwork mod recovery
for the samsung repp also.i did this on both of mine too.
Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English
Chainfire has the solution for you. Root and keep everything else stock.
http://forum.xda-developers.com/showthread.php?t=2507211
You will have to unlock your bootloader if you haven't already done so.
DreamLinker said:
Hi,
I would like to root my phone mantaining the stock recovery, and booting temporarily a custom recovery
If i execute a "fastboot boot customrecovery.img" and then i install from zip the "UPDATE-SuperSU-v1.69.zip" for example, I know that i will have a rooted phone with stock recovery.(right?)
I would like to do this in order to receive OTA without manual installation (i'm right?), thing that i have already done on my "old " Galaxy Nexus and now i would like to avoid doing it on the N5. I know that, in a case like this, i will lose root and then i have to do the process again.
The question is: There's just some contraindication doing this?
Thank you very much. I already tryed to find an exaustive answer searching the forum.
PS. Sorry for my poor English
Click to expand...
Click to collapse
Your method of booting a recovery image will work fine. That's the way I would do it.
Thanks you all very much!
I was trying to fix the kit kat sd card rw issue by first, rooting my smt800. This was no problem. I was hopimg to do as your forum suggested, add the missing command code in system/ etc/permissions/platform.xml. This did not work. I"m now want to find a rom that has this code inbedded in it or if possible, bring google down a notch by using a earlier operating system without this issue. My new problem is my access has been denied. superuser gives a notification stating, no binary installed. I know i will have to reroot. My question is whats is the reason it lost or cant locate binary, how do i keep from haing to reroot multiple times. i did not do anything other than a simple root and edit. any suggestions
Hello,
Try to roll back to your original firmware, link you can find it here.
And try to reroot back your device, sometimes some binary will lost or will be hidden and won't let you to edit however. But try to go back to stock and reroot. And all of the problem will be shorted out!
HashyCode.