Database Develop

Noob Question sorry (its about apps2sd)

Ok so I rooted and flashed the recovery image. Now I want to apply the MoDaCo Custom Hero ROM. Whats the easiest way to partition the SD card to allow apps2SD?
When I was in the recovery mode there were partition options can it from there or do I have to go on the desktop and use the cmd prompt?

Just use the partition option in recovery.​

Thank you for the quick response

hmmm apps2sd is not working. I got the Rom to work fine but before i flashed the rom I partitioned fat32+ext2+swap in the recovery screen so I can have apps2sd access and it does not work

Ok got the Apps2sd to work, but how can I see both partitions. I can't can only see the update.zip folder, footprints. and some other file but my music and photos are nowhere to be found and the Nanodroid back up. I did copy the nanodroid back up to my phone, but should it still be there on the main partition? Help please.

justin24 said:
Ok got the Apps2sd to work, but how can I see both partitions. I can't can only see the update.zip folder, footprints. and some other file but my music and photos are nowhere to be found and the Nanodroid back up. I did copy the nanodroid back up to my phone, but should it still be there on the main partition? Help please.
Click to expand...
Click to collapse
As should be obvious, partitioning the sdcard erased what was there.

2 things
1. Windows won't see that EXT3 Partition, it's not support by Microsoft.
2. The format to FAT SWAP EXT wipes the ENTIRE CARD, nandroid backups included.
I do an Nandroid anytime I go to mess with something in Shell or load a ZIP. Here in the past few days it seems like I do 2 or 3 a day lol.
More than likely you have a card larger than 2 gigs and the backups seem to be realativly small. I copy all of mine to a folder on my computer and Rename them with a small descript of the Rom build and Date. So I know what it is I can load back.

ROM - Deodexed with root, newest busybox, supports JAC kernel, no more lag fix

This has been updated to be deodexed+root+busybox only (though it still supports JAC kernel out of the box). At this point there are so many different lag fixes that it's hard to keep up with them all.
What it does have:
ROOT
No .odex files (deodexed)
Newest Busybox
ext manipulation files and libs, so it makes it easier to e2fsck or tune2fsck if you want ext4.
Also thanks to eugene373 for his work in establishing a baseline update.zip without which this would have taken a great deal more work.
Should work in clockwork, doesn't seem to need a wipe. If you have problems, use regular recovery, just rename it to "update.zip" on the root of your sdcard and it should flash just fine.
WARNING:
This should be completely safe. Nonetheless, should loss of job/loss of fertility/nuclear war ensue, I am not responsible.
Instructions:
1. Load the .zip file onto the root of your internal SD card (/sdcard)
2. Using Clockwork recovery, do "Install zip from SD card", then "Choose zip from sdcard", choose the VibrantDeodexed.zip, and choose "Yes"
2b.(ONLY If you don't have Clockwork) rename the download to "update.zip" and place it on the root of your sdcard. Then reboot into recovery and choose "Update packages".
3. (Optional) Flash JAC's kernel with ODIN using the directions specified HERE It is more stable and gets better benchmarks but there do seem to be some issues with the screen taking a while to wake up.
http://www.getyourboneon.com/VibrantDeodexed1_2.zip
NOTE: The first boot takes a long time because it has to dexopt stuff.

Version 1.0:
Just stock and rooted w/busybox
Version 1.1:
Uses the latest version of busybox and comes with support for JAC kernel out of the box (no need to flash the init.d update.zip and supersedes my method if his kernel is flashed.)
Version 1.2:
Updated busybox, added ext tools. Removed all lag fixes, though it will still work with the JAC kernels.
There are so many lag fixes out there at the moment that I didn't want to "lock in" people to a particular one.

Part of the high quadrant score is the 90 million triangles/sec. The data script boosts the data score.
Sent from my SGH-T959 using XDA App

what is the ext hack? and how does it make the phone faster?

the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
original link is here for the hack--http://forum.xda-developers.com/showthread.php?t=739647
anomalous, thanks for all your hard work...
so if we get a good deodexed rom, someone could compile JIT for our 2.1 right?

junkdruggler said:
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
Click to expand...
Click to collapse
why does the phone run faster with the data stored externaly? or is it because of the partition type?

im not quite sure, I would have figured our internal mem had a faster transfer rate than an sdcard, but Im on a class 2 and still getting better results... so it cant be a faster transfer rate...

@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.

Just so everyone Knows, the Format via the update script don't work, still trying to find the correct command for it....
But, in clockworkmod, just format the system / data / cache partition's before flashing.

designerfx said:
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Click to expand...
Click to collapse
Er, the internal storage is "rfs", samsung's proprietary fs. (And the read/write speed of fat32 tends to be a little faster than ext2, and TONS faster than ext3/4 - journals slow it down in exchange for stability after crashes)
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.

Disconn3ct said:
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Click to expand...
Click to collapse
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App

How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?

FastKatt said:
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll see what I can do to test it out this afternoon. (If you want to jump the gun, what I'm figuring is finding a static-linked arm version of bonnie++ or similar. Booting recovery, mount data or sdcard - not both - and test. Reboot recovery, test the other one. Maybe test dbdata and external sd as well, but the interesting numbers will be the first two - onboard-with-rfs and onboard-with-vfat..)

ivanmmj said:
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
Click to expand...
Click to collapse
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.

anomalous3 said:
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
Click to expand...
Click to collapse
Which ROM kitchen? I used my own script. Does the ROM boot up and run doing it that way? Should be interesting to play with.

Hmm, got the update script working almost perfect, but now it causes crashes. Seems to be missing dbus.conf.

OP updated - it works.

I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.

theMAGNUM said:
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?

ArbitrageMan said:
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
Click to expand...
Click to collapse
No adb shell doesn't find my device

ext & froyobylazo

Hello
I try froyo by lazo rom on my g1 and for me it's one id the best i try ( lite and fast )
But i got a problem with the ext partition, it does'nt apear in internal storage.if i select alowed application move to sd ext it work, but after reboot all the application desapear...
I got an ext4 partition and a swap one done thrue RA
Is this rom need a special ext?

You might have better luck asking in the development thread.

I know but i'm not able (junior member )

thi3um said:
Hello
I try froyo by lazo rom on my g1 and for me it's one id the best i try ( lite and fast )
But i got a problem with the ext partition, it does'nt apear in internal storage.if i select alowed application move to sd ext it work, but after reboot all the application desapear...
I got an ext4 partition and a swap one done thrue RA
Is this rom need a special ext?
Click to expand...
Click to collapse
if i select alowed application move to sd ext it work, but after reboot all the application desapear...
once you choose app2ext,you should reboot your phone,then install the apps.
otherwise they will desapear

Ok. I'm actually on this ROM now, and have been for a couple weeks. Despite the fact that the thread says to NOT use Firerat's ALL in ONE patch, you need to. The options you want to use are 2, 4, and 10 ONLY! Nothing else. This will force apps2ext to work on this phone/ROM combo. I thought all of this was fixed in version 5 of the ROM, but not sure. Any questions, the email is in my info to the left.
<<<<<<<<<<<<<<<<<

just flashed mine to the version 5.1 from previously ezGingerbread.
So far I can say the install on sd-ext functioned. Just set it to sd-ext and reboot.
Btw I don't install any AIO from Firerat as it is not advised to do so

Ok for me i partitioned again my sd using gparted and now everything work. I think the problem come from RA partitioning.
Sent from my Legend using XDA App

creezalird said:
just flashed mine to the version 5.1 from previously ezGingerbread.
So far I can say the install on sd-ext functioned. Just set it to sd-ext and reboot.
Btw I don't install any AIO from Firerat as it is not advised to do so
Click to expand...
Click to collapse
Take it from not only Tribal but from myself who are two very experienced members, if you don't want your data partition to be eaten up rather quickly then run the AIO patch options 2, 4 & 10 when you flash the rom, tried and fully tested working.

shadowch31 said:
Take it from not only Tribal but from myself who are two very experienced members, if you don't want your data partition to be eaten up rather quickly then run the AIO patch options 2, 4 & 10 when you flash the rom, tried and fully tested working.
Click to expand...
Click to collapse
hurmm, could u please elaborate a little bit as i can't really see why my data partition will be filled up quickly.
As for now, every apps that I've installed, just go nicely into the sd-ext partition. (actually I've already read the comment about AIO patch in FroyoByLazslo thread, but just couldn't make my mind) .
And if it is really needed, should I reflashed everything back or I can just run the AIO? Thank you in advance
Update : I've tried the script AIO but got an error saying that MT3G dalvik-cache didn't need to be bind. It is normal ?

creezalird said:
hurmm, could u please elaborate a little bit as i can't really see why my data partition will be filled up quickly.
As for now, every apps that I've installed, just go nicely into the sd-ext partition. (actually I've already read the comment about AIO patch in FroyoByLazslo thread, but just couldn't make my mind) .
And if it is really needed, should I reflashed everything back or I can just run the AIO? Thank you in advance
Update : I've tried the script AIO but got an error saying that MT3G dalvik-cache didn't need to be bind. It is normal ?
Click to expand...
Click to collapse
i would like to know this too..

You can just run the patch. No need to re-install everything.
Basically, the patch forces your ext partition to mount. Options 2 and 4 kind of work hand in hand with each other, while option 10 is a dalvik cache bind point. If you get an error with option 10, disregard.
In forcing the mount of ext, this ensures that future apps continue to properly install on the ext partition. they will still have a bind point, so don't fret. This is MUCH better than the ext option "possibly" messing up and your precious internal storage gets eaten away. While this has probably been fixed by now, since they are now in version 5.2 at the time of this post, I take no chances. LOL..

edit: do i flash these in fastboot?

northleaf65 said:
edit: do i flash these in fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=679572
Read the OP for instructions.

thnx, ill read up

[Guide]How 2 Create EXT3 for the Salsa only! * Increased Internal Memory*

Ok seems many usrs here have the same problems over and over again. so heres a tut!
This will probably cover many other topics but simplified here as much as i can.
You Must have the following to get this to work:
ROOT
Recovery 5.0.2.6
busybox installed.
if you have non of these...do not attempt any of this thread till you have!
To start with.
Creation of EXT3 Partitions.
you will need Minitool Partition Wizard. Mini Tool Partition Wizard Download
This is a harddrive/diskspace program allowing accurate modification of disk space.
Never create an EXT3 in CWM, as this will create whats known as a swap drive.
this causes the bootloop. Hence the non boot!
EXT3 has to be set as primary drive not logical.
Size allowance recommendations (personal choice, but this is after a few findings and results given by Salsa users)
SD Card Size.................................EXT3 Size
2GB......(Class 2).............................250MB
4GB......(Class 2-4)..........................500MB
8GB......(Class4-6)...........................500MB-1GB
16GB....(Class8-10).........................1.2GB​
WARNING, anything over 1.5GB will result in serious problems and SD damage
This also works around class types of SD Card. the higher the class the faster it works, there are various brands offering different class cards, find a fast and big card for best performance. I currently use Class 8 16GB with 1GB Ext3 with little/no lag
Wise idea before this to make an SD backup, if done correctly your data will not be affected...if you screwed up...you'll loose everything...so back it up!
To start with,
Remove Sd Card and use and SD Reader and insert into your computer USB Slot.
Open Minitool Partition Wizard.
Resize your sd card accordingly leaving 1.2-1.5gb of unallocated space. Apply the actions.
Now you have the unallocated space, reformat the space in EXT3 and set as Primary drive. Apply Actions.
Now normally the Application throws your sd out and says bad drive......this is sometimes normal so don't panic.
Reinsert your Sd in Phone and boot into recovery only
Data2sd script
theres 2 scripts available for these roms.
htc-data2sd-ext3 or data2whatever by m1ndh8x4r.
2.1 Roms work well with htc-data2sd-ext3 script with no problems.
data2whatever works really well with 3.5 sense Roms (Bens/M1nds)
*****There is a warning with this data2whatever script....When using this script, you will notice after a short period, that you cannot update or install any more apks. This is due to a Dalvik error within the script on Deodexed roms, currently it cannot be fixed, you have been warned*****​
these can be used easily but the following rules must be applied.
You must flash the rom firstly by the 3 wipes...regardless!
flash the rom as normal and reboot full, letting the rom fully build it self and load up... ie input your details/sign in wifi etc.
check it out for a few mins while your waiting...hey even make a backup lol!
OK now reboot in recovery and flash the chosen script....DO NOT WIPE ANYTHING!
once flashed reboot normally.
it will boot, it may take up to 5-10mins but it will boot. if by any chance you a boot loop at the boot animation screen then you have an EXT3 fault and you must redo the EXT3 Partition in Minitool to proceed again.
data2sd scripts are here>
http://www.mediafire.com/download.php?duigp9ky9796b65 for htc-data2sd-ext3.zip
http://www.mediafire.com/download.php?m7bv6pk024p63ef for d2extv0.43.zip (New/Advanced)
http://www.mediafire.com/download.php?qr5rh2fho1hnbnl for data2whatever
This is a proven way and so many have tried and failed other ways.
Please try this guide. If you get stuck please just ask!
Please Answer my poll at the top and Thank this post...Ty!
If you Answer NO to this guide, please post below and tell me why so i may help further

Heyy it worked thanks man

BigBearEvo said:
Open Minitool Partition Wizard.
Resize your sd card accordingly leaving 1.2-1.5gb of unallocated space. Apply the actions.
Now you have the unallocated space, reformat the space in EXT3 and set as Primary drive.
Click to expand...
Click to collapse
Trying to do this with fdisk on linux
It works but runs slowly for some reason
I have a 2GB cards, first partition is about 1.4 for normal /sdcard the remaining .4GB for /data
Both partitions are start aligned on 2048 sectors

Issue - applications get corrupted after restart
I am facing strange issue. I did everything described above and have /data on sd. But everytime I reboot something happens to most apps. They are installed but when I try to launch any of them I got errors and application closes. I need to reinstall EVERY app and they work until next reboot. Any ideas about the cause or what to check ? At this point I am trying not to discharge or reboot my phone by it;s impossible to keep it that way.

procek said:
I am facing strange issue. I did everything described above and have /data on sd. But everytime I reboot something happens to most apps. They are installed but when I try to launch any of them I got errors and application closes. I need to reinstall EVERY app and they work until next reboot. Any ideas about the cause or what to check ? At this point I am trying not to discharge or reboot my phone by it;s impossible to keep it that way.
Click to expand...
Click to collapse
thats a rom issue.
What rom are you running?
Are you using a Data2sd script? if so which one?
Are you using links2sd?

BigBearEvo said:
thats a rom issue.
What rom are you running?
Are you using a Data2sd script? if so which one?
Are you using links2sd?
Click to expand...
Click to collapse
I am running standard HTC ROM 1.12.401.2 With Sense 2.1.
I used ext3 version of script.
No. Shall I ?

procek said:
I am running standard HTC ROM 1.12.401.2 With Sense 2.1.
I used ext3 version of script.
No. Shall I ?
Click to expand...
Click to collapse
no dont lol...ok sounds a bit stupid but have u got root? because what your describing is and apps2sd thing...which u cant get on stock rom....but if u dont have full root....then this sort of thing does happen....or...you got a faulty ext3 partition...
questions next...
which guide did u make ext3?
size and did u make swap?
root?
Need file name of the data2sd script u used and how u used it...(this is important)
so i need full break down....assuming u have root that is....this almost sounds like a silly problem, but then most of us don't use stock roms anymore....so we dont have this problem lol

BigBearEvo said:
no dont lol...ok sounds a bit stupid but have u got root? because what your describing is and apps2sd thing...which u cant get on stock rom....but if u dont have full root....then this sort of thing does happen....or...you got a faulty ext3 partition...
questions next...
which guide did u make ext3?
size and did u make swap?
root?
Need file name of the data2sd script u used and how u used it...(this is important)
so i need full break down....assuming u have root that is....this almost sounds like a silly problem, but then most of us don't use stock roms anymore....so we dont have this problem lol
Click to expand...
Click to collapse
Of course I have a root - it works perfectly. I created the partition according to above instructions (I mean this thread). My ext3 partition is about 800 MB and 3200 MB is for FAT32. I did not create swap - just fat32 and ext3 with Partition Wizard. I used htc-data2sd-ext3.zip in I think normal way - phone reset, installing busybox, reboot, installing script with recovery - done. Everything is perfect until next reboot.

procek said:
Of course I have a root - it works perfectly. I created the partition according to above instructions (I mean this thread). My ext3 partition is about 800 MB and 3200 MB is for FAT32. I did not create swap - just fat32 and ext3 with Partition Wizard. I used htc-data2sd-ext3.zip in I think normal way - phone reset, installing busybox, reboot, installing script with recovery - done. Everything is perfect until next reboot.
Click to expand...
Click to collapse
sounds like a problem with your rom my friend....hard to tell without seeing it really...
have you thought about changing the rom itself?

BigBearEvo said:
sounds like a problem with your rom my friend....hard to tell without seeing it really...
have you thought about changing the rom itself?
Click to expand...
Click to collapse
To this moment no. But if there's no other option I will probably have to...

procek said:
To this moment no. But if there's no other option I will probably have to...
Click to expand...
Click to collapse
either that or find your ruu and reinstall stock again!

Funny thing
I used my previous card (smaller - just 2 GB) and there's no such behaviour as with my 4GB. Smaller one is Sandisk, bigger one is Kingstone - both known for good products. So switching ROM is rather not an option. There's something about SD but I can not figure out what...

Pls help
I have created 6gb of fat32 and copied ROM and data2sd-ext3.zip then formatted remaining 1gb space in ext3. When I tried to install zip from recovery mode it throws "E: can't mount /sdcard/"
pls help
Thx

yuva0103 said:
I have created 6gb of fat32 and copied ROM and data2sd-ext3.zip then formatted remaining 1gb space in ext3. When I tried to install zip from recovery mode it throws "E: can't mount /sdcard/"
pls help
Thx
Click to expand...
Click to collapse
how did you make the partitions? and are they set as primary?
what class sd card is it? you need a class 8 or 10 on that size.

I used mini tool for partition. I set fat32 as logical and ext3 as primary. I have 8gb class 10 SD.
Sent from my HTC Salsa C510e using XDA

Shrink the ext3 to 750mb and set all partitions as primary.
BigBear is using Xparent Tapatalk Purple

Yep now I can see my data in SD card. Another problem I triple wiped and flash arc rom again, and given detail/sign in. When trying to flash script in recovery mode, it asks for busybox in some sys folder. I don't have busybox and also script installed, but ext3 memory not reflects in as main memory. Am I used different script or I need to install busybox, if so how to do that.?

I installed busybox @ system/xbin and flashed script, it worked. Finally my internal memory problem solved:thumbup:
I request to add installing busybox step and download link for script in tutorial.
Thx bb
Sent from my HTC Salsa C510e using XDA

I used data2sd without without any problem for past two days, suddenly today some apps force closing. Instagram app show error msg like"unfortunately this device's filesystem is reporting a problem." and pointing to this url "bit.ly/igfilesystem".
pls help.
I'm using arc V2 ROM, class 10 8gb sd, with 750mb of ext3.

yuva0103 said:
I used data2sd without without any problem for past two days, suddenly today some apps force closing. Instagram app show error msg like"unfortunately this device's filesystem is reporting a problem." and pointing to this url "bit.ly/igfilesystem".
pls help.
I'm using arc V2 ROM, class 10 8gb sd, with 750mb of ext3.
Click to expand...
Click to collapse
contact instagram with a logcat or report for them to check

[Q]Supersu issue, re-rooting and other questions

Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1

Okkvltist said:
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Click to expand...
Click to collapse
Hello and welcome to xda,
Where exactly did you get the back-up from that you used to restore?
You were close it is TWRP or Team Win Recovery Project.
I believe the reason you can't install SuperSU is because you don't have a write protect removed kernel installed. You can find one here. Check out their related forums and see which one you like best. They are pretty much all great. Some aren't being supported anymore as a heads up. To flash a kernel, in case you didn't know how:
Go into Settings-About-Software information-More-Kernel version and write down the name of the Kernel
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button, until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your fastboot.exe from Android Studio or wherever you obtained it from (Mine is in C:\Users\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like:
Code:
HT42PXU89475 fastboot
if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Make sure your recovery.img or whatever the name of the recovery is, is in the folder you are currently in
11. Type
Code:
fastboot flash boot boot.img
in the command window
You should see something like:
Code:
C:\Users\yourusername\Android\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (12932 KB)...
OKAY [ 1.350s]
writing 'boot'...
OKAY [ 1.030s]
finished. total time: 2.385s
Your phone will still be in FASTBOOT USB mode
To test it out to see it was correctly flashed, reboot the phone
Go into Settings-About-Software information-More-Kernel version and see that the version changed
You can follow my little guide to use SD as Internal memory. Let me know if you need any help.

I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.

Okkvltist said:
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Click to expand...
Click to collapse
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.

blaqueknight said:
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
Click to expand...
Click to collapse
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
Click to expand...
Click to collapse
I'm sorry, please disregard that last comment. I was posting like your only problem was the Play Store. lol Sorry. But yea, check out those things I mentioned to you and you should be able to get SuperSU back up, if not I'll help you with anything else.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Click to expand...
Click to collapse
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"

Okkvltist said:
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Click to expand...
Click to collapse
Are you using Aparted? What was the method you used to partition? You should partition as ext4.

Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?

Okkvltist said:
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Click to expand...
Click to collapse
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.

blaqueknight said:
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
Click to expand...
Click to collapse
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2

Okkvltist said:
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Click to expand...
Click to collapse
Are you trying to partition the whole SDcard as ext4? To properly partition the card to be used with Link2SD you have to:
1. Delete the sdcard
2. Create a FAT32 partition of any size of your choosing
3. Format the FAT32 partition
4. Create an ext4 partition of any size of your choosing
5. Format the ext4 partition (this will take a long time, as it will create journals that are used to recover from an error such as removing the device while files are being copied)
After following those steps, Link2SD should properly create the script/mount and you should be able to link to your sdcard
If you are doing those steps perfectly and you still have an error, we have to find out another solution

Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.

Okkvltist said:
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Click to expand...
Click to collapse
I just made a couple of very simple tutorials to use Aparted and Link2SD and they are both working for me. Check them out: Aparted tutorial, Link2SD tutorial. I believe the ext2 that you are talking about is around the 10 second mark in the Link2SD video. Do you mean the /data/sdext2? That is just the name of the second sdcard partition.
If you can, you should buy the full copy of Link2SD to link external data and whatever other options become available.
The class of sdcard shouldn't have anything to do with the partition. That's just a classification of the speed of the card.
If needed, I'll make more videos to show exactly how everything is done. I think sometimes it is better to show than simply explain how something is done.
Hope this helps.

Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much

Okkvltist said:
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Click to expand...
Click to collapse
I'm happy it worked out good for you.
Yes, you are able to remove your sdcard. Be aware that your apps are on your sdcard so if you remove it, you remove them. They are placed on your sdcard and symlinked so Android thinks they are still on your phone in the place they would normally be. Nothing should crash, they just shouldn't show up. There is some great info about Link2SD here.

@blaqueknight..
nice videos man.