Related
I have a samsung vibrant that i rooted in order to tether, set cpu, etc. I am trying to unroot my device to return it to stock but i cannot figure out how to do it. I downloaded one click root for mac but when i connect my device and click unroot, nothing happens on my phone. I've tried usb debugging, non-debugging, mass storage, nothing gets the phone to boot into the recovery. Help!
Thanks a ton for the help!
PS i have a mac.
have u fixed this? try superoneclickroot 1.6.5 worked for me. this is the only one i trust rooting my fone with
as i said in title guys can anyone who know how to do this? is this impossible? my usb port is broken i cant charge and i cant to to pc. i already went to repair shop but im unlucky i can access the xRecovery but this is for 2.1 im on 2.3 and i install xRecovery without root 2.3.
EDIT: sorry for this ignore all message above. i remembered i root the 2.3 fw before did broken my usb port. but im using xRecovery 3.0 for 2.1 and i have a card reader and download the latest xRecovery made by Z. can i flash directly this?
gAracUh said:
as i said in title guys can anyone who know how to do this? is this impossible? my usb port is broken i cant charge and i cant to to pc. i already went to repair shop but im unlucky i can access the xRecovery but this is for 2.1 im on 2.3 and i install xRecovery without root 2.3.
Click to expand...
Click to collapse
Did you try this?
<CALL FOR STICKY>painless root for x10 in 5 seconds (TESTED ON MY X10i)
It states it works only by using the apk, if that is true the root would require the usb cable, you would only have to transfer the file, which can be done in many ways, dropbox, e-mail,...
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Have you loaded an insecure kernel using Odin?
SusieGalaxy880 said:
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Click to expand...
Click to collapse
The easiest way to gain root would be to flash a ROM that has root already. Such as this stock ROM: http://forum.xda-developers.com/showthread.php?t=1512331
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
These kinda more difficul steps,, and i dont wanna mess any of those because if any step goes wrong, I duno how to fix it. Aren't most people use the easy way to superoneclick to root and successful? I just want to know which step I did wrong for my fail root. I dont wanna mess with any deeper or more diffiuclt stuff.
SusieGalaxy880 said:
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
Click to expand...
Click to collapse
You shouldn't have connected mass storage.
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
SusieGalaxy880 said:
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
Click to expand...
Click to collapse
From my experience just have Windows 7 doesn't ensure have framework 4+ so check for a download on that.
If your USB debugging mode is ON then you shouldn't get the "connect mass storage" option on the device at all, so double check that (uncheck and recheck it if necessary.
Personally I choose to skip Kies entirely and just download the drivers only, but the first time you plug the player in with Debugging on windows should do it driver search thing down by the clock and it installs (i think 3) different drivers for the player (different then the mass storage driver) if you jumped in to superoneclick before that finished that may have been part of the problem, if you didn't get those to install then sounds like a driver issue.
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
SusieGalaxy880 said:
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
Click to expand...
Click to collapse
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
I didnt restart my device before rooting.
I got the superoneclick from XDA main page the offical one with 500+ page of posts and reply. "Superoneclickv2.2 -shortfuse.zip"
Try using doomlords rooting toolkit, it worked for me.
http://forum.xda-developers.com/showthread.php?p=18805532
thanks for info, but I duno how to use the DooMLoRD's Easy Rooting Toolkit. Any instruction? I have no idea why my device is so diffiuclt to root, as other people rooted very easy
I used version 2.3.3 to root mine.
Got to shortfuse.org and scroll down to the 2.3.3 download link.
I tired the 3rd time today, failed again, same outcome. This time I follow each step carefully, and I used superoneclick v2.3.3 Before ROOT, I make sure all the "READY TO USE" check mark on. But still hang at Shell Rooting device step #5. I patient waited for 20mins, still hang at this step.
I shoulda try root when I got it first day. Is there possible some mess up app might cause this? I never heard anyone have any diffiuclty Rooting their galaxy player 4.0 YP-G1 US version with superoneclick after so many tried. I officially give up. I only have this device for 1 week..............
Kernal Version 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build # Gingerbread.UEKI8
Firmware V2.3.5
Model Number: YP-G1
I found a very important issue might cause this failed. When I check the unzip folder, the Expoits folder IS NO FILE, EMPTY, but when I check the original zip file, it has 3 important files "GingerBreak,psneuter, zergRush" files (on the v2.2) I try unzip on desktop, pull out this Exploit folder, pull out the file, none work. I even uninstall winRAR and restall the newer version. These 3 files on the exploit folder in superoneclick v2.2 seem CANNOT pull out of the zip file no matter what I try. I think on shell Rooting device step #3 started the problem cuz cannot locate these few important exploit files. I just found out the unzip folder have no those file (psneuter,zergRush), while the original zip file has, and I cannoot pull out those file out of the zip folder NO MATTER WHAT I TRIED. Both superoneclick v2.2 and v2.3.3 exploit folder, i cannot get those file out of the zip folder.
Got rooted successful the 4th tired. Problem is my antiviurs always remove the psneuter & zergRush files in exploit folder when I extract everytime. And I didnt notice this problem. So I was rooting without these 2 important files in superoneclick folder. Now I disable antivirus, so i can extract those file and start rooting, after done rooting, i turn antivirus back on.
another problem
daniel644 said:
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
Click to expand...
Click to collapse
can someone help me i have the ``firmware uprade encountered....``
i can go to the the warning but
-if i press up to continue it return to firmware....
-if i press down the same thing
thanks.
Hi, this is my first post here.
I have an unbranded international Galaxy S3 GT-I9300, Android 4.0.4
Kernel Version: 3.0.15-928452-user
[email protected] # 1
AP: I9300XXBLG8
CP: I9300XXLG8
CSC: I9300DBTBLG6
Long story, so I better put my questions first:
How can I flash a non-rooted device without using the USB port? SD-Card somehow?? Download mode is working at least...
and/or
How can I remove a Super SU system app from a apparently non-rooted device? (...which can not be rooted by using the USB port)
What happened:
I had rooted my device via this instuctions: http://forum.xda-developers.com/showthread.php?t=1695238
-> [03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager.
I used heimdall 1.3.1 on Ubuntu 12.04 via 'sudo heimdall flash --recovery recovery.img --cache cache.img'
All worked fine.
When the latest OTA firmware showed up a couple of days age (45,76MB) I tried it and it failed at 29%.
I remebered I had deleted some bloatware and thought maybe bringing it back would make the OTA work. Because I coudn't find Samsung Video Hub at some point I thought it would be the easiest to just factory reset, then run OTA and reroot.
I made lots of backups with Titanium Backup ROOT and I rolled back the BusyBox changes. I also reverted some later installed App to a non-system App again but am not sure which one, it was not Super SU, maybe the terminal app.
I then made a factory reset from within Android, on reboot CWM appeared and I choose the single one 'yes, delete all data'
After rebooting I tried to apply the OTA, still stuck at 29%
I realized that there ist still Super SU left as a system app and thought that might be the reason. However I decided to first give Kies a try with the update.
Installing Kies and connecting the phone (via my gf's Xperia Ray cable) went fine and it showed me the update. Because of memory shortage I had to move some things around, time passes, my gf sit down on her office chair and somehow remaind hanging on the usb cable,
my phone fell down. At first there doesn;t seem to be any problem, but after trying to reconnect to Kies, it didn;t work. I found the USB cable not working anymore, which means that no mobile is charged if connected via that cable now.
However I could not establish a connection from my phone to a computer again since then (original usb cable, another usb cable).
Not to Ubuntu (not recognized in heimdall), neither to any of 2 different windows 7 computers.
I know there is a lot of connection problems out there for S3, I cleaned the connector, and tried lots of stuff like not giving google account credentials after wipe, try different usb-ports, restart computer. Windows always says "Unknow device" now. Ubuntu, also heimdall 1.3.2 just says nothing.
Thats why I guess that somehow there is a hardware problem with the USB connector on the phone now. Charging and MHL is working. It also recognizes USB OTG cable, but not the things that I attach to it, it worked flawless before. USB Debugging on/off -> no difference. Also the option to switch MTP/PTP under Preferences->Storge->USB is gone (was there before my first reset)
As a side note, also WLAN is not working as before anymore, I always have to use a static IP to get connected to my FritzBox.
Because the ruins of SuperSU are still in the system I can not update. However the phone is not rooted as all apps I have tried claim. Reinstalling Super SU did not bring root back. It is there, it thinks the device is rooted but it is not. But I also can not get rid of Super SU.
So now, I can't use normal OTA update, can't reroot or use my backups, bc Titanium requires root.
I am stuck. Is there any way out? Or at least a direction?
Thank you for taking the time.
Silvio
einSelbst said:
Hi, this is my first post here.
I have an unbranded international Galaxy S3 GT-I9300, Android 4.0.4
Kernel Version: 3.0.15-928452-user
[email protected] # 1
AP: I9300XXBLG8
CP: I9300XXLG8
CSC: I9300DBTBLG6
Long story, so I better put my questions first:
How can I flash a non-rooted device without using the USB port? SD-Card somehow?? Download mode is working at least...
and/or
How can I remove a Super SU system app from a apparently non-rooted device? (...which can not be rooted by using the USB port)
What happened:
I had rooted my device via this instuctions: http://forum.xda-developers.com/showthread.php?t=1695238
-> [03.07.2012] CF-Root 6.4 - SuperSU+CWM5.5+CWMManager.
I used heimdall 1.3.1 on Ubuntu 12.04 via 'sudo heimdall flash --recovery recovery.img --cache cache.img'
All worked fine.
When the latest OTA firmware showed up a couple of days age (45,76MB) I tried it and it failed at 29%.
I remebered I had deleted some bloatware and thought maybe bringing it back would make the OTA work. Because I coudn't find Samsung Video Hub at some point I thought it would be the easiest to just factory reset, then run OTA and reroot.
I made lots of backups with Titanium Backup ROOT and I rolled back the BusyBox changes. I also reverted some later installed App to a non-system App again but am not sure which one, it was not Super SU, maybe the terminal app.
I then made a factory reset from within Android, on reboot CWM appeared and I choose the single one 'yes, delete all data'
After rebooting I tried to apply the OTA, still stuck at 29%
I realized that there ist still Super SU left as a system app and thought that might be the reason. However I decided to first give Kies a try with the update.
Installing Kies and connecting the phone (via my gf's Xperia Ray cable) went fine and it showed me the update. Because of memory shortage I had to move some things around, time passes, my gf sit down on her office chair and somehow remaind hanging on the usb cable,
my phone fell down. At first there doesn;t seem to be any problem, but after trying to reconnect to Kies, it didn;t work. I found the USB cable not working anymore, which means that no mobile is charged if connected via that cable now.
However I could not establish a connection from my phone to a computer again since then (original usb cable, another usb cable).
Not to Ubuntu (not recognized in heimdall), neither to any of 2 different windows 7 computers.
I know there is a lot of connection problems out there for S3, I cleaned the connector, and tried lots of stuff like not giving google account credentials after wipe, try different usb-ports, restart computer. Windows always says "Unknow device" now. Ubuntu, also heimdall 1.3.2 just says nothing.
Thats why I guess that somehow there is a hardware problem with the USB connector on the phone now. Charging and MHL is working. It also recognizes USB OTG cable, but not the things that I attach to it, it worked flawless before. USB Debugging on/off -> no difference. Also the option to switch MTP/PTP under Preferences->Storge->USB is gone (was there before my first reset)
As a side note, also WLAN is not working as before anymore, I always have to use a static IP to get connected to my FritzBox.
Because the ruins of SuperSU are still in the system I can not update. However the phone is not rooted as all apps I have tried claim. Reinstalling Super SU did not bring root back. It is there, it thinks the device is rooted but it is not. But I also can not get rid of Super SU.
So now, I can't use normal OTA update, can't reroot or use my backups, bc Titanium requires root.
I am stuck. Is there any way out? Or at least a direction?
Thank you for taking the time.
Silvio
Click to expand...
Click to collapse
Hi. First of all you can have ota updates with kies even if you are rooted as long as you haveone of the official roms installed. Su does not disturb your ota updates through kies.You wont be able to have ota if you are rooted without kies.
R u sure you tried other usb cables and your connection failed? Try another one......You are saying you can charge....These cables have got a lot of thiny cables inside. Even if one is damaged you will have a problem.Try a new Samsung cable.
In the worst case if there is a hardware issue after the fall try kies wireless app so you connect to the pc without cable.
How do you connect to your FritzBox?
looks bad
Hi art,
thank you for your input!
art_arev said:
Hi. First of all you can have ota updates with kies even if you are rooted as long as you haveone of the official roms installed. Su does not disturb your ota updates through kies.You wont be able to have ota if you are rooted without kies. R u sure you tried other usb cables and your connection failed?
Click to expand...
Click to collapse
I tried with two different cables (Samsung, Lenovo) on 2 different computers. What makes me quite certain that there is an issue with the usb connector is, that USB OTG is not working anymore. No matter what I connect, the only thing it recognizes is the usb otg cable itself, but no stick/mouse/hub.
The cable which is broken now is the SE Xperia Ray cable from my gf's phone.
art_arev said:
In the worst case if there is a hardware issue after the fall try kies wireless app so you connect to the pc without cable. How do you connect to your FritzBox?
Click to expand...
Click to collapse
I tried it, it seems that the Kies Air App as well as Kies over WLAN (via Androids Preferences to connect to the Kies Desktop Application) does not support any firmware updating. I connect to the fritzbox via WLAN, it worked flawless before and I haven't changed anything.
It seems I have the following options:
1. find a way to reroot or flash the phone without using the usb connector (I read somewhere that it should be possible, but no further instructions were given)
2. find a way to remove the left overs from rooting (Super SU) -> that would at least open the possibility to apply OTAs
3. send it to samsung and hope they will repair it (problem is there are still traces of rooting on the phone)
4. try to repair the broken usb-connector myself
5. continue to try to somehow establish a connection via usb
Concerning option #1: I have unsuccesfully looked into the following options: unrevoked, UniversallAndroot, Z4root
All threads I read say it's not possible (e.g. http://forum.xda-developers.com/showthread.php?t=1870267&highlight=root+without+usb)
If I can't make any use of the leftovers of Super SU I think option 1+2 are dead ends.
I think I should try option 3 and if they deny, try option 4 or live with an unupdateable (?) unrooted phone (nah )
If there is SuperSU in system/app folder than it should work. Try to use build in options in SuperSU to reinstall. Also download and install busybox.
If root will be present and give you all needed partitions than you will be able to use Mobile Odin to flash stock firmware. But you also must remove binary counter information. This is imposible without root and/or working USB port.
There is a small chance that after flashing stock firmware USB port will be fully operational once again. I suppose it could be a software/driver issue, not hardware malfunction.
You can try to flash first with Everoot option enabled and after that check your USB connection. Of course you must transfer stock firmware to your phone. Do this via AirDroid or write it on external sd card on computer and put it into your phone. (copy this firmware to your internal sd card, it's better to flash from internal memory).
To resurrect your phone you need root or working USB.
i9.0.1.3k galaxy imperator
Thank you for keeping the hope alive SirKunon!
SirKunon said:
If there is SuperSU in system/app folder than it should work.
Click to expand...
Click to collapse
The App in system/app is called Superuser.apk (if that makes a difference), from inside the App I can see it is SuperSU v0.93.
There is an update available in the playstore which I can apply.
If I start any app which requires root (BusyBox, Titanium Backup, Root Explorer, Root Checker) I get the Superuser prompt to decide if I want to grant root access. Even if I choose "Yes" it never works.
Using the options inside SuperSU to reinstall fails (it does not close) as long as I don't have the update of SuperSU installed. If that is in place. It will close and left me with the former SuperSU version. Same for the option to "switch to another Superuser App" and "complete unroot".
If I try to remove the check from the box saying "activate Superuser" it tells me "Uninstallation failed"
SuperSU is there, Root access not. The only thing I can think of is do a factory reset once more (already did a couple) and try again.
It seems like there is a solution just behind the next door but I can't get through...
It's very strange, indeed.
Try hard reset service code:
*2767*3855# - hard reset
I don't have any other ideas. Service center will refuse fixing it if there are root traces. But you can try to find someone with jtag box to flash stock firmware or replace USB circuit on your own if you are sure that's faulty.
i9.0.1.3k galaxy imperator
Thanks for your help.
SirKunon said:
Try hard reset service code:
*2767*3855# - hard reset
Click to expand...
Click to collapse
Tried it, but situation remains unchanged, SuperSU is there, root access not, uninstall/reinstall it has no effect
OTA still hanging at 29%
no usb connection
no wireless connection unless I use a static ip
At least the phone is working as is...
Will probably send it to service center b/c I have nothing to loose. Maybe try to use my gf's insurance on beforehand.
If all fails, open the device or live with it, not sure.
einSelbst said:
Thanks for your help.
OTA still hanging at 29%
YES as it does .
Turn off signature verification via recovery may help.
Triangle Away
Mobile ODIN Pro and flash stock rom from external sd card
Then factory reset .
jje
Click to expand...
Click to collapse
hi jje,
JJEgan said:
Turn off signature verification via recovery may help.
Click to expand...
Click to collapse
but I don't have correctly working root access and only stock recovery.
Do you think it is still possible?
einSelbst said:
hi jje,
but I don't have correctly working root access and only stock recovery.
Do you think it is still possible?
Click to expand...
Click to collapse
No as we still have no way of flashing stock from phone without recovery .
it was just thinking aloud anyway .
What is required is a method to root from within the phone which we don't have .
jje
Hey guys I have a Samsung galaxy core that had android 4.4.4 and i managed to screw it up and now unable to reformat it from stock bootloader.. It will say it formatted and reboot into the android setup wizard but unable to finish setup because of crashes. (Hangouts, setup wizard, and keyguard all stop working) so I can't access home screen, settings, call/txt nadda.
So because of that, none of the solutions I've found work for my case (kies, adb sideload, installing twrp from store)..etc because it's hard to do any of that when it's impossible for me to enable usb debugging, changge usb to MTP, or root my phone. (Did root with kingo before I screwed things up, not sure if still rooted since I wiped it with stock bootloader.. but pretty sure usb debugging isn't enabled, and MTP doesn't seem to be working since windows can't install the driver's and kies won't detect it.
So anyway, I think my options are limited.. but I have an idea but wanted to ask here first.. I noticed in the stock bootloader there is option to install from external storage.. and I have another android phone that works.. so is there way I can put the SD card from my "bricked" phone in the working phone and install twrp and cyanogen mod on it and put it back in the bricked phone and install from that? maybe there is already a tutorial out there?