Could anyone told me what's the relationship between Odin and Rom Manager
I wanna upgrade captivate from 2.1 to 2.2, so i read some guides
It seems that some guides told me use odin and need the adb shell or combine keys to enter downloading mode.And then flash the pit,and csc,phone,pda.
But meanwhile, some guides said just put the rom in sd card and reboot the phone by Rom Manager.
So i get confused,could anyone told me which should i listen?
By the way,if the phone is locked 3 keys, does rom manager still work?
Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.
Trump211 said:
Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.
Click to expand...
Click to collapse
Thanks,you means these two tools can do exactly the same thing,but the rom source is different?
The rom manager can use a .zip rom contains data/META-INF/system etc. folders?
And the Odin should flash the rom which contains *.pit,*.tar,*.tar.md5 ?
By the way, i saw the 2.1 don't support the recovery etc. from apps, does that means rom manager doesn't work in 2.1? (I already read the 2.2 guide, and it said just use the rom manager)
Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)
Trump211 said:
Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)
Click to expand...
Click to collapse
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....
Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)
rogerhe said:
Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)
Click to expand...
Click to collapse
thanks
I've seen this topic, but i do actually got the 2e recovery running, so what's the point?
dimab said:
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....
Click to expand...
Click to collapse
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.
Trump211 said:
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.
Click to expand...
Click to collapse
Woah, this did helped! HUGE thanks! First time used Odin 1Click and it was smooth, and then restored my 2.1 backup.
Didn't needed to backup on computer the rom backups, since everything was left the same...
Dima
Related
The recently sold captivates(batch #1010) all cannot use the oneclick stock to Jf6 and get stuck in a bootloop when they use this so they have to do a more tedious process. This number is rising because every new captivate sold is 1010 and we need a stock jh7 one-click for easier rom flashing/de-flashing. Could some developer create a one-click to JH7?
DG made a flashable zip, but we can't use that to go from a custom rom to stock but maybe the files can be used? It can be found here:
http://forum.xda-developers.com/showthread.php?t=790080
joeshmoe08 said:
DG made a flashable zip, but we can't use that to go from a custom rom to stock but maybe the files can be used? It can be found here:
http://forum.xda-developers.com/showthread.php?t=790080
Click to expand...
Click to collapse
why can't it be used to go from custom to stock? it's essentially the same thing as all the custom ROMs out there except that it isn't modified. if my memory serves me right (and I'll download it just to check), it does a wipe, it applies a kernel and modem, and even includes the bloat.
ODIN is not a necessity, nor are one-clicks... they usually accomplish the exact same thing as this zip would, just with a third party program. and if you, for some reason, can't get into recovery but can get into download mode, just put JI6 on and then the 2e kernel and downgrade using this zip.
joeshmoe08 said:
DG made a flashable zip, but we can't use that to go from a custom rom to stock
Click to expand...
Click to collapse
lolwut?
I've done exactly that like 5-6 times now. It's totally cool, just run backups, disable your lagfix of choice, reboot recovery, flash, and you're using a (rooted) OTA UCJH7.
Edit: In fact, I keep a 'recovery' folder on my /sdcard/ and /sdcard/external_sd with a market-apps settings.db, efs-dev_block_stl3.img, efs.tgz, bootanimation.zip, Cognition.zip, FontPack-Storopia.zip, gps_fix_epic_signed.zip, gpsjm9.zip, JH7_OTA.zip, and update.ucjj4.modem.zip
I've only ever used Odin *once* and it was because I once tried to flash before disabling lagfix and bricked my dumb self.
Hi
Maybe I didn't search very well but I have a question that seems very stupid...
With Odin, is it possible to flash a custom rom?
I mean the rom that i use normally flash with voodoo on the recovery mode can't bee found by odin...
Thing is that i've got the corrupted memory problem and acted to fast and flashed the stock 2.2 firmware from bell....now i'm stuck with 3e recovery...
If I could flash to a pre-rooted rom with CWM or Voodoo it would be better i thing if i want to try some manipulation with adb
Teranox said:
Hi
Maybe I didn't search very well but I have a question that seems very stupid...
With Odin, is it possible to flash a custom rom?
I mean the rom that i use normally flash with voodoo on the recovery mode can't bee found by odin...
Thing is that i've got the corrupted memory problem and acted to fast and flashed the stock 2.2 firmware from bell....now i'm stuck with 3e recovery...
If I could flash to a pre-rooted rom with CWM or Voodoo it would be better i thing if i want to try some manipulation with adb
Click to expand...
Click to collapse
I haven't confirmed this or searched but I think it's because you have voodoo enabled, this format is ext4 which is a linux format and can't be seen on windows unless you ahve some 3rd party software installed. Just boot into recovery and disable the voodoo, this will put your phone back to the normal format and odin should recognize it.....i'm totally guess here since i haven't tried it but I think this would be the cause
Darky's ROM is meant to be flashed via Clockwork recovery and can not be flashed by odin, darky's comes in a zip file and odin only uses .tar extensions
How did I permabrick my cappy?
Flashing with Odin, I restored to the Rogers stock 2.1 firmware, however the phone refused to boot past the rogers loading screen. I re flashed the phone a few more times playing with the flashing options of Odin, using alternate stock .tar files with no luck. My final flash caused the phone to get into such a state that going into download mode no longer worked, as well as it failing to boot. Luckily Rogers warranty has replaced the phone for me
Any ideas on what caused the phone from booting into the OS, so I don't do it again?
Additional Questions
1. The new cappy given to me through the Roger's warranty has stock 2.2 loaded on it. Is there anyway to back up this firmware to a tar file for later use? If so, how can I use it in conjunction with Odin to restore to stock 2.2?
2. Do I HAVE to restore the phone to 2.1 eclaire firmware before loading a custom ROM on it? Or is it possible to root / reboot into clockwork recovery and successfully flash from stock 2.2 froyo?
3. In my past experiences, after restoring to Rogers 2.1 stock firmware through Odin, kies no longer recognizes the firmware currently loaded on my device... Is this normal? Any fixes? Is there anyway to get kies to recognize the firmware such that it would be able to upgrade or even wipe the phone with the standard stock firmware? I ask this because on the new kies I see the function "emergency firmware recovery".
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
#1 yes but unsure how to make, it would be used like any other tar and odin.
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
#3 normal. no fix. keis sucks
Trusselo said:
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
Click to expand...
Click to collapse
Yeah it was from the one in your sig (linked in the stickies I believe).
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
Click to expand...
Click to collapse
Thanks for the link! and the prompt response
Are there any .tar files floating around for the Rogers froyo 2.2 that address the warranty / logo issues? (search function seems to be broken).
Any stock 2.2 rogers .tar files for use with Odin floating around the board?
What is your recommendation with regards to proceeding with flashing? Should I try to flash 2.1 on the phone with 2.2 preloaded, or just go the 3e clockwork recovery fix route?
Any other pieces of reading you might be able to point me towards in this regard?
I would suggest adding your locale to your profile for future reference, as restoring an I896 is different than an I897.
There is also another way to get clockwork on your phone.
Use Odin and just flash the speedmod kernel .tar from here: http://forum.xda-developers.com/showthread.php?t=893880
I have done it this way since I got my phone and have yet to run into a problem. This works with 2.2 only.
2.2 odin flashable (NO ATT boot fix) and cwm upgrade from 2.1 zip. are here
http://forum.xda-developers.com/showthread.php?t=905042
the person i mentioned before that couldnt get my 2.1 stock to boot on his 2.2 ... he did fix the att boot by un-successfully flashing my 2.1 then the 2.2 overtop, then it booted correctly WITH the i896 bootscreen, basically double flash.
i will contact the creator of the updated 2.1 and see if he can do it to 2.2 as well.
feel free to attempt to flash 2.1 to confirm weather or not it does work on a phone that comes with 2.2. as this isnt confirmed. also note any new notes on the 2.1 stock rom page.
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Trusselo said:
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Click to expand...
Click to collapse
That's common. Everytime I flash the gf's Galaxy Spica, that's the first thing you have to do with it is clear the data and cache. I just do it instinctively now.
My i9000 is on i9000xxjvb stock rom. I flashed modified kernal to make it rooted and cwm enabled. I am unable to move appear from phone memory to internal SD. An error message appears " failed to move application, not enough memory."
To get rid of this, i tried Hamsterbread 1.1 custom rom, but problem not solved. I used every method from hard reset to wipe cache, data and more. But nothing happened.
Now I want to downgrade to froyo. I don't know how to do this? Please, tell the procedure in detail and step by step. I belong to India. There is no 2.2.1 version available for India. Can I go for other regions versions? or I should stick with i9000ddjp6 which is latest verison for India. Thanks
i havnt tried downgrading. but i think you could try flashin back using odin with bootlooder froyo.
i live in india but use european firmware an see no problem
^^ Im not sure about this. I think you can just flash a Froyo ROM via CWM. I am not sure about this. It always makes sense to search around before you do either. Good Luck!
If you flash speedmod (or whatever froyo kernel you choose) through odin, then simply install whatever rom through cwm via zip file. The downgraded froyo rom doesn't need bootloaders, the gingerbread ones are backwards compatible. Tried it myself and it worked without a hitch.
Just flash any stock firmware through ODIN with pit and repartitioned tick and you are good to go.
Makes sense to open eyes and read the post that tells you how .Or even use the search button .
http://forum.xda-developers.com/showthread.php?t=1033781
jje
just download a stock froyo firmware and flash with odin. there are tutorials all over the place
just flash froyo kernel using odin and then enter clockwordmod install zip
So, just switched out my captivate because my warranty was still in effect. Rooted etc etc. But I remember installing CWM with rom manager to begin flashing my first rom back in the day.
But anywho, I have installed ROM Manager, clicked to flash CWM but when I go into recovery (vol + - & Power) All I get is the samsung one. (Blue text) and I only have the options to reboot, install packages, clear cache or wipe sd card.
Can anyone offer any advice?
^ Try reinstall packages. U may have to do it twice.
Gotta install the update.zip with install packages but you have signed bootloaders if you're on stock froyo. Odin to 2.1 and install cwm from there. You can find the update.zip for cwm on the cappy forums and just put that on the root of your internal memory to avoid using rom manager. Don't even have to root to flash.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Hmmmm do you have the stock odin pit file/pda or is the old school odin where you couldnt even do that shoot you right back to 2.1?
^ If u want to go back to Stock Eclair...use the first link in my signature below.
I typically use Odin jf6 one click rev0 from designgears. Its still on the forums I believe but might be dead link. Just make sure it has the pbl and sbl. If you are worried I can upload the one I have used for the past 9 months without fail( but ffailure is always possible, just be sure to follow directions and you should be alright. ) alternatively there is a guide to get to stock jh7 on the forums using the Odin that you have to manually select files for. Should be an easy search. I believe people consider this safer for the newer builds but I used oneclick on my 1010 tons of times and have used it once on my 1012 no problems.
Sorry for the long post hope I helped
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
You all have helped. Thank you so much. Running MiUi again and still loving it.