yashsingh1/xdaforums huggingface dataset:
[MDA, XDA, 1010 General] xpq:
I'm sorry for my polish here but it's is the easiest way to explain this to him.

Co do pierwszego [formatowania karty] mam moja karte pamieci juz od okolo miesiaca i nigdy nie spotkalem sie z takim problemem, a i na forum rzadko o tym bywa, wiec chyba nie jest to rzecz pospolita.

Po drugie, brak mozliwosci zabezpieczenia karty przed zapisem pojawil sie takze u mnie, wiec nie sadze aby to byla wina bledu Twojej karty.

Po trzecie [niemoznosc zapisania systemu na karcie pamieci] - do tego potrzebujesz pliku itsutils.dll ktory mozna znalezc na FTP tutejszego serwisu - musisz go wrzucic do katalogu \Windows na swoim XDA.

Co do nielapania zasiegu to tez mam ten problem [na tym samym modelu]. Jest to wina radia, ktore jak chcesz ryzykowac to mozesz zmienic, ale ryzykujesz wtedy zupelne uszkodzenie modulu telefonicznego w XDA.

Co do podczerwieni to na to pomaga wlaczenie jej w ustawieniach i miekki restart systemu [chociaz i tak nie zawsze]
[MDA, XDA, 1010 General] angree:
i had enough of wm2003 and its formats. Changed to 2002 and no formats yet (2 weeks). Its a shame i cant have 2003 :/
[MDA, XDA, 1010 General] da_jon:
Not saying I am an expert but WM2003SE does not have that problem, maybe you should try going up from WM2003 instead of down. Just a thought.
[Xoom Android Development] LOGMD:
For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)

4.4 images are building im coming here for developers help on getting this rom working

i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...

this post will get more colorful and easier to read over time:

Below is a quote from my google+ post on Xoom Community (join it.. its a great place)

BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!

we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!

PROGRESS

I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel

DISCLAIMER

I (LOGMD) am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.

Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary ;)

REPARTITION

SYSTEM.IMG

BOOT.IMG (kernel, ramdisk etc)

THREADS OF LIFE

(words stolen from Shadows Fall Album)

This is where you and I should use as a starting point for homework ;) using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!

GOOGLE+

+LOGMD | +XDADevelopers | +XoomOwners

XDA-Forums

BLOG

OTHER (follow me)

Twitter | Facebook
[Xoom Android Development] logitechor:
I wish you luck. As your skill and luck is our luck.
[Xoom Android Development] notbrodie:
subbed! anticipating great things!
[Xoom Android Development] TrustAugustus:
way to be!! Super excited. Need guinea pigs? I'll help :D
[Xoom Android Development] LOGMD:
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
[Xoom Android Development] LOGMD:
I stupidly did not reserve posts so heres one more ;)
[Xoom Android Development] pots22:
boot.img

For the kernel, why don't ask to ElementalX ?
[Xoom Android Development] matt4321:
If we have a system.img but it's to large to flash through fastboot,

thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX

would that work?

---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------

Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://xdaforums.com/showthread.php?t=633246

I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
[Xoom Android Development] Schischu:
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
[Xoom Android Development] sheenswizner:
Incredible news!!

Love to see KitKat on Motorola Xoom!
[Xoom Android Development] publicanimal:
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.

I uploaded it here if you'd like to test it out
[Xoom Android Development] pots22:
TWRP

So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo

I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.

I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.

So do you thing we need another TWRP or the TWRP big part is ok?
[Xoom Android Development] LOGMD:
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
[Xoom Android Development] hawkstorm:
Elemental-X seems to have updated to beta with support for big partition.
[Xoom Android Development] pots22:
4.4

Exactly, http://www.androidfilehost.com/?fid=23252070760974877

Now we have a bigpart partitioning, a bigpart Kernel

So what needed for start a 4.4 kitkat test build?
[Xoom Android Development] Cameron581:
Technically we didn't even need the big part
[Xoom Android Development] hawkstorm:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
[Xoom Android Development] Cameron581:
That makes no sense he removed apps and was on a parted kernel
[Xoom Android Development] Domunus:
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.

They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
[Xoom Android Development] pots22:
4.4

Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2

http://download.cyanogenmod.org/

All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
[Xoom Android Development] Hoochie_Coochie:
What size is it installed, and with gapps?

Cm10.1 is 134mb download but installed with gapps can be >220mb

Some jellybean ROMs on the Xoom only left 5mb on the system partition after install and gapps.

I think the main problem is the chipset and kernel anyway
[Xoom Android Development] realjumy:
The problem is not the size of the rom. The problem are the GApps, that become too big...
[Xoom Android Development] Cameron581:
Why is it so big I don't believe that it is compiling correctly I have not had a ROM that big for the 3 devices I compile for
[Xoom Android Development] Schischu:
I finally got to see the boologo. :)

Unfortunately nothing else...

EGL createContext fails later with EGL_BAD_ALLOC, so no homescreen.

D/Atlas ( 434): Loaded configuration: SliceMinArea (768x768) flags=0x2 count=34
W/linker ( 434): gralloc.tegra.so has text relocations. This is wasting memory and is a security risk. Please fix.
E/gralloc ( 434): init_rotation_ctx: NvDdk2dOpen failed (6)
W/GraphicBufferMapper( 434): registerBuffer(0x1446390) failed -12 (Out of memory)
E/GraphicBuffer( 434): unflatten: registerBuffer failed: Out of memory (-12)
W/AssetAtlasService( 434): Could not create EGL context
D/Atlas ( 434): Rendered atlas in 5.74ms (3.79+1.95ms)
..
E/AndroidRuntime( 598): FATAL EXCEPTION: main
E/AndroidRuntime( 598): Process: com.android.systemui, PID: 598
E/AndroidRuntime( 598): java.lang.IllegalStateException: Could not create an EGL context. eglCreateContext failed with error: EGL_BAD_ALLOC
E/AndroidRuntime( 598):	at android.view.HardwareRenderer$GlRenderer.createContext(HardwareRenderer.java:1278)
E/AndroidRuntime( 598):	at android.view.HardwareRenderer$GlRenderer.initializeEgl(HardwareRenderer.java:1126)
E/AndroidRuntime( 598):	at android.view.HardwareRenderer$GlRenderer.initialize(HardwareRenderer.java:1057)
E/AndroidRuntime( 598):	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1550)
[T-Mobile, Samsung Galaxy SIII] bachnguyen310:
Is there an App for IMEI back up? What is the easiest way to back up my IMEI? Thanks
[T-Mobile, Samsung Galaxy SIII] k8108:
Search, friend! There are 2 ways I know of - an app called Andromizer or use Terminal Emulator with adb commands
[T-Mobile, Samsung Galaxy SIII] serio22:
There is actually, there's one called andromizer but I can't say if it works or not.. The best way to back up your IMEI is to look through the IMEI back up and restore thread for best results
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Terminal emulator. Free one on the play store is excellent.

su

reboot nvbackup

Done. This is the best method. Also the most overlooked.
[T-Mobile, Samsung Galaxy SIII] serio22:
I've actually done that myself, can't believe I forgot about that one
[Motorola Atrix HD] daltonhrrll:
after flashing stock att jb my device booted to unlocked bootloader screen then after sticking there for a while went black and now will not boot at all
[Motorola Atrix HD] TecknoFreak:
How did you flashed it?
[Motorola Atrix HD] daltonhrrll:
i flashed using myth tools everything went fine the device rebooted then wouldnt do anything after the bootloader screen i can still get into fastboot though, i did it because my device wouldnt boot after flashing a 4.4 rom it got stuck at the boot for like 30 minutes so i just went into fastboot and tried flashing stock but no luck
[Motorola Atrix HD] daltonhrrll:
actually i believe it was your rom lol no harm if its bricked or anything ill be getting my LGG2 in the mail in a few days
[Motorola Atrix HD] TecknoFreak:
I created this error on purpose on 2 atrix HD and I solved it the way I posted few minutes ago at my thread

Try rsdlite instead of mythtools
[Motorola Atrix HD] daltonhrrll:
would u happen to have a link to your thread and to rsdlite ? lol
[Motorola Atrix HD] TecknoFreak:
Here is one that should work as well http://xdaforums.com/showthread.php?t=1985031

My thread is the ROM that got you into bootloop http://xdaforums.com/showthread.php?t=2544362

Here is rsdlite and instructions

http://xdaforums.com/showthread.php?t=2231249
[Motorola Atrix HD] legendnexus:
I also have only black screen and nothing else! i cant make it go the the bootloader by pressing the vlume and power buttons an eventually cant get in the fastboot :( so the phone is all black!!!

i tried those above but rsd does recognize the device, but says it is not in fastboot.

Did you face the same problem?
[Motorola Atrix HD] TecknoFreak:
When you plug the phone to charge on AC do your phone at least open up a boot logo and then goes into charging mode?
[Motorola Atrix HD] legendnexus:
No it doesnt :/
[Galaxy Note 3 Q&A, Help & Troubleshooting] Hackenstein:
Hey All,

Am thinking of upgrading from my HTC DNA to the Galaxy Note 3.

Just have two questions:

Has root been achieved for the newest model/version and does anyone know if the Android WiFi Tether app (Note to iPad 4) works for it? Can seem to find the answer and need to know before I drop $700 on one.

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] pcboyy:
Android Wifi tethering works with any device with Wifi connection including laptop, ipad, tablet, iphone, ipod bla bla bla
[Galaxy Note 3 Q&A, Help & Troubleshooting] Hackenstein:
Good to know. A friend of mine had the hardest time getting his Galaxy S3 to work with it. I ended up going through the gauntlet one night and finally got it to broadcast a signal his laptop would see. Was hoping to avoid similar issues if I upgrade.

Do you know about root? I was reading through the root thread and followed the youtube link. People are claiming the root method only works for a previous version.
[Galaxy Note 3 Q&A, Help & Troubleshooting] winn75:
Would the app work with the GS3 on Sprint?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Hackenstein:
Yea, after about an hour and a half of trial and error, I finally found the right settings and got it working. It was a major pain.
[Galaxy Note 3 Q&A, Help & Troubleshooting] winn75:
What settings? could you list them. Are the download speeds fast? thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Depending on your Note version you can enable WiFi Hotspot within the settings.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Hackenstein:
Sure, np. The speeds were good for 3G (Sprint doesn't have 4G in this area still).

VERSION

3.2-beta2-041713

(TrevE Mod)

Device profile: Generic ICS/JB (wlan0)

Setup method: Netd-Ndc (master)

Send Netd Max Client Cmd (checked)

WiFi-driver reload (#1) (checked)

Keep-Alive Connection Check (checked)

MSS Clamping (checked)

Routing fix (checked)

Vibrate on connect (checked)

Disable Wake-Lock (checked)
[Android Q&A, Help & Troubleshooting] shimp208:
I would try using the latest version of TWRP for your device which can be found here and seeing if that allows you to flash the ROM coming from stock Touchwiz.
[Android Q&A, Help & Troubleshooting] easyrider77:
I've been on that page multiple times and cannot seem to find a download link. Perhaps you could direct me in the right direction where I could download 2.6 twrp for this phone (Samsung Epic 4g Touch SPH-D710)
[Android Q&A, Help & Troubleshooting] shimp208:
Try flashing this .zip file in your current custom recovery to update to TWRP 2.6.
[Android Q&A, Help & Troubleshooting] easyrider77:
I ran that file, and got "assert failed" and a result of a (status7) and it aborted.

I am currently on agats recovery trec_v0.3.5. agats version 1.3 I think it is.
[Android Q&A, Help & Troubleshooting] shimp208:
I'm afraid you may have to go the long route then for flashing your ROM. If you can provide me with a copy of your devices stock recovery.img I can try and compile the latest version of Clockworkmod Recovery for you in a .zip form so that all you would have to do is flash the Clockworkmod Recovery .zip file in your current recovery then flash your KitKat ROM.
[Android Q&A, Help & Troubleshooting] easyrider77:
that would be awsome if you could.....I reqally like twrp, but I am not partial to useing either cwm or twrp so if you can create the latest one they use that'd be awsome.

I'm fairly new, but somone a fast learner so I've picked up a few things here and there so I appologize for the questions at times.

when you say recovery.img, you mean the zimage, or boot.img?

I didn't find a file names recovery at all.

I have the roms they are using namely hood pope rom, and it has a boot.img file in it I can get, and i the stock deodexed gc01 rom I have there are 2 files, flash_image, and zimage.

.

I recognize the zimage file and if I remember right I pulled the one out and put in agats recovery zimage in that zip, so I guess I'm wondering what one you want I have like 3I can choose from.....

1: Hood Pope rom that has a boot.img file

2: Stock Deodexed with root rom with flash_image and zimage in it.

3: VILLUMINATI CM11 rom, which uses a newer recovery as well...that has a boot.img in it as well

4: I also have a odin factory non-rooted tar file that has multiple files in it as well.... a recovery.bin, zimage, boot.bin and factoryfs.img in it. <---this tar file is the one that will set the phone to factory stock no root as if it was straight from the factory.

I'm guessing the cm recovery would be the best choice in this case, so go for that.

Let me know and I will upload the files to dev-host

keep in mind the way I "normally flash" is with el29 and mobile odin, so if I can get one that would work from el29 so I could flash directly from it without going thru a rom to flash, that'd be sweet....then I could just mobile odin EL29 cm > reboot to EL29 receovery > flash the newer recovery > reboot to that bnew recovery > then install the rom, that cuts the steps taken by about 1/2
[Android Q&A, Help & Troubleshooting] shimp208:
Sorry that I have been away for a few days, I would recommend running the follow command form terminal emulator or adb shell as root:

cat /cache/recovery/last_log

And posting the output that way I can determine which partition is your recovery partition that will need to be dumped to recovery.img.
[Android Q&A, Help & Troubleshooting] shimp208:
Please run the following command from terminal emulator or adb shell as root user and please upload the resulting recovery.img file:

cat /dev/block/mmcblk0p6 > /mnt/sdcard/recovery.img
[Android Q&A, Help & Troubleshooting] easyrider77:
Ok here it is, http://d-h.st/Zpj
[Android Q&A, Help & Troubleshooting] shimp208:
After taking a look at your recovery.img, I unfortunately couldn't get it to unpack properly and compile as it's ramdisk setup is different then the standard layout.
[Android Q&A, Help & Troubleshooting] easyrider77:
That's ok I appreciate the effort greatly.

My guess is this phone is just that way, that or else it's a samsung thing.
[Android Q&A, Help & Troubleshooting] shimp208:
I believe it's the way Samsung does it's ramdisk on particular devices (Usually older devices like your's in this case) where the recovery image has to be injected into the ramdisk a certain way (After looking at official TWRP for your device as reference).
[Android Q&A, Help & Troubleshooting] easyrider77:
Yeah I've been told that same thing from other people.

What about the S3, think it's the same way?
[Android Q&A, Help & Troubleshooting] shimp208:
The Galaxy S3 uses different ramdisk setup, I've been able to unpack stock Galaxy S3 and compile recovery for it using the normal methods.
[Android Q&A, Help & Troubleshooting] easyrider77:
awsome thanks again for the efforts......seems like this phone has been a real pain for people heh.....I'm looking into the s3 as an upgrade, looks like it's maybe time to get that.

It's boost mobile so s3 is the ebst they have at the moment, no s4,....but still a nice move I think
[Moto G Q&A, Help & Troubleshooting] NeostarNeko:
Yea just wondering if they'll make a 4G version if there's demand
[Moto G Q&A, Help & Troubleshooting] parsa5:
I don't think anyone but certain motorola employees could even answer this question. It does support faux 4G though.
[Moto G Q&A, Help & Troubleshooting] jonmorris:
I expect there will be a 4G version next year. In fact I really hope Google has plans to make Motorola become an amazing brand for affordable but highly specified devices that will crush all those that dare sell crappy budget phones that do nothing to the reputation of Android.

Even someone used to devices like the GS4, HTC One and Xperia Z1 can look at the Moto G as a decent device, as it punches way above its weight.
[Moto G Q&A, Help & Troubleshooting] parsa5:
Couldn't agree more. Motorola is positioning themselves as a top contender for 2014.
[HTC One S] tacojohn:
I have installed Odyssey-ville-v-3.30.RC-OFFICIAL on my HTC One S. Everything works great but everytime I try to use the screen capture feature is says "Couldn't capture screenshot. Storage may be in use."

I know the HTC One S only has an internal SD memory card. Is there any way to fix this or if not, can I use a 3rd party tool to capture a screen for debugging?

Thank you!
[AT&T HTC One (M7)] dbrown101386:
I'm thinking of buying the Dual SIM w/ TFCard HTC One (M7 802W) (Newegg Item #9SIA2Z21051722)

Would like to know if it follows the same standards of the AT&T/T-Mobile/Verizon brands. Will I be able to OTA to 4.3 and 4.4 (when it's ready)? The same root tools and recoveries should work, yes?
[AT&T HTC One (M7)] clsA:
no it's a totally different phone

search the forums for info about it
[Galaxy Note 10.1 Android Development] iofthestorm:
​

Announcements

Discuss the official nightlies here! Also, TheMorpheus has taken over building and distributing N8000 unofficial builds, so go to his thread for more up to date builds!

Disclaimer

Standard disclaimer applies, your warranty is void, this may eat your dog or burn your house down, delete all your pictures, etc.

Instructions

0. You need a recovery that supports SELinux. I'm told that recent versions of CWM support it, but I haven't tried them myself. So if you aren't on the latest CWM (in particular, if you're on the last version of TWRP officially released for this device) you will need to flash a newer recovery. For best results, use my TWRP 2.6.3.x builds (other recoveries may not be compatible with delta updates for official nightlies).

If you want to flash my recovery, download the recovery.img and flash it using ODIN or Mobile ODIN. You can also use Recovery Tools to flash it from your device

1. Flash the ROM.

2. Flash SuperSU if you want root (it's not yet included in the ROM). I have not tried any other Superuser apps but SuperSU is supposed to be incorporated into Omni eventually. Important: you may need to install a backup script using SuperSU to persist it across flashes - see the settings in SuperSU for that.

3. Flash Kitkat/4.4 compatible Gapps (PA has some that work with this ROM).

1-3 can be queued in TWRP.

4. If coming from a different ROM wipe data/factory reset, otherwise you probably won't boot

Downloads

TWRP 2.6.3.1 (unofficial version; the 4th digit is basically just for device specific changes). Use Flashify, Mobile Odin, or Recovery Tools to flash .img files.

twrp-2.6.3.1-n8000.img

twrp-2.6.3.1-n8013.img

ODIN flashable tars:

twrp-2.6.3.1-n8000.tar.md5

twrp-2.6.3.1-n8013.tar.md5

You must flash this (or other 4.4 compatible recovery) if you're on the official TWRP 2.6.3.0 or other outdated recoveries, if you get an error about set_metadata_recursive when flashing

omni-4.4.2-20140210-n8000-HOMEMADE.zip - N8000 Builds discontinued by me, see posts from TheMorpheus for updates.

omni-4.4.2-20140302-n801x-HOMEMADE.zip

Older releases in the Downloads tab

Sources

Device trees:

android_device_samsung_n80xx-common

android_device_samsung_n801x

android_device_samsung_n8000

Frameworks (I may make some device specific changes or just cherry pick things like MultiWindow)

android_frameworks_base

Thanks, and have a nice day!

XDA:DevDB Information

OmniROM, a ROM for the Samsung Galaxy Note 10.1

Contributors

iofthestorm, Entropy512, espenfjo, humberos

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.0.x

Based On: AOSP

Version Information

Status: Alpha

Created 2013-12-01

Last Updated 2014-03-03