yashsingh1/xdaforums huggingface dataset:
[Fire TV General] tselling:
I just re-did my 3 Fire TVs after doing the full bootloader unlock, installing CWM and latest pre-rooted rom. Previously I was just rooted. Anyway this is my procedure that has worked for all 3. I don't mess with the adb key stuff... not sure why you would need it when the install-recovery.sh script is called at boot and not by adb. The mounts will work for both Link2SD (I use the Plus version) and FolderMount. The latest version of Link2SD Plus can now move the obb and external data from the internal fake sdcard to the mounted sdcard1 so you may not need FolderMount anymore unless you want to move a directory like Pictures, Movies, etc.

I have attached my install-recovery.sh file as install-recovery.sh.c (I had to add a .c to the end to get it to attach here).

Note that I use a flash drive with first partition fat32 and second partition ext4. You will need to modify if you don't

have the same partition setup. The umask is necessary to prevent sdcard1 from mounting read only.

Sleep is necessary or mounts don't occur. I am guessing have to wait for other operating system stuff to load.

My install-recovery.sh:

#!/system/bin/sh

#mount usb partitions

/system/bin/sleep 10 # necessary sleep before mounting

/system/bin/mount -t ext4 /dev/block/sda2 /data/sdext2

/system/bin/mount -t vfat -o umask=0000 /dev/block/sda1 /storage/sdcard1

/system/bin/vold

Procedure to install:

First download install-recovery.sh.c and modify if necessary for your partitions.

Next: adb connect <your firetv ipaddress>

Next: adb push install-recovery.sh.c /sdcard/install-recovery.sh

Next: adb shell

Next: su (not needed if fully unlocked bootloader and already have the # promt)

Next: mkdir /data/sdext2

Next: mount -o rw,remount /system

Next: cp /sdcard/install-recovery.sh /etc

Next: chmod 777 /etc/install-recovery.sh

Next reboot the FireTV. '

After reboot you can adb shell into the box and use "df" command to see that they are mounted correctly.

I believe I included all my steps... but always possible I forgot one thing. Let me know if you have any problems.

*** Standard disclaimers apply. Not responsible for any harm to your Fire TV, life, etc. ***
[Fire TV General] tselling:
Just found an even better way to mount external usb stick. It allows link2sd to work and changes /sdcard to mount on the same stick all on one ext4 partition. This means that all the obb's and external data files will automatically be installed on the usb stick. FolderMount not needed. I still use Link2sd Plus to install internal data to the usb stick (automatically) for new apps.

===

my install-recovery.sh is now changed to:

#!/system/bin/sh

# mount usb partitions

/system/bin/sleep 10 # necessary sleep before mounting

/system/bin/mount -o rw -t ext4 /dev/block/sda1 /storage/usb

/system/bin/mount -o bind /storage/usb/link2sd /data/sdext2

/system/bin/mount -o bind /storage/usb/sdcard /storage/emulated

/system/bin/mount -o bind /storage/usb/sdcard/0 /storage/sdcard1

/system/bin/mount -o bind /storage/usb/sdcard/0 /storage/usb/sdcard/legacy

/system/bin/vold

===

Note that I mount the whole usb stick to /storage/usb then I mount the other directories to make data/sdext2 for link2sd and /storage/emulated/legacy for /sdcard. I also mount so that both /storage/sdcard0 and /storage/sdcard1 point to the same place.

I do not mount /mnt/shell/emulated to the usb stick ... because that causes headaches and I had boot to CWM to fix it.

Procedure to install:

First: create usb stick with one big ext4 partition.

Next: download install-recovery.sh.c

Next: adb connect <your firetv ipaddress>

Next: mount -o rw,remount /system

Next: adb push install-recovery.sh.c /etc/install-recovery.sh

Next: adb shell

Next: su (not needed if fully unlocked bootloader and already have the # promt)

Next: chmod 777 /etc/install-recovery.sh

Next: mkdir /data/sdext2

Next: mount -t ext4 /dev/block/sda1 /storage/usb

Next: mkdir /storage/usb/sdcard

Next: mkdir /storage/usb/sdcard/legacy

Next: mkdir /storage/usb/link2sd

Next: cp /sdcard/* /storage/sdcard/

Next: cp /sdcard/.* /storage/sdcard/

Next: cp /data/media/* /storage/sdcard/

Next reboot the FireTV.

*** Standard disclaimers apply. Not responsible for any harm to your Fire TV, life, etc. ***
[Fire TV General] will4958:
I installed the first version of your apk with a 32GB flash drive I partitioned with the first partition of just over 22GB and FAT32, and an ext4 partition of just over 7GB. Both are set to primary and I can link and move apps to the ext4 partition in Link2SD. When I click on Recreate mount scripts, it says Device not found, Make sure you have two partitions and both are set to primary. I formatted my flash drive to be similar to the setup I have on my Tab 3 8.0 and it works fine. I'd prefer to not have to redo the whole thing, since I've already linked a few apps to my ext4. Any thoughts would be appreciated. Thanks.
[Fire TV General] tselling:
You cannot use recreate mount scripts in link2sd. It is meant for sdcards and never finds the usb drive that is why we create our own mount scripts. I am not sure why you are doing that?
[Fire TV General] will4958:
Like I said, I was trying to set it up like my Tab 3:) I have a thing about trying to make my Android devices reflect what's on the other one. My Tab 3 has the same theme and live wallpaper my S4 does. I guess I like symmetry:)
[Fire TV General] tselling:
You will need to do the mount script outside of link2sd and reboot. Make sure you have install-recovery.sh in /etc and make sure you chmod it to 777 or it will not run on boot. After a reboot, if you do a "df" command in adb, you should see that /data/sdext2 listed. If not then you have a problem with the script.

If you do see /data/ext2 in the "df" command, link2sd it should also see the partition. Then install and link what you want (I have link2sd set to automatically link new apps). When you reboot stuff should still be linked. Don't mess with creating mount script in link2sd... it will just error as you saw.
[Fire TV General] marvelous-marv:
Link2SD on Fire TV 1.5

I just rooted my FTV yesterday with the hardware root. Unfornately I was already at the most recent firmware. Link2SD did not work for me, at least not automatically.

In the end I managed to get it mounting automatically. If anyone struggles the same as I did, here is my short Howto:

Prerequisites:

Scripts set up like here

I used "Amazon FireTV Utility App" to get the scripts on my FTV, shouldn't make a difference.

And you'll need Tasker! (Might work without it, but I didn't test it)

After you've completed the steps in the mentioned post, and I mean all of them, you start Tasker.

You create a new Profile that triggers on startup. Then create a new task for that.

First action should be a timer (wait or similar), 2 minutes should do it. If anything breaks, this buys you time to disable Tasker and prevent a bootloop.

The second action has to be Code->Shell. The command has to be:

umount /storage/extUsb/.android_secure && umount /storage/extUsb && /system/etc/install-recovery-2.sh

Mark run as root as well.

I've set the timeout to 20 seconds. In case something hangs it will just be cancelled.

Then do a restart.

After a little over 2 minutes a popup will ask you to allow Tasker Root access, shortly after that the USB connect message will pop up and then you can check in Link2SD whether it has worked.

If you want you may now lower that 2 minute wait. I've set it to 30 seconds now.

My guess why the scripts alone weren't working is that Amazon blocks every other USB drive when mounting. Might be, that they even unmount the drive.

Mounting my ext4 drive manually with "su -c /system/etc/install-recovery-2.sh" worked most of the time, but then FiredTV sometimes crashed completely. When manually unmounting the USB Drive from the ATV Settings the mounting worked perfectly. So I tried unmounting "/storage/extUsb" first, but my FTV wouldn't allow that. The device was busy... It took some time and a "mount" without parameters to see the mount of .android_secure inside the other mount....

Long story short: It may work if you put the two umount commands into install-recovery-2.sh, but I didn't try that. It might very well interfere with the AFT boot procedure and leave your AFT unusable.

Hope this helps somebody.
[Fire TV General] dictorclef:
Sorry for the revival of a five year old thread, but has anyone managed to make it work on a fire tv stick 4k?

EDIT: I managed to make it work. Very simple: just mount your ext4 (dev/block/sdx) drive to /data/sdext2 and don't be an idiot like me, revive a 5 year old thread when I should just have checked if the drive was already mounted XD
[Fire TV General] Intenti0n:
anyway to use link2sd or something similar without root ?
[Galaxy S 5 Themes and Apps] Umair Ahmad:
can anybody port this for our galaxy s5 SM-G900F???

http://xdaforums.com/att-galaxy-s5/themes-apps/mod-johns-touchwiz-laucher-mods-various-t2822791
[Galaxy S 5 Themes and Apps] s8freak:
No need to port just download and flash 900F is compatible with 900A

"No soup for you!Come back one year!!"

Sent from my ViSiX powered AT&T G900A
[Galaxy S 5 Themes and Apps] Umair Ahmad:
hello

i flashed this on rooted s5 g900f???

but it says touchwiz has stopped
[Galaxy S 5 Themes and Apps] s8freak:
Rooted but what Rom? Completely stock? Stock Roms are Odex custom are deodexed launcher is for deodexed Roms.

If you're completely stock flash a, custom stockish Rom which there are several then flash the launcher mod

"No soup for you!Come back one year!!"

Sent from my ViSiX powered AT&T G900A

---------- Post added at 04:23 PM ---------- Previous post was at 04:20 PM ----------

Here's an 900F stockish Rom that hasn't been debloated that works very well is deodexed and you can flash launcher mod

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

"No soup for you!Come back one year!!"

Sent from my ViSiX powered AT&T G900A
[Galaxy S 5 Themes and Apps] Umair Ahmad:
hello

yes rooted stock rom i flashed this ....
[Galaxy S 5 Themes and Apps] Umair Ahmad:
Here's an 900F stockish Rom that hasn't been debloated that works very well is deodexed and you can flash launcher mod

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

"No soup for you!Come back one year!!"

Sent from my ViSiX powered AT&T G900A[/QUOTE]

thank alot man.... means i can flash this rom on my SM-G900F???
[Nexus 4 Q&A, Help & Troubleshooting] Ramayya:
Hello guys,

I am pretty new to rooting & installing custom firmware on my phone. I have done some research and i ended up giving a go to Matr1x from Mathkid95.

Could someone distinguish to me what is the difference between the two version mentioned bellow?

CFS – GPU OC

and

CFS – CM – GPU OC

What is the CM stand for?

I am asking this as I can only install the CFS – GPU OC on my nexus 4. When I try to install the CFS – CM – GPU OC the process finishes and the phone boots to the google logo but after that it soft bricks the phone and i need to flash in the stock image to make it working again.

I have done a binning on the CPU and i have the "fast" version if that helps.
[Nexus 4 Q&A, Help & Troubleshooting] jd1639:
Cm is cyanogenmod. It's a caf based rom, Google caf android. The cm kernel will only work on caf based roms.
[Nexus 4 Q&A, Help & Troubleshooting] Ramayya:
Thanks for the answer.
[HTC Butterfly S] Bareq:
Hi guys......

I have Butterfly s 901e with HBOOT 1.57, when I tried to s-off with firewater, I didn't get anything while in the process..... when I made the last step (root@dlxpul:/ # chmod 755 /data/local/tmp/firewater then root@dlxpul:/ # /data/local/tmp/firewater), I got nothing.... I tried to check data/local/tmp manually in ES File Explorer to see what is going on, I noticed that after pushing firewater through adb it will appear in the TMP folder and after executing root@dlxpul:/ # chmod 755 /data/local/tmp/firewater then root@dlxpul:/ # /data/local/tmp/firewater the firewater file just disappear from TMP folder, and nothing is starting....

please help.
[HTC Butterfly S] ling751am:
Did you unlocked your device?
[HTC Butterfly S] Bareq:
Yes Of course, hTC dev unlock
[HTC Butterfly S] ling751am:
Did you "adb reboot" first?

If u did that and the firewater disappeared in the folder

Make sure u have correctly rooted ur device

Sorry for my bad english
[Sony Xperia L] yash989:
Hi guys this is L-colors theme which is in different colors for now only purploe and green other colors will soon be available.

View attachment 2872065

Features :

1. Flat Design

2. Coloured action Bars

3. Themed action bar, buttons

4. New font

5. New navigation bar Icons

6. New Network Indicators

7. New wallpaper

8. New keyboard [Removed in v2]

9. Themed Calculator

10. New colors in each app

11. New bootanimation

12. Notification sound from L release

13. Ringtone from L release

14. Lockscreen wallpapers

15. Some more changes
[Sony Xperia L] yash989:
L-Purple

Downloads

Android L Purple

L-Green

View attachment 2872077

View attachment 2872078

Downloads

Android L Green

Credits

-> ME

-> B16h22

-> Koulis2000

-> FateNozomi

-> tung91
[Sony Xperia L] przemek4113:
Nice,good work.Thanks for it.
[Sony Xperia L] yash989:
will also be available in other colors soon
[Sony Xperia L] freakzapster:
youre back again dude

thanks
[Sony Xperia L] Navneet Suresh:
Nice work :) :good:
[Sony Xperia L] Chocklety Boyee:
[MENTION=4838935]yash989[/MENTION] bro...you walkman theme for cm.is very preety but..menu button is not themed like that of ibanez7..plz update thanks
[Sony Xperia L] S1N1S73R:
Looks like herathon 5.0 with modified hue...nice one anyways:)
[Sony Xperia L] yash989:
nope u can compare its bot assets
[Sony Xperia L] yash989:
new color added
[Sony Xperia L] ekaj98x:
wow this is really good man! I'll definitely be using this when I get home
[Sony Xperia L] Navneet Suresh:
[MENTION=4838935]yash989[/MENTION]

This thread should have been in

Android > Themes

section.

Its universal theme app for CM11 Theme Engine so it should be there, you will gain more users there. ;) :)

EDIT : You have a thread there, Why not add a link to the main one?
[Sony Xperia L] deepankargupta:
can you port full UI of android L to CM11 and 4.2.2 Stock firmware
[Sony Xperia L] yash989:
its full only no and for 4.2 cant promise will see
[Sony Xperia L] yash989:
http://xdaforums.com/android/themes/theme-redfire-t2831686

check this my new theme
[Sony Xperia L] Amar Vautre:
will these work on jelly bean???
[Sony Xperia T, TL, TX, V] 3clipse:
*sorry if this is the wrong subforum for this

OWNERS OF ANY OF THE FOLLOWING, PLEASE POST!!!

XPERIA V

XPERIA VX

XPERIA VL

XPERIA AX

LT25i

LT25c

I am currently working on a fix for the gamma correction problem on these models after cross flashing.

I need the owners of WORKING phones with

ANY firmware

to post the information listed below.

This will

NOT

change your phone in anyway.

INSTRUCTIONS/THINGS I NEED:

Restart phone

, open terminal, type:

su
dmesg|grep panel >/mnt/sdcard/dmesg.txt
dmesg|grep panel

Copy the two scripts files in the zip attached to this post to your phone.

readnvm_old.sh

and

readnvm_sharp.sh

Type into terminal:

su
cd /sdcard
sh readnvm_old.sh
sh readnvm_sharp.sh

The scripts just read some NVM data to a txt file. Screen flashing is normal.

Take a picture of phone's screen for reference. (Post of different screen models)

REQUIREMENTS:

Root (https://towelroot.com/ or old method)

terminal emulator (Like this: https://play.google.com/store/apps/details?id=jackpal.androidterm)

PLEASE make a

single post or PM me

with the

dmesg.txt

,

nvm_sharp.txt

, and

nvm_old.txt

files!

Thanks for any help!

My previous work on this issue: http://xdaforums.com/showthread.php?p=50776261
[Sony Xperia T, TL, TX, V] 3clipse:
RESERVED

RESERVED
[Sony Xperia T, TL, TX, V] lux44:
1000 thanks for picking this up! :good:

I have one colleague with functioning phone, not rooted. If all else fails, I could persuade him to root his phone.

I hope somebody else posts the info before that.
[Sony Xperia T, TL, TX, V] tajimura:
Running CM11 latest nightly. dmesg|grep panel > path_to_txt_file gives nothing - created txt file is just empty

Sent from Asia

---------- Post added at 11:47 PM ---------- Previous post was at 11:40 PM ----------

nvm_sharp:

Spoiler content hidden.

nvm_old:

Spoiler content hidden.

Sent from Asia
[Sony Xperia T, TL, TX, V] tajimura:
Got dmesg, here it is:

Spoiler content hidden.

The phone is SXV (LT25I, tsubasa).

Sent from Asia
[Xposed Framework Modules] MOHAMMED NAEEM:
On this site, you can browse and download modules for the*Xposed Framework.

http://repo.xposed.info/

website of xposed framework's and modules, where you can get information of each modules.

Thank you.

Hit Thanks ?
[Xposed Framework Modules] kingvortex:
Yes. That's the official repository for Xposed. Everyone knows about it.
[Xposed Framework Modules] GXGOW:
And what is the point of this thread? You didn't ask a question and you didn't post anything useful.
[Xposed Framework Modules] laurorual:
I though the same LOL
[Xposed Framework Modules] Naddict:
Ok, thanks for the info...but we are here at XDA, not offsite elsewhere???

Not very classy = thread closed....
[Galaxy S III Mini Q&A, Help & Troubleshooting] cvkef:
Hi everybody,

The vibration motor of my SGSIII Mini stopped working. It happened after I updated the Recovery to TWRP v2.7.1.1 by NovaFusion.

* CM 11 by NovaFusion [20140724]

* TWRP v2.7.1.1 by NovaFusion [20140720]

Flashing a stock ROM did not fix anything. Maybe pointless but also tried to flash another Recovery. Nothing changed.

Does anybody have an idea how to bring it back? Should I go for a vibration motor replacement?

Thank you!
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Does it still vibrate when you turn it on?

I mean that little vibrate before bootlogo appears.
[Galaxy S III Mini Q&A, Help & Troubleshooting] cvkef:
No. No vibration at all. Anywhere.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
That vibrate is there to tell that bootloader is loaded, before os loads, so if no vibrate is there then it's probably the motor or a loose connector to it.

Unless you got warranty left you could try to change it. They're probably cheep on eBay.

Otherwise take it to service.
[Galaxy S III Mini Q&A, Help & Troubleshooting] cvkef:
Thanks man. I'll take it for service probably.

Though, still wondering why it happened just after a recovery installation.
[Galaxy S III Mini Q&A, Help & Troubleshooting] HMIDA92:
tap *#0*# in phone keyboard and click vibration (to test vibrator in stock rom, other rom i didnt try it)
[Galaxy S III Mini Q&A, Help & Troubleshooting] mastermind256:
I have the same problem

So, does the vibration works on your phone right now?
[Galaxy S III Mini Q&A, Help & Troubleshooting] cvkef:
Nope. I have to find some time and give it for service. What happened with yours exactly? Do you have vibration when the phone powers on and boots?
[Galaxy S III Mini Q&A, Help & Troubleshooting] mastermind256:
I don't know what happened to my device, it just stopped vibrating out of a sudden.. Maybe the device felt upset because it knew that I want to buy another phone.. :laugh::laugh:

Just out of a sudden no vibration during phone calls, messaging, power on / off.. My device is rooted by the way..

Sometimes, the vibration came slowly when I received notifications, but then disappeared again.. I don't know whats wrong.. maybe hardware related..
[Galaxy S III Mini Q&A, Help & Troubleshooting] cvkef:
the same as me. it's just died.
[Dell Venue] ninjaax:
I had booted up my new Dell Venue 7 (with Android 4.2) for the first time, and it was working pretty well. I was about to install some apps when I noticed "System update, touch to install". I did just that and it downloaded, rebooted, and started installing, with nothing seeming to be wrong. I patiently waited for it to install, and right at the end of the installation it stopped and displayed an error message- which amounted to an Android bot in a 'broken, shut down, stwaming' pose and the message "Error."

And it was frozen.

I held down the power button to turn it off and then turned it back on to see the dell logo for a split second, then a USB symbol for a split second, then it shuts off. This now happens every time I boot.

I tried using Droidboot to reset the installation. I can get that to work, but after I select Recovery it reboots, and after the Dell logo, gives me the "pic of the dead android" error message with the message "No command." This is another freeze screen, as I can't get further without rebooting.

All I want is for this thing to boot, I don't care what version of Android it runs at this point. Any assistance in getting the thing to boot would be greatly appreciated. I won tthis thing in a contest, I don't want to be the proud recipient of a brick.
[Dell Venue] Terry Kennedy:
Take a look at my response to another user with the same problem here.
[Dell Venue] xxxx-g-xxxx:
Well i got this problem by following this guide in first place :

http://xdaforums.com/showpost.php?p=51090059&postcount=3
[Dell Venue] tomtom1265:
Did you get this fixed?

[MENTION=4821597]social-design-concepts[/MENTION] has released a newer version of his tool, that seems to fix problems users were having with older versions.

http://xdaforums.com/android/development/intel-android-devices-root-temp-cwm-t2975096
[Dell Venue] xxxx-g-xxxx:
Hi,

Well i finally did. What got me into that situation was a issue with drivers, so lesson learned.

- If you ever get into the bootloader, never select manually the "Recovery" (let the tool handle it) :) or atlast not if you are new to this thing.
[Dell Venue] jumpup:
FWIW, http://xdaforums.com/showthread.php?t=2681793 has a link to a rooted, working 4.4.4 factory ROM. I'd recommend everyone grab a copy since Dell hasn't made one available via support.
[Dell Venue] frnndhrnndz:
check this URL, on second PDF brings a steps to recover from brick, maybe can help you.

opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/Doc/
[Galaxy Tab S General] mitchellvii:
The Tab Pro 10.1 has tons of development activity. Tab S 10.5 not so much (i.e., practically none as far as roms). Just private messaged the top Developers in the Tab Pro forum asking if their work there can be ported to the Tab S. Hardware other than the screen is very similar. Seems like it should be doable (although I'm not a developer and there may be complications of which I am unaware).

Anyway, flare fired, emergency beacon activated. Let's hope we can get some port love here and get a solid rom or two going.

** They may need some guinea pigs to test things out. But these are extremely experienced recognized Devs and you should take some comfort in that.

UPDATE: All development for the 10.1 is for the SM-T520 which is the Exynos 5 wifi model. Should be no issues there.

TAB PRO 10.1:

Chipset	Exynos 5 Octa 5420

CPU	Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7

GPU	Mali-T628 MP6

TAB S 10.5:

Chipset	Exynos 5 Octa 5420

CPU	Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7

GPU	Mali-T628 MP6

Identical.

UPDATE:

Good news folks! Our little project here has resulted in a working, smooth and pretty dammed fast rom for the 10.5 (US Version). It is still in Beta but based upon my experience, everything seems to be working.

Special appreciation to [MENTION=5883270]Shaheer[/MENTION] who came here from the 10.1 Pro Forums and without the benefit of his own device built a working rom for us. My thanks also go out to all the smart people who teamed with him to make it happen.

Go give it a flash. It only gets better from here :)

http://xdaforums.com/galaxy-tab-s/development/sm-wip-rom-t2832360

** Update: Have just heard from [MENTION=1429197]mrwookie6379[/MENTION] in the Tab Pro 10.1 forums. He has also expressed interest in developing for us. Cool.
[Galaxy Tab S General] Orphee:
There is a big difference between tab pro and tab s.

Maybe I'm wrong but the development is only on snapdragon version of the tab pro...