Related
So I have an interesting little problem.
A few days ago after flashing Infinity ROM i noticed that when I plug my phone into my computer by USB, instead of reading the device correctly and matching/installing drivers I get an error message that says "USB device has malfunctioned" and is not recognized. This is a problem because I can no longer use ODIN to flash anything, it simply does not recognize my phone.
I have attempted to troubleshoot the problem myself by replacing the usb cable, uninstalling / reinstalling the drivers, resetting data and caches on my phone, using different computers etc.. So far nothing as helped. I would go so far as to guess that the USB controller in my phone is malfunctioning, but I can still charge my phone.
So I called verizon because my phone is still under warranty and they are going to ship me a replacement, so now my problem becomes how do I get back to stock or anything resembling stock so I don't void my warranty when I send this one back in.. remember I cannot use ODIN, and I am currently on the ext4 file system. Someone even suggested purposely bricking my phone, although I'm not sure how i would even pull that off. Thoughts? I'm still open to troubleshooting if anybody has any ideas.
Any ideas or help would be GREATLY appreciated!! Thanks!
In Summary:
Summary for those who think the first post was tfltr..
--Computer won't recognize phone through USB; device not recognized
--Phone will still charge but only with certain cords??
--Have troubleshooted through XDA boardsn
--Waiting on a replacement from Verizon
--Need to get phone to stock or close to stock for when I send it back in so i do not void warranty
--Is there a way to zip flash stock, even though I am on ext4 ow??
--If not, should I just brick my phone and then send it in?
Thanks bros!
If you get into download mode, your phone should be fine. If you get into download mode, go ahead and make sure everything else works. Use USB ports on the back of the computer, and try different ports. Try different cables. Try reinstalling drivers.
Sent from my SCH-I510 using XDA App
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Bleh..
xdadevnube said:
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Thanks for the response, but I have tried several official verizon USB cables to no avail. I just received the replacement charge which works on the same computer port and with the same cable that was definitely not working with the old phone. I will try compressed air when I get home later.
Does anybody know what would happen if I attempted to flash a stock recovery image with RFS as a filesystem through CWM, on the phone which is currently running an EXT4 filesystem? Would I brick it?
I'm not sure, but that seems like a poor way to going back to stock.
Just use the stock ODIN images. They will take care of all your needs. I've used them on multiple occassions.
Format your SD card first so that Verizon doesn't know you were rooted, etc. I usually do this through USB mass storage when its connected to the computer, but since you probably can't get it through the computer, either pop in your SD card into your other phone and do it through mass storage or simply use a memory card reader. I format with FAT32 /w 32KB block size.
Then just ODIN the stock recovery image and there you go.
*EDIT* der, I just realized you can't get the USB to work. This is a question for somebody who knows more than I do!
I'm not sure if this is possible with that rom(doubtful) but try disabling lagfix by creating a file on your sdcard inside the Voodoo folder, named "disable-lagfix"(may not even be a folder for this). Reboot. If you hear the voice again maybe it worked.
Does Imo kernal support reverting? If the above doesn't work(or try this first) flash the Imo 4.0 Kernel and try reverting. NOT sure if that kernel is compatible. Try all this at your own risk.
then cwm flash this:
http://forum.xda-developers.com/showthread.php?t=1108115&highlight=cwm
So here's a doozy. First, some background. During a routine update to a new version of my favorite rom, IMEI data got borked. My backup was apparently incomplete, so couldn't restore it that way. My phone has been unable to connect a computer via usb in more than a charging capacity for a few months, so any pc-based tools like ODIN or QPST were out of the question. Only hope was to go back to a rooted stock rom and try the dialer solution. So I try flashing root66 via Mobile ODIN. Note that this overwrites CWM to the stock recovery, in addition to overwriting pretty much everything else. For whatever reason, the OS is now borked. Can't get past the Samsung GSIII screen. I can still reach Download Mode and Recovery, though. However, as mentioned before, ODIN is not an option because no computer can see my device over USB. The recovery is now the stock recovery, so the only thing it will recognize is a signed update.zip from Verizon herself. Anything else I try to flash from external SD gets the whole signature verification error.
To sum:
The Problem
Need to get to a working OS. This likely needs to be stock.
Complications and Constraints
ODIN is not an option, nor is any other pc-based or usb-based tool.
I'm stuck with the stock recovery, which requires signature verification.
Theorized Solutions
I could either somehow flash CWM via signed zip file from stock recovery (don't know if this exists, if it does I haven't been able to find it), or,
I could flash a signed OTA zip, like what would arrive on the phone from Verizon. I've been having a lot of trouble finding one of these, since everyone and their grandmother seems to want to use ODIN to flash leaked OTAs. I'm thinking that of the OTAs, the initial upgrade to JB is probably my best bet, since it likely replaced more of the system than the other OTAs. I'm more than open to suggestions, though.
Thoughts?
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset was the first thing I tried. No go. I've tried every option available in the stock recovery, with no success. Gotta say, not really fond of this whole stock recovery thing. Fairly useless.
I haven't had usb to pc access ever since I played Ingress in a snowstorm a few months ago and some moisture got into the charging port, and I didn't properly dry it out. There's a little bit of corrosion in there now. It still charges fine most of the time (I'm sure not as well or as consistently as when it was new), but it can't connect to the computer in more than a charging capacity. I've tested a large variety of usb cables, most of which worked before the snowstorm, and none give me pc access. Some give me pc access for a few seconds, but none give a connection that's stable enough to run ODIN or QPST or the like.
I should note that I have a microSD to SD adapter, so I can still move files to and from my external SD card. Anything available on the internet can make its way onto my SD card so long as it's 7.96 Gb or smaller.
EDIT: I should clarify that I *did* have usb to pc access before the snowstorm. Samsung drivers worked fine, etc, the typical file transfers over usb worked fine, adb worked fine, etc.
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
adiv.paradise said:
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
Click to expand...
Click to collapse
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
prdog1 said:
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
Click to expand...
Click to collapse
Some phone is bricked that not recognize the phone on device manager and won't charge too.
tomy1986.nt said:
Some phone is bricked that not recognize the phone on device manager and won't charge too.
Click to expand...
Click to collapse
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
prdog1 said:
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
Click to expand...
Click to collapse
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
tomy1986.nt said:
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
Click to expand...
Click to collapse
If a device can boot to recovery or download or if it charges or is detected when connected to PC then it isn't truly bricked, it's only softbricked. A truly bricked device will not charge, has no LED when connected to PC, can't be detected by PC in any kind of way, will not boot to recovery or download mode and will not power on in any way. This is actually called a "hardbrick".
Sent from my SM-S903VL using Tapatalk
Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.
It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.
berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.
berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.
Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea
Hey guys,
I have an HTC One XL with TWRP and Pac rom's 4.4.4 and about a week ago my touch went out. Hoping it was the digitizer, I got one but that wasn't it. I believe it's the mainboard since it doesn't even work in recovery mode.
Well anyway, I got a new phone, LG G flex, and I would really like my data out of the one X. (Pics, messages, etc)
Is there any way to take it out not having to use the touch or the soft buttons?
And I know it's been asked before but I tried the similars and got nothing.
Theres numerous remote control apps in the app store that will let you remotely control your android device from a pc eitger wirelessly or over usb. Also, if you just want to get data off there's just using the usb cable to access the phone storage.
Web key app may be worth a try.
Sent from my Nexus 7 using Tapatalk
The latest versions of TWRP are MTP enabled, so if you can flash that and then connect the phone to your PC while booted into recovery it'll be as simple as using Windows Explorer to copy your data across.
Transmitted via Bacon
I'm gonna bring this up again since last time produced no results.
I can't instal softwares without touch. But that TWRP option seemed viable.
Can someone elaborate on that?
Put the phone into fastboot mode, unlock the bootloader (if it isn't already), flash TWRP recovery, boot into TWRP recovery, connect to PC.
Transmitted via Bacon
timmaaa said:
The latest versions of TWRP are MTP enabled, so if you can flash that and then connect the phone to your PC while booted into recovery it'll be as simple as using Windows Explorer to copy your data across.
Transmitted via Bacon
Click to expand...
Click to collapse
I have TWRP installed on my GS5. I can't see my screen so I think I've booted to it and it's plugged in, but I'm not getting my usb connection. Could you tell me the sequence of volume keys to press to mount MTP? Or why isn't it happening automatically?
Hi,
my PH-1 has a waterdamaged display, so i bought a Inspira Hdmi Adapter to rescue my Data.
Unfortunatly i´ve installed the 8.0 Beta and the Hdmi adapter only works on 7.1.1 or 8.1.
Any suggestions to up- or downgrade my system without Display?
Rough.. I would assume the only way, would be to update it to the beta 8.1 using the back to stock zip Blek has graciously posted in the development and ROM section for our PH-1.
If you can get the device in BL mode, and flash that, perhaps you can leech the data after it boots up, mind you that's gonna be a bit hard without a display, especially since at default the device uses USB charging instead of MTP..
MoistPicklez said:
Rough.. I would assume the only way, would be to update it to the beta 8.1 using the back to stock zip Blek has graciously posted in the development and ROM section for our PH-1.
If you can get the device in BL mode, and flash that, perhaps you can leech the data after it boots up, mind you that's gonna be a bit hard without a display, especially since at default the device uses USB charging instead of MTP..
Click to expand...
Click to collapse
couldn't you just flash twrp via fastboot
and go into recovery that way, and twrp is automatically set to connect mtp..
although might be an issue if you're not oem unlocked.
Nothing worked.
I can access the phone by fastboot but USB debugging is not enabled.
Sam_11 said:
Nothing worked.
I can access the phone by fastboot but USB debugging is not enabled.
Click to expand...
Click to collapse
is the screen totally black?
Yes, there are many vertical stripes in black/black, backlight is working.
I´ve disassembled the display and orderd me a defect PH-1 with working lcd, this is the last try.