After some frustrating failures with romdump v72 I could extract a romdump out of my Motorola Defy Plus MB526 (carrier Vodafone-Italy) with v82b.
Here is the result:
Code:
04/02/2012 18.17 185 checksum.md5
04/02/2012 18.14 0 config.gz
04/02/2012 18.14 1.399 system.info.gz
04/02/2012 18.16 286.179.328 system.tar
How can I know if everything is ok?
How can I make a recovery out of those files?
I would like to try CM7 but I will not until I know I have a working backup.
I don't really know what you're doing here but can't you just do a nandroid backup from CWM recovery?
miscz said:
I don't really know what you're doing here but can't you just do a nandroid backup from CWM recovery?
Click to expand...
Click to collapse
I think that he want's to dump his official stock rom before modifying his defy. So i guess he has not got 2nd-init or CWM or CM7, (or probably even root?)
Sent from my 1Ghz CM7 + CM9 Defy
Almost perfect ;-) I did root to enable Titanium Backup. Next step is having a firmware backup and then finding a CWM recovery that works on Defy+
Edit: you can not romdump without rooting.
Update: I wiped all data from the phone, rooted again, made a "clean" romdump, installed the recovery, and made a backup from there (I suppose it is a nandroid backup).
Now I will restore all data, backup again and study CM installation.
Thanks for suggestions.
Hi UncleDan,
I have Motorola Defy Plus MB526 2.3.5, and would like to make romdump before doing 2nd-init and installing CM7,CM9
So far I understand that phone has to be rooted(done), romdump should be installed.
Did you use ADB, or terminal to install/start it?
(addictivetips.com/mobile/how-to-backup-your-android-phones-boot-recovery-and-system-partition-images)
Was the backup running without problems, or did you fight with something...?
Finally, if I got system image, how do I make restore from it?
As on romdump page is only stated:
Once the program has finished you should find a directory in the root of your SD card called romdump and a sub-directory named after your device model. Take those files and give them to someone who knows how to make a recovery zip
Click to expand...
Click to collapse
BTW: Will be this image usable after screwing something with CM7, CM9?
Or I will need to flash one of SBF anyway?
(sorry if that a silly question - the more I read on forums, the more confused I'm)
Thanks.
UncleDan said:
Almost perfect ;-) I did root to enable Titanium Backup. Next step is having a firmware backup and then finding a CWM recovery that works on Defy+
Edit: you can not romdump without rooting.
Update: I wiped all data from the phone, rooted again, made a "clean" romdump, installed the recovery, and made a backup from there (I suppose it is a nandroid backup).
Now I will restore all data, backup again and study CM installation.
Thanks for suggestions.
Click to expand...
Click to collapse
how you installed recovery? link please...i've rooted, done titanium backup & wiped the phone..but i cant find any CWM recovery fr Defy+ :-(
Sent from my MB526 using XDA App [ still on stock 2.3.6 :-( ]
apurvdate said:
how you installed recovery? link please...i've rooted, done titanium backup & wiped the phone..but i cant find any CWM recovery fr Defy+ :-(
Click to expand...
Click to collapse
2ndInit
I had no problems in making the image with romdump v82b but I had no clue on how to restore.
So I parked it and went for 2nd init + nandroid. I restored twice and works like a charme.
The only little issue is that if you install bootmenu 0.6.1 it installs an old recovery which makes a single backup image and if you restore that you always get the old recovery, even if you had a recent one e.g. by flashing CM7.
Sent from my MB526 using XDA App
ejstubbs said:
2ndInit
Click to expand...
Click to collapse
i hv alrdy tried installing SndInitDefy.apk v2.0 from d given thread..but no use..when i reboot in recovery mode i get error logo (android with ! sign in triangle)...
Sent from my MB526 using XDA App
No idea then, sorry.
ok..i managed it..
uninstalled v2--installed v1.9--again installed v2...now its working
got backup of all..
time for cm7/cm9 now
Sent from my MB526 using XDA App
apurvdate said:
when i reboot in recovery mode i get error logo (android with ! sign in triangle)...
Click to expand...
Click to collapse
Dude, that's not an error, that's what's meant to happen when you boot in to recovery mode. When you get that logo, press vol+ and vol- at the same time and you will get the stock recovery menu.
Related
I've tried to search but cant find a guide how to make a backup of my phone... if someone can explain or post me a link, i will be a happy man
Root phone.
Power off.
Hold volume down and power the phone on, and enter recovery mode.
Get into recovery menu (recoverywhatever.sh on *NIX or recovery-windows.bat)
Scroll to backup/restore in recovery menu.
Select backup NAND only - backing up EXT causes errors right now.
Find saved nandroid on your SD card.
Back up your apps separately using Titanium Backup or MyBackup Pro. Restore by wiping the phone, restoring the NAND, and restoring the apps via one of the above apps.
You need root for nandroid. Then it's done in recovery.
its rooted, but when i go into the recovery menu, the phone just shows a picture with a red triangle, is that correct?
No. Get back into the green recovery menu by running recovery-windows.bat or whatever method you used in step 2 of the rooting process to flash the rooted zip file.
ok thnx
one more thing, the titanium backup said i need busybox, how do i install that?... Found out myself
Did you get this problem solved as I have the same problem. I re rooted my desire and the same thing happened. The only time i can go to recovery is when I use recovery-windows.bat from the r5 tools. Any help?
i just use rom manager. choose backup in there, phone reboots itself, backs itself up and done.
used the recovery options a few times when moving from rom to rom.
ClockworkMod Recovery tool
ClockworkMod Recovery tool is really handy. Does everything itself in few clicks. I used Rom manager to backup with no problems without any previous experience.
tommo123 said:
i just use rom manager. choose backup in there, phone reboots itself, backs itself up and done.
used the recovery options a few times when moving from rom to rom.
Click to expand...
Click to collapse
installed rom manager and when choosed backup curret rom it asked for desired name then tap ok and reboots, now its freeze into htc slash screen
A2SD
Edit:
I accidentally posted on the wrong thread...
Are there still problems with this?
"backing up EXT causes errors right now."
I have one question.
If i make a nandroid backup, does it make a FULL nand backup or just certain parts of nand ?
If i for example make a backup of my leedroid rom with all my apps and settings
make wipe and then try a gingerbread rom, will restoring nandbackup actually restore the prevision rom with all the settings and apps ?
hojnikb said:
I have one question.
If i make a nandroid backup, does it make a FULL nand backup or just certain parts of nand ?
If i for example make a backup of my leedroid rom with all my apps and settings
make wipe and then try a gingerbread rom, will restoring nandbackup actually restore the prevision rom with all the settings and apps ?
Click to expand...
Click to collapse
It will restore the entire rom to the exact state as the time before the nandroid. So yes all settings and apps will be there.
Great to know..
Thx
Is it worth rooting for a backup?
Also will a new OTA just remove root if or when another OTA comes out... ?
Sent from my HTC Desire using XDA App
Lothaen said:
Is it worth rooting for a backup?
Also will a new OTA just remove root if or when another OTA comes out... ?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No there is not a real point in rooting for the ability to back up. And despite what some say, never apply OTA updates on rooted devices! But custom versions will come out at the same time as the OTA so you don't miss out on anything.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
No there is not a real point in rooting for the ability to back up. And despite what some say, never apply OTA updates
Click to expand...
Click to collapse
What's an OTA update?
Just install rom manager then click on back up . Boom you have a nandroid back up.
Sent from my HTC Desire using XDA Premium App
Ota update is
Over the air update so its basically stock updates from phone manufactures
Sent from my HTC Desire using XDA Premium App
Hi.
Is there any way to do a full (sbf) bacup of CM7 Defy?
When I enter bootmenu, there is option to restore, but not to make backup.
CWM does not support defy, right?
Any other options? (I am a noob)
Hi,
welcome in the XDA forum!
You can´t make a sbf backup, because these are service flash files, made by motorola or by a provider.
CWM doesn´t support our defy directly, but you can download "Defy 2nd init" from the market.
You can make backups and restore backups, they will be created on your SD Card
Thanks. Actually I've had one attempt with "Defy 2nd init" and I failed (and ended up with logo-reboot cycle, had to reflash). I wasn't able to find a guide for this online, what to do step be step... Could you please help?
I'm pretty computer literate, but this is 95% new territory.
and (edit) by the way, that's in 2nd init info:
[Important Note]
If you're already running CyanogenMod or MIUI don't use this app to update bootmenu, wait for a new ROM update, since bootmenu bundles with those ROMs itself, and using this tool to update in those ROMs might break your installation.
Click to expand...
Click to collapse
?
Even I ended up installing every thing from scratch after installing 2nd unit, better be careful.
Sent from my MB525 using Tapatalk
That's the thing, sg3707.
So back to the question: how to make a full backup of CM7 defy?
I have successfully (nandroid) backed up and restored my CM7 (110715 nightly) by: long press power button -> choose reboot -> choose recovery.
This will bring you to CWM recovery 4.0.1.0-defy when the system boots up.
Since I'm still very much a noob I can't tell you if this qualifies as a full backup or not.
I don't have cm7 but I have 2ndinit and with it you have the custom recovery clockworkmod.
You can use it to make a backup on your sd.
Usally I press volume - when the LED is blue at boot select recovery then custom and backup/restore to make my nand backup
Sent from my MB526 using XDA App
twa_priv, thanks, that's the way to do it. I've been 100x in this menu and was affraid to click "Latest Recovery"... but there is another menu behind and it's possible to make a full backup!
You can't. All you can do is a nandroid back up. For you to use 2nd init, you have to be rooted and don't forget the usb debugging should be turned off other wise boot loop. Read cm7 faq
Sent from my MB525 using XDA App
Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks
wallendiaz said:
Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks
Click to expand...
Click to collapse
For a nandroid restore to work properly in CWM, the path to the images needs to be EXACTLY the same as it was when you created it. For example, if when you did the backup, the file was located in /sdcard/clockworkmod/backup/2012.06.30.07.30.00, then you need to make sure that that path is exactly the same. Otherwise, you will need to regenerate the MD5, and then it will work by doing this:
adb shell
cd /sdcard/clockworkmod/backup/2012-06-30.07.30.00
rm nandroid.md5
md5sum *.* > nandroid.md5
exit
EDIT: And please change your title. Your phone is not bricked. Bricked means it is as useful as a brick -- i.e., it does not work anymore and it cannot be fixed without returning it. You may have messed up the firmware, but your device certainly works just fine.
wallendiaz said:
Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks
Click to expand...
Click to collapse
What recovery are you using and how exactly did you try to restore?
If you renamed the backup make sure there are no spaces
Sent from my Galaxy Nexus using Tapatalk 2
If you can get to recovery then you are definitely NOT bricked.
Sent from my Galaxy Nexus using xda app-developers app
Hello to all,
I have Arc with ICS .587 installed and rooted, CWM is Also installed. Whenever i try to restore my Backup i end up in bootloop, sometines its restored but somethings are not working like no service, some widgets are Gone, cant get into Phone settings as the setting button is completly gone from phone.
Please can good Samaritan help me
Thanking All in Advance
Do you Wipe Data/Factory Reset/Cache etc before restore?
did you changed kernel?
if you chanege the name of the backup, things will not work.
gabimx said:
did you changed kernel?
if you chanege the name of the backup, things will not work.
Click to expand...
Click to collapse
yes....not change the name of backup...
moreover if you have flashed a zip and it didn't go fine....there is a possibility that the istallation have spoiled the backup or file of kernel...(for all I know it happened to me in this way)
Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder
centi50 said:
Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder
Click to expand...
Click to collapse
If u flash custom kernel, u need to also flash wifi modules before rebooting after restore...
I dont Flash custom Kernel, everything is stock, by the way My Arc is Bootlocked so customs kernels
While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?
nikufellow said:
While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?
Click to expand...
Click to collapse
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.
centi50 said:
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.
Click to expand...
Click to collapse
Then do it ! and try again .
This is what is happening to me. Lets say am Running on GB Rom e.g X-Gamer, now i want to try lets say Optimax Rom, i backup my Current ROM which is X-Gamer, then i try to restore it to see if its works, and i find that it works. so Flash ICS Original Sony ROM and root it. in the end i Have Sony Stock ROM.587 and CWM installed. So far am ok.
Now i Install ICS based ROM like Optimax or JellySandwhich. Everything goes Fine, so i Backup That ROM too and keep a copy on my Laptop. Now i decide to go to my old backup of X-Gamer, i Boot to recovery do a full wipe + i mount data/system and fix permission as i have CWM 5.5.0.4. which has permission option in it. i continue to restore my X-Gamer Backup. After Finnishing of course without error. i reboot the phone and Bam!!. Bootloop.
I reflash GB.42 with Flashtool, root it and install CWM. Boot to recovery and try to restore my X-Gamer backup, and WOLA!! it's restored.
same with ICS Backup. Reflash Stcok Rom root it and restore the ICS backup i made, and it works.
As i know i may be wrong (am a noob) The backup is a snapshot of the rom, so regardless of what rom someone is running when he restores the Backup, he should be back to that ROM in the backup and not to reflash first the corresponding Stock ROM in order for the Backup to work.
Please somebody help and shade some light
Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium
Jessie-James said:
Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have tried to use same recovery, but same result. restoring backup across different ROM does not work for me it seems. I have to have a working corresponding rom as the backup am trying to Resotre. for example if i want to restore my backup of GB ROM, i have to have a working GB Rom already on Phone. I Can't restore an ICS Rom while my Phone is On GB and vice verser.
centi50 said:
Please somebody help and shade some light
Click to expand...
Click to collapse
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.
XperienceD said:
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.
Click to expand...
Click to collapse
Thanks XperienceD for Clarifying. now i undersatnd. Just wanted to ask is it possible to flash A GB Sock Kernel on an ICS ROM or vice versa, then using the backup to restore thru CWM, as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.
centi50 said:
as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.
Click to expand...
Click to collapse
This is why it's better to unlock your BL, then it's just a flash of a kernel then restoring your backup.
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
To install official updates u need to have stock recovery which comes with phone, but u have CWM
Jotne said:
Hi
I have a HTC one X rooted phone with stack 4.1.1
I get a message that there is a new update 3.20.401.1
After download it tells me to reboot. My phone then goes to ClockWorkmode (CWM)
It stoops there. I do not find any zip file to install.
Any tips for this, or should I just ignore this?
Thanks
Click to expand...
Click to collapse
You just need to flash stock recovery through fastboot again mate then on booting up you should be able to install the update. Or you could install a custom rom with that base without having to flash recovery :good:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Jotne said:
Thanks for quick reply.
If I go for a custom room, what is the best out there?
Do I loose anything by not upgrading the stock room?
Click to expand...
Click to collapse
they are all pretty damn good roms mate! too hard to choose really, just best to flash em, and see remember to make a nandroid backup also
u shouldn't loose anything apart from bloatware
If you want a custom based on stock, i suggest Android revolution, Viper Rom, or SD ROM.
Sent from my HTC One X using xda premium
CM10.1 ROM
Click to expand...
Click to collapse
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
Are you sure you've made the backup with the same recovery as you are attempting to restore it with?
The Android version shouldn't really matter, but there may be exceptions for some things.
Sent from my HTC One X using xda premium
Jotne said:
UFFFFF
I did try out Cyanogen lastest image, that do work fine.
But I have to look long for how to find out that I needed to extract boot.img from the cyanogen zip file and install this with flashboot.
But now I like to go back to my original rom. I did take a nandroid backup, and also have an older nandroidbackup.
Its not possible to make the phone go back. When I start restor, all looks ok MD5 etc, but then gets this message
Error while restoring /system!
Do I have to do more flashboot stuf to go back?
I am still able reinstall Cyanogen from zip file. But my Cyanogen backup also fail.
Why
Edit. The Cyanogen Image is 4.2.2 and Orginal image is 4.1.1. Could that be any problem?
Click to expand...
Click to collapse
If you are using CWM recovery u should be able to go into the backup file (under clockwork mod/backup on sd) and take the boot.img u need to flash via fastboot there. Put it in your fastboot file and then flash using "fastboot flash boot boot.img"
So I should take the boot.img from the backup, run fastimage and restore it?
Then try to restore the backup using clockworkmod?
I am not user if the backup was made with
recovery-clockwork-touch-5.8.2.7-endeavoru.img or
recovery-clockwork-touch-5.8.3.1-endeavoru.img
Is it important to restore with correct version? If so how to see what version that was used?
I am not able to go back to my old image
Not sure why, but the Cyanogenmod does not give me any Mobil data (3G etc)??
I tried to restore the boot.img from correct backup using flashboot flash boot boot.img and then try to restore.
But still I get Error while restoring /system!
Some note:
I made a backup of my working Cyanogenmod, this I am able to restore without getting the restoring error.
No I also have tried recovery-clockwork-touch-5.8.4.0-endeavoru.img
But there are some different thing going on.
When I first tested to restore my original image, I get menu like this when trying to restore:
Code:
Yes-Restore
No
Go-Back
Now I do get:
Code:
No
No
No
No
No
Yes-Restore
No
No
No
*** Go back
Have I used another clockworkmode to make the backup?
If you want to be sure you use the same recovery as where the nandroid is made with ? Flash the recovery.img from the nandroid folder.
Then flash the boot.img from the nandroid folder, go into recovery :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid.
Thanks
You saved my day.
It seems that the backup was done with CWM based v6.0.2.7
Not sure where I have got this version.
Latest version listed here: http://www.clockworkmod.com/rommanager is 5.8.4.0 and not 6.0.2.7 that I have used
Here http://forum.xda-developers.com/showthread.php?t=1941630 is 6.0.3.2 listed
What is the latest version of CWM for HTC ONE x and where to get it?
And last, what is the best to use
Yeah well after all the replies i thought i chip in give my 2 cents
This is one of the latest i use now.
http://db.tt/SPXdFfPw
Everything is working fine and I start to understand how its connected together.
But there are one thing that still puzzle me, the boot.img
When and why do I need to change that when I go to and from CM 10.1.2 (4.2.2) and Original image 4.1.1
What trigger the need of the change?
Should not this be restored correctly when I restore a backup. (In Clockwork mode)?
Does this work automatically whit Philz recovery 5.6.1.img?
I do like to change image in my phone without need a PC to run fastboot !!
When you change rom you need to flash the corresponding boot.img from that particular rom or nandroid backup.
We can't flash boot.img files via recovery because we have s-on devices so fastboot is a must.
Wilts panttsic
Ok, thats some sad, but thanks a lot for you help here
No problem.
CASE CLOSED !
Mr Hofs said:
No problem.
CASE CLOSED !
Click to expand...
Click to collapse
Another one for the Hof!!! :good:
exocetdj said:
Another one for the Hof!!! :good:
Click to expand...
Click to collapse
1 for Hofs = 1 for everybody mate.....we all are helping here !