Two Questions
No mount option now. Does the phone automatically mount to a PC once updated JI6?
Use a mac and in order to connect need to turn USB debug on. Anyone know where they moved it to?
xda - This forum is awesome. Could not wait for the official update. Took me 10 minutes and phone is running great. My first use of Odin but went very smooth with following instructions provided here. Just wanted to say thanks to all..
Related
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.
I have tried several ways to get around this issue I'm facing. But I'm not able to get my device rooted. Whenever I connect to the PC using the USB cable with USB debugging enabled, it always detects as Portable Media Device. This just stops every process that is related to rooting. My device is running on 4.0.3 ICS for the moment and I very badly want to try the Jelly Bean version. Please help me in getting over this hurdle.
neoronin said:
I have tried several ways to get around this issue I'm facing. But I'm not able to get my device rooted. Whenever I connect to the PC using the USB cable with USB debugging enabled, it always detects as Portable Media Device. This just stops every process that is related to rooting. My device is running on 4.0.3 ICS for the moment and I very badly want to try the Jelly Bean version. Please help me in getting over this hurdle.
Click to expand...
Click to collapse
If that gives you trouble you are gonna be in hell. First you have to set up adb. I don't know if you need the ask. Then install easy root. After this use apxtool. To use this you need some other programs and then you can flash a rom. You need to root, then unlock bootloader. I can post later ALL the pages you are gonna need but still, a storm is coming...
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...
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
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.