PDA

View Full Version : Read everyfing i can find on Bigstorage and still no success


garethsimpsonuk
23rd January 2006, 04:55 PM
Hi I know the big storage hack is plastered all over this forum but i still cant get it right.Some one please help me!
Ive got a magician with rom version 1.13.00 WWE radio v. 1.12.00 (i used to have 1.12.00 but i upgraded it by accident.<I woz finkin of it anyway>)
I fink Ive tried every procedure possible but always have problems but basically this is what ive done:
1.Using OS image tool ive copied my rom to pc.
2.Ive changed the 80 00 00 thingy to b8 01.
3.Ive tried to use the os image tool to write it back t ppc but it comes with a usb/communication error in programme A.Im using this way because I have only 32mb mmc card.

Any help would be much appreciated,
Thanks

oltp
23rd January 2006, 06:40 PM
Try the wiki (top right link on the page) & go to the magician section. It contains a description howto patch a shipped-rom, the one you used to upgrade to 1.13WWE, & get BS. Apperently you missed this method.

Cheers, M

garethsimpsonuk
23rd January 2006, 08:16 PM
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,

Gareth

garethsimpsonuk
23rd January 2006, 08:34 PM
I already have all of them files.Wen I patch it the size goes right up then 'programme a' doesnt copy it over becuase its too big.it has 2 b excactly 32 i fink and after i patch it the size changes.
My main problem is getting the rom over 2 the magician.Since I dont have a card the only 2 ways i can fink are using osimage tool or program a, both of these im having problems with.I have roms that i have patched and changed the 416 bytes to my roms.I have roms that were patched and ive changed to my roms.I have roms made using byte copy.I just cant get any of them over!!
Thanks 4 ure help,

Gareth

oltp
23rd January 2006, 08:52 PM
Stop,

You're going in the wrong direction. The BS from shipped-rom method is about patching the provider supplied exe file. & after the patch you run it like a regular rom-upgrade. No SD or MMC involved!!! It's a rom-update via USB like the normal update.

pls read it once again @ the wiki.

garethsimpsonuk
24th January 2006, 12:50 PM
ok thanks im trying that now.Im stuck on getting nbfdec to run.Ive extracted it to the unzipped rom folder.I open ms-dos command prompt and drag and drop the .exe on the command line to save typing the path.The program runs but then it crashes.Can anyone help me?

oltp
24th January 2006, 01:16 PM
Try putting everything in "C:\BS" saves a lot of typing errors including filename handling.

garethsimpsonuk
24th January 2006, 04:10 PM
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks

oltp
24th January 2006, 05:02 PM
Ive done that now but I dont know how to execute the command.Do you think you could type the whole command for me?When I open command prompt it says this c:\documents and settings\rod simpson\> ive tryped typing in that command but i dont know how to put it in with the path etc.
Sorry for going on and on I cant get my head round it!
Thanks

Hi Rod,

To go to C:\BS from your personal doc&settings type on the commandline:
cd \ [Enter]
now you should be in C:\
then type:
cd bs [Enter]
now you should be in C:\BS

Works for other directories too.

Cheers, M

garethsimpsonuk
24th January 2006, 07:10 PM
Thanks, that helped me a lot.Ive done everything els now so I converted it back to nbf and then executed the maupgrade_noid.It checked device info then displayed the rom to and from screen and both were blank.I proceeded and it displayed the 'success' screen but nothing had actually happened on the ppc.Ive tried the other upgrade program and the one thats cracked on the site.
Any help would be much appreciated
Thanks

oltp
24th January 2006, 07:40 PM
Did you reset after the update process finished? & if so did it boot normally? & if so did you look at the internal storage folder size? Cause that's the only thing that's changed & the ext-rom has disappeared. Oh & you shouldn't see the customization start after a hard-reset...

btw rom to & from shouldn't be blank, pls run the update program without patch cause I think the editing somehow invalidated the shipped-rom. The original upgrade program should work & if so you know what's going on. If the original program fails there might be something with your device.

So start the plain shipped-rom first to find out..

garethsimpsonuk
25th January 2006, 10:48 AM
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8

garethsimpsonuk
25th January 2006, 10:54 AM
Thankyou!Its worked!!
I went from scratch and downloaded all the files again.This time i didnt put my own header in the file because i thought thats where i'm going wrong.My devicedata.txt file looked like gibberish to me and it wouldnt copy and paste in to hex editor.So i just left it.I changed the 2 values in the code, converted it and flashed it.Will not having my header cause problems?My storage is now 26.72mb is that right?
Thankyou very much oltp for your help.It's much appreciated.
I think this site is long overdue a donation from me.
Cheers m8

oltp
25th January 2006, 11:46 AM
The header contains info about romtype & provider name, probably some things more I'm
not sure about. The reason for changing it is to avoid errors like the country id error. With the use of maupgradeut_noid it's less important.
One thing I'm questioning is the reason why some of us have probs with connecting to the, I believe, special O2 services. Some claim there not able to connect anymore... Can some other setting as well. I'm on T-Mobile & everything works fine.

Basically if the upgrade was succesfull, you have an enlarged storage & the rest of your device will be working as before.

Cheers, M

shivam
2nd February 2006, 05:35 PM
how much space would i have in my main memory now? i have a 64+64 system (O2 Xda Mini) now branded to T-Mobile 1.33 and now applied the new patch (BIG STORAGE) using the Wiki Information guides. However any idea how much FREE space on first reboot i should have.

shivam
2nd February 2006, 05:49 PM
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?

shivam
2nd February 2006, 05:52 PM
nevermind got it :)

Total Main Memory - (FREE MEMORY) - 43.99MB Storage / 25.54 MB Programs! woo hoo this is HOT

oltp
2nd February 2006, 06:35 PM
did the first reboot...(soft reboot) after flash...its been 3 mins and just the T-Mobile Screen..how lng should i wait before i "think" its a bad flash?
First boot takes much more time than next boots.

Have fun, M

bartgomes
4th February 2006, 01:52 PM
all,

look over here (http://www.imateforum.com/forums/showthread.php?t=141).


cheers!

oltp
4th February 2006, 02:50 PM
Sorry to say, but it's old news. We got a thread about it for three months now I guess with that method. Problem is you always need to update first & then dump your rom again. & somehow not all dumps are accurate. The brick change with a SD is larger than with a shipped-rom.

M