yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] Scott_InAK:
Can use A Cooper USB Electric Outlet with S3 and S4

I saw this thread while trying to solve this very issue. I have the Cooper USB outlet and installed it thinking it would charge my phone and my wifes. It would charge her S3, but not my S3. She has the LTE version (SGH-I747) and I have the HSPA version (GT-I9300). Well I thought it would not charge my S3. After playing with it for a few minutes, I could get the charge light on the outlet to blink. No charging was happening as the charge light on the outlet would just blink and then stay off. On my wifes S3 I could plug it in it would start charging instantly.

After playing with my S3 and the cord (The same cord used for my wifes S3 as I had already tried numerous cords) I found I could slowly insert the micro usb end into my S3 and it would start charging. It was tricky, but after 30 minutes of wasted time, I got it to charge. I would have to ever so slowly plug it in, either at a sideways angle or at a slightly elevated angle. This was regardless of the usb cord used.

However my S3 died and I got an S4. Naturally my S4 would not charge just by plugging it in, but I tried the "slow insert" method, on both the micro USB side and the outlet side and both worked.

I am thinking there is some kind of tolerance issue surrounding the electrical connections. Sliding the USB connector in slowly at the outlet side, I beleive, would ground the connection first and then allow for charging, but this is where my knowledge of electricity starts to bad. That said it is possible to use the charge, but it is not plug and play.
[T-Mobile Samsung Galaxy S 4] DaMadOne:
I just picked up a couple of these for the kitchen to alleviate the eyesore of the wall warts and I can also confirm it charges everything I have thrown at it except my S4 (jfltezvw) =( I quickly found this post after googling it. I am currently doing some work on the phone now but I will attempt the super technical "plug it in slowly" later and see if it works =)

Has anyone had any luck with other brands? I find this REALLY odd.
[T-Mobile Samsung Galaxy S 4] maximus96:
just installed this same outlet, and sure enough it charges everything except the S4..."slow insert" doesn't seem to work...does anybody know of any other solutions besides not using it?
[T-Mobile Samsung Galaxy S 4] lovoltage:
wall charger option

I also have one of these outlet/usb from cooper that will not work with my s4.

Has anyone tried to use a DUAL POWER micro USB cord (like the ones that comes with the portable hard drives) to see if that would do the trick?

unfortunately, I do not have one of these cables, or I would try it myself.

Here's what I am thinking is happening...

The S4 is equipped with a smart charger that can trickle charge after a complete charge cycle.

When first connected, the s4 starts a trickle charge while it tests the battery for the charge cycle.

The cooper is equipped with a current limiter that shares power between the two outlets.

The cooper unit sees the trickle charge, and switches to a lower current setting for the slot with the s4 plugged in. reserving current for the empty outlet.

The s4 then tries to engage a fast charge, but cant due to the lack of current, and shuts down the charge circuit.

If a dual usb cord to micro usb cable was used, both outlets would be tied to the s4, and full power would be available to the s4 at all times.

Of course, without a cable myself, this is almost all conjecture on my part, and I could be just blowing smoke up my own arse, huh?

LoVoltage

EDIT: Of course, remember that the cable you use has to have the D+ jumper to signify the 2.1 amp availability. If you don't, the cable won't work. (Most dual port usb cables have this jumper already. so does the OEM samsung cable)
[T-Mobile Samsung Galaxy S 4] redneck_666:
Just installed one of these tonight. Specifically the Cooper TR7745/TR8245 15A/125V

I can charge my Note 2 (SGH-I317), Nexus 7 wifi, but not an Samsung Galaxy S4 (SGH-I337). Kinda weird.
[Samsung Galaxy Nexus] ok11:
Hi,

My friend has a 4.2.1 Yakju Gnex and I'm trying to update it to 4.2.2 or even 4.3 and neither OTAs work. It has never been rooted, so it's stock. I have followed numerous sites' instructions to adb sideload the ota and they transfer fine, but when it's about to verify and install, it aborts installation. I have tried everything and I'm stumped. I have read quite a few people who have encountered this problem, but haven't found anyone giving a solution to this problem. I have downloaded the OTA file many times and even from different sources, leading me to the same problem.

Does anyone know what I can do besides rooting it which I rather avoid.
[Samsung Galaxy Nexus] mrgnex:
What is everything? What exactly did you try? I suggest flashing the factory images via fastboot.

---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------

What is everything? What exactly did you try? I suggest flashing the factory images via fastboot.
[Samsung Galaxy Nexus] ok11:
By everything, I mean tinkering with settings like the verifying apps through adb in depeloper settings. Trying having the developer mode on and off. Dowloaded the ota file from different sources. Made sure my drivers were up to date. Anything i could do in order to get the ota installed without losing data.

flashing the factory image via fastboot would erase data, wouldn't it? I was hoping you had an answer to the problem of installation aborting which many people have experienced. Hoping to find out why it does that.
[Samsung Galaxy Nexus] hgmichna:
No OTA update from 4.2.1 to 4.2.2

Similar problem here. Galaxy Nexus came back from a repair and had been reset to an older Android version. The next day it received the OTA update to 4.2.1, which went through perfectly, without a hitch.

Since then—nothing. A week has passed without the next OTA update.

The phone is regularly in Wi-Fi range and should have no problem downloading OTA updates.

Does anybody have a clue whether it is normal that updates take that long? Or should I be worried and try to get the update another way?
[Samsung Galaxy Nexus] mrgnex:
You can flash the factory image via fastboot without losing data. I'm afraid you have to use google though because I don't know sure how. I thought by deleting userdata.img but I'm not completely sure.
[Samsung Galaxy Nexus] beekay201:
Remove "-w" from the 'fastboot -w update update-xxxxx.zip' command in the flash-all script.

a manta sent this.
[Samsung Galaxy Nexus] hgmichna:
Thanks for the good information! It may become very useful to me as well, once somebody answers my question or when I run out of patience.
[Samsung Galaxy Nexus] hgmichna:
I got another Galaxy Nexus now, again completely stock, unrooted, with Android 4.2.1. Does anybody here understand why it is not automatically getting an OTA update? It was in Wi-Fi range for several days, but no update.

This is unsettling. Is Google's updating service defective? Does anybody here have any idea how it is supposed to work?
[Samsung Galaxy Nexus] Zepius:
you need to read through this. i bet you do not have a firmware updated by google.

http://xdaforums.com/showthread.php?t=1728555

and no, the update service isnt defective as plenty of people have the OTA to 4.3.
[Samsung Galaxy Nexus] hgmichna:
Thanks, good reading. But this one is pure yakju, not even the boot loader is unlocked.

He, where's your logic, man? You mean, if 90 out of 100 people crossing the river are not eaten by crocodiles then the river must be safe?
[Samsung Galaxy Nexus] Zepius:
1) prove to me its pure yakju. give me a screenshot of your about phone.

2) considering you claim you're on 4.2.1 yakju, and pretty much every yakju device is now on 4.3, i doubt your claim that its pure yakju.
[Nexus 7 (2013) Q&A] xnifex:
So I've been trying to get tabletsms to pair with my phone but it keeps saying the pus notification test fails. Except if I try to pair it with the 2012 nexus 7 still running 4.2 it works. Has anyone else had luck getting it to work on 4.3?
[Nexus 7 (2013) Q&A] TADitto:
That was one of the first apps I installed on mine after unlocking and rooting. Haven't had a single problem with the app or sending and receiving messages. I have desksms install on my Note II as well as my laptop and had no issues during setup on any device.
[Nexus 7 (2013) Q&A] xnifex:
Hmm that's weird. I've tried reinstalling in both devices & that doesn't work.

Of course once I try reinstalling again it works. Yay!
[HTC One V] dlongnasty:
ok so i rooted my aunts one v cdma on VM because it was lagging so bad. didnt even think about checking radio and hboot to see if she had ran the ota because with my phone i have s-off and i can downgrade at will. anyway she did and i can get roms to boot with sick kernel but the Bluetooth will not work. i have read so many threads and i know its a kernel issue. my question is does anyone have a pure stock kernel that is compatible with the radio and hboot 157 update or does anyone know of another kernel that will boot a JB rom that the Bluetooth works on. i never use Bluetooth but she always has one in her ear so its a must. when i ran the backup b4 i installed the first rom i somehow only backed up the checksum and not the system like a dummy so its either get it to work or buy her a new phone and i dont wanna do that. Please tell me i can fix this!!! thanks in advance.
[Nexus 7 (2013) General] TheUnladenSwallow:
This is a thread I will be updating tonight and tomorrow, I will be comparing benchmark performance for stock, the new paranoid android build and an unofficial cyanogenmod build compiled for the new nexus 7 (It uses the exact cyanogenmod code, nothing custom. Just to tide us over before nightlies. I will test all of these roms with and without jassy's kernel (Yes I will be rooting stock for that.)

Stock Benchmarks:

Antutu Benchmark:

19318

Quadrant Benchmark:

5229

3d Mark Ice Storm Benchmark:

11866

3d Mark Ice Storm Extreme Benchmark:

7210

Stock with Root and Jassy's Kernel (Using Jassy's settings w/ 1890 mhz clock) Benchmarks:

Antutu Benchmark:

21803 (Large improvement)

Quadrant Benchmark:

6757 (Very large improvement)

3d Mark Ice Storm Benchmark:

13048 (Large improvement)

3d Mark Ice Storm Extreme Benchmark:

8120 (Large Improvement)
[Nexus 7 (2013) General] TheUnladenSwallow:
Don't even think about it

Reserved.
[Atrix 4G Q&A, Help & Troubleshooting] dark_prince:
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).

I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
[Atrix 4G Q&A, Help & Troubleshooting] dark_prince:
Update

I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.

Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)

So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.

RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.

Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.

I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.

I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.

Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.

This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>

Thanks for reading atleast
[Atrix 4G Q&A, Help & Troubleshooting] dark_prince:
Update 3

Fixed it myself.

I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.

All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
[Atrix 4G Q&A, Help & Troubleshooting] mynonama:
Did all rom u flash succesfull..or fail mount?

Can u mount/unmount system..data etc..

If no..then yr cwm was not fr yr models..try another version

Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
[Atrix 4G Q&A, Help & Troubleshooting] dark_prince:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX

And I flashed the fruitcake using fastboot. No flashing of stock sbf :)
[Atrix 4G Q&A, Help & Troubleshooting] noobButStudying:
Please help...recovery bootloop

I have the same problem and tried several CWMs, and TWRP.

I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).

I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.

I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.

Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.

Still no luck.

Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.

Anyone have any advice?

Thanks in advance.
[Atrix 4G Q&A, Help & Troubleshooting] palmbeach05:
did you try the updated and usually standardly used CWM, 5.0.2.6?
[Atrix 4G Q&A, Help & Troubleshooting] noobButStudying:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.

Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.

Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
[Atrix 4G Q&A, Help & Troubleshooting] palmbeach05:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
[Atrix 4G Q&A, Help & Troubleshooting] noobButStudying:
Resolved!

So here's the full story:

It would boot up and say "failed to boot 1"

It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.

Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.

Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."

This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.

But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)

So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!

Yay!! I am ridiculously happy right now!

Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again) ;)
[Atrix 4G Q&A, Help & Troubleshooting] palmbeach05:
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.

Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer :)
[Nexus 7 General] Khaiyan:
Thanks dude! This helped :)
[Nexus 7 General] pmckay:
Thanks!

These instructions worked perfectly. The only minor complication was downloading the necessary drivers - but once they were installed, your directions worked perfectly. Thanks so much.
[Nexus 7 General] Mitsiboy:
I had my n7 rooted before the update, but did not have the bootloader unlocked. If I use these instructions can I just root the device and not change the way it is running? When I rooted it did not make any changes. I just don't want to have a factory reset done.
[Nexus 7 General] fangthorn:
Worked like a charm, Thanks
[Nexus 7 General] AndDiSa:
No, this is method works only with an unlocked bootloader. Either wait for the OTA update (which hopefully still works for you ...) or you need to unlock your bootloader which will imply a factory reset.
[Nexus 7 General] NickDVS:
Are the XXX in the"XXX/ADB..." the name of the folder we have the files in?

Never mind, I found it lol
[Nexus 7 General] NickDVS:
Hello, my N7 has been loading for about 30 minutes after it reset. Is this normal?
[Nexus 7 General] ShadowOf:
Mine took about 5, maybe ten minutes from the last .ZIP flash to being up and running.
[Nexus 7 General] jfmcbrayer:
This is very much the same method I used to update, and it worked great. (I actually copied flash-all.sh to flash-some.sh, commented out all the 'fastboot erase' lines that affected anything I cared about, and changed the 'fastboot update -w' to just 'fastboot update', but overall, very nearly the same thing). Anyone wanting a smooth upgrade path should follow ShadowOf's instructions above.
[Nexus 7 General] ferracam:
Hei man, thanks, it took 30 minutes and everything worked as a charm.
[Nexus 7 General] mzlin:
I had this error on the nexus 7, "signature mismatch", when i'm at step 8.

on the command prompt, i got the following:

sending 'bootloader' (1280 KB)...

OKAY [ 0.206s]

writing 'bootloader'...

FAILED (remote: (InvalidState))

finished. total time: 0.305s

My n7 is rooted, boot unlocked and on stock rom.

Can any one help me?
[Nexus 7 General] peeka73:
Thank you!

Thanks so much for putting together this process in a nice, straightforward and easy-to follow method. :) It worked like a charm! :good:
[Nexus 7 General] sym_richard:
Works perfectly for me. Thanks!
[Nexus 7 General] jollyb:
[MENTION=4819471]ShadowOf[/MENTION]: Thank you very much for this guide. All went ok.
[Nexus 7 General] nuzua2002:
help

Can you help me about updating my nexus 7 to 4.3. My nexus seven .rooted on android 4.2. My official notification bar tells me you can uptade it to 4.3. My only concern is will I lose my root access if uptade it officially. What should I do to update my rooted 4.2 android to 4.3. Thanks
[Nexus 7 General] ShadowOf:
Of course I didn't do the OTA....but from what I read best case scenario is OTA runs smoothly and you lose root.

Worst case scenario you OTA, it locks up at some point because you've change a system file and you are stuck with a non-booting device. Which you can hopefully then flash to stock 4.3 (hopefully).

Again from what I've read going from 4.2/4.2.2 to 4.3 via OTA you will lose root.

Can anyone confirm this method from 4.2 (not 4.2.2) to 4.3? G/L
[Nexus 7 General] d4v3w:
Worked perfectly thanks
[Nexus 7 General] freddy0872:
Very Nice!

Great work! This is great! already took the 4.3 OTA and rooted it before reading this. Used TiBu but this is fantastic for all the others who havent upgraded yet! :good:
[Nexus 7 General] alexxdj:
hi, i have custom kernel (franco) and recovery. Can i use this method to update to 4.3? :confused:
[Nexus 7 General] toni_gon:
I updated to 4.3 with the rooted ROM from Androguide.fr but lost SU along the way, oddly enough I was able to boot into recovery and reflash Update SU v1.51, I assume I never lost root, but all is well now.
[Nexus 7 General] pool0513:
So good !
[Nexus 7 General] jfmcbrayer:
Yes, but you will end up with the new stock kernel, and whatever recovery you flash during the last part of the instructions. If you follow the instructions exactly, you'll end up with a rooted, fully stock 4.3 with your existing data preserved. You can then flash the new franco kernel (r75). You may then have to re-flash SuperSU 1.51 to re-root, as some people lose root after flashing the new franco kernel. It should stick after you re-flash SuperSU, though.
[Nexus 7 General] ShadowOf:
Thanks for replying...I only know how it worked in my case. I couldn't answer.
[Nexus 7 General] Gster09:
Maybe I missed what it is you're trying to do exactly, so let me just make some observations...

A) The 2012 Nexus 7 WiFi is known as the Grouper device and your WiFi model will need the "nakasi" builds.

B) Based on the above, you should flash a Grouper bootloader image (unless they're the same), and

C) Your system image (*.zip) should be the "nakasi" version, looks like you're trying the "nakasig" which is for the mobile device.

I think you've mixed and matched your images so that may be causing the issue(s). Does that make sense? Hope this helps.
[Nexus 7 General] freddy0872:
Yea your flashing for tilapia. The tilapia device is the nexus 7 3g model. You have grouper.... Which is the wifi version.

You cannot mix and match their files! That goes for roms. Recoveries. Or bootloader!

Look for grouper files and you'll be all set!
[Nexus 7 General] Gster09:
I just realized that when you follow the link on the OP to the images, it can look like the one you want is the 'nakasig' because of the way the page loads on a browser.

Here is the link from the same page, but specifically for the nakasi JWR66V build. (That means WiFi model and Android 4.3) ;)