[Odin] Froyo leaked packaged custom ROMs w/root and clockwork **UPDATED**3/25

Quick question, on step 1 how do I put the Update.zip onto my sd card? I apologize if there is an obvious answer =)
 
ok. i have been Adrynaline's thread for 2 hours trying o get the 2.9.1 patch working. I have downloaded the 2.9.1 zip and it's on my sd card, but when i go to recovery apply sd update it fails every time. I flashed the last 2.9 from this thread last night and am having random reeboots and my contacts won't use the back button. Any suggestion ?

Delete the contacts icon and crate a new shortcut for it.

As for the random reboots, 2.9.1 should fix that. What the issue with the CWM failure? Where are you failing?
 
Quick question, on step 1 how do I put the Update.zip onto my sd card? I apologize if there is an obvious answer =)

Just put it on the sd card. Don't create a folder and place it there, as it should be in what's called the "root: of your card. So if your card is your G drive, for example, after you mount the card to your pc, then drop it right in G:
 
  • Like
Reactions: DreMan1990
ok. i have been Adrynaline's thread for 2 hours trying o get the 2.9.1 patch working. I have downloaded the 2.9.1 zip and it's on my sd card, but when i go to recovery apply sd update it fails every time. I flashed the last 2.9 from this thread last night and am having random reeboots and my contacts won't use the back button. Any suggestion ?

If you are going to recovery and you go to red directly, you do not need to hit apply sdcard:update.zip. When you boot directly to red cwm-all just forget update.zip even exists. Follow DroidXcon's directions in this thread http://forum.androidcentral.com/ver...-clockworkmod-recovery-w-screen-captures.html
When you boot to red it is as simple as using the volume buttons to scroll to install zip from sd card, hit the power button, scroll to choose zip from sd card, power button, scroll to the 2_9_1 zip, power button. After install hit the menu soft key or the search soft key to go back one menu page until you are at the cwm-all main page where reboot system now will be highlighted, power buttton and wait for the phone to reboot
 
Way to go SuD. I always like to link everyone to DXC's clockwork thread to have them install cwm-all right after using one of the 2.9 packages. Eliminates a lot of headaches later on with blue recovery and update.zip.
 
"insufficient storage"

Hey guys I had issues with gps and wifi and decided to Odin back to the eb01 leak(deodexed/debloated). Long story short the flash went fine and once I started to restore apps from the Market I kept getting a "Install failed insufficient storage" so I went to menu/settings/sd card and phone storage and to my surprise Internal Phone Storage was 0mb. I have since completely rewiped and tried odin again with the same results. The device is reading the sd card and all other aspects seem fine. Any thoughts?
 
Just put it on the sd card. Don't create a folder and place it there, as it should be in what's called the "root: of your card. So if your card is your G drive, for example, after you mount the card to your pc, then drop it right in G:

And its okay if its still zipped on the sd card? Its labeled "update"
 
Just put it on the sd card. Don't create a folder and place it there, as it should be in what's called the "root: of your card. So if your card is your G drive, for example, after you mount the card to your pc, then drop it right in G:

Hey SuD, not sure about you, but I think if people are going to 2.9 I think it is easier and better to have them skip the update.zip step, link them to DXC's clockwork thread, have them flash cwm-all through ODIN first, close ODIN, reopen ODIN, hold volume down button to re-establish connection to ODIN, then flash DXC's package. No need to bother with update.zip or having to explain where it goes. Easy peasy, winner winner chicken dinner.
 
And its okay if its still zipped on the sd card? Its labeled "update"

Hey DreMan, finally caught up with you. My recommendation is not even worry about update.zip. After you go to 2.9, you won't even need it, so why go through the step of installing it. Instead, download this file MEGAUPLOAD - The leading online storage and file delivery service to your computer, but don't unzip or extract this file, just leave it like it is. Then when you get to step #12, put this cwm-all file in the PDA section, it will take 7 seconds to install, close ODIN, unplug usb cord from the phone, open ODIN again, connect phone to usb while holding down volume button, then go back to step 12 and follow the instructions exactly from there (don't forget to follow the instructions in post #2 for extracting the 2.9 .tar.md5 file from the 2.9 package you downloaded. After you reboot your phone you will now have cwm-all and will boot directly )to it in the future. For a complete description of what cwm-all is and how you will use it in the future, read this thread: http://forum.androidcentral.com/ver...-clockworkmod-recovery-w-screen-captures.html
 
Hey guys I had issues with gps and wifi and decided to Odin back to the eb01 leak(deodexed/debloated). Long story short the flash went fine and once I started to restore apps from the Market I kept getting a "Install failed insufficient storage" so I went to menu/settings/sd card and phone storage and to my surprise Internal Phone Storage was 0mb. I have since completely rewiped and tried odin again with the same results. The device is reading the sd card and all other aspects seem fine. Any thoughts?

I've seen this issue before, I'm just drawing a blank on the fix for it. It will take me a little while of searching the forums for the answer.
 
And its okay if its still zipped on the sd card? Its labeled "update"

Correct. Keep it zipped. It will be update.zip on the phone. If you're looking at your pc and are looking at your SD card and only see the word update instead of update.zip, that's okay. You have your extensions turned off.

Landshark

I'm with you on this. But I try to keep to the version of answers that are in parallel to the questions so as not to add additional confusion. But if we can use Odin for all things related to the flashing and upgrading of the phones, I see the point of using nothing but Odin.

DreMan1990 You're not doing anything wrong or our of sync if you continue to use update.zip. If you don't put it on your SD card, you're not doing anything wrong, and can actually put another file there that prevents you from having to do multiple steps to get to the correct version of CWM when/if you ever need it. So, for now, continue your path with update.zip.


Landshark I'll try and get folks on CWM ALL from this point on when the issues/questions arise.

SuD
 
Hey guys I had issues with gps and wifi and decided to Odin back to the eb01 leak(deodexed/debloated). Long story short the flash went fine and once I started to restore apps from the Market I kept getting a "Install failed insufficient storage" so I went to menu/settings/sd card and phone storage and to my surprise Internal Phone Storage was 0mb. I have since completely rewiped and tried odin again with the same results. The device is reading the sd card and all other aspects seem fine. Any thoughts?

Topher74,

Go with Landshark on this one. I've not seen the complaint on this issue before, but if he has, he will find it and provide the solution that also worked for the previous complaint. If not, I have a thought on what will fix it, but would rather wait until Landshark comes back with a reply.

Folks, I'm in and out throughout the day, so please accept my apologies ahead of time if I'm not able to reply quickly enough, of don't seem to keep connected to those that I'm already helping.

SuD
 
Topher74,

Go with Landshark on this one. I've not seen the complaint on this issue before, but if he has, he will find it and provide the solution that also worked for the previous complaint. If not, I have a thought on what will fix it, but would rather wait until Landshark comes back with a reply.

Folks, I'm in and out throughout the day, so please accept my apologies ahead of time if I'm not able to reply quickly enough, of don't seem to keep connected to those that I'm already helping.

SuD

yeah all my search results yielded nada...except one recommendation and that was to odin back to DI01 package. Im gonna hold out and see if Landshark or anyone else can confirm this as a working solution. Ive been around android since the begining and when i would have to ruu on and htc or sbf a moto device Ive personally never had these issues...the Sammy devices are a whole new animal to me lol...
 
yeah all my search results yielded nada...except one recommendation and that was to odin back to DI01 package. Im gonna hold out and see if Landshark or anyone else can confirm this as a working solution. Ive been around android since the begining and when i would have to ruu on and htc or sbf a moto device Ive personally never had these issues...the Sammy devices are a whole new animal to me lol...

this usually happens when you have enabled voodoo lagfix and you try to flash a nonvoodoo kernel over, have you ever messed with voodoo?
 
  • Like
Reactions: Landshark
this usually happens when you have enabled voodoo lagfix and you try to flash a nonvoodoo kernel over, have you ever messed with voodoo?

Yes! I had previously been running sc 2.9.1 with the vodoo eb16 kernel and the wifi and gps were borked for me (no themes or other mods maybe a corrupted zip) so I proceeded to Odin flash back to the eb01 debloated/deodexed leak. Then theres when the internal storage errors began.
 
Yes! I had previously been running sc 2.9.1 with the vodoo eb16 kernel and the wifi and gps were borked for me (no themes or other mods maybe a corrupted zip) so I proceeded to Odin flash back to the eb01 debloated/deodexed leak. Then theres when the internal storage errors began.

ok you have two options,

either use clockwork and flash another voodoo kernel and make sure lagfix is enabled

or

flash the EB01 fix all with odin
 
Correct. Keep it zipped. It will be update.zip on the phone. If you're looking at your pc and are looking at your SD card and only see the word update instead of update.zip, that's okay. You have your extensions turned off.

Landshark

I'm with you on this. But I try to keep to the version of answers that are in parallel to the questions so as not to add additional confusion. But if we can use Odin for all things related to the flashing and upgrading of the phones, I see the point of using nothing but Odin.

DreMan1990 You're not doing anything wrong or our of sync if you continue to use update.zip. If you don't put it on your SD card, you're not doing anything wrong, and can actually put another file there that prevents you from having to do multiple steps to get to the correct version of CWM when/if you ever need it. So, for now, continue your path with update.zip.


Landshark I'll try and get folks on CWM ALL from this point on when the issues/questions arise.

SuD

Hey SuD. I completely understand wanting to keep things simple, but if update.zip is going to be completely useless and not used, why have people go through the step of installing it? If people used DXC's packages and already have update.zip they can leave it there and not go through the step of deleting it. Because DXC was unable to include cwm-all in his 2.9 packages, everyone who uses them is eventually going to have to flash the cwm-all file if they are ever going to have to use cwm to flash themes, patches, or mods. Having anyone who used DXC's ODIN packages flash cwm-all at step 12 before flashing the 2.9 tar file saves them the extra steps of powering off the phone, pulling the battery, and opening ODIN after they have rebooted the phone after flashing the 2.9 file. They have already done those steps to get to step 12, and flashing cwm-all only takes 7 seconds. Danny go ahead and chime in. These are your packages and your hard work. Whatever you say goes. Tell me how you would prefer to guide new rooters and that is how I will do it.
 
i would have them not delete update.zip and still use cwm all,,,incase a mistake is made and they flash a kernel that removes cwm all then they have update.zip to fall back on in a pinch
 
this usually happens when you have enabled voodoo lagfix and you try to flash a nonvoodoo kernel over, have you ever messed with voodoo?

Nice catch. I was having a senior moment and couldn't remember where the posts on that problem were.