I have been trying to root my gf's new epic 4G and after a few complications I am pretty sure I am facing the same issue I had with my Evo.
There were the instructions I used to fix it on the Evo: http://forum.xda-developers.com/showthread.php?t=695243
Would this same fix work on the Epic or would changes need to be made? Thank you in advance.
Idk and this belongs in the q and a form
Sent from my SPH-D700 using XDA App
What are you developing? Please post things like this in the q & a.thank you.
Idk what you did but I have never heard of those issues with this phone. Mod please move this tread.
Sent from my SPH-D700 using XDA App
For further clarification:
I was using the one click root after connecting the phone to the computer with win7 and getting drivers installed so that it was visible through adb with "adb devices". After beginning the rooting process it says it should take about 2 minutes but if it takes more than 5 to reboot the phone. After 20 minutes I rebooted the phone but now when it is plugged into the computer I go into devices manager and the phone no longer shows up with adb and mass storage, it shows up as a non-functioning device. When trying to update the usb drivers it says that they are already current and that the device is not functioning properly. After rebooting the computer and the phone I tried to connect it with adb and it identifies the device but shows it as offline no matter how many times I try killing or restarting the adb server. The only solution I have found to this issue once it happens is to go into recovery and wipe everything out and start from scratch.
After some searching it is clear there are tons of users out there that have apparently run into this same situation. Unfortunately all of the recommendations are "you need to update the usb driver" or "restart adb" and after the OP says that doesnt help then the thread goes dead and the OP typically resorts to using an sd card reader on their computer. This issue plagued the Evo for a long time until someone figured out that the recovery was setting the Evo into USB debugmode and fixed the issues for everyone with the above post. I am pretty android savvy and I am friends with a couple developers that I asked first but they said they werent sure and that I should ask the devs of the Epic. If I am in error mods please move or delete this post.
Related
So ADB was working (I thought?) and ADB recognizes my phone when I just plug it in, but when I go to do the steps for rooting, it no longer recognizes it.
I got it to say offline ONCE after the loop, but the on the unplug re-plug, it went away. I'm bummed...
cmon now http://forum.xda-developers.com/showthread.php?t=703429
You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!
Can A Mod PLease Lock this thread, thee is Multi Post in Multi threads Reading this!
The Answer you are Looking for.... UN-PLug the the USB wait 5 second if that and plug it back into the Phone..
I did that, on several different occasions, but alright, will try again. Thanks.
missxoash said:
You must have misread my post. I've looked thoroughly through that post, actually.
What I am needing help with is after that loop, going from offline in ADB to recovery...
thanks!
Click to expand...
Click to collapse
ITs not recognizing your phone when in recovery thought correct? if so thats the same thing discussed there. If it did recognize it as offline in recovery then do as eugene said.
missxoash said:
I did that, on several different occasions, but alright, will try again. Thanks.
Click to expand...
Click to collapse
it needs to stick to offline, not just say it onec or twice. itll say offline many times not just once then disappear. Once it does it and sticks, it doesnt turn off, you dont need to rush and hit ctrl c
I'm having a issue that's somewhat related. I have a tmo mts3g and I had it rooted with no issues following the instructions provided in eugene's previous posts on the matter. Tmobile recently dropped a OTA update for 2.1 and it relocked my phone. Now that I'm trying to reroot it I'm having issues getting the phone to be adb online in recovery mode. I do adb reboot recovery and when it starts I have the loop going and I have no problem getting it to say "device offline" but when I unplug the device (no matter how long I wait) and plug it back in it still remains in "offline" status under adb devices. I've heard about driver issues and all kinds of other madness but I'm using the same computer that I used when I rooted it previously. My question is; is this something tmobile might have fixed in their ota update and am I just wasting my time continuing to try this method? If not i'm more than happy to continue to try but not if it's with no point.
Thing is you did the OTA update, so instead of following the old guide, you follow the one in the rom bible in the development section. Hope that helps.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Yeah, I found my way there eventually. I got it all straightened out and currently on Eugene's MyFroyo6 with no complaints. Thanks
Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?
I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.
Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?
Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????
Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.
Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.
When my phone is just sitting in bootloader, it is not recognized by adb devices.
You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.
gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.
Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore
Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly
Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?
Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.
Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.
Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
Okay first of all, let me start by saying this is my first post and I AM a noob, so be patient.
Okay, my problem is that I can't root my Sprint Samsung Intercept. I've tried SuperOneClick, Z4Root, Universal Androot, and some other one. NOTHING has worked. The SuperOneClick somewhat worked, it installed SuperUser but when I downloaded apps that require a root, they said my device isn't rooted.
I'm with Sprint and running 2.2.1.
Pease help because this is driving me crazy!!
i dont know how this stuff works either but my brother has that phone. it could be your usb isn't reading. or rather, your computer isn't recognizing the device. google samsung intercept usb and you'll see a lot of issues. this may not be your problem but its better to tell you just in case. so far for his cell phone, because he wants to tether it to his computer, so far nothing works. not downloading the right drivers. loading without debugging. mounting the sd card. thats one big solution that hasn't worked. i have high hopes for this other fix, to load samsung pc studio. New_PC_Studio_1.4.0.IL2_4.exe is the file. you can google and find it.
this site has some info. if it works and i remember to, ill repost and let you know.
en.kioskea (take out space, insert a dot)net/forum/affich-240949-samsung-sgh-f480-usb-driver-problem
hope this helps. if not then good luck. and heck if anyone else knows why exactly it does this and a real fix other than the whole disable usb debugger issue. then let me know. i even thought about trying to load the sdk for android to see if that would create some sort of connection with the phone and computer. thanks and take care
hope this helps
sdx-developers is the best place for intercept developement
http://forum.sdx-developers.com/int...ructions-on-rooting-spring-samsung-intercept/
follow the first step to get SWUpgrade setup (the rest is instructions for eclaire [pretty sure])
http://forum.sdx-developers.com/int...-2-2-(easy-root-via-swupgrade)-(battery-mod)/
flash this kernal with SWUpgrade and youll be rooted.
http://forum.sdx-developers.com/int...important-features-working!)-(updated-11311)/
i assume youll be wanting a recovery as well i recommend cm01 get the tar and flash it just like the kernal
intercept doesnt have many custom roms but there is tons of mods you can apply to the stock rom
I tried SWUpgrade and I bricked my last phone but it didn't matter because it was already defective.
Sent from my SPH-M910 using XDA App
did you patch SWUpgrade? delete everything in the binary folder except the file you were trying to flash?
ive never had a problem with it. it even saved me from quite a few softbricks in the short time ive had my intercept.
I did everything the videos and forums said to do. When I did that I got a different kernal but I couldn't get any service, my phone would restart every 2-5 minutes, and it would randomly vibrate. Until I got another one. I finally got SuperOneClick to get passed the "waiting for device" stage and I supposedy rooted my phone, when I tried to install apps that required root access they said my device is not rooted.
Sent from my SPH-M910 using XDA App
Sorry to ask for help in this thread. But my work gave me a new razor and yesterday. It came preinstalled with jelly bean. I rooted it and installed safestrap. Went through multiple flashes with no problems. Last 1 I tried it got stuck at the fast boot. It says locked 0 battery okay. I've tried every remedy. I believe I have all the files on my computer to revert back I cannot figure out how to get ADB to recognize my command it keeps telling me that file or that system cannot be located maybe I'm working it wrong maybe I have the wrong information I really need to have this fixed by tomorrow morning if anybody can please help me either send me a private message or even call Maine just p.m. me for my number thanks sorry to take this thread hostage.
Sent from my Nexus 4 using xda premium
Well take it easy on you. For future reference, all questions and requests for help go in the q n a section. This section is for posting ROMs, kernel, mods, etc.. only. Anyway, you say that you cannot get your phone to be recognized through adb? Here are number of reasons why that might be.
1. You do not have the proper drivers installed. Install the drivers for this with the proper driver software for this phone.
2. The obvious reason is in order to use adb, your phone has to be booted on. (You can still access adb even if your stuck on boot animation) or have to be in recovery mode.
3. Make sure you have all the files in a folder you need to initiate adb commands: fastboot and a dB for example. You can get all these from downloading the SDK tool kit.
Now I do not know what remedies you have tried to restore it. But the first thing you should've done after you have installed safe strap was make a backup of your original ROM.
If all else fails, you will need to flash the jellybean stock firmware using rsd lite. Which of course requires you to have yih phone recognized by your. PC. Check to make sure it isn't your cord by hooking it up to another computer. Try swapping different cord too.
And moved...
see post 4
see post 4
see post 4
d802 int
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
kye1987 said:
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
Click to expand...
Click to collapse
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
XxZombiePikachu said:
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
Click to expand...
Click to collapse
Cheers I'll see if the supermarket has them at a half reasonable price, otherwise ebay has them for £1 delivered and I'll have to wait. Thanks for the reply and confirmation that would work though.