Related
Project Description
This is a project to port the Droid version of CyanogenMod to the milestone. While the Droid and Milestone devices are twins, they are CDMA and GSM respectively. Hacks include not flashing the boot image provided by the CM Droid package and some GSM configurations.
Status
CyanogenMod 6 RC1 (with CoburnROM hacks) will flash successfully, however it will refuse to boot (possibly due to incompatible stock kernel or that the milestone doesn't like unsigned ROMs). So far, flashing works from koush's ClockWorkMod Recovery and Open Recovery 1.14. When rebooted, the device hangs on the M Boot logo.
Downloads
PoC/RC #1: Download from my blog, Geek In The Family - 75MB.
What you can do
Pretty much this ROM is currently a playground, if you want to have a poke around, download a copy of the above versions of the ROM and extract it, and then poke around and see what makes it tick.
Other notes
Space saved for future use.
Cheers!
Reserved for future use
Sent from my Milestone using XDA App
Good luck man, I really hope this happens
You should check with the guys on and-developers.com, and their IRC channel #milestone-modding on Freenode for any progress on the bootloader
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
kholk said:
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Click to expand...
Click to collapse
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Good luck to you. I commend you for your efforts.
After 1 year waiting for the bootloader to be hacked...I am slightly skeptical. However, now that the Droid X has been released to the masses with the same locked bootloader, we might get some fresh eyes to look into this matter.
I would be happy enough with a custom kernel running on 2nd boot ;-)
SenseUI Mod
Hello, You might try using the mot_boot_mode file, which is also used with the SenseUI Port for the Milestone, I guess that would make this boot too? If I'm right, this is the boot sequence:
This is what I'm talking about:
"the ramdisk is located in /system/ramdisk.tar folder, it all starts here.
the ramdisk is opened by /system/bin/mot_boot_mode."
You should download the SenseUI Mod and analyse it's way of booting.
Good luck!
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
the problem is not about being negative but you are facing it the wrong way .
the problem here is to hack the thing not to port an already existing mod .
Once the bootloader is bypassed they ll be hundreds of real ROMS .
Anybody can pretend at porting there own roms it is completely IRRELEVANT since it wont be possible until its hacked.
you said it 'even if I have to wait ' well there you go do like thousands of others and just wait . BUt please dont pretend at anything else , thank you .
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
So you're not going with that 2ndboot method?
In any case, my eyes are glued to your twitter account
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
dude your my hero
It's kinda off-topic, but I just thought, why don't we go 4chan style on Motorola, and, for example, black fax local Motorola offices or something?
Coburn64 said:
My my, that's negative. I do know about the custom kernel via kexec/2ndboot trick.
Nothing is impossible to be hacked, it's a matter of time and blood, sweat and tears. As Paul from MoDaCo stated, nothing is impenetrable.
I'll get this ROM booting, even if I have to wait a year or two before the Boot loader is hacked or a proper method is working.
Click to expand...
Click to collapse
As I said, it IS possible to skip the BL checks, and it's fully hackable...but...I know.... you don't want to resolder your OMAP....
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
why not work together dexter? i think this may help out in particular cases
Dexter_nlb said:
if this mod is "Droid" based, you need to make many modifications to the startup..
the Droid is in no way protected, where Milestone has GSM radio protected, and specific drivers required to open it, which for now only opens when using the original "init" process of a milestone.. the "init" from droid disables radio completely..
but take a look on how i got the senseui port running.. i got the froyo partly running the same way, so im sure my solution used in senseui mod will help you along to make it work...it just requires some debugging and "adb logcat" so you at least can see what happens at startup..
Click to expand...
Click to collapse
DO YOU HAVE FroYo running!?!?!?!??!?!?!?!?
Coburn64 said:
I am actually porting the ROM to the Milestone, in case if you're concerned that I'm lying. Check my twitter for progress reports.
@Mikevhl we may have a hope if we try that! Thanks for the recommendation!
Also, kexec is working. However, instead of rebooting Android with the Droid CM6 Kernel, it just reboots the phone instead. I'm working on a possible fix for that, thank Kiljacken for compiling the kexec module.
Click to expand...
Click to collapse
I never said you were lying all I said was dont pretend ' about rom ' when even a basic kernel wont run .
if you have a workin kexec would you mind sharing it ?
I'm very interested in your work since it seems that we will never see an official 2.2 from Motorola... I don't know if we are going to have the new update, here in France (2.1 update 2).
Well, I just have a question. On a french forum, someone posted a method to downgrade the ROM of the Milestone by implementing the right version of the bootloader in it, I don't know if I very clear. This member had some major problems with the 2.1 update so he decided to downgrade to 2.0.1. However he wasn't able to do it because his Milestone was using the 90.78 bootloader while the 2.0.1 rom was using the 90.73 bootloader. Eventulally, he managed to install the 2.0.1 rom on his Milestone by putting the 90.78 bootloader in the 2.0.1 rom.
So my question is : will it be possible put a bootloader in a custom rom in order to make it boot on the Milestone ?
(I would give you the link for the topic on the french forum once my account si verified)
kholk said:
Hacking the bootloader is impossibile on our Milestone, the TI OMAP chipset runs in High Security mode and for switching to General Purpose mode you have to desolder and resolder the OMAP chipset on your mainboard, soldering the right pins for enabling the GP mode.
Anyway, 2ndboot can make us able to boot a different kernel (for now GSM modem is unusable, so we can't use the phone with the new?y booted kernel) and this is the way that we'll take on the Milestone for using a custom kernel.
No custom ROMs. Or at least not this way.
We'll NEVER be able to boot this ROM.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Actually this is a wrong assumption. HS chip cannot be turned to a Generag purpose.
For those who are interested, here is kexec.
Devs should know the drill, insmod kexec.ko etc etc.
Originally made by Kiljacken (compilation, etc), shared by me.
As for the Android 2.0.1 on Boot Loader 97.73, he may have just made a custom update zip that nukes the system partition and installs 2.0.1 on the device.
Also, I updated my Boot Loader to 90.78ch, which is the XT702 Boot Loader - no bricks. Yet.
Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. If you have problems uninstall everything and start from Step 4 again. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead
US Owners - If you flash the UK firmware, you will lose 3g and wifi calling app etc... There are fixes for this problem that can be found on other Forums. A guide on how to restore this which has worked for others is HERE
##WARNING: be careful when flashing 2.51 firmware, firstly its patched so root isn't achievable by the usual methods, and isn't easy to downgrade back to other firmware - I suggest you search and read the various topics on it. My advice is to use 2.21 UK or 2.34 Deblur firmware##
This guide will show you how to debrand your Motorola Defy (Eg bought on T-Mobile UK and want generic UK firmware), or indeed restore the phone if you brick (Eg removing important apps that you shouldn’t have touched!!)
Props go to jutley (Modaco)for his debranding guide for the flipout, and dkspook (Modaco) for his information in other threads, and anyone else who thinks they may have contributed, oh yeah and my Mum.
##Disconnect phone from PC##
STEP 1 Download usb drivers here below
Motorola Drivers Here
STEP 2 Download the debranded Firmware here (To debrand to generic UK I used the one marked UK - choose the one for your country)
Choose Firmware Here
STEP 3 Download RSDLite - I used v4.9, I found earlier versions would not work. Get it here.
RSDLite 4.9 Here
STEP 4 Install the USB Drivers and the RSDLite program and reboot PC
STEP 5 Extract the firmware file you downloaded a while ago. Then copy the .sbf firmware file to c:\Program files\Motorola\RSDLite folder (installation directory for RDSLite). this should come out as JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_S
rvice1FF.sbf for the UK one.
STEP 6 Start the RSDLite program now where it says filename press the select button and find the .sbf firmware file in c:\Program files\Motorola\RSDLite (it should default to this folder) and select the (sbf) file some details will appear on the right hand side.
STEP 7 We now need to boot the phone into the bootloader (as above make sure the phone is disconnected from USB – not sure if matters tho!). Hold the volume up and then power the phone on, after about 5 seconds release the buttons and the bootloader should display - it will show the version and a battery check. Now plug in the USB cable and it should install the drivers . Once the driver installation has finished you should see the phone appear at the bottom of the RSDLite program window under `port 1` - Once this is there you are ready to flash the firmware. NB: I had issues getting it to show a number of times. Uninstalling RSDLite/Drivers, rebooting PC, and then reinstalling these resolved this issue.
STEP 8 Press the start button on the RSDLite and just relax while your device gets flashed,debranded etc. you will see a progress status on the right hand side wait till it reaches 100% but please do not disconect it will reboot the phone automaticly and restart the phone.And just wait untill android comes up and fully running untill you disconnect it should read (PLEASE START PHONE MANUALY) on RSDLite when this shows it is safe to unplug.
Hopefully now you will have a debranded/unbricked phone.
One thing I noticed that was cool is that the data partition stayed intact for me when I debranded, meaning all my settings and installed app (providing you hadn’t moved stuff to /system) were still there after the process – cool! The only thing you will have to do is re-root the device.
Hope you find this useful and I look forward to a great community for the Defy!
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
nitewalkergr said:
Nice job! This worked perfectly. We now just need the tmo us FW. I'm kind of iffy about messing with my phone much more until I have a failsafe.
Click to expand...
Click to collapse
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
If a tmo us user flashes with the uk FW they lose 3g.
A tmo us or just generic us fw would give us the clean sweep option while keeping our 3g.
Can I use the Uk Firm for a Vodafone Spain Defy??
Higgsy said:
Whats the benefit of the T-Mobile US Firmware - some kind of extra functionality? If we could get it, we could flash by this method and flash back if we didn't like it anyways I suppose.
In theory this method is a failsafe tho because if you mess any thing up you can get back to a different firmware. I must say I personally would like to get my hands on the original T-Mobile UK .sbf, just in case I wanted to put it back to its original state for returns/repair, so if anyone has found it (I haven't yet) please let me know.
Click to expand...
Click to collapse
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
pedrogamo said:
Can I use the Uk Firm for a Vodafone Spain Defy??
Click to expand...
Click to collapse
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Cesar Pipes said:
Yes, I have a simfree defy, and this is my versión. Same version for France, UK, Spain, etc
Click to expand...
Click to collapse
Thanks!! I did it. Now my Defy is debranded. Bye Vodafone!
dj_destruction said:
Hi Higgsy, long time no see! Guess its cos you sold your Hero/G2 Touch so you have no need to visit htcdevscene, Its dead there now a days lol. I just got my Defy from T-Mobile UK. I here your after the T-Mobile UK Defy firmware? and I havent rooted or touched the firmware on mine at all, all i've done is charged it up and used as my day to day phone. If you know of a way to pull the firmware from the phone i will gladly upload it for you, if its even possible?
P.s. still got my Hero/G2 Touch not sure if i wanna sell the lil work horse yet lol, what are they selling for these days?
Click to expand...
Click to collapse
Now then DJD!
Na we need the .sbf file for it but it no biggy at the moment. Get it rooted mate - easiest way is to download z4root from the market - works a treat and roots in like 10 secs lol.
Stopped going on htcdevscene for a number of reasons, firstly i could never get on the site and secondly i felt the way it was run was very inconsistent.
Just sold my Hero - they are going for between 80-120 on ebay the top end is for brand new boxed. I have just sold mine to a mobile recycle place for £103. This phone is different gravy to the hero for sure.
Anyway mate look forward to seeing you around again
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
milesg said:
Thanks for this guide Higgsy, very easy to follow even for a noob like me.
I have now said goodbye to Vodafone's crap a mere 20 minutes after opening the box with my shiny new DEFY in that was delivered today.
Click to expand...
Click to collapse
No probs - Gone be the dirty network custom apps and splash screens!!
Done too. Thank you.
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Higgsy what are the benefits of rooting and flashing the generic unbranded software apart from getting rid of the t-mobile rubbish?
tim440 said:
EDIT: Just reflashed and then calibrated the compass. Seems to be working now. Sorry for the unnecessary message.
Ok, having taken the phone out since I got rid of the Vodafone stuff, I've discovered that the GPS is no longer working. I've got GPS Test on it and it only sees one satellite where before it saw a load. I'm going to reload the firmware now, but does anyone have any ideas?
Click to expand...
Click to collapse
Hmm strange My GPS is fine, locks on in like 5 secs, maybe try rebooting with GPS switched on, if you haven't already done so.
DJD,
No real benefits apart from getting rid of any tmobile crap, there isn't much bloatware in the tmobile uk build anyways. I just like generic lol. And as for rooting - please tell me that question is joke surely as a seasoned veteran you know what that is geezer
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
dj_destruction said:
I know rooting opens up a world of goodies but there arent any goodies for this phone yet in the way of ROMS, at least thats what i can gather so far lol. Can it be over clocked and JITenabled yet? after rooting it of course, sorry im being lazy n not google-ing lol.
Plus for my totally blonde moment if i flash the generic uk firmware would it still mean i could get the over the air 2.2 update when it is released by motorola before t-mobile release their bloatware version?
Click to expand...
Click to collapse
JIT can be enabled - its not stable imo - I tried it before, gonna have a better look at it.
i would expect you will be able to get the generic 2.2 update, to be fair, I think we will be flashing roms by that time anyways
Anyway stop being a ***** and get it rooted
OI lol,
Just downloaded z4root will put it on my memory card n get root tomorrow me thinks.
p.s z4root is no longer on the market, found the z4root.apk in a thread on here tho luckily lol.
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
tim440 said:
Ok, now I do have a problem. I've flashed the non-branded rom and very happy with it, but my in-call speaker has failed this morning. This seems to be a common problem with the Defy and I suspect it needs replacing or repairing, but I need to put back the branded rom to have the phone in warranty, don't I? How do I even begin to go about that?
Click to expand...
Click to collapse
You can't unless you can find the vodafone .sbf sorry mate it was mentioned at the top of the post.
They probably wouldn't know anyway, just deny all knowledge if they say anything.
So, just for fun, I decided to check out motorolas update timetable to see if the full version of froyo was released for the motoroi. it was. bad news is, i cant read korean xD if anyone can read korean, and would be able to download the .zip or .sbf, PLEASE let me know how to, I would be more than happy to try it out as compared to this test version, please help me out guys, im sure more of you would like to use this over the test version for now.
Here is the link to the update table
https://supportforums.motorola.com/community/manager/softwareupgrades
here is the korean site that i do not understand
http://www.mymotorola.co.kr/product/PrdRsdMain.aspx#
thank you in advance
I don't understa.d korean either. Bastards.
Sent from my DROIDX using XDA App
i cant read korean and i dont know why but stupids created the web page with pictures!!! so we cant translate it with google translate either... if anyone can find a way to download it please share with us )
win pc and motoroi xt720 needed for download
hey there for download we need a win pc (i´m on mac) and a motoroi xt720
on first page ( http://www.mymotorola.co.kr/product/PrdRsdMain.aspx# ) click on start download green round button in middle
on popup orange click link "USB §§§$"§§" in new tab scroll to XT720 and press orange USB Button to download usb driver and install. exit tab via X in right down corner.
back in first popup window click the 2nd link (darkgrey box)
in popup check "checkbox lower right and then the "[$§$§]" darker symbols beside the checkbox on the right side to exept end user licence.
again back in first popup click dark Back "$%$$>" symbol lower right
now download the active x thing in middle (orange button) and install
now i´m stuck because of no active x but i think you have to activate the x link on top of page and then connect phone via USB ......????? (see little video on left side)
....
i already did all those steps browsers downloads the active x and another page appears and a girl says somethng in korean again
can someone maybe download and upload to a web site for the rest of us
yes can someone get the update for all of us
i try to do the update and it stop at 4% and i don't know that she say :S
i have the UK room on so i will try to pot the Korea room on my phone and try maybe it will work ...............
ok i have pot the Korea room 2.1 and it see my phone and it start to update now i am at 17 % it stop at 18 % and reboot to bootloder
...........
why dont they just publish the file easily?? making all that stupid steps, its just and update software...
amjad_2020 said:
i try to do the update and it stop at 4% and i don't know that she say :S
i have the UK room on so i will try to pot the Korea room on my phone and try maybe it will work ...............
ok i have pot the Korea room 2.1 and it see my phone and it start to update now i am at 17 % it stop at 18 % and reboot to bootloder
...........
Click to expand...
Click to collapse
Where did you get the Korean 2.1 ROM. Could you post a link. Im going to try those steps
The Motoroi link looks like the only live link left here
I think this froyo is same froyo
It looks same version..
default froyo
MOTOROI(XT720)
XT720 .STSKT_N_79.33.50R
This froyo
MOTOROI(XT720)
XT720 .STSKT_N_79.33.50R
It looks like same..
I think this froyo is same froyo....
This froyo version is
MOTOROI(XT720)
XT720 .STSKT_N_79.33.50R
default froyo version is
MOTOROI(XT720)
XT720 .STSKT_N_79.33.50R
.../..
It looks like same froyo...
Hi folks. I need to change my sig. My Korean SGS was destroyed and ended up with a korean Motoroi xt720 for cheap. I am in Korea. I can read a few computer terms and for anything else have easy access to people who can read more.
Anyway, I made it through the upgrade process. However, it didn't give me a rom file, rather it actually flashed the phone from the web page. There's a chance I can find the rom file somewhere on my hard drive.
I had to do it twice. The first time it seemed like it was installing some upgrade manager tool (but I was clicking ok pretty fast). There was a yes or no question that I didn't bother to try to translate any further even if I could. Yes allowed the continue button to pup up.. but then the computer rebooted. I did it again though and the second time after hitting the big orange button.. it rebooted the phone and flashed it.
Let me know if I can help with something, and let me know if you know of any big things to watch out for if I'm taking advice from the U.S/EU threads. Obviously, not using those ROMS is the main one.
By the way, rooting by adb with rageagainst the cage worked fine for me as expected.
update: so I checked the ahrd drive. The file isn't there. With a somewhat similar samsung process I sometimes had to kill the program just before it flashed, then I could find the file. Unfortunately, it won't do it again, because it detects that I'm already upgraded. Of course I can just tar up my /system directory.
appagom said:
Hi folks. I need to change my sig. My Korean SGS was destroyed and ended up with a korean Motoroi xt720 for cheap. I am in Korea. I can read a few computer terms and for anything else have easy access to people who can read more.
Anyway, I made it through the upgrade process. However, it didn't give me a rom file, rather it actually flashed the phone from the web page. There's a chance I can find the rom file somewhere on my hard drive.
I had to do it twice. The first time it seemed like it was installing some upgrade manager tool (but I was clicking ok pretty fast). There was a yes or no question that I didn't bother to try to translate any further even if I could. Yes allowed the continue button to pup up.. but then the computer rebooted. I did it again though and the second time after hitting the big orange button.. it rebooted the phone and flashed it.
Let me know if I can help with something, and let me know if you know of any big things to watch out for if I'm taking advice from the U.S/EU threads. Obviously, not using those ROMS is the main one.
By the way, rooting by adb with rageagainst the cage worked fine for me as expected.
update: so I checked the ahrd drive. The file isn't there. With a somewhat similar samsung process I sometimes had to kill the program just before it flashed, then I could find the file. Unfortunately, it won't do it again, because it detects that I'm already upgraded. Of course I can just tar up my /system directory.
Click to expand...
Click to collapse
Can you post your kernel version and configuration strings (S/W version etc)?
model XT720 (but korean one of course)
S/W version STSKT_N_79.33.50R
android version 2.2.1
kernel version 2.6.29-omap1
Did I miss anything?
I am capable of extracting and probably unpacking a kernel image, assuming it doesn't go too differently than for the Samsung. I would want hints on what block device to get it from though.
Another possibility is flashing back to an older rom, and trying to upgrade again, but I'd need to find an older rom. I wrote down my original ROM version somewhere, so I can try to search for it.
I'd actually like to have this too, because it's nice if I mess something up or need A/S, to have a clean ROM to fall back to.
appagom said:
model XT720 (but korean one of course)
S/W version STSKT_N_79.33.50R
android version 2.2.1
kernel version 2.6.29-omap1
Did I miss anything?
I am capable of extracting and probably unpacking a kernel image, assuming it doesn't go too differently than for the Samsung. I would want hints on what block device to get it from though.
Another possibility is flashing back to an older rom, and trying to upgrade again, but I'd need to find an older rom.
Click to expand...
Click to collapse
I think that's the same as what we have. You can download the sbf here: http://forum.xda-developers.com/showthread.php?t=881801 Thanks!
Ok thanks!
One thing you could try change your build prop to the motorio but this could be dangerous.
Sent from my XT720 using XDA Premium App
So it seems like we'll need to fight over at the Microsoft forums if we're to try to stay up-to-date. I need you to contribute to my post over at msdn here: http://forums.create.msdn.com/forums/p/78753/476964.aspx#476964
Maybe if enough of us hit'em, we can get some kind of answer. Dev phones should have been the first to be updated.
Still no updates for Taylor.
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
the92playboy said:
It says in the forums that you linked to that there will be no updates for the Samsung Taylor phones.
Click to expand...
Click to collapse
Seems like there won't be and update for LG Panthers either.
Anyone wanna trade for an Android device?
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
the92playboy said:
Might be a newb question here but....
Did people have to pay for these developer phones? Or did MS just send them out to registered/respected developers?
Click to expand...
Click to collapse
Yup, Microsoft just sent them out.
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
NevinM said:
day2die said:
I suppose, you can flash your phone with the Omnia 7/Quantum ROM at your own risk.
I would like to give th Quantum ROM a try , but I do not know where to start. I am a Bell user in Canada so I think they have the Quantum. I used to flash old WM and Android Devices all the time, but WP7 is new to me. Anyone have a thread or no if anyone has sucessfully flashed a LG Panther to anything else? I can get into a bootloader, but it is probably just Microsofts bootloader.
Click to expand...
Click to collapse
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
Useless guy said:
Looks like it's really possible, because i succesfully connected to the phone using QXDM, and even downloaded NAND's image (it's raw, so for extracting page size required, because size in the partition table is relative to page size). Though may flash it, i think bootloader will work. But you probably can get bricked device. Unfortunally i have no enough time for explorations.
Click to expand...
Click to collapse
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
fb401 said:
Useless guy said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
Goldcard isn't required. Only HTC devices require it.
I've dumped my ROM, so if bootloader will work (i hope), device can be easily flashed.
Is anyone wanna to try? QPST can flash certain partitions (looks like only dsp1 and efs are required for succesful update). Unfortunally i can't risk my phone, because i'm developing an application.
Click to expand...
Click to collapse
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
Not every got it free.
Me to...
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
the92playboy said:
Not being rude, but are people complaining that a phone that they received for free is not getting the update and not being continued? If you never paid anything for it in the first place, what are you out then?
Click to expand...
Click to collapse
I got mine off of eBay due to it being the best keyboard phone out at the time (the Quantum is a joke), so it wasn't free for me. Once we get a HTC 7 Pro here that's compatible with AT&T's 3G bands, I'll switch over to that.
NevinM said:
I am not sure if it is worthwhile attempting a flash. The problem is we are all developers and having no device is probably not worth the risk. I have not flashed anything WP7 so I am pretty hesitant. Is this the link to flashing info you guys are considering?
http://forum.xda-developers.com/showthread.php?t=935605
In reading the other threads, there is no real confirmation on the Panther not getting updated. It is clear the the Taylor will not. I am curious if we are running the exact ROM that another device is? If so, ROM from those devices may work. I am trying to remember what the download name was (was it Pacific or something?). I deleted the file. If I still had it I would consider giving flashing a try. I wish Microsoft had not shut down the microsoft connect site for these phones. Any thoughts?
Click to expand...
Click to collapse
I was thinking more the Europe Open Optimus 7 rom here: http://forum.xda-developers.com/showthread.php?t=935578
Like you said, I can't be without a device so I'm really hesitant to try flashing
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
dragoxt said:
Well there is going to be a point where and update or feature will make our phones aka gw910 or Taylor completely useless as for development or testing, so this is something to consider.
Yeah connect has been down since a long time ago I have been struggling to find the FW file provided in the msdn/connect/internet forums, I’m guessing the only way now is to contact either a developer/evangelist/god/msdn who has that file available in storage, with the firmware we can create our own updated custom FW way easier than creating one from scratch and/or experiment with other FW like the optimus 7/Q.
And idea can we consider spoofing the gw910 to an optimus 7/Q .7004 using the registry editor? Making ZUNE update just the components needed.
also im willing to give it a go flashing mi gw910 UsellesGuy any info on how can i dump mi firmware. and posible explanation as in how to recover.I read the bootloader post before but is there anything else i need ?
Click to expand...
Click to collapse
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Useless guy said:
Microsoft delivers updates using binary patches, they apply only to concrete file version, else they will be broken (or updating will be failed).
Thank you, but i think better way is to wait a bit, until situation about updates will clear up. If update will be not received - i'll begin my work
Click to expand...
Click to collapse
On twitter I've tired contacting @winphonesupport as far as our phones being updated. They replied: "Let us see if our team knows and we'll get back to you. ^EB"
I haven't gotten another answer back yet. I doubt I'll get one at all honestly.
quick question about updating a developer device
Hi
I'm a complete newby about wp7.
I've two Optimus 7 in my possession that seem to be developer devices.
Here the phones info:
OS Version: 6516Mainline
SW Version: LG-E900AT-00-V08d-ORG-UK-JUL-24-2010
HW Version: E
More info:
OS Version: 6516Mainline (buildlab).20100713-1228
Firmware revision number: 0.8.4.10
Hardware revision number: 0.1.5.0
Bootloader version: 1.4.1.0
Chip SOC version: 0.30.2.0
Now I've tried to update the firmware like in this post:
http://forum.xda-developers.com/showthread.php?t=935578
But it doesn't work (LGDP2 connect to phone start the update but give the error 1002)
Is there a way to flash these phones to be like normal phones? (I don't intent to develop on them) Or my hardware version is to old (prototype)
Thanks for the help
fb401 said:
I think flashing the unbranded Optimus 7 ROM would be the best bet for us. There is a registry key named "HasKeyboard" that's defaulted to 0 that we can change to 1. That might be the way to go. Also I'm wondering if we'd have to go the goldcard method to move over to a Quantum or Optimus rom.
The problem is I don't have another phone and there's no MTTY process to unbrick our phones so I'm a little hesitant to try.
Click to expand...
Click to collapse
so you are relying on a dev phone that MS was gracious enough to give you as your only device and are complaining that you didn't get the update???
edit: after reading your replies, this wasn't a publicly released phone, so if you don't get the updates, I don't feel you have a complaint.
Just got my G-Tablet off of WOOT and wanted to let everyone know that it shipped with version 1.1-3389. Just thought I would ease everyones mind around here.
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
The first thing mine did was update to 1.1-3588. I'm off to figure out how to get the Market on it.
roebeet said:
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
Click to expand...
Click to collapse
Well apparently there will be a second batch, which I guess mine will be a part of, so there is still a chance for 3991 to still be used.
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
I'm guessing they are all 3389 - I'm sure they work off the same image.
However, I'd check it anyway - better safe than sorry, imo.
Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
sigvader said:
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
Click to expand...
Click to collapse
If you see 3991 on your Woot tablet, please tell us immediately. I would very shocked at this point if that happened, but then again I didn't expect 3389 either. I really thought they were going to be 3588.
Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
One of the woot staffers gave an unofficial update the day after the purchasing ended and said that they were getting a rush shipment on Monday from the vendor to fulfill the second half of the orders. So they are physically a separate set from the first batch.
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
theroblog.com said:
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
Click to expand...
Click to collapse
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
received my tablet from woot today. ill post back as soon as its charged and powered up with the version.
roebeet said:
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
Click to expand...
Click to collapse
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
cbay said:
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
Click to expand...
Click to collapse
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
TNT Lite 5 was pulled after about a week, due to more than a few issues where users were soft bricking their devices. Going on metrics I tried to compile, the majority of the problems stemmed from the use of clockworkmod, thus my reasoning for not recommending its use anymore. This is despite the fact that the update it was based on was a non-released firmware. I will explain further. Btw, we are seeing similar issues over in the Notion Ink Adam forums in notioninkhacks.com, for the same exact reasons (clockworkmod).
In the case of the GTAB, the vendor (Viewsonic) adds the bootloader.bin to its stock update firmware. And it has been updated at least twice tmk - once in a November firmware update, once in a December firmware update. And also with this 3991 UAT update, but for the sake of argument we won't count that one. But they have updated it in released firmware.
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
3388 to 3588 seems to have the same bootloader so, for the short term, using clockworkmod is probably OK. But there is no guarantee that a future update will not require a bootloader change. Again, we have already seen this happen with the NI Adam, and also the Viewsonic non-released UAT. So, with all that being said, I cannot recommend Clockworkmod as a flashing tool.
I've actually kept TNT Lite 5 (which is now TwoTapsX) on ICE specifically because of the expected surge of new Woot users. The last thing I want to happen is for a large number of inexperienced users with mixed information to flash that firmware with the wrong tool (clockworkmod) and then soft-brick their device.
I actually require clockworkmod for my gADAM mod because that mod requires a user data wipe, which standard recovery does not support. But gADAM has a "Recovery Pack" built-in - what this does is allow the user to easily flip between standard recovery and clockworkmod, as needed. Since gADAM is a 1.1-based mod, the use of clockworkmod to flash it is low risk. But if you later flashed to a mod that might require a new bootloader, the Recovery Tool allows you to put standard recovery back before you flash again.
I know this is all very confusing - believe me, it is for me as well. Suffice is to say that modded ROMs are risky business and you should read the instructions very carefully before proceeding. I have started to add the firmware type in my own ROMs as a guide - "1.1" for example. So, a "1.1" to "1.1" firmware mod change should be a low risk, for example. Right now, most of the stock ROMs and probably all the modded ROMs are "1.1" based.
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
eak0703 said:
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
Click to expand...
Click to collapse
i can't update it as the moderators locked it (trust me, I want to update it). I already PM'd jerdog to either open it up or delete it, as I don't think it's needed anymore. I'm not a moderator so I cannot do this, myself.
EDIT: It's been unstickied and updated. TheImpaler handled the unsticky / unlock.
roebeet said:
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
Click to expand...
Click to collapse
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Also that it overwrites stock recovery.(True?)
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
cbay said:
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Click to expand...
Click to collapse
Correct.
cbay said:
Also that it overwrites stock recovery.(True?)
Click to expand...
Click to collapse
Yes, they cannot co-exist. Stock recovery (specifically 3588) will update the bootloader, I've tested this repeatedly. clockworkmod .8 does not.
cbay said:
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
Click to expand...
Click to collapse
Not exactly. If you have cwm and revert to stock 3588, you might not have the latest bootloader (since clockworkmod doesn't touch that) but everything else should be reverted back to stock. But an important note: I've heard stories from users who used clockworkmod to revert to 3588 stock and, although it worked, recovery was actually broken. This happened to a lot of users who were trying to get back to 3588 stock before they upgraded to my later-pulled TNT Lite 5. This is actually the reason why I created the 3588 Recovery Pack.
cbay said:
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
Click to expand...
Click to collapse
Possibly. Lets assume for a moment that the new firmware is a released "1.2" with a new bootloader. Once everyone moves off the "1.1" to "1.2", the issues with the bootloader will probably stabilize. Until there's a "1.3", of course.
And yes, this is all speculation. Viewsonic could throw us a curve balll with their next firmware.
cbay said:
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
Click to expand...
Click to collapse
Right as the Wooters were buying their GTABs, I did a few things to help users out with recovery options.
1) I created a "3588 Recovery Pack". This is a flash update.zip that will add few sripts to your rooted 1.1-based ROM and will allow you to flip between clockworkmod and 3588 stock recovery with a minimum of fuss.
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
nvflash is a different animal. Think of it as a low-level format tool for when your device is messed up and cannot boot anymore. It's good to know about it and learn how to use it, imo - some devices like the Advent VEGA and even Viewsonic's Viewpad10s offer nvflash updates, only. nvflash is a tool specifically for Tegra 2 devices.
adb is a generic "remote shell" tool that is part of the Android SDK. You can find information about adb here or on other Android sites, and that would apply to the GTAB as well. you can make changes via adb, including flash updates, but you need to know what you're doing.
roebeet said:
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
Click to expand...
Click to collapse
That is great! I dont think I will have the patience to wait for Viewsonic to release an update beyond a few weeks.
I was debating between Vegan and TNT Lite, the Recovery Pack will push me towards TNT Lite, at least till I can get a 1.2 bootloader.
Thanks for all the help
--
Recently received G tablet from woot
I'm new to this and would like to know what the best thing to do to my viewsonic g tablet purchased from woot that makes it run the best way. I'm not sure how many and what mod's are recommneded. I've read alot of the posts here and figure TNT Lite (version?) is highly recommended. It is 3588, build frf91. Please give me the best mod's to do, what versions, and where I can find the step-by-step to make it all happen. thanks