Related
NOTE
This is my first cooking, feel free to try it out.
Eventhough I've been testing it and the results are good, conditions still apply: Use this at your own risk :!:
Explanation
This version of ROM is basically a Sin.Merged.v2.0 ROM cooked with xda2jojo/toenailed's extended_rom compression method.
And the result is a fully automatic ROM upgrade which can be done within your XDA II, no PC needed (except when flashing).
The Difference
Sin.Merged.v2.0 :
- Manual ROM merging using ActiveSync (you need to use your PC).
- Extended_rom installed manually using either Sprite BackUp or run it one by one.
Xda2.HERY.mod :
- Automatic ROM merging (no PC needed) continued with automatic extended_rom installation.
- All done automatically following the hard reset after flashing.
Ingredients
ROM = Sin.Merged.v2.0.
Cab files = collected from Sin.Merged.v2.0's collection.
Extended_rom = compressed by xda2jojo/toenailed (using CrunchIt).
Methods
There are 3 ways to take you there.
No matter which method you choose, the end result will be the same.
Method A/B/C How To:
Download the Xda2.HERY.mod.A/B/C.exe
Flash your XDA II by running the downloaded file.
You'll be asked to perform a hard reset after that.
Soon xBackup will automatically start after a while.
Tap "Restore" tab, tick "All Data", open Storage (not Storage Card) and tap Start.
Then wait until it finished, and tap "YES" when it ask for a restart.
Then it will start installing automatically.
Don't bother with the debug pop-up window.
At the end, you'll be asked to choose your provider.
At this point, you HAVE TO choose one then tap "X".
Coz if you don't, it won't restart, and it will ruin the whole process.
If you don't, even another hard reset won't help since the config files in extended_rom has been changed.
Method A/B/C CAUTION :
Whatever you do, DO NOT tap or do anything during the whole process.
You are only allowed to tap "YES" or "OK" everytime.
During the process, NEVER tap anything unless you're asked to (including tapping the Start button).
Changes are made inside the extended_rom during the process.
After everything finish, I've created a file to reverse those changes back to its previous state (before the hard reset).
Therefore when you need to do another hard reset, the files inside extended_rom will be exactly the same as before.
So it is VERY IMPORTANT for you NOT TO interrupt the process except tapping "YES" or "OK" when it asked.
I have tested this method and the result is flawless, but always bear in mind: "Do this at your own risk".
Method A:
Xda2.HERY.mod.A.exe
Method A README.txt
ADVANTAGE :
The benefit of this method is you'll have plenty space in your extended_rom.
The free space can be used to put the cab files that you always reinstall after every hard reset.
DISADVANTAGE :
The downfall of this method is you won't be able to see the compressed cab files.
They will be automatically deleted after the process.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Open config2.txt.
- Add the name of you cab file(s) in the FIRST line, I repeat, ... FIRST line.
- Example, if you want to add a file named "sample.cab", then insert this in the first line, CAB: \Extended_ROM\sample.cab
- Save and close the config2.txt.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Just in case if you want to see the compressed cab files, just run the ExtROM.exe file in your extended_rom and choose a
folder to extract (if your extended_rom is hidden, Unhide it first).
You don't have to run Unlock the extended_rom to run the ExtROM.exe, just keep it in locked state.
Method B:
Xda2.HERY.mod.B.exe
Method B README.txt
There will be a short delay before xBackup showed up.
Just be patient because a quite large CompactFlashBackUpNew file is being extracted and copied to the Storage folder.
ADVANTAGE :
The benefit of this method is you'll have plenty space in your extended_rom.
The free space can be used to put the cab files that you always reinstall after every hard reset.
DISADVANTAGE :
The downfall of this method is you won't be able to see the compressed cab files.
Because everything has been backed up in a backup file (CompactFlashBackUpNew), which will be automatically deleted after
the process.
Eventhough there's plenty of free space to put extra cab files, with this method, you have to install the added cab files
manually from inside extended_rom.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Run it.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Method C:
Xda2.HERY.mod.C.exe
Method C README.txt
ADVANTAGE :
The benefit of this method is you'll be abe to see all the installed cab files.
DISADVANTAGE :
The downfall of this method is you won't have much free space left in your extended_rom.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Open config2.txt.
- Add the name of you cab file(s) in the line.
- Example, if you want to add a file named "sample.cab", then insert this line, CAB: \Extended_ROM\sample.cab
- Save and close the config2.txt.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Just in case if you want to see the compressed cab files, just run the ExtROM.exe file in your extended_rom and choose a
folder to extract (if your extended_rom is hidden, Unhide it first).
You don't have to run Unlock the extended_rom to run the ExtROM.exe, just keep it in locked state.
Millions of Thanks to :
Sin for:
- the Backup.stg file of ROM 2.02.t1WWE.
- all the cab files.
- the genius discovery of merging between ROMs.
xda2ojo & toenailed for:
- the XdA2JoJo[1].v3.0.1t.cab file.
- the CrunchIt.exe file.
- the brilliant idea of compressing extended_rom files.
In conclusion, you guys are simply THE BEST !!!
using the xbackup... :lol:
xda2jojo said:
using the xbackup... :lol:
Click to expand...
Click to collapse
Yes, Jojo, all three methods using xBackup.
But I believe you refer to method B.
For method B, the tricky part is, to make it all run in one step.
As we know, after a ROM flash, all will be back to standard.
I've already put the CompactFlashBackupNew file in the extended rom, which will be auto copied to the Storage folder, ready to be xBackup-ed.
After xBackup complete, you'll be asked to do a reset.
Then, where's the auto config part?
After the xBackup reset, you're suppose to MANUALLY go to Start, Programs, Communication, AutoConfig.
And to clear things up, you have to MANUALLY delete the CompactFlashBackupNew file in the Storage folder.
Plus for safety reason, just in case you accidentally change files in the extended rom, you have to Lock and Hide it, ... once again, ... MANUALLY.
Here's the tricky part, you don't have to do all those things manually.
Everything will be automatic following the hard reset after ROM flashing.
After the xBackup reset, you'll be brought automatically to the AutoConfig, which will bring you to another final reset.
After that, ... voila, you're done.
And the CompactFlashBackupNew file in the Storage folder will be automatically gone, plus your extended rom will also be automatically locked and hidden (you can always unlock or unhide it with the pre-installed Extended ROM Tools).
So no need for you to do step 2, 3, etc.
Only 1 step, and it'll take you to straight to the finish line.
So does the other methods, all in 1 step.
Can anybody tell me the passwords for these files? I want to use them on a german t-mobile device.
Thanks
Password?
What do you mean?
I didn't put any password.
Is it the password to open/run the file or to download the file?
The Password to change the country ID. I need a password if I want to change it in ER2003 Edit.
Or are there any other ways to do it?
Thanks Herry
For ur rom!!!
VIVA O2XDAID !!!
bravo hery go go go hihihi
Hopefully it works, Phreak.
Mengesankan herry.
Halo kepada teman saya di Bali.
Bagaimana membicarakannya benang merah ini menggunakan indo bahasa?
:wink:
Hey, I didn't know that you can speak Indonesian, Jojo.
If you find it hard to say it in indonesian, then just do it in english.
Surely most of indonesian gadgeters speaks english.
hch_111 said:
Hey, I didn't know that you can speak Indonesian, Jojo.
If you find it hard to say it in indonesian, then just do it in english.
Surely most of indonesian gadgeters speaks english.
Click to expand...
Click to collapse
hahaha...
How about this...
''If you find it hard to say in ENGLISH, then just do it in INDON.
Surely SOME(hehehe...some of my friend) of indonesian gadgeters HARDLY speaks in english''.
Yo! my friend.... :wink:
is it Indonesian EXT-Rom only?
It's nice to know our gadgeter (indonesian) can improve the extended room for XDA. i hope we can make better one in next day.
but i've some question for u herry.
1. This rom is only for indonesian user?
2. wht's content in this rom? is it same like the xda2jojo's rom?
3. Any freatures are good in urs rom?
Just inform to you, i'm also cooking my extended room for indonesian only. but i'm not a programer. so it'll take long time.. he he.. i hope we can combine with the others.
btw.. where do u life? tinggal dimana pak?
for XDA2Jojo, i think i must learn from u so much more, buddy. would u teach me about cooking? ya... maybe about some philipine's cooking? ok, thank's b4..
Salut!
Iya donk, gadgeteer Indo jgn kalah...
Tapi kayaknya cara kamu ribet deh. Pake XBackup lagi... PELAAAAN nya ga tahan. Bisa mandi dulu, makan dulu & blm selesai juga. :x
Gue sendiri pake Sin Merged tapi ext romnya gue ganti dgn file2 sendiri kecuali Sin Merged v2.0.cab. Khususnya carrier files hanya gue tinggalin yg gue pake aja. Lagi tunggu Win2K5 nih... kayaknya the great Buzz baru saja release full 128 RAM.
Anyway, keep contributing! 8) 8)
Re: is it Indonesian EXT-Rom only?
moeya said:
It's nice to know our gadgeter (indonesian) can improve the extended room for XDA. i hope we can make better one in next day.
but i've some question for u herry.
1. This rom is only for indonesian user?
2. wht's content in this rom? is it same like the xda2jojo's rom?
3. Any freatures are good in urs rom?
Just inform to you, i'm also cooking my extended room for indonesian only. but i'm not a programer. so it'll take long time.. he he.. i hope we can combine with the others.
btw.. where do u life? tinggal dimana pak?
for XDA2Jojo, i think i must learn from u so much more, buddy. would u teach me about cooking? ya... maybe about some philipine's cooking? ok, thank's b4..
Click to expand...
Click to collapse
Sorry for the late reply.
Allow me to answer the Q's:
1. Actually the only thing that make this one feels like Indonesian ROM is the AutoConfig cab files, which consist 3 Indonesian provider.
For other countries have to search or find the suitable cab file(s).
The rest (other than AutoConfig stuff) are all universal use.
2. Nope, the same thing about JoJo's version is the cooking method (using the compressed ext_rom). It's more alike to Sin.Merged.v2.0's version.
3. The good feature in this ROM is the ability to do it all automatically.
Thank you, hope it explains.
See ya again, friend.
MMS setting for mentari subscriber
can anyone with working mms setting using mentari card, plase post their setting in here.
i tried to set mine but still won't connect to the server / mms won't send.
already went to mentari shop, but still won't work. the step by step they used is for 1.60 rom, i think not for the 2003se version.
so, once again anyone with working mms setting for mentari, please help me.
tks.
Hi there, flashed the rom on my XDA II using method C, was wondering if I got it correct. Whenever I soft reseted my PDA, there will be a prompt from PHM reset for me to reset the phone shortly after load up, as you can see it will be an endless loop if I did not choose "NO" when prompt to reset the phone on startup. Will like to know if this is normal ir did I do something wrong during the process.
Thanks in advance
naoki1980 said:
Hi there, flashed the rom on my XDA II using method C, was wondering if I got it correct. Whenever I soft reseted my PDA, there will be a prompt from PHM reset for me to reset the phone shortly after load up, as you can see it will be an endless loop if I did not choose "NO" when prompt to reset the phone on startup. Will like to know if this is normal ir did I do something wrong during the process.
Thanks in advance
Click to expand...
Click to collapse
Can you tell me what files you have in \Windows\StartUp?
Hery
What is the content of the file 'CompactFlashBackUpNew'?
Is it important
Did you actually notice a difference between merged and non-merged performance (with exactly same extended-rom)?
:!: :?: :roll:
llbasha said:
Hery
What is the content of the file 'CompactFlashBackUpNew'?
Is it important
Did you actually notice a difference between merged and non-merged performance (with exactly same extended-rom)?
:!: :?: :roll:
Click to expand...
Click to collapse
Yes, it is very important.
It contains all the extended ROM that listed in the other methods.
Like I said, all three methods ended up with same results.
Nope, I didn't try to put the extended ROM in merged and non-merged.
Since this already concluded by Mr. Sin that merged one is better than non-merged one, therefore I just use the merged one instead of the non-merged one.
Thanks.
Greetings,
Here is a simple step-by-step method for taking a virgin Hermes to HardSP-V7 and fully upgraded radio and ROM of choice. This method is especially usefull for those on Vista and Mac machines, it's also somewhat safer and MUCH faster than using RUU to flash your device. From initial download to completely upgrade device took me about an hour, all done before my first phone call.
This is intended for those who HAVE READ the Wiki and the forums, but don't know what to do first, and for those who don't want to use the old-school USB cable methods. All of this is simply gathered info from other posts and guides written by people much more clever than I, and is IN NO WAY meant to be a substitute for reading the Wiki and the forums. I spent days reading everything on this site and so should you. If you jump into something you don't understand and brick your phone, it's not my fault.
FROM BOX TO ROCKS SD-CARD UPDATE GUIDE
[1.]Read the WIKI and as many forum threads as you can, at the very least read all of the stickies.
[2.]Start by gathering all of the files you will need in one place for easy access. For bookeeping purposes I recommend that you put each one in it's own folder. You will need:
Hard-SP-V7
Radio Upgrade- XDA-Dev has a great list of extracted radio ROMS here, I use 1.43.00.00
ROM of Choice (I used Shaps WWE 3.0C, he's got a lot other languages for this ROM as well, chck the thread)
[3.]Use WinRar to open each of the compressed files you downloaded, in each one there should be TWO files, take the filed called "RUU_signed.nbh" and extract it to the same folder. Be sure not to get these mixed up as they all have the same file name, hence the individual folders.
[4.]Use a card reader or your laptop's SD slot to format an SD card, make sure you select FAT32. After formatting do a disk check and select the "fix errors" option.
[5.]IF your SD is healthy, move the unzipped "RUU_signed.nbh" file from the Hard-SP-V7 folder to the root of the SD card.
[6.]Turn on your phone and put the SD card in.
[7.]AFTER transferring the file and putting the SD in your phone, use the phones file explorer to change the name of the "RUU_signed.nbh" file to hermimg.nbh (be sure not to add a superfluous .nbh when you do this, DO NOT change the .nbh extension..ever). The flash is much more reliable when you change the name ON THE PHONE, I have no idea why, but when i do it this way it works everytime.
[8.]After changing the filename and exiting the file manager you'll need to enter the bootloader. To do so, simultaneously press the left-side OK key, the power button, and use the stylus to press the reset button on the bottom of the phone. This open the bootloader, the screen will go white and say "loading," then it will ask you to press the power button to confirm the upgrade, do so.
[9.]About one second later you get confirmation and have flashed Hard-SP-V7
, your phone is now pseudo-SuperCid and much more resistant to bricking. Do a soft reset to exit bootloader by pressing the reset button on the bottom of the phone.
[10.]Pop out the SD and put it back in the card reader and delete the "hermimg.nbh." Now on your PC navigate to the folder where you extracted the radio upgrade, copy the unzipped 'RUU_signed.nbh" file to your SD card, put it back in the phone, and use the phones File manager to change the name to HERMIMG.NBH.
[11.] Repeat step 8. The radio upgrade is the slowest, and takes about 5 minutes, it may appear to hang, but don't worry, the progress bar is a bit jumpy, everything should be OK.
[12.] You have now upgraded the Radio, confirm by checking the radio version in the System INFO tab of the setting menu.
[13.] You guessed it, delete "hermimg.nbh" from the card, replace it with the extracted "RUU_signed.nbh" from the ROM version zip you downloaded, put the SD in the phone, change the name to HERMIMG.nbh, and enter the bootloader VIA method in step 8.
[14.] Congratulations, you have now upgraded the SPL, the radio, and flashed a new ROM, all without installing drivers, using cables, running .exe's or anything else, all in about an hour.
[15.] Follow onscreen instructions to set up the phone.
[16.] pop out the SD and delete the .nbh file, otherwise it will try and flash your phone next time you enter the bootloader.
[17.] Load your new phone with Apps and enjoy!
MANY, MANY thanks to all who make this place what it is, too many to mention. Sites like this one are examples of how the Internet has changed the world forever. I'll be making a full tutorial with screenshots and better instruction over the next day or so and will put it in the WIKI.
Very nice writeup Mlalahoi.
Coud have used this i was a flash virgin
Props to you.
Thanks Charon
unable to install Hard-SPL-V7
Hi
I done all the steps you mentioned but i am still unable to install the Hard-SPL-V7.
After copying hermimg.nbh to card and going to boot loader it shows loading ... and then again comes back to boot loader without installing the Hard-SPL.
Please advise....
Thanks,
Malik
Format card FAT32, hermimg.nbh must be how its spelled...
1. you will need No2chem's basekit 5048.
2. you need DCD's kitchen 2.3.1
Then the fun part....
Go into No2Chem's OEM/OEMDrivers directory and copy the OEM_FLASHDRV.DLL folder.
Paste it into DCDs kitchen OEM/OEMDrivers directory.
Then go to DCDs ROM/XIP directory and edit the boot.rgu file.
Add these lines to the bottom of the boot.rgu file.
*******************************************************************
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV]
"DefaultFileSystem"="FATFS"
"Name"=""
"PartitionDriver"=""
"MountHidden"=dword:0
"Folder"="Extended_ROM"
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV\FATFS]
"FormatTFAT"=dword:1
"EnableWriteBack"=dword:1
"EnableCache"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV]
"DriverPath"="Drivers\\BuiltIn\\EXT_FLASHDRV"
"LoadFlags"=dword:1
"Order"=dword:12
"Bootphase"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\EXT_FLASHDRV]
"Profile"="EXT_FLASHDRV"
"Index"= dword:1
"Dll"="OEM_FLASHDRV.dll"
"Prefix"="DSK"
"Order"=dword:13
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
*******************************************************************
Then get the no2chem_nueExtROM package and put it into the DCD OEM directory.
BUILD - BURN - ENJOY!!!
P.S. Thanks No2chem and DCD for the awesome work!!!!!!!!!!!!!!!!!!!!
P.P.S. There might be an easier way but this worked for me.
Extended Frustration
Is there a purpose for having the Extended Rom? With older devices you were able to unlock the extended rom and use it like an internal memory card but afaik there is no way to unlock the extended rom, right?
gimpdog said:
Is there a purpose for having the Extended Rom? With older devices you were able to unlock the extended rom and use it like an internal memory card but afaik there is no way to unlock the extended rom, right?
Click to expand...
Click to collapse
With No2Chems nueEXTROM you can unlock and write to the Titan extended ROM. Just like the 6700.
http://www.weienterprises.com/nue/
How much space is in the ExtRom?
Slightly less than 10MB
thanks dude...i've been working on a custom rom for myself and no i can include this....whooottttttt
so is this like another 10mb to put things onto, or 10mb for programs to use?
Is the extrom cleared with a hard reset? If not, it could be cool to store CABs in there to reinstall your programs after flashing. Isn't this what happens when the Sprint customization runs?
Shiva1 said:
Is the extrom cleared with a hard reset? If not, it could be cool to store CABs in there to reinstall your programs after flashing. Isn't this what happens when the Sprint customization runs?
Click to expand...
Click to collapse
its like having a 10mb sd card inyour phone, it doesnt get cleared unless you run a stock rom ruu or delete files from it. nice to have in case you have to hard reset out on the road, you can get all your cabs installed without an sd card
The EXTRom is copied from ROM during a hard reset. So anything you put in there will get erased and copied over from the ROM. There should be a way to create a .nb for the ExtROM and flash your device with it to pre-populate the cab's you want in there tho.
jrebeiro said:
The EXTRom is copied from ROM during a hard reset. So anything you put in there will get erased and copied over from the ROM. There should be a way to create a .nb for the ExtROM and flash your device with it to pre-populate the cab's you want in there tho.
Click to expand...
Click to collapse
hmm. thats not how it worked on the apache. a hard reset just touches the os rom, not the extended rom. otherwise it would erase the carrier info and programs on a hard reset... that would defeat the purpose of it.
hello, I followed the guide exactly and was successfully able to unlock the extrom and erase /write to it, but i now have Extrom and Extrom2 in the file explorer. they are both the same 9mb memory allocation ( i wrote files to both,, different files, and soft reset. Both drives ended up showing the 2nd file i wrote to whichever extrom, so they are the same drive. anyone have any ideas how to correct this?
fallingup said:
hmm. thats not how it worked on the apache. a hard reset just touches the os rom, not the extended rom. otherwise it would erase the carrier info and programs on a hard reset... that would defeat the purpose of it.
Click to expand...
Click to collapse
Ummm... no it restores the OS and Extended Partitions. Your carrier info is not located in the Ext ROM it's located in .provxml files in the OS. Customization programs are located in Ext ROM and during a hard reset are restored.
You also basically just retyped what I explained in my post. The Carrier provided files in the Ext ROM are restored during a hard reset. But anything you have put in there by unlocking the Ext ROM and making it read/write will be gone after a hard reset.
Feel free to try it yourself.
fallingup said:
its like having a 10mb sd card inyour phone, it doesnt get cleared unless you run a stock rom ruu or delete files from it. nice to have in case you have to hard reset out on the road, you can get all your cabs installed without an sd card
Click to expand...
Click to collapse
After reading some of these posts I wanted to clear a few things up but then I noticed Fallingup had it exactly correct!!!!
Only two ways to wipe your extended rom...
1. unlock it and erase it yourself OR
2. Install a custom .nbh file specifically designed to over right the extended rom.
If you uncompress an OEM rom.exe file you will probably find thee .nbh files.
1. is for the rom itself (like what DCD and No2chem put together)
2. is the Radio!
3. Contents of the extended rom.
Since we our content directly to the rom through OEM packages it is unnecessary to have cabs there for a custom rom install. Therefore, no one wastes there time building custom .nbh files to write to the extended rom. ALSO, if you have it unlocked, when you build your custom OEM packages, you can specifically target the extended rom just like you target the windows directory. NOTE: this last bit is for completeness all that is really needed is an emphatic statement... The Extended rom DOES survive a hard reset AND it survives a CUSTOM rom install as well. (unless you build a custom .nbh file to write to it)
atomclock said:
After reading some of these posts I wanted to clear a few things up but then I noticed Fallingup had it exactly correct!!!!
Only two ways to wipe your extended rom...
1. unlock it and erase it yourself OR
2. Install a custom .nbh file specifically designed to over right the extended rom.
If you uncompress an OEM rom.exe file you will probably find thee .nbh files.
1. is for the rom itself (like what DCD and No2chem put together)
2. is the Radio!
3. Contents of the extended rom.
Since we our content directly to the rom through OEM packages it is unnecessary to have cabs there for a custom rom install. Therefore, no one wastes there time building custom .nbh files to write to the extended rom. ALSO, if you have it unlocked, when you build your custom OEM packages, you can specifically target the extended rom just like you target the windows directory. NOTE: this last bit is for completeness all that is really needed is an emphatic statement... The Extended rom DOES survive a hard reset AND it survives a CUSTOM rom install as well. (unless you build a custom .nbh file to write to it)
Click to expand...
Click to collapse
theres actually a third way, which is when the xip specifies to format the extended_rom partition, which would cause your extended rom to be empty on boot, even if you wrote to it during a flash.
also, you don't need to download the entire basekit, i posted the necessary files to insert to oem on my website. also, stroths has developed a cab so you don't have to install it to rom.
jarmenti said:
hello, I followed the guide exactly and was successfully able to unlock the extrom and erase /write to it, but i now have Extrom and Extrom2 in the file explorer. they are both the same 9mb memory allocation ( i wrote files to both,, different files, and soft reset. Both drives ended up showing the 2nd file i wrote to whichever extrom, so they are the same drive. anyone have any ideas how to correct this?
Click to expand...
Click to collapse
I am getting the same results here. Something is duplicating.
no2chem said:
theres actually a third way, which is when the xip specifies to format the extended_rom partition, which would cause your extended rom to be empty on boot, even if you wrote to it during a flash.
also, you don't need to download the entire basekit, i posted the necessary files to insert to oem on my website. also, stroths has developed a cab so you don't have to install it to rom.
Click to expand...
Click to collapse
Do we still need to modify the file in XIP. Because I tried your files (not from basekit) and I added the code from 1st post. I ended up with 2 ExtRoms. both duplicates.
Help
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
irus said:
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
Click to expand...
Click to collapse
You could try using a provxml file operation instead? Not sure if initflashfiles generally is happy about copying from a removable storage device such as the sd slot (just a guess), since in your Athena it is a fixed disk it may behave differently??
Another thing you could try is to do the copy operation as a stage of the customization process, use an xml file in there?? Perhaps the SD bus driver is not loaded until after initflashfiles has completed since really it has to run that before alot of other operations on first boot?
irus said:
or anyone who knows the answer... lol
Ok so here is my problem....
everytime my phone starts it copies over the following files to the root of my storage card "pim.vol, eT9Cdb.Cdb, eT9Rudb.Rdb" so when i do a hard reset i put into the initflashfiles.dat
Directory("\"):-File("pim.vol","\storage card\pim.vol")
Directory("\Windows"):-File("eT9Rudb.Rdb","\storage card\eT9Rudb.Rdb")
Directory("\Windows"):-File("eT9Cdb.Cdb","\storage card\eT9Cdb.Cdb")
I also tried, as a test to copy them to my documents and that also did not work. Now the rom still loads and it does not freeze during first boot, if you were thinking that i did not delete the first two bytes. it just does not copy them from the storage card to the device i had it setup like this on my x7500 and it worked perfectly so im not sure what the problem is. Any thoughts ?
thanks for looking
Click to expand...
Click to collapse
I'd use CPY1/CPY2 in a UC script
Code:
CPY1:\storage card\pim.vol
CPY2:\pim.vol
CPY1:\storage card\eT9Rudb.Rdb
CPY2:\Windows\eT9Rudb.Rdb
CPY1:\storage card\eT9Cdb.Cdb
CPY2:\Windows\eT9Cdb.Cdb
mrvanx said:
You could try using a provxml file operation instead? Not sure if initflashfiles generally is happy about copying from a removable storage device such as the sd slot (just a guess), since in your Athena it is a fixed disk it may behave differently??
Another thing you could try is to do the copy operation as a stage of the customization process, use an xml file in there?? Perhaps the SD bus driver is not loaded until after initflashfiles has completed since really it has to run that before alot of other operations on first boot?
Click to expand...
Click to collapse
i will try this if all else fails but i would like it to be from the initflashfiles.dat but what you say makes sense.... thanks
andret said:
I'd use CPY1/CPY2 in a UC script
Code:
CPY1:\storage card\pim.vol
CPY2:\pim.vol
CPY1:\storage card\eT9Rudb.Rdb
CPY2:\Windows\eT9Rudb.Rdb
CPY1:\storage card\eT9Cdb.Cdb
CPY2:\Windows\eT9Cdb.Cdb
Click to expand...
Click to collapse
i thought about doing this but i read somewhere that sdautorun does not like spaces in the files path.... thanks for the info
ok so i tried using the cpy1/cpy2 and it actully worked however it did not copy over the pim.vol so i tried to copy it over manually and it let me but after i did that i could no longer press on contacts, calender, or get to the phone pad any thoughts?
I think you'll probably need to close down any process actively using the pim database before copying it over, it's probably open when you're overwriting it and getting corrupted..
Da_G said:
I think you'll probably need to close down any process actively using the pim database before copying it over, it's probably open when you're overwriting it and getting corrupted..
Click to expand...
Click to collapse
i changed the reg values to my documents then changed them back, i am kindof thinking that htc may have set this up a little differently on the TP which is why i am having so much trouble but thats is only my guess
ok so im thinking part of the problem is that the pim.vol file is working with some other file for contacts, here is why: i copied the pim.vol file from my rom renamed it pim.vol_ put it into my rom and flashed it, of course i put Directory("\Windows"):-File("pim.vol","\Windows\pim.vol_") into the initflashfiles.dat file and still not contacts. so i have no idea why this does not work any thoughts. thanks
If your rom supports this it is VERY COOL!!
http://forum.xda-developers.com/showthread.php?t=496809
NGGeekZ said:
If your rom supports this it is VERY COOL!!
http://forum.xda-developers.com/showthread.php?t=496809
Click to expand...
Click to collapse
I have been using UC and provxml for autorun on new flashes for some time and it is the only way to go, but takes a little time to get it right. Not everything is possible using this however, but most everything is there. I have all of my Roms and Radios on a non-SDHC card, with all of the cabs on there too with SDconfig.txt. I move a copy of some nbh file from a folder onto the root, and flash from bootloader on the phone. Then I move the next thing until my custom rom which runs customizations based on my sdconfig.txt. I have all of my Cabs in a folder, including a cab that has all of my UC regedits, file copies, and other personalizations such as outlook settings, program hacks, and everything else. Every time I have a new favorite program, I add that cab to my cabs folder and add a regedit to my personlization cab. When I flash next, my phone is 98% where it was before. I can usually have a stock phone to totally modded out within 30 minutes.
Problematic areas that don't really work when loading SDconfig.txt: HTC Home pictures and contacts, some preferences for windows settings, and some other unique problems.
I can help you understand how to work this out, if anyone is interested. It really is worth the time if you flash a lot. See my screenshot of my sd card I use for flashing. I also uploaded my sdconfig.txt. I won't put my cab on here as there are personal information but I will share information if you need help that will be relevant.