Database Info

Help, can't flash 'fixed' sbf files except for one. Telstra Au MB525.

I just tried to flash the Telstra (Australia) SBF. No info comes up in file properties and it gives an instant 'failed flash' message.
I am a bit stuck- i can only flash the China Froyo and the GB Froyo, the only 'Fixed' SBF I can ever flash is the 2.2GB_NoCG_31_39.sbf -(Higgsy fix). The China rom is the first and only Froyo rom I flashed with the above fix.
1a. :I want to know why I cannot flash 'fixed SBF's' that come with JBoogie, ADXLmod, barebones etc roms.
1b :Why do I still have to use the 'Higgsy fix' 2.2GB_NoCG_31_39.sbf? It appears that I am somehow locked to it.
1c :Is it because of the Telstra rom I am on- with all rom flashing instructions, it is mentioned eg 'if you are on 2,21 or 2.34 fw etc- no reference is ever made to the 2.26 fw.
2: I want to know how flashing a rom without the corresponding SBF actually affects the operating of the rom- eg: I get random reboots, black screens, freezups=- is this likely an issue with the rom or because I cannot flash the fixed SBF.
3. Will restoring a Telstra nanodroid on top of the China Froyo SBF that I am running, then applying the fixed Telstra SBF that racca graciously provided make my Defy exactly like stock- or will there still be remnants of the China Froyo etc rattling around under the hood and potentially affecting stability and continuing to affect my ability to flash fixed SBF's as per Q 1 & 2.
4. Does anyone have a FullTelstra SBF that works unlike the one already posted on XDA.
I have tried renamimg and moving sbf to root folder as per a suggestion for 64 bit windows, though i am only on 32bit, it didn't work for me- 'start' is still greyed out in RSDLite..
I have also tried different rsdlite versions.
I welcome any other suggestions or questions.. At least I would like to know what is going on and how it affects my phone as I have spent hours and hours searching these and other forums and am none the wiser..
Cheers
Gavin

Accidental 2nd post-ignore.

what exactly are you trying to do?
i can't make much out of your long and pointless statements.
be specific about what you need, then maybe we can help.
all i can understand is that you might want the fixed sbf, so here it is.
http://mir.cr/6MJBVDCN

Thanks for that, pointless is a bit harsh though, long maybe- i was trying to give some background to prevent 'have you tried that, just do this- when it is clearly not applicable to my situation.
I will try to put it in point form.
I hope that is a bit clearer, but it is a complicated situation- there are alot of threads dancing around similar themes, but I cannot find specific answers to these questions- i can't see how I could provide less information without having 5 pages of people directing me to posts that I have already looked at but aren't applicable, so yes it is a bit long, but by doing this much misdirected effort is saved by myself and those helping.
Thanks again

Looking at my original post again, it was hard to see what I was asking, thanks racca.

I just restored the Telstra factory reset nanodroid- the start button was greyed out with the Telstra SBF , so i can't use it. Had to use the 'Higgsy fix' to get it to boot. Weird, i just don't understand it.
To be honest, with all the eventual issues with any rom i use, i would prefer to go back to stock (i will have to put up with the grey status bar, short battery life and no flash). I am tired of getting crashes at the most inopportune times.
Can't wait until the bootloader is fully cracked- I have put Gingervillain (CM7 base) on her Desire, which is much more stable than any rom when i was using it.
Update- it just won't boot now, have to reflash the China Froyo SBF, looks like I am stuck with daily @ 3x daily reboots, bluetooth that works 60% of the time, dropped calls etc....

Change SBF file name
Hey there,
I kinda have the same issues as you do, I think...
The RDS lite gave me an instant ROM-flash error when trying various SBF's. I simply renamed the file name to an SBF file name that was working, yes it got a little confusing... first I renamed the original working SBF to *.old.
Suddenly the flash process was working, I've renamed SBF-files on 4 different occasions in order to get it to work.
I'm not quite sure whether you have this issue or you have something different going on, but feel free to try it.
//Dave

Sounds like a plan, I will give it a go. Thanks.

Thanks Dave69 and Racca, i just renamed the TElstra fixed sbf to the higgsy fix; restored the stock nanodroid and flashed it and it worked. It at least gives me the confidence to flash others now, but will sit on this for a bit- don't have time for more tinkering this weekend.

Titanium wouldn't work with the Telstra rom- said it had restored apps, but wouldn't restore evn one.
Thankfully I got Barebones running, SBF and all. Looks great. Thanks guys.
I would still like to know what's going on though, I haven't tried the TElstra full SBF with the rename yet- it had a different issue than others- just failed. May try again later.

Sounds like you have the same problem as me, was on the telstra on. Not being careful enough I flashed a non downgradable 3.4.2_155-002 sbf. So now I can't downgrade back to the stock Telstra one. I have tried both nandroid backups and flashing the stock telstra sbf and neither work. so am stuck on this rom running JBoogie GingerBlur
Not compaining, for a blur rom it is quite fast, only thing is I can't downgrade back to telstra if the phone needs to be returned for anything.
Hope this helps.
Cheers.

Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...

superfastmonkey said:
Try following the renaming method-though i had titanium issues, it os enough to get me through a warranty claim- i did it before with the same nanodroid backup from xda. Btw, i just flashed the 3.42 out of frustration and it let me go back with the renamed fixed sbf.
I am very impressed with barebones, even the xda app is quicker...
Click to expand...
Click to collapse
ok, now where do i begin. i'll just say what i can think of instead of answering every single question.
sbf's contains various code groups as you may noticed while flashing it slipts into smaller pieces.
out of those, cg31&39 are non-downgradable and the pair of them must match. all other partitions on the phone are either not flashed by the sbf (e.g. bootloader/mbmloader, pds), useless (cdrom) or downgradable (kernel, recovery, lbl, devtree).
there are no hardware incompatibilities except the chinese ones, but if you don't update cg31(cdt) to match your /system(cg39) you might have some minor issues (i singles these out because they are not downgradable, of course you'll have issues if you don't match all other things).
you might have a chance fooling tel$tra by flashing the sbf i provided (stock 2.26.0) and restore the nandroid. it should be almost identical except you'll get busted when they try to do flash their service sbf.
the bottom line is,
1. if you flashed any sbf larger than 50MB it must have cg39 in it, and you can't downgrade.
2. you must use matching kernel/devtree with the system: the chinese ones will not be compatible with any other roms, you can't mix match froyo with eclair.

Thanks racca, it makes things a bit clearer. I didn't think I had flashed the GB rom, but I must have-it was 3 or 4 mths ago- it explains why I used the Higgsy fix...i think the China one came out very shortly after..
I should probably try flashing a 2.1 rom b4 restoring the telstra nano if I want stock-( with Telstra, we will have to wait until 3 mths + after the rest of the world gets Froyo for them to fill it to the brim with bloat ware..)..
It looks like the Higgsy fix didn't work for our devices anyway-i suspect my phone believes it is a 3.42 fw now.
In any case, I am relieved to have a way to flash the fixed sbf's now.. Barebones is very impressive, no hint of an issue, but need to run it for a week to really see.
Thanks.

I have a Telstra phone too and after a week of owning it back in January, I had already installed a 2.2 De-blurred ROM. I did have radio issues at first and also remember a non-stop reboot issue. I think it was the USB debugging somehow but I could be wrong.
Now I install new ROMs with ease when the need strikes me.

Are you able to flash the fixed sbfs for roms you install?

I've just put the CM7 rom on mine, best rom I've used. Also flashed a fixed rom with it.
Next thing i tried was restoring a nandroid backup of the default telstra rom, then flashed a fixed stock telstra sbf, this worked and was able to at least make the phone look like it was stock. Whether or not that would be enough if i had to send the phone in for repairs. Can only try if it needs to go in.
CM7 is by far the fastest rom I've tried. Only used for a day so far and no problems yet. Highly recommend this one.
Cheers
Sent from my MB525 using XDA App

I flashed the fixed sbf by renaming after restoring the telstra nano and it worked, but didn't run properly, I did it a couple of months ago with just the nano after having jboogies blurless ginger and it passed for warranty. Haven't tried renaming the full telstra sbf yet. I might over the long weekend.
Sent from my MB525 using XDA Premium App

That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App

samorgs said:
That's what I was hoping, but for now I'm staying with cm7.
Will go back to the telstra one only if it needs warranty work.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
You'll be fine.
On a side note, it's ridiculous that Optus have official froyo already, Telstra due in July.
Sent from my MB525 using XDA Premium App

[GUIDE] GUIDE to get the official US T Mobile OTA

If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo

hi is this only for US people or will it work in UK as well?

It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App

Does it supports 720p video recording!!

vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?

Anyone can upload nandroid and sbf ?

It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App

Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!

I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz

On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.

i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.

you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.

Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk

i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.

I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk

It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App

Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.

i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.

[SBF-ROM]MIUI 1.5.27 English

Here is a test SBF version of MIUI latest (27/5/11) with English patch applied and including Swype and full battery percentage display too. Replaced data icons with sense ones as the green ruins the whole look!
Please do a nandroid first as i'm not sure if this even works on other peoples Defy. I tested and it works on mine.
To install:
You need to be on Nordic rom or be using it as a base for your current rom such as CM7
Install my sbf through Moto flasher. Let boot. Report.
Note: May not be full English on first boot. Go to settings and re-set English language, reboot into recovery and clear cache and dalvik cache it seemed to do the job for me.
DOWN!Download me now!

Thanks, man

Remember this is a test please don't blame me if your wife leaves you.
Ephumuris. Defy CM7 by Quarx.

sounds not good. after flashing bootloader error . restart same error after moto logo.

Good Job.
Thx

is it working?

Is there only english/chinese? Any other languages like Polish?
Sent from DEFY running Quarx's CM7

joker20 said:
sounds not good. after flashing bootloader error . restart same error after moto logo.
Click to expand...
Click to collapse
Same
Swyped by my Defy using CM-7 beta 6 with the XDA premium App

Hmm seems to not work for others... I wonder what would need to be done differently.
Removed download link for now.
Ephumuris. Defy CM7 by Quarx.

ephumuris said:
Hmm seems to not work for others... I wonder what would need to be done differently.
Removed download link for now.
Ephumuris. Defy CM7 by Quarx.
Click to expand...
Click to collapse
i think the problem is when we make a data factory reset from normal recovery which makes 2-nd init unusable. i am trying this baut for build spanish miui, and i think a method that would work is first install an original froyo->boot it completely->reboot to bootloader and flash the moded sbf. i will report back if works.

I tried it, flashed over CM7 without wiping and it worked. Then tried a full wipe with stock recovery and it sticks at the M logo.
I was on nordic 3.4.2.177 base before I flashed. After wiping had to reflash full nordic and tried again, still stuck on Motorola logo.

I made a Custom sbf with CM7 nightly build before,
http://forum.xda-developers.com/showpost.php?p=14199021&postcount=14
Came across the same problem, it seems that we should modify the dumped CG39 a bit.

I think it would be greate&enough if we would have a SBF which only contains Custom Bootmenu so it's small and flashes very fast.
After flashing that CWM can be used to flash.

m11kkaa said:
I think it would be greate&enough if we would have a SBF which only contains Custom Bootmenu so it's small and flashes very fast.
After flashing that CWM can be used to flash.
Click to expand...
Click to collapse
This is what you are looking for. http://forum.xda-developers.com/showthread.php?p=14223629#post14223629

That Thread was created 2 minutes before my post
Thank you very much

I'm sorry if it's a dumb question, I'm new to this, what's the point of a sbf? Why not just a nandroid?

It's quite useful to have a SBF. If something is going wrong, let's say you'll try to put one nandroid which is not successfully applied or you by mistake wipe your phone using stock recovery you'll have to flash fist a Froyo SBF and then you can install 2nd Init and apply the nandroid, while by having the CM7/MIUI SBF you'll have only to apply it and that's it.

So, basically , it's for the lazy ones instead of flashing nordic, root, install 2ndInit and Miui, you just flash this sbf. 5 minutes less and a chance of bricking the phone. I'm going for the long way.
We should focus on finding and reporting bugs on the basic Miui, this would really help make a better release.

wife vs modding
ephumuris said:
Remember this is a test please don't blame me if your wife leaves you.
Ephumuris. Defy CM7 by Quarx.
Click to expand...
Click to collapse
u got me there.my wife
is starting to bothered by my modding schemes on my defy.
she said im so poor of me,if i get my defy brick she will buy me iphone4..
but i say no,buy me more defys.she said how many defys u want-2 more defys.
thats 3 total ^^ then she raised her brow & silently smiles.
maybe she think im going nuts.
little offtopic fun

[Q] Return to Stock for Nexus S

Hello there.
I would like to ask for your good help restoring my Nexus S. I'm actually really exhausted looking for answers and tried downloading programs (e.g. One Click Stock) already. I wouldn't try to poke you guys if I hadn't reached dead end. Painstakingly exhausted for the last 3 days plus the slow connection we have here.
Using One Click Stock by Michael Peerman, I'm stuck without a signal since it says that I'm on Sprint. Everything works except that I'm always without signal.
My phone is under Globe Telecommunications Philippines. Build Number GRJ22. Currently it is in Gingerbread 2.3.4.
I won't bother rooting it again. I just want a simple droid without the extra benefits of a rooted phone.
Any help pointing me to the right direction would be really appreciated.

just flash a stock rom! and that would make a stock nexus s! and if you want even more you can lock the bootloader again!! and about the signal try flashing another radio!
see here:http://forum.xda-developers.com/showthread.php?p=14564429#post14564429
ps. you can grab the stock rom in rom manager

quiquegabriel said:
ps. you can grab the stock rom in rom manager
Click to expand...
Click to collapse
Pretty sure that it is the tmobile version in rom manager...
Sent from my iPhone using Tapatalk

bdpyo said:
Pretty sure that it is the tmobile version in rom manager...
Click to expand...
Click to collapse
It's only the ICS rom the one fot t-mobile. The GB one is for everybody
http://www.clockworkmod.com/rommana...s&name=Stock Images&deviceName=Google Nexus S

Hello There.
Thanks for the hot tip. I got it all back to stock.
I did was root the phone again,
installed ClockworkMod. > Mount USB to PC > on the clockworkmod folder I created new folder "backup". Then paste the Stock Rom.
Reboot to Recovery then install from zip.
Voila! It worked.
Very much thanks to everyone.

Stock is different baseband version
I had recently flashed an ICS rom and could not get my mobile data working after trying every single radio for my model I9020A.
So I used rom manger to download 2.3.3 stock GB as described in this thread. Now it is showing I have baseband version I9020XXXB1 and when I go to system updates it says my system is up to date. How do I update to newest version of GB and show the correct baseband version of my phone?

[Q] How do I install the new ics mod?

Hello everyone,
I'd like to express my gratitude to the developers for their great work to keep this phone working..
I have a couple of questions and would appreciate all the help I can get to help me with the phone.
I had installed CM7 on my phone for 4 months during which it kept rebooting and giving me a lot of trouble, so I installed the russian stock sbf (since it has arabic) two days ago and it works great and fast, except for one thing: the battery drains extremely fast. Now, I consider installing the new ics recently posted here:
http://forum.xda-developers.com/showthread.php?t=2069578
My questions:
1- The russian stock has everything I need and is fast and stable, so I do not want to go back to CM7 which keeps rebooting and wouldn't recognize my sd at times. Is there anyway I can improve battery life on it?
2- Would you please post how I can install the new ics in that link? Please be as specific as possible..
3- How do I clean my sd card? which folders should I not tamper with? it looks messy with all the different zips and folders..
Thank you all.. Happy new year

1 download rom
2 (if you have xt720 not motoroi)
3 in open recovery(in update)flash rom,gaaps and bootfix)

Got it
It took me a while and some research to apply it.. Thanks for your reply.. I will try to post the steps I did so that people like me won't have the problems I had.. I needed to refresh my memory to remember what I did when I first rooted the phone and installed 7.2 a while ago..
BTW.. I couldn't find the keyboard.. the only/default input is the google voice typing!! isn't there an android keyboard for this mod? or do I have to install one from the market<-----------which will mean a lot of pain to sign into my google account then searching for a keyboard using voice typing
Update:
I was able to find an apk for a trial of swiftkeyboard, so I installed it and installed a keyboard from google play and everything is working fine.. I love this mod, it's fast and still no problems; except for video recording (which I don't use) and the voice search which recognizes the commands but does not do anything else..

You can usually use the same steps as other roms:
Make sure you have OpenRecovery. See the OpenRecovery thread with detailed instructions.
Download rom zip file and copy into /sdcard/OpenRecovery/updates
Turn off device
Hold power and volume up to enter recovery. (You should see a white box with an arrow coming out of it going into a phone. If you see a yellow triangle, something went wrong.)
Go to Apply Update (use the volume keys to move up/down and camera key to select)
Pick the rom (and in this case, then pick the bootfix and gapps)
Go Back to main menu
Now do three wipes: There's three wipe options (dalvik, cache, and user data). Most mod makers recommend wiping all of these, but when you wipe user data, you lose everything you stored on the phone (but not sd card). So your game highscores, sms messages (backup app), etc...
Reboot system
ray86 said:
BTW.. I couldn't find the keyboard.. the only/default input is the google voice typing!!
Click to expand...
Click to collapse
I didn't even have google voice when I installed (I think I forgot gapps), but this thread has stock ICS keyboards and instructions.

bugs network motoroi
im having a problem on that rom the 3g network is not working i am from phil globe network it shows no signal when i switch to 3g but when on gsm it has a signal this is not a network problem bcoz my family has 3g sgnal on the same network i tried all the baseband and it didnt work.

zhelin07 said:
im having a problem on that rom the 3g network is not working i am from phil globe network it shows no signal when i switch to 3g but when on gsm it has a signal this is not a network problem bcoz my family has 3g sgnal on the same network i tried all the baseband and it didnt work.
Click to expand...
Click to collapse
Make a new apn flash a rom with good working 3g or stock.
Flash cm9 then add new apn.
Sent from my XT720 using xda premium

still not working
mchlbenner said:
Make a new apn flash a rom with good working 3g or stock.
Flash cm9 then add new apn.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
still not working i used stock rom motoroi since my phone is motoroi 39.50 froyo 2.2.1 before flashing this rom. like i did in miui but the 3g is working on that rom. should i flash a milestone stock rom.

NO!!!!
You have a motorio xt720.
When you flash cm9 you should not flash bootfix it is the milestone xt720 im just guessing you might have flash are bootfix that why you dont have 3g.
Sent from my XT720 using xda premium

no i didnt
mchlbenner said:
Make a new apn flash a rom with good working 3g or stock.
Flash cm9 then add new apn.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
mchlbenner said:
NO!!!!
You have a motorio xt720.
When you flash cm9 you should not flash bootfix it is the milestone xt720 im just guessing you might have flash are bootfix that why you dont have 3g.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
no i didnt since i read 1st page to last before flashing this rom.

vadims746 said:
1 download rom
2 (if you have xt720 not motoroi)
3 in open recovery(in update)flash rom,gaaps and bootfix)
Click to expand...
Click to collapse
Sorry, the BootFix what is it?

andrexo said:
Sorry, the BootFix what is it?
Click to expand...
Click to collapse
The bootfix in general is a patch to be applied when a ROM was developed for one version of a model of phone, but because two phones are so similar, it can be used on other versions of the same model of phone, with a few tweaks. The bootfix performs those tweaks. If you were to have a Motoroi and you actually applied the bootfix also, I mean logically it wouldn't think it would be harmful (just redundant), but I don't know enough about how the patching process works to accurately predict that. If you did this and you were experiencing issues, back up your data and do it over, without applying the bootfix.
In specific to the XT720, there are two versions of this model: the Motoroi and the Milestone. There are ROMs that were developed for the Motoroi that actually work on the Milestone also, with a few tweaks. The bootfix patch includes those tweaks. It fixes things like rotation issues, etc. If you didn't apply the bootfix and you have a Milestone, you would absolutely run into issues. Redo it, applying the bootfix.
Scenario 1:
You want to load a ROM that was developed for Motoroi users. You have a Motoroi. You would simply install the ROM, Gapps if you wish, and do your wipes. You should be good to go.
Scenario 2:
You want to load a ROM that was developed for Motoroi users. You have a Milestone. You would intstall the ROM, Gapps if you wish, AND install the bootfix patch, then do your wipes. This would fix any incompatibility issues between Motoroi and Milestone.
All of the ROMs posted in the dev forum are very clear in instructions (and plenty of discussion afterward in replies to the thread) as to whether or not a bootfix needs to be applied. Of course, you need to determine what kind of XT720 you have, in order to make a decision as to which instructions you will follow.
That's my "non-technical" answer!