Related
Ok, so this is my first Informative thread..so bear with me.
Im a VERY regular hero flasher, and to me, it always seems frustrating to do the whole routine of
Backup>Wipe>Format>Flash>Setup Process>Restore Backup.
especially after you get used to a Rom and you have some stuff that cant be backed up.
Well, i came up with a solution-type thing.
Some people might have tried it out..not sure.
You need:
Nandroid
Android SDK ---> Get it Here
First, do a nandroid backup..(you need it for this to work)
type this into adb
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file ---->to mount SD in recovery..(or you could just reboot and mount or use an SD reader..whatever)
go to the nandroid folder, and recover the data.img file from your most recent backup. copy it somewhere on your computer.
Start up adb and type
adb shell
rm -r /system/sd/app_s
rm -r /system/sd/app-private -->to prevent bootloops
then wipe, and flash new Rom.
reboot and let the device go into setup process, then power off.
boot device into fastboot mode by holding the camera button + Power button.
open cmd, and cd to your android sdk directory. (or however you do it in linux)
now, type in
fastboot flash userdata <chosen path>/data.img
fastboot reboot
Thats it..all done. Now you have all your stuff from previous hero..and dont have to re-enter loadz of information...and also the benefit of having new stuff like "secret optimized apk's" and what-not.
if you have problem with touch-flo force-closing, go to
settings>applications>manage applications.
choose touch flo
choose clear data.
you should have ahome or some other type of home rplacement program because it seems touchflo DEFINATELy force-closes. and you'll need other home replacement to go into settings.
Or you could just assign a shortcut to settings by going to settings>applications>quick launch selecting what u like.
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
would this work with a non-Hero ROM? Or going from a Hero back to a cupcake (or whatever it's called?!)
Thanks!
kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Yeah, that would work, because it's the same thing but rather than just flashing data.img with fastboot, you're reflashing data + everything from your current setup. If that makes sense. You could just use fastboot...
sorry double post..
jomtones said:
would this work with a non-Hero ROM? Or going from a Hero back to a cupcake (or whatever it's called?!)
Thanks!
Click to expand...
Click to collapse
Dont think so, dont think there is a data partition in google based ROMs, all your apps are in the system partition. I'm not entirely sure about that, but I expect you'll get a bootloop.
kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
yes, that should work. sems abit more straight forward...especially for those who dont use adb
kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Dude that's perfect! I like your style of thinkin!
kjdiehl said:
Hey, I really like the idea behind this approach, but being not as savvy as I'd like, lemme ask this:
Could I achieve the same thing by:
1. performing a nandroid backup.
2. Go thru all the steps to flash a new Hero rom.
3. perform another nandroid backup.
4. copy the data file from the first backup to the appropriate location in the new backup, replacing the newer data file with the old.
5. Perform a nandroid restore with the the newly modified backup file. Et voila!
Or not? If not, would someone mind explaining to me the difference in as layman's terms as possible. A clear explanation could likely go a long way towards teaching me alot about many things that I'm not quite clear on.
Thanks!
Click to expand...
Click to collapse
Sounds kinda round-about to me... You'd have to make a nandroid... flash... then nandroid again... those nandroid backup/restores take much longer than flashing a simple userdata from fastboot. Using fastboot, you could flash it in what... a minute vs another 7-8minutes, but I guess its alright for those terrified of a command prompt...
EDIT: Forgot. Instead of doing the long echo command to mount your sdcard in recovery, you can just type:
Code:
adb shell ums_enable
to start the service and
Code:
adb shell ums_disable
to unmount it from your computer
Thanks for the responses, folks. It's much appreciated.
Yeah, I'm still getting the hang of adb. I don't typically mess around in Terminal, (I'm on a Mac,) so I'm not used to it or the lingo. That doesn't stop me from trying very clear directions, and I do learn a little bit, but the drag-n-drop world makes more sense to me, at least for now.
For instance, when given instructions like this:
"open cmd, and cd to your android sdk directory. (or however you do it in linux)
now, type in
fastboot flash userdata <chosen path>/data.img
fastboot reboot"
I THINK I understand most of it, but I don't know what "cmd" or "cd" means or if it's a typo or what. Also, I think most instructions don't make it clear after what lines I should hit enter and what not. I know that stuff is old hat to most of you guys, but I'm still trying to get the hang of it.
Anyway, thanks for the help!
Drizzy NewVision
Does this work for Drizzy's NewVision? Does it back up the ext3 partition so you dont have to wipe it and get rid of all your apps??
just got my GS4g yesterday, and it's my 1st SP (yay), rooted it with SOC - and I'd like to make a full backup of it's 'out of box' condition ..so I found this Froyo CMW thread and would like to utilize it
http://forum.xda-developers.com/showthread.php?t=1099374
however, it assumes the reader has previous knowledge of wtf they're talkn about..
I read further in the post "I have sent this to Koush as well to have it added to Rom Manager" - so I ran over to market and DL'd Rom Manager, but now I can't find the file ..hell I even googled "I downloaded from android market, where's my file" and no useful results come up ffs xD - so then I find this thread (yay) - but I can't afford to buy an app, here an app, there an app, everywhere an app app - so are there any free root explorer type applications? -ALSO- how do we mount our device as R/W? ..as it seems every single tutorial I come across is ambiguous
anywayz, I'd be really grateful if someone could help me out here..
I'd like to make a full backup of my 'out of box' Froyo, update it to stock 236, make another backup, flash it to Valhalla black 236, make another backup, ect - thanks for the read
KotsChopShop said:
just got my GS4g yesterday, and it's my 1st SP (yay) - and I'd like to make a full backup of it's 'out of box' condition ..so I found this Froyo CMW thread and would like to utilize it
http://forum.xda-developers.com/showthread.php?t=1099374
however, it assumes the reader has previous knowledge of wtf they're talkn about..
I read further in the post "I have sent this to Koush as well to have it added to Rom Manager" - so I ran over to market and DL'd Rom Manager, but now I can't find the file ..hell I even googled "I downloaded from android market, where's my file" and no useful results come up ffs xD ..anywayz, I'd be really grateful if someone could help me out here - I'd like to make a full backup of my 'out of box' Froyo, update it to stock 236, make another backup, flash it to Valhalla black 236, make another backup, ect - thanks for the read
Click to expand...
Click to collapse
1. Never use Rom Manager! ever!
2. Root your phone and then make a nandroid backup through recovery then flash whatever you want and make another nandroid backup and so on. There are enough Roms here that you really do not need to worry about a stock back-up but, as always it is good to back up everything. Trust in the THE BIBLE as it is your friend.
thanks for actually reading my post :rollseyes: lol
1] ok.. but I DL'd it, where is it so I can delete it? lol
2] already did, and I already found the bible (thx tho)
the problem is these tutorials and guides are ambiguous, and all of them assume you have prior knowledge of what their talkn about.. pretty much , no, exactly like the last
few statements of your own post "then make a nandroid backup through recovery then flash whatever you want and make another nandroid backup and so on" = lolwut? :/
I can't make a backup because.. well, read my 1st post again lol
KotsChopShop said:
thanks for actually reading my post :rollseyes: lol
1] ok.. but I DL'd it, where is it so I can delete it? lol
2] already did, and I already found the bible (thx tho)
the problem is these tutorials and guides are ambiguous, and all of them assume you have prior knowledge of what their talkn about.. pretty much , no, exactly like the last
few statements of your own post "then make a nandroid backup through recovery then flash whatever you want and make another nandroid backup and so on" = lolwut? :/
I can't make a backup because.. well, read my 1st post again lol
Click to expand...
Click to collapse
1. setting/applications/ROM manager/ uninstall
The rest would take a full page post. If I were you I would just go straight to GingerBread and do not worry about trying anything with Froyo. For that go here GB starter pack and follow the well detailed directions and if still confused I will do a step by step for you for GB. The aforementioned guide tells you what to get and where to put it and what to press. The technical knowledge will come in time after dealing with Roms, kernals, flashing, etc. You don't really need to know anything other than what files to use, where to put said files, and what buttons to press and that will get you rooted and Rom'd. Before your rooted and Rom'd you should learn what does what and why and that will take a lot of reading and time but, if your impatient like a lot around here you can always learn after you've rooted and Rom'd your phone.
thanks for your replies swann, underneath my amagad, I do appreciate it lol
ok so.. I DL'd RM last night, but apparently it didn't install because it's nowhere to be found...
it's not in my apps, and idk where DL'd files are stored so I can delete it (it's not on my SD either)
anywayz, before I do anything else, I want to make a backup of my out of box Froyo
(and idgaf if anyone thinks I should skip this part, I still want to do it =)
and in order to do this, I went here --> http://forum.xda-developers.com/showthread.php?t=1099374
but since it doesn't fully explain the how to's, I went here --> http://forum.xda-developers.com/showthread.php?t=1122508
but then I don't have root explorer, and can't afford to pay for a bunch of different apps, therefore, I need to know of a trusted/stable/free alternative - and I also don't know how to "mount my system as R/W"
...and when I google it, nothing helpful comes up.. or is that something indigenous to root explorer? (which wasn't explained, because as I stated, all these so called tutorials are ambiguous)
wait.. is it me or do I seem to be repeating myself? *scratches head* lol
I have all kinds of patience swann, I can do all the research and studying that's needed without qualms - as I know exactly how it is.. I own and operate a forum which specializes in teaching kats how to mod the gta series and how to model in 3d applications.. and we home grow some of the most talented kats the gta modding scene has ever been blessed with ...but that's because all of my tutorials are concise and clear and leave nothing to guess - as are my answers to everyone's questions - so when I ask a question and nobody answers it, but thinks for some reason that they did, I tend to get a little uh.. how should we say.. urhrhr towards them because they're obviously wetoded or some shyt lol
anywayz, assistance would be greatly appreciated..
1. Are you rooted? If not, you will need to do this first.
2. ES file explorer is a good free alternative to root explorer, you will have to go into setting to allow for system files.
3. You would be better off just downloading a stock Froyo Rom and using that as your back-up but...if your wanting to do it your way you will need to be rooted and for that you will have to read because I took my phone out of the box, plugged in USB to the computer and installd GB before even setting the phone up so I am not sure of the process of flashing Froyo or if it even differs from GB. After that I will be happy to help you when you get to point of wanting GB.
KotsChopShop said:
rooted it with SOC
Click to expand...
Click to collapse
yes, I am rooted
thank you, I'll have a look for it asap
my plans are this; backup out of box Froyo, install stock/factory 236 update, backup that version of GB, then flash to Valhalla 236 black w/FBis's debloater
the reason I didn't automatically update to Tmo/Kies 236 is because I've read about the bad KJ6 modem causing text send errors as well as gps failures..
Dude fyi, Samsung doesn't make android. All new people see to credit Samsung for android. Google makes Android
Sent from my SGH-T959V using xda premium
uhh weally? lol ..yes, I understand that
but exactly what relevance does that hold with anything I've said thus far? ..was it because I mentioned Kies? - and if so, soeffnwhat.. your post effectively does nothing in it's frivolous existence lol
KotsChopShop said:
yes, I am rooted
thank you, I'll have a look for it asap
my plans are this; backup out of box Froyo, install stock/factory 236 update, backup that version of GB, then flash to Valhalla 236 black w/FBis's debloater
the reason I didn't automatically update to Tmo/Kies 236 is because I've read about the bad KJ6 modem causing text send errors as well as gps failures..
Click to expand...
Click to collapse
I believe the problems arose from using the leaked KJ6 items. I have not had any problems using anything related to KJ6 items built from the source. When you get to the GB flashing/Roms and such and have any problems just let me know.
for real? ..ok, I'll back this ish up tonight and [email protected] if need be
edit; welp, I decided to just roll with it and install stock 236 w/o backn up Froyo.. and it's exactly as everyone says, longer text messages and/or messages with images will not send :mutherF*$*ingSuicide:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah
hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.
Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!
yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah
Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah
check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah
just try opening it with a plain windows explorer
xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah
hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.
Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah
No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.
does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!
well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient
On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.
Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah
It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah
Mod is listed under the international version of the one x, but i wanted to repost it over here so the rest of us aware of this awesome mod.
Original Thread : http://forum.xda-developers.com/showthread.php?t=1582506\
Basically it gets rid of the option bar at the bottom of the screen on non-ICS apps/games and makes the multitask/tast switch button, the new options menu.
Long pressing the home button becomes the new switcher.
Ahem. http://forum.xda-developers.com/showthread.php?t=1645290
pretty sure the general section dwellers just don't come in here, and when they do they don't search.. lol
_MetalHead_ said:
Ahem. http://forum.xda-developers.com/showthread.php?t=1645290
Click to expand...
Click to collapse
But I dont want the extended power menu.
Is this even safe? This is for the international version and while they are similar, they are not the same. Someone already softbricked his phone trying to use the odexed version of this mod. http://forum.xda-developers.com/showthread.php?t=1652566
_MetalHead_ said:
Is this even safe? This is for the international version and while they are similar, they are not the same. Someone already softbricked his phone trying to use the odexed version of this mod. http://forum.xda-developers.com/showthread.php?t=1652566
Click to expand...
Click to collapse
Yup...I still need help if someone has experience with fixing these things and not losing data on ones phone (currently adb is not letting me push my backup-ed files)
can't search for something i didnt know existed
Berserk87 said:
can't search for something i didnt know existed
Click to expand...
Click to collapse
Why did you assume this worked for the stateside One X? I checked and trust me, it doesn't.
ErikWithNoC said:
Yup...I still need help if someone has experience with fixing these things and not losing data on ones phone (currently adb is not letting me push my backup-ed files)
Click to expand...
Click to collapse
Flashing an RUU does not erase files on /sdcard... I'm assuming you have them backed up in Titanium Backup? So this method should work for you.
zonk7ate9 said:
Flashing an RUU does not erase files on /sdcard... I'm assuming you have them backed up in Titanium Backup? So this method should work for you.
Click to expand...
Click to collapse
I flashed the RUU and my music and photos are still there, but I lost all my apps because there stored somewhere else on the device (thanks HTC), at least that's what I thought.
ErikWithNoC said:
I flashed the RUU and my music and photos are still there, but I lost all my apps because there stored somewhere else on the device (thanks HTC), at least that's what I thought.
Click to expand...
Click to collapse
That's what Zonk7 meant. Of course it wiped your apps. In order to be able to use most apps while SD card is mounted as USB drive, the apps are not stored in the SD card.
Hence the comment about Titanium backup.
Simply restore your apps after you RUU from the titanium backup you have in your SD card.
the mod should work for us Rogers users though, shouldn't it?
lilhyper said:
That's what Zonk7 meant. Of course it wiped your apps. In order to be able to use most apps while SD card is mounted as USB drive, the apps are not stored in the SD card.
Hence the comment about Titanium backup.
Simply restore your apps after you RUU from the titanium backup you have in your SD card.
Click to expand...
Click to collapse
Yeah I know, but I didn't make a backup with Titanium. I know I should have, but I didn't think about it at the time and I'm just concerned with space.
_MetalHead_ said:
Ahem. http://forum.xda-developers.com/showthread.php?t=1645290
Click to expand...
Click to collapse
designgears said:
pretty sure the general section dwellers just don't come in here, and when they do they don't search.. lol
Click to expand...
Click to collapse
Well the one you link to says it doesnt work yet. So maybe the general section dwellers did search and the forum police got it wrong this time lol jk
imma let someone else try it first though lol