yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
read 1st post in that thread to make sure , but i think it says to flash MJB then fully reboot phone , go back into recovery and flash NE4. then you should be all set. thats how i did it when i upgraded anyway. please remember you CANNOT downgrade or it WILL brick your phone. :thumbup:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ionutbarna:
Yes but, in this thread of a rom: http://xdaforums.com/galaxy-s3-att/development/s3rx-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080 says on intructions that "MUST BE ON I747UCUEMJB FIRMWARE BEFORE FLASHING, OR FOR RESTORING NE4". So i need to flash a 4.3 firmware?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
If you have an 4.1.1 lk3 bootloader and 4.1.1 lk3 modem , use Odin to flash back to completely stock 4.1.1, unlock your phone if not already done, and run OTA updates until you get to the latest stock ROM. You can then install a custom recovery, flash supersu, disable know, and flash custom ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
i believe those instructions are for flashing the NE4 firmware. in otherwords dont jump from LK3 to NE4. do it in steps.

your on LK3 > go to MJB > then to NE4.

"all i can really do , is stay out of my own way and let the will of heaven be done"

---------- Post added at 06:33 PM ---------- Previous post was at 06:30 PM ----------

thanks audit , i always forget about going back to stock and unlocking.

:good:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ionutbarna:
I have done it that. I have a stock rom with a custom recovery and root and now i'm trying to flash that rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Remember, flashing via Odin will put everything back to stock, including recovery, apps, etc. It will also wipe all of your data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ionutbarna:
Thanks, but tell me: i need to get a 4.3 firmware on MJB bootloader and modem to flash NE4 or will work fine on 4.1.1 firmware with MJB bootloader and modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Flashing back to stock and running OTA updates will progressively update the modem, bootloader, and ROM; that is, the 4.3 OTA update will take everything to mjb.
[HTC One SV] -=GQ=-:
Download here

Donate here

[IMG="Say 'Thank you' to Alexander"]https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif[/IMG]

Changelog:
[HTC One SV] -=GQ=-:
App Storage of 6,8GB

Phone Storage
[HTC One SV] Near710:
There would be an easier way ? or otherwise make 3gb data and 2 internal sd ? anyway, congratulations : D and sorry for my bad english xD
[HTC One SV] Ivory_75:
Hello ,

Thanks for your post.

That would be Wonderful !!!!

Please can you confirm which K2 model you use ? (K2UL or something?)

Alos i understand you have a TWRP boot :

it means : S-OFF & Root ?

The more detailed it is, the best it is !

Thanks, and Congrats !
[HTC One SV] -=GQ=-:
Definitely yes.

No.
[HTC One SV] -=GQ=-:
The main idea (posted above) is proof of concept. It could be implemented with any rom/firmware/model (even not only K2). All you need is unblocked bootloader and you do not need S-Off.

But right now I'm testing fully automatic method, it will be released soon.

Successfully tested on K2_UL S-Off TWRP_2.7.1.1 Stock JB rom.

K2_U support work is in progress, there are minor issues.

S-Off is not needed, I think, but may be wrong.

Root is not needed.

TWRP 2.7.1.1 is the only supported recovery, I did not tested any other.

Script supports only JB stock based roms, but other roms could be added in the future.
[HTC One SV] -=GQ=-:
Ok, several phones (K2_UL and K2_U) were successfully converted using new automatic method.

You could try it right now from here [1].

Instruction is in Russian for now (you can try google translate), I will put English one in 1st post later today.

[1] http://4pda.ru/forum/index.php?showtopic=439253&st=7020#entry37175308
[HTC One SV] -=GQ=-:
Tadaaam! Post is updated with new end-user friendly instruction.
[HTC One SV] Near710:
After reboot says Type Password to Decrypt Storage... what can i do?
[HTC One SV] -=GQ=-:
Sad to hear this.

Please write here your configuration (model, rom, recovery, s-on/off) and output of swapper READONLY command. This will allow me to find problem in swapper script.

Then just restore your phone from backup as described in top message.
[HTC One SV] Near710:
K2U Stock Rom

TWRP 2.6.3.2

S OFF

Try to restore but nothing..

Solved by flashing RUU
[HTC One SV] -=GQ=-:
That looks very strange, because the dump you posted shows, that you have stock unmodified partitions and even signed boot.
[HTC One SV] BHoller:
any chance this would work on k2_cl(boost)?
[HTC One SV] -=GQ=-:
There is support in the code of swapper, but nobody has tested this.

Sent from my HTC One SV
[HTC One SV] Ivory_75:
Hello

I'm trying to do the swapp. On Readonly, i have the following message :

../abootimg: not found

what's wrong ?

abooting appears in the /tmp folder with TWRP....

My phone

TWRP 2.7.1.0 (same error with 2.8.0.1 version), phone K2_UL unlock, root, s-off (S-off is complicated and required root. and it is too risky to try it with S-On )

Thanks for your help;
[HTC One SV] BHoller:
my concern is that the boost variant is most likely formatted differently and this could actually brick my phone indefinitely.. i can recover from a soft brick no problem and i have my backup files but i have never tried to format the internal drive.. ive swapped them with the fstab trick in the past but i found extending the apps to the external to work better.. your method, if im not mistaken, would allow me to use the current 4.45gb "media" partition as the "data" partition and use the 1.22gb "data" partition as "media".. this would allow me to install more apps to the phone without running out of space.. this method doesnt effect the system rom partition at all though? as long as it doesnt modify any of the system rom i should be able to recover if your swapper doesnt work with my variant
[HTC One SV] -=GQ=-:
I use info from /proc/emmc about partitions and modify only recovery, system, boot, data and fat.

As I do no modification to hboot, maximum problem you could get is the phone in fastboot mode. That's my view.

But of course there is no warranty.
[HTC One SV] dx822:
same problem like Ivory_75

Hello,

i have exactly same problem like Ivory_75. Please, how to fix it. thanks
[HTC One SV] Ivory_75:
Ok,

It doesn't work.

Stupid question : running adb command is from system or from TWRP recovery ?

from system, it says /tmp is readonly.

From recovery, it says (after pushing both files):

Possible stock signed boot, stripping signature...

65535+0 records in

65535+0 records out

16776960 bytes (16.0MB) copied, 0.934992 seconds, 17.1MB/s

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Extracting boot:initrd...

1937 blocks

Extracting recovery...

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Extracting recovery:initrd...

12444 blocks

Checking current state...

States: boot: STOCK, recovery: UNKNOWN, system: STOCK

Fatal error: Current state is unknown, nothing changed, aborting.

My guess is TWRP 2.7.1.1 is mandatory, but i can't find it in http://techerrata.com/browse/twrp2/k2_ul

Thanks for your help :)
[HTC One SV] -=GQ=-:
Please test swapper v0.6 from here:

https://raw.githubusercontent.com/g...381ae0ed2df19d0904711afa21402812f2587/swapper

Looks like it should work with openrecovery-twrp-2.7.1.0-k2_ul.img from the link you posted above.

At list I think I've fixed error "States: boot: STOCK, recovery: UNKNOWN, system: STOCK"

But I still don't understand how to reproduce

"./swapper: line 226: ../abootimg: not found"

error.

Which recovery version have you used to get this message?
[HTC One SV] Ivory_75:
I've found out !

TWRP 2.7.1.0 -> default settings don't mount /data partition. :)

Aaaaaannnnd Awesome !!

Reboot, back to recovery, restore /data and /android Secure and PERFECT !

Thanks and congrats, you saved my day !

I'll post a screen capture very soon.
[HTC One SV] marceli-szpak:
Hi. Somebody try use this method with Venom Rom?
[HTC One SV] -=GQ=-:
As I heard, it won't work. Anyway you could try readonly to check compatibility.

Sent from my HTC One SV
[HTC One SV] imankareem:
I am really confused about this..

Could you possibly put up a video, PLEASE? :)

I make a complete backup using TWRP

Then I boot in to TWRP's adb mode..

Type in all the commands ..

Restore from recovery

and then I am done?

How do I reformat to FAT?

I am a noob.. Sorry :(
[HTC One SV] marceli-szpak:
I think if you only want swap /data and /sdcard you no need nothing to format. After restore you have everything on the place. I made this on stock rom and all is ok. Would be grate if this work with Venom rom. I must check.

Wysłane z mojego HTC One SV przy użyciu Tapatalka
[HTC One SV] :
Hey guys, I was contacted to take a look at this to see if it would work with the K2_CL variant. Will do just that to resolve any questions. I did notice that the script will check to see if the image is stock or not but assumes that it is automatically and strips the first 256 buts of code. Not a prefered method honestly and I believe I have a better solution for that which I implemented in one of my own personal scripts a while back. In addition, abootimg should be compiled statically without any dependencies to shared objects dynamically. This will insure that the binary works effectively and resolve the issue of any error reports stating that abootimg "cannot be found". Right off the bat these are the two things I took notice of and I do believe that by insuring those two things are handled properly then any future problems may no longer exist. For the recovery repartitioning scheme, it should work with all TWRP versions available for our K2 devices. The only file in the recovery image that should be getting modified is the recovery.fstab file or twrp.fstab file which both files should be looked for since either can be used in a twrp build given the device tree. I will conduct some more study time in to this and report back later on. Meanwhile, fantastic job OP. Concept is similiar to my thread about making certain mods to allow dual booting roms. Impressive :).
[HTC One SV] -=GQ=-:
No, not to check. I just try to unpack image in-place or, if there is crypto signature, strip it and unpack.

Real check will be later in test_boot (or something like this).

Bingo! Lost this when do initial work, and forget to fix it later.

As for fstab name in some of recoveries, I'll take a look on this.

Thank you very much.
[HTC One SV] :
You are welcome. Also, here is a snippet to check the boot.img/recovery.img. You would need to touch it up of course to fit with your script but it will do the job. Your current method isn't best simply because if the image is not stock and you strip 256 bytes of code off of it then the image will be corrupted since the non stock image is most likely already missing the 256 byte signature prior to the android header.

# Boot.img uses a magic header of ANDROID! so, lets check for strange boot.img headers
SIGNATURE_CHECK() {
check_header=`"$ACTIVE_PROJECT/TEMP/binaries/busybox" od -A n -h -j 0 -N 8 "$ACTIVE_PROJECT/TEMP/boot.img" | sed 's/ //g'`

if [ "$check_header" != "4e415244494f2144" ]
then
ui_print " ";
ui_print "Android magic header not found at start of boot.img";
ui_print " ";
ui_print "Checking if it exists elsewhere ...";
# Look for Header
hex_offset=`$ACTIVE_PROJECT/TEMP/binaries/busybox od -x -A x $ACTIVE_PROJECT/TEMP/boot.img | grep -m 1 "4e41 [ ]*5244 [ ]*494f [ ]*2144" | sed -e 's/ .*//'`

if [ "$hex_offset" != "" ]
then
# Remove leading bytes before the Android header
dec_offset=`printf "%d" 0x$hex_offset`
ui_print " ";
ui_print "Android header found at offset ${dec_offset}";
ui_print " ";
ui_print "Removing extra stuff before ${dec_offset} so boot.img can be read properly ..."
dd bs=$dec_offset skip=1 if="$ACTIVE_PROJECT/TEMP/boot.img" of="$ACTIVE_PROJECT/TEMP/modboot.img"
rm -f "$ACTIVE_PROJECT/TEMP/boot.img"
cp "$ACTIVE_PROJECT/TEMP/modboot.img" "$ACTIVE_PROJECT/TEMP/boot.img"
rm -f "$ACTIVE_PROJECT/TEMP/modboot.img"
ui_print " ";
else
ui_print "Warning: Android header not found in boot.img (unsupported format)";
fi
fi
}
[HTC One SV] Ivory_75:
Ok, as promised,

App Storage of 6,8GB

Phone Storage

and SD Card (i did not swap internal and SD Card...

Thanks again, i think i will keep this phone for anoter 2 years !
[HTC One SV] -=GQ=-:
Thanks for pictures.

That was the reason, I did it. It could serve much longer, just need to fix one small but annoying issue.

Sent from my HTC One SV
[HTC One SV] coolbeans2015:
change app space

**will this workwith my Boost HTC One sv (C525c) k2_cl? I would rather have 6gig of app storage or whateve I can get away with, just direct everything I make, or store to ext_sd.

lee

---------- Post added at 12:50 AM ---------- Previous post was at 12:35 AM ----------

I am running the latest TWRP openrecovery-twrp-2.8.4.0-k2_cl
[HTC One SV] russellvone:
Please do not quote the whole original post.....
[HTC One SV] coolbeans2016:
not finding file or directory

c:\android-sdk\platform-tools\one_sv_swapper-0.6>adb push

failed to copy 'swapper' to '/tmp': Read-only file system

getting read only file system error now ??

open these idiot eyes a little more please

lee

---------- Post added at 03:11 AM ---------- Previous post was at 02:15 AM ----------

this is what I am getting, seems like my only problem now is read only?

c:\android-sdk\platform-tools\one_sv_swapper-0.6>adb push swapper /tmp

failed to copy 'swapper' to '/tmp': Read-only file system

how to I get past this ??

lee
[HTC One SV] -=GQ=-:
Is your phone in recovery, when you do this? What recovery are you using?

Sent from my HTC One SV
[HTC One SV] coolbeans2016:
can't get past this

this is what is stopping me:

c:\android-sdk\platform-tools\one_sv_swapper-0.6>adb push swapper /tmp

failed to copy 'swapper' to '/tmp': Read-only file system

I have root and am becoming more & more knowledgeable every day, but I need help in pointing me in the right direction, please.

lee
[HTC One SV] -=GQ=-:
Stop overquoting and answer my questions, dude!

Sent from my HTC One SV
[HTC One SV] coolbeans2016:
wow

I am at a loss

trying to do the adb push swapper /tmp with phone booted up gets read only error

of course when in fastboot usb adb will not find device...... ?????

just one iota, a tiny bit of help will get me past this, please? anyone? anyone?

:(

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.21.0000

(bootloader) version-baseband: 1.12.50.0516

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) product: k2_cl

(bootloader) platform: HBOOT-8930

(bootloader) modelid: PL8011000

(bootloader) cidnum: SPCS_003

(bootloader) battery-status: good

(bootloader) battery-voltage: 4291mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dc34ae5

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.078s

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>fastboot devices

HT********** fastboot

fastboot finds devices when booted to fastboot usb

when phone is booted to desktop

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb devices

List of devices attached

HT********** device

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push swapper /tmp

failed to copy 'swapper' to '/tmp': Read-only file system

so I am at a loss, this might seem a stupid problem to most but I just do not understand how/what/when/where to type this to accomplish what I have already lined up to run.....

A-N-Y help

:(
[HTC One SV] :
[MENTION=6402619]coolbeans2016[/MENTION], remove your imei, meid, and serial numbers. That information needs to remain private and not made public so go back and edit your post. You are pushing swapper to "/tmp". I assume "/tmp" exists otherwise you are wasting your time. If it exists, then it needs to be changed from read only to read and write permissions. In order to push swapper to the /tmp directory it must be able to write to it. It currently can only read it which is why it fails. If you have root then it would be much easier to just put swapper on your phone via usb storage and use a file manager app on your device to move swapper to where you need it to be.

A flashable zip would make this really simple for those with less technical skills but that will be up to the OP if he wants to make one or not.
[HTC One SV] -=GQ=-:
Read the instruction! You need to boot the phone to recovery, prior calling any adb commands.

Sent from my HTC One SV
[HTC One SV] :
Were you able to ever compile abootimg statically without libc.so and libdl.so being needed? I messed with it a little but compiling it statically either popped off with too many issues or the static libs were ignored and would still link to the shared objects lol.
[HTC One SV] -=GQ=-:
Ah! Thanks for remainder. Totally forgot about this. Need to download toolchain and repeat some hacks, cause my ssd have failed and fixed abootimg's sources are lost.
[HTC One SV] coolbeans2016:
thanks

l will edit the post. That is the problem... can't seem to understand how to change to read/write! Also c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push swapper /tmp

failed to copy 'swapper' to '/tmp': Read-only file system

is what I am getting when I try to push one_sv_swapper-0.6 to the tmp as first command of three:

adb push swapper /tmp

adb push abootimg /tmp

adb shell "cd /tmp&&chmod 755 *&&./swapper /data-4GB flash/sdcard-1GBflash/sdcard/est_sd-external SD"

in trying to mod the app vs phone storage allotment.

any ideas?

lee

---------- Post added at 11:47 AM ---------- Previous post was at 11:19 AM ----------

no, phone is booted up, usb debugging mode. I have TWRP's 2.8.4.0 but have not used it for any of this. I type the adb push swapper /tmp command and get the read-only file error. Adb recognizes the device and commands work while adb shell, su

it says no such file or directory.....

?????
[HTC One SV] -=GQ=-:
This is where your problem occurs. You didn't read the instruction.
[HTC One SV] coolbeans2016:
missed?

Yes, I did read as well as I can. I am disabled, not to go into it, but if it is plain to you, could you please point out

what I am missing, I do have problems, worse sometimes more, than the usual day to day.

zls

---------- Post added at 12:16 PM ---------- Previous post was at 11:58 AM ----------

Okay, I have twrp 2.8.4.0 for recovery, booted in it, nice interface but have never used it except to back up the phone when first rooting it last week.

removed the serial & IMIE and such out of my other post, sorry...

lee
[HTC One SV] -=GQ=-:
Install instructions.

1. Boot into recovery!

then, while your phone in recovery, do call those adb commands.
[HTC One SV] coolbeans2016:
okay:

has install wipe

backup restore

mount settings

advanced reboot

buttons......

what would be the buttons be to get to where to enter the commands?

thanks

lee

---------- Post added at 12:39 PM ---------- Previous post was at 12:26 PM ----------

okay I have gotten to:

1. c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push swapper /tmp

578 KB/s (9235 bytes in 0.015s)

2. c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push abootimg /tmp

270 KB/s (25924 bytes in 0.093s)

3. adb shell "cd /tmp&&chmod 755 *&&./swapper /data-4GB flash/sdcard-1GBflash/sdcard/est_sd-external SD"

saying "not found"

is the last one typed right?

---------- Post added at 12:59 PM ---------- Previous post was at 12:39 PM ----------

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb shell "cd /tmp&&ch

mod 755 *&&./swapper /data - 4GB flash/sdcard - 1GB flash/sdcard/ext_sd - extern

al SD"

HTC One SV partition swapper by Alexander GQ Gerasiov.

Version: 0.6, target state: /data.

Fatal error: unknown target state.

---------- Post added at 01:06 PM ---------- Previous post was at 12:59 PM ----------

It went through it all....... but storage is still 3.85gb, out of which there is 1.09gb available.....

what went wrong, I finally got it where I can copy & paste the commands quickly.

Fatal error: unknown target state. [/QUOTE] ?

lee

---------- Post added at 01:21 PM ---------- Previous post was at 01:06 PM ----------

?

lee[/QUOTE]

it reset everything on phone. What did I do wrong? Setting usb debug again, booting to recovery... try again. under mount settings it has check boxes for mounting different folders... choose them all? There has to be just one tiny thing I did wrong >>...?>

Any idea?

lee
[HTC One SV] -=GQ=-:
The last command should be

adb shell "cd /tmp&&chmod 755 *&&./swapper D_I_MOD"
[HTC One SV] coolbeans2016:
one last check

This is what it is up to now:

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb reboot-bootloader

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push swapper /tmp

578 KB/s (9235 bytes in 0.015s)

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb push abootimg /tmp

405 KB/s (25924 bytes in 0.062s)

c:\android-sdk\platform-tools\one_sv_swapper-0.6\Fastboot>adb shell "cd /tmp&&ch

mod 755 *&&./swapper D_I_MOD"

HTC One SV partition swapper by Alexander GQ Gerasiov.

Version: 0.6, target state: D_I_MOD.

Emmc partitions: recovery=21 boot=20 userdata=37 fat=38

Extracting boot...

Segmentation fault

Possible stock signed boot, stripping signature...

65535+0 records in

65535+0 records out

16776960 bytes (16.0MB) copied, 1.093088 seconds, 14.6MB/s

Segmentation fault

what should I change?

lee
[HTC One SV] -=GQ=-:
Great progress so far =)

Please, try version 0.7 (just check the download link in the 2nd post for it)
[HTC One SV] coolbeans2016:
0.7

this is with 0.7:

c:\android-sdk\platform-tools\one_sv_swapper>adb push abootimg /tmp

1852 KB/s (88796 bytes in 0.046s)

c:\android-sdk\platform-tools\one_sv_swapper>adb shell "cd /tmp&&chmod 755 *&&./

swapper D_I_MOD"

HTC One SV partition swapper by Alexander GQ Gerasiov.

Version: 0.7, target state: D_I_MOD.

Emmc partitions: recovery=21 boot=20 userdata=37 fat=38

Extracting boot...

/dev/block/mmcblk0p20: no Android Magic Value

/dev/block/mmcblk0p20: not a valid Android Boot Image.

Possible stock signed boot, stripping signature...

65535+0 records in

65535+0 records out

16776960 bytes (16.0MB) copied, 1.066687 seconds, 15.0MB/s

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Extracting boot:initrd...

1940 blocks

Extracting recovery...

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

Extracting recovery:initrd...

16641 blocks

Checking current state...

States: boot: STOCK, recovery: UNKNOWN, system: STOCK

Fatal error: Current state is unknown, nothing changed, aborting.

what do you think?

lee

---------- Post added at 04:14 PM ---------- Previous post was at 03:56 PM ----------

changed back to 0.6 and it just gives the Segmentation fault.

Could I have unpacked it in a wrong directory, or ?? it is a long directory

segmentation fault under a google search says something about protected os, should I disable MTP in twrp before mounting?
[HTC One SV] -=GQ=-:
Just give me the link to your recovery, so I can fix my script. And wait for next version from me.