Hi there. I just recently was toying around with my hone, rooting it, installing some ROMs and stuff. After flashing the ion revision2 ROM, my phone would not go past the rogers screen. Being my stupid self, I never backed up with nandroid. What should I do now? Please help.
Make a Nandroid backup in future. Anyway, you can find a wiped Rogers stock rom here:
http://forum.xda-developers.com/showthread.php?t=534464
Bought captivate from craigslist, from a guy who works for HP and said he got official AT&T 2.2 ROM on it from a buddy of his.
Attached screenshot (taken from another captivate) - Is it official AT&T or a mod?
JI6 is the unofficial 2.2 leak that all of our other 2.2 roms are based off of. The official 2.2 rom hasn't been released yet.
Can I upgrade to official ROM when it releases?
Or do I have to do something to force it? I don't want to be struck with this version if it's unofficial
ODIN usually gets you back to stock as long as you have the 3 button combo
The official firmwares are utter garbage.
Sent from my Captivate.
There is currently no office release of 2.2 (Froyo) for samsung captivate!
There however are a ton of unofficial copies of the unofficial leak.
All unofficial copies still use a beta version as their source, but if it works ok for you then I would not roll back to 2.1.
Personally, I stayed on 2.1 due to the 2.2 bugs that bothered me.
That's a leak we've been using for a while. You can go back to the current stock ROM with the tools in this thread.
Can you point me what bugs I can expect?
alphadog00 said:
All unofficial copies still use a beta version as their source, but if it works ok for you then I would not roll back to 2.1.
Thanks for all replies....
Personally, I stayed on 2.1 due to the 2.2 bugs that bothered me.
Click to expand...
Click to collapse
This phone is for my wife and I want to go back to 2.1 now, instead of wiping the data later
rajetta said:
This phone is for my wife and I want to go back to 2.1 now, instead of wiping the data later
Click to expand...
Click to collapse
There's a whole thread about 2.2 bugs in the General forum.
There isn't really any way to just 'downgrade' back to 2.1 without losing your data. Your best bet is to install Titanium Backup, Rom Manager and the 2e recovery.
The 2e recovery will allow you to use Rom Manager to boot to the clockwork recovery where you can do a Nandroid backup of your rom, in case anything breaks while you are flashing 2.1.
Titanium Backup will backup all your apps and whatnot. You would use the ODIN one click 2.1 installer to go back to the stock factory 2.1 install, which will also wipe your phone clean. Then you would install Titanium Backup again from the market, and restore all your apps that you backed up before you flashed back to 2.1.
I knew craigslist had the "official" Froyo update!
Swyping...please read slowly!
I don't mind losing data, what is the quick way to go back to 2.1?
I don't mind losing data, what is the quick way to go back to 2.1?
Calls drop frequently , so the phone is unusable.
Thanks -
Raj
modest_mandroid said:
There's a whole thread about 2.2 bugs in the General forum.
There isn't really any way to just 'downgrade' back to 2.1 without losing your data. Your best bet is to install Titanium Backup, Rom Manager and the 2e recovery.
The 2e recovery will allow you to use Rom Manager to boot to the clockwork recovery where you can do a Nandroid backup of your rom, in case anything breaks while you are flashing 2.1.
Titanium Backup will backup all your apps and whatnot. You would use the ODIN one click 2.1 installer to go back to the stock factory 2.1 install, which will also wipe your phone clean. Then you would install Titanium Backup again from the market, and restore all your apps that you backed up before you flashed back to 2.1.
Click to expand...
Click to collapse
rajetta said:
I don't mind losing data, what is the quick way to go back to 2.1?
Calls drop frequently , so the phone is unusable.
Thanks -
Raj
Click to expand...
Click to collapse
Read what you quoted - Odin One click will get you back to 2.1. Read the captivate bible thread in the dev section.
I was in a hurry and upgraded my GF's Rogers Captivate to the leaked 2.2 ATT some time ago. It seems now that the backup I performed (via Titanium) was not the full backup I required and therefore I have no backup to revert to my Rogers stock 2.1.
Her phone is operational, it's an improvement from 2.1 Rogers stock but I've now realized that if the phone isn't actually mine to play with, its not worth playing with.
With Rogers 2.2 released there is indications that it fixes things that I/she would like resolved (mainly the SMS timestamp? and better GPS functionality?)
I would like to return to a normal state of Rogers 2.2 and then stop playing with her phone.
There is a thread here on how to return to Rogers 2.1 but it is large and has multiple solutions and warnings enough to make it seem like its not the easiest path to venture...
http://forum.xda-developers.com/showthread.php?t=846501
Then again there is other threads showing how to just simply flash to a Rogers 2.2 ROM....
http://forum.xda-developers.com/showthread.php?t=905655
Will there be disadvantages to taking what seems like the easy route and flashing simply to Rogers 2.2 without going through a convoluted process to revert and kies update to 2.2? Clearly I'm not fully competent regarding this and its difficult to get better when you don't yourself actually own an android phone (hence why I'm trying to bail). I just want to find the easiest way to essentially get out of the mistakes I've made, and make them as forgettable as possible. Any advice would be appreciated.
I don't see anything wrong with flashing straight to Rogers 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
I use Odin to flash stock 2.2 most simplistic way to do it. Saves you the hassle of having to deal with Kies.
I used the odin flashable file from here. No need to get the kernal/moden file it's already in the .tar
Do I need to save the APN settings or anything?
Assuming I have no interest in any personal data will flashing via odin the above mentioned I896UXJL1-HOMEBINARY.TAR bring me back completely to Rogers?
My APN settings and everything will be back to default rogers?
Will the AT&T symbol still be there on boot?
If I want to try a custom ROM in the future will I be able to do it from here, or will I need to flash to 2.1 or some other stock ROM?
I can't seem to install CWR in my current state, will this potentially change that?
Uc an use ODIN to flash back to 2.2 Rogers but I am afraid u will stll see At & T logo when u boot it up
There is a thread to replace that logo as well
The AT&T thing doesn't really bother me.
I left this problem and didn't deal with it because her phone was working fine and I would have rather not touched it. The problem now is that Rogers in Vancouver had some massive downtime a few days ago and now her phone refuses to run data. Voice is fine, I modified and played with the APN settings to no avail.
After testing the SIM and some other options it seems that I'm left with no other choice but to conclude that this is my fault and I guess going forward on flashing a stock 2.2 Rogers hopefully will resolve this.
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
Is there an international rom for the Atrix 2 yet, ive flashed a few roms but they are all still loaded with AT&T stuff.
has ANYONE got a link to motorolas stock firmwares?
id quite like to flash back to my stock rom (telecome New Zealand)
if anyone can help me ill bow down
I don't think there's an FXZ for New Zealand yet.
This is why it's recommended to do a cwm backup before flashing new roms.
Daywalker04 might be the guy to go to to get fastboot files tracked down, though I think he needs some of the details about the system to find the fastboot files for us...
Hopefully there's another kiwi around here that can back up the system for you to do a restore.
Note that most of the AT&T stuff can be removed...
I'm kind of interested in the build numbers for Telecom NZ's Atrix 2 firmware.
Thanks, its not actually my phone, before the guy did a backup he used titanium backup to remove some stuff he didnt want, in his haste he deleted something that was related to contacts and he couldnt add contacts anymore, at that stage it was to late to make a CWM backup.
He flashed someone elses CWM backup but it went into a bootloop and wouldnt start at all, so he flashed a custom rom from here but it was AT&T and he couldnt get any service.
hes currently on rebel rom but desperately wants it back to stock (hes a 52 year old man) he was even gona go as far as paying a mobile repair site to fix it back to stock.
I realise this is now an old topic. But, here http://sbf.droid-developers.org/edison/list.php