yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] FFDA:
I did this so long ago, but I think gdisk is in the /rbin directory. If that's the case you have to

cd /rbin

before doing anything with gdisk.
[Android Software/Hacking General [Developers Only]] romanlynch:
Tried it again and got the same errors. I think it has something to do with the error in the first pic. Also, how do I check to make sure my SD card is formatted the right way in Win10? I right click - properties and I see it's FAT32 but I can't find any other info about the format. Is there a way to format the SD card through cmd prompt?

dd: can't open '/mnt/extsd/brnects0.715/kas.boot.bin': No such file or directory

cp: can't stat '/mnt/extsd/brnects0.715/build.prop': No such file or directory

https://imgur.com/J2JV5Sb

The second error is the gdisk one and I cd /rbin before the command

https://imgur.com/nTskHrM

EDIT: the file is named sgdisk but in the directions it just says gdisk. Am I supposed to be typing 'gdisk /dev/block/mmcblk0' or 'Sgdisk /dev/block/mmcblk0'?
[Android Software/Hacking General [Developers Only]] FFDA:
So I reading through alex-kas guide again.

If you can't get into new recovery you should redo that step again, because I was wrong. Gdisk will be in your path after new recovery is installed. Just the backup scripts and what not will be in rbin.

You should not reformat your sdcard, because it already has backups and you will lose it. As far as I can tell your sdcard is fine.

As I said before just redo recovery and you should at least be able to get into recovery. After try repartitioning.

That's the best advice I can give you.

Good luck.
[Android Software/Hacking General [Developers Only]] romanlynch:
Got it :D for some reason it didn't load the superuser stuff.

Also, is the only difference between the kas.recovery.bin-0.9 and 0.9.2 that the partitions are preset? I set them to

13 2818048 13303807 5.0 GiB 8300 userdata

14 13303808 13565951 128.0 MiB FFFF GROW

just like he had in the instructions. If I'm reading it right 0.9.2 does that for you so you don't have to delete/add the partitions, is that correct?

And last question, can I try any rom or does it have to be ice cream sandwich?
[Android Software/Hacking General [Developers Only]] FFDA:
There isn't any custom rooms for NEC Terrain. If you try to load a random one it will brick your phone. Unless you will get very lucky and you will find one that is compatible with your phone. At least that's my understanding.

The only change between recovery.bin 0.9 and 0.9.2 is that the latter has two scripts that you have to execute if you want that they do something. But as far as I understand you already repartitioned the phone following the guide so they will not do anything for you. If you install new recovery or boot image it does not change partition table of the device.
[Android Software/Hacking General [Developers Only]] romanlynch:
Cool, thank you for the help.

---------- Post added at 07:55 PM ---------- Previous post was at 07:06 PM ----------

Sorry, 1 last thing. I downloaded superuser and tried running it and it said root was not detected. I read the 'readme' in the system folder and was wondering if these were implemented when I went through the guide or if I had to load them myself.

superuser.tar.gz - contains su binary and Superuser.apk

apk* - contain program lists discussed below
[Android Software/Hacking General [Developers Only]] romanlynch:
So I tried redoing all the steps to try and get superuser loaded and running. I messed something up and now the phone boots, I get the NEC screen but then it's just blank. I take out the battery and hold the down button while putting the battery back in and it will boot to recovery, still blank screen. What can I do to fix that?

Also, I was re-reading alex's github stuff and I reformatted my SD card as MBR fat32 with a partition (I just halved my 16gb card) but I couldn't figure out how to name them like this:

Device: /dev/mmcblk0p1

Does the name really matter?
[XDA Assist] leojxda:
Hi guys, I've been searching on this forum about this concern and there are many similar threads about this one, however, it doesn't suit to my situation right now. Okay, so I was able to extract my bootanimation.zip from my android phone and there are 15 images inside a particular folder and what I did is just I customized them, changing the graphics cause I don't really like how it looks. now I re-zip folder with normal compression then I copy the file into my sdcard then to my system/media directory and also to my system/data/local directory with 644 permission on both files. Of course I rename my original boot file.

Here's the problem, before I copied the bootanimation.zip to data/local/ directory, after I reboot my phone, it only shows the main or the primary logo of my default bootanimation.zip then, the rest is just plain black. no animations at all. Then I tried to copy the bootanimation.zip file to my data/local/ directory and I found out that my boot animation was changed but the problem is, my custom bootanimation.zip is not detected as what I expected but it shows the default android logo (not the green one) it looks similar to this one "default android logo.png" (see my attachement) I think it's nicer rather than my default one but I don't know what's going on here. I really preferred to make it something different and I don't know if there's any other way to accomplish this one.

I hope you guys can give some advice. Thanks a lot.

Anyway, attached file is my custom boot animation.
[XDA Assist] rirozizo:
Hello, thank you for using XDA Assist.

Use THIS GUIDE to make your own customizable bootanimation. Unzipping/rezipping generally doesn't work that way.

This is the best/easiest method I've found so far.
[XDA Assist] leojxda:
Thank you sir, let me have a look.
[XDA Assist] leojxda:
Hi sir, it works perfectly... love it. thanks a lot!!!

I have another concern with the first brand logo, is there any way that we can get rid of that?
[XDA Assist] rirozizo:
Try asking in the linked thread ;)
[XDA Assist] leojxda:
Thank you sir,;)
[G4 General] chrisokaly:
If anyone is looking for a solution to touch screen issues where scrolls register as taps, go to settings>accessibility>motor & cognition and set Touch Feedback Time to Medium (or Long, your choice).

I factory reset my phone, and it improved a bit... but was bored and cycling through some menus and saw this. Since I changed it I haven't had a single problem.
[G4 General] jerflash:
i will give this a try today. let you know my results. I set mine on medium
[G4 General] Shaffer678:
On vzw its actually under dexterity and interaction. Will give it a shot and see how it goes thanks!
[G4 General] liamR:
I'll give it a try too. Will report back. Thanks!
[G4 General] karendar:
As of now, this seems to fix my Knock to Wake issues I've been having! BEAUTIFUL! You rock!

Did not have many touchscreen issues to report though, but I'll make sure and keep everyone posted if I notice any improvements.
[G4 General] jerflash:
Since turning it on medium in this short time I will say it is better. Knock to wake works much better but like [MENTION=423607]liamR[/MENTION] above I did not have as severe issues as others have reported. Will report back at the end of the day again
[G4 General] kmcphee:
Set to long. Works fantastic. Thanks!
[G4 General] mrxjhsnx:
This seems to help I think
[G4 General] daddymikey1975:
Set to long. So far, there an improvement but not perfect. Digging this little gem so far. Thanks for the find.
[G4 General] tveith:
No change for me. Tried medium and long. Still missed taps and lag.
[G4 General] jerflash:
factory reset the phone...pretty much your only option to fix. If not you may have to get a replacement
[G4 General] tveith:
Haha I've exchanged the phone once and factory reset twice. I have tried developer options, screen booster app, etc. The missed taps aren't horrendous, but just bad enough to make me want to pull my hair out when typing an email or text. I have 1 day left to decide if I want to trade it for an s6 edge. Just know I'll miss the removable battery and sd slot. Decisions decisions.
[G4 General] Red_Baran:
Seemed to have helped! At least so far.

Sent from my VS986
[G4 General] player911:
On the Verizon Model, the location is little different, as noted:

Settings>Accessibility>Dexterity and Interaction>Touch feedback time: [Short, Medium, Long]

Just did this, so I have no response to whether there are any changes.
[G4 General] RedOCtobyr:
Thanks for the tip! Unfortunately, I haven't noticed a big difference yet, and still has a failed knock code attempt, but I'll need to give it more time to evaluate better.

At least with Verizon, however, this does seem to involve a bit of a trade-off.

When long-pressing the square button on the home screen, for instance, I need to hold it longer before I get the long-press menu. Quite a bit longer, if set to Long vs Medium, coming from Short.

This seems to apply in other apps, as well, for holding the square button. I don't notice a difference in how long I need to long-press a Google Keyboard key to get the alternate character. Long-pressing on text to select it seems to take longer.

This may be obvious to everyone else. But as I'm not sure what this setting really controls, I hadn't expected it.
[G4 General] john306:
I've just gone from short to medium and the one issue I had with swipes becoming taps seems to have been resolved... Cheers
[G4 General] chrisokaly:
Glad this is working for the most part. I've gone 2 days strong with no more scrolls registering as touches.
[G4 General] Azure1203:
Factory reset originally worked for me, but will try this as well.
[G4 General] billybong10:
Set mine to medium. Completely fixed it on T-Mobile. Thanks OP!
[G4 General] Swizzle82:
I don't know.. Impretty sure this only adjusts the time it takes for something to react on a long press.. If you set it to.medium or long it will take longer for long pressed items to react.. Could be wrong, but I think it's placebo..
[G4 General] Animatorman:
I'm pretty sure you're correct and most are just experiencing a placebo (wishful thinking)
[G4 General] shook187:
I can see how this could affect the "swipes registering as taps" issue.
[G4 General] KiaAfzali:
If I were you, I would return it. 5 new phones are coming out in the next 2 months for you to chose from. The new Nexus, OnePlus2, Note 5, Moto X, and Iphone 6s. If you have a backup phone, just use it until these come out.
[G4 General] tomtomhr:
It seems that it works for me, no false touches when scrolling since set it to medium. Before that I couldn't surf the web normally because almost every scroll ended up on some other page.

Setting name doesn't say anything about "long press" or something similar. It says about regular touch and I think that low value causes false taps because phone constantly lags a bit and have problems with processing scrolling movement when lag occurs. When set to medium or higher it has enough time to recover from this tiny lags.
[G4 General] Cwey55:
If this works I'll be wicked friggin happy. The swipes turning to taps and missed taps are one of the only things bothering me on this phone! Just changed it to medium, seems like kind of a trade off. The swipes may not register as taps now but on the downside I do believe the long press duration is noticeably longer.
[G4 General] Animatorman:
Sorry I just don't see an improvement but what I do see after changing it to long is an extremely long wait during press and hold instances. Change it to long and then go in and press and hold to delete a picture or text message and you begin to wonder if it forgot about you.
[G4 General] tveith:
I've decided to keep the G4 for a year. I'd like to see if it gets rooted. Perhaps a custom ROM will resolve some of these issues. In the meantime, today I tried a few different keyboards. I've been using SwiftKey forever (with my last four phones). When I changed to TouchPal, I seemed to be able to type pretty much non stop without any missed taps or errors. I'm starting to think that part of the problem was with Swiftkey. It seems to lag / miss taps at times when it is trying to load predictions. TouchPal seems to load predictions much faster. Also tried the LG and Google Keyboards again. Also less missed taps. It really is a pain in the as* trying to figure this touch screen issue out. LG really needs to man up and take some responsibility for this. I never had these problems on my S4 or G3. For now, I'll stick with the TouchPal keyboard as it is definitely working better and eliminating some of my frustration.
[G4 General] Ken4G:
Well that's because that is exactly what that setting changes. :good:
[G4 General] Animatorman:
Lol yeah I know, my sarcasm is subtle.
[G4 General] liamR:
Afrer more than 24 using the phone, I don't see any change.
[G4 General] Lock-N-Load:
Agreed.

Total placebo.

Make the change from short to long and then go long press something. Make the change back to short and go long press something. THAT is what this is for.
[G4 General] chrisokaly:
placebo or not, im now 3 days and have had an absolute flawless experience.
[G4 General] creaky:
Working well on medium setting - thanks! Used to misinterpret swipes as taps, no problems now!
[G4 General] Swizzle82:
Maybe you guys have really heavy thumbs that press on the screen a bit longer than others. I've never had a single tap/swipe swipe/tap issue and this is my third G4..
[G4 General] ambervals6:
Touch is not where it needs to be yet. Those that say is fine maybe haven't used a smartphone in ages. If we had root and some custom kernel the touch issue would have been solved very easily.

Sent from my LG-H811
[G4 General] liamR:
Unless of course it's a faulty hardware. According to my sources in LG, there isn't a fix on the way (for H815 international)...
[G4 General] MooseJC:
I've had incredible results since changing this to medium (H815EU), so THANK YOU.

Here's the thing - it's slightly changed the 'speed' I use my phone at, BUT, there's much more 'consistency' now if that makes sense. Double tap to wake/screen off works almost flawlessly now, meaning I'm comfortable enough picking up/putting down the phone and tapping it on/off without having to visually check and retap (this was happening ~30% of the time previously). Makes a big difference to the user experience for me when I'm doing that multiple times an hour. Also as some of the rest of you have said, scrolling has also improved massively for me, so good stuff all around. Slightly longer response time for long press is something I'm willing to trade off for this increased usability.
[G4 General] ambervals6:
Not hardware. Have seen such stuff happen since nexus 4 days. Always get easily fixed by making some kernel changes.

Sent from my SM-G920T
[G4 General] megamanfre:
I use swype and find that although the swype typing works nearly flawless, the tap to type us horrendous. Have no problem with any other keyboard but it's the only one I can rely stand using, even though it doesn't have a number row.
[G4 General] flamadiddle:
Setting mine to medium completely fixed all issues I was having. I was only have rare missed taps when typing (SwiftKey). Now, no touches are missed at all. Crazy. I have the double-knock-to-wake feature disabled, so can't comment on that.
[G4 General] lawrence750:
I'm not saying I think this is a fix/workaround, I haven't actually decided yet, but here's my logic as to why I think it could make a difference:

If the delay is set to short, then whilst swiping, the delay may be so short that some bug in the firmware (this touch bug) then decides that it is a tap and hold, but then other lines of code relating to the touch drivers say something like "this isn't possible, he's swiping not tapping and holding, I know this because the finger has moved..." All of this confusion within the code, causes it then just to tap instead.

Set the delay to medium, and this would be a workaround, that stops it trying to register as a tap and hold in the first place, which actually results in a tap.

I'm struggling to explain what I'm thinking here, even if the above was the case, I believe that there is still a bug in the firmware that needs addressing, as we should be able to use it properly with this delay set to short.

I must say, I'm not 100% decided yet, but since changing it to Medium, the phantom taps *seem* (as I say, not ruling out placebo effect yet) to have reduced considerably and the general phone experience does seem better.
[G4 General] droidrev71:
Definitely a difference. Not a placebo effect either. This is my second g4. My first one was bad with the touch screen issues. I liked the phone so much I decided to buy another and I'm glad I did. I do still get mis touches here and there. Changing the setting to medium has eliminated any of my occasional mis taps/swipes. I can fly through the home screen and app drawer without any mishaps..
[G4 General] rgs2:
I use the great Fleksy keyboard that uses swipes to enter spaces and periods and setting this to medium makes everything work much better. Before it would frequently enter swipes as taps. Now that doesn't seem to be the case.
[G4 General] Ramsey:
My theory as well, the bug isn't necessarily hardware but software. Probably a sensitivity issue and when set to medium, it doesn't activate as fast so you don't get missed taps anymore. Some are reporting that it didn't work so I'm not sure about that.

I don't have the phone yet lol so I'm still monitoring the situation to decide between this and the M9.
[G4 General] lawrence750:
I agree, I remember when the HTC One X first came out, I got it just after release, and there was this issue where the screen backlight was flickering like an old dodgy lightbulb. Only some people had it, and replacement devices were mostly resolving the flickering issue, however this turned out to be a firmware bug.

They released a series of updates, and those people who either held out and didn't get a replacement, or those people who couldn't get a replacement for whatever reason, had the issue fixed by these updates.

Based mostly on the experience above, I'm convinced this is a software and not a hardware issue. Especially due to the intermittency of this touch problem...

EDIT: I just realised you're considering between this and the M9. I haven't used the M9, or infact anything more recent of HTC's than the One X. But I will say, that I had to go through 7 replacements in order to get one that was satisfactorily made. I had a number of build issues, forget the flickering screen which probably did account for 1 or 2 of the replacements, but the rest was down to speaker holes that were drilled wonky (there was a line of holes, and 2 of these were off by 3-4mm, as if the phone/mount had slipped whilst drilling during the manufacturing process.. Then there was one where the screen hadn't fitted properly into the case itself, and there was a sharp edge on the side of the phone, then there were multiple dead pixels over nearly every one I had, including the one that I had last, when I eventually gave up and just settled, as with that last one, it had 2 dead pixels I believe, but for the first phone out of the 7, had no other issues... So I quit whilst I was as ahead as I was ever going to get. That experience sucked.
[G4 General] dontpannic:
I changed the options a few days ago and now the amount of swipes recognised as taps are far fewer than before I changed the setting. Much, much better. Thanks for the tip!
[G4 General] Biker1:
I've been using my G4 for a couple of weeks now. The touch screen not registering touches intermittently has been a pita. Would happen in all areas of the screen, and several times within 20 minutes.

I just toggled the 'Force GPU Rendering' option found in Developer Settings and my screen hasn't missed one touch in almost an hour. What a difference. I've read where this hasn't helped everyone, but this change is working for me.
[General Questions and Answers] little_tear:
Where i can found the link for the original TWRP 2.6.3.0 touch recovery?

The link from the post http://xdaforums.com/showthread.php?t=2506997 comes to a movie [HorribleSubs]%20World%20Trigger%20-%2030%20[720p].mkv ?????
[General Questions and Answers] :
https://twrp.me/devices/motorolaxoom.html
[General Questions and Answers] armido:
TWRP 2.6.3.0 R.A.H BigPart Edition Recovery

The link to TWRP 2.6.3.0 R.A.H BigPart Edition Recovery takes you to Dev-Host, which for a file hosting website is useless! Trying to download this file takes you from advertisement to advertisement and exposes folks to potential malware. One page was even blocked as an attack page. Long story short is I need TWRP 2.6.3.0 R.A.H BigPart Edition Recovery to successfully restore my Everest (European version) Xoom (BigPart partitioned) and cannot find a download source anywhere.

I'd be grateful if someone with this file will send it to me.

Thanks!

*p, li { white-space: pre-wrap; }TWRP 2.6.3.0 R.A.H BigPart Edition Recovery
[General Questions and Answers] Creepergames360:
https://androidfilehost.com/?fid=889764386195932359 Copy and paste it into your browser. Helping you and myself here cuz I couldn't find it either.
[Verizon Samsung Galaxy S 4] dr0832:
So I have a S4 i9545 for Verizon. It was on 4.2.2 rooted and I upgraded using Fireflash with I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Everything seemed fine so I was using Titanium back up to remove the bloatware and then my battery died. When I charged it and booted up it got to the Verizon screen and hung there. I reset and tried several more times. I tried to use odin and flash a stock ROM SCH-I545_VZW_1_20140330160240_yni63xq6zh and I also tried one more. Odin gave a an error and failed. I then tried going into the boot loder and flash the I545_OC1_Stock_DeOdexed_ROMwNK4_BL.zip. Not sure if this was foolish or not. When I booted up I got to a black screen and there was a voice talking, maybe some sort of training, but I couldn't do anything.

If anyone can point me in the right direction on how to unbrick my S4 I would appreciate it. I know I screwed up.
[Verizon Samsung Galaxy S 4] dr0832:
Right now when I turn on the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. I tried connected to my computer and opening kies but it doesn't find it.
[Verizon Samsung Galaxy S 4] graywolfman:
Try disconnecting your phone, completely closing Kies, then re-launching it with your phone still disconnected. Then click Tools > Firmware Upgrade and Initialization then follow the prompts