Database Info

ROM Manager error I NEED Help Plz

hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time

praramis said:
hey guys i had andromeda installed but messed the flash up by disabling lots of system stuff so i one clicked back to stock, rooted, installed rom manager like normal but every time i try to flash clockwork recovery mod it keeps telling me "An error occurred while downloading your recovery." and i cant install it so i can re-flash the rom plz help me i dont know what to do thx ahead of time
Click to expand...
Click to collapse
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.

I just had the same problem after doing countless ROM flashes in the past. Perhaps its something in their server preventing the download of CWM? Anyways, thanks for the .zip. Worked like a charm!

yes thank you very much for that zip u saved my life well appreciated

Keep that .zip on your HDD and you can bypass Rom Manager (and all the associated problems) altogether.

I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan

lanternslight456 said:
I have my phone rooted and unlocked. It's the AT&T Captivate but I'm using it on T-Mobile. I've had no problems so far with it.
I downloaded Clockwork's Rom Manager (v3.0.0.7) and tried to Flash ClockworkMod Recovery to begin experimenting with ROMs.
When I click on that it tells me "An error occurred while downloading your recovery."
I have over 4 gigs of memory left and I have 3 bars on 3g and WiFi going. No internet connection problems (i checked the net using market and using the browser, it works fine.)
What else could be causing the problems.
I'm just wanting to get a good stable rom going which ditches all the junk AT&T put on the phone.
Jonathan
Click to expand...
Click to collapse
Read the above solution...

I Can't get the update.zip file to work. After I reinstall packages is says E:Can't open /sdcard/update.zip (No such file or derectory) Installation aborted. I've tried it probably 20 times today with no luck.

Thank You
Nothing like flashing to find out it wasn't working. Thanks for making my day go better.

Noobie Mistakes
Just like everyone in this forum I'm having the same problem, I followed your instructions posted, but every time I reinstall packages in recovery mode a whole list of new problems comes up..... see below.
---Install from sdcard---
Finding update package...
Opening update package....
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
PLZ Help.......
Thanks

i have been fight this same thing for 2 days. im going to try the update.zip he posted i hope it works

npe didnt work. still says error downloading

tat2messiah said:
npe didnt work. still says error downloading
Click to expand...
Click to collapse
if the update.zip is already on your /sdcard/ then there is no reason to try and download/flash clockwork recovery.....thats what the update.zip IS

thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error

I'm having the exact same problem. After reading the development section I have decided to flash a custom rom from my stock rom. Installed "Rom manger" from market, then tried to run the "recovery" got the same error msg. Also uploaded the update.zip to my /sdcard the I got the below errors:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted

tat2messiah said:
thats what i thuoght but not true. even goin in normal recovery and selecting to install packages gets a error some about no such directory or something even though updat.zip is there even fix permissions gives a error
Click to expand...
Click to collapse
Did you flash back to stock JF6 first not JI6?

try this cuz this is what i did and the update.zip worked just fine for me
1. one click back to stock jf6
2. master clear
3. root with galaxy s one click root
(after the root there should be an update.zip in your sdcard)
4. replace the update.zip in the root of your sd card with the one here posted which is the clockwork recovery one and if you want while u do that you can throw in the rom that you want to flash in there as well to kill 2 birds with one stone
(i will re post the update.zip for cwm just in case)
5. power off the phone and boot into stock recovery and hit reinstall packages two times
6. you should now be in clockwork mod recovery and can now flash the rom of your choice
this is what i did and everything went smoothly but this is just me if this helps someone else plz let me know if this works for you
p.s. i will make a video if needed just ask

Try This
After flashing back to stock do a master clear from Odin3
Put update.zip onto internal sd
Boot into recovery
Reinstall packages
After boot enable USB debugging and mock locations
Get Rom Manager from market
Start Rom Manager
Flash ClockworkMod Recovery
Flash away

jhernand1102 said:
Put this on your internal SD card along with your ROM of choice. Reboot in to recovery and install packages 2 times. The second time it will be in clockwork recovery and you can flash your ROM.
Click to expand...
Click to collapse
You guys are making it harder then necessary, the update zip I posted is the clockwork recovery MOD, just flash stock, reboot into recovery and reinstall packages 2 times and you will be in the green clockwork recovery then you can install zip from sd and choose your ROM you placed on your internal sd card. No need to root every again as long as you keep this update zip handy.

I too am having problems with Rom Manager. I just wanted to change modems. No go. So I used the power button to go into Recovery mode, picked the modem file, flashed it then told the menu to reboot system.
Sent from my Samsung Captivate with Perception 10.3, Firebird2 v0.8 #77 Kernel, Firmware 2.2.1, Modem T9000UGJL2 using XDA App

Cant update ROM. What am I doing wrong

I have a NS unlocked and rooted. I have ROM Manager, busybox etc. I followed all the instructions but I can't update ROMs or the 2.3.3 update or CM7 nothing. Each time it starts to unpack or whatever it gets about 1/3 the way and aborts. Something about verifying signatures or something.
Very frustrating.
Thanx in advance
I Love The Smell Of Burnt Rubber Anytime

try to download the ROM again
sounds like the zip file is corrupted

What version Clockwork Recovery are you using? Try reverting back to a older version or something.
Verify the ROM's MD5 Hash using HashTab (Google it)

I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
what's the latest clockwork recovery? did you try 3.0.0.5?

Ya. The new ver is 3.0.2.4
I Love The Smell Of Burnt Rubber Anytime

hllywd said:
I've tried several times with downloads and now the latest clockwork and the version prior.
Samething always aborts, can't verify signature. Tried manual and through rom manager.
When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.
Thanks
I Love The Smell Of Burnt Rubber Anytime
Click to expand...
Click to collapse
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.

the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.
what you should do is...
1) go to bootloader
2)flash the clockwork recovery using fastboot
3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)
4)flash you new rom
just for u to have an idea. the recovery should be orange in colour.
option 2.
you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.

OK I played alot today and this is what happened.
After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.
At least I can get in it now.
Any ideas/thoughts/
Thanks and sorry for the long post.

Root, EP OTA?

I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.

luckdog said:
I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.
Click to expand...
Click to collapse
Try getting back into CW recovery and let me know how that goes. If so then just download superuser and you got it.

No root
I can boot into CWR after using ODIN to put it on once and under voodoo controls app it shows my phone as being voodoo on all partitions, just don't have root. I knew the OTA would kill root, was just hoping thier was a quick fix out there like just flashing a kernel. The phone is pretty snappy though with imoysens kernel running voodoo and using ADW as the launcher. Like what I see so far.

luckdog said:
I can boot into CWR after using ODIN to put it on once and under voodoo controls app it shows my phone as being voodoo on all partitions, just don't have root. I knew the OTA would kill root, was just hoping thier was a quick fix out there like just flashing a kernel. The phone is pretty snappy though with imoysens kernel running voodoo and using ADW as the launcher. Like what I see so far.
Click to expand...
Click to collapse
Someone didn't read the instructions for properly installing the leaked OTA?
BEFORE YOU ODIN BACK TO EE4, MAKE SURE YOU HAVE THE SU FLASHABLE ZIP, THE OTA UPDATE AND IMOSEYON'S KERNEL ON YOUR SDCARD!
Make sure the update file is renamed to "update" and that it's on the root of your sdcard. (not in any folders or anything)
Odin back to EE4. Reboot normally.
Turn the phone off, then reboot into Stock Recovery and run the update.
Once the update finishes and the phone boots regularly. Reboot into Download Mode and plug the phone into the computer.
Start Odin, Uncheck "Auto Reboot", select PDA, NOT PHONE!
Click on the PDA tab and find your recovery file then click "start."
Once it is done and you see the word "PASS" on Odin, unplug the usb cable and press down all three buttons to boot into recovery (volume up, home, power)
Once in recovery, wipe cache, wipe dalvik, mount /system and flash the SU flashable zip.
Go back and wipe cache and dalvik again, mount /system again and flash the kernel.
After that, your recovery will stick and you're good to go. You are now rooted and running on EP4D.
Here is the flashable Super User zip. http://www.multiupload.com/V6R1RZJPXV

luckdog said:
I just finished putting on Clockwork recovery after the OTA and then flashed Imosyen's 4.0 kernel. During the process I heard the Voodoo stuff take place, but upong rebooting my phone I don't have root. I read in these boards on the EE4 OTA that this should have worked, any ideas and has anyone got thier phone rooted on the new OTA?
Thanks.
Click to expand...
Click to collapse
Did you install superuser? I bet you are rooted, but you don't have the tools installed to use it.
Sent from my SCH-I510 using Tapatalk

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A

Thanks!!! Rooted
spc_hicks09,
Thanks sir, I started from CWR and followed the instructions and it worked! The original instructions I got yesterday didn't have any information on rooting, just on how to install the update. I appreciate the help and if the "spc" in your username represents a military rank, thanks for serving!

luckdog said:
spc_hicks09,
Thanks sir, I started from CWR and followed the instructions and it worked! The original instructions I got yesterday didn't have any information on rooting, just on how to install the update. I appreciate the help and if the "spc" in your username represents a military rank, thanks for serving!
Click to expand...
Click to collapse
You're very welcome for the instructions! Yes the Spc in my name is my rank and thank you for your support!

most if not all root issues can be fixed by simply flashing superuser in CWM (you can get the latest .zip from the dev ChainsDD's superuser site), then downloading/updating it in the market if it doesn't show up
blazing through on my 4G Droid Charge

If interested, the CWM version found here is already rooted.

[Q] Updating to 4.1.1 OTA

I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.

Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button

Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks

Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery

So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?

TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.

Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2

What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app

joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.

sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2

mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.

The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree

z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!

The phone will not install a Verizon update with a custom recovery installed.