yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] AlexZap:
progress...

i take it by the deafening number of replys, no one has any idea whats up with my issue or any idea how to fix it. so i have been digging deeper myself and think i have come up with some solutions.

first of all, i was just planing on flashing one of the roms off of the NeedRom.com website, but i read a couple of posts on chinaphonearena.com and one in some german forum that listed a phone with my same baseband and ROM build, and when they flashed the new rom, it screwed up their touch screen. something about having an incompatible touch screen driver. i don't know if the person flashing the rom chose the correct rom, or incorrect rom, but it made me skidish to attempt this as a fix.

so i checked in on modifying the EBR files, which people have been doing on these mediatek phones for a while. i thought maybe one of mine was screwed up. i extracted the EBR1 and EBR2 file from my fine with MTKDroidTools and i pulled the files out of the rom update. i also took the scatter file generated by MTKDroidTools and the scatter file from the rom update. i compared them line for line. the EBR files are totally identical! as was the scatter file. address of where the partitions start and stop inside the phone are 100% the same. so flashing a new rom wouldn't have fixed the problem anyway.

i started googling around at the error that parted gives me: "Error: Can't have a partition outside the disk!" this is discussed elsewhere, but mostly on actual machines, not phones. there are some postings here on XDA, but none that address my specific issue. anyway, the ways it always suggests to fix it is to figure out which partition is oversized, used the sfdisk utility to dump the partiton table, fix it, and re-write the partition table to disk. simple enough, if you know what your partition table should look like.

back to fdisk, i reprint out a copy

this does indeed tell me that the internal flash memory is about 8gb (Disk /dev/block/mmcblk0: 7792 MB, 7792492544 bytes) but it is not obvious to me which partition is screwed up.

anyway, i'd love for someone that has an mtk6582 based phone with 8gb of internal storage to provide me with a dump of their partition table, then i could just restore it over mine, and it should fix the issue!... the command is simple...

from what i see (i may be wrong here) but these phones run with something like 2 partition tables... there is the one that is physically connected to the first 512 bytes of the SD card. then they have the EBR's which map out all of the EMMC partitons. so there is just one big partition seen from the outside, but through software, we can map that big partition in to smaller ones by knowing start and end addresses inside that big partition. i tell you, it is confusing.

i'm sure if i use the spflash_tool and format my phone and re-install a rom, it would fix the problem, but i am nervous about doing that because so many people have had issues putting rom's on this phone. they report that even when going back to their original backup the touch screen issues persist.

anyone have any comments? any ideas? any mbr backup they could share with me?
[Android Q&A, Help & Troubleshooting] PMoto:
I believe you read my thread in chinese forum, I have one here too, because my touch is not working well since the rom upgrade.

Anyway, I'm almost sure you have like me a STAR Ulefone N9002 MTK6582 (1.3GHz) with 8Gb total memory.

AnTuTu 17500 values are 6582, 13000 are 6589T.

The original ROM have 1Gb RAM, 2Gb Internal Memory, and 8Mpx camera.

The ROM you have, and the MARCH Rom Update of Needrom, make the fake values, and the ram and internal memory are not correct. The camera is updated to 13Mpx too.

If you want, here you could read the procedure to edit the MBR by yourself.

Or you could flash the JAN rom of needrom.

I'm not sure about what cause my touch to get screwed, I guess I will never know, but I will keep flashing my phones...

At the moment, I'm waiting for a new touch for replace.

Cheers and good luck.

PMoto.
[Nexus 7 Q&A, Help & Troubleshooting] Legobricke:
Ok.... A brief description....

Nexus 7 is on..... Sometimes it's in the dock..... Sometimes it's in the case.....

All seems fine and running.....

Then.... When not in use (in the case) or sometimes charging in the dock, It just shuts down and will only restart with a loooong press on hold of the power button. In all cases, the battery is 90% > 100% charged.

Now.... I have reset the cache and factory reset a few times.... Yet the problem is still there.

Last few times, I have reset the cache and then the factory reset.... The reset of cache works fine, but if I reset the cache prior to factory reset, the factory reset shows a bunch of errors trying to access the cache....

Am I doing something incorrectly or does it have to go back to Asus for a second time?

These issues didn't start occurring until after the last system update to 4.4.2

Lego.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Legobricke...

How are you resetting the cache? Do you mean clearing the cache? Are you referring to Dalvik cache? Are you doing this via a Custom Recovery (CWM or TWRP)?

What error messages do you see? Can you post a screenshot of these error messages?

Sorry for the barrage of questions... but the more information you can provide, the more likely you are to acquire a diagnosis, and a possible solution.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Legobricke:
I am clearing the Dalvik cache..... This is done in stock recovery on an unrooted Nexus 7.

I can't take a screen shot unless I do a full factory reset again... But if I remember right it was trying to access E drive and the at least on error said it could access the cache...
[Nexus 7 Q&A, Help & Troubleshooting] Legobricke:
This is what I get after clearing Dalvik and then trying a Factory Reset:

Formatting /data...

E: failed to mount /cache (Invalid argument)

E: Can't mount /cache/recovery/log

E: Can't open /cache/recovery/log

E: failed to mount /cache (Invalid argument)

E: Can't mount /cache/recovery/last_log

E: Can't open /cache/recovery/last_log

E: failed to mount /cache (Invalid argument)

E: Can't mount /cache/recovery/last_install

E: Can't open /cache/recovery/last_install

E: Failed closing /dev/block/platform/sdhci-tega.3/by-name/MSC (I/O error)

E: failed to mount /cache (Invalid argument)

Anyone?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Legobricke...

Apologies for not getting back to you sooner, but I've been really busy this past week with work.

And if truth be told, I've also been finding excuses

not

to write this post... because I hate delivering bad news. And your above quoted output, I think, is very 'bad news'.

Everything about it suggests you have either a bad eMMC/NAND chip (hardware failure)... or a partition corruption.

There is very slim possibility you **might** get your Nexus 7 working again, by fastboot flashing a Google factory stock image... but given your previous descriptions of random shutdowns, and this sort of thing...

E: Failed closing /dev/block/platform/sdhci-tega.3/by-name/MSC (I/O error)

(...and which is something I've never seen or heard of before...)

Well... I'm not optimistic fastboot flashing anything will work, to be honest.

I think your best bet, is to return it back to Asus and hope they'll fix it.

Sorry I couldn't be of more help.

Rgrds,

Ged.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mooseknuckles1:
I just switched from CM11 to SlimKat4.4.2, couldn't be happier, BUT, my 64gb microSD card is no longer recognized. Any idea why this is and what the solution is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StuckOnDestiny:
You can try the flashable .zip from PwnCakes. He made it for Quantum but he mentions here that it should work for all ROMs:

http://xdaforums.com/showthread.php?p=52203110&highlight=exfat#post52203110

Here's the DL link for the .zip:

http://d-h.st/ELH

---------- Post added at 09:32 PM ---------- Previous post was at 09:27 PM ----------

I should mention that the latest Quantum is based off of SlimKat. The issue has been mentioned in that forum before so I imagine this should fix it for you as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mooseknuckles1:
I looked through the link and the main page of that post, but it doesn't look like there are instructions. I just want to make sure before I go ahead with it, do i flash/install the zip for exfat the same as any other zip with TWRP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StuckOnDestiny:
I believe so, yes. I haven't needed to use it myself but it is a flashable zip. I recommend searching through the Quantum thread a bit to see how people have done this and how it works. My guess would be wipe cache and dalvik as well. Sorry I don't have more info.
[T-Mobile Samsung Galaxy Note II] cooljd1:
Hi I am new to this forum and a casual user. I wanted to root my note 2 tmobile android version 4.3 and actually rooted it once but knox created a lot of problem. I could not even launch titanium backup to freeze knox. Or was completely unable to disable knox. Now as android 4.3 has been released for quite a few months. Does anyone know of a method which will root my galaxy note 2 tmobile (SGH-T889) for sure and let me completely disable knox? If so please give me step by step instruction of rooting my device or alteratively you can provide me a link of the instruction so I can root my note 2 phone. I appreciate your help.
[T-Mobile Samsung Galaxy Note II] mattlowry:
cf auto root should work for root. what did you use to root? if you are rooted install a custom recovery and flash a knoxfree rom from the dev section
[T-Mobile Samsung Galaxy Note II] Sobaro:
Flash CF auto root via Odin then download latest superuser from play store and you are ready to go.

All credits to ChainFire
[T-Mobile Samsung Galaxy Note II] J3D1mineTR1X:
Did you try this method, if so did it work for you? Im having similar issues with my tmobile note 2 running 4.3 too. I'd appreciate it, thanks in advance...
[T-Mobile Samsung Galaxy Note II] wavv.drama:
Just as a suggestion, something that happened to me while playing around with the phone: if you're running Stock rom and then flash a custom recovery via Odin (I used Philz Touch) upon booting on recovery just to wipe cache/dalvik I found something interesting: my phone wasn't rooted, so when chosing the option "reboot system now" a message that said something like "root is broken, would you like to root your phone before rebooting" appeared. I was curious, as I normally use a website called Kingo root that does it in a one-click kinda way. When I chose Yes in the recovery, upon booting my phone it was rooted. After, I just intalled Chainfire's SuperSU from the play store and it was all good.

It's worth trying I believe.

Cheers
[T-Mobile Samsung Galaxy Note II] J3D1mineTR1X:
+wavv.drama

I have a question. If you don't run odin as a administrator do you get this error message: Windows cannot access the specific device path or file. You may not have the appropriate permissions to access. The last time I tried to root my phone i didn't run odin in administrator mode. I'm just finding out about this recently. I have all of the files installed on the computer and ready. Odin, recovery, keis, and supersu zip on sd card. Im just trying to figure out why I got that error message. Any ideas or suggestions would be appreciated. Thanks in advance... Awaiting your response...

"What good is knowledge if it's not to be shared"...
[T-Mobile Samsung Galaxy Note II] wavv.drama:
The only answer that pops up in my mind would be that you weren't running Odin as an administrator, like you mentioned. Maybe try running Odin as an admin, or alternatively (and I haven't tried this myself but Chainfire's thread gives a good step-by-step and people in the forum do help) use mobile Odin ------> http://xdaforums.com/showthread.php?t=1347899. The first time I wanted to root my phone I was having issues too, not being able to do it because of lack of experience. I stumbled upon this website: http://www.kingoapp.com/. Check it out, if you would like. This kingo app is a downloadle app (kind of like Odin) that Roots yourm phone alone, without needing to flash anything. The step-by-step's are there, just turn on your developer options and then turn on USB debugging. I personally rooted A Galaxy Tab, SIII, a Note I i717 and an Asus MemoPad with that website and it worked perfectly for me. Rooting via custom recovery is something that I learned recently, and by chance. I do not know whether it trips the Knox counter or not to be honest with you, to me it doesn't make a difference since I will not be returning any of the devices I rooted, After rooting the phone like so you could potentially download mobile Odin from Chainfire's thread and then use Odin without needing to use your computer.

Hope this helps
[T-Mobile Samsung Galaxy Note II] J3D1mineTR1X:
+wavv. Drama

Yeah that was it, i rooted it earlier today. I do have another question for you. I ran root checker pro and it says I'm rooted. I tried to install busybox but it said remove supersu permissions reinstall supersu and to delete and reinstall busybox. Also the adb shell doesn't have root access either. So is that a common occurrence, or is it the norm after rooting and installing custom recovery? Awaiting your reply. Thanks in advance...

What good is knowledge if it's not to be shared...
[T-Mobile Samsung Galaxy Note II] wavv.drama:
Sorry for the late reply, hadn't been to the forum in a minute. To be honest with u, I don't know for sure. I haven't personally yet served myself from adb so I can't tell u. However, the reason why you received that response from busybox may be because when u were partially rooted it gained root access (if it ever did, I only assume).

Try what was asked of u and I'm sure busybox will work no problems. Also, if u have the terminal emulator apk try entering the command "root" (without the ") and if u gain roots access it will definitely mean you are rooted for sure.

What do you want to use adb for, if I may ask?
[Sony Xperia S, Acro S, Ion] Revaey:
Hello.

Recently I've tried to get myself a new ROM. I've decided to choose this one:

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

Everything was going just fine. I unlocked bootloader, flashed device, accesed CWM menu, did all the wipes but the dalvik cache one and then my device kinda re-connected through the usb (you know, the sound windows makes when you disconnect and connect device). I had no idea what happened and from that point I can no longer acces my phone. It's stuck at Pac Rom logo. The phone only responds when i turn it on in fastboot mode (power + volume up button). Then a blue led lights up.

Have I really just bricked my phone beyond repair? Could anyone help me?
[Sony Xperia S, Acro S, Ion] Bornon17th:
You didn't brick your phone, the latest version isn't working for me too.
[Sony Xperia S, Acro S, Ion] Revaey:
What a relief. But is there any way I can, well unbootloop my phone? In case someone asks, I've already looked through the forums and all the advices were connected to people who can, in fact, acces CWM Recovery menu. My phone is not being recognized by flashtool.
[Sony Xperia S, Acro S, Ion] Bornon17th:
Did you have back up of your current ROM or any other ROM or its zip file ?
[Sony Xperia S, Acro S, Ion] Revaey:
I didn't have any custom ROMs before. This was my first attempt at customizing my phone. The only thing I've done is

followed instructions in this http://xdaforums.com/showthread.php?t=2327473 thread after upgrading my phone to 6.2.B.1.96 Firmware. Then I unlocked bootloader and tried to flash Pac Rom. What should I do?

And one more thing, thank you for such a quick respond. :)
[Sony Xperia S, Acro S, Ion] Bornon17th:
Flash stock ROM via flashtools.
[Sprint Samsung Galaxy Note 3] :
Is there a way to disable it as there was in almost every other Galaxy Android phone I've owned?
[One (M7) Themes and Apps] Philstadt:
Can anyone post the Emojis and tell me where to place them?
[One (M7) Themes and Apps] BouncingObject:
So you're looking for the Sense Emoji .ttf file to use Sense Emoji's on a non-Sense ROM?
[One (M7) Themes and Apps] Philstadt:
No,miui from miui Germany uses sense Keyboard...but the emoji's are missing
[Galaxy S 5 Q&A, Help & Troubleshooting] mattan:
I've just upgraded from Galaxy S4, and surprisingly I am missing some useful options and settings:

1. Dropbox folder on Gallery - In S4 the Gallery app display every photo folder on dropbox as a separate album (like "Summer vacation 2013" etc). In S5 all of the thousands of photos in my dropbox cloud are merged into a single album, named "Dropbox".

2. Lock Screen - unlike S4, no option to define applications on the button of lock screen for fast loading. Only the camera.

3. Widgets on Lock Screen - unlike S4, no option to insert widgets on lock screen, including option to swipe in lock screen to the right camera) and to the left other widgets).

4. Torch - no option to press volume-up to light the torch

5. Air Gesture - no option to put my hand above the phone when off, to get fast info about clock, messages, battery etc.

And few more problems (not related to the S4 options):

1. Home Screen - I often need to press it TWICE in order for it to work (both when phone is off and on). I'm not talking about the lag. Is it normal?

2. Geo News - in which countries does it works?

I have an official rom, not custom.

Thank you
[Galaxy S 5 Q&A, Help & Troubleshooting] dawolverune:
Simple answer. Certain reviewers on mobile websites (who don't use the S4) complained that the S4 has a lot of features that they deemed unnecessary, so samsung listened to these reviewers and removed them.
[Galaxy S 5 Q&A, Help & Troubleshooting] fredysb:
But some of these were very useful features. e.g. Widgets on home screen, a very helpful feature, Additional shortcuts like contacts, phone button on the home screen. The camera in S5 click when you press the volume button rather then enable zoom! For zoom you are forced to go thru the screen based zoom Isn't this odd?.

Why would anyone deem these as not helpful. It is high time that someone on Samsung reviews the user experience versus online reviewers (some of them may not be expressing unbiased opinions).
[8125, K-JAM, P4300, MDA Vario General] DonnieZ:
It seems that as of late I have to re-align my screen almost on a daily basis. It will be ok vertically, but horizontally it seems that it's always shifting.

Has anyone else ran into this?
[8125, K-JAM, P4300, MDA Vario General] markgamber:
Yep, I've run into it. Sometimes it can go days without having to realign it, other times I have to realign it every 15 minutes. Seriously. I thought it might have something to do with opening and closing the keyboard but it's been hit and miss so far. I can't prove that it and I can't prove that it isn't. Sure would be nice to figure out what it is, however, and have it fixed.
[8125, K-JAM, P4300, MDA Vario General] abubasim:
How do you carry your phone around? Do you keep it in a case on a belt clip or do you keep it in a front pocket of your pants? If you do not use a case then try it for a few days and see if this helps with the alignment problem. (Body heat and/or pressure on the screen may cause the alignment to drift.)
[8125, K-JAM, P4300, MDA Vario General] xenos:
This is a know hardware defect. It should be covered by your warrenty. T-Mobile exchanged mine with no problem.
[8125, K-JAM, P4300, MDA Vario General] GapBoyT:
Mine had the same issue but it hasnt been an issue since the 2.26 update on Tmo.
[8125, K-JAM, P4300, MDA Vario General] optical:
I had my phone replaced and it's still having the alignment issue. This sucks bad. Realigning and resets doesn't help!
[8125, K-JAM, P4300, MDA Vario General] chnky18:
Getting rid of magic button and vbar, if you run those apps, did the trick for me...I switched to wisbar desktop and ever since I have not had to realign my screen once in 2 months
[8125, K-JAM, P4300, MDA Vario General] bam099:
I'm going to try this out and let everyone know. I'm having the terrible screen alignment problems (I at first thought that it was the keyboard and switching landscape mode) but I have magic button installed. Going to try the switch to wisbar lite and see if that helps. Does anyone know if the business card trick for the hermes will help with this?
[8125, K-JAM, P4300, MDA Vario General] sevenfire:
I think it is a hardware defect, i have problems with mine, not only i have to re-align it often, my screen is also not responding to touch either. (from time to time).
[8125, K-JAM, P4300, MDA Vario General] bam099:
Not to respond right away without extensive testing, but I did just put on wisbar lite and noticed a definite improvement in aligment (certainly seemed better than magic button) someone else should try this too and see if they notice an improvement.
[8125, K-JAM, P4300, MDA Vario General] Avatar28:
I was having this issue for awhile. The card trick had helped on my previous 8125 but not this time. Carrying it in the case instead of my pocket seems to help quite a bit. The issue also seemed to be affected by pushing on the plastics around the screen so that might be a clue right there too.
[8125, K-JAM, P4300, MDA Vario General] dankaren:
align

delete
[8125, K-JAM, P4300, MDA Vario General] Avatar28:
Sounds similar to my fix of pushing on the plastics all the way around. I haven't really had this problem since I did so and I have only had to realign it a couple of times in the last few weeks.
[8125, K-JAM, P4300, MDA Vario General] GldRush98:
my phone's alignment used to get screwed up multiple times a day.

I took the stupid stick on screen protector off it though and haven't had that problem nearly as often. I maybe realign once a week, and when I do, it's only because it's off just a bit.
[8125, K-JAM, P4300, MDA Vario General] new2city:
I had alignment problems frequently a few months ago but it is all history now.

1) Fix current alignment problem.

Just make sure you confirm if it is a hardware defect first, by checking the tiny gaps between the touchscreen and the casing for dust particles. Use a high power scope(I work in a semicon backend company so no problems getting one). Clean the gaps all around the touchscreen. See if that fixes your alignment problem. If it does, then probably your screen has some electronic problems(claim warranty).

2) Protect your screen from pressure at ALL times except when you use it with your stylus or finger.

I carry my Wizard in my pocket with a plastic transparent plate covering the entrie screen(ala HP's RW6828 forgot that model already).. Have been doing this since last year and no alignment required since last year...

Just wonder why HTC doesn't make it an option of have the protective screen on their devices... Beats having a bulky casing..
[8125, K-JAM, P4300, MDA Vario General] thevic:
Permanent fix for Alignment problem in 10 seconds

Well I read many posts and finally came to the conclusion that the best and permanent fix for the alignment problem is as under.

Slide out the keyboard, you will find 2 screws at the back. Loosen them and then retighten them but not as hard as they originally were but lightly.

Presto

Problem solved.

U will never see your screen misalign again.

Thanks
[8125, K-JAM, P4300, MDA Vario General] goofeyass:
software problem

The original Cingular wm5 rom had this alignment problem, I flashed NBD's WM6 v5.1 rom and it was fixed. I tried other wm6 roms with mixed results, some would get misaligned, others alignment stays perfect. Anyway the NBD rom just works, improves battery life, speed, I could go on all day.

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