Database Info

[Q] How to Root the Samsung Galaxy Prevail?

I am a c++ programmer by trade who is just now looking into android phones not only for communication but also for development. I picked up the Samsung Galaxy from Boost Mobile in order to first learn how to root, flash ROMs, and then get into dev.
My first goal is to root the phone so i can use it as a wifi hotspot. I first tried to download quick settings to see if i could get the wifi hopspot that way. I can see the hidden option for wifi hotspot but everytime I press it to turn it on, the phone disables the wifi totally. I then tried z4root, not root. I tried gingerbreak and it did not work. I would try to use superoneclick but cannot find usb drivers that will work with the galaxy prevail while its in usb debugging mode.
Any advice on how to get this phone rooted would great. Can you also list the prevail as one of the device supported on this site to spur development?

Not sure if you've come across the Prevail source code, the file name is SPH-M820_OpenSource_Froyo.zip
I can not post an actual link because I'm new to this site, but you can find the file here:
opensource dot samsung dot com/reception/reception_main.do?method=reception_search&searchValue=m820
replace "dots" with a period

I have not been able to get mine rooted either, but I did find these drivers seem to work for the phone with win7 and xp.
http://dl.dropbox.com/u/12826399/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe

Try Z4root app I think this might work considering there arent any nam locks on this phone go to 4 shared and look for the apk files as this app is no longer available in the market! I have used this app on the following devices, htc hero, sprint zio, samsung moment, droid 1, droid 2, &droid global!

I tried Z4Root it did not work.

recovery mode
recovery mode is vol up + power
says
Android system recovery (3e)
EATH /data/update_sucess
E:Update logfile dose not exsist
#MANUAL MODE#
navigate with vol keys and camera button to select

z4 root and super one click
i tried z4 and the app closed at acquiring root shell
super one click also failed with psneuter and ginger break
fails at running psneuter and at running gingerbreak
also fail with shell root in same way

unrevoked
ps the unrevoked roots just do not detect the phone

odd recover style screen
if you hold down vol + and vol - and camera then tap power a screen comes up that starts with little kernel
vol - and camera makes the phne show "downloading..."
this is shown in windows as "samsung usb compsite device"
and "samsung mobile modem"

on linux
dmesg output of the "downloading..." screen
[ 77.031415] usb 1-1: USB disconnect, address 2
[ 84.590135] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 84.748548] cdc_acm 1-1:2.0: This device cannot do calls on its own. It is not a modem.
[ 84.748762] cdc_acm 1-1:2.0: ttyACM0: USB ACM device
********-laptop:~$

i have tried all known roots to my knowledge: z4 (rageagainstthecage), psneuter, and gingerbreak. none work. so im with you, out of luck.

same here i tired a bunch and no luck

I've been trying too, no luck at all, been at it since last Friday, but my knowledge is not nearly as good as most of you, so I assumed I just didn't know what I was doing.

I tell ya, I'd love to see root on this thing. Sweet little device. Greatly appreciate all who are working on this task

I have not found a way to root this phone but i did accomplish USB tethering. Install Samsung Kies (for usb driver for prevail), install PDAnet on computer and phone, and away you go. I am looking for a windows 7 bluetooth driver for the prevail that way i could tether via bluetooth DUN. Does anyone have any success finding a prevail bluetooth windows driver?

how to root
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.

themonkeymixer said:
Is there someone who can direct me to a good place on how to develop the root, I would be willing to spend some time working on this. In particular is there any work that I can do to help a developer to create the root.
Click to expand...
Click to collapse
I wish google could help for that lol. I want to move my apps from the internal memory onto a sd. 164mb internal memory come the **** on

Any1 root this thing yet??????????

Same experience here, z4root required phone reboot as it kept setting off the vibrate function (permanent root) and eventually locked up the phone. z4root temporary root didn't work either. SuperOneClick failed as well with both exploits and locked up on Windows 7 x64 while running exploits. Can't find any information on Google. However, I am a 4th year Software Engineering student and would be willing to work with others to find a fix.
The Samsung Galaxy Prevail is a pretty cool little phone for the money and worth the exploitation effort. For those interested in working on this issue with me know that I am both a Windows (7 x64) and Linux (Slackware x64) user with a Java programming background. Look me up (email) on my profile.

From what I understand... We'd have to set up a rom manipulation environment (cooker?). Unfortunately the only tutorial I can find is the one for manipulating HTC roms. I'm not experienced enough to know if it could be used for all Android roms and too much of a chicken to try it out and risk bricking my phone.
Once the rom manipulation environment is set up you can go and add root support, take out unwanted apps, etc.
I'd also be willing to put in some effort into learning this if someone is willing to put in some time to show me the ropes... or point me in the right direction.

[Q] su errors when trying to root

hello, I have been trying to root my motorola backflip 1.5 for over a week now with no luck. I have been trying the rageagainstthecage-arm5.bin method and it seems to run fine but when I run su in the terminal emulator it gives me the following error:
bionic/linker/linker/.c:1581| ERROR: 7265 could noot load ´libbinder.so`
bionic/linker/linker/.c:1641| ERROR: failed to link su
bionic/linker/linker/.c:1741| ERROR: cannot link executable `su`
I am trying to root my phone so I ca update it to 2.3 but I can't complete the rooting process, can someone please help me!

try superoneclick

I tried superoneclick, same results!

god damn it....... search xda for rooting methids then if you keep getting su errors then you might not be able to root the phone

jose_am said:
hello, I have been trying to root my motorola backflip 1.5 for over a week now with no luck. I have been trying the rageagainstthecage-arm5.bin method and it seems to run fine but when I run su in the terminal emulator it gives me the following error:
bionic/linker/linker/.c:1581| ERROR: 7265 could noot load ´libbinder.so`
bionic/linker/linker/.c:1641| ERROR: failed to link su
bionic/linker/linker/.c:1741| ERROR: cannot link executable `su`
I am trying to root my phone so I ca update it to 2.3 but I can't complete the rooting process, can someone please help me!
Click to expand...
Click to collapse
Well bionic is the android version of the libc programming library and libbinder.so is a library of some kind, which it can not load, either because it is not there, or not where it is looking for it, or not accessible due to permissions or an incompatible library for your system.
No idea how to fix it though, but thought i would shed some insight.

Hello there well I'm using superoneclick and I found that its not putting the su exe in the right place it puts it in (/system/xbin/) and where it should go in /system/bin where all the commonds are.?

Are you sure that you're rooting it correctly?
Please make use of the instructions below .
Download Super One Click, make sure you have the Android debugger (SDK developer kit) running, expand the Super One Click zip file and click the SuperOneClick icon to run it. When SuperOneClick launches, you’ll see several large buttons at the top of the screen. Make sure your phone is connected to the computer via USB and that the debugger can “see” it (activity will start logging). Make sure your SD card is not mounted, and go ahead and click “Root” in SuperOneClick.
You’ll see the scrolling activity as SuperOneClick does it’s job, with “OK” appearing after each task. You may see warnings, but so long as it doesn’t “hang” on waiting for device, things should keep scrolling until it finally returns the “Success!” message. If you're stuck , go to your phone and enable usb debug and disable again . Until you get past it , that's how i got it to work for my phone.
At this point, check out the installed apps on your phone and you should see a “Superuser” icon that looks like a Droid skull and crossbones. If you see it, you’re rooted. If you don’t see it, reboot the Droid. In fact, I’d suggest rebooting even if you do see it, as I had some issues getting rooted apps to work until I actually rebooted my own device.

Need help with samsung skyrocket root!!

So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.

is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.

shansmi said:
is the sdk installed under admin and your running the tools as a user or vice versa? they have to be equal. you could try killing adb and running it again if it is not a permissions thing.
Click to expand...
Click to collapse
I have not changed anything since the first success of my Skyrocket root. It's weird that it would root the first Skyrocket but not the second one.

I used this one.
http://androidadvices.com/root-samsung-galaxy-s2-sky-rocket-4g-sgh-i727-tutorial/

Solution for "Files not found" and "permission" when trying to run ZergRush
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!

trying to root
ashque01 said:
Usually, I do not have a habit of writing on discussion board. But out of sense of gratitude for makers of ZergRush, I felt obliged to share way to get your phone rooted..
My phone is Samsung Galaxy SkyRocket (Android 2.3.5)
Steps:
1. Get instructions and Samsung driver from following site
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
2. I used ZergRush root from following location
http://www.google.com/url?sa=t&rct=...sb2HAg&usg=AFQjCNFU6uftUB2XRt8Q0rZC8faCn1PfBA
Now the most important thing of running the Root
1. For windows 7, do NOT double click on the root.bat or any exe file.
2. Open Windows Command prompt in ADMINISTRATIVE MODE, navigate to the batch file.. for example:
D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat
and your root process will start.
Most of the people when try to double click do not have required or correct Environment path settings hence they see the error for files not found!!
Hope this resolves the issue.. Goood luck !!
Click to expand...
Click to collapse
I still get errors "system cannot find the path specified" and it doesn't work.
ashque01 you put "D:\Android\DooMLoRD_v3_ROOT-zergRush-busybox-su>runme.bat"
I didn't get that to work until I switch the > to a \ the arrow instead of a backslash makes a difference, beg pardon but I don't know dos very well and I did use the arrow with no success, lol...
Once in the command prompt (you get there by typing exactly that "command prompt" in search bar, after clicking the start button in windows 7) Right click on command prompt to run as administrator.
I put D:\DooMLoRD_v3_ROOT-zergRush-busybox-su\runme.bat because that's where I used 7zip to extract it to, in the root of hard drive partition. It ran but with errors and announced done! press any key to continue.
I tried it again by creating a subfolder on the D: partition named android like you did, tried it again, same thing,
Still hoping to get a superuser icon so I can download my root explorer app from the market.

YAY!
I got root.
I told all of about it in that thread I started titled s#%rocket. I did admire what Entrophy remarked about it's hardware being disagreeable, but that was in the i777 thread. I had no business there (mod moved my thread, thank you) as my handset is i727.
I coulda swore that's what about phone said before I started but sure enough when you pull the battery it says i727 right there, can't argue with that, I was just being "elevator up, but door not open"
Beg pardon

androiduser1 said:
So, here's my story. I am trying to gain root access to my Galaxy S II Skyrocket. I see a lot of posts/replies of other people having success with SuperOneClick 2.2 using the zerg exploit but for some reason mine just hangs and doesn't go any further. To kind of backtrack, I was able to root my first Galaxy S II Skyrocket, but then I had charging issues so I exchanged it for a replacement. Now, the replacement will not root. And even with the first one I had a hard time gaining root. It took me several, several attempts to get it working. I don't understand what I'm missing. Any help or suggestions would be greatly appreciated.
Few things...
- Samsung Galaxy S II is currently on stock 2.3.5 with firmware UCKJ2
- USB debugging has been turned on
- Samsung USB drivers have been successfully installed on PC
- Using Windows XP
- Using SuperOneClick 2.2 with zerg exploit
- Tried uninstalling USB drivers and reinstalling
The status one the SuperOneClick is as follows...
Killing ADB server
Starting ADB server
Waiting for device...
That's it. Nothing else beyond that. And on the right hand side it indicates this...
It's keep stating that 'daemon not running... starting in now on port 5037' and it keeps looping and eventually does not move.
I've tried using different methods of rooting this such as Skyrocket-Easy-Root and Doom's EasyRoot 1.0 and the 'daemon not running... starting it now on port 5037' message occurs on those as well.
PLEASE TELL ME WHAT THE HELL IS GOING ON because the regular Samsung Galaxy S II and other devices go through just fine. I know it can be done because obviously other users are successful with root and I was too with my first Skyrocket.
Click to expand...
Click to collapse
use 2.3 not 2.2
Sent from my SAMSUNG-SGH-I727 using xda premium

[Q] adb doesn't recognize my phone

I posted this question over on Phandroids but this forum seems perhaps more appropriate. My Lenovo laptop running XP sees my phone just fine (Samsung Gravity Smart SGH-T589) and I'm able to transfer files to/from the phone. However, adb doesn't seem to be able to see it. A search about this problem turns up solution suggestions that mostly involve drivers, but my Samsung driver is up to date and clearly working (or else the phone wouldn't show up to Windows and I wouldn't be able to transfer files). My phone is rooted, which also makes it obvious that my laptop can talk to it just fine -- I used OneClick to root it last week using the same computer.
I'm using the DOS prompt (cmd) to run adb, and adb works fine. It simply doesn't see any devices. Here's an actual text transcript:
===============================
C:\Android\adt\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Android\adt\sdk\platform-tools>adb shell
error: device not found
C:\Android\adt\sdk\platform-tools>
===============================
Any ideas? I'm pretty new to this, so perhaps I'm missing something really simple. I hope so anyway!
--
Craig
Sunnyvale, California

Make sure that USB debuggin is enabled on your device. (This option should be changed only while device is disconnected from USB).
Also, try to restart adb server by killing it from the device manager.

Thanks for the suggestions. I had indeed already done both of those things. USB debug must be enabled to do file transfers, so I already knew it was definitely on. I still cycled it off/on anyway to make sure. And I did both kill-server and start-server commands as part of my checkout to assure myself that adb was in fact working correctly. I had Windows task manager up as well so I could watch adb disappear and reappear with those commands.
--
Craig
Sunnyvale, California

Hmmm... Try to reboot both your computer and device.
Have you tried to connect other devices to ADB? May be there is a problem with ADB installation?

Phone and laptop have both been rebooted many times. I also tried it with the phone in charge-only mode because that's what One Click Root required, but nothing changed. I also tried using all of the different USB ports on my laptop and tried two different USB cables, although that was silly because the phone is obviously talking to the laptop via USB. It shows up in file explorer, and I am able to transfer files using Windows drag and drop.
I'm afraid I have only one device, my recently rooted Samsung Gravity Smart phone, so I can't try it out on anything else.
I'm not sure how the adb installation could be at fault since the commands work as long as they don't involve the USB port. And I know that it MUST be possible to shell to the phone with what's already on this computer because One Click did it. I tried running the adb commands from the One Click Root > ADB directory just in case something about that particular install of adb was different, but I got exactly the same result.
It seems to me that I must be failing to do some setup step that an experienced Android developer might know about. I've never done anything like this before, so I wouldn't have even known about downloading the Android sdk if it weren't for forums like this! I sure appreciate the community of knowledgeable people here, who are clearly willing to help newbies like me.
If there are any software tools that anyone can suggest using to help me figure out what's going on, please let me know.
EDIT: Is there something that I need to load on my phone before adb will work? It occurs to me that OneClick might push something to the phone when it does the root, then delete it when the task is complete. I tried using QTadb, which is an adb GUI, and got the same result: no devices seen on the port even though Windows sees my phone and can talk to it via USB.
--
Craig
Sunnyvale, California

[Completed] Srrange ADB sideload error, shows device but can't push or sideload files.

Hello all,
So I have a Kindle Fire HDX and I decided to try play around with safestrap on it. It was going well but me being stupid didn't realise that when I was wiping everything, I was not just wiping the contents of the rom slot but the entire device! So I am in a soft-brick state at the moment, which is OK because I have been here with lots of devices before, just not any quite as restricted and complicated as the HDX. So my only option is to push the zip file or sideload it through ADB, which seemed to be a fairly easy task. My first challenge was installing the necessary drivers for windows 8.1 to recognise the device in adb sideload mode. I managed to do this successfully however now I have a problem when trying to sideload or push files to the device. When sideloading, the server starts successfully but I get a *failed to write data 'protocol fault (no status)' * error. When trying to push files I get an error:closed, the same by running the usb command (I am not sure what this one does but I seen it as a possible solution so have tried it). When I run the devices command I see my device connected and it is shown to be in sideload mode. I have tried the following in order to resolve this error, all have been unsuccessful:
New USB cable
Different versions of ADB (minimal and android studio)
Different computers and operating systems (each again with minimal adb and android studio)
Updating the packages in android studio, including installing the official kindle fire driver from amazon
Killing the server and starting again
None of these steps have helped and I am finding this to be incredibly frustrating as in every thread I have read online one of these solutions has managed to fix the problem for the person asking the question. I figured there isn't a place on the internet with a better knowledge and understanding of adb than here so there would be no better place to ask. Any help you guys could offer would be much appreciated. Also I am relatively new (and dumb) when it comes to adb and using the command line so if you guys could dumb it down as much as possible that would be brilliant.
Thanks in advance
EDIT: I have also noticed that when trying to format the device from the TWRP menu I get an 'unable to locate device to partition' error. I'm guessing this has something to do with it

Just thought I'd update this thread with the fix I found in case anyone else in future has this problem and googles around. I am not sure if I specified but the issue was with a kindle fire hdx 7". Safestrap would not let me change the active rom slot to the default OS and it was stuck in rom slot 1. So I contacted amazon and asked them if there was anything they could do to help me. They started off by giving me the usual reset by holding the power button. I thought there is no way that could fix it because I wiped the system files and that is the problem (I could see from TWRP that the system files were empty). So just in case I done as he said and after holding for a full 40 seconds, the previously soft bricked kindle booted back into the stock os and whilst it was completely wiped, it was now fully functional! I am sure this will only work for a very small percentage of people with a soft brick but definitely try it none the less. I would be interested to hear anyone who actually knows the technical aspects of this chime in with what happened here. Did it just look like I wiped the entire system in TWRP because it was hiding the system files? (even though I could see the folder and it appeared empty). Or does the kindle have a built in recovery drive through which it will replace these files when the power button is held for 40 seconds?

Hi,
Thanks for using XDA Assist if you are getting partition error then possibly your partition table is wrong rectify it and see
Good luck!

No Response .. Thread Closed .. Thanks