Related
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.
All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.
I did a stupid thing today. Had issues with my P769 lagging due to different mods I have been doing. I figured I would do a nice clean install.
Rebooted into TWRP and did a full wipe. OK, that's pretty standard with me. I screwed up by forgetting to load a ROM on my SD card. Feel free to laugh, you know what's happening next. Couldn't get TWRP to do any form of mass storage mode so I can connect it to my computer so I had a moment and rebooted. Phone rebooted to the LG screen and nothing else. I can get the device to show up as a mass storage device. Not accessible. I can get into software update, set up for a kdz restore (been there, done that) gets stuck at 15%. OK, tried to update fastboot, no go. PC (Windows 8.1) doesn't recognize the omap so I can even verify drivers. I have soft bricked before and managed to come back. Any suggestions?
Try online update
Use the KDZ update tool, without all the shttps stuff. Just run the tool. Look for a 'recovery option' and use that.
Hey guys, new member here but been a lurker off and on for awhile.. not sure what to do, you guys are my last hope.
I have a Samsung Galaxy Core Prime from straighttalk. Android version is 4.4.4 (I think).
Anyway, I was screwing with it trying to speed it up using a few apps I downloaded from the store, the apps let you uninstall apps that the normal manager won't let you and manage what system apps are allowed to run at startup..etc. also I was messing with applock and phone encryption.. So I'm not sure what messed things up.
Well needless to say, I shoulda been more careful, because now my phone is screwed! I can't view my home screen at all so can't call/txt and can't access my settings to try to fix the problem..
Before people tell me to reformat it, I have tried 100 times.. I press volume up + power + home to get to bootloader and tried doing a full reformat as well as wiping the cache partition... Reboot phone the setup screen comes up asking for my name/google account..etc but I can't complete it, it always crashes sayin either "hangouts has stopped working" "setup wizard stopped working" or something about a android.keyguard service.
So next I jumped on Google and read to try the Kies software but I can't for life of me get it to detect my phone.. took awhile but I think I got all the drivers installed.. kies will just say it's connecting to my device but never does. Tried kies 2 and 3 and different cords, I think it's because android isn't even truly fully installed since the setup wizard crashes.. so the MTP capability isn't even there.. under my computer I don't see my phone either like I use to, just a blank drive that has no name and can't be accessed.
So then after more reading I decided to try "ADB sideloading".. I'm a newb is to this stuff so idk if I even did it right but hooked usb up went into bootloader and reformatted/cleared cache then I went to ADB and using cmd on my pc I tried to send a zip of cyanogenmod (got it on xda, suppose to work on galaxy core prime) and it said it was successful but it doesn't do anything.. so idk if it's cuz u can't use custom roms with the stock bootloader? I read about other Rom managers but how am I suppose to install them?
if a stock firmware will work, where can I find one?
Sorry for the wall of text, I'm just stuck here and wanted to add everything I could think of that I tried already.
I dont think it's a physical hardware problem, I think i just screwed some system files up somehow which screwed up the recovery partition..
Extra note:
I am able to use the internet browser though, when the setup gets to the step to link your google, in the top right I can go to "enter browser signin" and then I can bypass the fact there's no search bar by clickin privacy policy and clicking a logo to bring me to Google's homepage.
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Mr.cryptkeeper said:
At this point I don't even care about saving data, what Rom is used or anything. Just wanna be able to text and make calls again.
Forgot to add but using the Google accounts bypass to use the browser I also tried going to google play from there and got the play app to open on my phone but it won't let me install any apps (stuck downloading forever) and will say the app isnt supported on my device even when it should be... tried the android device manager but it cant locate my phone and the reformat option there doesnt work either.
Click to expand...
Click to collapse
Get a custom recovery (preferably twrp) and then wipe EVERYTHING in the wipe section except your sdcard and then just adb sideload cyanogenmod or any other CUSTOM rom for your phone.
You should just be able to reload the original firmware with Odin. Or Kies will probably work, but you have to use Download Mode to be able to restore it, not while it is booted into the OS.
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Mr.cryptkeeper said:
Thanks for the replies, bit I wish it was as easy as you guys make it sound. Kies isn't working because the MTP driver fails to install on windows no matter what mode I'm in or usb port/cord, no way to access usb settings on phone since I can't get past android setup into the homescreen. Also usb debugging is probably not enabled.. how can I enable that when I can't access settings?
I tried to install TWRP (through adb sideload since can't install anything from store) but when I do "adb devices" nothing is listed.. when I tried it on linux there WAS a device listed though so I did sudo adb sideload twrp.zip from within adb folder and it said it sent it but on my phone it says something about a error verifying it or something then it automatically tries again and says it completed and goes to reboot but it doesn't appear to have worked because there's no sign of it.. is TWRP just suppose to replace the stock bootloader if the sideload is successful? If not how do I access it? Also tried sideloading cyanogen right from the stock bootloader but get the same thing.. says it was sent 100% and phone reboots but there's no sign of it... perhaps I'm doing something wrong?
Argh so frustrating all the time I've wasted trying to fix this. I even completely wiped linux off my pc and installed windows 7 again thinking it was a compatibility problem, but now I think I just went backwards because at least on linux my phone was detected doing "adb devices"...
Click to expand...
Click to collapse
Yes you have to be in recovery to actually be able to do adb sideload, try adb reboot recovery.
Hello
First of all, I'm kinda noob so bear with me.
So, I have a ZE554KL that used to be rooted and working quite fine, but I want to unroot and install the stock rom, as if just came out of the store.
After several problems, now I have a phone that I can access the fastboot and thats it. No recovery mode, no TWRP, no regular boot.
Also the PC cant find it. When I connect the device to the PC, the devices manager cant find anything new, no sound of a new USB device or nothing similiar. Tried on my regular PC, same that I did the root months ago, and on a new PC, recently formatted.