Motorola DEFY sd card driver FIX - Defy General

DO NOT APPLY THE ZIP I UPLOADED, READ EDIT 2​
Edit: I will make a flashable fix in a .zip inspired from CM7 RC1.5, with only the mmcfix in it, therefor anybody can use it, even people on official ROMs or other custom ROMs than CM7.
Work in progress....
Flashable zip nearly ready with mmcfix from CM7...
Zip script works correctly, testing...
Soft brick..
Flashed back my stock Froyo, restoring my nandroid backup (this shows you how important a backup can be! )....
Back to work! ^^ .....
Edit 2: I'll upload my mmcfix_signed_crakeron.zip for show only, it !!!DOES NOT WORK!!! right now and if you apply it through CWM you will !!!SOFTBRICK!!!. It is for people to take a look at it only, especially my update-script, and try and figure out what is wrong, or in my opinion, what i have forgot to put in it, seen as there is no sytax problems.
Hi all,
As you all know, our lovely Defy seems to have a problem when it comes to using sd cards... where *GENERALLY* all class 2 cards are fine, and problems may occur with higher class cards.
The problem is basically: the phone loses its write acces to the card, and therefor for example the photo camera app can take pictures, but can't save them... Another sign of this issue would be an absurd "SD Card damages/corrupted, please format" notification, and the sdcard never mounting again untill you well...re-format the card. This happens to me once a week, making me have to backup my stuff to the pc, format the card, and then put it all back on the card, and voila off we go till the next "false corruption" .
I've done some research, seen as this is a software issue, and not hardware, and i have found out it is an OMAP kernel issue:
"SD card problems since 2.2 update is a bug in OMAP kernel sources for froyo. CyanogenMod developpers worked hard to patch the kernel but it is hard to correct motorola bugs due to the locked bootloader." (source: Motorola support forums")
here is what i also found:
http://maemo.org/community/maemo-users/n900_microsd_card_i-o_errors_and_corruption/
To resume the thread, a Nokia n900 user, which also has a TI OMAP proc., discovered what was faulty:
some function in the driver (to keep this simple i will not name it, people interested and devs please just click on the link), dynamically calculates a DTO value based on the SD card's caracteristics. THIS IS WHAT IS NOT WORKING CORRECTLY
the guy simply modified a function in the omap_hsmmc driver so as it would use a constant universal DTO value, that would work with all sdcards, turning the DTO from dynamic, to static
Right, now you're thinking "what has this got to do with our Defy?"
Well...it has been sead in motorola milestone forum in xda, that:
"Since N900 uses the same SOC as Milestone and probably much of the drivers code are the same, perhaps the fix for N900 could be implemented as well? Not sure whether TI OMAP drivers are builtin in the kernel or not... If possible, could you please check this?"
(source: http://forum.xda-developers.com/showpost.php?p=17033833&postcount=5563)
and it is also said somewhere that this fix should also apply to the Motorola Defy.
I think I could be capable of making this fix for us, i just need some help:
(1) Where is the omap mmc driver situated in our /system ?
After having found it, i can copy it on to my sd card, and open it up and have a look (it is expected to be a C language file, i'm familiar enough with C to be able to edit the driver )
(2) I would like that driver from an official 2.1 ROM, and one from a 2.2 one, just to compare them
What do you think guys? If one of you know where to find the driver could you PM me to help me get started?
P.S This is not a thread about who's sdcard works and who's doesn't, so don't post millions of "my kingston 8gb class X works fine"
P.P.S Hit the THANKS! button if you want to support me, it costs nothing and makes my day!

the fix is already included in cyanogenmod since RC 1.5

reserved for futur use

vick33 said:
the fix is already included in cyanogenmod since RC 1.5
Click to expand...
Click to collapse
I know, but some of us out here don't want to go CyanogenMod, i'll contact Quarx and see if he could cooperate with me so that every one and every ROM could benefit from the fix

crakeron said:
I know, but some of us out here don't want to go CyanogenMod, i'll contact Quarx and see if he could cooperate with me so that every one and every ROM could benefit from the fix
Click to expand...
Click to collapse
The sources are public you can use them if you want. Now cyanogenmod is extremely good and stable. Because of the same kernel i think you can use the modul from cyanogenmod. Try if it works or not.

vick33 said:
The sources are public you can use them if you want. Now cyanogenmod is extremely good and stable. Because of the same kernel i think you can use the modul from cyanogenmod. Try if it works or not.
Click to expand...
Click to collapse
Will do. I'm working on it right now and planning to make a flashable .zip for cwm, that way everyone will have the fix
P.S. this is exciting

Made the update zip, the script seems to be OK, but just a bit missing, the device didn't like having something added in /system/lib/modules. I had write acces to it, maybe i have to put acces back to read only before ending script?
You can have a look at it to try and find out, but DO NOT flash the zip or you'll soft brick

Hi Crackeron, any good news for your script ?
Best regards
Cordialement...

alias4defy said:
Hi Crackeron, any good news for your script ?
Best regards
Cordialement...
Click to expand...
Click to collapse
no aka fail

i´m waiting for this fix too!!!

I've built an update-script which writes the module into "/system" partition.
In case of soft-brick, i've built another script which erases the file.
I've flashed it on CM7 ( 15th of october ) and it worked as the fix is already embedded in the ROM.
Let me know whether it works with other ROMs.
P.S. Scripts are written in Edify syntax.
Update: i forgot to include the init.d script that loads the fix once the device is on.
Now i've fixed. It should work!

Could u please drop a few words about install procedure? Thx.

toffifee63 said:
Could u please drop a few words about install procedure? Thx.
Click to expand...
Click to collapse
You've only to flash the zip through clockwork recovery mod.

carlo93 said:
I've built an update-script which writes the module into "/system" partition.
In case of soft-brick, i've built another script which erases the file.
I've flashed it on CM7 ( 15th of october ) and it worked as the fix is already embedded in the ROM.
Let me know whether it works with other ROMs.
P.S. Scripts are written in Edify syntax.
Update: i forgot to include the init.d script that loads the fix once the device is on.
Now i've fixed. It should work!
Click to expand...
Click to collapse
I've been looking on github on the CM7 project, and unfortunately it seems that there is not ONLY mmcfix.ko needed. We must figure out which files are needed in order for the fix to work :/ (i'm thinking of this "hangs.c" file if i remember correctly that appears in the C code in mmcfix.ko... I'll have a talk to quarx.
Sorry for the time it takes, i'm quite busy with my studies right now, but i haven't forgot you guys =).

Solved!!
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997

espaciosalter20 said:
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997
Click to expand...
Click to collapse
Oh, it wasn't as hard as i thought then :/..i was going waaay complicated in the init scripts ><. Anyway well done
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy

espaciosalter20 said:
i figure out:
please, see this post
http://forum.xda-developers.com/showthread.php?t=1596997
Click to expand...
Click to collapse
I can't post/reply at Development group, so I post here. The patch still have problem. After apply this path on MS2Ginger 3.0, any install app action from SD card will cause reboot problem. My phone is defy with red lens, and the sd card is transcend 16G c10 card.

need this fix, don't have a reader...
my SD cards were all recognised on stock froyo (not sure of build, possibly taiwan retail):? but now after new eclair and froyo sbfs the sdcards not recognised...weird huh?

I have a class 10 16GB.
The stock Froyo SEA 15 hangs often.... yesterday the defy said that SD card is damaged... but I did not format it and removed sdcard and put it in Nokia E5 and to my surprise it was working perfect there....
I have not installed your fix or any mcc fix till now.
This FIX is desparately needed.
For those who get the error that SD Card is damaged... please dont format it in your defy.
Use a computer or other mobile to format the sd card.

OK Guys got solution in this thread:
http://forum.xda-developers.com/show...00&postcount=2
Copy mmcfix.ko & symsearch.ko in /system/lib/modules and change the permissions to rw r r for both files.
Modify load_modules.sh as mentioned below and set permission as rwx r-x r-x
So just add the following lines in load_modules.sh files of /system/bin so it looks like this:
#!/system/bin/sh
export PATH=/system/bin:$PATH
# Install GAN virtual interface kernel module
if [ -e /system/lib/modules/kineto_gan.ko ]; then
insmod /system/lib/modules/kineto_gan.ko
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/mmcfix.ko
fi
Enjoy !!

Related

[Android] _BETA_ Eclair Hero-KingxKxKlair-0.6 Updated with working Wifi 17 Dec

Starting this thread here for running this Eclair-Hero build on our Kaisers. Many thanks to all devs below!!
jamezelle said:
King Klair Hero 0.6
First and Foremost this build was ported by Mssmison and the ril(radio interface layer), and audio libraries were written by Vilord!!! im pretty sure the gps library was written by Srwalter. vilord may have helped port it to eclair. (will get back to you on that). without DZO we would still be using windows mobile "" but were not ""
To Donate: to these fine gents visit http://sourceforge.net/apps/trac/androidhtc/wiki/WikiStart and scroll down to the donation links
B to the E to the T to the A
this is very beta, well almost alpha(first release for us vogue users so report any bugs that havent been mentioned in this post)
what works:
gps
calls
data
wifi
sync(dont sign in to google during htc wizard, wait till next boot!! you have been warned!!!)
market
gmail
what doesn't:
camera
bluetooth
gtalk
get more widgets
will add screenies later
ENJOY
Click to expand...
Click to collapse
UPDATE 17 Dec:
Download the new rootfs below for working WiFi! Thanks enatefox!
Download:
system.sqsh [ver 0.6.01]
Eclair-ready__rootfs.img (rename to rootfs.img, of course)
eclairhero.user.conf (goes on your SD card in /android/conf)
OR if you have a swap partition on your SD card: eclairhero-swap_partition.user.conf (goes on your SD card as /android/conf/eclairhero.user.conf)
And if you don't have them already:
zImage-15-12-09 (the latest kernel from 15 Dec)
startup.txt (My personal HaRET startup.txt)
rootfs changelog:
Copied /init.cfg/init.eclairhero.rc to /init.cfg/init.eclairhero.kaiser.rc
Copied /init.cfg/init.eclair.rc to /init.cfg/init.eclair.kaiser.rc
Altered init to check that media folder exists in /sdcard/android/media instead of /sdcard/media
Altered init to support eclair.user.conf and eclairhero.user.conf
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Go straight to version 0.6.01 as posted above, version 0.6 gives me weird SIM errors.
This build takes FOREVER (5-10min) to boot. It goes through and even attempts to make a number of thumbnails for your images during first boot. I suggest watching it over adb so you'll know when it's settled and ready for input.
The HTC widgets are not working with this build.
TaskKiller is an absolute must, like other Hero builds this one loves to keep apps open.
Hmm, this build has successfully rebooted itself twice, during heavy use. I wish I knew how that worked, so we could get it to reboot on command!
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Almost downloaded Hero, just got vanilla Eclair to boot the first time. I'll look into wifi. Maybe it's me but Eclair seems faster than Donut but I haven't messed with it much. That should make Hero much nicer.. will post back when I get further
rugalck said:
Wifi not working D:
Also if I put 15-02-19, Haret asks for 11-12-09 (where can I find the latest haret?)
Why does it happen?
Click to expand...
Click to collapse
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
@enatefox:
O
Hero is very buggy, has too many problems to run daily for now. Overall Eclair Mike the fastest yet though! And the fonts are much better for qvga. Text autocomplete has issues.
polyrhythmic said:
The startup.txt needs to be updated for the new zImage, or you can download my updated one from the first post.
Click to expand...
Click to collapse
Nah, don't worry, it was something really really stupid.
In the same file you said, it was like "zImage 11-12-09" so now I saved it saying just "zImage". Now works fine.
Waiting for wifi updates, great work guys!
BTW, is there any way to take screenshots?
damn bootloop. I'll look at this tomorrow but that's a promise . I don't know where these wifi files came from. I dropped in the ones that I've used and we'll see. Right now I'm fixing telnet and some other issues to post back with but it will take a little bit of time. We're going to get this working for daily use.
Here's working wifi for Eclair:
http://www.mediafire.com/?ezyzekjozj3
EDIT, I didn't get Hero to boot for me (looping) but I forgot to update Eclair Hero's conf file to match conf.eclair.kaiser.rc.. can someone either do that and repost or wait for me to finish some perm issues with it and I will upload one for Hero. Sorry about that.
I have got to be doing something wrong. I am using all of the files from the 1st post and the rootfs.img from enatefox's last post and this sat for 30 minutes. I even copied the user file to the sd card, to the /sdcard/CONF folder and into the /sdcard/Android/CONF folder and still it sits. I'll get a post of the last few lines up later to see if I just need to wait more or not. I am also using an empy 2GB Fat32 SD Card with the 1.71 radio. All other builds work but this one???
Any ideas?
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
rugalck said:
I could mirror my files. They're working perfect, even wifi and etc (bluetooth not yet).
Folder Screenshot:
http://i46.tinypic.com/oqbo2c.jpg
Then you delete data.img to start from the beginning.
that could solve your issues
Click to expand...
Click to collapse
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
polyrhythmic said:
TIPS:
You will need a fresh data partition/data.img for this build. Don't forget to back up your old one first!
Click to expand...
Click to collapse
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
FYI, your 'conf' and 'android' folders should be named in lowercase, if they aren't already.
The only way we can tell what is wrong is to see whatever the console says before it freezes, or ADB logs if you can make it that far. Post whatever you've got.
j101399j said:
If u don't mind, that would be great. I also just noticed that even after a 1/2 hr, a data.img file never was created
edit: wait, your system file in that picture is only 44.325 MB; the latest system file from post 1 is 89.3? Why so different?
Also
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
If it wasn't created then... you wouldn't need to delete it, do you?
ROM Size: That's because I use mixed files from the different Eclair thread's.
It's a "package" of what worked fine on my device.
Most of the files are from this thread, but the system.sqsh is from this one:
http://forum.xda-developers.com/showthread.php?t=600154
Mirror File: http://rapidshare.com/files/322793487/android.rar.html (up to 10 times, I don't have a premium account D: )
j101399j said:
What do you mean, clean data.img, do I need a clean one already on the SDCard for 1st run, so none present?
Click to expand...
Click to collapse
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
rugalck said:
ROM Size: That's because I use mixed files from the different Eclair thread's.
http://forum.xda-developers.com/showthread.php?t=600154
Click to expand...
Click to collapse
thank you, will try
polyrhythmic said:
You need to have one of two things:
If you are using the partitioned SD method, you need a fresh ext2 partition (newly created with a partition manager, or wiped using the Android install script)
If you are using the data.img file method, just make sure there's no data.img on your SD so the installer can create one during boot.
Click to expand...
Click to collapse
I competly forgot about needing all lowercase letters; as for the data.img file, that is what I though; Thank you
[EDIT]
That is so wierd; I had to place the system.img into the /sdcard/android folder and the use user file in these 3 places /sdcard /sdcard/android and /sdcard/android/conf
Now it works. Don't know what changed, but it works
j101399j said:
thank you, will try
Click to expand...
Click to collapse
http://rapidshare.com/files/322793487/android.rar.html
I can almost guarantee you that the .conf file in your SD root and the .conf file in /android/ are ignored, try deleting them and just leave the .conf in the /conf/ directory. And yes, everything including the system.img/system.sqsh should go in the /android/ folder now.
I bet you can boot this Hero build, but it has a lot of bugs, you'll probably be happier with plain Eclair that rugalck linked.
hey guys ill update when king drops 0.7
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
RDilus said:
keep getting stuck at this part:
ANDROID [ 30.906001] init: Unable
to open persistant property directory /data/property
error 2
How to fix this
thanks
Click to expand...
Click to collapse
If it's the first boot, make sure to have at least 300mb free in your SD card.
rugalck said:
If it's the first boot, make sure to have at least 300mb free in your SD card.
Click to expand...
Click to collapse
not to be rude but im not stupid -.-'
i have like 5GB free...

[26 JAN][CWM] DR Desire V.0.1 [Kern.MDJ 10.3][DATA2EXT][RMNET]

Hello,
this is my first attempt to Android build for HD2, i'm not a dev, i only made this build for my personal purpose and i thought to share it with this community.
Before some specs i wanna thanks some people:
-XDA-Developers
-DFT Forum
-Cotulla and bepe for MAGLDR link
-RaiderX303 for ClockWorkMod link
-M-Deejay for Kernel link
-Gauner1986
-Taknarosh for Bootanimation link
-Rafpigna for his fonts link
-EStrong Inc. for Es-Esplorer link
and......
all guys at #HTC-linux, DarkStone, Markinus, Projection, Bauner, Tytung, White-Energy and many other, give me a call if i missed you
REQUIREMENTS:​
Hardspl 2.08
MAGLDR 1.11 (follow my sig for 1.12)
ClockWorkMod
SPECS:​
Based on Desire Sense 2.29.405.5 with all stock apps.
Kernel by M-Deejay 10.3
Data and Apps to EXT 2/3/4
GoogleMaps 5.0 Included
Es-FileExplorer included
Custom Fonts (ty to Rafpigna)
Custom BootAnimation (ty to Taknarosh)
No Sound on boot
Battery with %
Properly rooted
Quadrant score 1700-1800 @ 998
Quadrant score 2000-2200 @ 1536
Battery at sleep 4-6 ma
Code:
[CENTER][B]INSTRUCTIONS:[/B][/CENTER]
[B]1. back-up your SD Card files and folder
2. Copy the file inside "Copy to SD Card Root"and "Copy to SD Card" folder to your main root SD Card
3. Boot you phone while hold and press "power" button till MAGLDR menu will appear.
4. Choose n.5 voice, "USB Flasher"
5. Plug in your USB cable to your phone and PC till when "wait USB...USB" will appear
6. Run "DAF.exe" from ClockWorkMode, your phone will go to reboot, press and hold power button to enter MAGLDR menu
again.
7. From MAGLDR menu, choose "Boot AD SD"
8. Now you are in ClockWorkMode (CWR) menu.
9. Choose "advanced"->"Partition SD Card" and grab the EXT size of your choice, i suggest to don't go over 2048.
10. Set Swap Size to 0
11. Now you have an EXT3 partition in your SD card, you should be good to go but if you want an EXT4 partiton, you
need to :
11A. Boot into any Linux Live Distro build (Ubuntu 10.10 is what i have) and format your sd card.
11B. Search in XDA-Developers forum for a Tutorial (don't remember yet the link lol)
12. From CWM menu choose "install zip from SD card"-->"Choose zip from sdcard"--> next find "DR Desire HD2 V.0.1 and press the green button till the process will end and then reboot your phone.[/B]
-----------------------------------------------------------------------------
Testes on my phone with daily use and it works fine.
TMOUS users : untested.
VoiceInCall fix, inside.
My Radio is 2.10.50.28_2
-----------------------------------------------------------------------------
DOWNLOAD.
happy flash.....and be kind
ChangeLog:
Code:
V.0.1
Initial Release
UPDATES:
(copy your choice .zip to your SD card, reboot to CWM and apply .zip from menu)
Gauner Kernel : Download No Overclock but less power consummation and more stable (smartass Gov)
MDeejay 10.4 : Download
Congratulations on your first build, will download and test tomorrow
Downloading...
I'll report back soon.
yay nice to see another android dev on the scene, welcome
please another mirror for downloading...i cant download it -.-
Hi,
Thank you so much. This is the best nand sense rom that i have come across so far. I love that you decided to bundle Data2EXT with Stock Desire.
Aside from some wakeup lag (bearable), I haven't been able to find any problems.
Keep up the good work.
Thanks
Mostly, i dont have lag on power, though it seems to be a common Sense build issue, anyway i did put some kernel updates on post #3.
I used all the day my build with SetCpu @ 1190 without problem and lags and battery is fine, worth a try .
Check in first post what radio i'm using, maybe changing it can help.
smakazmi said:
Hi,
Thank you so much. This is the best nand sense rom that i have come across so far. I love that you decided to bundle Data2EXT with Stock Desire.
Aside from some wakeup lag (bearable), I haven't been able to find any problems.
Keep up the good work.
Click to expand...
Click to collapse
Looks good, tempted to download as the build I'm using at the moment doesn't work with MDJ S10.3.
Maybe, you could include a stock framework and stock fonts for stock lovers?
No problem......i will make an update with both stock fonts and framework.
shadiku said:
Looks good, tempted to download as the build I'm using at the moment doesn't work with MDJ S10.3.
Maybe, you could include a stock framework and stock fonts for stock lovers?
Click to expand...
Click to collapse
build looks nice - this is my second nand flash both desire based.
The first worked perfectly and then i installed yours so i could get the sd memory but now im finding that alot of the apps that previously worked no longer do and i have also lost contacts.
The previous build was lightning fast whereas this seems to have a slight lag.
Do you think i have done something wrong? And should i download those 2 updates
Which build you was using?
Looking at your reply i suppose that you was using a non Data2Ext build, so it is normal:
_ Loosing App and Data if not a previous backup with Titanium backup,Mybackup,...
_A little lag, because Data are on SD card.
perfectknight75 said:
build looks nice - this is my second nand flash both desire based.
The first worked perfectly and then i installed yours so i could get the sd memory but now im finding that alot of the apps that previously worked no longer do and i have also lost contacts.
The previous build was lightning fast whereas this seems to have a slight lag.
Do you think i have done something wrong? And should i download those 2 updates
Click to expand...
Click to collapse
No, it wasnt a d2ext build (DFT's Desire build)
I guess you are right and i should expect lag etc
Am i right to assume that the apps that i find that arent working are doing so because they dont support a2sd? or should they 'believe' that they are on the rom?
I find that a large number of them, when i try to load them, just flash up the screen asking me to force close them.
Basic apps that should always run like Lookout security (worked previously) but only works intermittently now and i keep having to register apps such as the Android Market.
Also i cant seem to save contacts.
I dont know if there are apps that doesn't support a2sd but i just gave a try to Lookout Security and it does work as expected and i also can save contacts without any problem.
My guess is that you have something wrong with your SD card partition, read again the Readme.txt for "how to" partition it and before flash again the build, give a wipe from Clockworkmod menu.
perfectknight75 said:
No, it wasnt a d2ext build (DFT's Desire build)
I guess you are right and i should expect lag etc
Am i right to assume that the apps that i find that arent working are doing so because they dont support a2sd? or should they 'believe' that they are on the rom?
I find that a large number of them, when i try to load them, just flash up the screen asking me to force close them.
Basic apps that should always run like Lookout security (worked previously) but only works intermittently now and i keep having to register apps such as the Android Market.
Also i cant seem to save contacts.
Click to expand...
Click to collapse
yeah i think that's what i will do.
Although i followed all the steps - im sure i must have gone wrong somewhere.
I was also finding that some of the games dont save my progress.
I'll let you know how i get on.
Thanks for your help
thanks for this rom seems to be the best desire rom,only one thing can you increase usb transfer speed?Markinus has done this with his rom,thanks again
Thanks
Anyway USB transfer it is already patched, though i've seen that it is slow while using Multi Mount SD card.apk, can't go over 2,00 mb/s.
kgian2007 said:
thanks for this rom seems to be the best desire rom,only one thing can you increase usb transfer speed?Markinus has done this with his rom,thanks again
Click to expand...
Click to collapse
this version is awesome! thanks
Hi,
Sorry to join that late but I was conviced that the desire HD had the closest hardware to the HD2.
Now knowing it is not would you be king to provide a working link ?

Installing Android without SD, to test NAND?

Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.
No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!
n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??
daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.
If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.
help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam
I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...
I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.

[BUILD] XDAndroid Froyo 2.2.2 FRX06 for CWM Recovery 1.8 (ClockWorkMod)

THIS BUILD IS OUTDATED, CHECK:
http://forum.xda-developers.com/showthread.php?t=1177721
I'd like to "present" my recompilation of XDAndroid FRX06 to work with Neopeek's CWM 1.8
No credit for me, but for all XDAndroid devs and Neopeek &co for this.
It doesn't have any other modifications apart from making it available to install from CWM, so everything that applies to FRX06 is useful here. You're the one to decide if you prefer looped or partitioned installs.
Don't try this if you don't know what you're doing. It's only tested by me, so what I'm looking for are TESTERS. PLEASE READ EVERYTHING CAREFULLY BEFORE DOING ANYTHING.
Normally it would be easy to return to previous state by repartitioning/formatting SD, but who knows. I take no responsability for any damage to your device.
The instructions for installing CWM are in Neopeek's forum. Only points:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
2.- Startup.txt, ts-calibration, kernel and modules must be in the same dir as haret.exe, in this case inside "npkboot" dir.
3.-To move in the CWM menu with our Blackys:
Peteflyman said:
I just toggle between "Reboot system now", push "Vol Up" to get directly to "Power off", and then toggle "Vol Down" to get back to "Reboot system now". I just do that a couple of times then "Back menu button enabled" usually shows up. That's it. Hope it works for you guys as well!
Click to expand...
Click to collapse
After the "back menu button enabled" you can use power off button to confirm menu selection. Just select "install zip from sdcard", "choose zip from sdcard" and choose my zip (ofc, don't uncompress it).
4.- You don't need to install Gapps, they're included in the build.
5.- After installed, "reboot system now" and start haret again. Let it work for a while without touching anything until you see PIN or unlock screen to begin using Android.
6.- I'd recommend rebooting a second time before starting to configure everything...
It should work in any device where CWM and XDAndroid work, but the configurations I attach here are for TOUCH HD (Blackstone). If you want to try with other devices, be careful to use the appropiate config files (they shouldn't be difficult to find in your device's forum).
I'm using 1337 kernel & modules from Glemsom's autobuild and it works perfectly with my device, feel free to use the one that suits you better.
Download link:
http://www.megaupload.com/?d=SUBUG5I8
If you have any problem, I'll try to help, but for CWM problems please ask in their forum as you'll find better assistance.
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
if you want to install any other build,or reinstall frx06,go to recovery,choose mounts and storage,then format data,format cache,format system (don't format sdcard for obvious reasons) and then mount data,cache,system,go back and install zip from sd card,choose your zip.
also if you find a build without gapps,go to cyanogenmod.com and grab it there,you should pich gapps for cyanogenmod 6 because that's the froyo build....MDPI or HDPI doesn't matter in our case
many problems are result of gapps missing (some builds come without them,this one doesn't) such as call rejecting or showing black screen instead of lockscreen when you wake the device,so be sure to install them
arrrghhh said:
Huh. I guess I'll give it a shot - I cooked a build with CWM & FRX06, was force close city. Tried to fix it, but not hard... Just chalked it up to CWM being crappy since I was able to run FRX06 on dedicated partitions no problem .
Click to expand...
Click to collapse
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Eodun said:
Then the only difference you'll notice is that you have CWM recovery Anyway, it works pretty well for me, and since I can now write updater-scripts I'll be able to change things very easily
Edit: Now I only have to learn to compare directories to be able to give incremental updates when FRX07 and so on come out!
Click to expand...
Click to collapse
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
farukb said:
i suggest you to take a working build and start swapping things and trying,it's not that hard,you can go @ neopeek and ask there,there are several tutorials i believe
just be sure to use a froyo build for your froyo build
Click to expand...
Click to collapse
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Eodun said:
Well, from now I only want to have the /system updated from time to time and identical to XDAndroid if I can.
If I think I can add something of value, I'll make another package to make clear they're different things But for now, I can't add anything (that works)
Click to expand...
Click to collapse
you can at least start with
/system
/app (add or remove apps)
/fonts (obvious)
/framework (the "look" of the build is defined here,so if you want your froyo to look like ginger,take some of the ginger files and swap with those in this one)
/media (it'll tell you what to do by itself)
other folders are build regarded and some playing and asking pros is advised here
any screenshots ?
Simon_WM said:
any screenshots ?
Click to expand...
Click to collapse
It's a vanilla Froyo, identical to FRX06, so I didn't think they were needed. Just look at any basic original Froyo install.
Eodun said:
1.- My partition schema, for 8Gb SDCard, is:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 150MB) Contains /system - the base ROM
3rd partition: EXT2 (data / about 400 MB) Used as device's internal memory. You can use more if you install a lot of non-movable apps, but between 4 and 500 should do.
4th partition: EXT2 (cache / about 100MB) Dalvik's cache. 100 should be enough
I used Minitool Partition Wizard for the partitioning.
Click to expand...
Click to collapse
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
every card is "original" just the manufacturer is different....eg trandescent cards dont work,what's your card?
ypsmav said:
Hi Eodun,
Can you pls let us know if you are working with the original microSD 8Gb class2?
Thanks
Click to expand...
Click to collapse
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Eodun said:
Didn't change the sd that came with the device if that's what you mean. It's a Sandisk, can't tell the class
Click to expand...
Click to collapse
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
arrrghhh said:
If it has no C2, C4 etc then it's a "classless" card. I have several, seems any card below 2gig that was sold before a certain time are classless.
Click to expand...
Click to collapse
Well, I can't tell because I'm in android now and can't extract it XD Never had the curiosity to check.
Let me see... Yeah, it has a "2" inside sort of a "C", so it must be a C2 8Gb SanDisk MicroSDHC lol
Working on FRX07 update.zip to test if it works with CWM
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
ypsmav said:
Hi Eodun,
Looking forward to the FRX07 CWM!
Do you think that it is required that Neopeak updates the roofts to the latests version?
Click to expand...
Click to collapse
helicopter88 is already working on that
ypsmav said:
regarding your FRX06 CWM, I have a quick question. It is possible to use my old data.img from the normal FRX06?
I guess that it may be possible to copy it on the data EXT2 partition but I can't access via windows XP.
Also tried restoring using CWM (I did a backup and replaced the data.img), but I get a checksum error. Any way to change the checksum to be able to do it?
Thanks in advance
Click to expand...
Click to collapse
I don't think so. But if you backup everything with titanium backup and then restore apps, appdata and system settings (only those that appear in green) you'll have everything as before.
Eodun said:
Working on FRX07 update.zip to test if it works with CWM
Click to expand...
Click to collapse
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
arrrghhh said:
Dude, you don't need to work on anything.
Just grab the FRX07 update.zip from XDAndroid and you're golden... stine makes updates for recovery, which should work fine for CWM.
Click to expand...
Click to collapse
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
ypsmav said:
Confirm it updates correctly, but there are some problems with the old Kernel/rootfs.
I can't get wifi to work and I can't turn the device off.
The 20110716 Kernel is not working for Blackstone Topaz.
We need to wait...
Click to expand...
Click to collapse
@arrrghhh: Yeah, I know the update is available, but ypsmav noticed the problem: I need the new rootfs for CWM, and I'm not able to adapt it. As I said, work is being done for that.
Thanks for your replies
Ps It will be a big problem if latest kernel doesn't boot. I haven't been able to boot with it. Edit: But still have to check if it boots with a clean data.

CWM NEOFroyo v0.1 fastest build yet (updated8/21/11))

This is a complete package just unzip folder on sd card.
Here is original thread by neopeek
people having wifi problems check the original thread they have a fix
This is the CWM 1.9 thread wich is included in folder already
Using starfox test kernel from XDA (Rhodium only)
EDIT: per starfox dont use test kernels use his new vanilla stable kernel
GAPPS already included.
Im not a dev, just put stuff together credit goes to all authors just posting here to spread the word
DOWNLOAD
Sure, I'll bite. I've got an extra micro-sd card here. What's the worst that could happen?
It's a pretty fast build, I tried it on Neopeeks site.
It is MDPI, so the look of it isn't quite as crisp... (you can see what I mean by the notification bar 3g, etc...lower resolution basically) but I was impressed by the speed. All the animations, etc are disabled by default and I believe that's Zeam that is the default launcher... it is quite snappy out of the box.
what tweaks you did?
no tweaks just put it together
This version is the fastest thing I've tried (probably due to mdpi-gapps), but I have two major issues.
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
2) Camera is tremendously unstable. Most of the times it crashes bringing down the entire OS or if I am lucky it will crash the camera app and refuse to start again until a reboot.
Of course there are random hiccups here and there (like most builds), but it is quite close replacing WM for every day usage.
XavierGr said:
1) Wifi will sometimes refuse to turn on, saying wifi error on the check box. It must be related to tethering and hotspot settings, because after I mess with these I get an instant reboot.
Click to expand...
Click to collapse
This is actually not that unusual... I would get this on my epic4g... which is an android phone .
If you don't mind, please use the vanilla kernel that I posted instead of the testing kernel. While I don't mind that it is being bundled, the [Test] kernel was never meant to be used for long term, and is liable to include stuff that is unstable and/or changed on my whim. The vanilla kernel contains some of the tweaks that I consider to be stable and is based on known autobuild releases+supports all devices. Thanks.
http://forum.xda-developers.com/showthread.php?t=1221499
-- Starfox
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
anish88 said:
you think you can make a build with the latest rootfs, starfox's latest kernel, the led patches too?
Click to expand...
Click to collapse
There's nothing stopping you from doing that.
Including testing stuff into a public build is never a good idea. I wouldn't appreciate anything I distribute for testing to be put into a build. It's meant for testing, so anyone that installs/uses it should know full well what they're getting into. Placing it into a build circumvents that, and everyone ends up using it unknowingly.
To everybody with wi-fi issue:
I've done a small fix
http://www.multiupload.com/7NSGZQZXPC
(wich is in the first post of this thread on neopeek.com)
This will fix if your problem isn't the kernel
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
nekikekec said:
wifi scanning problem:
after updating wifi-nvram seems to be ok.
anyway,
fastest rom i have tried.
Click to expand...
Click to collapse
What problem did you have exactly and what do you mean by updating wifi-nvram?
I also have a wifi problem specifically with this build but can't solve it.
(Wifi works only once per boot)
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
nekikekec said:
after turning wifi on phone started scanning for networks. after few seconds app crashed not finding anything. i guess there is a problem with assigning mac address.
anyway, as already described, it is known problem :
here
Click to expand...
Click to collapse
That didn't work for me at all.
Can't get CWM working
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
nileshvedi said:
Hey guys,
I must be doing something wrong, but don't know what.
I just can't get CWM running on my TP2. I followed all the instructions precisely, got into CWM once, even flashed the ROM from SD card, but can't do it again.
I even reflashed my device, Re did the entire SD card but just can't get in to CWM.
Upon booting Haret, I press volume down, but the screen just gets stuck there and doesn't move forward. Please help, I'm trying to flash NeoFroyo 0.1
Regards,
Nilesh
Click to expand...
Click to collapse
Did you set all your partitions as primary?
vzihome said:
Did you set all your partitions as primary?
Click to expand...
Click to collapse
Yes I did that too....
SD Card (All Partitions Primary)
Partition 1: 6.4 GB - FAT32
Partition 2: System - 300 MB - EXT2
Partition 1: Data - 300 MB - EXT2
Partition 1: Cache - 300 MB - EXT2
I put the npkboot folder with startup for RHOD100 on the SD Card (Root) and the NeoFroyo Zip also on the root.
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Run Haret from SD Card through File Explorer & press Volume Down - Result: Frozen Screen!!!
Does not enter into CWM recovery...
Are all the steps above right.
Regards,
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
WHY?
CWM rootfs works only in npkboot.
nileshvedi said:
Plus, I also put the contents of the npkboot folder on root of the phone. (Not the folder npkboot)
Click to expand...
Click to collapse
I'm a little confused with what you did.
Basically just unzip his folder you downloaded and then move the Entire npkboot folder to the root of ur sd card.
So there will be nothing on your sd card except the folder. Inside that folder will be everything just as you unzipped it. So for example haret would be at "Sdcard/npkboot/haret.exe". Then just switch/edit the startup.txt in the npkboot folder for your phone and boot into CWM.
You don't need to move anything outside of his npkboot folder that you unzipped.

Categories

Resources