Database Users

how do you update the radio rom??

Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse

Firstly it needs to have a recovery image installed I recommend Amon-Ra v 1.6.2.
Secondly you need to find the radio rom you wish to flash and put it onto the root of you phones sd card.
Thirdly enter the recovery image you have installed by holding power and home button from the phone being off.
Then select the radio.zip to flash.
Everything I have said here can easily be found how to do via searching this forum or its wiki.
also www.theunlockr.com will help with installing the recovery image.

lohtse said:
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Click to expand...
Click to collapse
First you will need to install the custom recovery console if you haven't done so already.
Then download your updated radio, put it on your SD, load into the recovery, then apply update. DONE!
If that is too brief,... let me know,...
EDIT... Ooops,... too late.

way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....

really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.

Lennyuk said:
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Click to expand...
Click to collapse
I came from wimo to android, and as it is said, it's quite hard to catch the thing at the beginning, but after everything seems easier than in wimo !! and more reliable... you have almost no chance to brick your hero after you installed the recovery boot.
radio : boot in recovery then select the good option.
rom : nandroid backup / install whatever rom you want / if you don't like it go for nandroid restore ( all you need is two Sd card.. the good one and the one for the "tests" ).... etc....
But at the beginning i was totally out but with a little time.. reading some posts (here and on the web) ... one day everything was more clear !
Ciao
Fred

lohtse said:
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
Click to expand...
Click to collapse
Its not hard at all. You can have the recovery installed and the radio updated in 5 minutes.
For step by step instructions follow the "Installing a recovery image" section in BTDAG's guide linked in my signature.
Then further down the same post, in the second yellow box there are instructions on "Updating your Radio".

Guys, the OP said he was issued the Hero at work, then two hours later said he was going to ditch Android... so what then, he's quitting his job? Troll alert. Don't feed the troll.

As to troll comment(yes offence has been caused)....hmmmmm.... Am going back to the trusty Kaiser... WE DON'T HAVE TO USE THE HERO.... We live in free(ish) world.. And the Phones are issued as an update to our old duty phones... Also I'm not the only one who uses them that feels the same.
Now to updating being easy. Gulp I must be eeer dum!!! Du hu Du HU must be the TROLL in me!
I have tried to install recovery image thing and well just cant get it to work... And now I find I have to root the hero too so things will install to sd card!!!! WTF this should all be standard like winmo and symbian etc...
I have been using smart phones since the Ericsson r380 and so far Android has failed to impress to the degree I am beginning to hate it....
Am far to used to having simply andfull access to everything..
Android is a HUGE learning curve that I suspect I may not have the patience for..
regards The TROLL sorry I mean Lohtse

Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL

lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
Click to expand...
Click to collapse
Wahey!!!! Good job man.
Ok,... So now you have the recovery image all you need to do is pick a custom ROM. Personally, I highly recommend MCR3.2 (link in signature at botom). It is an Android 1.5 ROM but is stable and fast, what more could you want for a work phone.This ROM is rooted and has apps2SD enabled. Once you have installed the ROM you will need to remember to create an ext2 partition on the SD card (easily done through the recovery). Then you are set to go!!!!

lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL TROLL
Click to expand...
Click to collapse
You're welcome And what ddotpatel said. MCR is fast & clean. By installing a custom recovery you've already done the only tricky bit.

Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..

lohtse said:
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
Click to expand...
Click to collapse
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Someone with more knowhow than me correct me if I am wrong?... CAULI?,... LENNY?

Can someone who knows please answer this question:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Thanks!

ddotpatel said:
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Click to expand...
Click to collapse
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition. All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer, if you're curious. Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed. The saving you make just from shifting the apks to sd is more than enough for most people it seems.

cauli said:
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition.
All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer.
Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed.
Click to expand...
Click to collapse
hmmmm I certainly noticed a drop in available memory on the phone to the degree of only having 54 megs free...

SebHTCHero said:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Click to expand...
Click to collapse
what is rf calibration?

What is radio rom used for by phone?

kendong2 said:
what is rf calibration?
Click to expand...
Click to collapse
A set of tables usually stored in NVRAM that takes into account the slight differences in the components used to build your phone. Every single phone is calibrated during manufacturing.
If the calibration is erased, it will look like it works but you can have all sort of problems from poor battery life to random drop from the network or poor sensibility (not to mention the higher than expected radio levels you could be emitting right next to your brain )

[Q] Motorola Flipout rooted. How to apps2sd?

The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?

I just got the flipout from rogers.. Is there anyplace that has a development forum for it? And does it have the efuse ? If it does, is it possible to do what was done with the droid X to it?

How did go so far ghostwheel? I'm eager to hear what else you have figured out.

You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App

ghostwheel said:
The Motorola Flipout is fairly easy to root, at least now. Universal Androot (get it here) works.
I am thinking about moving apps to the sd card. However, since I haven't reflashed the phone, and I don't have a ROM for it, I'd like to do it without reflashing. Is that possible?
If I partition an SD card correctly (ext3), copy all of /data onto that partition, and then mount that partition over /data, will that work? Or do I have to mount the card before the phone boots?
Or is it better to just copy /data/data, and mount the partition over /data/data?
It seems to me that mounting over a directory, as opposed to creating a link is least invasive, because on reboot the phone is as it was before. Is this right?
If I have to mount the sdcard before the phone boots, can I just edit one of the init scripts, or is that more complicated? I read about editing init.rc and repacking boot.img
Oh, HOWTO unpack edit and repack boot images seems to give good instructions. On the Flipout, boot is mtd4, and recovery is mtd5.
If I only modify boot, I can't brick my phone too badly? Since I haven't changed recovery, I should be able to recover (?). Can I create an update.zip that flashes the old boot.img and undoes my changes in case something goes wrong?
Click to expand...
Click to collapse
Hi,
I'd really like to help with that (I'm a confirm dev. for Cliq and CliqXT phones).
Hopefully we can do great things like we did for Cliq and CLiqXT (upgrade to 2.1!). (check my work at http://bit.ly/adlxmod).
First thing would be to generate a system dump (a dump of all the files in the /system partition). Hopefully we then could generate a custom recovery to flash on the phone, and then custom roms, either base on the dump you provide or other roms from other files. Contact me on twitter @adumont (say it's for Flipout) and I'll guide you to generate the dump!
Looking forward to do great things for that litle phone!

I'm in touch with adlxdum to give him my dump but I think we should start a separated thread like "Custom rom, modding (work in progress)" so that we can follow adlxdum work.
And...thx in advance ;-)

flusshd said:
You use App2Card.apk at below for app2sd without flash:
http://www.tinhte.vn/f280/app2card-2-4-4-20-9-cai-dat-ung-dung-len-nho-phan-vung-456586/
Requires: just a rooted phone
Steps:
- install app
- click Menu / Partition button then use slide bars to create ext2 for your sd card if it hasn't been splited yet
- click Install App2card button
- phone will be rebooted and you just taste app on sd after then
Note: above page has further instruction but it is vietnamese, you must use google translate to get it. This app runs perfectly on my Milestone.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Worked!
I couldn't repartition the SD card with the program, so I had to partition it myself. But once that was done, thing seem to work well. A bit slower...
I'm not totally sure how to use the app. Internal seems to still be full, but ext2 on the SD is quite empty. I can't seem to be able to tell if an app is installed to internal or external.
I have to try and install some more apps to see if I run out of memory.
Thanks!!

I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.

MrShides said:
I'm guessing the flipout and charm are almost identical phones?
My wife has a charm and i'm one of those "i'm not a developer, but I'd like to help" guys.
Click to expand...
Click to collapse
Yes, I think they are very similar.
One thing that I'm interested in is the accelerometer. On the Flipout, most apps that use it are twisted - for example wikitude, and many games (labyrinth lite works!) I wonder if things work on the charm...

the charm has the same issue.

MrShides said:
the charm has the same issue.
Click to expand...
Click to collapse
thanks! Too bad....

Hi ghostwheel
I've tried installing app2card, but I'm having some problems. I got the new version 2.7.2.
As you said, the partition doesnt work. For me it says sd card is full but its empty...
How did you manually partition it?
I've found some tutorials but it was for other phones and they required a custom rom...

I partitioned the card using a linux computer, with the program fdisk.
I allocated 2GB to a partition of type ext2. But, I think there are many alternatives for partitioning a disk, see this page:
http://androidcommunity.com/forums/f9/how-to-create-ext2-partition-14232/

Wow great link! Many different options! Will try this as soon as I get a micro sd card adapter. Thanks!
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
I just started using this phone and I'm almost running out of memory... this is quite annoying!

longlife_01 said:
You mentioned in your old post that you were having problems using app2card, That you weren't sure if it was working. Have you been able to use it since? Is it working well? and if not have you found an alternative?
!
Click to expand...
Click to collapse
Yes, I was having problems. Mainly when restarting the phone, sometimes oodles of apps don't work, including launcher pro, and app2card. You have to remember that when the phone reboots and seems to have FC problems, don't chose any home screen as the default, in case it crashes, and keep a spare app2card to reinstall on the sdcard. I think "severe" problems I had only twice, or so.
So, I have almost no problems. Most of the time it works really well. So well, in fact, that I'm a bit afraid to upgrade it, in case something breaks. And, I totally forgot what it is like to have to delete apps to install another one.
I have more of the opposite problem - finding an app among all those installed takes a realllly long time if you forgot its name. Apps organizer helps.

hello, i am new and i have flipout to test in poland orange network, i just root him using 1st post in this forum, great job! thanks

OK, I am having some problems with the current version of app2card. As I said, sometimes when I turn the device off and back on, app2card fails, and many apps give a FC which starting. Then one needs to fix the apps from app2card. It seems that once that is done, some apps lose some of their data. So, for example, droidwall (excellent program!!), lost all firewall data. I'll have to check if newer versions of app2card don't have this problem. It doesn't happen very often.

Instructions to root Flipout
Hi - I'd consider myself a newbie regarding rooting. I just got the AT&T Flipout - I really like the form factor. I just tried running the Universal Androot from my phone but got the security warning message about only being able to install from trusted sources.
Can someone point me in the right direction please?
Many thanks!

it says that with a lot of apps installed like that, including gmote that I downloaded from the developers site. Just look at what you're downloading like you would on any machine

go to settings > Application and tick on unknown sources to be able to install it.

Eris Dual Boot ROM

I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.

man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.

i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/

I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started

KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?

I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android

When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide

heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.

unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.

s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less

KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App

App location on SD card

Question...
I moved a lot of applications to my SD Card. The problem is that it seems to move every app off of the root directory which makes for a messy SD Card directory structure.
Is there no way to move the apps to a directory called /apps or something like that??

Milkman00 said:
Question...
I moved a lot of applications to my SD Card. The problem is that it seems to move every app off of the root directory which makes for a messy SD Card directory structure.
Is there no way to move the apps to a directory called /apps or something like that??
Click to expand...
Click to collapse
It should move it to sdcard/data/app/

Whosdaman said:
It should move it to sdcard/data/app/
Click to expand...
Click to collapse
I have a few files in my root directory starting with . (like .android_secure, .dataviz, .downloadTemp, etc.), and also having some start with com., and others that are regular applications.
In my apps/data directory there is only like one app... I don't get why this is so messy?

Milkman00 said:
I have a few files in my root directory starting with . (like .android_secure, .dataviz, .downloadTemp, etc.), and also having some start with com., and others that are regular applications.
In my apps/data directory there is only like one app... I don't get why this is so messy?
Click to expand...
Click to collapse
any directory starting with a "." is a hidden directory and thus should not be accessed by the user. just let android handle the directories and return to stock as you wont have any issues if you are using an ext4 with journaling turned off. EXT4 sucks data loss and fc all the time after a few days unless you allways reinstall your rom everyday i usually do.... i decided to use one rom for a few days and then i get those stupid errors.

dzuchowski said:
any directory starting with a "." is a hidden directory and thus should not be accessed by the user. just let android handle the directories and return to stock as you wont have any issues if you are using an ext4 with journaling turned off. EXT4 sucks data loss and fc all the time after a few days unless you allways reinstall your rom everyday i usually do.... i decided to use one rom for a few days and then i get those stupid errors.
Click to expand...
Click to collapse
You state these problems with EXT4 as if they are standalone facts. They are not.
I have had none of the problems you refer to with EXT4, and have benn enjoying this technology since Bonsai 3.0.0 on DK28. I do not experience any issues compared to RFS, do not have to reinstall my ROM, etc. I am a very happy user of EB13-based Bonsai 3.0.1.
The only issues I've had have been generic EB13 problems-- Bluetooth connectivity, audio routing after disconnecting BT A2DP, and some problems with apps moved to SD via Titanium Backup that were not available to be moved via the standard method in Manage Applications.
With many thousands of people using EXT4 via Bonsai, ACS, and all the other bleeding-edge ROMs, and the lack of problems for most --perhaps 95% or better -- the issue is obviously something YOU'RE doing, not the EXT4 technology.
I know that isn't helpful to you, and I sincerely have sympathy. I hope the community can help you, and others, figure out the cause of your difficulties.
Regardless, it is not helpful, nor does it contribute to the community, to spread false information. It's true that for you and a handful of people that EXT4 is problematic; it is not true that EXT4 if some sort of risky feature that should be avoided.
Rather, EXT4 is a solid, very useful step forward in technology with major advantages. No one here should fear using it any more than any of the other mods they're willing to risk beyond using the official stock software.
Sent from my mind using telepathitalk

[IDEA] Implement Firerat's Custom MTD Partition for HD2

Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .

cure for ORD....
I DON'T THINK SO.
Flashed from my fingers to your face

On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face

raven_raven said:
Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .
Click to expand...
Click to collapse
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.

malybru said:
On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face
Click to expand...
Click to collapse
Tried cLK, but it can't change partitions as you would like it to, you can't change it on the go without PC.
zach.antre said:
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.
Click to expand...
Click to collapse
A1: No, it is not possible. Firerat is genius and he does masterpiece of scripting, those scripts are 100% safe. It will of course break you ROM, but simple nandroid backup/flashing a new ROM will fix it.
A2: We resize /system, /data and /cache. You simply put two values in text files, i.e.:
Code:
mtd 130 2
First number is how many mb you want to spend on /system, second on /cache. Rest of internal memory is used by /data. /boot and /recovery are not touched by this script.
A3: I don't know for sure, just connected it to Haykuro SPL, which also changed partitions back then.
A4: Don't know for sure, I'm simply intermediate in this stuff, just wanted to pass an idea, I don't have required knowledge and experience to make this idea come true.
I know that there are 2 bootloaders, but I don't know how they work and how far you can modify partitions from recovery by using each of them. HD2 obviously isn't a native Android phone and regarding that either this idea may be impossible to implement or has to be completely redesigned. I really don't know .
Just wanted to pass an idea, but I'm terribly dissapointed how little response I received...

Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App

zach.antre said:
Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...

raven_raven said:
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...
Click to expand...
Click to collapse
Yeah i did, don't worry about it.
I have read the original thread, i have compared the different devices mount points (as much i could) and conclude that is the same.
What i have also noticed is that kernel must be patch in order for this script to work and the script checks for a specific bootloader? I'm not sure, i need to restudy that thread.
Anyway, I tried using the script but didn't happen anything.
I formated all partitions except /boot and /recovery
I first created the mtdpartmap.txt in SD root and flashed via CWM the script FR-recovery-v1.5.8-CustomMTD_S.zip
Then reboot and again to recovery
Flashed ROM and then flashed FR-boot-v1.5.8-CustomMTD_S.zip
Reboot to ROM worked fine.
I run terminal
#df
Sizes where the same as before

Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?

raven_raven said:
Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?
Click to expand...
Click to collapse
Well, I guess Firerat need to come by and post a thread in HD2 Dev forum since it is his work.
He could ask what info he needs for the HD2 such as partition layout and filesystem in each partition etc... I am sure many people are willing to help with that.
I also think that SPL is locking the partition tables (not sure) and the way we are flashing just overcome that. Else when i used the script should have f**cked up my partitioning.
You can ask an HD2 moderator to move this thread but first ask for Firerat permission.