Related
It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...
Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.
ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?
i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...
Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...
I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either
My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list
Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?
Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!
I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...
Anyone, anything?
Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR
I still have this problem.
I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.
The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something
I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.
It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR
Ah yes it works! Beautiful beautiful!
Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere
I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?
use the right starup.txt file
Hi guys, have posted this into the coolrom forum but no answer as yet. Fresh install of Coolrom HD... it says "D2SD" in the title but i still only have 130mb free on my phone? When i installed StarbustRom D2SD i had way more free space... any ideas?
Have you flash the data2sd script?
Did u partition the Sd exactly the way its described in the Rom thread?
Yeah i believe so, and it worked fine with the old Starbust rom. Are you saying that the rom will detect if the partition table is correct and automatically use it for Data2SD?
hmm as far is i read the post of starburst its a speacial D2SD script or a specific version ... dunno maybe thats the problem?
Trying it again now... i bet i messed up somewhere
Hmm.... same again followed it to a T... reboots fine 1st time but 2nd reboot after installing D2SD Tiny zip im now stuck on a white HTC screen...
Partitioning SDcard
1st Partition: FAT32 - xyzMB
2nd Partition: EXT4 - xyzMB But Not More Than 2GB.
A2SDKillerV5.zip
Data2SDInstallerv1.3_tiny.zip
The guide for data2sd...As Per BlueVD thanks man!
People shouldn't finish the setup wizard. If you backup your data with google, upon signing in, it will start to reinstall the apps you had before. In my case it installed a few apps before I could reboot into recovery and flash data2sd. Not sure if the data2sd had problems, but upon flashing it and restarting I got a lot of FC's. So the safest steps would be to finish the setup wizard after the data2sd install.
Here's exactly how I did it (5 times, just to check) and got no problems:
1) Place Cool_Rom.zip, A2SDKillerV5.zip & Data2SDInstallerv1.3_tiny.zp into SDcard.
2) Reboot in Recovery, toggle signature check off.
3) Flash Cool_Rom.zip. DO NOT REBOOT.
4) Flash A2SDKillerV5.zip
5) Reboot, don't finish the configuration wizard or don't add your google or htc sense account during setup.
6) Reboot into Recovery.
7) Flash Data2SDInstallerv1.3_tiny.zp reboot, finish the setup wizard or manually add the google and htc sense accounts from Settings -> Accounts & Sync, and enjoy.
Follow those instructions exactly and you will be fine, don't cut corners. On first boot follow the initial setup to the end but don't sign in to anything (google, HTC sense, facebook etc etc).
Then use the power button to restart into recovery and flash the last zip and reboot. This will take about 10-15 minutes to load depending on the speed of your SD Card.
i have htc desire, and just installed Cool Aces v7.It's a great ROM but i was having a hard time managing apps for free space so i decided to install data2sd.
-I partitioned sd card with ROM manager.
-reflashed ROM
-imediatly without rebooting i installed A2SDkillerV11.zip
-the next step was to reboot but here is were my phone got stuck at the boot logo.
any ideas?
Try partitioning using G-parted in stead of Rom-Manager
how long did you leave it?
I read that data2sd can take up to 20 mins to sort itself out in some cases
Lothaen said:
how long did you leave it?
I read that data2sd can take up to 20 mins to sort itself out in some cases
Click to expand...
Click to collapse
probably not 20 mins.i will try that.10x for the tip
cevacu2005 said:
probably not 20 mins.i will try that.10x for the tip
Click to expand...
Click to collapse
hehe - its exactly what problem I ran into when I tried a data2... rom - only waited about 5-10 mins then flashed RUU/another rom... I should have waited longer to be honest as it probably would have worked
be interesting to know if it works or not!
Lothaen said:
hehe - its exactly what problem I ran into when I tried a data2... rom - only waited about 5-10 mins then flashed RUU/another rom... I should have waited longer to be honest as it probably would have worked
be interesting to know if it works or not!
Click to expand...
Click to collapse
i will keep you posted.i ran into another problem now.my sd card doesn't mont.i have to fix that now and after i can try again
cevacu2005 said:
i will keep you posted.i ran into another problem now.my sd card doesn't mont.i have to fix that now and after i can try again
Click to expand...
Click to collapse
i had similar problem which ended up being a corrupt SD card - sent it back and bought a new one...
tried running the hkw2test thing on it?
looks like the problem is a bit more serious now.u i try to wipe my data and cache i get this error Can't mount /dev/block/mmcblk0p2 (File exists) so i am pretty sure i messed up my internal partion.i looked it up and i found a very interesting post that tells you what to do in this case.but my problem is now that i am supossed to use adb shell to fix it but when i try to push the files i get this error: /sbin/sh:adb not found
i fixed this problem and now i am back to the original problem.the one i opened this topic for.i reflashed the rom and data2sd.now i am wainting for it to boot.it's been 10 mins now and still nothing.i will leave it for another 20 maybe i get lucky
Did you boot the rom after applying a2sdkiller? You should boot it up, run initial setup wizard skipping everything until it goes to the homescreen, then untick fastboot in settings>power, reboot to recovery and only then apply data2sd script. After installation of data2sd reboot and use the newly set up rom in any way u like with unlimited storage.
Smashed with my RCMix S loaded HTC Desire.
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!