Related
I recently tried to flash my US T-Moble Phone Edition with the SER 1.1. Since my model number was different then the rom I couldn't use the Program A method and had to use the ROM Image Tool. The tool worked great for downloading my old backup ROM off of my card... but every time I tried to write the new SER 1.1 to the card, it gave a can't open physical device error???
After much interigation on these forums and my setup... I downloaded to source to try to see if the mistake was simple. After fixing several typos which prevented it from compiling (not sure why the source link points to something that wouldn't compile) if found a funcitonal typo which was causeing the problem.
In the call to the WriteImage function in RawDiskDlg.cpp the device index is was specified by 'dip->Id', this is not the actual index of the device and should be 'dip->index' as in the ReadImage calls.
After this fix, I was able to recompile and use the app to put the rom on my flash... then upgrade my Tmobile and everything seems to work perfect (thanks guys).
I really do appeciate the work you guys are doing... and can't wait till 2003 comes out!!!
- T.J.
I dont suppose there is any chance that you could send me the recompiled file so that I could try it.
Many thanks BORIS
Or to me too
We would greatly appreciate it!!!
Here's a link to the exe...
http://givemebeer.com:8080/warez/XDA/xdarit.exe
Which is latest version of bootloader in JAM??. Is there any version higher than 1.0??. Please submit...
i have 1.02
Due to some issues happened during big storage mod I have restore my phone from other old JAM backup. I think before that my boot loader is also 1.02 But now it is 1.0 . I did the d2s with 80000 0400000 full backup. Will it overwrite bootloader??. Can I upgrade my bootloader in anyway? Please help....
Do we have any advantages with latest version boot loader?? What difference we will have with the each versions??
SD Flashing can change your bootloader .. if you really want to change back your bootloader .. just use your old SD backup (the first/original SD backup that you made) then flash it to your device.. if you dont have it already you can change your bootloader using
itsme's PNEWBOOTLOADER.exe , the tool can upgrade bootloader of WALLABY, HIMALAYA and MAGICIAN .. tnx itsme for creating this tool ..
the only difference i see with different bootloader is during flashing .. some bootloader have some problem in flashing .. like in HIMALAYA .. 0.23 cant flash radio ROM using SD backup , 0.26b cant flash Extended_ROM in nbf, all version below 1.03 .. have this problem that sometimes it cant flash using a nbf(himaupgradeut.exe) and need to make a sd flashing..
Anyway my point is if u didnt find any problem using your current bootloader, i suggest to stay with that but if you do then thats the time that i can only suggest to change your bootloader .. anyway changing your bootloader can fry your device ..
-toe
To use pnewbootloader tool where can I get the rom file of the new bootloader version??
heres bootloader 1.02
15:03:32 Jan 24 2005
1.02 version: 1.38
3d1b0f86b5f1774c32982611b813abbb <- m not sure with md5 (pls itsme correct me if m wrong .. )
i dont have a magician so i didnt try it and i cannot guarantee that this is a correct bootloader
PS. This bootloader is for Magician and not for anyother device, i will not take responsibility for any thing that will cause for a brick device due for using of this bootloader .. please be very careful .. i already once killed my device due to bootloader ..
-toe
SD Flashing
Hi toenailed,
What's SD Flashing?
thanks
Toenailed:
could u be so kind to tell me what i'm doing wrong, i'm trying to upgrade / or maybe should i say fix my bootloader, when I do a pmemdump 80000000 00040000 I get little stuff, mostly it's blank.. (*uh oh*) I'm sure this is not the way it should be. I tried using it'sme pnewbootloader, and got an error
"Unable to find flash info offset, cannot disable bootloader writeprotect"
this is what i typed:
Code:
C:\exp\1\build>pnewbootloader.exe -f -o 80000000 -l 00040000 c:\flashboot.bin\BL1.02-1.38.nb0
Unable to find flash info offset, cannot disable bootloader writeprotect
also tried the simple
Code:
pnewbootloader.exe BL1.02-1.3.28.nb0
I'll post my setup in a bit, i'm trying to re-flash my devices SHIPPED roms, hopefully that will restore things.. (crosses his fingers) anyways what I think I did is erased the GSM bootloader, thus I cannot use my phone at all, the close i get to using my phone is getting to WinMobile.. anyways this is really not a problem thus I called my carrier and they are going to ship me a new one.. I just wanted to known for sake of knowledge and if someone else has the same problem.. also just incase i do it again with my new phone, doubt my carrier will fall for the "I pulled out my battery, and now my device is dead" lol heck i even think I erased my ESN and PRL out of my device, since I get N/A when i'm in Mobile..
[/b]
it means that i did not add code for your specific rom version to pnewbootloader.
what is the OS version you are using?
willem
Oh sorry about that: it'sme, (btw thanks for ur great tools, and website, full of resources). currently I just upgraded to the PDA2k_WWE one, that was just posted recently here is the info...
ROM VERSION: 1.40.00 WWE
ROM Date: 03/10/05
Radio Version: [blank]
Protocol Version: [blank]
ExtROM version: 1.40.176 WWE
but the ORIGINAL one that came with this device is:
I'm not sure if the info below is correct so I also provided the actual full filename of my update..
HA_VZW_13500_115_01140_WOC.exe
MODEL ID: PH20A3
ROM VERSION: 1.35.00
ROM DATE: not sure, since i don't have it installed atm
Radio Version: DM FAIL
Protocol Version: DM FAIL
ExtROM Version: 1.15
also do u happen to know how to bypass the NOT ALLOW UPDATE when using a SD card? I tried to do a radio dump first. but i get Radio stack fail (tm). also i think i messed aroud with some of the rroute rrouter settings, could u possibly tell me what the default/correct settings might be?
thanks lots..
oh yea, and also using xdatools, when I try to use them, It either says that my image is to big, or it says it's to small, or it says cannot connect to USB using Programme a
thanks again..
itsme said:
it means that i did not add code for your specific rom version to pnewbootloader.
what is the OS version you are using?
willem
Click to expand...
Click to collapse
Hello "itsme"... I have a little question to you...
It's posible to use 'pnewbootloader.exe' to flash any OS ROM offset using the '-o' and '-l' parameters?
Thanks :wink:
Hello toenailed / itsme..
Before I'm trying to change my bootloader to the 1.02 (and it can be a disaster some times) what are my advantages with a newer bootloader like 1.02 from 1.00. Now I'm sure before the SD flash restore from another JAM mine was 1.02. Do I have (with 1.02) a higher performance or bugfree or more support to hardware device? I have also notice one thing after this change to 1.00. Some time after soft-reset I will a "Unidentified USB device error" and it will prompt for correct USB driver and bluetooth will not work for sometime. But after 5 mins it will start working. This problem will not occur if I'm removing the main battery for a soft-reset.
Is this issue could be with bootloader version? Other than the OS booting and loading what else bootloader doooo??
zxvf: i don't think you are talking about a magician rom.
the 'not allow update' means that you restore a backup made with a different bootloader version. .... or that the sdcard contains an invalid signature.
MKS: in theory, yes, but for several locations in the ROM, the protection needs to be removed.
the protection is a list of values which specify where the non-flashable area of rom starts and ends.
pnewbootloader temporarily changes these non-flashable area's to something not in the ROM.
nishadks: there is no real need to upgrade your bootloader, it is more useful, to downgrade, since older bootloaders, usually have less protections built in.
Thanks a lot itsme for your help....
Itsme:
You are correct, I didn't pay attention to it being a bootloader for the magician, (eventhough it's bolded lol) anyways, I tried it ones again, with a rom that I KNOW is the same that I had, because before messing around with it, I made a backup with two different tools osupdate.exe and bootblaster.exe (the one from handhelds.org for unix flashing). So i have this files both as .bin files, but can't seem to use the l command AT ALL eventhough I have both of the passwords, (actually don't really know how to use mtty.exe) I can't get the concept on how u send the files.. because it timesout and says something like "the second computer timed out.." or something like that, it seems that I need to start some type of send transfer something similar like (tx, and rx) in unix.. but not really sure how to do this with mtty.exe, or do i actually need to have a serial cable, is it not possible with the cradle that came with the device? I was actually thinking on creating a cable since, I got a USB to Serial converter... so maybe that will work.. but havn't had much time to mess around with that...
I also tried every possible version that u said is supported in ur .cpp file and none will actually work with my device, they all just make my device screan white and it starts fading out to black, (or sometimes it starts with a diff color.)
so what should I do/try to get pnewbootloader.exe to work? or is there any software that I can use in Win mobile (on the pda) to just run it locally?
Cheers, and thanks again...
how to use pnewbootloader
hi mate would u plz like to to tell me how can i install b0otloader 1.02 on my magician. i hav tried to use pnewbootloader but cant find any help abt it how to use it. i hav 2 magicians 1 hav bootloader 1.02 and other 1.0.
the problem is i cant read my high speed sd card on magician with bootloader 1.0. but it works on magician with bootloader 1.02 both hav same versions of roms. i hav extracted my bootloader from newer one but dont know how to copy it on old 1.
if possible than email me on
[email protected]
thanks
bl*.nb
Please someone where I can download any version of the bootloader. I can not download on the link in post number 7
thanks, and sorry for my google translate.
same for me, page goes blank, and download never starts
All,
I own an MwG (formerly ubiquio) 501 and eventually started looking for software updates for it. The device is mostly ditto to the imate JAQ3, so I proceeded as follows:
1- get a WM6.1 ROM for JAQ3 (as linked in a thread of this very forum)
2- try to flash it (fail)
3- disassemble the ROM with tools from chinese website (osnbtool.exe)
4- port XIP merging with the ROM of my own device (thanks to the wonderful manual full xip porting thread!)
5- insert my original IMGFS of SYS and OEM
6- success!
the current situation is (settings -> about)
CE OS 5.2.20269 (Build 17936.0.3.0)
The performance boost obtained by upgrading the XIP is significant (keyboard is usable and video playback is ~ 15fps @ full screen), but I would like to perform more optimizations (e.g. switch to .NET CF 3.5) but as soon as I start to work with the dumped SYS and OEM I have troubles, it seems that every kitchen is expecting to work on the XIP (or on .nb and .nb.payload) but such files are not compatible with the one I get from osbntool.exe (but the dump folder is).
Do someone have advice on how to proceed? I would like to either
1-find a kitchen that works with my device
2-go for manual cooking
For 2 I achieved to split the dumped folder to packages and removed some of them, then - as far as I understood - I would need Greloc (got it) and bepe's buildos.exe (nowere to be found )
Is someone willing to help me? Thanks a lot.
Rest assured I am going to share the obtained ROM (I am already willing to share the current one, of course, just drop me a line!)
Best,
DAniele
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
thanks i will try....
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Not working
indresh88 said:
oh!!!!! it takes a long time as Compaed to earvius kitchen.....also i am not able to flash .nbh file it stops at 1% in ruu and then device restarts.......
Click to expand...
Click to collapse
same here...the final ROM when flashed says image corrupt
Same here all the rom file made by sjkv0.8 gives unflashable rom.
Something might be broken then. I changed the executable last minute. What size is the NBH you are all producing?
ivan the output nbh size is ok it seems for a lite rom it produces about 56mb and remember the one nbh u provided for testing is also having prob it says its corrupt.
help me...SJK won't cook
i cannot make it work...
i get an error while cooking about some files (ringtones) not able to be copied and then hangs.
i tried it on Windows7 and it says that the some payload.nb file is not found in temp folder.
gui-wise/appearance wise...this is the best kitchen ever!!
can someone please tell me where i went wrong? i download four files from the SJK website: ext package, sys package, opal package and the SJK package and extracted to the same folder.
Update:
v0.8.1 - Fixed unflashable ROM bug
Thanks ivan now finally i can use sjk v0.8 (now 0.8.1) after using sjk 7 for so long time.
v0.8.2
Fixed LZX
still gives an error...
ivanmmj said:
v0.8.2
Fixed LZX
Click to expand...
Click to collapse
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
+1 Exactly same result since v8 and above
freelancer81 said:
last night, i cooked 3-4 times using different settings, compression, rom version but it still gives a flash write error for me
cooking works fine except for some errors regarding some *.wma ringtone files inside SYS/PhoneRedist folder not being able to be copied (i overcame them by deleting)
flashing goes upto 100% (i used RUU via the usb cable) but the device reboots and goes to tri-color screen and says Rom Code Error.
btw...do i have to re-download every thing (SYS, EXT, *device_specific*) and the SJK_0.*.* or just the single SJK_0.*.* file?????
Click to expand...
Click to collapse
No, if you already had the *_0.8 for all the files, just download the SJK_0.8.3. If you didn't have anything, download EVERY file that's not device specific and your device's file.
You're getting a flash write error?
Still error
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
freelancer81 said:
what might be the problem????
flashing goes upto 100%, device reboots and goes to tri-color screen
and displays a "ROM CODE ERROR".
i tried all compression methods including UPX on EXT packages but same problem.
Click to expand...
Click to collapse
I think I know what happened. Please hold while I work with airxtreme to fix it.
gooooddddyyyy....i am looking forward to it!!!
Try this:
http://justkitchen.info/main/rokdownloads/SJK_0.8.5.7z
Please let me know ASAP if it works.
thank you for your promptness...i will surely try and let you know.
freelancer81 said:
thank you for your promptness...i will surely try and let you know.
Click to expand...
Click to collapse
Did you ever get a chance to try it out?
Good staff
I have already installed several androids and they all happen and then install it works fine until the restart after that never get put to work again!
What am I to fail!
Help please!!
HTC HD2
★ |Artemis HD2 ROM Family Ver 35.0 Gen III | ★
ROM date: 17.09.2010
Radio version: 2.14.50.04
HSPL2: 1.66HSPL
Protocol version: 15.42.50.09U
Manila version: v2.5.20191914.0
WinMO: WM 6.5.5 Professional COM5 Build 23578
Android:● SEVERAL
Wow. If I understand you correctly, this has been SOOOOO covered in this forum.
The HD2 does not BOOT to Android unless you have set up a special program that STILL loads Windows Mobile first and then boots to Android.
You always have to run CLRCAD and HARET from your Android folder on your SD card, EVERYTIME you reboot. There are programs that automate this if you do a SEARCH.
J
Thanks for your response
I always do the same, and similarly, that is the way you have mentioned!
But it only works once after turning off or renice do the same and already works if you delete and re-paste it all makes work on sd!
U have several android builds ................ duh................... each folder is on the root of your SD card so Windows doesn't know which build to load since each build has an Android name on it. Rename each folder and its startup text to match it.
If its not that then I'm not sure what your talking about.
I think its your radio version, your using 2.14.xxxxx but you should only use up to 2.12.xxxxx see the following thread.
http://forum.xda-developers.com/showthread.php?t=732380