I recently just flashed a new rom and I had realized I never tried the stock 2.2 from samsung and I was wondering what people thought of it and if they were still able to flash other roms or use odin to go back to stock 2.1 and then flash other roms again. Or does updating to 2.2 mess up some of that?
And is it even worth it to try and check it out?
I am running serendipity and my wife has stock. I would not go back to stock if att were to pay me. Her Gps was messed up, bad battery life and other strange issues.
Sent from my SAMSUNG-SGH-I897 using XDA App
the only thing 2.2 may mess up for flashing roms is it installs 3e recovery which needs signed update.zip packages (can be patched ) , and sometimes you need a new root program.
besides that its... stock. with the 2.2 updates...
Has anyone tried reflashing odin or using clockwork/rooting in 2.2?
I'm thinking i'm going to stay away from it at this point but curiosity my get the best of me....
jlt220 said:
Has anyone tried reflashing odin or using clockwork/rooting in 2.2?
I'm thinking i'm going to stay away from it at this point but curiosity my get the best of me....
Click to expand...
Click to collapse
i sucessfully rooted it using superone click method...but had problem flashing clockwork mode as there is sign verification problem...so i tried to flash back to 2.1 and used AIO method...which bricked my phone...so better to keep flashing good custom roms and be unbricked ....stay away from stock froyo...its exactly 2.1 with stock froyo capabilities...
Trusselo said:
the only thing 2.2 may mess up for flashing roms is it installs 3e recovery which needs signed update.zip packages (can be patched ) , and sometimes you need a new root program.
besides that its... stock. with the 2.2 updates...
Click to expand...
Click to collapse
jlt220 said:
Has anyone tried reflashing odin or using clockwork/rooting in 2.2?
I'm thinking i'm going to stay away from it at this point but curiosity my get the best of me....
Click to expand...
Click to collapse
rooting 2.2 via clockwork, see the post above you...
3e sig check. fix with http://forum.xda-developers.com/showthread.php?t=909213
First I have a Captivate 1007.
Very easy to get into Download Mode so I know the phone isn't bricked.
I was running a version of Serendipity Rom. I wanted to try something different.
So I used what I always use the ODin3 One-Click Stock back to Eclair.
I get nothing but a boot cycle showing the AT&T screen.
Must I go to Stock Froyo now?
Would appreciate some guidance as I'm stuck after a few hours of searching!
Have you tried to flash odin again
CM7
Frawgg said:
First I have a Captivate 1007.
Very easy to get into Download Mode so I know the phone isn't bricked.
I was running a version of Serendipity Rom. I wanted to try something different.
So I used what I always use the ODin3 One-Click Stock back to Eclair.
I get nothing but a boot cycle showing the AT&T screen.
Must I go to Stock Froyo now?
Would appreciate some guidance as I'm stuck after a few hours of searching!
Click to expand...
Click to collapse
have read someone something the same what only works with him is flashing the leaked froyo. you may flash back to stock eclair after everything is working.
The leaked Froyo from Eugene?
I have that one I was just hesitant to flash it.
There is no .PIT file with it though. Is that ok?
EDIT:
Just tried with Odin3 1.7 got Eugene_JK2_Froyo.tar (2).md5 is invalid.
Going to try this one I897UCJI6-OCD-REV02-Low-designgears.exe
Frawgg said:
The leaked Froyo from Eugene?
I have that one I was just hesitant to flash it.
There is no .PIT file with it though. Is that ok?
EDIT:
Just tried with Odin3 1.7 got Eugene_JK2_Froyo.tar (2).md5 is invalid.
Going to try this one I897UCJI6-OCD-REV02-Low-designgears.exe
Click to expand...
Click to collapse
the designgears revo 2
mcord11758 said:
Have you tried to flash odin again
CM7
Click to expand...
Click to collapse
I have 1007 build, I would have to agree with ^^this^^.
Something might of happened in the flash. Try it again.
Use these specifically.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702
Working now after flashing with I897UCJI6-OCD-REV02-Low-designgears_1_.exe
What do you guys recommend flashing now back to original Eclair stock or staying?
Really up to you at this point. I don't bother with stock (original) firmware as they are bloated and whatnot.
Indeed. Going to try something with good battery life now!
Thank you for all the help fellas!
EDIT: Also I can't go back to 2.1 Stock. Only 2.2 Stock!
hey all - I got a new D3 replacement today after the touch screen stopped working on the old one. it came with 5.7.906 installed. i am confused as to weather there is a way to unbrick it if i manage to muss it up when i go back to cm9. i love cm9 and hate the stock rom but considering this is my 5th D3 i am not willing to flash roms if i have no way to return to stock in case of hardware malfunction so i can get a new one under waranty
i appreciate any information on the topic
As long as you can get to the Moto Bootloader, then it is 90% likely that you can unbrick it. The tools can be found here:
http://forum.xda-developers.com/showthread.php?t=1255198&page=23
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
ovelayer said:
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
Click to expand...
Click to collapse
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
redsox985 said:
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
Click to expand...
Click to collapse
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
ovelayer said:
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
Click to expand...
Click to collapse
Oh, ok, so these are just the 5.6.890 FXZ files?
redsox985 said:
Oh, ok, so these are just the 5.6.890 FXZ files?
Click to expand...
Click to collapse
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Q9Nap said:
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
redsox985 said:
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
Click to expand...
Click to collapse
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Q9Nap said:
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Click to expand...
Click to collapse
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
redsox985 said:
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
Click to expand...
Click to collapse
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Q9Nap said:
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Click to expand...
Click to collapse
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Q9Nap said:
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Click to expand...
Click to collapse
Nope, XT862 with WiFi tether hacked radio. Request sent.
redsox985 said:
Nope, XT862 with WiFi tether hacked radio. Request sent.
Click to expand...
Click to collapse
yeah, i'd make sure your'e on fully stock 890 with no modifications before flashing 894; it should work. request accepted.
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
nemiroG1 said:
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
Click to expand...
Click to collapse
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
redsox985 said:
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
Click to expand...
Click to collapse
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Q9Nap said:
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Click to expand...
Click to collapse
I never did get around to formatting my SD card. Stock recovery only sees the EXT SD correct?
I'm currently chatting with Moto... This is odd. I'm going to start my own thread for it to leave this one be.
My friend has a bionic that he flashed the leak where he didn't have to be rooted is there a way he can go back to stock latest gingerbread firmware and wait til it its officially released? He's having to much problems with it.
Sent from my Galaxy Nexus using xda app-developers app
FXZ to .902 using RSDLite, then take OTA to get back to .905.
What problems?
I haven't heard anything negative at all about the leaks before this.
Also needing to FXZ back to stock from ICS leak 2233
I also flashed to ICS from. 905. I love ICS and have had absolutely zero problems with the leak version but I need to go back to 905 via 902 to get ready for the OTA update. I have rsdlite but need a "working" link to the FXZ file for 902. I was observing a thread in the development section but that link went to fileserve with a message that it was pulled because of copyright violation. Hopefully I can find the right file and avoid bricking during my jump back to Ginger.
Johnny7778 said:
I have rsdlite but need a "working" link to the FXZ file for 902.
Click to expand...
Click to collapse
https://rapidshare.com/files/3690790507/VRZ_XT875_5.9.902.XT875.Verizon.en.US_CFC_01.xml.zip
Does anyone have the Odin files for the latest Ota? What to go completely back to stock. Pretty sure I screwed something up. Thanks!
Sorry no Odin files for the official kit kat release are available. Urdroid in the general section is the closest thing available. It's a slightly modified stock rom.
cclark1894 said:
Does anyone have the Odin files for the latest Ota? What to go completely back to stock. Pretty sure I screwed something up. Thanks!
Click to expand...
Click to collapse
Use these instructions to get back to complete stock if your on 4.2.2 stock.
http://forum.xda-developers.com/showthread.php?t=2703006
I'm completely stock after taking the ota and using towel root . I'm unrooted stock.