so i recently came across a used Infuse (at&t model) from a friend, and wanted to do my part on fixing it up from the way he had it.
that meaning of course, flashing a new version, rooting, the basic good stuff we all love to do.
to change to my plan from his, which he didn't have it running under a contract or anything, was slap my SIM card in, and tweaked the APN settings a bit
to work with my Straight Talk plan. it's worked flawlessly and the speeds are way better than what my modded A953 can push through.
as i plug it into my laptop, it reads it can't be recognized and will only charge. not a problem. i Google how to fix this and to try workarounds.
nothing seems to work, and i'm stuck at the rooting process. after rooting, i can workaround to actually flashing and whatnot.
-i've tried Odin and a few other similar programs listed, but need Mass Storage/Download Mode and actual connection to work properly.
-z4root and Gingerbreak, only lag and freeze up my device, causing it to reset/restart with no changes.
-tried using 5 other USB wires, all act the same way.
-won't be recognized by other PCs/laptops, not even my PS3.
-uninstalling and reinstalling the Samsung drivers didn't help.
i've been using it as-is with barely any issues, but the feel of being held back of great roms and goodies.. it's almost disappointing.
this is by far the best phone i've been able to get my hands on and i just want it to work 100%, my way.
so my question is this; are there any other ways to root this Infuse without having to buy a whole new device or USB port/piece for it?
kind of running low on funds due to real life issues and such, so i have close to nothing to spend.
any other root apk's i could try other than what was listed above? any help is greatly appreciated.
Try a dab of alcohol and toothpicks to clean the contacts in the phone. Then try a different 2 or 3 cables. Some cables don't contact correctly. Some don't have data capabilities. Depends on your cables. Also try pushing the cable up firmly or down firmly to ensure contact.
Don't panic till you have done all this.
Sent from my SGH-I997 using xda app-developers app
hi..
after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.
i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.
Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.
Let me know if the above works (battery pull).
I had this issue too, didn't realize it until I tried updating different roms...
I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.
I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.
I also updated to the latest CWM per OmniRom thread in development forum.
I trust Magamo, though, in providing the right diagnosis and solution.
mod please delete
REV3NT3CH said:
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder
Edit: like this for example https://github.com/TeamApexQ/androi...mmit/b9d389cca9f241d778f1d8206195e16dfcb3dee8
Click to expand...
Click to collapse
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.
This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.
Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.
Surprisingly, pulling the battery fixed the problem!
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Autolooper said:
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Click to expand...
Click to collapse
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
xob3444 said:
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
Click to expand...
Click to collapse
Android 4.0+ no longer supports USB Mass Storage out of the box for the internal storage, and neither do any of the custom images that I can think of. MTP is the answer here. The fact that you are getting MTP means that the device is talking over USB, which means that you are not suffering from the problem described in this thread.
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
rice923 said:
I'm currently on a Moto x (2013), coming from a Galaxy Nexus. I switched because I needed a faster phone, and the GN hardware is just too dated. The moto x seemed perfect, until I found out I can't tether, root, or unlock the bootloader to save my life.
That being said, I'm in the market for a Verizon S3, which will likely already have 4.4.2 installed. My main concern is root access and native hotspot tethering (unlimited data). The following are what I have found thus far:
1) root: http://www.andromods.com/root-unlock/sch-i535-vzw-galaxy-s3-kitkat-rooted-nc1-ota.html
2) tethering: https://www.youtube.com/watch?v=PxBRrsucdLo <---- the guy who created the vid doesn't have VZN, so was hoping someone here can verify if that works.
3) bootloader: I found nothing on unlocking a VZN bootloader, but this is the least of my concerns
4) ROM: http://forum.xda-developers.com/gal...nt/rom-superliterom-v1-0-i535vrudne1-t2805797
My assumption was always that an unlocked bootloader was necessary to flash ROMs through custom recoveries. I'm unfamiliar with safestrap, but I'm all in for a bit of reading and enlightening.
Again, I don't necessarily need a custom ROM or bootloader. My main concerns are still tethering (main priority) and root access (second priority)
Thanks all, and I definitely appreciate any help at all!
Click to expand...
Click to collapse
Root is still possible. Tethering *USED* to work on stock by using the FoxFi app. I haven't tested it in quite some time though. There's a limit for the free version, use it for testing though.
Sent from my SCH-I535 using XDA Free mobile app
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
rice923 said:
I actually made the jump already. Sending this from my s3, boot loader unlocked, twrp, and running cm11.
Thoroughly enjoying this! Tether is flawless too
Click to expand...
Click to collapse
Do tell how. Especially if you did start with a Verizon galaxy s3 sgh-i535 that was not rooted and was running on stock Verizon Android 4.4.2
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
rice923 said:
To clarify, I bought it set up this way. I knew clearly well that I wouldn't be able to get any of this with stock 4.4.2.
On the other hand though, the camera won't focus correctly when taking pics, and the charging is ridiculously slow. My only two complaints
Click to expand...
Click to collapse
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
I remember seeing you around MWs FML thread! 5.0 is looking decent over there, so I'm very happy for them.
If you get the chance, I'd definitely recommend CM11. It make me feel like I'm running a nexus device again, except significantly faster than the gnex with a better camera.
Regarding the charging speed, I don't think it's a kernel issue. With the phone plugged in, I keep getting notifications that it's being disconnectedAnd reconnected spontaneously. I've done some reading and and it seems there is a bit of oxidation or hardware issue within the charging port. The port also requires soldering of the mother board to change. I've resorted to ordering some qi chargers[emoji106]
As for the camera, this seems to be an old issue of cm11. I flashed a camera fix zip, but to no avail. The focus issue seems to be problematic only at macro distances though. I can't find a fix besides touching to focus prior to taking macro shots
Rushead said:
Hey Rice,
I'm still on the GNex, but my wife just offered up her old GS3. It's still on 4.1.2 unlocked, rooted. I'm working on bringing it up to speed...still reading....
P.S. Is there no kernel fast charge option?
Click to expand...
Click to collapse
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
ShapesBlue said:
With 4.4.2 if that's what your referring to you can't change the kernel like those of us who are unlocked
From my CM11 S3
Click to expand...
Click to collapse
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Rushead said:
No, it's 4.1.2 I put her on Andy bonestock years ago and never touched it again.
Click to expand...
Click to collapse
Then yes there are several kernel options for fast charge. I know of lean kernel and ktoonsez off hand that are
From my CM11 S3
Don't want to start a new thread even though the title is irrelevant at this point, but was hoping someone could chime in regarding the camera auto focus issue. The camera focuses beautifully when I touch the screen, or when I allow it to autofocus. When I proceed to take the pic, it will try to focus again and take the pic right as it's completely blurry. This happens on both the stock CM11 camera and google camera.
I tried to flash the zip mentioned here http://forum.cyanogenmod.org/topic/85493-camera-wont-focus-cm11/ and nothing has improved.
Does anyone have any insight about this? These symptoms are identical to what many have mentioned in the thread above, so this is certainly not an isolated incident. Thoughts or input?
Who reads titles anyway?
I flashed Slim, and messed around with the camera a little, but I had wifi issues and am in the process of flashing cm11 11-09.
On Slim, the camera seemed to work fine. I took some "macro-esque" shots of text that came out pretty good (at least as good as the GNex, if not better).
I'll let you know how it fares with cm11...
So far, camera FCs on hitting the "No Thanks" button for location reporting.
OK, Camera is now functional (probably didn't wait long enough for the phone to settle on initial setup). The quality is mediocre. I'm still messing with it and will report back.
switching phones, want to keep/root the old Galaxy s3 as a lab/toy
Have an old Verizon Galaxy S3. Just got a new TMo Sony Xperia Z3 (which I am liking so far).
Will soon disconnect my Verizon service. Would like to root the S3 and use it wifi only as a experiment/toy thing, since there's no trade in value (cracked screen).
Possible? Cyanogenmod recommended?
I'm a total n00b at all this, and would steer totally clear of it for my main driver. But since I don't really NEED this phone anymore, thought this would be a safe way to dip my toes in. If I brick it in the process, no great loss.
Any advice or links would be much appreciated. Definitely want it to keep working as a wifi device and not brick once I cancel my Verizon service. Would be cool to be able to play with some of the fringier apps that require root. Those are my only requirements. Camera, cell service, etc all unnecessary. But do need wifi and don't want to create a big vulnerability to the rest of my home wifi network from this device once I'm done.
Thanks again!
evbb, depending on your current OS version, you might be able to root. If you are on the most current official OS, then you will likely just be staying with that.
Rushead, any update on how CM11 11-09 is going? If everything looks stable, I think I'll make the jump to that build.
Update about my charging times: The phone seems to charge at a normal rate if I use a 12V car charger made by Griffin (item does not specify amperage). I don't believe amperage has antying to do with my situation, as I've been yielding miserably slow charge times with the Nexus 7 (2.1 amp) charger. The phone is also very picky with cables. I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
When my wife had the phone it was extremely loose as far as cables went. I could use virtually any cable whereas my GNex is super picky.
I haven't had much time to mess with the camera yet. I'm using it as a WiFi device, too, so I can't comment on data, signal, etc. But so far it seems pretty stable. The battery drain is excessive imo. On standby for most of the day, battery was dead by 10pm. That's factory kernel.
For those looking for a decent tethering app there's one on sale, free on the Amazon app store. Easy Tether is the name of the app. It's free 11/14 & 11/15
http://www.amazon.com/s/ref=amb_lin...d_t=101&pf_rd_p=1973721462&pf_rd_i=2350149011
From my CM11 S3
rice923 said:
I've used 4 different AC adapters so far in different combinations with 4 different USB cables. I don't know what to think of my charging situation anymore...
Click to expand...
Click to collapse
You should try a very specific type of cable. The problem is the fact that you use a data cable at all. What I use is an aftermarket universal USB cable and it has the detachable tip for other phones. What this does is force the phone in "Charging (AC)" mode no matter what charger you use. Attached are 2 pictures to help identify exactly the kind of cable to solve your issue. I can charge my 7000 mah battery attached to my phone in 5 - 6 hours. A 2100 ah battery should be 1 - 2 hours with this.
Sent from my SCH-I535 using XDA Free mobile app
Some chargers identify as a USB hub rather than an AC adapter, and others do not. This is why on some chargers, it still charges slow. If ever the phone thinks it is on USB, it will not allow more than 650mah to pass through the cable. So even if you had a 10amp charger, it would not use that much if it identified as a hub.
Using the cable I mentioned removes the ability for any charger to send the identifier info to the phone. Reason? You are missing the data+/- cables that data is transmitted through. Only the +/-5v wires remain.
Sent from my SCH-I535 using XDA Free mobile app
But why would the phone have a constant disconnection and reconnection while being plugged in? That's the part that confuses me.
Regardless, I just received my qi charge in the mail! It's been pretty nice so far! I'm happy to answer any questions about it if anyone is interested
Rushead, wanted to give you a heads-up about the latest CM11 build I used. I clean flashed 11-15 and everything was great except for the camera, which consistently gave me a "cannot connect to camera" error. Otherwise, it seemed like a great build with some great options. I gave up and clean flashed 01-15. Camera is all great except for the autofocus issue mentioned before. GPS lock is great, and battery life is loads better than my GNex days.
Regarding my qi chargers, I am pulling a net positive charge of 315mA on my house charger (Nexus 7 2.1amp AC adapter). This is with the phone turned on, connected to Wi-Fi, screen off, and doing nothing.
My car qi charger is doing about the same. I ran the GPS with screen on (auto brightness) and the charger only charged the phone 3% in 2 hours with screen on and GPS running the whole time. I might switch the DC socket to the included one to see if I get better results.
Hi, I bought a used Verizon Note Pro 12.2 SM-P905V and when I got it, noticed that the wifi is very flaky. Initially, it connected to my router fine but took 9 hours to load 120 apps when I signed in to Play using my normal Google account. So I did a factory reset, and then it wouldn't see my router at all. Restart router, factory reset device, no dice.
In the notification shade, wifi icon is always green as if it's on, but when I go into settings, the toggle is off. When I slide it to on, it turns gray and after a minute or so goes back to off. Multiple hard resets, still the same issue. Occasionally, it will "see" the routers, but this only lasts for a few seconds and then they are gone.
So I decided to flash the firmware. I did not complete another factory restore before I embarked on this, but had only just gone through the initial language screens and signed in on the tablet with a brand new Gmail account that had nothing on it. So I downloaded official 5.1.1 ROM from Sammobile, installed device drivers, installed Odin, (followed some great instructions found on XDA, thanks), got the tablet into download mode, connected to laptop and Odin on my laptop showed connection was live and it began to do it's thing. So I left it alone for 30 minutes and when I came back, Odin read "all done!" (or something similar) highlighted in green , and the tablet had restarted, so I assumed all is good.
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!
Wifi circuit has many components on mainboard and I believe it's beyond abilities of most users even professionals as you cannot find components and schematic to fix them.
Your best source is looking for this tablet with a broken LCD like this one:
http://www.ebay.com/itm/172145691764?_trksid=p2060353.m1438.l2649&ssPageName=STRK:MEBIDX:IT
http://www.ebay.com/itm/Samsung-Gal...069075?hash=item1a15927393:g:D8MAAOSwbYZXZKDb
If you don't have the need to LTE connection, Note Pro wifi mainboard SM-P900 also fit but you need rear camera for SM-P900 as rear camera of LTE won't work in Wif mainboard.
Any LTE Note Pro 12.2 like P907T( Tmobile) P907A ( AT&T ) mainboard will fit to P905V as they are exactly the same mainboard, except firmware, bootloader and software loaded into it.
I swapped a SM-P907A mainboard to a SM-P905V tablet, it works as an AT&T tablet because the software is for AT&T.
I purchased a verizon note pro 12.2 SM-P905V refurbished from groupon last October. For the last few months the wifi on the tablet has been very flaky. I have a number of devices and only this one frequently drops connection. I never upgraded from kitkat I and was hoping that this issue was software related. Seeing that moransw is experiencing the same problem with this same model but is trying to get back to sock kitkat gives me concern that a software update will not resolve the problem. The other problem I've been having lately is that the device no longer recognizes the stock charger, and will now only charge painfully slow. I've tried a different charge cable from a samsung s6 to no avail. Is the SM-P905V a lemon?
You should use this one to test your charger and usb cable
http://m.ebay.com/sch/i.html?_nkw=u....Xusb+voltage+current&sqp=usb+voltage+current
If you're using correct cable and charger, current should be 1.7 A and voltage should be 5.3 V
Test with known working cable and charger, if nothing is different you should consider to buy new usb flex charging port, around $10.
These basic steps you should do first as nobody can give exactly an answer with many unknowns. It happens to many used tablets, not just this model.
These basic troubleshootings are easy done for simple problem of bad cable, charger or USB port
Try them first then post your results if you need more help for further steps
moransw said:
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!
Click to expand...
Click to collapse
1) I am using stock kitkat rooted and I was experiencing the same issue
2) I found this thread regarding our tablet that seems to suggest a bug with wifi if you are using a Bluetooth device
http://forum.xda-developers.com/galaxy-note-pro-12/help/wifi-disconnects-bluetooth-device-t2851406
I was streaming audio through bluetooth to my home surround system, I disabled the bluetooth radio and I haven't had an issue with wifi since. I now use chromcast to stream audio through my surround sound.
Alright, so here's the scenario: I have a Verizon Google Pixel that I have unlocked the bootloader, rooted and is currently on Android 7.1.1. I recently lost the ability to have it quick charge even though when the original charger is connected it says "charging rapidly". I have tried 5 different chargers and use Ampere on my phone to test the charger and my roomate has a Pixel with the same app and he gets way higher results than I do. I'm just getting regular USB speed, not Qualcomm 2.0 speed.
Anyway, I don't have a home ISP, I have the original $20 unlimited data plan and went through this procedure to get hotspot to work without checking with Verizon so I get it free:
1.) androiding.how/unlock-bootloader-verizon-pixel-and-pixel-xl/
2.) androiding.how/google-pixel-xl-twrp-recovery/
3.) androiding.how/root-pixel-xl-magisk/
4.) androiding.how/enable-wifi-hotspot-tethering-pixel-and-pixel-xl-verizon-sprint-others/
So, I've tried rebooting etc and can't come up with a solution to fix it. I have an extended warranty on my phone, through Verizon, and can get a new phone. I am wondering if I get the new phone if I can unlock the bootloader and if the above procedure will work or if there are any other methods to do so cause having hotspot, free, is critically important to me.
I would just prefer to fix the quick charging on my phone, but otherwise I want to know if the above process will work for a new Verizon Pixel, possibly already loaded with 8.1.
Thanks for any help, I appreciate it.