I rooted my Motorola Milestone with Super One Click, then installed ROM Manager. I did flash CockworkMod recoveries but I could not do the backup or installation of new Custom ROM. The phone always was back to the screen with the yellow exclamation inside the white triangle. If I use VOlume + Up button, it will appear the recoeveries with four options: reboot system, wipe data/factory reset, apply update.zip and wipre card partition with the info: E:cannot open cach/recoveries/command. I did try to apply updated.zip but it failed and say that it cannot verify the signature and installation aborted.
Could you please help? Thanks
Phone: Milestone rooted with android 2.2
Root: by Super Once Click
ROM manager: newest version
hwithv said:
I rooted my Motorola Milestone with Super One Click, then installed ROM Manager. I did flash CockworkMod recoveries but I could not do the backup or installation of new Custom ROM. The phone always was back to the screen with the yellow exclamation inside the white triangle. If I use VOlume + Up button, it will appear the recoeveries with four options: reboot system, wipe data/factory reset, apply update.zip and wipre card partition with the info: E:cannot open cach/recoveries/command. I did try to apply updated.zip but it failed and say that it cannot verify the signature and installation aborted.
Could you please help? Thanks
Phone: Milestone rooted with android 2.2
Root: by Super Once Click
ROM manager: newest version
Click to expand...
Click to collapse
Dude, ROM Manager does NOT work on Milestone. You need to flash a Vulnerable Recovery using RSD Lite, install Androidiani Open Recovery, go from there:
http://forum.xda-developers.com/showthread.php?t=983516
skadude66 said:
Dude, ROM Manager does NOT work on Milestone. You need to flash a Vulnerable Recovery using RSD Lite, install Androidiani Open Recovery, go from there:
http://forum.xda-developers.com/showthread.php?t=983516
Click to expand...
Click to collapse
Thanks, dude. In the list of ClcokwordMOd, i find out there is a row for Milestone. Click on it, I also am able to download a file of Recoveries which is specific for milestone. But it does not work.
One thing I would like to raise here is that after i cannot use update.zip any more. Cuold you please explain why? It also says "cannot verify signature"
Thanks
Because your phone does not have the vulnerable recovery installed. Look at the link I posted. It has everything you need to get up and running. Don't hesitate to ask if you have any questions.
Sent from my Milestone using XDA Premium App
I did do as your instruction. But as i did the backup, it is stuck. the phone went to "system:dumping..." and stayed there in one hour.
I flashed the recoveries sucessfully. please advise
hwithv said:
Thanks, dude. In the list of ClcokwordMOd, i find out there is a row for Milestone. Click on it, I also am able to download a file of Recoveries which is specific for milestone. But it does not work.
One thing I would like to raise here is that after i cannot use update.zip any more. Cuold you please explain why? It also says "cannot verify signature"
Thanks
Click to expand...
Click to collapse
The Milestone mentioned in ROM Manager / clockworkmod is probably the Alltel Milestone, which in reality is a droid 1.
Now that you have installed cwm, you have to remove it from your phone and then install Androidiani openrecovery. Before that you need to install vulnerable recovery from here using rsdlite.
Note that it may take more than one try to get cwm out of the system.
hwithv said:
I did do as your instruction. But as i did the backup, it is stuck. the phone went to "system:dumping..." and stayed there in one hour.
I flashed the recoveries sucessfully. please advise
Click to expand...
Click to collapse
What did you end up doing after it hung for an hour? Because if you haven't flashed a custom ROM, you should still be able to boot (rooted) and you can try the Nandroid backup again.
Sent from my Milestone using XDA Premium App
skadude66 said:
What did you end up doing after it hung for an hour? Because if you haven't flashed a custom ROM, you should still be able to boot (rooted) and you can try the Nandroid backup again.
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
I take the batterry out of the phone and restart it again. It works normally but the backup is not done because i do not find out the backup under Openrecoveries folder. I did try the second time but it happed again and i had to take the battery out of the phone and restart.
please help
I actually had the same mistake as you before (using ROM Manager on our Milestone).
I recommend this:
1. Backup your SD card content
2. Reformat your SD (slow format)
3. Place the AOR 3.3 (Androidiani Open Recovery) files back in (use a fresh download if possible)
4. Perform Nandroid backup again
Note that there will be no "backup" content in your OR folder. Instead, you will see a new "nandroid" folder in your sd root.
Thanks dude. I find out the solution. I wipe all data + cache, then I download a fresh recoveries and then i did the backup again. It works well.
CWM problems
I used androidiani and flashed cm7. then i tried ROM manager while i was unaware that it messes with the milestone. now i cant enter recovery at all!!!! Help!
lspdv1991 said:
I used androidiani and flashed cm7. then i tried ROM manager while i was unaware that it messes with the milestone. now i cant enter recovery at all!!!! Help!
Click to expand...
Click to collapse
You have to flash vulnerable recovery again from here.
lspdv1991 said:
I used androidiani and flashed cm7. then i tried ROM manager while i was unaware that it messes with the milestone. now i cant enter recovery at all!!!! Help!
Click to expand...
Click to collapse
You should not use ROM Manager to do the backup or flash for Milestone. please use Open Recovery 3.3. Download it and please delete CWM folder also. Please wipe data/facotry reset for doing backup or flash. (IMPORTANT). It will work.
Related
I really need help i used to have paragon rom then i installed phoenix but i did not liked it so i tried to go back to paragon but when i used odin to go back to stock. I rooted my phone but when i installed rom manager to install paragon it doesnt let me rom manager tells me that an error has ocurred when i tried the clockword recovery
Sent from my SAMSUNG-SGH-I897 using XDA App
pumasmedina7 said:
I really need help i used to have paragon rom then i installed phoenix but i did not liked it so i tried to go back to paragon but when i used odin to go back to stock. I rooted my phone but when i installed rom manager to install paragon it doesnt let me rom manager tells me that an error has ocurred when i tried the clockword recovery
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Do you have 3 button recovery?
If you do, dont bother installing, ROM Manager, you wont need it. Just copy the ROM and CWM's update.zip to your phone, 3 button into recovery select reinstall packages, you'll then "go back", reinstall packages again, then you reboot into recovery, and install your ROM
Where can i get that
Sent from my SAMSUNG-SGH-I897 using XDA App
If u ca. Help me plz call me at 8057321104 i will really apreciated
Sent from my SAMSUNG-SGH-I897 using XDA App
pumasmedina7 said:
I really need help i used to have paragon rom then i installed phoenix but i did not liked it so i tried to go back to paragon but when i used odin to go back to stock. I rooted my phone but when i installed rom manager to install paragon it doesnt let me rom manager tells me that an error has ocurred when i tried the clockword recovery
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Okay. So, you were running Paragon, you flashed Phoenix, and you want to go back to Paragon.
Hopefully you made a backup of your ROM before you flashed Phoenix. You then used Odin to flash to stock, rooted, and installed ROM manager.
If you flashed back to UCJF6 (Android 2.1) you won't be able to restore a backup based on Froyo 2.2.1, which is what Paragon is based on. That's why you're getting an error. You're going to need to do a fresh flash of Paragon. Place the base Paragon ROM on your SD card.
Use ROM Manager to flash the base Paragon ROM. Now, on the base Paragon ROM, use ROM Manager to restore your backup.
I'm hoping you did everything one should do prior to returning to stock with Odin, as in creating your backup, disabling your lagfix, etc, before using Odin to get back to stock. Also, take into account that you need to have the same kernel installed on the newly flashed ROM and the ROM you're attempting to reinstall. So, if you had a custom kernel installed when you made your backup of Paragon, make sure to flash that kernel on your newly installed base Paragon before you try to restore.
Good luck.
The sad thing is that i cant use rom manager i rooted my but it doesnt let me use clockword recovery
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm having a problem with rom manager as well.i get the error downloading recovery. I may try to flash an older version I have on my laptop. I'm using the stock rom and rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App
I too am having a similar problem, I'm on stock and trying to get ROM manager to work but it won't let me flash ClockworkMod Recovery or even an older version. As stated already I get the error message "An error occurred while downloading your recovery." However, it seems that if I select my phone as an i9000 Galaxy S, ClockworkMod will download, but it won't work.
And for the record, using the 3-button recovery I only get the options of:
reboot phone
reinstall packages (which says the update.zip is a bad file and won't open)
delete all user data
delete cache data
I should add that this is the first time I've seen this situation and usually I'm able to "install .zip from sd card" but in this case I can't.
pumasmedina7 said:
The sad thing is that i cant use rom manager i rooted my but it doesnt let me use clockword recovery
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My apologies. I should have read your original post a little closer.
You can try installing clockwork recovery manually via this method:
Take the attached zip file and rename it update.zip. Connect your phone via USB to your computer. You'll notice there's already an update.zip file on your phone. That's the update.zip which was used to give you root permission. Take the newly named update.zip file (clockworkmod) and replace the update.zip (root) on your phone's sd card.
Now, disconnect your phone from your computer, and power down your phone. Press the volume up AND volume down button at the same time, then hold down power. Keep holding all three buttons down. The ATT screen should pop up once, but keep holding down the buttons. The ATT screen will pop up again, and now, you can let go. This should get you to the stock recovery screen. Use your volume down button to scroll down "reinstall packages". Use the power button to select the option. This will install clockworkmod on your phone. Now, it'll come back to the same stock recovery screen. Tick down once again to "reinstall packages" until clockworkmod pops up.
I'm not sure if ROM manager will work with this version of clockworkmod, as I stopped using ROM manager a while ago. I just reboot into recovery manually and navigate clockworkmod with phone's physical buttons. I guess you can give it a go.
If this doesn't work, something might have happened with with the odin flash, or a lagfix wasn't disabled prior to going back to stock, or Dalvik cache wasn't wiped, or your cache partition wasn't wiped, etc, and you might be out of luck.
When I want to flash a ROM, I always make a backup, copy the backup onto my computer, backup my apps with Titanium Backup, copy that backup onto my computer, disable any lagfixes, flash to stock using ODIN, master clear, root, install clockworkmod, copy the new ROM zip file to my SD card, do a factory reset in clockworkmod, wipe cache partition in clockworkmod, and wipe Dalvik cache in clockworkmod, then install my new ROM.
I've never had any problems using those steps. Good luck.
guys the files you need and most answers are here
http://forum.xda-developers.com/showthread.php?t=942217
woops he posted before me but yea hes right
Thanx alot mexican american i dowloaded the file an my phone is working really good with paragon again thanx a lot
Sent from my SAMSUNG-SGH-I897 using XDA App
pumasmedina7 said:
Thanx alot mexican american i dowloaded the file an my phone is working really good with paragon again thanx a lot
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You're welcome.
I was bout to give up on my phone but u saved my life thanx again
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok so I'm new to flashing a ROM, and Im having a little problem with ROM Manager. Ive been trying to make a backup of my current ROM prior to flashing to a new ROM. However when I choose the option to backup current ROM it shows me the name of the backup and then reboots my device (Samsung Captivate) into recovery mode. Not really sure what it wants me to do there so I choose to reboot the device, I then check to see if it made the backup and nothing??? Im not sure what it is that Im doing wrong but Im sure I must be missing a step. The phone is rooted, running 2.2 other than that nothing else has been moded. If any of you can help me I would appreciate it, I just dont want to move forward with flashing a ROM before Ive backed up the current ROM. I have made a backup of all apps and data using Titanium.
Xanaki said:
Ok so I'm new to flashing a ROM, and Im having a little problem with ROM Manager. Ive been trying to make a backup of my current ROM prior to flashing to a new ROM. However when I choose the option to backup current ROM it shows me the name of the backup and then reboots my device (Samsung Captivate) into recovery mode. Not really sure what it wants me to do there so I choose to reboot the device, I then check to see if it made the backup and nothing??? Im not sure what it is that Im doing wrong but Im sure I must be missing a step. The phone is rooted, running 2.2 other than that nothing else has been moded. If any of you can help me I would appreciate it, I just dont want to move forward with flashing a ROM before Ive backed up the current ROM. I have made a backup of all apps and data using Titanium.
Click to expand...
Click to collapse
When it goes into recovery, is it the ClockWorkMod recovery menu? Green text? If it isn't getting there you need to install it from ROM manager first or just install it off an update.zip file that is floating around XDA and other sites. Once that is setup, you can run the backup through ROM Manager. It should boot into a recovery mode and then start doing a lot of writing of files to your new backup directory.
Post back if you are still having problems.
I did select the option for flashing ClockWorkMod recovery and chose the Captivate as my device. It did say that it sucessfully downloaded the file and Im assuming that it meant it installed it. And to answer your question I think I can safely say that no its not clockwork recovery when it reboots as it does say at the top of the screen "Android Recovery" so Im pretty sure that ClockWork is not installed. But I will look for that update.zip file and try to install it that way...
Xanaki said:
I did select the option for flashing ClockWorkMod recovery and chose the Captivate as my device. It did say that it sucessfully downloaded the file and Im assuming that it meant it installed it. And to answer your question I think I can safely say that no its not clockwork recovery when it reboots as it does say at the top of the screen "Android Recovery" so Im pretty sure that ClockWork is not installed. But I will look for that update.zip file and try to install it that way...
Click to expand...
Click to collapse
I'm sorry, you are looking for recovery-update.zip. I would try to run the ROM Manager install again and see what happens. I haven't had to play with the Android Recovery in quite some time but if the recovery-update.zip file is in the root of your sd card, you should be able to install it through the Android recovery. I'll keep looking. If I can find the file on my phone, i'll post it. Good luck.
If this is your first time booting into CWM recovery it will go to the base recovery first. Then you need to "reinstall packages". That will replace the recovery file with the CWM recovery file and return to the main menu. Then choose reintall packages one more time and it should bring you to CWM recovery instead of the base one. From then on it should bring you directly to the CWM recovery.
As for the backup it's done from CWM recovery. So once you get thru the steps above you will see backup and restore options on the recovery menu and you can go thru that process.
There may be some help in here: http://forum.xda-developers.com/showthread.php?t=734163
First try to flash it again through ROM Manager.
mxracer101 said:
If this is your first time booting into CWM recovery it will go to the base recovery first. Then you need to "reinstall packages". That will replace the recovery file with the CWM recovery file and return to the main menu. Then choose reintall packages one more time and it should bring you to CWM recovery instead of the base one. From then on it should bring you directly to the CWM recovery.
As for the backup it's done from CWM recovery. So once you get thru the steps above you will see backup and restore options on the recovery menu and you can go thru that process.
Click to expand...
Click to collapse
DUH...I thought there was another step. Thanks mxracer. Give that a go and see if you get what you are looking for.
Thanks!! Trying that now
Ok still having a problem, I followed the instructions just as posted but this is what I get:
-- 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.
Ok so what do I do? Im thinking I need to find that recovery-update.zip you were talking about?
Xanaki said:
Ok still having a problem, I followed the instructions just as posted but this is what I get:
-- 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.
Ok so what do I do? Im thinking I need to find that recovery-update.zip you were talking about?
Click to expand...
Click to collapse
That update.zip should have been placed there by ROM Manager. Possibly try uninstalling & reinstalling ROM manager. Else, that update.zip should be somewhere. I'd grab the one off my phone but I'm not entirely sure which one it is. My ROM already had CWM with it. I'll try to look for a correct update.zip but I'm at work so I'm not going through XDA all day.
trekie86 said:
That update.zip should have been placed there by ROM Manager. Possibly try uninstalling & reinstalling ROM manager. Else, that update.zip should be somewhere. I'd grab the one off my phone but I'm not entirely sure which one it is. My ROM already had CWM with it. I'll try to look for a correct update.zip but I'm at work so I'm not going through XDA all day.
Click to expand...
Click to collapse
you missed the part where he said he was running 2.2?
2 words:
3e recovery
trekie86 said:
DUH...I thought there was another step. Thanks mxracer. Give that a go and see if you get what you are looking for.
Click to expand...
Click to collapse
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
Not sure what it is that you're saying I need to do, what is 3e recovery?
Xanaki said:
Not sure what it is that you're saying I need to do, what is 3e recovery?
Click to expand...
Click to collapse
this will explain and provide a fix for you....
http://forum.xda-developers.com/showthread.php?t=909213
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
You're right, I did miss that. Haven't had to do anything with 3e recovery before. Xanaki, are you on Rogers with their official 2.2 or the leaked AT&T 2.2?
Pirateghost said:
you missed the part where he said he was running 2.2?
2 words:
3e recovery
Click to expand...
Click to collapse
I missed it too. The above post regarding 3e recovery is what you need to do, one of the phones I have I need to do the same process after flashing back to stock. Sorry for the confusion.
Been having a similar issue when it takes you to stock recovery, I hold down both volume buttons and power until I see AT&T let go of power it usually takes me to clockwork recovery menu, I then select whatever I want to do backup, recover, or install from sd.
I don't know why it started doing that but that's what I found works. Hope it helps.
trekie86 said:
You're right, I did miss that. Haven't had to do anything with 3e recovery before. Xanaki, are you on Rogers with their official 2.2 or the leaked AT&T 2.2?
Click to expand...
Click to collapse
Im on the leaked AT&T version of 2.2 not Rogers. I haven't had the chance yet to try the recovery method mentioned but I plan on doing so today, I will update as to if this works or not. Also I did read somewhere that flashing a new Kernal might resolve this issue, I do have SGS Kernal Flasher but I dont have another Kernal to flash to...
Hi,
I'm trying to get out off the stock rom, but I just can't
What am I dooing wrong.. (No SD card is used)
1) install CWM 4.0.0.5 (Int)
2) nandroid backup
3) Mount USB, to get the backup on to the PC
4) Smartflash Baseband 0606
5) NVFLASH stock rom (just replacing the recovery with CWM 4.0.0.5)
6) boot into CWM
7) Wipe Data/factory, cache, dalvik
8) Install zip (CM_p990_full-50), have also tried build 43
9) Reboot
10 ) crying... everytime it starts with FC of LGE everything. (10-13 popups, and endless loop in LG.SetupWizard)
Yes, I know i'm a NOOB, but this just makes no sence to me...
Please advice....
Can you install any other ROM, say the MoDaCo vanilla?
Rusty! said:
Can you install any other ROM, say the MoDaCo vanilla?
Click to expand...
Click to collapse
Yes, and it seams to work.
Then I did a Backto ext3 from cwm, and then tryed wipe and install CM. but now noting happers, it says "installing" but nothing like "writing to ...." and after that I'm stuck on the LG logo on an reboot.
Can't even restore back to my old rom....
so back to an NVFLASH for me and a restore...
Anyone.... Please HELP....
OK, that's proper weird.
From memory (and it's not that great as I'm on the Amigos) you wont see much other than 'installing..." when flashing CM, so wouldn't worry about that.
Did you do anything in recovery before applying the back to EXT3 patch? If so it might not have worked, as it needs /system and /data to be unmounted (found that one out for myself lol)
i had the same issue, try to reflash original cwm from ROM manager and youll be able to install cm7
Sent from my Optimus 2X using XDA Premium App
cokeman0 said:
10 ) crying... everytime it starts with FC of LGE everything. (10-13 popups, and endless loop in LG.SetupWizard)
Click to expand...
Click to collapse
I've no idea what you are doing. But I'm pretty sure there isn't supposed to be any "LG.SetupWizard" in CM7.
^ What he said. There is a SetupWizard.apk and an LGEServices.apk but no LG.SetupWizard. Or LG anything else, for that matter.
Hi,
Updateded Rom Manager.
Installed CWM 3.2.0.0
Did an CM_52 via Rom Manager (Selecting Backup and both Wipe's)
No Google Apps (As they are still failing to download via Rom Manager.
Booting Cyanogen mod 7
AND YES YES YES YES YES YES... this time it worked!
Boot to CWM and install ZIP (gapps-gb-20110613-signed)
And now time to play.... Thanks for the help..
Guess CWM 3.2.0.0 was the fix...
cokeman0 said:
Hi,
Updateded Rom Manager.
Installed CWM 3.2.0.0
Did an CM_52 via Rom Manager (Selecting Backup and both Wipe's)
No Google Apps (As they are still failing to download via Rom Manager.
Booting Cyanogen mod 7
AND YES YES YES YES YES YES... this time it worked!
Boot to CWM and install ZIP (gapps-gb-20110613-signed)
And now time to play.... Thanks for the help..
Guess CWM 3.2.0.0 was the fix...
Click to expand...
Click to collapse
glad to hear that AFAIK cwm 3 series work better so far.
Sent from my Optimus 2X using XDA Premium App
I have the same problem coming from stock.
I have CWM 4.0.0.5 external installed. Took nandroid backup, wiped data and cache, flashed nightly 52, flashed gaaps and everything went fine but when I reboot I get stuck on the CM7 logo in an endless bootloop.
Thankfully I could restore stock but what I am doing wrong?
Try cwm 3.2.0.0 saved me.
Sent from my Optimus 2X using XDA App
cokeman0 said:
Try cwm 3.2.0.0 saved me.
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
That´s what I did and it worked like a charm, wonder why though?
cokeman0 said:
Hi,
Updateded Rom Manager.
Installed CWM 3.2.0.0
Did an CM_52 via Rom Manager (Selecting Backup and both Wipe's)
No Google Apps (As they are still failing to download via Rom Manager.
Booting Cyanogen mod 7
AND YES YES YES YES YES YES... this time it worked!
Boot to CWM and install ZIP (gapps-gb-20110613-signed)
And now time to play.... Thanks for the help..
Guess CWM 3.2.0.0 was the fix...
Click to expand...
Click to collapse
I have kindly the same problem
When I want to root CM7 always says installation aborted
but i want follow the same strategy
how i can
Updateded Rom Manager.
Installed CWM 3.2.0.0
Install CM via Rom Manager, or download CM and do it yourself
Boot into recovery
Mount USB, move the CM to the SD card. Wipe user, cache and delvik
install ZIP and select CM, and remember to put gapps on the SDCARD and install that before rebooting...
------ I didn't realise there is page 2 and the question is solved...
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860
Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.
Ok, I have ROM Manager premium installed, rooted, etc. I'm running 2.2 version UVKB5 on my T Mobile Samsung Vibrant.
I've selected the option to Flash ClockworkMod Recovery for the "Samsung Vibrant" and it won't boot to CWR. If I select reintall packages, it fails every time.
Help!
did you install both the free and premium version of rom manager?
kcfried said:
Ok, I have ROM Manager premium installed, rooted, etc. I'm running 2.2 version UVKB5 on my T Mobile Samsung Vibrant.
I've selected the option to Flash ClockworkMod Recovery for the "Samsung Vibrant" and it won't boot to CWR. If I select reintall packages, it fails every time.
Help!
Click to expand...
Click to collapse
Make sure the "update.zip" file is on your Int SD card... power off your phone.
While holding down the Vol up+down, press and hold all 3 buttons till the "Samsung/Vibrant splash screen pops up.
You should boot into stock recovery, use vol up and down to move up and down and choose "reinstall update" with power... it should reboot and bring you right back to where you were... repeat choose "reinstall update" with power... now you should boot into CWM recoery.
I think the problem is that you have the new recovery (3e I think) that requires signed update.zip files. I'd recommend using Odin3 to flash another kernel which will come with CWM. If you don't want to do that, there is a guide somewhere on xda to allow 3e recovery to flash unsigned update.zip files.
Sent from my T959 using XDA App
phantomsniper773 said:
I think the problem is that you have the new recovery (3e I think) that requires signed update.zip files. I'd recommend using Odin3 to flash another kernel which will come with CWM. If you don't want to do that, there is a guide somewhere on xda to allow 3e recovery to flash unsigned update.zip files.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Exactly clockwork will not install with 3e recovery. Either flash a new kernel or do the 3e mod recovery. Odin will take 1 min to complete its process of flashing a kernel, you should definitely do this. Or just go back to stock and start your flashing journey from there.
aeok18109 said:
did you install both the free and premium version of rom manager?
Click to expand...
Click to collapse
Yup, I installed ROM Manager, then bought the premium key. I've got all functionality available to me.
Only problem is that when it flashes the recovery, nothing happens. If I reboot to recovery, it says the update.zip has an invalid signature. It seems nothing works. Am I supposed to flash back to droid 2.1 to get this thing working? It seems like it should be easier than this....
ferhanmm said:
Exactly clockwork will not install with 3e recovery. Either flash a new kernel or do the 3e mod recovery. Odin will take 1 min to complete its process of flashing a kernel, you should definitely do this. Or just go back to stock and start your flashing journey from there.
Click to expand...
Click to collapse
Thanks for the info. Any suggestions on kernels to use and a link for more info on what specifically a kernel is/does? Last thing I want to do is brick this puppy
Update...
Ok, did a little google-fu and found some links. I am using 3e, so ODIN it is! Thanks for the nudge int he right direction - wish me luck!
you can download this and used it to flash back to stock http://forum.xda-developers.com/showthread.php?t=954509 .and root and then try rom manger again this work for me all the time.
phantomsniper773 said:
I think the problem is that you have the new recovery (3e I think) that requires signed update.zip files. I'd recommend using Odin3 to flash another kernel which will come with CWM. If you don't want to do that, there is a guide somewhere on xda to allow 3e recovery to flash unsigned update.zip files.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Richcar said:
you can download this and used it to flash back to stock http://forum.xda-developers.com/showthread.php?t=954509 .and root and then try rom manger again this work for me all the time.
Click to expand...
Click to collapse
Yes, you are correct... another solution is to Odin the KB5 kernel with Voodoo and Recovery, make sure nothing check in Odin - LINK
Richcar said:
you can download this and used it to flash back to stock http://forum.xda-developers.com/showthread.php?t=954509 .and root and then try rom manger again this work for me all the time.
Click to expand...
Click to collapse
Well ****. I got CWM on there, installed zip from SD card (latest Cyanogen for vibrant) and now the thing's in an infinite reboot loop. ARRRGH! What now?
kcfried said:
Well ****. I got CWM on there, installed zip from SD card (latest Cyanogen for vibrant) and now the thing's in an infinite reboot loop. ARRRGH! What now?
Click to expand...
Click to collapse
Cotton needs new shorts! In CWM recovery, I did another wipe/format, reinstalled the zip and BOOYAH, it's done!
Thanks VEYR much for everybody's help!
kcfried said:
Cotton needs new shorts! In CWM recovery, I did another wipe/format, reinstalled the zip and BOOYAH, it's done!
Thanks VEYR much for everybody's help!
Click to expand...
Click to collapse
Originally Posted by kcfried
Well ****. I got CWM on there, installed zip from SD card (latest Cyanogen for vibrant) and now the thing's in an infinite reboot loop. ARRRGH! What now?
Click to expand...
Click to collapse
If your running CyanogenMod, there no way around Odin'ing to get back to stock. CyanogenMod (CM7) changes the partitioning to MTD from Stock RFS/Ext4. Only way to get that back is to Odin back to stock.