yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Iz3man:
Hey everyone.

I have the Bell (Canadian) note 3 and I just tried the smooth motion video recording. Very neat, but the playback is very garbled and distorted. When I play it on my PC it's fine.. Could this be a flaw in the phone that could cause issues?

Anyone else have or hear about this?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] BeastSpencer:
try doing a factory reset or flashing to stock via odin. if it doesnt work, just exchange your phone
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Iz3man:
I resolved it. Turns out another video playback app was set as default and it cannot handle the video. Only stock samsung app is able.

Works great now.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] DrAzzy:
Video playback on android is where video playback on PC was a decade and change ago: A maze of incompatible codecs and video playback tools, and nowhere is there any decent explanation of how the whole mess is supposed to work together or why it sucks so much.

It was just as bad on PCs before. I remember having to have like half a dozen different video players, because each one could handle some - but not all - video formats. And you couldn't rely on file associations either (as is the case on android today), because all the video formats that we talk about are just "containers", which can contain video data encoded with any of a number of different codecs. So you can't say "Play the .mp4's with this player, the .wmv's with the other player" - but that's the level that file associations work on.

Suffice to say, my experience with making my existing video library play on android has been very frustrating, and there are still numerous videos that play fine on windows which I haven't been able to play on android. Naturally, just like on windows in the dark ages, none of the players provide useful feedback on what went wrong - a failure results in black screens, or no sound, or a force close, or occasionally a useless error. God forbid they say something like "the required codec ______ is not available", so I'd know what I needed to look for. Is there a reason for this? Who knows?!

It probably doesn't help that google has a financial interest in it being difficult to play video from sources other than their Google Play Movies store and Youtube.
[HTC One Mini] abracadabra19:
hi for all

am have big problem with one mini after unlock bootloader and whem am try to flash custom recovery phone hang and now whem am try to flash any rom by recovery give me failed by twrp and cwm and am havnt ruu file for it

phone info

m4_u_pvt ship s-on

hboot -2.22.0000

radio-1.24.40e

cid is HTC__038

build no 3.10.707.3

on recovery give e

E:cant mount cashe

cant mout open cashe

please help me how ican slove any one have this ruu for india
[HTC One Mini] cmvienneau:
Are you s-off?

---------- Post added at 05:49 AM ---------- Previous post was at 05:47 AM ----------

Nvm.lol i see you are not. If you have twrp recovery. Go into wipe and press the wipe data button. Enter "yes" let it format then go to advanced wipe and only put a check by cache.
[HTC One Mini] kyasu:
I also have the same problem. this is because the emmc partition was changed from 4.4.

I have a HongKong version (HTC__622) and EMMC info of 4.3 (2.12.708.3) was:

$ adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 85fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 29fffe00 00000200 "cache"
mmcblk0p35: 2d8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
mmcblk0p27: 00004000 00000200 "control"

Now EMMC info of 4.4 (3.10.708.4) is:

$ adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"

You have to modify ramdisk of recovery image.
[HTC One Mini] cmvienneau:
Nope you flashed a firmware package from an htc one. Hahahaha
[HTC One Mini] kyasu:
I flashed an OTA update (OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip).

Any useful information to share?
[HTC One Mini] cmvienneau:
Do you have soff or access to custom recovery or unlocked bl?
[HTC One Mini] kyasu:
My one mini is working perfectly as 4.4 (3.10.708.4) and the partition modified TWPR 2.6.3.0 by myself is also working.

And my home build CM11 with modified partition is working perfectly.

My conclusion is that an asian version of one mini (or my one mini only) has new partition from 4.4 (3.10.708.4).

Unbelievable!
[HTC One Mini] cmvienneau:
what do you mean modified partition?
[HTC One Mini] kyasu:
I modified /etc/fstab. the following is a diff of CM11:

diff --git a/rootdir/etc/fstab.m4 b/rootdir/etc/fstab.m4
index d83a00a..5bb45c9 100644
--- a/rootdir/etc/fstab.m4
+++ b/rootdir/etc/fstab.m4
@@ -8,12 +8,12 @@
/dev/block/mmcblk0p17 /firmware_q6 vfat ro,shortname=lower wait
#/dev/block/mmcblk0p18 /firmware_wcnss vfat ro,shortname=lower wait

-/dev/block/mmcblk0p31	/boot	emmc	defaults	defaults
-/dev/block/mmcblk0p32	/recovery	emmc	defaults	defaults
-/dev/block/mmcblk0p24 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
-/dev/block/mmcblk0p33	/system	ext4	rw,noatime,barrier=0	wait
-/dev/block/mmcblk0p34	/cache	ext4	nosuid,nodev,noatime,barrier=0	wait,check
-/dev/block/mmcblk0p35	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard	wait,check,encryptable=/dev/block/mmcblk0p29
+/dev/block/mmcblk0p33	/boot	emmc	defaults	defaults
+/dev/block/mmcblk0p34	/recovery	emmc	defaults	defaults
+/dev/block/mmcblk0p25 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
+/dev/block/mmcblk0p35	/system	ext4	rw,noatime,barrier=0	wait
+/dev/block/mmcblk0p36	/cache	ext4	nosuid,nodev,noatime,barrier=0	wait,check
+/dev/block/mmcblk0p37	/data	ext4	noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard	wait,check,encryptable=/dev/block/mmcblk0p30

# USB Storage
/devices/platform/msm_hsusb_host/usb	auto	auto	defaults	voldmanaged=usbdisk:auto
diff --git a/rootdir/etc/remount.m4 b/rootdir/etc/remount.m4
index c5960dd..8789c5e 100644
--- a/rootdir/etc/remount.m4
+++ b/rootdir/etc/remount.m4
@@ -3,4 +3,4 @@
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

-/dev/block/mmcblk0p33	/system	ext4	remount,ro,noatime,barrier=0	wait
+/dev/block/mmcblk0p35	/system	ext4	remount,ro,noatime,barrier=0	wait
[HTC One Mini] cmvienneau:
Hmm? That's weird because even stock I never had p036 or 37
[HTC One Mini] GixxGle:
How, help please

I'm new, How you do? or Link Please.

Thanks
[HTC One Mini] tirlol:
Try this one
[HTC One Mini] GixxGle:
thanks for your reply :)

I'm not advanced user (new noop). i not modified /etc/fstab by myself :( , can you guide me step by step !?
[HTC One Mini] cmvienneau:
hey bro.. i can confirm its not an asian issue i recieved the att update. it seems as if maybe they have merged sources with the htc one? it looks as tho the partition schemes after the 4.4.2 update from att are the same as the original htc one..please correct me if im wrong?
[HTC One Mini] kyasu:
Try another derived from http //mdmower.cmphys.com/twrp-m4/
[HTC One Mini] kyasu:
Steps for installing cm11 to new partition after ota 4.4.2 update:

Flash recovery that supports new partition.

(TWRP2630-KKOneMine.zip or twrp-2.7.0.5-m4kk.img.zip)

Download the latest nightly from http //download.cyanogenmod.org/?device=m4.

(cm-11-201404xx-NIGHTLY-m4.zip)

Edit nightly zip file by replacing boot.img and META-INF/com/google/android/updater-script with attached files.

(boot.img and updater-script(updater-script.zip))

Flash the editied nightly zip file from the recovery.
[HTC One Mini] morschesholz:
Great! :good::good::good:

This saved my a**. I was tinkering around for hours and couldn't get the recoveries to work properly. Thought I was going mad.

What a relief. :D
[HTC One Mini] morschesholz:
[MENTION=4861355]kyasu[/MENTION]: The 2.7.0.5 version isn't able to mount my encrypted data partition. It asks for the password and then keeps telling me the password is wrong (which definitely isn't). The phone is booting fine and during startup my password is accepted. Do you have any ideas? Is there more modification needed to match the new partition layout?

Btw, the 2.6.3.0 version linked in this thread isn't working at all. Doesn't ask for a password to decrypt /data in the first place. And /system can't be mounted, too.
[HTC One Mini] romy134:
If I am on stock 4.4.2 with twrp-2.7.0.5-m4kk.img.zip recovery can I flash [4.4.2][Sense 5.5][3.10.401.4][Stock]? so far iv tried 3-4 times and it never works im HBOOT 2.22 s-off. or will i need to use a different rom? should have just stayed on the ddoxed 4.4.2 instated of going stock...
[HTC One Mini] morschesholz:
As I already said over there (http://xdaforums.com/showthread.php?t=2708997) you can. But you have to edit the update-script within the update zip file to match the new partition layout.

So you have to change every line referring to one of the partitions which have changed now: system (previously mmcblk0p33, now mmcblk0p35), data (previously mmcblk0p35, now mmcblk0p37) or boot (previously mmcblk0p31, now mmcblk0p33).

As far as I know for now you can use the boot.img provided with the [4.4.2][Sense 5.5][3.10.401.4][Stock] as well as the boot.img from your recovery backup (that is, the stock kernel with absolutely no modifications). Since you're S-OFF you're probably ok with just flashing the zip from the recovery. Nevertheless you could play it safe and flash the boot.img via fastboot after you have done flashing.
[HTC One Mini] romy134:
awww ok, not sure how to do that, so I will probably run the RUU go back to 4.2.2 then unlock, and flash Dedoxe 4.4.2 tomorrow, thx for the info
[HTC One Mini] cmvienneau:
Do y'all need a modified boot.IMG for cm11? I can post one
[HTC One Mini] morschesholz:
Well, I suppose it would help some people. There is already one in #16 on the previous page. But probably a new one from the latest nightly would be nice.

Personally I still stick with the stock rom. At the moment I'm trying to figure out why TWRP isn't able to unlock the /data partition which I encrypted on the stock system before. Maybe HTC modified something with the encryption process?
[HTC One Mini] cmvienneau:
Did you try using dd if=/dev/zero of=/dev/block/mmcblk0p37 from terminal in twrp then reformat?
[HTC One Mini] kyasu:
I just modified fstabs of the original 2.7.0.5 as follows:

diff -urN ramdisk-contents.orig/etc/recovery.fstab ramdisk-folder/etc/recovery.fstab
--- ramdisk-contents.orig/etc/recovery.fstab	2014-04-03 11:24:52.580058600 +0900
+++ ramdisk-folder/etc/recovery.fstab	2014-04-03 11:34:30.489058600 +0900
@@ -1,8 +1,8 @@
# mount point fstype device [device2] [parameters]
-/boot emmc /dev/block/mmcblk0p31
-/recovery emmc /dev/block/mmcblk0p32
-/devlog ext4 /dev/block/mmcblk0p24
-/system ext4 /dev/block/mmcblk0p33
-/cache ext4 /dev/block/mmcblk0p34
-/data ext4 /dev/block/mmcblk0p35
+/boot emmc /dev/block/mmcblk0p33
+/recovery emmc /dev/block/mmcblk0p34
+/devlog ext4 /dev/block/mmcblk0p25
+/system ext4 /dev/block/mmcblk0p35
+/cache ext4 /dev/block/mmcblk0p36
+/data ext4 /dev/block/mmcblk0p37
/external_sd auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable
diff -urN ramdisk-contents.orig/fstab.m4 ramdisk-folder/fstab.m4
--- ramdisk-contents.orig/fstab.m4	2014-04-03 11:24:52.590058600 +0900
+++ ramdisk-folder/fstab.m4	2014-04-03 11:32:44.026058600 +0900
@@ -1,8 +1,8 @@
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
-/dev/block/mmcblk0p31 /boot emmc defaults defaults
-/dev/block/mmcblk0p32 /recovery emmc defaults defaults
-/dev/block/mmcblk0p24 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
-/dev/block/mmcblk0p33 /system ext4 rw,noatime,barrier=0 wait
-/dev/block/mmcblk0p34 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
-/dev/block/mmcblk0p35 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard wait,check,encryptable=/dev/block/mmcblk0p29
+/dev/block/mmcblk0p33 /boot emmc defaults defaults
+/dev/block/mmcblk0p34 /recovery emmc defaults defaults
+/dev/block/mmcblk0p25 /devlog ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait
+/dev/block/mmcblk0p35 /system ext4 rw,noatime,barrier=0 wait
+/dev/block/mmcblk0p36 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
+/dev/block/mmcblk0p37 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0,discard wait,check,encryptable=/dev/block/mmcblk0p30
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=usbdisk:auto

Something wrong?

I will upload cwm 6.0.4.7.
[HTC One Mini] kyasu:
Here is a clockworkmod recovery 6.0.4.7 for	new partition layout compiled from cm11.
[HTC One Mini] kyasu:
Here is an updated boot.img for new partition layout.
[HTC One Mini] kyasu:
Here are fstab.m4 and recovery.fstab.
[HTC One Mini] morschesholz:
Thanks for the tip. Did it. May have helped or not. I'm not sure.

Just to share my insights so far. After completely erasing /data I flashed CM11 (with adjusted boot.img thanks to [MENTION=4861355]kyasu[/MENTION]), encrypted the /data partition again and rebooted to TWRP (the adjusted version) and voilà, it works. TWRP can unlock the encrypted /data partition. So everything seems fine. Just don't know exactly whether it is due to the dd-ing of the data partition or the result of having CM on the device now.

However I'm still wondering what's the reason for this strange behaviour. Since everything worked so flawlessly with CM I suspect HTC having modified the encryption process. I'd usually say this is quite unlikely but there is another thing I noticed: Running the encryption with the Stock ROM took less than 10 minutes. But with CM11 it took about 30 minutes or even more. In both cases the data partition was almost empty though it shouldn't make any difference since I expect the encryption to run on block level and therefore include the empty parts of the partition anyway.

That's it for now. Probably I stay with CM now and hope that the remaining bugs get sorted out soon. Runs pretty well already.

Thanks to [MENTION=4861355]kyasu[/MENTION] again for providing new recoveries and boot.img.
[HTC One Mini] romy134:
quick question im trying to run RUU nut i get 155 error, heres my info from my bootloder

Relocked

S-off

hboot 2.22.0000

radio 1.25.40g.00.19

os 3.10.502.3

ruu is ofr 1.32.502 is that why i am unable to run it? and is there a way to get back to stock 4.2.2? im having a hard tim flashing any roms do to the partition changes from 4.4.2
[HTC One Mini] morschesholz:
Have a look over there for error codes from running RUU: http://xdaforums.com/showthread.php?t=2659109

I'm not sure, if your RUU is too old. Probably it can't run properly due to the modified partitions, too.

Don't you have a nandroid backup from your stock 4.4.2?

I can provide one. It's from a German 4.4.2 (3.10.111.4). Don't know if it will work on your device (there could be connectivity issues). However, I can't upload it until tonight.
[HTC One Mini] romy134:
TBH i just want to get deodox of this rom [4.4.2][Sense 5.5][3.10.401.4][Stock]. would a nandroid from another person be able to get me to this>?
[HTC One Mini] cmvienneau:
I can upload a nandroid of the latest cm build I'm running for all of you. Make it easier.

---------- Post added at 03:09 PM ---------- Previous post was at 02:52 PM ----------

Actually Ill upload a the boot.IMG and meta.inf folder. Then all you have to do is download the newest cm11 build unzip and replace the files i give you with the ones in the new cm11 you download rezip and flash.
[HTC One Mini] morschesholz:
Additionally here is a ready to flash version of the 0403 CM11 nightly for the new partition layout: https://dl.dropboxusercontent.com/u/5035075/m4kk/cm-11-20140403-NIGHTLY-m4kk.zip (MD5: 3bc8d4694f1ee80992665138b252431f)

Remember you need the modified TWRP 2.7.0.5 to flash this successfully (or the modified CWM 6.0.4.7, but didn't test it).

Maybe I will make another one from one of the latest nightlies in the next few days.
[HTC One Mini] cmvienneau:
Well there ya go just use the files from this zip. Thanks saved me some drive space:)
[HTC One Mini] morschesholz:
Actually the deodexed 3.10.401.4 from over there is a 3.10.631.5. Nevertheless, here you can find a ready-to-flash version for the new partition layout: http://xdaforums.com/showthread.php?p=51779967
[HTC One Mini] cmvienneau:
If your actually a member of xda. The only reason for stock is warranty.lol after all custom is what is all about.
[HTC One Mini] morschesholz:
What changes did you made to boot.img? Did you only modify the ramdisk? Or did you modify the kernel, too? If yes, how did you do that?

I only know the way of splitting boot.img, modifying fstab of ramdisk and merging ramdisk and kernel back to a boot.img.

Or did you build the kernel from source?

I just wanted to fully understand the changes you made. So I took your boot.img, splitted it and compared the files to a splitted boot.img from the CM11 nightlies. Strangely the kernel files (zImage) differ, that is, they have a different MD5. So does this mean there have been changes to the kernel, too?
[HTC One Mini] kyasu:
I just modified fstab but compiled from source for my hobby.

You can edit boot.img by using Android Kernel Kitchen (http://xdaforums.com/showthread.php?t=1659584).

Here is a modified 0411-NIGHTLY boot.img that is edited by using Android Kernel Kitchen. I just replaced fstab.m4 in ramdisk. The kernel file (zImage) is the same as the original.
[HTC One Mini] morschesholz:
Thanks for clearing this up. :good: :good: :good:

So I know what to do whenever I want to flash a new nightly.

Compiling from source would be an option, too, yeah and is quite a cool thing. :cool:

I'm afraid I'm just too lazy to this everytime a new nightly pops up. :D
[HTC One Mini] GixxGle:
Ohhhhh lay!, i'll try today.

Thanks in Advances.

----------------------------------

Big Thanks Again kyasu for your recommend.

My HTC One mini Life Again.
[HTC One Mini] GixxGle:
Dear kyasu

Your update-script.zip can i apply for OTA update?

(OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_WWE_3.10.707.3-1.32.707.2_R_release_351633.zip)

i success to update hboot 2.22 from cmvienneau (http://xdaforums.com/showthread.php?t=2584810)

If i try what your concern? :confused:
[HTC One Mini] kyasu:
My update-script.zip cannot be applied for OTA update.

OTA file you specified contains hboot 2.22.

So if you are using stock rom, you can update by the OTA file and modded hboot 2.22 will be replaced by the stock hboot 2.22 (maybe).
[HTC One Mini] GixxGle:
:good:

:good::laugh:

Thanks
[HTC One Mini] silverbox750:
Boot loop help

Hi there,i used the fuu for stock rom and recovery,i was runnning 4.4.2 hboot 2.21 s off

and after fuu phone was on boot loop so i run the 4.4.2 fuu and phone still in boot loop.

i made a back up via twrp and saved it in my pc,now no backup in the phone and phone

on boot loop.

how can i push the backup to restore via twrp..? if its possibile

or how can i just fixed that bootloop.?

please help..
[HTC One Mini] lfe.zaius:
Corrupt emmc

Apologize for reviving an old thread, however this seems to be the correct path to fix my BRICKED M4.

UNLOCKED M4 S-OFF CID 11111111 HBOOT 2.22

Have failed to write new boot and recovery via fastboot. NO recovery image to boot into from fastboot. Unable to get adb running. Posted below terminal logs of various commands. Any help would be appreciated, thanks!
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] almaqhor:
DEAR ALEX

TRY TO MAKE THIS V 2.03a.64WWE

ITS BETTER THAN ANY OTHER

NO NEED TO EXT ROM

JUST UNLOCK IT AND COPY ALL YOUR ROM AND FORMAT IT

INSTALL TO FLASH DISK AND MAKE BACK UP ITS BETTER
[Android Q&A, Help & Troubleshooting] Kevin Koli:
Sir i downloaded thundermiuiv4update.zip rom for micromax a91. But sir when i try to install it shows no os installed. please sir i need a proper suggestion on it. After rebooting my phone gets stuck on ninja image and dont go forward. And please can u suggest some roms for micromax a91
[Android Q&A, Help & Troubleshooting] droid man:
Dude if you are still stuck use this as it would help you......:good:
[Android Q&A, Help & Troubleshooting] Kevin Koli:
Sir can u please send me some links of custom rom for micromax a91
[LG Optimus G (International)] Hardtron:
It's possible port to OG?

http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
[LG Optimus G (International)] jancis201991:
Maybe.
[LG Optimus G (International)] Hardtron:
I have an Xperia play, and have many ports in xda. Xperia play don't get update, still in GB. But developers port a lot of original firmwares of a lot Xperia devices.... Awesome if possible made to E975 to
[LG Optimus G (International)] nch26:
If we are talking about port official kdz from g2 to optimus g is not posible. Lg g2 is very dofferent in hardware. Xperia play, neo, ne v ray etc they all have the same hardware 1 ghz single core gpu adreno 205. That why they can port things
[LG Optimus G (International)] hasan4791:
G2 is difficult but i hope with G pro chances there...but still waiting for boot.img file to port..!!
[LG Optimus G (International)] vntoan78:
Looking forward a port rom:good:
[T-Mobile Samsung Galaxy Note 3] calebcaudill:
Is there anyway to get the stock camera/gallery app on an AOSP rom? I really don't want to have to keep a touchwiz just for the camera.
[T-Mobile Samsung Galaxy Note 3] dramitt_live:
No way... But there are other options like the lenovo super camera, focal, snap camera or camera zoom fx maybe?

Enviado desde mi SM-N900T mediante Tapatalk
[Sprint Samsung Galaxy Note 3] Lexlagger:
Hi guys, did some digging last night, couldn't find anything... Asking now because time is a factor as I currently have no phone coverage...

I purchased a Note 3 with SlimKat on it last night. Had sprint check the ESN and it's fine, we tried to activate it but only the internet (Data) portion of the phone will activate. I can't get the actual phone service to activate. (Your account can not be validated. <--error message over the phone when trying to make any call)

Here are my questions:

1. Is there a way to force a refresh on slimkat so I can activate it? Or to manual go in and change the settings?

Sprints ## codes don't work with this OS.

2. Where can I find a factory Sprint rom (or one that is known good and will activate?)

I have TWRP and used it to clear the phone and re-instal SlimKat and the small app package they have with it.

Please help as I am running out of touch and need to contact some people for work today.... Thanks in advance.
[Sprint Samsung Galaxy Note 3] JonSCSL:
You will be better off wiping the phone then install stock Unrooted kit kat then activate. Once you activated root and then flash what you want.