yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Daniel x88:
Hello, XDA-Comminuty.

I selected a long text with 64 Lines that I wrote with the stock Samsung Keyboard of my Note 3. I wanted to copy it and paste it into a text editor to save it.

Suddenly, this tooltip with the editing options (Copy, Paste, Cut, Select all, clipboard) disappeared, and I touched the keyboard button R with my S-Pen, while the complete text was selected.

I thought: Damn it! What the hell happened?

But I knew, that this is no computer or Omnia 2 (GT-i8000), where I can press STRG+Z (CTRL+Z) or pushing Revert in a context menu (The Omnia II does have this feature actually).

I can't believe that a high-end Android-Smartphone possibly lacks of such a feature.

My question is: Is it possible to revert text changes in a text box? (Something like STRG+Z)

I would really appreciate any help. Thank you.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Daniel x88:
Does it really have no undo feature? Does the Note Five have undo? A current flagship should have this, because the Omnia 2 GT-i8000 from 2009 also had it.
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
I just finished unlocking and rooting my 626s via this fanstic guide http://xdaforums.com/desire-626/help/complete-detailed-step-step-root-t3217505 thanks jtrosky :)

Anyway I kind of messed up and removed a lot of the default aps that came with the phone, I just had to do a reset and now I dont have a home screen or keyboard. This was my first time doing someting like this so I did not even create a backup/recovery.

I know how to correct the problem I just need a default ROM/RUU from another Canadian (preferably bell) service provider so I can reflash it onto the phone. I know that HTC allows you to down load other roms but they are all for american carriers and when I try to install them I get an error stating something along the lines of "invalid service id" details of the default build are as follows : Android version 5.1 and Firmware version 1.21.666.4.

If anyone could help me out I would greatly apreachate it, otherwise I will need to get a new phone because even tho is under warranty as soon as Bell sees that its been rooted and such they wont fix it.

PS hopefully I posted this in the right place I am a new member here.
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
Does it at least boot?

Edit: try flashing this in recovery (I'm assuming you have a custom one, preferably TWRP). It's just a Titanium Backup update zip with the Sense Home and keyboard apps. Let me know if it helped

https://www.dropbox.com/s/jd41x83q0vcq0o3/htc_launcher_keyboard.zip?dl=0
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
Ya it boots into android with out any problem, I just cant getinto google app store to download anything because I can type anything. I am using CyanogenMod recovery as that is the one the guide suggested to use.

Edit: do I launch it via fastboot or load it unto the phone and run threw Cyanogen recovery?
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
Try downloading and flashing the zip I posted above

Put it onto internal memory and flash in cyanogenmod recovery

If that doesn't work but you're able to boot, just sideload/install Google keyboard apk like normal. You'll have to download the apk elsewhere since you can't use the Play Store for now
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
ok tried what you suggested and the phone spat out a whole bunch of errors which are listed in order below they all showed up red.

finding update package

opening update package

verifying update package

E:footer is wrong

E:signature vitrifaction failed

Install failed

E:unknown volume for path [/cash/recovery/log]

E:cant mount cash recover log

I installed the file you provided in zip format into the main folder of the phone, unplugged from computer, restated phone, then selected the same as you would to run the root in cyanogenmod recovery.

is there something I am doing wrong or am I just plain screwed?
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
No you're not screwed.

I'm not familiar with CM recovery.. Can you disable those verification checks?

If not then try putting Google keyboard apk on your phone memory and installing it while booted. Use the file explorer, if you didn't delete that as well
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
ok will have to put default recovery on it first...with CM recovery installed the phone gets stuck at the part "verifying installed aps" but it boots normally if I reflash the default recovery. I dont know if that means anything to you or not.

EDIT: just flashed it to TWRP instead of CM recovery seams like TWRP is the preferred choice
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
Nice[emoji106] So did it work after all?
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
I flashed your zip with twrp and it worked now i just need a file manager apk do I install that threw TWRP recovery the same way as I did with the zip you gave me. I think I am on the road to getting this working again thanks to your help.
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
What installed? It was supposed to install Sense Home launcher and Sense keyboard.

If they installed correctly then you should be good to go already. I can make a zip with the HTC file explorer but if your keyboard is working, you should be able to just download it from the Play Store
[Desire 626 Q&A, Help & Troubleshooting] Rakivic:
Thanks for all your help I was able to get everything sorted out and my phone back working....this time before I start removing anything I will back it up lol
[Desire 626 Q&A, Help & Troubleshooting] maximepull:
Hi,

I am having the same issue here.

I am missing the Setup Wizard so I can't get passed the connect to a wifi prompt.

Tried looking for a Canadian flashable zip..no luck. Tried flash your privous ZIP but I guess I am missing more that the launcher and keyboard to move on :/

I have a Titanium backup on my SD card but not as a ZIP and can launch into the OS without going through the Wizard.

Cheers
[Desire 626 Q&A, Help & Troubleshooting] Surj138:
Try flashing this in recovery and rebooting... it's just a zip with HTC and Android setup wizards. Hope it works

https://www.dropbox.com/s/cfaujbqzf9nbyh5/setup_wizard.zip?dl=0
[Desire 626 Q&A, Help & Troubleshooting] geogolem:
Has anybody had any luck flashing this variant of the HTC DEsire 626s with marshmallow... (Bell/ PC Mobile) Variant?
[Desire 626 Q&A, Help & Troubleshooting] helix512:
sorry to post this here but I have been looking for help on my mothers Desire 626s from eastlink. I really don't care what provider its on I just want to put a Stock Rom on it. it is currently on 1.24.428.4 firemware and the phone keeps asking to update to 1.30.428.3 and it cant. I put a stock Recovery back on the device and it will start the install then it will fail and give me a triangle with a exclamation mark. I have tried 5 or 6 different recoverys and the same thing over and over. I even went as far as contacted HTC and they told me since they DONT and I QUOTE DONT have a copy of the RUU for my phone they cant help me. so I turn to the internet and have been searching for weeks and I cant seem to find anyone who can help me out. so I hope some one here can. thanks
[Desire 626 Q&A, Help & Troubleshooting] maximepull:
Hi and thanks for the zip.

I'm sure it would help alot. Problem is, I don't have a recovery and can't flash through fastboot because my Bootloader is relocked...

If you tell me where to unzip them, maybe I can extract them to the proper location on the phone?

I know a few months passed since your post but my xda account was linked to an email I no longer use...

Cheers
[Desire 626 Q&A, Help & Troubleshooting] maximepull:
I am replying to myself. After trying several things on the phone, I went back to the OS's setup wizard. The second step (2 steps before the crash), has some text and one has a clickable link saying "learn more". It actually opens some phone settings, and from there, you can access all of the phone settings. So I was able to activate Dev mode, OEM unlock and debugging without going through the Wizard!!

Followed the BL unlock procedures on HTC website and as soon as it was unlocked, phone rebooted and TWRP reappeared! I'm saved!!

Thought I would share my discovery in case this ever happens to you too.

I also discovered another possible course of action. When accessing the same "link" to get to settings, go to the network settings and put the phone on Airplane mode. Go back to the setup wizard and skip the connection to wifi. I think it will skip the part of the Setup that made the OS crash.
[Galaxy S II Original Android Development] Lanchon:
Lanchon REPIT: A Data-Sparing Repartitioning Tool for the Galaxy S2 i9100

DUE TO IRRECONCILABLE DIFFERENCES WITH MEMBERS OF THE XDA MODERATOR TEAM, THIS PROJECT HAS MOVED TO GITHUB.

this thread is no longer monitored by me. if you require my help, please DO NOT send me private messages of any kind, post a public question on github instead.

i am sorry for the inconvenience.

XDA:DevDB Information

Lanchon-REPIT-i9100, Tool/Utility for the i9100

Contributors

Lanchon

Version Information

Status: Beta

Created 2016-02-09

Last Updated 2016-02-25
[Galaxy S II Original Android Development] Lanchon:
Downloads

[deleted]
[Galaxy S II Original Android Development] fireburner-de:
Great work, I hope it might help some unexperienced users!
[Galaxy S II Original Android Development] pacman7:
[MENTION=4141005]Lanchon[/MENTION], thank you for the awesome work and support for the SGS2.

Regards.
[Galaxy S II Original Android Development] Acid0057:
[MENTION=4141005]Lanchon[/MENTION] I think I asked this in the cm13 thread, but this can still be used on a S2 gt-9100 on cm12.1 in preparation for switching to cm13?
[Galaxy S II Original Android Development] Lanchon:
the only requirement is that you are running twrp. doesnt matter which os.
[Galaxy S II Original Android Development] the.gangster:
[MENTION=4141005]Lanchon[/MENTION]

Great that you finished your testing and published your script. I was courious already from the day you first announced to work on it. Would have loved such an easy way back then, when I repitted my two i9100 phones.

And as it seems to be 100% Noob-friendly, they will love it, too.

Once more: amazing work! Thank you in the name of all here, that now can simply link to your scripts instead of answering million questions about how to pit.
[Galaxy S II Original Android Development] Acid0057:
Awesome. I'm running your IsoRec Recovery with Arnabs Twrp on my other s2
[Galaxy S II Original Android Development] juapao:
Nice one [MENTION=4141005]Lanchon[/MENTION] thank you for the great tool! Though I'm used to repart my i9100 over Odin. This will make a lot more easier since no need for triangleaway for this one.

I would just like to suggest to give us an option for reverting to stock partition or is "lanchon-repit-v0.1-sys1GB-i9100.zip" the stock one?

Keep the updates coming! Though our i9100 is already 5 years old already, MM OS still works because of your consistent support and contribution with the CM team.
[Galaxy S II Original Android Development] cherryb8844:
I really want to test can you attach stock pit :D I'm still on custom pitted by Odin
[Galaxy S II Original Android Development] Lanchon:
thanks. stock is not very useful. you can switch among 4GB and 6GB data to test.
[Galaxy S II Original Android Development] prazola:
Very nice, but putting the zip in tmp and wiping all the partitions was the only way make this script work. No way from externalSD for me.
[Galaxy S II Original Android Development] Lanchon:
thank you! stock is not very useful and i really have very little time. v0.1 is released just to help people through their upgrade to CM13. i don't want to proliferate files for each and every taste, that's not the proper solution. i rather do it the right way.
[Galaxy S II Original Android Development] Lanchon:
thanks. why would wiping be "the only way" and why there would be "no way" to run from external sd?? there was a VERY detailed log that explained what went wrong if anything. without that info the "no ways" don't really help in any way. and which script and what were you trying to do in the first place?? you don't even say that. i can tell you there was definitely "yes way" the tool would run without wiping all partitions. maybe you had some corruption in one of the partitions, who knows without the log.
[Galaxy S II Original Android Development] vizdak:
Coming from markox 12.1 ROM then full wipe and install AICP MM ROM, gapps, and recovery-Lanchon-Isorec-CM-6.0.5.1. To my surprise my /data is back to 2 GB so I rebooed to recovery and flashed lanchon-repit-v0.1-sys1GB-data4GB-i9100.zip but there's an error:

info: checking tool: parted

info: checking tool: blockdev

FATAL: required tool missing: blockdev
[Galaxy S II Original Android Development] Lanchon:
there's an error indeed: you didn't follow instructions. in particular step #1.
[Galaxy S II Original Android Development] vizdak:
Thanks, my fault. I have to reread again.
[Galaxy S II Original Android Development] prazola:
Sorry, no log, at 3am (time of flash) i wasn't totally lucid. For the external sdcard it was about the mount point of the card (common busy error). Without full wipe I remember a loop while polling system partition to read partition info, maybe related to a corrupted FS, because I recently got some reboot while tweaking the phone.
[Galaxy S II Original Android Development] OrganLoc:
Hi!

Lanchon, first: thank you so much for this great effort!

I was always thinking about how it must be possible to resize partitions instead of just wiping them and start from scratch. But I was lacking the deeper knowledge to realize such a thing without losing data / messing up my phone.

I have a question though: I formatted my sdcard with ext4 a while ago.

Does your tool take care of this?

Thanks!
[Galaxy S II Original Android Development] Drhedphuk:
Hi [MENTION=4141005]Lanchon[/MENTION] thank you for this, this will save a great deal of effort. One question, do I untick 'Only mount system read-only' box or does that not matter?
[Galaxy S II Original Android Development] AddictedToPlaying:
i really do not understand anything from this configuration part. Read this many times but don't know what to do..

Just want to have 1gb partition and not wipe
[Galaxy S II Original Android Development] the.gangster:
Do you use DorimanX Dualboot feature or some other stuff, that depends on 512 MB preload partition?

If not and if your SDCard is formatted as vFat (which is the default), you can use the ZIP as named in the download.

It will only resize and wipe the preload then.

Otherwise (if you really need preload): lanchon-repit-20160213-system=1.0-data=same-sdcard=max-preload=same+keep-i9100.zip

or if you formatted internalSD to EXT4 before: lanchon-repit-20160213-system=1.0-data=same-sdcard=max++ext4-preload=min+wipe-i9100.zip

or a combination of both.
[Galaxy S II Original Android Development] AddictedToPlaying:
the.gangster i just flashed this rom from stock. I didnt use dualboot etc. I just want to get gapps working on this rom nothing more :)
[Galaxy S II Original Android Development] the.gangster:
[MENTION=5805436]AddictedToPlaying[/MENTION]

Well then you've got the answere. (Take it as is)
[Galaxy S II Original Android Development] AddictedToPlaying:
[MENTION=6560258]the.gangster[/MENTION] oh god this was so simple. Thanks for help, it's really late and i stopped thinking :P i flashed this and everything works fine
[Galaxy S II Original Android Development] Acid0057:
Sorry if this is a little off topic. Might be better in the cm13 thread.

Are you using Open Google Apps? That's what I use and I'm getting no force closes or errors. You'll have to wipe system again and install cm13+open google apps to test. Also make sure you're getting google apps for Android 6.0 arm. Not arm64 or x86. We need ARM and 6.0 for CM 13 on gt-i9100
[Galaxy S II Original Android Development] chhapil:
Solved: Error repitting system partition

Hi Mate, first of all thanks a ton for such a wonderful tool.

I decided to give a shot at CM13, so ultimately decided to use to tool.

I'm getting following error while repitting with following config

----- CONFIGURATION -----
system: size=1, content=wipe, fs=ext4
data: size=5, content=wipe, fs=ext4
sdcard: size=max, content=keep, fs=vfat
preload: size=same, content=wipe, fs=ext4

But getting following error

===== EXECUTION =====
----- analyzing partition #9 /system (FACTORYFS)
***** processing partition #9 /system (FACTORYFS)
info: deleting the partition
Error: Partition /dev/block/mmcblk0p9 is being used. You must unmount it before you modify it with Parted.

Solved: By flashing lanchon's CM13 isorec kernel.

Thank once again mate :)
[Galaxy S II Original Android Development] Lanchon:
UPDATE: new release !!

20160216

-added automatic support for 8, 16 and 32 GB variants of the i9100.

-now attempts to salvage the partition data in case of a hardware read error while moving an ext4 partition around.

-some improvements to sanity checks.

enjoy!
[Galaxy S II Original Android Development] Lanchon:
thanks for the report! glad it worked
[Galaxy S II Original Android Development] Lanchon:
hmmm your internal sdcard seems pretty screwed up; usually dosfsck is able to fix it.

can you even mount it at all? are you sure it's FAT and not ext4?

EDIT: wont help with this in particular, but i suggest you uprade to the new script before continuing.
[Galaxy S II Original Android Development] Lanchon:
you don't seem interested, but anyway, i added autodetection for your device.
[Galaxy S II Original Android Development] Talkrabb:
​Hi Lanchon,

the phone works just normal. I'll try your new script (I downloaded the one I use just yesterday):

lanchon-repit-20160213-system=1.0-data=4-sdcard=max-preload=min+wipe-i9100.zip

In TWRP I can mount/unmount Cache, System, Data, eMMC and Micro-SD (Storage: eMMC 9601 MB). The TWRP File Manager shows the /sdcard directory and the files inside.

Diskinfo says SD card (UMS) is ext4.

Now I try: lanchon-repit-20160213-system=1.0-data=4-sdcard=max++ext4-preload=min+wipe-i9100.zip

Script busy since 5 Minutes keeping fingers crossed that it runs through...
[Galaxy S II Original Android Development] Lanchon:
yes, it was your fault.

why are you using "preload=0.5+wipe" instead of "preload=min+wipe"?

if a mistake, suggest you re-run correctly after it finishes.
[Galaxy S II Original Android Development] Talkrabb:
Sorry,

lazy copypasta, I use preload=min+wipe.
[Galaxy S II Original Android Development] Lanchon:
so what happened?
[Galaxy S II Original Android Development] Talkrabb:
Had to run the script twice (second time after manual unmount). SUCCESS!

Now going for CM13.

Thank you for your help.

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] AngelGR:
Hi. Thanks for your excellent work! You've made the repartitioning process as easy and safe as it can be.

But I have a minor problem. It seems that my internal sdcard partition can not be formatted as vfat, and I don't know why. I've followed your instructions step-by-step, and you can see my config in the picture. If I change the format to ext4 works fine.

I've tried to flash the file from external sd too (so that option works, if someone is interested), with the same results.

Thanks again ;)
[Galaxy S II Original Android Development] Ponsel:
I found in the last (changelog the string:

t0lte: Enable F2FS(android_kernel_samsung_smdk4412)

Does your script support F2FS?

If so, that would be my primary choice for cache and data partition. ;)
[Galaxy S II Original Android Development] Lanchon:
hmmmm interesting... it looks like you found a bug in the mkfs.vfat tool. maybe the partition is too large for the 32-bit build you are using. what recovery are you using? what is the size of your internal sdcard?
[Galaxy S II Original Android Development] Lanchon:
a line in a changelog doesnt mean a thing. CM13 probably does *NOT* support F2FS for now.

why cache??? that's completely pointless. you need to research what cache is used for.

no, the tool doesnt support it and wont. F2FS does not support resizing for now, AFAIK.

but that doesn't matter: just resize the partitions and afterwards convert to F2FS.

keep in mind that TWRP currently doesn't support F2FS either, so you'll be pretty effed up if u did that.

unless you develop it yourself, you wont have F2FS until some developer announces it.
[Galaxy S II Original Android Development] pilotn:
Great great great tool.

Thanks [MENTION=4141005]Lanchon[/MENTION]

Repit without format is a big time saving
[Galaxy S II Original Android Development] Acid0057:
Not to mention much much safer than using Odin with a kernel and pit.

Just ran the latest version on my other s2 as I had used the 0.1 release. Working great here no errors.
[Galaxy S II Original Android Development] Ponsel:
You are right!

The Patch refers to a Change which enables the galaxy S3 to check if F2FS is present and if so, to use it.

That does (as you correctly mentioned) not mean that TWRP supports it and neither our kernel. So I was a little bit overexited.

As far as i know F2FS was created to "take into account the characteristics of NAND flash memory-based storage devices". The most interesting part for me is, that they tried to avoid writing on the same sector over and over again which would otherwise decrease the lifespan of the NAND chips. I'd chose data and cache as primary targets for this file system, vecause they are written frequently. By doing so I'd hope to increase the time of use of our device.

Whenever F2FS is available (for kernel and recovery) I'll try exactly that.

That will probably never happen, because I don't know how. All I can do is press my thumps and hope. ;)
[Galaxy S II Original Android Development] the.gangster:
But there have been already other users here, who reported errors due to configuring the "wrong" filesystem.

Although they just wanted to resize, but in the end it failed due to configured fs-type (in the zip's name) not matching the current one. Although if I remember right, they failed on fschk-ing when configured to keep, not wipe (as is now).
[Galaxy S II Original Android Development] AngelGR:
- Following your instructions, IsoRec TWRP by arnab

- Internal memory: 16 GB

- More info about my partitions (trying again with 1GB system / 8GB data / max sdcard):

Anyway, it's not a big problem, since I can format as ext4 and it works fine.

Thanks!
[Galaxy S II Original Android Development] Lanchon:
nope, neither: they dont try to avoid writing the same sector over and over, and writing same sector o & o does not decrease lifetime.

because there is an FTL in the middle! F2FS is NOT designed to run over naked flash. it cant run over an MTD. it is not a flash file system.

anyway, cache is never written to. using f2fs there is as good an idea as using it in system
[Galaxy S II Original Android Development] Lanchon:
reformat the partition to vfat using twrp. ill have to look into this.
[Galaxy S II Original Android Development] KickerTom:
Considering the latest posts, I was thinking: if I specify keep for a partition, the fs type can't be changed anyway, so can't the script 'autodetect' current filesystem (e. g. by mount, list mounts, unmount)? Maybe that would make it even more foolproof?
[Galaxy S II Original Android Development] AngelGR:
OK. Using TWRP:

Updating partition details...

...done

Full SELinux support is present.

MTP Enabled

Formatting eMMC using mkdosfs...

Done.

E:Unknown MTP message type: 1

Updating partition details...

...done

Format Complete

Successful

Under CM 13 all seems ok, it doesn't matter ext4 or vfat.

Anyway... is there any advantage of vfat over ext4 in this case?

And... is there any chance of save a few bytes more in sdcard partition with tune2fs?