Database Develop

[Q] Why do we have to use ODIN instead of full wipe with Clockwork Recovery?

I'm a HTC guy here and we always just use recovery (Amon_Ra or Clockwork) to wipe data/system restore before flashing a new rom. We don't have to revert all the way back to completely stock. It seems to me that I should just be able to use the update.zip to install Clockwork recovery, do a full wipe, and flash a new rom.
If I'm already on the stock rom do I still need to ODIN before rooting/flashing or can I just root/flash? Every time I switch roms do I have to ODIN back to stock, re-root, then reflash? That sounds really obnoxious.
Just wondering if anyone can explain the difference to me because it's not making sense. I'm suddenly REALLY glad I have an HTC phone with T-mobile.
Thanks!

This confused me at first as well since I had a magic.
I think mainly it is because of the lagfixes and compatibility with some of the recovery modes. Instead of thinking whether this may be right or not, if you ODIN then flash a new rom, you get rid of potential problems compared to just the standard wipe. That's my take on it anyways and I just follow the majority.
Sent from my GT-I9000

don't blame me when your phone explodes but i've never flashed back to stock once i starting using custom ROMs. and i've flashed at least 10.

It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.

And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard

avgjoegeek said:
It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.
Click to expand...
Click to collapse
I agree, wiping is important and I always do it from recovery by choosing WIPE DATA/FACTORY RESET. My actual question is this:
Why not just use Clockwork Recovery to wipe? That's what I always did with my Magic 32B and what I've done so far with my Glacier. It has never caused me any trouble to do it this way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As for the sdcard and maintaining root - I'm really not sure how that's related, as root access is under /system, which doesn't live on the sdcard, right?

avgjoegeek said:
And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard
Click to expand...
Click to collapse
That's actually how I flashed Cog 2.3b8. From her stock setup just update.zip to clockwork recovery, wipe data/factory reset, flashed Cognition and went on with my life.
QUESTION - Updating to Cog 3 do I need to uninstall lagfix before flashing anything else? Can I flash Cog 3 over Cog 2 as an update.zip without wiping data? If I do wipe will a WIPE DATA/FACTORY RESET be sufficient or do I need to ODIN? If I use the wipe through clockwork do I need to uninstall lagix first?
Sorry for all the questions, I'm still learning how all of these things interact with each other.

you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.

mengbo said:
you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.
Click to expand...
Click to collapse
So add the disable lagfix folder, reboot, then go back to cwr, wipe data flash, cog3? I would really like to avoid wiping if possible, but oh well...

that is correct. copy the cog 3 install package to your phone internal sd, remove external sd and sim before update for safe by the way .

[Help] Flashing of ROMS

i tried following everything whats inside the guide via recovery but i encounter this.
Whenever I tried to flash always come this .
In red.
Short write of/tmp/sideload/package.zip{No space left on device}
what went wrong ?

Another one when I try using ROM Manager .
It show this .
Failed to verify whole file signature
Signature verification failed

The file you trying to flash is not belongs to Galaxy Note.... Or not belongs to the Particular Version of Firmware..

ranjan.alva said:
The file you trying to flash is not belongs to Galaxy Note.... Or not belongs to the Particular Version of Firmware..
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash Kingdroid and Darkynote Roms . Still the same .

put the roms file in your internall sd
Enter recovery via 3 buttons
First wipe dalvik cache and the wipe data
then istall from internal sd
----------------------------------
if this does not work for you
Try flashing PC ODIN but follow exactly the steps.

mythbusted said:
if this does not work for you
Try flashing PC ODIN but follow exactly the steps.
Click to expand...
Click to collapse
Do not use PC Odin for flashing custom Roms like Kingdroid or DarkyRom. It will raise your binary counter and void your warranty.
Always use CWM Recovery for flashing custom stuff.

mythbusted said:
put the roms file in your internall sd
Enter recovery via 3 buttons
First wipe dalvik cache and the wipe data
then istall from internal sd
----------------------------------
if this does not work for you
Try flashing PC ODIN but follow exactly the steps.
Click to expand...
Click to collapse
that what ive been doing and i received a error afterthat

Are you trying to flash a package that you have created or modified?

Im flashing kingdroid roms

So I'm gonna post my problem with pictures as I can't flash any roms .
Bear with me as the camera quality quite sucky as im using iPhone 4s.
Firstly I'm on recovery mode ;
Secondly , as what you see I've my ROM inside my SD card which is Kingdroid ;
Lastly, when I tried to flash the rom and it show me this

That's Android system recovery 3e, not CWM recovery.
And, ROM Manager is incompatible with Galaxy Note...........................

Are you having rooted device?
you need is CWM
download guide from last link on my signature, n follow it. It have instruction for both Root n CWM
N Rom manager won't work with Note.

Captivate won't load E:

Hello everyone,
I'm new to rooting and ROM's so I've been playing around since my Captivate's speaking is broken and of no use (I have a Note now.) I was using CornKernel and had installed CM 10.1 but the nightly I had installed was horrible and I wanted to revert to stable I HAD been running. Anyways, had a problem restoring the stable so I did a battery pull.
I could no longer get into CornKernel recovery, so I flashed Semaphore's ClockworkMod Recovery from CM's install directions. I now get this error I AM able to get into download, but not load any .zip's via this new recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you flashed an old version of cwm and it isn't compatible with cm10, I think.
if you can get into download mode and flash stock kk4 via usb and odin or heimdall, you should be able to recover. then you can do corn to get cwm back.
If you have a cwm backup of your stable 10.1 rom on a dropbox or google drive, don't try to recover it using Corn Kernel version of cwm. Do the full wipe, factory reset and flash stable CM10.0 plus appropriate gapps from Corn kernel. Then restore your backup, if you have it.

laughingT said:
you flashed an old version of cwm and it isn't compatible with cm10, I think.
if you can get into download mode and flash stock kk4 via usb and odin or heimdall, you should be able to recover. then you can do corn to get cwm back.
If you have a cwm backup of your stable 10.1 rom on a dropbox or google drive, don't try to recover it using Corn Kernel version of cwm. Do the full wipe, factory reset and flash stable CM10.0 plus appropriate gapps from Corn kernel. Then restore your backup, if you have it.
Click to expand...
Click to collapse
Thing is, I pushed via ODIN, Cornkernel again (same I originally used) and it loads, but then the status bar (phone) just sits at full and won't show the recovery menu. I then tried CWM and got the error in the image. So why won't Cornkernel work?
I'll try KK4 later tomorrow.

Like I said, I'm new at this.
I can't flash anything from internal SD at all. It just comes up and says can't read from E: I tried CornKernel again, the CWM kernel in the CM instructions, and a stock kernel. Both stock and the CM kernel (the pic in 1st post) go into recovery but don't do anything but give errors/invalid arguments. CornKernel just reboots after the splash screen. I've done the factory reset, dalvik and cache partition cleared.
stock:

from your screenshot, you are still on wrong version of cwm, I think. Corn doesn't use 3e.
Can you get into download mode? that is the yellow triangle with the shovelling androbot.

laughingT said:
from your screenshot, you are still on wrong version of cwm, I think. Corn doesn't use 3e.
Can you get into download mode? that is the yellow triangle with the shovelling androbot.
Click to expand...
Click to collapse
I didn't screenshot Corn. The 1st screenshot is Semaphore's ClockworkMod Recovery, found here, step 1: http://wiki.cyanogenmod.org/w/Install_CM_for_captivatemtd
2nd is a stock KK4 kernel I found as suggested in previous posts.
Yes, download mode works fine. ODIN detects the phone, but Windows won't let me put anything into the E: internal storage, or external for that matter.

The image you posted is stock 3e recovery on a kk4 rom, and not CWM recovery.
you need to install Corn kernel via usb with either odin or helmdall. You can find the corn kernel in captivate development forum. It will change your existing kk4 rom by replacing the kernel and will add CWM recovery that you need, but it will still be a kk4 rom, because it doesn't change the android OS.

I flashed Corn, this is what I get. Flashed it 3 times, same result.
Just sits there.

did you flash a complete kk4 rom, verify that you are rooted, before flashing corn? if not, then, do so. see TRusselo's thread in stickies for links to complete stock kk4. you will need to do it via usb. then get rooted, then flash corn.
the full rom will be a larger tar file that will take a long time to flash.
you might want to use full odin, rather than the oneclick versions. I am assuming you are using odin 1.85 for windows. you are going to put a tar file in the pda slot, then flash the complete stock kk rom first, then root the phone. wipe the cache, wipe the dalvik cache, and do a complete boot. then verify you have root, with an app like root checker, or run superuser to check - it wont run if your are not rooted.
if all that checks out, then go back to download mode, and flash corn from odin.

Bootloop directly after flashing ANY rom with Heimdall or Odin, partitions at fault?

Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!

vindikleuk said:
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Follow
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat and use PIT file, to repartition with the JVU 2.3.6
Check this out! Links to useful Guides and " Banned " Documentaries ​

vindikleuk said:
Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2

TeKnoGin said:
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Wow, how did I not think of that? Thanks!

Real issues trying to install a custom ROM (Cyanogenmod, etc...)

I have a real issue trying to install any zip files for ROMS.
At first I thought it was just the file I had downloaded so I downloaded another, and another, and another through a different browser (as I had read this might be an issue?).
Still nothing worked. I've put some screenshots below of what I am getting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I flashed a newer version of CWM (from the Cyanogenmod thread) and got this...
These are all stored on my external SD card which is where I am trying to boot from. The weird thing is that I can install the Alliance ROM but no others! I'm not sure whether its something to do with the Alliance one being a 4.3 ROM and the others all based around 4.4??
I really am out of ideas and can't find any solutions that seem to work, please can anyone help?

User does not have CWM recovery in image one its stock 3e.
Image 2 reads as a faulty file package .
Please try Philz Recovery .

Thanks.
I'm not quite sure what you mean by your first sentence but I will try Philz Recovery as well.

I've just flashed Philz Recovery but still no joy
I tried installing CM and OmniRom which was stored on the phone, and then also from the SD card but its still giving me the same messages?
I really am at a loose end here, I'm hoping there is a simple explanation for this????

Simple explanation reads as faulty zip files .
message says cannot open .
First sentence you did not have a custom recovery only stock recovery on image one .
Suggest format phone in recovery format sdcard system data cache then boot to download mode and flash stock rom .
With 63 posts you can ask in your roms thread or its Q&A thread ,

I see that you installed Philz Touch 5. Try latest 6.12.8: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 > This is based on CM11 tree, so it will work only with ROMs that hve the update binary from a CM11 ROM. So it will work with the stock CM11 you are trying to use. Try before you flash the ZIP to search it with ES File Explorer. If it appears the files inside it, than it should be OK. If it shows an error message saying that it is not a ZIP, you hve to download it again, because the file is not good. You have here:http://forum.xda-developers.com/showthread.php?t=2201860 some other issues and how to fix them. Hope I helped you.

I have to agree, go back to full stock, the modify the phone step by step. Root-cwm-custom rom
Sent from my GT-I9305 using xda app-developers app

Thanks for your replies guys.
This is odd, but I now have CM11 on my S3 LTE.
After installing Philz Recovery, I then reverted back to the latest version of CWM and tried to re run the file and this time it ran! I have no idea what was going on there?
Just in case this whole thing happens again if I want to flash an alternative ROM... What are the steps for returning the phone to a factory 'stock' state?

zim_zimmer said:
Thanks for your replies guys.
This is odd, but I now have CM11 on my S3 LTE.
After installing Philz Recovery, I then reverted back to the latest version of CWM and tried to re run the file and this time it ran! I have no idea what was going on there?
Just in case this whole thing happens again if I want to flash an alternative ROM... What are the steps for returning the phone to a factory 'stock' state?
Click to expand...
Click to collapse
See the sticky in General .

All sorted now, thanks guys
Sent from my GT-I9305 using Tapatalk