Related
Hi all!
Well, thanks to everyone for their donations-- without you, this wouldn't be possible.
I present to you, one stepping stone towards custom ROMs: the shipping ROM on the device, backed up as a NANDROID.
What is this?
This is the shipping ROM on the device. There are no changes to this ROM besides being rooted.
Click to expand...
Click to collapse
How do I use this?
Extract the contents of this file to your SD card (external SD card) under
Code:
/clockworkmod/backups/
and you will end up with a
Code:
/clockworkmod/backups/revo_stock
folder.
Run Clockwork on your device, and select "Backups and Restore" then "Advanced Restore". Select "revo_stock" as the backup to restore, and choose to restore ONLY "system".
(You can also restore boot.img, but it is unnecessary, and I only left that in there for future use.)
Click to expand...
Click to collapse
What does this backup include?
This backup ONLY includes /system and boot.img. There is no recovery.img in this backup, nor is there a /data or /cache.
Click to expand...
Click to collapse
Will I lose my apps or information if I restore this backup?
No you will not, this backup will not touch your /data partition.
Click to expand...
Click to collapse
Why is this useful?
Accidentally erased something important in /system?
Removed something and now 4g Hotspot doesn't work?
Restore this, and it'll fix that... of course all the stock OS will come back, but hey-- you get a second chance
Click to expand...
Click to collapse
Downloads
http://goo-inside.me/private/iomonster/files/revo_stock.zip
Special thanks to Snipa and s0up for hosting this file for me, as I really really really hate upload sites.
Click to expand...
Click to collapse
Contact Me!
Got an issue with this release? Post here!
Want to contact me privately? PM me on XDA or Rootzwiki
Twitter your thing? Follow me, @tylerfixer on Twitter
Join the official LG Revolution dev IRC channel at freenode on #lgrevolution
I'm IOMonster on IRC!
Click to expand...
Click to collapse
thanks icecube, i hit refresh all yesterday waiting for this!!!!!!!!!!!!!!!!
leemsami said:
thanks icecube, i hit refresh all yesterday waiting for this!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
i meant thecube!!
Haha! No worries, it's 3:30AM
do i push this through adb or do i extract it on windows then put it on my sd card.
leemsami said:
do i push this through adb or do i extract it on windows then put it on my sd card.
Click to expand...
Click to collapse
Extract through windows and put on your SD card in the proper folder.
its telling me that i have a md5 mismatch!!! i will try downloading it again.
Thanks cube please keep up the hard work! I wish I could do something to help other then sending some $$$ I would love to help bring the revolution along.
Viva la revolution.
Did anybody use this yet. i tried and it says my md5 does not match. i tried numerous times
Haven't tried it yet but I checked the MD5 against the images and they are correct.
Ah, sorry, forgot to state select "Advanced Restore" or whatever it's called-- JUST restore system.img.
If you select "Restore" it looks for the /data and recovery.img in the nandroid.md5 file, and when it doesn't find it, it errors out with an md5 error.
I'll edit the instructions now...
Just tested this. I can't advanced restore the system.img either. Comes back with MD5 mismatch. I can restore my own backups without a hitch however.
[Edit] I forgot to mention. There's a carriage return on the Rooted Factory-Stock ROM MD5 file. Removing it didn't seem to matter. I was thinking that maybe it was the culprit.
Agh! you just gave me the answer... I saved it in windows, rather than linux, so the line endings are wrong...
If you're able to, just open the file nandroid.md5 in Notepad++ or something like it, and remove the extra blank line, and change the line endings to UNIX style.
Thanks, I'll re-upload the .zip when I'm on a faster connection.
The actual .img files themselves are good, though.
thecubed said:
Agh! you just gave me the answer... I saved it in windows, rather than linux, so the line endings are wrong...
If you're able to, just open the file nandroid.md5 in Notepad++ or something like it, and remove the extra blank line, and change the line endings to UNIX style.
Thanks, I'll re-upload the .zip when I'm on a faster connection.
The actual .img files themselves are good, though.
Click to expand...
Click to collapse
thanks thecube, it worked with the notepade++ steps and unix style.
re-uploaded. Should work just fine now.
Is there a version of this with everything? In other words, not just system but data, etc. I somehow am stuck in CWR...don't have a nandroid backup. I pushed this to the right place on the SD card, did the system restore, but it still repeatedly boots into CWR. Is there anything that will do a FULL restore instead of just system?
Thanks in advance.
MarkyD311 said:
Is there a version of this with everything? In other words, not just system but data, etc. I somehow am stuck in CWR...don't have a nandroid backup. I pushed this to the right place on the SD card, did the system restore, but it still repeatedly boots into CWR. Is there anything that will do a FULL restore instead of just system?
Thanks in advance.
Click to expand...
Click to collapse
Hm, so you did a data wipe from within Android. Yep, that'll get you stuck in CWR, but it's not a problem with the backup, it's that the LG bootloader isn't happy with Clockwork.
When installing Clockwork, did you make the p8 backup?
so im having the same problem i even started a thread too but im an idiot and didnt make that p8 backup because the md5sum didnt match so i stopped there but clockwork still seem to flashed to the phone now im in clockwork everytime i boot up was wondering any way to work around this if not guess imma just get a new phone until there is a way
rodney323 said:
so im having the same problem i even started a thread too but im an idiot and didnt make that p8 backup because the md5sum didnt match so i stopped there but clockwork still seem to flashed to the phone now im in clockwork everytime i boot up was wondering any way to work around this if not guess imma just get a new phone until there is a way
Click to expand...
Click to collapse
There is a way, I just haven't written it into an easy-to-use program yet.
For now, if you haven't made a p8 backup, the easiest method is for you to come on IRC and have me adb into your phone and fix it for you.
If I get a spare moment though, I will work on a stuckinclockwork.zip that you can flash using clockwork to get you out of clockwork.
Stuck in clockwork fix:
http://forum.xda-developers.com/showthread.php?p=15501302#post15501302
**** ****. I was messing around with the options in Titanium Backup Pro and selected an option that said that i can remove a few apps that have been linked to my ROM and free upto 80 MB in memory. It had something to do with Dalvik Cache. The software said that the phone will restart after the process. But the phone gets stuck at the HTC Quietly Brilliant Brilliant" white screen and re-boots. I tired Pulling out the battery, Wiping cache, Factory reset using CWM but the problem continues. What do i do? The phone is hardly 3 weeks old. Its still S-ON, rooted and unlocked at htcdev.com
Can you not restore a nandroid? Or try flashing a rom that doesn't need s-off like CyanogenMod 7.
Sent from my Incredible S using xda premium
InsertDumbNick said:
**** ****. I was messing around with the options in Titanium Backup Pro and selected an option that said that i can remove a few apps that have been linked to my ROM and free upto 80 MB in memory. It had something to do with Dalvik Cache. The software said that the phone will restart after the process. But the phone gets stuck at the HTC Quietly Brilliant Brilliant" white screen and re-boots. I tired Pulling out the battery, Wiping cache, Factory reset using CWM but the problem continues. What do i do? The phone is hardly 3 weeks old. Its still S-ON, rooted and unlocked at htcdev.com
Click to expand...
Click to collapse
Restore your nandroid, I think I remember you posted that you had one.
Nonverbose said:
Restore your nandroid, I think I remember you posted that you had one.
Click to expand...
Click to collapse
Yeah i tried doing that. But get this error message in CWM:
Code:
Couldn't open directory.
No files found.
The Backup is in a folder "2012-02-12.06.04.17" and this folder is in the sd-card root. Do i have to copy the files in this folder to the root as well??
Edit: I forgot to mention that the above nandroid backup folder was saved in my computer and the sd card on which i had made the backup initially was involved in multiple formats during my futile attempts to gain S-OFF ..
InsertDumbNick said:
Yeah i tried doing that. But get this error message in CWM:
Code:
Couldn't open directory.
No files found.
The Backup is in a folder "2012-02-12.06.04.17" and this folder is in the sd-card root. Do i have to copy the files in this folder to the root as well??
Click to expand...
Click to collapse
You shouldn't have to. Was the backup created in cwm? Have you checked that the files are in the folder? What option were you using to restore your backup?
Another option would be to installed a custom ROM.
I guess if you are using CWM, the folder will not be on root.
As far as I remember, it use to be in some folder named CWM or ClockWorkMod something like that.
I guess the folder "2012-02-12.06.04.17" should be under "\clockworkmod\backup\" folder.
Not quite sure as I am using Ext4 recovery now.
But guess someone around here should tell you the correct folder structure.
And, I guess if you could try to mount card on your computer you will be able to see and modify the folder and put it in right place with correct backup directory.
I think i have to create a few folders since the path that CWM is looking for the recovery doesn't exist. Can you tell me the correct path so that i can create an identical location to copy the backup to??
It'd literally take you 5 mins to install a custom rom? And then in theory your fine will work perfectly. Then just set it up and create a nandroid.
When I had problems I formatted the SD card and only left the CWM files on. Then it restored/worked fine.
Sent from my Incredible S using xda premium
InsertDumbNick said:
I think i have to create a few folders since the path that CWM is looking for the recovery doesn't exist. Can you tell me the correct path so that i can create an identical location to copy the backup to??
Click to expand...
Click to collapse
way2shree was correct in his post about the file structure. I think you need to do a bit of research before you do any serious damage to your phone.
vizzy said:
It'd literally take you 5 mins to install a custom rom?
When I had problems I formatted the SD card and only left the CWM files on. Then it restored/worked fine.
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Like i said the SD card on which CWM made the backup was formatted many times. Completely. So i had copied the folder with the backup to the computer.[Newb mistake. I realized the hard way]. And no the path is not \clockworkmod\backup\. Thanks anyway shree. Also i think CM7 is the only 1 that can be flashed with a S-on phone. so ill keep that as a final option since i still like sense.
Nonverbose said:
way2shree was correct in his post about the file structure. I think you need to do a bit of research before you do any serious damage to your phone.
Click to expand...
Click to collapse
I looked all over the place and found only this \clockworkmod\backup\<date> . Made both the folders but still not recognized. Can anyone confirm that this is in fact the correct path??
Phew. Atlast got the backup restored. THank you guys for all your help. Looks like i wont be doing anything android related for the next MONTH till i at least have a general idea of wth im doing.
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
tramp20 said:
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
Click to expand...
Click to collapse
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
N00BY0815 said:
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
Click to expand...
Click to collapse
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
tramp20 said:
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
Click to expand...
Click to collapse
The link I provided is for CWM touch 5 only. This version will make the "normal/full-sized" backups. I think you're right about the new update, but I gotta confess, I dont really understand it myself yet... I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
If your not sure about the old version, just install the one from the link I provided.
Hope it helped you, if not, you may also PM me.
N00BY0815 said:
I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
Click to expand...
Click to collapse
To test:
I made a backup, installed a new app, then after another backup I looked in the blobs dir: only a few subdirs are new, all other remain unchanged.
So all files in blobs are cumulative and important for a restore, but bad for a later extern backup on my pc.
The old method of CWM was better.
Perhaps I will try the link from you.
I was trying a backup and found under "choose backup format" the following points:
- dup (default)
- tar
-
-
So I can choose
I did a backup (dup format) and all is working again.
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff
Hi all,
I am trying to restore a twrp backup that I made, but when I go to twrp and click restore I get a black screen where it should show me the backup file, yet I can navigate via the pc to phones internal storage to TWRP/BACKUPS/2013-06-19--12-07-12/ and all the win files and md5 files are in that folder, tried making that folder into a zip and flashing like you would a normal rom install but it just fails. Please help folks!
never mind, figured it out
germinus said:
never mind, figured it out
Click to expand...
Click to collapse
You should really write a quick method of what you done to fix it incase anyone with the same problem ends up on this post in the future...
Sent from my HTC One using xda premium
redbull123 said:
You should really write a quick method of what you done to fix it incase anyone with the same problem ends up on this post in the future...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Sure I just figured it was me being stupid and most people would know!, for some reason, twrp was only reading the sdcard but the backup was actually stored in /data/media/twrp/backups (no idea why it started doing this, I actually have 2 HTC ones both being sent back to vodafone and never had this prob on the first unit), anyway, I downloaded a app called root explored which enabled me to copy the backup file from data/media/twrp/backups to the sdcard/twrp/backups folder and then I could restore
I am sure there is a reason why I had this problem but I wouldn't have a clue as to why! But anyway that's how I solved it, I am sure there is an easier way tho!
germinus said:
Sure I just figured it was me being stupid and most people would know!, for some reason, twrp was only reading the sdcard but the backup was actually stored in /data/media/twrp/backups (no idea why it started doing this, I actually have 2 HTC ones both being sent back to vodafone and never had this prob on the first unit), anyway, I downloaded a app called root explored which enabled me to copy the backup file from data/media/twrp/backups to the sdcard/twrp/backups folder and then I could restore
I am sure there is a reason why I had this problem but I wouldn't have a clue as to why! But anyway that's how I solved it, I am sure there is an easier way tho!
Click to expand...
Click to collapse
It does this with 4.2.2 I think it sucks actually because if you want to copy a back up to/from your computer you have to use adb push or copy it over to your sd, then move it into /data/media