hey guys im new to the scene and trying to figure as much stuff out on my own as i can, usually i do a good job and don't need to ask for help. but i do when i have to, so the problem i am having is with a sony xperia play .
its my brothers phone and i was thinking about getting one but i want to "root" it and see whats what with it but i am trying to do so without unlocking the bootloader just incase anything goes wrong with it later so it remains under warranty. im coming from the iphone jail-breaking scene so this is a little different. but i want to give it a go. so i'm trying to root it i checked out this post
http://forum.xda-developers.com/showthread.php?t=1044765&page=1
i realize at the top of the post it says not all devices are supported because of new FW's does the FW i am on fall in this category?
i tried it with the 1.2.apk and the 1.1
im not sure why it is not working.
but i have a feeling its got something to do with the FW the phone has come with
its running 2.3.3
build number 3.0..1.A.0.145
model number r800i
kernal version 2.6.32.9-perf
i formatted the SD card before anything then after i installed gingerbreak to the phone itself. (also tried it without formatting it, i installed gingerbreak and tried to run it then and it didnt work so i rebooted formatted SD card and tried again and still nothing)
made sure the phone was set to be in USB debugging mode.
gingerbreak opens and has the options there but when i tap "root device" it just says "running exploit" ect on screen and nothing changes. on the post it says usually about 10 minutes but i read through it and one person said it worked for theirs but it took an hour and a half, but another said it took 3-5 minutes.
so i do not know what i am doing wrong. but i have a feeling its the FW it has come with out of the box but i have not been able to find out any information about it as of yet.
i have found another post saying to flash it with a UK generic FW 2.3.2 .184
but im guessing i cannot downgrade to a FW that was not on the phone from packaging. although i may be wrong but that is usually the norm with this kind of thing.
any help in getting me in the right direction is greatly appreciated, and i hope to be able to help others in the future. yes it doesn't seem like i am of much help right now seeing as i can't even get it rooted yet. but i tend to pick up on things very fast. today i am having trouble getting in to it. but soon enough i will get there thank you to anyone who read this i know it is a little long but i wanted to make sure i gave as much information as possible to make sure i haven't left out something critical if i have left out anything let me know and once again thank you for taking the time to read this post and reply (if you did reply =] )
BUMP -- ?
anyone available who can help me out at all
i know im new to the forum/site but please don't let that stop any of you. if that is stopping you
ive done as much searching as i can and i keep drawing up blanks.
hey guys im new to the scene and trying to figure as much stuff out on my own as i can, usually i do a good job and don't need to ask for help. but i do when i have to, so the problem i am having is with a sony xperia play .
its my brothers phone and i was thinking about getting one but i want to "root" it and see whats what with it but i am trying to do so without unlocking the bootloader just incase anything goes wrong with it later so it remains under warranty. im coming from the iphone jail-breaking scene so this is a little different. but i want to give it a go. so i'm trying to root it i checked out this post
http://forum.xda-developers.com/show...1044765&page=1
i realize at the top of the post it says not all devices are supported because of new FW's does the FW i am on fall in this category?
i tried it with the 1.2.apk and the 1.1
im not sure why it is not working.
but i have a feeling its got something to do with the FW the phone has come with
its running 2.3.3
build number 3.0..1.A.0.145
model number r800i
kernal version 2.6.32.9-perf
i formatted the SD card before anything then after i installed gingerbreak to the phone itself. (also tried it without formatting it, i installed gingerbreak and tried to run it then and it didnt work so i rebooted formatted SD card and tried again and still nothing)
made sure the phone was set to be in USB debugging mode.
gingerbreak opens and has the options there but when i tap "root device" it just says "running exploit" ect on screen and nothing changes. on the post it says usually about 10 minutes but i read through it and one person said it worked for theirs but it took an hour and a half, but another said it took 3-5 minutes.
so i do not know what i am doing wrong. but i have a feeling its the FW it has come with out of the box but i have not been able to find out any information about it as of yet.
i have found another post saying to flash it with a UK generic FW 2.3.2 .184
but im guessing i cannot downgrade to a FW that was not on the phone from packaging. although i may be wrong but that is usually the norm with this kind of thing.
any help in getting me in the right direction is greatly appreciated, and i hope to be able to help others in the future. yes it doesn't seem like i am of much help right now seeing as i can't even get it rooted yet. but i tend to pick up on things very fast. today i am having trouble getting in to it. but soon enough i will get there thank you to anyone who read this i know it is a little long but i wanted to make sure i gave as much information as possible to make sure i haven't left out something critical if i have left out anything let me know and once again thank you for taking the time to read this post and reply (if you did reply =] )
-.- 88 views and not one reply....
anyway if anyone here can help me at all please do,
what use is knowledge if it isn't shared or spread.
none.
Today, I acquired a infuse 4g, off contract. I wanted to mess around with android, as my current phone is an iphone, and maybe switch over.
One of the first things I tried to do was tether my iphone to my infuse using mywi. I soon discovered android doesn't work with ad hoc networks. I googled a couple fixes, and decided to try my hand. I have never touched android before. I found this thing that said I could. So I went for it. After reading a few guides, I decided the first step was to root it using superoneclick. That went fine. Then, I read the instructions and it told me to 'flash the zip file using a recovery rom' which was total gibberish to me. So I did some more googling and found a modified 3e recovery thing for the infuse. I used some file system app to put that where it was supposed to be, but then saw that I needed clockworkmod to be able to flash things. By this point I realized I was far, far over my head, but stupidly pressed on. At about the same time, I also extracted the zip file from exop.pro, and replaced the wpa file that existed already in system/bin with the one from the zip. I also booted into recovery mode, and tried to install clockwork mod, which failed even though as far as I can see. Now, when I turn my phone on, everything is ok except that it can't scan for wifi. I assume this is because I ****ed with the wifi file. I've basically decided to give up at this point, so please, just tell me how to made it work again and I'll promise to not **** with it anymore. Also, I neglected to make a backup. Stupid, but I didn't know how and didn't want to go through another huge thing.
tl;dr
I tried to make it so I could connect to ad hoc networks on my infuse 4g and ended up destroying my wda_supplicant file in system/bin (i think) and
Google the original file you replaced, ' wpa supplicant file download for infuse 4g'. Next time save a copy or backup of whatever your doing.
Thanks, but I really have no idea what is what. Could you link me the right one? I'm sorry that I'm so useless.
Itaer said:
Thanks, but I really have no idea what is what. Could you link me the right one? I'm sorry that I'm so useless.
Click to expand...
Click to collapse
this was your problem the first time... you need to read and study before you just start flashing things to your phone man. haha... us linking you somewhere will not help you figure that part out... and its an important part of tinkering with these phones in the way you are trying to.
rid yourself of the apple mentality where everything is spoon fed.
moving on, however, do what the guy previous to me said... find that file you downloaded. and do some reading, watch some instructional videos, focus on just rooting the phone properly for now. do that, then read, watch, ask questions like you are doing when you need to, then proceed.
read comments and stuff in forums about the ROMs you are flashing, what kind of problems do they have, what recovery is recommended for that particular ROM, stuff like that. just READ everything and anything you can about what you are doing....
the company that made your newly found OS has a nice little search engine called google... and it works pretty well if you know how to use it i'll keep an eye on this thread for you as others are probably doing so we can provide you with whatever answers you might need. good luck!
a good rule of thumb when flashing hax0red software to these phones is when something ****s up, 9/10 times it's just a little tiny thing you missed or did during the install yourself... so back to square one, and pay close attention to detail. these phones can be a little touchy when flashing ROMs if you are not doing it exactly they way it is recommended.
perfect example of this: when i had my samsung moment... when i converted from 2.1 OS to 2.2... for some odd reason i would ALWAYS have to flash a little script zip to wipe the 2.1 data from the device before flashing the 2.2 zipped ROM to the phone... the 2.2 ROM was supposed to do this and take care of it completely for me, but even though it did, the only way it would work properly every time i was going from 2.1 to 2.2 was to flash that zip beforehand...
hope that long rant provided some useful insight
Thanks.
But I have read the instructions on the stuff I'm trying to do, several times, and like I said, I'm more confused that I was at first.
I'm just not willing to break it any further.
So basically what I'm wondering now is, how do I put everything back to how it should be. Is there a way? Like, is there a way to load the original software back? I don't think restoring it to factory settings would fix what I did, but tell me if I'm wrong.
I just want everything back to normal.
Please.
Edit: I know it seems like I'm not doing anything to help myself, but I have a lot on my plate in life right now, and I also have absolutely no idea where to even start. Half of the terms you use mean nothing to me, and I'm just so overwhelmed.
I just want to know if there is some way to put it back to how it came out of the box.
Turns out that once the new wda_supplicant thing is ACTUALLY GRANTED PERMISSION TO EXECUTE, that everything works fine. Thanks guys
see... Knew you would figure it out man
Sent from my EVO3D using XDA App
I'm not new to android whatsoever.. I've just returned from an Iphone 4s cause i was missing the openess of android. Now.. i've pulled out my old Nexus S 4g, Updated it to 4.0.4 and i cant get it to connect to my computer for the life of me! tried 4 different cables, 5 different computers, every driver i could find and nothing. I've come to believe this is a software failure... All i need is root and i will be able to sleep at night. Could someone package up .zip to give root and twrp recovery that i could flash through stock recovery? I dont know else i could do to get root... but this problem is becoming quite annoying.
1. There is no way to package a zip to flash through stock recovery since it would have to be signed.
2.For someone who is "not new to android whatsoever" making 2 threads about the same topic 2 minutes apart isn't exactly acting the part.
Try this guide.
Actually you're wrong, On the Epic 4G someone did in fact manage to do so. And yeah since i'm not new to these forums i understand that stuff like this gets overlooked so i made two posts. Cry me a river.
BTW Thanks harb... but that would involve being able to connect to my PC. Which just is not possible right now.
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
robogoflow said:
Thats the Android Karma... it happens but a little advice.
If you can't connect to the computer then it might a hardware issue not software.
If getting root was that easy that you just had to flash a zip on stock then everyone would be doing it. And good luck getting root without unlocking your bootloader first. Not to be rude but the problem could possibly be between the computer and the chair.
Click to expand...
Click to collapse
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
Bro... Chill... They're just trying to help you out. There is NO way to to root your NS without a computer (currently. We are not Epic 4G owners here). You said you didn't use your NS since GB, SO during the time in between something could have happened to the hardware. Don't rule that out just yet. Your drivers might also be bad. Is this what migrating to iOS does to people? Makes them snobby and demand fixes to problems they can't figure out on their own? Don't hate on the XDA forums. If we're not helping you "hit the thanks button anyways, you ungrateful bastard" (XDA into video ). Anywho. Chill. Keep trying.
Nexus S (GSM i9020a)
Paranoid (14.a Hybrid - 4.0.4)
Matrix Kernel (CFS - 20.0)
Intellidemmand (800/100)
Live OC (105 - 800/1000)
Deep Idle (On - Noop)
BLX - 96 (Inverted Apps)
I am chill, i am just trying to describe what I've already done so maybe someone could suggest something else. And no what i meant is i downloaded the OTA on my computer than transferred it onto my Nexus through USB mount a couple of days ago so i know its not a hardware issue. Im not demanding fixes, just trying to see if anyone has done been able to figure this out yet as i know im not the only one with this issue. And there is a big problem w/ people on the XDA forums as a whole.. i am a little frustrated and just dont like when someone is telling me is a User issue when i have tried everything conceivable and know what i am doing.. Sorry if this offended you. and IOS is a good device.. its just like.. NWO they want to control everything haha. I'd rather be part of the rebel faction. even though i love my ipad XD
There is currently no way to root 4.0.4 without an unlocked bootloader (and no custom recovery), and the only way to get an unlocked bootloader is to either have root or plug it into the PC and unlock via fastboot. As such, you are stuck with sorting out drivers - despite how annoying they are.
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Harbb said:
The video i linked to above describes in detail (and through video) exactly how to sort out NS drivers on Windows machines as well as the required fastboot commands to get a custom recovery.
Click to expand...
Click to collapse
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
grumpySasquatch said:
Yes that is a good video, and does a job well done in describing on how to install drivers. My main issue is that my Computer(s) are'nt recognized my device at all... It doesn't show up as android device, or nexus s... but Unknown device. If i could figure this out i believe i could handle the rest.
Click to expand...
Click to collapse
Pretty sure that video describes that. You need to open up device manager, double click unknown device (while device is in fastboot), hit update driver and navigate to the provided drivers on the site. Watch it a few times, you'll figure it out.
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
d_phekt said:
Have you tried to install PDANet? I've read numerous times about it working wonders for users who have trouble with drivers. It has all of the necessary drivers built in.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
yes i second that,PDANet Drivers usually work across all devices you should try them.
Like ppl said before, try PdaNet drivers it might help.
thanks everyone, , but like i said i tried pretty much every driver you can find online. they will not install as my device comes up as "Unknown", i've literally tried every piece of literature on the web relating to this issue... at this point i'm just going to wait for the JB update and see what happens.
grumpySasquatch said:
It's ok, not rude. I understand what you are saying... but did you not read what i just said? somebody had accomplished this on the Epic 4G and i'm just trying to find someone who has done it with the NS4G.. I've had 4 Android devices, rooted them all and been here since the beginning. It's not a hardware problem, it connected fine before when it was on gingerbread... i downloaded the OTA ICS then flashed through stock recovery.. but if you read what i said in the first post this problem only occured AFTER updating. This is why i quit using XDA a long time ago, because people just post a bunch of useless information instead of trying to help... The problem is not me my friend, its the damned ICS update, i've read multiple posts all over the interweb w/ people who have had the same problem, yet no resolutions other than bending up the micro usb male piece on my phone which is not the problem as i said it was working fine before i updated. Have tried multiple samsung drivers, pda net, and Android SDK Drivers, multiple Cords from samsung, to htc, to blackberry and palm pre and even a nokia one now. and 5 different computers... so tell me smart guy, what would you do?
Click to expand...
Click to collapse
So the ICS update makes you unable to boot to fastboot and makes your device unable to be recognized by your computer from there?
That's a new one. As far as I know, "Unknown device" is actually your device being recognized, just the driver doesn't get installed correctly.
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
polobunny said:
Have you tried manually specifying which driver to install and selecting the PDA Net driver? Look at Harbb's last post.
Have you went as far as editing the drivers inf to match your hardware ID? I know I had to do that way back when the PDA net drivers weren't even available.
'til then, user error.
Click to expand...
Click to collapse
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Epic 4G could do this in FROYO... It was patched by google in 2.3+. Do you want an app to secretly root you and install malware?
Sent from my Samsung Epic 4G using Tapatalk 2
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Well it is going to be basically one of two things.
1. Is user error of some sort. That is what people have been trying to help with.
2. Is hardware issue that no one can help you with of course. Or some software issue causing it to not show up for who knows what reason. Neither of which folks can help with since a computer is not seeing it. So they revert back to what they can. Point 1
When you asked a question like is there a zip that you can flash in stock recovery to give you root or custom recovery that also doesn't help your cause for people assuming user error.
The one other thing you can try is download mode and Odin.
grumpySasquatch said:
I swear you people don't listen, look i did everything in the video exact when i try to manually specify the driver it comes back saying that the folder you specified doesn't contain a compatible driver for your device... I'm not an imbecile and know how to follow instructions on a video. I know most people skip research cause they're too lazy to figure it out themselves... i posted on here as a last resort and feel like people are telling me what i already know then telling me its my fault, ridiculous. if you guys are just going to repeat what the last five people have said instead of trying to offer a new soloution then why even bother posting?
Click to expand...
Click to collapse
Cool. Trash your Nexus S, clearly broken.
Edit: That's nice of you albundy, but Mr grumpySasquatch (fitting name eh?) has tried everything, including modding the drivers inf. His Nexus S is broken beyond repair, also the first one we've ever seen that won't adb but works fine for USB mounting. *chuckle*
OK, My first attempt at messing with the firmware on an Android phone resulted in dismal failure and a dead phone..
Here's the scenario as events unfolded..
Bought an unlocked Galaxy S 4G
Trying to connect my phone to my PC resulted in dismal failure, wondered if it might be a dodgy firmware someone had installed.
*#2663# to update the TSP firmware. This just hung on the updating screen. Eventually the battery gave out. (Don't ask me why I was updating the Touch Screen Panel Firmware, I don't know.. I was fiddling. )
Recharged the battery and rebooted the phone.. Menu and Back buttons on touch pannel light but don't work.
Searched this forum and many others, seems to be a common problem but no clues as to how to resolve.
So I downloaded Odin 307 and the USB drivers, put phone in download mode, installed the following via Odin
CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar
SGH-T959V-CSC-TMB-VIBRANTP.tar
T959VUVKG4-Phone-CL1037720.tar
Worked fine, but didn't fix the issue with the TSP.
Somewhere I read that maybe it was partition corruption, so I decided to repartition. Ticked the "Repartition" box and used Hawk_Sidekick_VibrantPlus_831.pit (All four of these came as a package I found linked to on this site somewhere.) Odin said it was ok, but now I can't even power the phone on. Screen stays blank. Computer does not recognise USB device. Odin doesn't see it. It seems to be dead.
So.. Is there a rescue remedy from this scenario, or do I use this piece of glass and electronics to wedge my door open?
Please help I'm not going to pretend I knew what I was doing, but I'd like to unbrick this thing so I can at least make phone calls on it and send emails to people saying what a plonker I've been..
Thanks. :crying:
Do you have a T959V or T959 ?
Check under your battery.
Sent from my SGH-T959V using xda premium
T959V
No, I've not tried that. I'll give it a go.
The Heimdall One Click has saved my phone quite a few times, it's simple and effective! Let us know how it goes!
Sent from my Illūsîøn'd Galaxy S³
Ok, so I managed to get it into Download mode and reflashed it in Odin. I'm going to have a go with "oneclick" and see what happens, but at this point the only outstanding thing to fix is the TSP, which is still kaput. (Maybe one click will fix that) I've searched and searched on this forum, there's a whole bunch of dead threads where people have killed their TSP, and no resulting fixes posted. If anyone has any ideas, its would be great if you could post them, because at the moment, "menu" and "back" are still U/S.
Thanks for your help so far. If I get a solution, I'll post it here, I hate abandoned threads where people leech solutions to their probems and don't give feedback.
OK, So I tried this : http://forum.xda-developers.com/showpost.php?p=23121150&postcount=12&nocache=1&z=6720291850525859
No luck..
Next thing to try is an older version of the O/S, apparently if I put on then it downgrades one of the firmware, and running the update again fixes the issue. (On can only hope.. Now I gotta go see if I can find an older version of the OS and try this http://forum.xda-developers.com/showpost.php?p=21987511&postcount=9
:fingers-crossed:
Oh well.. On the plus side, I bought this little cheap phone to play around and learn on.. I seem to be doing just that. :cyclops: