yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] Egregious Philbin:
Same thing here, but dock isn't charging...
[Asus Transformer TF700] ImYoungxD:
Defective. Exchange dock or send to Asus for repair.
[Asus Transformer TF700] Clegs:
I don't know what happened but I left it plugged in all night yesterday and this morning it was half charged with the light on orange so I'm hoping that sometime when I was sleeping it fixed itself.
[Asus Transformer TF700] junrider:
A whole night charged and half charged still doesnt seem right... If its all fully charged now.. it a matter of time when it will happen again..
[Asus Transformer TF700] pceasar:
I've had a dock die and just flash with no charging on the prime before guess it was defective. Picked up an open box from ebay for 90 bucks works like a charm.
[Asus Transformer TF700] Egregious Philbin:
I got the dock to charge, but had to monkey around to get it to fit just right....still not fun....
[Asus Transformer TF700] rafaumm:
Got it solved by doing a cold boot.

Turned it off then held power + vol down combo untill I saw the text "cold-coot linux" apear, released the buttons and waited boot.

Now the charging light is blinking.on the dock.
[Asus Transformer TF700] rafaumm:
Ok. Honest mistake. It wasn't charging. It blinks when active (connected to tablet and tablet unlocked...if you lock the tablet the dock led stops blinking).

Tried the cold boot thing described above. Didn't work.

The charger charges the tablet alright, but not the dock.

Opened it up yo see if there was something wrong (cable disconnected or so). Unplugged and plugged everything back. Still won't charge. =/

Any ideas????

Thanks in advance!
[Asus Transformer TF700] rafaumm:
Got it to charge using a pliers. Images attached.

Apparently or my dock jack is bad or my cable connector...most probably the dock. =/

Any ideas on what to do now? Where can I get this jack? Is it not extremely hard to replace? Worth it?

I'm in Brazil, so I got no official ASUS support for this piece. =(
[Asus Transformer TF700] geniv:
did you manage to fix the problem?

I have the same issue
[Asus Transformer TF700] davis_llb26:
I have the same problem

Hi, did you resolve the problem? I have the same issue
[Asus Transformer TF700] jgrills:
I have the same issue, and after reading your post, I tried your hack and the charging light finally came on for my dock. Evidence strongly suggests its a flaky electrical connection in either the cord or the jack. I am leaning towards jack because my cord will charge my tablet when directly plugged in, but I am not yet convinced.

Noticing that the connector's pins are on the outside, and it connects to a double-sided blade of pins, I tried to squeeze the connector some to make a better electrical connection. It was a little better, in that I could occasionally now get the charging light to turn on for a few seconds by applying pressure to just the cord's connector, but still not reliable. I then tried to use a small blade between the plastic and outer metal casing of the cord's connector, and I destroyed the came and now it won't even charge my tablet. I'll have to go to the store tomorrow to replace the cable, and we'll see if a new cord works to power the dock.

There's a distinct possibility that a new cable might just be all the fix I need.

Looking at the teardown on ifixit, it seems like the tablet uses a slightly different connector housing than the dock. Perhaps the dock has a less reliable part.
[Asus Transformer TF700] jgrills:
A new cable did not fix it.

Without another good path forward, I get brave and have attempted to reshape the receiver jack's metal housing to be more snug, hoping that a squeeze would do it. I have only managed to mangle it further.
[Kindle Fire Q&A, Help & Troubleshooting] TheKid2:
I removed back cover from kindle, rear cover did not seat fully upon re install. Loose on two corners.

was wondering if anyone has had there kindle apart and had a similar issue.

Was thinking of just gluing with silicon adhesive, so as to be able to remove later if needed.

Any thoughts?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Did you break any of the clips?
[Kindle Fire Q&A, Help & Troubleshooting] TheKid2:
Must have broken something as cover does not snap back as cleanly as it did before.

It does not seam like it is going to fall off, would just like to be sure it is secure.
[Kindle Fire Q&A, Help & Troubleshooting] nnutter:
I rooted and installed an ICS ROM several months back on my Fire. One morning the wife brings it in and says my son got it stuck in some weird mode. Turns out it is stuck on the TWRP yellow triangle and does not seem to be able to get into recovery mode. I have done that several times before so I am pretty confident I am not messing that up. Just the power button never turns orange and eventually the device just turns off. My computer see the USB device but ADB does not. I did `android update adb` and then added '0x1949' to '~/.android/adb_usb.ini'. Do I have any options left or is it bricked?

Thank you to anyone who takes the time to read this. Especially to any who can reply with suggestions.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Download TWRP and FFF1.4

TWRP

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

FFF1.4

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

ADB will not work because you're in fastboot mode. Use fastboot commands to install the new TWRP and change the bootmode.

fastboot flash recovery /path/to/recovery.img
fastboot oem idme bootmode 5001

Hold the power button to perform a hard shutdown and restart the device. You should then be able to launch recovery using the power button. If not, you'll have to flash the bootloader as well. If this is the case, be extremely careful you don't pull the USB cable during the flash or you will really brick your device.

Also, it is very important to know that the version of FFF you'll download comes in a .zip format to be flashed in recovery. Don not flash the .zip file directly to your bootloader partition. Instead, unzip it and find the "fff-u-boot_v1.4.bin" located in the cache folder and flash it.

fastboot flash bootloader /path/to/fff-u-boot_v1.4.bin
fastboot reboot

If you were able to access recovery just by reinstalling it with the first command, push the FFF1.4.zip file to your sdcard and flash it in recovery. Just remember not to wipe anything before installation. That will help you to fix your bootmode problems a lot easier in the future by holding the power button untill the boot options appear at the bottom.
[Kindle Fire Q&A, Help & Troubleshooting] nnutter:
Thank you! I am back in recovery!
[Verizon Samsung Galaxy S III] CovXX:
Anyone else having their phone over heat ?

Tomorrow will be my 3rd phone beacuse of overheating and i have one more replacement before i have to switch to a different phone.
[Verizon Samsung Galaxy S III] ooofest:
What do you consider overheating and how are you measuring its temperature?

- ooofest
[Verizon Samsung Galaxy S III] sRDennyCrane:
NOT a known issue. The S III might get warm under a heavy load or charging a very low battery, but overheating? I'd look at the mods you've done to the phone. The ROM you flashed, the apps you're running... this sounds like a user error.
[Verizon Samsung Galaxy S III] 4zureSky:
Roms?

I have cyanogenmod 10 nightly with jellybean 4.1.1 and I've been getting temperatures around 95-101 fahrenheit under pretty heavy use. From what I've found out, it seems normal.
[Verizon Samsung Galaxy S III] annoyingduck:
If your in the 140 degree area, start investigating, if your 150+ start worrying. Other than that, don't worry about it.
[Verizon Samsung Galaxy S III] SMR-DINO313:
No over heating what so ever. On my s3. But I have seen one s3 b4. I from Sprint though. It was over heating from just talking on the phone.

U got any temp. Measurements?

Sent from Land Line using pay phone
[Verizon Samsung Galaxy S III] Hypnosis4U2NV:
Do you know that these phones have CPU's that given certain stresses, will heat up quite a bit? That's why they are installed on metal frames and with thermal paste, so the phone can dissipate heat..

These aren't your ordinary dumb phones, these are portable computing devices too..

Sent from my Commodore 64..

READY.

load"*", 8,1
[Verizon Samsung Galaxy S III] mdt73:
My original S3 was getting a bit too hot to hold with a 2 bar 4G connection, surfing the web. Exchanged the phone using the 14 day return policy at the local verizon, and my new phone has no issues.
[Verizon Samsung Galaxy S III] CovXX:
i mean like 120 + With little use. Im also using reborn battery widget to get the cpus temp. And my pc doesn't even get past 101 and that has 6 cores.
[Verizon Samsung Galaxy S III] ooofest:
You realize that your PC likely has rather decent ventilation and actively controlled fans, yes?

120 F isn't really a cause for concern, IMHO. Above 140F consistently might be, though - could be the battery, actually.

- ooofest
[Verizon Samsung Galaxy S III] dnap941:
No over heating here

I'm currently on CM10 nightly 9/18. No over heating here. Ever. I've had the phone since it was put on shelf.
[Verizon Samsung Galaxy S III] sendtoworthington:
Hi All,

I'm just coming over to the S3 from a Motorola Photon.

I loved the universal inbox app on the photon (to be able to manage my 10 different emails (Gmail/Hotmail/Yahoo/Corporate etc).

Is there anything like this for the S3? The S3 email app is not as well organized as the Photon's was (each email had it's own icon i could click on an view emails from - instead on the S3 its more a drop-down selection). Could one port / take the photon's email app and install it on the S3 (where would I find this?)

Thanks!
[Verizon Samsung Galaxy S III] ooofest:
Kaiten Email has a universal InBox, as does its free version, K-9 Mail.

I'm just a satisfied Kaiten Email purchaser.

- ooofest
[Verizon Samsung Galaxy S III] mav3rick478:
I use K9.

= sent from my Unlocked VZW S3 =
[Verizon Samsung Galaxy S III] sendtoworthington:
Bummer... I was really hoping there would be another solution. K9 and Kaiten just aren't very clean/ slick interfaces...

(back to using my photon...)
[Verizon Samsung Galaxy S III] tomalrocks:
you can try flashing the default samsung mail. It has combined mailbox.
[Verizon Samsung Galaxy S III] ooofest:
OK, I guess that "clean/slick interfaces" didn't come through in your original post, though that's a highly subjective statement: e.g., Kaiten is pretty clean and slick, to me.

Plus, there's tons of unified email apps out there, such as AquaMail and others. Just search the Play store for possible hits.

Seems like you didn't need to move in the first place.

- ooofest
[Verizon Samsung Galaxy S III] ssnapier:
The release notes on OTA Rootkeeper specifically say it will not work on any Samsung phone that was rooted using Kies or ODIN. I loaded Root66 with ODIN, and I have a locked bootloader so I was just curious if anyone else in my situation has tried this with the same setup.
[Verizon Samsung Galaxy S III] mrniko81:
yes, i was using route66 and voodo root keeper and it worked fine... have seen it not work on other roms, but if u get one of the pc based rooting apps its a sinch to reroot even if it doesnt work
[Galaxy Tab 2 General] BigBot96:
Hi all,

I've got a VZW G Tab 2 7.0 Got it rooted and now looking to port CWM over to it.

I found This guide to port cwm, however he states it won't work for Samsung devices. I also attempted using the Recovery Builder with no luck. It wouldn't boot into CWM at all.

My question is.. can somebody give me some tips on how to port CWM to my tab? I've got some experience with programming/scripting/linux, but no idea where to start!

Thanks in advance
[Galaxy Tab 2 General] imnuts:
That guide is old, so it should work for Samsung devices now. Back in the days of the original SGS phones, it didn't due to a different recovery/kernel setup. If you can pull the boot.img and recovery.img from the tablet, it should be relatively easy to get it to work. Seeing as people have rooted the I705, that should be easy enough to do.
[Galaxy Tab 2 General] BigBot96:
Ah ok that's good to know. I have already pulled all of the stock partitions for my own keepsake. I'll do what I can. Thanks man.
[Galaxy Tab 2 General] BigBot96:
Well I followed the guide to exactly and got a recovery.img.. same result as I had using the 'builder'. The device reboots, little blue words saying 'recovery booting'. Screen goes black, then lights up with black background, flashes once, then reboots normally.

recovery.fstab has the correct values for this tab.

/boot	emmc	/dev/block/mmcblk0p7
/system ext4	/dev/block/mmcblk0p14
/data	ext4	/dev/block/mmcblk0p15	length=-16384
/cache ext4	/dev/block/mmcblk0p17
/recovery emmc	/dev/block/mmcblk0p18
/sdcard	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1
/efs	ext4	/dev/block/mmcblk0p11
/modem	emmc	/dev/block/mmcblk0p1

Would a locked bootloader prevent a CWM from booting? How would I tell if it is? In 'download mode', in the top left corner it says the following:

ODIN MODE

PRODUCT NAME: SCH-I705

CUSTOM BINARY DOWNLOAD: NO

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Official

QUALCOMM SECUREBOOT: Enabled

Then in the middle of the screen it says 'Downloading.. do not turn off...'

Don't know if this means the BL is locked or not, though.

My recovery.img download

If anyone want's me to post any more info let me know.

EDIT: What else needs to be done to build a successful recovery? I hardly think it's as easy as it is in the guide.. though I could be wrong. :)
[Galaxy Tab 2 General] ketut.kumajaya:
http://xdaforums.com/showpost.php?p=31671148&postcount=21 No feedback? Fail?
[Galaxy Tab 2 General] BigBot96:
Didn't notice that! I stopped following since It seemed the others did as well. Yes... fail. I'll check that out.

I'd like to know more about the process, though. So my questions still stand :)
[Galaxy Tab 2 General] ketut.kumajaya:
I have my own scripts to unpack and repack boot.img or recovery.img using unpackbootimg and mkbootfs tools. What I've done:

1. Unpack yours stock recovery

2. Add CWM's /res/keys contents to yours recovery /res/keys

3. Repack the recovery

$ unpackbootimg.sh recovery.img

Edit /res/keys

$ repackbootimg.sh recovery.img
[Galaxy Tab 2 General] BigBot96:
I'm getting the same reboot issue after trying to access recovery using yours. :/
[Galaxy Tab 2 General] ruben00:
If the SGS3 for Verizon is any indication, it may very well be that the Verizon GTab2 has a locked bootloader, which doesnt allow unsigned recovery images. You were doing the right steps to test though.

Here is my suggestion (I don't own this tablet, but im trying to see if I can help you out)

First, Use the image you built using recovery builder

open odin

uncheck "Auto Reboot"

Flash your Recovery Image

Make sure it didnt say "Failed" under Message, if it did, its probably locked. If not, read on

At this point, close Odin, but leave your tab attached to the PC

Hold down the power button until you get the "battery charging" image

Unplug from the PC

Hold Volume Up + Power until the first Samsung Splash appears then let go

See if CWM loads

Once you exit, CWM

SHOULD

tell you that ROM will overwrite it, if you want to fix that, pick Yes

You now have CWM (crossing fingers)

report back and let me know
[Galaxy Tab 2 General] BigBot96:
It failed.. so I'm assuming it is locked then..
[Galaxy Tab 2 General] imnuts:
I haven't used a Qualcomm chipped device, but I'm going to guess that the above highlighted part is your issue. Until that says "Disabled" you get to have fun with whatever VZW gives you and nothing more.
[Galaxy Tab 2 General] BigBot96:
Well my gs3 says that also and i have the bootloader unlocked. Both devices show it greyed out.
[Galaxy Tab 2 General] Maximinus I:
Being that its Verizon I will go ahead and say its locked. That means unless someone finds an exploit you won't get a custom.recovery to work.
[Galaxy Tab 2 General] BigBot96:
Yeah... that's what I was afraid of.. had high hopes though! I may never be able to crack it myself... but I'm not gonna give up. Besides, gotta learn somewhere so what better place to start. I'll probably start off by studying the gs3 unlock... seems sensible. Anyone have some tips for a noob 'developer'?
[Galaxy Tab 2 General] imnuts:
If you don't know where to start, I wouldn't start with the bootloader. Also, the best person to talk to would probably be Adam Outler. As far as I know, the unlocked VZW SGS3 is because they got lucky and someone sent them, or someone found, an unlocked bootloader that could be flashed to the device.
[Galaxy Tab 2 General] BigBot96:
I was reading through the original s3 bootloader thread and they were saying that even with the bootloader locked, you would still be able to load a recovery and flash TW roms etc. /boot is encrypted and /recovery is not. That still prevents ODIN flashes, but not using dd from ADB. If this device is anything like the s3 (which so far as I, it is) than the same *should* apply here.

Most of the attempts I've had were from ADB using dd. Any truth to this? I don't care to have custom kernels or even CM10. Just would like to make backups and I'd like to get started with ROM development.

I kinda believe my recovery is NOT encrypted/locked because if it was I'd assume I'd get that nasty VZW Warning screen which I don't.. thus I should be able to load custom recoveries.
[Galaxy Tab 2 General] Maximinus I:
You still would need an exploit in order to even attempt a custom recovery. Pretty much anything out of Verizon will be locked even the sgs3 needed an exploit in order to load recovery I be leave. Your best bet as mentioned before would be to contact one of the experienced devs to see if they can help.
[Galaxy Tab 2 General] BigBot96:
I don't think there needs to be an exploit for recovery. I've been reading up on all the original dev on that device and there were recoveries before it was unlocked.
[Galaxy Tab 2 General] keymaster911:
I tryed these steps. Now I have a brink device that won't even turn on at all.. I have tryed everything I can.. Does anyone have any clues how to get this thing back up and running..
[Galaxy Tab 2 General] BigBot96:
What steps? This isnt a tutorial and there currently isnt a working recovery for this tab.

Im currently compiling another one with some modifications. We'll see..
[Galaxy Tab 2 General] Mohamedselim:
You should try all button combinations after charging the tab for even 10 hours as volume up+ power to go to recovery or volume down+power to go to download

If not so hard brick so return if you can or try some jtag services which require paying

Sent from Galaxy S2 or Galaxy Tab2
[Galaxy Tab 2 General] keymaster911:
Let you guys know in the morning.

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] keymaster911:
Tryed everything under the sun. Hard brick the device. Time to send it to Samsung for repair

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] BigBot96:
Just curious... what steps did you take to flash a recovery? This thread wasn't a guide so I'm not sure what you flashed or how you flashed it. If you used ADB, can you give us the exact command you used? It's not flashable through ODIN so I doubt you used that.
[Galaxy Tab 2 General] Maximinus I:
The exploit is needed because its locked. You can't access the proper files to use recovery without getting by the systems check and security. You can have recovery without being unlocked.
[Galaxy Tab 2 General] BigBot96:
Ah, gotcha. I'll ask around in the s3 forums to get some more pointers. Thanks man.
[Galaxy Tab 2 General] BigBot96:
Been talking to invisiblek who got recovery working on the vzw s3. He confirmed what i thought: NO exploit needed for custom recovery other than root. Bootloader only checks the boot partition. (Does not include odin, thats locked for recovery and boot) Suggested i inject my zImage into a recovery for one of the other gtabs to see if i can at least boot into recovery. Ill do that and let yall know the results.
[Galaxy Tab 2 General] imnuts:
Make sure to include any modules for the kernel as well.
[Galaxy Tab 2 General] keymaster911:
I know one thing. Do not use either, ezrecovery or ezunlock from the market. That's what brick my tab. Figure it wouldn't hurt to try. Lmfao

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] ketut.kumajaya:
From my experience on MSM platform, when packing a boot/recovery image, base address and page size must be correct.
[Galaxy Tab 2 General] BigBot96:
I'm having the same problem after the advice. Repacked the recovery with my zImage. Repacked it with this command

./mkbootimg --kernel recovery.img-kernel --ramdisk ramdisk-new.gz --board MSM8960 --pagesize 2048 --base 0x80200000 -o recovery-new.img

Even tried using a recovery from the GS3 and the WiFi g tabs. The recovery from the other gtabs doesn't even look like it's working. However the GS3 gives the same results as my compiled recovery. I need some more pointers here. Even if somebody else what's to give it a go, I can dump whatever files you need.
[Galaxy Tab 2 General] keymaster911:
I would try getting hold cwm development group. They might be able to help you. I have root with super user. But no recovery. Did you get that yet

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] BigBot96:
Nope, no recovery yet. Just reboots. I was going to try and get ahold of Koush, who I think started CWM or if he didn't he sure did a lot for it.
[Galaxy Tab 2 General] keymaster911:
thats what i would do. i bricked my last tablet. but Verizon sent me a new one.

Sent from my SCH-i705 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] ketut.kumajaya:
Have you already tried to unpack and then repack the stock recovery? Just unpack, repack without any modification and then flash to your device to confirm the mkbootimg options is correct.

EDIT:

I have two nice script to unpack and repack a boot/recovery.img

$ ./unpackbootimg.sh recovery.img
$ ./repackbootimg.sh recovery.img
[Galaxy Tab 2 General] BigBot96:
Good point. I'll give that a try when I get home and report back.
[Galaxy Tab 2 General] keymaster911:
Did anyone even get the bootloader unlocked yet.

Sent from my SCH-I535 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] BigBot96:
The bootloader is unlocked on the vzw gs3. Different hardware here. And I don't think anyone is even working on this tab except me.
[Galaxy Tab 2 General] Gilbot:
Try contacting loccera from the vzw 7.7 forums. Maybe he can help. The dude is a lifesaver for us i815 7.7 users. :)
[Galaxy Tab 2 General] keymaster911:
just shot him a messege. god be with us on this.

Sent from my SCH-i705 using Xparent SkyBlue Tapatalk 2
[Galaxy Tab 2 General] BigBot96:
Well here's a weird one. Unpacking and repacking stock image does the same boot/reboot. Hmm... I'm pretty sure I have the correct values.

board MSM809

pagesize 2048

base 0x80200000

To be honest, I can't remember how I found the board name.. lol. Where would I find that again?

Got pagesize from the unpack

Got base from config (config.gz extracted)

edit: also, after repacking the stock recovery with no modifications, the freshly packed IMG is roughly 3.5 mb smaller than original. This normal?

edit2: and just verify my flashing is correct and not missing any arguments

# dd if=/sdcard/recovery-new.img of=/dev/block/mmcblk0p18
[Galaxy Tab 2 General] ketut.kumajaya:
# cat /proc/cmdline
# cat /proc/last_kmsg

Have a lot of informations. Better you share the results here.
[Galaxy Tab 2 General] BigBot96:
cat /proc/last_kmsg is not found.

cat /proc/cmdline

console=null
androidboot.hardware=qcom
user_debug=31
sec_log=0x80000@0x88d00008
sec_dbg=0x40000@0x88d90004
sec_debug.reset_reason=0x1a2b3c00
etb_buf=0x4000@0x8fffb9c0
androidboot.debug_level=0x4f4c
sec_debug.enable=0
sec_debug.enable_user=0
cordon=2fc5c9fad43d8769d6a967cd3c1dcc3a
loglevel=4
samsung.hardware=SCH-I705
androidboot.emmc_checksum=3
androidboot.bootloader=I705VRALG3
androidboot.nvdata_backup=1
androidboot.boot_recovery=0
androidboot.uart_debug=0
level=0x574f4c44
sec_pvs=0 androidboot.emmc=true
androidboot.serialno=620f35b1
androidboot.baseband=msm