yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] thenameisnigel:
FakeFlash posted as promised. There's no changes between the 07/26 MD5 and the 07/27 FakeFlash other than the build date.
[Android Q&A, Help & Troubleshooting] LDee:
Please can someone who has a copy of A789_ROW_S107_cybermaus_ICS_v3.21.zip that THEY KNOW WORKS please upload it to somewhere and please post the link. There seems to be a problem downloading the version that is in the guide in Cybermaus' DevHost site, it downloads extremely slowly and then at the end files are missing every time, I have tried to download it many times on different days, the scatter file and lots of others are missing and sometimes it stops at around 150MB but says it is 100% done.

Please help, this might be what's preventing me from following the guide.
[Verizon Samsung Galaxy S 4] TeamAndroidGray:
Sorry for starting a new thread. I'm overwhelmed with all the reading and corrections. Hopefully someone can help me.

1. Verizon Samsung Galaxy S4 (MODEL)SCH-I545

2. Running KitKat 4.4.2

3. Build: VRUFNC5

I rooted my Galaxy S3 so if I have everything I need I should be able to handle it. I prefer to do it from my PC if possible.

I'm currently downloading THECOMPLETEPACKAGE but it's massive @2.3GB :(
[Verizon Samsung Galaxy S 4] joshm.1219:
Google towel root. It's an app you install with one click root.
[Verizon Samsung Galaxy S 4] riker147:
Search Towelroot and Safestrap.
[Verizon Samsung Galaxy S 4] TeamAndroidGray:
Can you help????

I downloaded new software update the other night. Now my phone is unrooted somehow.... On top of all that when i try to reroot my phone it says THIS PHONE IS NOT SUPPORTED. I been using towelroot for about the past 3 or 4 months. I don't understand
[Verizon Samsung Galaxy S 4] bamige1:
The Towelroot method only works with the nc5 and nc1 kernel i believe, not ng6.
[One (M8) Accessories] Chris_c81:
Does anyone have this case please?

http://www.incipio.com/cases/smartp...-m8-cases/htc-one-m8-watson-wallet-folio.html
[One (M8) Accessories] phil.culler:
I don't but it looks nice albeit a bit bulky. Curious as to what exactly "vegan leather" is though...
[One (M8) Accessories] MoNsTeReNeRgY22:
http://lmgtfy.com/?q=vegan+leather :D
[One (M8) Accessories] Chris_c81:
Still considering this case. Looks smart.
[One (M8) Accessories] rhoddog77:
Classic

classic lmgtfy!
[One (M8) Accessories] PcFish:
The black is $25 and white $29 on amazon prime.

Reading reviews, it seems like it takes a bit of effort to separate the case from the wallet.

And the band blocks the headphone jack if you're listening to music.

EDIT: Mine came in, used it all weekend. The card slots are hard to access. Have to kind of scrape with the credit card until you get it in the slot. You need to use the band to close the case, as the cover bends unattractively with a card in each slot.

The band does block the headphone jack, though you can bend it to the side. Though I suspect this will stress the elastic band as there are already signs of wear and I just got it.

It is a bit difficult to separate the wallet from the case at first, you definitely need a bit of nail to do so. But once you do it's simple. (I start at the right corner, work my way down until it pops out from the side.)

Overall, this'll do until I get my devilcase in. It's a bit too bulky over my supcase beetle or spigen hybrid, even without cards in the slots.

EDIT AGAIN: After about a week of use, I've noticed the same problems as the dot view, where it doesn't seem to detect the cover is closed. I have 3 cards in the slots (The max allowed) and the cover bows with the elastic band wrapped around. At it's widest, the case with phone is 3/4 inch wide. The elastic band is already starting to show wear, it may separate from the case any time now. I've probably wrapped/unwrapped the elastic band less than 50 times. Separating the case from the wallet has gotten easier, I no longer need nails.
[Samsung Gear Live] Dees_Troy:
Thanks to [MENTION=3682533]AdamOutler[/MENTION] for testing!

It took a lot of effort to make this happen. Adam was able to get UART working. When the kernel source dropped I compiled a kernel. We used information from the UART output to determine correct addresses for kernel, ramdisk, and tags to make our first image. We could tell that it was init'ing and booting via the UART output, but no adb. We were eventually able to get adb by kanging the init.rc from the LG G Watch which allowed us to finally get a rooted shell via adb to dump the factory images. From there we determined that TWRP needed to use Qualcomm's overlay graphics to get display working. With that and some more init.rc work we got TWRP booting up and adb working. With 4 cores running, the Gear Live gets very hot and the battery drains quickly. With more changes to the init.rc we're now running with only 2 cores with a max frequency of 600MHz to keep thermals and battery drain in check.

The theme is undersized. Hopefully next week I can work on upscaling the the 240x240 theme up to 320x320 to fit the full screen. Still, for now I present the first fully working recovery for the Gear Live.

Manual install instructions.

Download folders with current and prior versions:

Mirror 1

Mirror 2
[Samsung Gear Live] skitty:
TWRP installed and backup made. Let the custom ROMs begin
[Samsung Gear Live] rant:
Recovery installed fine, but now my only option appears to boot into recovery, regardless of what I select from twrp or bootloader, cannot boot into the OS.
[Samsung Gear Live] AdamOutler:
Sounds like you did Fastboot flash boot recovery.img.
[Samsung Gear Live] rant:
Crap, you may be right. Any suggestions on how to resolve? I did download your factory image but not sure where to start
[Samsung Gear Live] zav22:
Same issue here. Recovery seemed to install fine, but every time I try to boot to system it loops back to recovery. Trying to figure out Adams factory image too. Doesn't seem like there's a download mode on the watch so I assume odin is out?
[Samsung Gear Live] skitty:
I installed twrp fine using fastboot flash recovery recovery.IMG. have to use a PC to boot into it tho
[Samsung Gear Live] Dees_Troy:
Those of you who flashed TWRP to the boot partition can download the boot.img from Adam's dump of the stock software and flash it using fastboot mode with this command:

fastboot flash boot boot.img
[Samsung Gear Live] zav22:
Still no luck. Flashed stock boot.img. Trying to boot to system returns to TWRP. Trying to install SuperSU, factory wipe, or ADB sideload all generate errors "unable to mount '/data'", '/data/media', storage, etc. Applying KVM78X update will get me as far as the spinning colored dots..
[Samsung Gear Live] jeffrey1790:
did a fastboot oem unlock;fastboot flash recovery recovery.img;fastboot flash boot rootADB.img and it still boots into twrp when i turn my watch on
[Samsung Gear Live] Dees_Troy:
You should not be flashing the rootADB.img
[Samsung Gear Live] lichti1901:
Flashed twrp yesterday and run into the same issues as some others here.

1. Unlocked bootloader (fastboot oem unlock)

2. falashed twrp afterwards (fastboot flash recovery nameofrecovery.img)

3. boot into recovery and played with it a little

4. tried to reboot system, but it boots straight into recovery again

5. Flashed boot.img from Adam´s system dump (fastboot flash boot boot.img) .... still the same-boot straight to recovery again

6. flashed system.img from system dump (fastboot flash system system.img) .... the same

7. flashed recovery from system dump (fastboot flash recovery recovery.img) ... system tries to boot, but bootloops.

8. Now the funny thing, i cant get into bootloader mode, only in the menu where you can enter download mode, upload mode, recovery and power off, tried to adb sideload the rom but that doesnt work because adb and fastboot dont work, notebook doesnt recognize the watch.

Seems like i bricked it.

If anyone have ideas what else i can do or know something i i dont know, please help me out. :angel:

Regards, lichti
[Samsung Gear Live] jeffrey1790:
Ended up doing that exact thing. And it seemed to work for me. Hmm.
[Samsung Gear Live] lichti1901:
Let it loop for 30 min. But doesnt boot up, got extremely hot so i stopped

Gesendet von meinem Nexus 5 mit Tapatalk
[Samsung Gear Live] Dees_Troy:
I pushed out a 2.7.1.1 update with a full screen 320x320 theme included.

The proper process for unlocking the bootloader is to fastboot oem unlock then fastboot reboot. Let the device boot up normal after unlocking so that it completes the wipe of the data partition. For those that are stuck in a bootloop because you flashed and/or booted TWRP first, try going to Wipe -> Format Data and type yes to complete the wipe then let the Gear Live boot normally.
[Samsung Gear Live] skitty:
Installs perfectly.

Looks much better now that the recovery fills the whole screen
[Samsung Gear Live] JoeFCaputo113:
Where are backups stored? Phone, right?
[Samsung Gear Live] Dees_Troy:
No, there's no Bluetooth in recovery and even if there was, the transfer rates would be slow and probably consume a lot of battery. Both the Gear Live and G Watch have 4GB emmc chips in them with about 3GB of user accessible storage. The backups are stored directly on the watch.
[Samsung Gear Live] JoeFCaputo113:
How big is the AVG backup? And cool I did not know that!

Also, in your opinion, what are the benefits as it stands right now to rooting, installing a custom recovery on the Live?
[Samsung Gear Live] Krunk_Kracker:
I'm in this same boat.

Flashed the stock recovery image and boot and system image and it's stuck on a bootloop.

To get into recovery is pretty easy, hold the power button and when the Samsung logo appears, swipe from top right corner to bottom left and it takes you to recovery. I've factory reset and wiped cache...stuck on a bootloop.

I'm sure it's not bricked since I can get into recovery. Just not sure what to do in the meantime.

Hopefully Samsung will release an image soon so we can use odin to restore to default. I've had this watch for literally two hours, lol.
[Samsung Gear Live] skitty:
Am I the only one who can get it to work then?
[Samsung Gear Live] Krunk_Kracker:
I followed the directions exactly, I know for a fact I flashed the recovery image to the recovery partition. It's odd that it happened.

As soon as samsung gets off their asses and releases the factory image and we can flash it through Odin, this won't be a problem.
[Samsung Gear Live] lichti1901:
I think no, adb doesnt recognize the watch, so we cant flash anything.

Gesendet von meinem Nexus 5 mit Tapatalk
[Samsung Gear Live] Krunk_Kracker:
It can still be put into download mode, which means once we have the correct files from Samsung, we can use Odin to push the stock image and factory restore it.
[Samsung Gear Live] Tower1972:
all went well for mine. unlocked first...rebooted and let it settle.. Waited a few min, flashed the revcovery, entered recovery, got an error about not being rooted and did I want to install SuperSU, to which I hit no, phone rebooted and is back up and running

Thank ya!
[Samsung Gear Live] Krunk_Kracker:
I called Google, told them my watch was boot looping and they sent me another next day air. I've unlocked the bootloader but I think I'll wait to flash recovery until we've got an Odin image from Samsung.

I know what I did wrong though... The first time, after I unlocked the bootloader, I flashed the recovery immediately instead of rebooting first to let it clear everything.

So yeah, don't do that.
[Samsung Gear Live] zav22:
I finally managed to boot properly. Sounds like there are two issues people who have followed the original instructions are running into:

A) Flashing TWRP and booting directly into recovery without a normal boot first to let /data to be wiped. This seems to result in the watch constantly booting to recovery.

B) Attempting to remedy 1) by flashing the stock boot.img, system.img, and/or recovery.img, or reflashing TWRP and getting stuck at the infinite boot animation.​

I followed the initial instructions to the T which never stated it was necessary to immediately boot normally afterwards. This resulted int the infinite boot animation. I then booted into recovery and tried to reboot to system. No luck. Bootloader worked so I was able to send fastboot commands. tried flashing the stock boot.img, and system.img (was hesitant to mess with recovery.img because I was afraid I would truly brick the watch). No luck. I tried combinations of wiping /data, factory resetting, flashing TWRP over again. No longer had the infinite boot animation but the watch would only boot into recovery. So I'm essentially at A). This eventually worked:

1) Turned watch on, booted into TWRP

2) Wiped /data and factory reset

3) Attempt to Reboot -> "System", watch returns to TWRP

4) Reboot -> Bootloader

5) On PC: fastboot flash recovery recovery.img (from http://xdaforums.com/gear-live/development/ear-live-stock-firmware-image-24jul14-t2827274

6) Reboot to "Start"

7) Watch now gets stuck in the infinite boot animation again

8) Hold down power button, restart watch, swipe diagonally while holding power button

9) Watch reboots to bootloader menu

10) On PC: fastboot flash recovery openrecovery-twrp-2.7.1.1-s

prat.img

11) Reboot to "Start"

12) Watch finally boots normally and is all factory reset​

That's what worked for me. Hoped that helps. I am greatly relieved and am happy to be able to play with my new toy again. By the way the new theme looks great and TWRP has otherwise been rock solid. Thanks.
[Samsung Gear Live] Dees_Troy:
2.7.1.2 has brightness settings and properly working screen timeout in TWRP.
[Samsung Gear Live] rant:
Thanks to those that have posted steps on how you got your device out of the boot loop. None of those worked for me, so I'm just doing an exchange with Google. New one should be here tomorrow, and that will likely be the first Android device I've owned in several years that I haven't immediately rooted and installed a custom recovery. Or at least that's what I'm telling myself after fubar-ing this one.
[Samsung Gear Live] Krunk_Kracker:
I was about to reply the same exact thing.
[Samsung Gear Live] Krunk_Kracker:
I'm not sure why it matters. It has the device name on the file name, so it'd be real hard to mix up.
[Samsung Gear Live] lichti1901:
Can someone post his nandroid backup here, its the last thing i want to try before i send the gear back. Maybe i can restore it and get the watch to boot again.

Everything else doesnt work, flashing system.img, boot.img, original recovery, factory reseting in twrp and orig, wont work either.

Gesendet von meinem Nexus 5 mit Tapatalk
[Samsung Gear Live] vanessaem:
Hello,

I know talking about TWRP recovery version numbers is technically on-topic discussion but I don't think it's something that needs to be debated. As you can see, the thread has been cleaned a bit so that there is no more references to version number arguments. Lets all start fresh and everyone please try and move on to more important matters and discussions pertaining to this recovery.

Regards
[Samsung Gear Live] baj24:
Worked like a charm. Thanks so much for all your hard work!
[Samsung Gear Live] beastes:
hi im on 6.0.1 on my gear live bl unlock i flash twrp everything work but after reboot is gone and im back to official recovery any help be really apreciate thank
[Samsung Gear Live] Jsonic:
If this is anything like what happened with the LG Watch Urbane the issue is because the 6.0.1 update changed the System file system format to quashfs. This means it can't read/mount it so it can't patch the Recovery auto restore. Rbox was quick to hack together a TWRP fix that got things up and running. I'm sure the same needs to happen here.

This thread
[Samsung Gear Live] beastes:
thx i better understand ,any news about this thank you
[Samsung Gear Live] tlmasonaea:
Same thing is happening to me. Steps I went through are:

1. fastboot oem unlock

2. fastboot reboot

3. adb reboot bootloader

4. fastboot flash recovery twrp[...].img

5. fastboot reboot recovery

6. From twrp, reboot system

7. adb reboot recovery

8. twrp is gone.

What am I doing wrong? Seems like twrp isn't patching system to prevent it from overwriting the custom recovery.
[Samsung Galaxy Player 4.0, 5.0] niklus101:
So the gp 4.0 can get cm11 and other kitkat based roms and the gp 4.2 cannot get them ? C'mon people this is xda do something.
[Samsung Galaxy Player 4.0, 5.0] Androthan:
THAT is really annoying!

This is XDA, right. XDA is made for developers, hackers, modders, device-increasers,... but definitly NOT for people like you, who use the work from others without being a bit thankful. I mean we're really investing a LOT of time in developing, modding, porting, WITHOUT being payed! This is our hobby, not our job, so dont blame us for it. If you really want CM11 on your player, why don't you develop and learn everything on your own? You may now say "I don't have time for that, I got too much to do" , but we devs also got jobs, other hobbys, girlfriends and families. So maybe start it on your own (that's how I and a lot of other devs began) or don't tell us what to do.

Yours Sincerely,

Androthan
[Samsung Galaxy Player 4.0, 5.0] niklus101:
i understand my mistake and i will actually try to port it even though i have no idea how to do that
[Samsung Galaxy Player 4.0, 5.0] troy5890:
Dude calm down its okay
[Samsung Galaxy Player 4.0, 5.0] jmindset:
Dude they are different devices plus the 4.2 was released AFTER the 4.0. So the support for it isn't as much as the 4.0 and 5.0. I heard that some devs are working hard to port cm11 to the 3.6 and 4.2. I'm grateful that they are. Might be a while but we will likely get it. Until then look at the "holofrenzy ROM" by drakonizer. Its awesome. Reskins your gingerbread to look like cm11 and KitKat. Brought some life to my old galaxy player.
[Samsung Galaxy Player 4.0, 5.0] AndyYan:
VASTLY different devices. If the 4.2 and 3.6 had been using an Exynos3 CPU then they would be getting ROMs in no time, but using OMAP3 CPU effectively limits their processing power and ROM arsenal. You might wanna try porting from Galaxy SL, though.

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Player 4.0, 5.0] Androthan:
Great, thats how I started, if you need help feel free to pm me :)
[LG Optimus G Pro] yankeefan:
How much free disk storage should be on e980 with stock rom. Mine is showing 10gb. everywhere online shows this should be 32gb .

any ideas?
[LG Optimus G Pro] fastwanabe:
Had this issue as well. I had to....

1. flash stock ATT KDZ ... that brought back the 32gb memory.

2 flashed (in my case) e988 rom with TOT file in LGPST.

This way I had all my memory back and the ROM I wanted.
[LG Optimus G Pro] wjazdbitu:
I'm on CM11 and got same issue:

u0_a55@e980:/ $ su
root@e980:/ # df
Filesystem Size Used Free Blksize
/dev 898.8M 128.0K 898.7M 4096
/sys/fs/cgroup 898.8M 12.0K 898.8M 4096
/mnt/asec 898.8M 0.0K 898.8M 4096
/mnt/obb 898.8M 0.0K 898.8M 4096
/mnt/fuse 898.8M 0.0K 898.8M 4096
/system 2.5G 761.8M 1.7G 4096
/cache 1009.3M 18.8M 990.5M 4096
/data 10.1G 3.7G 6.4G 4096
/persist 7.9M 4.1M 3.8M 4096
/firmware 64.0M 55.1M 8.9M 16384
/sns 7.9M 4.1M 3.8M 4096
/factory 15.8M 4.1M 11.7M 4096
/mnt/shell/emulated 10.1G 3.7G 6.4G 4096
root@e980:/ #

/data and /mnt/shell/emulated are basically the same. Any help?
[LG Optimus G Pro] yankeefan:
fixed issue by tot to att and then reset phone, now back to 23gb free
[LG Optimus G Pro] oVeRdOsE.:
but how can I flash a custom ROM and keeping all the free space?

tried sphinx and slimbean, both keep hiding the original internal sd partition.

when I format data through CWM, then I can see my old files on the full 23gb free space.
[LG Optimus G Pro] NardVa:
When you factory wipe and flash a new rom there are old files still on the internal storage that don't get deleted. Those files take up space, but don't read under storage. Get ES File Explorer from the Play Store. Go to device>data>media. There you probably have your old downloads, media and pics. Delete that whole media folder and your space is back. (Backup or copy the files if needed before deleting) You may have to reboot your phone.
[One (M8) Q&A, Help & Troubleshooting] muzia22:
Ee in the UK is notorious for not giving software updates. And this is concerning especially with Android L on its way soon! Anyone have any experience dealing with them at all?
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
They will update the phone, they have to. Not sure where these worries come from. Or s-off and convert the phone to unbranded wwe and have the fastest updates.....

Kinda useless to speculate on this topic, they must update but when they do .... that's something you have to wait for. Patience is the word you need i guess
[One (M8) Q&A, Help & Troubleshooting] muzia22:
I've has a bad experience with them in th email past with regards to the s3 and they literally never updated it ! Was wondering if people had similar experiences on other phones.
[One (M8) Q&A, Help & Troubleshooting] StuMcBill:
I've converted to unbranded wwe and I don't seem to be getting the 4.4.3 update here in the UK?

Hopefully I have everything set up right and I will get the update soon.
[One (M8) Q&A, Help & Troubleshooting] uronfire:
The update hasn't been released yet for UK. Once it's hits UK you will find out here on xda.
[JAMin, XDA Neo, S200 General] nandlal_mk:
Hi all,

Being a newbei in PPC based on windows mobile OS i want a tiny guidence from Prophet users. I am planning to buy ( and shift from synbian base Nokia 6630) my first budget PPC as XDA Neo, but only cocern is its slower proccessor speed of 200 MHz (compared to other having 400 MHz). I am confuse whether it can handle video smoothly and multi-application running simultaneously ( with or without overclocking) ??

Beside this, im an addict of 6630's stereophonic music in headphone( and speaker), so please tell me about the sound of O2 XDA Neo also.Is it comfortable good( i guess it may not match 6630's stereo).

Being a uesr, if u all please guide me , i will be higly thankfull to all of u.

ASAP
[JAMin, XDA Neo, S200 General] abubasim:
Hermes -- not Prophet!

I doubt that the Prophet (XDA neo) would be a good choice if you are concerned about sound quality and processing power to play really smooth video. A better choice would probably be the Hermes (TyTN). The size is almost the same (not counting the size of the hole it leaves in your wallet if you buy it unlocked!) and the keyboard comes handy if you do a lot of texting. And it has official support for stereo Bluetooth. The Hermes is still fairly new so it will probably receive software updates for a while longer. At the same time, while it is still being actively marketed and sold, software support for the Prophet seems to have ended.

I sold my Prophet a week ago and considered the Hermes for a while but decided on the SE P990i instead and I am so much happier for it.
[JAMin, XDA Neo, S200 General] nandlal_mk:
Frnds ,Please Reply.

Thanx
[JAMin, XDA Neo, S200 General] anonimo:
I don't use it for video but I use it a lot as mp3 player connected to a stereo bluetooth headset. I think audio quality is eccellent. I have used a Nokia 6630 in the past and there isn't much to miss. The issues I had with synchronising that phone with Outlook put a giant X on Nokia for me.

Another option for you would be the HTC P3600 which will be in shops in a week or so. It's faster (400 MHz) and it's 3G. (But quite expensive!)
[JAMin, XDA Neo, S200 General] X_Farhad:
i have a qtek s200 and i use Pocket Music for mp3 playback and tcpmp for video, and i use a pair of creative 630 earbud headphones, and i have to tell you, the whole auido/video experience is superb! plus i'm planning to buy a pair of wireless bluetooth stereo headphones which SonyEricsson has recentcly released, i know it's gonna be AWESOME!!

anyway, if you have enough money, then i'd suggest you buy htc TyTn or 3600 or o2 atom exec
[JAMin, XDA Neo, S200 General] nandlal_mk:
frnds, i have read/heard( dont remeber source) that TI OMAP 850 proccessor is dual core and so its performance is nearly acceptable as other intel or samsungs processrs with 400 Mhz speed. Is something like this true ?