Database Develop

[RELEASE][NANDROID] Rooted Factory-Stock ROM

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

[Q] Restoring contacts from a Nandroid backup

Hello,
I recently decided to update my ROM, radio, etc. I had previously had an Eclair rom. I updated the radio, and all other assorted stuff and flashed to a EZgingerbread rom.
In my zeal, I neglected to export a copy of my contacts. I did, however, remember to make a Nandroid backup of my old eclair rom.
So, I attempted to follow some tutorials in copying the file
/data/data/com.android.providers.contacts/databases/contacts2.db
using the adb command
cat /sdcard/contacts2.db > /data/data/com.android.providers.contacts/databases/contacts2.db
from my old backup to the corresponding folder on my phone. However, the phone does not show my contacts, as it seems to reformat the contacts2.db when I reboot the phone, as evidenced when I take a look at the db file on the phone.
Help is appreciated, thanks!
Small edit: I tried restoring the backup, but it gets stuck at the G1 boot screen, reboots, and shows the g1 screen again. So I can't extract my contacts that way. Probably because I loaded a new radio/hboot?

One Question! You have GMail Account Tied to G1, right? All your contacts should be saved in that GMail Account.

You might try performing this same copy while in recovery mode,
so that the overwrite of the file with the 'live' database doesn't happen on reboot.

GiantCrab said:
Hello,
I recently decided to update my ROM, radio, etc. I had previously had an Eclair rom. I updated the radio, and all other assorted stuff and flashed to a EZgingerbread rom.
In my zeal, I neglected to export a copy of my contacts. I did, however, remember to make a Nandroid backup of my old eclair rom.
So, I attempted to follow some tutorials in copying the file
/data/data/com.android.providers.contacts/databases/contacts2.db
using the adb command
cat /sdcard/contacts2.db > /data/data/com.android.providers.contacts/databases/contacts2.db
from my old backup to the corresponding folder on my phone. However, the phone does not show my contacts, as it seems to reformat the contacts2.db when I reboot the phone, as evidenced when I take a look at the db file on the phone.
Help is appreciated, thanks!
Small edit: I tried restoring the backup, but it gets stuck at the G1 boot screen, reboots, and shows the g1 screen again. So I can't extract my contacts that way. Probably because I loaded a new radio/hboot?
Click to expand...
Click to collapse
IANADBA, but you're probably running into an incompatibility in the data structures between the .db files. I'll bet the db versions between Eclair (I don't even remember what Android version that is) and GB are quite different. You might be able to get away with dumping the data from one and loading it into the other using an appropriate sqlite app.
Of course, there may be an very easy way I'm not aware of, in which case I am prepared for maximum flamage.
Jeff

[Q] upgrade to 2.0.6 and re-root?

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

FULL backup ... how?

I'm about to flash stock 4.4.2 prior to flashing 4.4.4 soak ... and I can't figure out how to do a complete backup of phone, in case things get screwy.
I can't do nandroid; not enough space.
I tried rsync, but couldn't get rsync running on phone as server.
I'm trying to just copy everything over with SFTP, but there are so many duplicate folders...
/storage/emulated/0 =
/storage/emulated/legacy =
/data/media/0 =
/mnt/shell/emulated/0,
etc etc.
and they don't appear as symlinks.
I tried 'adb backup ' etc ... but I don't want an ".ab" file that I cannot look into.
Is there an easier way?
thanks

d0g said:
I'm about to flash stock 4.4.2 prior to flashing 4.4.4 soak ... and I can't figure out how to do a complete backup of phone, in case things get screwy.
I can't do nandroid; not enough space.
I tried rsync, but couldn't get rsync running on phone as server.
I'm trying to just copy everything over with SFTP, but there are so many duplicate folders...
/storage/emulated/0 =
/storage/emulated/legacy =
/data/media/0 =
/mnt/shell/emulated/0,
etc etc.
and they don't appear as symlinks.
I tried 'adb backup ' etc ... but I don't want an ".ab" file that I cannot look into.
Is there an easier way?
thanks
Click to expand...
Click to collapse
Copy enough stuff off the internal memory to do your backup. Then copy the backup to your PC....then put everything back.
A full backup should only take a couple gigabytes. Moving your pictures, or music or whatever is taking up all that space should suffice.
If you are returning to stock, everything will be erased anyways....unless you modify the XML or manually flash and skip the erase userdata command.
Regardless, your backup won't be fully usable once you are on 4.4.4. If you restore it, your partition table and/or bootloader will be mismatched and you will likely get FCs if you restore back to it.
Are you on a custom ROM or something?
Additionally, if you PROPERLY flash back to stock 4.4.2 (erasing userdata - which is advisable), there's nothing that will go 'screwy'...
What variant are you on? If you are using an XT1060, there is a better way.

samwathegreat said:
Copy enough stuff off the internal memory to do your backup. Then copy the backup to your PC....then put everything back...
Are you on a custom ROM or something?...
What variant are you on? If you are using an XT1060, there is a better way.
Click to expand...
Click to collapse
Ah, so you're saying, remove photos/videos/etc so there's room for a full nandroid, yes?
No custom ROM; I'm on XT1056.

d0g said:
Ah, so you're saying, remove photos/videos/etc so there's room for a full nandroid, yes?
No custom ROM; I'm on XT1056.
Click to expand...
Click to collapse
Yes, it will erase it - unless you modify the XML or manually flash and skip the erase userdata command. I suggested that you take a nandroid backup, then reboot. Connect to your PC, and copy the entire nandroid backup to your PC.
Regardless, you should connect the phone to your PC and save everything on the SDCARD.

Use Philz cwmr & you can do a backup right to your computer (USB mount or OTG). Or use online backup apk (play) & do a nandroid right from your home screen to your OTG card.

As indicated.... Kind of a waste of time. If you go to 4.4.4 then try to nandroid restore to 4.4.2...assuming it even works... You'll be on the wrong bootloader. Then you risk many issues, the worst being a possible brick if you take an OTA down the road... Or for another reason.
Just backup apps and data if you wish... With titanium backup for example... Then if you want to be safe, transfer all your pics and what not, and the titanium backup file to your pc. Then upgrade.
You're pretty much stuck with 4. 4.4.... So a nandroid is pretty much not needed.

Use 'adb pull' to get whatever you want off the phone onto your computer.

[Q] Questions regarding compressed recovery img and data on note 4

Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.

Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.

Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app

ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.

Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.

YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)

Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working

Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.

I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app