yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
The small image is too small to accommodate the size of the plain stock zip. It is over 400MB. Use the new procedure in section 1a and you can use the whole 2GB.
[Nook HD, HD+ Q&A, Help & Troubleshooting] drummer4261900:
what do i need to copy for mine i am not seeing 5 files?
[Nook HD, HD+ Q&A, Help & Troubleshooting] drummer4261900:
i see a couple folders and some files
[Nook HD, HD+ Q&A, Help & Troubleshooting] drummer4261900:
i downloaded the unrooted factory 2.1.0
[Nook HD, HD+ Q&A, Help & Troubleshooting] leapinlar:
You need to download the BOOTFILES rar file attached to the post and unarchive the .rar file. It has the 5 files there.
[Frameworks] yigajoel:
i was trying to modify an apk with apktool and others and all went ok but when i run the app on my phone it says this is a pirated app...how to i remove this restriction
[Frameworks] vrock25:
Lol
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] louvega:
Ok, back again.

So, my situation is now this: The root worked, by appearance but somehow, it only seems to be a "partial root", for lack of a better description.

I have SU and Rootcheck Basic installed and it says that I have root, but I can't get the play store to work no matter what, and can't change permissions on the /system/apps folder or write to there when trying to copy the Google Play apk there (attempting to see if I can run or install it there).

And, IDK if this is relevant, KFFirstAide doesn't seem to be able to "find" certain folders and keeps showing errors such as: "The system cannot find the path specified. mkdir failed for /data/local/tmp, File exists" and "The system cannot find the path specified. rm failed for /data/local.prop, No such file or directory" for many operations during it's process, but overall, the operations don't fail.

For instance, the OTA updates seem to have been blocked, the ad services have been blocked and I was able to install Gmail.

Ultimately, any way to get the Google Play store installed?
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] louvega:
Ok, I solved my own problem but for anyone that might have a similar problem, it was definitely the fact that the /system and /system/app folder for some reason, wasn't mounted as r/w after the root.

Solution: I downloaded the apk, https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en , which is a "mount system as rw" app (lol - go figure!), and voila!! SUCCESS!

I was then able to install the Google Play Store! So, as I suspected the fact that it was r/o, even after using KFFirstAide to root was what was preventing me from installing the Play Store.

And here's another site that really helps, if you can't download any apks or are trying to sideload something using an alternate method using your PC: http://apps.evozi.com/apk-downloader/

tags: locked system folder, /system/apps, locked, read only after root, rw/ro, mount system, half root, incomplete root
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Neither user or system is r/w after root. You can do this in about five seconds with ES File Explorer. Just to save you some headache next time.
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] louvega:
Yeah, thanks but... sorry to contradict you - didn't work for me. Had ES File Explorer installed and tried multiple times to reset it the system folder using the permissions (rwx, etc.) I'm convinced there's something new with the update but whatever.
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Just user error if it didn't work for you. Next time click on the words "Root Explorer" and select "Mount R/W and then select path, system or both.
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] louvega:
Well, I might have missed it so, I take it back. Thanks!
[Android Q&A, Help & Troubleshooting] aydd:
hii xda developers.

my android tablet Practica 8 inch tablet

but x coordanition problem new touch screen problem

this youtube video same problem help to me fix .

youtube.c om/watch?v=VORVeRWYNgI
[AT&T Samsung Galaxy S 5] Rakuu:
I noticed after turning my phone on one day that the keyboard shortcuts (back slash from long press on "m" key, ETC) were missing. The only change ive made related my keyboard freeze swype and uncheck google voice typing since I didnt use them. Any help is appreciated, thanks.
[AT&T Samsung Galaxy S 5] Rakuu:
I have a screenshot of the issue.
[AT&T Samsung Galaxy S 5] csfile:
If you use wanam xposed, there's a system option to enable keyboard symbols. You can give that a try.
[AT&T Samsung Galaxy S 5] Rakuu:
Ya I saw that and gave it a shot, no dice though.
[AT&T Samsung Galaxy S 5] norbarb:
Did you try to reset settings in keyboard settings or restore swype keyboard?
[AT&T Samsung Galaxy S 5] GDofWR420:
Yea mine disappeared to but no biggie just hit the "sym" button and it still works just no longpress

The Gods Approve This Post, From The Ghost Of Sparta's S5 active.
[AT&T Samsung Galaxy S 5] Rakuu:
Yep tried both of those things, still not there.
[AT&T Samsung Galaxy S 5] FilthyFord:
Mine done the same thing after installing xposed framework. Make sure to go into exposed framework and click on modules then check to make sure Wanam us enabled, once that is done reboot phone, then open Wanam and click the "so keyboard symbols" then reboot using Wanam in the notification bar. Should be there after that. Or at least for me they were.
[AT&T Samsung Galaxy S 5] Rakuu:
Already said I've tried that lol, still no symbols.
[AT&T Samsung Galaxy S 5] FilthyFord:
Yea I seen that, I was mainly just wanting to point out the part about making sure Wanam is enabled inside exposed, I've read a few article on here before where people will forget to enable it or not know that after downloading a module that you still physically have to go into xposed and enable it. Hopefully you get it figured out.
[AT&T Samsung Galaxy S 5] Rakuu:
I was able to get them back finaly with the fix noted here. http://xdaforums.com/showthread.php?t=2171449

I think the issue may have had to do with wanam and the "keep my extra CSC" features because my features.xml was actually blank, and reportedly wanam messes up your features.xml

So for future refrence, if your keyboard symbols are missing the fix from that link should work, all thanks and credit go to him.
[AT&T Samsung Galaxy S 5] segordon:
After installing the xposed module and Wanam xposed I also lost my symbols. But I fixed it buy using root explorer and going into: system/and csc/ you will see 2 feature.xml files. One is feature.xml and the other is feature.xml.bak. Rename feature.xml to feature.xml.bakk then rename feature.xml.bak to feature.xml. Then reboot. Now the symbols are back on the keyboard.
[Kindle Fire 2 Q&A, Help and Troubleshooting] herrenfam:
My daughter's Kindle Fire 2 HD keeps getting this message. It is rooted using Kindle Fire First Aide (though I don't know where to find the most current version). I just re-rean the root process this morning as it didn't help. I don't know what the "timely" process is or how I get rid of it. Although I'm a fairly savvy computer user, these tablets seem to confuse the heck out of me!

Thanks for your help!
[LG G Watch] joeinbend:
I just got my LG G Watch yesterday, and I noticed last night when you leave it with the "always on" option where it dims the screen way down, that in the dark I can see the screen flickering. I tried all the different brightness levels in Settings to see if that would change it, but does not. Can anyone else confirm this? You'll have to get in pitch black environment to see this.

Also, is there a way to turn off the "shake n wake", where it turns the screen on from motion? I tend to sleep with a watch on, and noticed this watch is very sensitive to (or that I flop around like a fish when I sleep.. that's possible too) motion, and I'd rather be able to set it in "touch to wake" mode.
[LG G Watch] johnus:
I haven't noticed any flickering on mine, but I may just not be as sensitive to it. You can disable the 'wake by motion' function by muting the watch. (Pull down from the top of the screen)
[LG G Watch] Bladder61:
Thanks for the tip on muting to stop the motion sensor from activating the watch. I find it very sensitive and just sitting at my desk working tends to make it constantly wake up. Muting also turns off vibration so I miss when a notification comes to the watch. Maybe in an OS update or possibly a Developer will enhance the settings so you can still get vibration alerts, but turn off motion wake.
[Android Q&A, Help & Troubleshooting] SolarTrans:
I figure it's possible, but could I theoretically port the Android L Preview for the Nexus 5 to my HTC M8 Google Play Edition?

The hardware is fairly similar: same amount of RAM, same resolution, pretty much identical CPUs, same Bluetooth number.

I'm aware it was recently ported to the Nexus 4, but the 4 and 5 are both LG devices.

It's summer, so I have plenty of time, and I really want to have KitKat on my M8 XD

I found a couple tutorials for porting ROMs, but they've been between the same manufacturer.

I'm almost wiling to just go buy a Nexus 5, but I much prefer the M8 so I'd like to give this a shot if possible.

Thanks in advance!
[Android Q&A, Help & Troubleshooting] SolarTrans:
Oh, and I'm not sure if this is the right forum section to put this in, so I might move it to the M8 section.
[Verizon HTC One (M8)] knifedroid:
I hope someone can help me, I'm about to go insane.

Just got the M8. Got S-Off/unlocked bootloader via Sunshine (after trying via firewater for 5 hours before reading that method was patched. Achieved permanent root and flashed TWRP recovery. Made a backup. Wiped. Banged head against wall.

Have tried to flash both GPE and Viper. Have downloaded each twice. Have reflashed TWRP (through ADB and Rom Installer).

Every time I try to flash a rom, it fails. It just hangs for a few seconds then says: error flashing zip '/external_sd/ViperOneM8_1.7.1.zip'.

I can restore my backup through TWRP with no problem. Please help...I am at my wit's end. :confused:
[Verizon HTC One (M8)] mashk:
I ain't much of a guru but I think it would be easier to help when you state the errors you are receiving and possibly some screenshots!
[Verizon HTC One (M8)] thunderbls:
Could just be a bad download.. try redownloading to you internal memory and flash from there. I had this problem when I used my sdcard from a previous phone.. formatted the card and all was well after.
[JAM, MDA Compact, S100 General] amelie:
If anybody is interested in selling me their broken o2 minis or imate jams at a reasonable priceI would love to hear from them.I am trying to get a supply of spares so that I can fix them and provide a better service than the registered repair agent in aus .Thanks
[G2 Q&A, Help & Troubleshooting] El Che:
Microphone not working during calls but i can record my voice perfectly fine and if i switch to speaker mode during calls then too it works fine.

I did drop my phone but then again if the microphone was physically damaged then it shouldn't be working entirely and it was working fine right after i dropped it so thats also confusing.

anyone know any fixes :confused:
[G2 Q&A, Help & Troubleshooting] El Che:
its working now, i opened up the phone and cleaned the microphone.
[Galaxy S 4 Q&A, Help & Troubleshooting] 189cutter:
Hi i would like to know if a ps2 controller would work with galaxy s4 gt i9505 via adapter and usb otg?
[T-Mobile Samsung Galaxy Note II] DLinkwit:
As of right now I have 4.3 Pacman rom and wanting to upgrade on 4.4 pacman rom

but everytime I flash it says error. I had this issue when I was at 4.2 trying to flash 4.3 and I updated to official 4.3 then rerooted then

flashed 4.3 rom.

Now do I need to officially update to 4.4 kitkat first coz there isn't one yet.

but how to I flash 4.4 rom. I'm using twrp from playstore.

Thank you! for all the help I can get.
[T-Mobile Samsung Galaxy Note II] Double0EK:
Try this. .

After wiping (System, Data, Dalvik-Cache, Cache and/or Internal SdCard)

Go back to the Recovery Main Menu and find the option to reboot. But you'll want to select Reboot Back Into Recovery. After it boots back into recovery then try and flash the Rom.
[T-Mobile Samsung Galaxy Note II] Coug76:
Which version of twrp are you running? TWRP is not an app available on the play store. It is a recovery that may be installed by apps from the play store. The version you run is important if it is over 4-5 months old.

Hastily spouted for your befuddlement
[T-Mobile Samsung Galaxy Note II] DLinkwit:
like I said, I just re-rooted so I installed the newest twrp. It is also in play store as goomanager/goo.im whatever the name is

it is rebranded in twrp as downloadable now and will install the newest recovery.

Double0EK I will try that method since I never reboot back to recovery, I usually wipe then flash.

Thanks! guys will try that and let you know.
[T-Mobile Samsung Galaxy Note II] Coug76:
Your petulant impatience aside, if you won't tell us which version you are on (which is quite possibly a part of this scenario) it is difficult to help you.

Goomanager is not being supported and if that was your source for TWRP you are not on the latest version.

TWRP is not an app on the play store. There is a "TWRP Manager" in the store but I won't install it to find out the answer to the question I asked you. I don't trust apps like that personally as they may rely on markers that can be changed easily which may affect which version of recovery you get. If the app thinks your T889 is an N7105 and accordingly installs the wrong recovery you might end up with weirdness when installing ROMs with the wrong recovery.

I suggest downloading the current version of your device's recovery from the TWRP website and flashing it via a zip or via Odin.

That will take variables out of the equation. At the very least just tell us what version you are running. It shouldn't be a big secret.

Hastily spouted for your befuddlement
[T-Mobile Samsung Galaxy Note II] RoxAbout:
twrp link

I make no claims about if this link works or not but it was referneced on another page here on xda for the t-889...they said to use the latest/highest #

https://goo.im/devs/OpenRecovery/t0ltetmo/?page=2

hope that helps.
[T-Mobile, Samsung Galaxy SIII] kojam:
Moderators, please forgive me in not in the right place...

Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...

Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..

Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!

Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.

I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying::confused::rolleyes::eek:

Any help would be greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] Bass_Man25:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
[T-Mobile, Samsung Galaxy SIII] kojam:
Thanks bud.

Oh, I got the phone up and running on the Cyanogen dated dec/2013.

ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.

Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.

Thanks for the suggestion!!!
[T-Mobile, Samsung Galaxy SIII] kojam:
any idea why this happened? anyone?

as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...

Will have to give ODIN a try if I can ever get the time some day..
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!

Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.

Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....

Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.

Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.

Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.

Hope that helps! Good luck!
[T-Mobile, Samsung Galaxy SIII] kojam:
What's up, Doc? Sorry for that...

I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!

Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?

As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.

A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.

Thanks again!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
[T-Mobile, Samsung Galaxy SIII] kojam:
Thanks!
[T-Mobile, Samsung Galaxy SIII] kojam:
S.O.S!!!

Downloaded the rooted firmware from your link and the ODIN (3.09)...

Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!

Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!

Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone

Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.

Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.

Any suggestions? :rolleyes::(:eek:
[T-Mobile, Samsung Galaxy SIII] kojam:
In the words of George Costanza:

"I'm BACK, babyyyyyyy!!!!!"

The official firmware worked!

Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!

Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....

batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...:confused:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Earplugs! Lol! I definitely feel for you about your work status! Been there!

About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!

If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)

This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
[T-Mobile, Samsung Galaxy SIII] kojam:
The Doc is in!

That's EXACTLY my thought too. That was really perplexing...

I am up again...

Facotry Reset? How do I do that if stuck at the Samsung splash though?

Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.

Oh!!!!

I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
[T-Mobile, Samsung Galaxy SIII] kojam:
....and battery life is STILL pretty bad...

Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.

Will see how it goes after doing the factory wipe.

Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
[T-Mobile, Samsung Galaxy SIII] getochkn:
Maybe your battery is dying. it happens. That would explain a big drop from the start.