Develop Bugs

[JAN 25][ROM-ZIP]Stock Desire HD on EU HD2 [A2SD+][CWM][RMNET/PPP][Kernel:MDJ,Gauner]

Hi all,
This is not squashed ROM for EU HD2 which contains all files from the stock RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed. Yes of course some executables(akmd, reboot, vold), some libraries, some config files and kernel were replaced for Leo. The reason of why I do this is my wish to have Desire HD ROM on my EU HD2 which is closest to stock.
The ROM size is about 407M. I do not like squashed ROMs. We all have sdcards and I do not see any sense to make squashed ROM. Therefore this build uses the second partition of sdcard to store dalvik cache, data, system apps, framework. So size of this rom in NAND is 391Mb, and in sdcard is 16Mb. I recommend you to use 1024MB second partition, but not less.
My CWM installation script mounts the second partition of sdcard to /data, creates sysfiles directory and copies /system/etc/clockwidget, and /system/etc/slideshow and /system/etc/soundimage to this second partition into /data/sysfiles directory. After that the script creates symbolic links to these three directories in /system/etc direcory, and copies all other files of ROM to system partition in NAND. So we have 391Mb of files in NAND, and 16Mb of files in the second partition of sdcard.
The kernel mounts the second partition of sdcard to /data before the init.rc script will be run. Therefore android use this partition as internal storage, and we see free space of this partition as free phone storage in info.
The content:
- Full stock Desire HD RUU 1.72.405.3
- Last Gauner's kernel.
- Fixed mms.
- Fixed WiFi MAC.
- Fixed su.
- Fixed sql lib.
- Fixed first and external partition mounting.
- Percent battery.
- Rmnet is ON by default, if you would like to enable ppp you should create ppp file in /system directory and reboot your phone. To create the ppp file you should connect your phone to PC and run this command in a terminal:
adb shell touch /system/ppp
You should delete this file and reboot your phone if you would like to enable rmnet again:
adb shell rm -f /system/ppp
Not worked:
- 720p recording
- bluetooth MAC
Removed apps:
- Ereader. Use the attached archive if you would like to use ereader. Install it by CWM.
Link to ereader
"How to install" is in the readme file of the build. Please, read it! This ROM is only flashable using ClockworkMod. CWM v 1.2 is included into archive of this build. Note, system partition in NAND should be 399Mb.
CWM v 1.2 fix:
If you would like to use CWM backup and restore you should replace CWM initrd.gz file on this file. I fixed CWM to soppurting partition layout without userdata partition..
Update the previous version ROM:
If you would like to update the previous version you should not touch your sdcard. You should do this only: format NAND by task29, install magldr, flash new CWM partition layout, install new ROM.
Recommendations:
- I recommend to format NAND by task29 before install this ROM. After formatting will be done you should install magldr again. All tools are included into the archive.
- I recommend to calibrate G-Sensor. To do it go to Seetings->Display->G_Sensor calibration->, place your phone FACE-DOWN on level surface, press Calibrate button. After calibration will be finished press Ok button.
- If you would like to use the "backup second partition" feature in CWM, the second partition should be labeled as sd-ext.
- Sometimes magldr does copying of data with errors(lost data) in the "USB MassStg" mode, but you do not see these errors. Next you can see that the ROM installation was finished shortly. If it happens you should look into CWM log and you will see some errors of files extraction from archive. If you will copy this archive to sdcard again, but only by CWM or by other cardreader, you will not see these errors in CWM log. Therefore I recommend you to copy ROM zip to sdcard by CWM or by other cardreader.
- To get a CWM log you should do this:
a) Install the ROM
b) After the installation will be completed you should not reboot your phone! Go to "advanced" item of CWM menu.
c) Next select "Report Error" item. CWM will create the clockworkmod directory in root of sdcard.
d) Next copy the recovery.log file from the clockworkmod directory and attach this file to the thread. I will check it.
- The first loading(from the phone rebooting moment to appearance of the language choice screen) is long. Be patient, please.
- Please, setup only that you really need during the first boot. Desire ROM is syncing and configuring a lot of stuff during first boot if you have entered your google account. I recommend to setup all needed accounts after initial setup. And, please, let system sync and configure all stuff, next reboot your phone. After this work will be completed the ROM will be fast. I recommend:
a) disable the sync of accounts which are no needed for you, or change "Update schedule" of these accounts.
b) disable the "Back up my setting" for google account if it is no needed for you.
c) disable Automatic brightness and set Brightness to min value.
- Note, please, you can use CifsManager to mount cifs(samba(ms windows))/nfs network resources to your phone. This tool is available in the Market. It allows you to play music or watch movies from any shared resources which are available in your local network without copying this content to your phone. To use it your phone should be connected to local network by WiFi.
Currently I have 2Gb ext4 second partition on my Transcend 6-class sdcard. I can tell the system works properly and fast:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Performance:
Please, look at my video if you would like to see the performance of this ROM.
Download:
EFP v.2 HD2 Desire HD stock (last Gauner's kernel)
Kernels: (only if you would like to replace a kernel of your already installed ROM to other kernel)
Gauner's kernel with ext4
MDJ's 10.3 kernel
MDJ's 10.4OC kernel
Updates:
Desire HD stock toolbar
Desire HD custom toolbar with percent battery
How to install kernels, updates or fixs:
1. You should have already ClockworkMod(zImage and initrd.gz) on sdcard. If you use ROM-ZIP builds I think you have it already.
2. Copy the update.zip file from an update or a fixs archive to sdcard root.
3. Reboot your phone, hold Power button to access the magldr menu.
4. Next select the "Boot AD SD" item. ClockworkMod will be loaded and you will see ClockworkMod Recovery menu.
5. Select the "apply update from sdcard" item.
6. Select "Yes".
7. After flashing will be done select the "reboot system now" item.

what working and not working ???

It would be nice to have the readme of each build at least posted in the first post, so we don't have to download everything to see if we need it
I am always looking for a PURE/Stock Desire HD build, with no frils and no EXTRA apps, for a TMOUS HD2. But with no readme , i'll wait for someone first.
Greetings Santroph

Did it Include CM Mod setting?

Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.

is this ext 2 ,ext 3 ,ext 4 same?

santroph said:
Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.
Click to expand...
Click to collapse
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.

sathara said:
is this ext 2 ,ext 3 ,ext 4 same?
Click to expand...
Click to collapse
check www.google.com

AngelDeath said:
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.
Click to expand...
Click to collapse
same here.. I also find CWM yest..

does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone

wtf? i can`t choose CWMREC directory...

i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm

hamdir said:
i dont get it its based on andrews work, so is it a2sd+ or data2sd?
Click to expand...
Click to collapse
a2sd+ as per the title

swordfish2009 said:
a2sd+ as per the title
Click to expand...
Click to collapse
the title says its based on andrews rom and the screen shots shows data2sd (768MB free)
so yea although i know the title says a2sd+ i need confirmation

What working?
What working and what not?
mms, volume, hd video???????

after i unlock phone its stuck at the htc logo
i have ext2 partition already
and i flashed the required partition size!

zheliapov said:
wtf? i can`t choose CWMREC directory...
Click to expand...
Click to collapse
From the "How to instal" in readme file:
...Copy the CwMRec directory from the 2_step directory to root of sdcard.
After copying will be finished disconnect USB cable.
Go to "Services->BootSettings->AD SD Dir" in the magldr menu and select the CWMREC directory....
1. Perhaps you forgot to disconnect a USB cable safely.
2. You copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory. In this case the CwMRec directory not exists on sdcard, the zImage and initrd.gz files are placed in root of sdcard. You should skip the step of selecting directory for boot from SD or select the <.> .
hamdir said:
i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm
Click to expand...
Click to collapse
This is a2sd+.
In case of A2SD the internal storage does not include external partition, you will see only size of free space in NAND. But in case A2SD+ you will see free space of the external partition as size of intrenal storage.

rejdzu said:
does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone
Click to expand...
Click to collapse
I am using Gauner's kernel build currently and I do not have any issues with root.

something is awfully wrong
the gauner version keeps giving me a bootloop

I think you forgot to disconnect a USB cable safely. Or you copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory.
Click to expand...
Click to collapse
Not working... Any ideas?

[Q] How to intal MIUI on the Incredible?

After a solid 2 days of searching XDA forums and around the internet in general, I give up on searching around and want to know if there is a straightforward way to install the MIUI ROM that I have already downloaded. I have the ROM already on an SD card, and I figured I am just supposed to restart the phone and some kind of .bat file will automatically start running and itself the rom onto the phone. Well, that didn't happen.
How do I get this ROM installed?

use rom manager. find it in the market place

cn0421 said:
use rom manager. find it in the market place
Click to expand...
Click to collapse
no? use hboot, and cwm 3.x wipe data/factory reset wipe cache, wipe dalvic,
install from zip.
If that doesnt make sense its time to read more about modding/flashing
additionally rom manager app is trash for flashing, only useful to create nandroid backups.

Some people prefer ROM Manager, I'm not sure what type of MIUI releases are avaiable through there, you might need to purchase premium which is a total pain.
It is overall just better with flash it through hboot and cwm3. Also... andorid/linux do not read .bat files, that's specific to window's OS.
Basically (I'm simplifying this, plus there's 500,000+ other posts saying the same info)
1) Root your phone
2) Install CM3 or if you rooted with unrevoked3 then it automatically installs it.
3) Download ROM of choice
4) Put that ROM on the root of your SD card
5) Boot into hboot (turn off phone, then hold down the 'volume down' and 'power on' your phone.
6) Choose install .zip from location, navigate to SD card and install
7) done

POQbum said:
Some people prefer ROM Manager, I'm not sure what type of MIUI releases are avaiable through there, you might need to purchase premium which is a total pain.
It is overall just better with flash it through hboot and cwm3. Also... andorid/linux do not read .bat files, that's specific to window's OS.
Basically (I'm simplifying this, plus there's 500,000+ other posts saying the same info)
1) Root your phone
2) Install CM3 or if you rooted with unrevoked3 then it automatically installs it.
3) Download ROM of choice
4) Put that ROM on the root of your SD card
5) Boot into hboot (turn off phone, then hold down the 'volume down' and 'power on' your phone.
6) Choose install .zip from location, navigate to SD card and install
7) done
Click to expand...
Click to collapse
I may be wrong because I have an EVO but between 5 and 6 you need a step that says to choose recovery. On my phone you can't flash roms through hboot.

cvbcbcmv said:
yesterday I flashed MIUI. I was doing it the traditional way, the way I always do. But when I tried to flash it in recovery, it just started to flash and stopped. I figured I'd do it in rom manager, it had the newest version, I told it to wipe data and cache, and I'm now running MIUI. It's great. Similar to iOS, but very much android. Netflix works, and battery life is ****ing incredible.
Click to expand...
Click to collapse
+100000000000000 to that, battery life is fuking incredible

battery life is the main reason i'm not going back to CM7. it's almost twice as good, and with the same features, if not better...

Cannot view SD EXT

Hi
I have rooted my phone with unrevoked, s-off'ed with alpha rev 1.8, partitioned 1gb of my 4 gb card to ext 3 and installed Gingerbread F1 V3 Ap2SD ENG.
On first load of the rom i can see that my SD card FAT 32 storage has been reduced but the only other memory internal memory which was at 147mb when i first booted the rom.
All apps are installing to the internal memory by default with only the option of moving to the SD FAT 32 partition. and there is no option to move to the sd ext3 part as there is no option - so I have lost 1gb off my sd card.
What have i done wrong?
on a 2nd note i appear to have a call delay when answering the phone my radio version is 32.49.00.32U_5.11.05.27 - do i need to update this ? will it solve the problem ? my carrier is vodafone UK.
appreciate the help

ararararar... Sorry had to do something.
This has been explained SO many times by me included. The way a2sd works is by symlinking the folder containing the apps(/data/app) to you ext-partition.
You cannot see this partition listed in the system info, as the partition is not supposed to be there. The system have no way of knowing that you are using an ext-partition, as it just installs apps to /data/app, however as it's symlinked to ext, they are actually being placed in sd-ext/app.
This means that you will only see you internal memory, but it still works. Your apps will just take up less space on internal, as the apk file is placed on the ext-partition. They will still take up some space for data and dalvik cache.
edit: bonus info. Install "quick system info" or "titanium backup" from the market to see the size of your ext-partition in those apps.
edit2: and if i did not make my self clear. The partition-size info in the system settings is not supposed to be a partition manager. It's written to be userfriendly, and it only provides the regular user with the partitions they should care about(/data and /sd-card). If you want a detailed view of all your partition(and there is more than a few) go get root explorer. It'll let you play around with all the partitions mounted.(you won't have access to recovery, bootloader and so on from here)

Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App

Well i take it that your cache partition is too small(this is why people using alpharev cm hboot cannot use recovery for this). In that case you have already flashed another hboot(using "fastboot flash hboot hboot.img") if you haven't done this, you cache-partition should not be too small, and the recovery method should be able to do this just fine. If you have done this, use the same command to flash the radio eg "fastboot flash radio radio.img"
Either way it is very unlikely to fix your call delay(read: it won't fix your problem, as it's got nothing to do with the radio). It's a problem caused by some incompatibility between the htc libs and GB. It's quite common on GB roms apparently. Wait for HTC to release the real GB update, and we might very well be able to solve this problem.

dazzr123 said:
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Install android sdk:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Copy the downloaded radio.img to e.g. partition C: on your computer (if you downloaded a zip, extract the radio.img from there). Check the md5sum!!!
Boot your into fastboot mode (start it with pressed back and power button) and connect your phone to your computer.
Now open command prompt on your computer and type
Code:
fastboot devices
It should list your device now. If it does, type
Code:
fastboot flash radio C:\radio.img
(in case your radio.img was copied to C: ).
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Click to expand...
Click to collapse
A nice guide about adb/fastboot can you find here:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
Flashing radio is a risky thing. Because if there something is wrong, your phone won't be more than a paperweight.

[Q] ICS for Desire [Sandvold]

Hi,
First i will say thanks for the great rom, i will try it asap (a little bit more stable)
i read about this rom in the topic since it was started .
i have some Questions, it will be my first "clean" Android (without Sense)
There should be a installer after first start of the rom after flash? Where can i found more information about the things i can chose?
Evervolv toolbox, is that an addtional Settings Dialog with more Options or still a app which can be used as "standalone"
(sorry for the bad english)

When you install it you will get some options to choose a launcher and a2sd-script.
On first start you won't get the app to set your g-acc and so on, you'll have to do that in the system settings.
And the Evervolv-Toolbox are additional settings the this rom it's not a standalone app.
Hope this helps
grtz

Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig

stig_dk said:
Please note that Sandvold ICS v. 0.4.2.1 has some stability problems at the moment. Many people experience "black screen of death", device fails to turn on screen after a period of inactivity, battery has to be removed to reboot. I found that raising the minimum CPU speed from 245mhz to 384mhz completely removes this problem. With this small tweak the rom is great! You *should* be able to change this setting with Evervolv toolbox, sadly it does not work. For some reason the toolbox runs with insufficient rights to tweak cpu speed, I did my own scripts to set cpu speed from the console instead.
cheers
/Stig
Click to expand...
Click to collapse
Black-screen-issues can be solved by flashing MIUI-kernel:
http://www.miui-au.com/wp-content/plugins/download-monitor/download.php?id=166

Hi! I use ICS since beta 0.3.9 and I'm now updated to 0.4.4
This release seem very stable now. Just remember that the camera preview doesn't work. Also, you might have some problem with MMS.

App space problem
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?

Looloup said:
Hello - some help for a newbie please (well Desire newbie)...
I did try reading though Sandvolds thread, and I have tried to remedy, but I don't seem to get much further ....
I am running an ICS beta on my tablet, so I thought it would be interesting to try it on my Desire too. On the tablet there is more memory, so I have never experienced space problems with apps.
I rooted the Desire OK - and flashed 0.4.2.1 ... ran fairly smoothly, but hit space problems when trying to load up some of my favourite apps. I have a 16gb sd card. I downloaded apps2sd from the market - and moved some of the apps. However still not able to update some system apps from the market due to insufficient space (even though there appears to be enough).
Reading the other thread, I have gathered some/little understanding... and so before flashing 0.4.4 I reformatted my SD card from recovery choosing the largest ext4 that I could.
I was then ready to go to try 0.4.4.
On trying the Amarullz script and Nova launcher - I was having lots of lag after boot and I kept getting prompted to enter PIN number and reboot the phone. (I had done a factory wipe and cleared Dalvik after flashing the ROM).
I then reflashed choose Apex launcher, stock Kernal and data2sd option.
I wiped after flashing, did a few waits and reboots - as others recommended this.
Now seems to run quite smoothly, I have added back a bunch of apps via Titanium Backup ... but I don't see any apps 'automatically' being moved to sd card. I have moved as many as I can manually.
But I can also see that I am going to run out of space again soon ....
If I look in the settings at storage I see...
Internal storage - Apps 104MB Available 26.86MB
SD Card - Apps 239MB
Am I doing anything wrong?
Click to expand...
Click to collapse
1). www.revolutionary.io use this
2). www.alpharev.com download cm7r2.img
3). flash the hboot
Code:
fastboot flash hboot hboot.img
4). re-flash 4.4 and choose stock a2sd
5. enable a2sd
Code:
su
a2sd install
#choose settings#

Thanks for quick response..... I have a fee more questions....
I originally rooted my Desire via revolutionary .... do I need to do it again?
I guess I then flash the zip file.
The fastboot command - can I do this from the terminal app?

hi,
fastboot command and adb must be running from computer.
you need to instal sdk android sdk android
if you run revolutionary, u don t need to do once again but to flash an hboot you must be Soffed.
dunno if revolutionary does the job... i used alpharev to do son gain S-offed and able to flash hboot from fastboot command.

I saw the option to install agps in the installer but i chose gps. How can i add the agps when i already installed the rom? Because getting gps fix in navigation is taking way to long, so long that i abort it while trying

Getting closer
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.

where have my apps gone?
So I can't get cm7r2 to work, so I reflashed hboot back to standard, I then reflashed 0.4.4 choosing stock a2sd. I installed a2sd via terminal and moved cache too. After reboot I installed a bunch of apps .... and eventually ran out of space - as if apps not being moved.
I then rebooted, and all of the apps except the paid apps have gone. I installed a couple of apps from the. Market and they have also gone after reboot.
I turned a2sd off, then I was able to keep apps over a reboot ..... but I would like to get a2sd working.
Any ideas?
For now I am manually moving apps to SD card.

Sorry for this question...
Your 3G, Wifi is working.. My wifi, 3G is not working..

3g (once APN set up) and wifi both working well

Looloup said:
@bortak
1. Done OK
2. Done OK
3. Done OK
4. Done ... BUT ... no Gapps, no Terminal app ... not much really not even a keyboard (even after 2 reboots)
- The link to Gapps for CM7r2 no longer works
5. Unable to try this as no Terminal app ... and I can't get ADB working on my PC.
Click to expand...
Click to collapse
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.

muellersmattes said:
Did you do a wipe after flashing the rom? I had a similar problem when doing that. CWM Recovery also deletes the sd-ext partition, and as on cm7r2 there are also system apps on sd-ext, they are gone.
With the included a2sd apps should be moved to sd-ext automatically. It is not shown on the phone.
How big is your ext4 partition? And did you create it with CWM Recovery? If so, try recreating with gPartEd.
Click to expand...
Click to collapse
This.
10chars

I created the extra partition via CWM recovery - maybe too large as I made it 4gb.
I wiped the device and Dalvik cache after flashing the ROM.
I then set a2sd via terminal and allowed reboot.
I then downloaded apps (or restored via Titanium)
Eventually ran out of space when downloading apps - so they were not being moved.
Apps run OK.
When I did a normal reboot - the apps 'disappeared '.
Reading Bortaks debug guide the only thing I can see that looks relevant is to try reformatting the SC card with 2 primary partitions.

Read what i wrote? Do the following:
1) Recreate the partitions on your sdcard using GParted
2) Do a full wipe BEFORE flashing.
3) Re-flash the rom and select stock a2sd
4) Do NOT wipe again
4) Reboot, start Terminal emulator, set up a2sd
5) See if apps stay

On my first try I selected stock A2SD and set it up as explained using the terminal. (using a 2GB ext3 partition, placed after FAT32)
I rebooted and everything seemed fine, and I installed several apps. After a while, though, I got the "insufficient storage" error whenever I tried to install something. In the application manager the internal memory available had a large negative value.
I then wiped everything, reformated the 2GB ext3 partition to ext4, using "Minitool parition wizard" and reinstalled the Sandvold ICS ROM with Amarullz. Everything seems fine, and it shows 2GB internal memory. However, I've noticed that the ROM gets more unstable the more apps I install (it shows 500MB installed apps now, after removing around 50MB)...
Most of the time what happens is that system apps start crashing (Google Music, Dialler, Contacts, etc.) out of nowhere. After a while normal apps crash on execution as well. Google music is useless, as it crashes after a few songs and brings down the whole phone. Other music apps don't have this problem.
Am I doing anything wrong with the way I set up Amarullz? Should I retry stock A2SD with ext4?
I'm using stock HBOOT, Nova launcher and stock kernel.

Got there ..... but.....
After repartitioning my SD card for the third time ... I finally have this working.
Thanks to all for help/advice ..... but (isn't there always a but) ....
Downloads from the Market/Play are extremely slow maybe 5+ times the same apps took before .... I have tried on different WiFi connections - still the same.
Is this a consequence of the write speed of my SD card (it is only class 4) ... I did see a post in another thread where a class 4 wasn't recommended, but this was refuted by others using a class 4 card.
Otherwise all apps seem to be running OK, with no real loss of performance.
I guess once I have finally loaded up on all the apps I want, the Play updates will be more infrequent and less of an issue.

Phone no longer has anything in 'Internal Storage', can't download files

A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?

xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root

Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!

dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.

I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!

dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.