Related
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
I hadn't seen mention of this in the EVO LTE forum, but here's a way to backup everything before the HTCDev unlock that wipes your phone.
I was waiting for some way of doing this since you can't run Titanium Backup before getting root, and getting root (with current HBOOTs) wipes your phone. Found this in the generic Android hacking section:
http://forum.xda-developers.com/showthread.php?t=1844032
I never knew there was an ADB Backup command. I've posted questions before and nobody mentioned it.
Since the phone prompts for an encryption password, it probably does do a deep copy of all the app settings.
I haven't actually done the restore from this yet - I'll be rooting this weekend then try the restore.
(Also backed up in MyBackup Pro just in case, for the little good that does.)
It's a huge Windows .BAT file that presents a menu of choices. It DOES take a while. Set a path, then choose a backup option.
I'm trying several different backup options under different backup names to see what restores the best.
If this works as advertised, it should save me days of re setting everything up and many rounds of annoyances about apps that no longer remember their settings.
OTOH, If this doesn't work, don't blame me
Dont you still need root to gain access to app data and the system files?
Sent from my EVO using Tapatalk 2
I would assume this uses fastboot root for anything that can't be accessed but fastboot has access to practically everything, there's even a fastboot command to flash splash screens lol
Again, I haven't tried the restore yet, but it looks to me like it requests the system to do it, which asks your permission first, so I'm assuming it gets everything.
I ran it with the phone booted up and it didn't complain. I guess I'll find out when I unlock and try to restore.
I may play with this later, seems like something handy for my guide
Sorry, I'm still too tired to understand what the hell is going on half the time, you're talking about adb and I'm taking about fastboot lol
pbarrett said:
Again, I haven't tried the restore yet, but it looks to me like it requests the system to do it, which asks your permission first, so I'm assuming it gets everything.
I ran it with the phone booted up and it didn't complain. I guess I'll find out when I unlock and try to restore.
Click to expand...
Click to collapse
Wouldn't think the restore would mess anything up, but I'm paranoid as $h1t with this phone.
Ask me about my ability to annoy complete strangers!
Nah its just a couple of image files, the worst thing that could happen is a bad flash that you can easily recover from in recovery
Hmm.
Well restoring a backup that didn't include system data *does* restore the app settings.
Now I'm trying restoring a backup that did include system data (the one marked as "unsafe" in the menu).
I'm hoping it'll restore my home screens, WiFi credentials, etc. The backup with system data took maybe 2 hours.
I'll check the restore in the morning...
(Oh well, either way, now that I'm rooted I can ditch all this and just go with Titanium from now on. Yay.)
Results:
Restoring a backup without system data did get all my app data/settings back.
Restoring a backup that included system data also had the side benefit of restoring the boot screen without the red tamper warning even though I'm S-ON. LOL.
I wonder if modifying a backup file then restoring it could be exploited...
This type of backup also includes all the SD contents. You might want to manage media files yourself instead.
Neither type restored home-screens. In fact, after restoring the one with system data, I had no icons or widgets whatsoever.
Even when I also told MyBackupPro to restore homescreens I got nothing. Oh well.
pbarrett said:
Results:
Restoring a backup without system data did get all my app data/settings back.
Restoring a backup that included system data also had the side benefit of restoring the boot screen without the red tamper warning even though I'm S-ON. LOL.
I wonder if modifying a backup file then restoring it could be exploited...
This type of backup also includes all the SD contents. You might want to manage media files yourself instead.
Neither type restored home-screens. In fact, after restoring the one with system data, I had no icons or widgets whatsoever.
Even when I also told MyBackupPro to restore homescreens I got nothing. Oh well.
Click to expand...
Click to collapse
Very interesting...You could be on to something there with exploiting a backup. May want to drop the lazy panda devs a line and see if it could be used to downgrade the hboot in some way. When you restored the system partition did you lose root?
Sent from my EVO LTE
Nope - I was wondering if that would happen, but it's still rooted & su, busybox, etc are still there.
It restores the screen as a side effect of copying the entire system state. As a restore you get the system state in tact as it was before the phone gets tampered. An interesting exercise would be to see if you can use the back up function to flash a system state with superuser privledges
Gaining root with fastboot...I like it. Are the backups locked to the device or can they be shared and restored on others?
Sent from my EVO LTE
I would assume they aren't but they may have access to back up misc info related to only that phone. I haven't had a chance to poke around with this program yet
pbarrett said:
Neither type restored home-screens. In fact, after restoring the one with system data, I had no icons or widgets whatsoever.
Even when I also told MyBackupPro to restore homescreens I got nothing. Oh well.
Click to expand...
Click to collapse
That's one of the many reasons why I use Apex. It allows you to back up and restore your home screens and settings. I also find that the multitasking is much improved if the sense launcher isn't running.
premo15 said:
Very interesting...You could be on to something there with exploiting a backup. May want to drop the lazy panda devs a line and see if it could be used to downgrade the hboot in some way. When you restored the system partition did you lose root?
Sent from my EVO LTE
Click to expand...
Click to collapse
Anybody know if it is actually possible to exploit hboot using this adb method or something similar. Has a hboot been exploited vin the past through adb
Sent from my EVO using xda app-developers app
It has been but only on early versions of Android, the odds of an exploit found like that again isn't at all likely. We just like to think out loud
I can't get this working. I run UBT.bat and it just flashes on my screen and closes.
Flashed My wife and I's OG's with CM 10.2. She was coming from stock 4.0.1 I was coming from 4.1.2
My has no problems. Hers wouldnt connect to wifi even though it could pick up the signals.
Last night her Kernel crashed. I figured maybe I didnt fully wipe her files clean so I rebooted her into recovery and did a factory wipe,
cleaning Dalvik, etc. and reinstalled.
Still no wifi connectivity.
Is this a driver, antennae, modem issue? Please help, I've run out of ideas.
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Hmmmmm
Dr0!dFreek said:
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.1.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Roms for the OG don't contain modems, your wife's phone would still have ICS modem. If you had the ota to 4.1 on your phone it will have jb modem.
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
[r.]GimP said:
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
Click to expand...
Click to collapse
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
adfurgerson said:
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
Click to expand...
Click to collapse
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
How does this sound?
[r.]GimP said:
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
Click to expand...
Click to collapse
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
brionbey said:
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
Click to expand...
Click to collapse
Don't panic, you can always load onto the SD card externally, with a microsd to SD adapter or through TWRP/CWM with "mount usb storage" mode. Failing both of those things I'm fairly certain one of your two phones will be enough to load the SD card for the other phone if needed.
I'm thinking everything you need is going to be the LGNPST route now anyway, and that being said you may as well just flash them both to stock 4.1.2 in that case. First things first, you definitely want to backup before anything gets out of hand, if twrp isn't getting it then pull with adb. Quick breakdown of that below.
The universal drivers straight off the LG site work just fine, but in my experience to get the adb part happy you need to click on your devices, and find your phone, whether it says LG/Nexus4/MTP, doesn't matter. Open it and click on the hardware tab, it should list 3 devices.
unknown (or adb if you're lucky)
Your phone
USB Composite Device
If the top isnt some variation with ADB in the name, double click it, then change settings, it may say drivers not loaded, so on the driver tab we're going to give it one.
Update driver, and it will ask how, the option on the bottom is "browse my comp for driver software" and after that the bottom option again is "let me pick from a list..." I think then it shows a split list, the device type should be ADB something, and if you installed the LG universal drivers then near the bottom you will have "LGE Mobile Sooner Single ADB Interface" windows will complain because it couldn't figure out that its the right driver, confirm you want to use it and it will then show "this device is working properly" go ahead and close all those windows and it will update on the first one with the three devices listed the next time you open it.
At this point you need the adb application itself, I usually just download the whole android SDK personally, but where you get it from doesn't matter. If you're booted in android, make sure adb has root access in developer settings, and debugging is enabled.
open a command promt, for the sake of easy navigate to the folder where you put adb, in windows, or in the SDK example, /android/sdk/platform-tools/ hold shift and right-click on an empty space and select "open command window here"
If android is running, type "adb root" without quotes
and adb will inform you its restarting, if in twrp you will already be root.
Type "adb devices" and as long as its not blank you should be good
again, for the sake of easy "adb backup -shared -all"
and let it do its thing, it should start creating a default file named "backup.ab" it's bound to take awhile as -shared should grab all the sd card contents just to be safe.
Disaster recovery aside, I would use a combination of Titanium backup root, and "backup your mobile" - especially add the second option in addition to titanium, thats one of the only free backup apps that can get MMS as well as SMS, and restore them.
Again, if you're having issue with the computer normally seeing the device, these are still good tools, save to external sd card, remove card and transfer manually to your computer.
ok.. now that all your stuff is *hopefully* now redundantly backed up, depending on the stock image you find, you can either push it via fastboot commands or flash with lgnpst. I know the images are in our forum, most likely in the lgnpst thread. just follow through that and read well ahead before performing each step, you'll be ok.
I believe fastboot can relock your bootloader in all off one command, i don't have the answer if its necessary or not to receive the OTA, but having skimmed the lgnpst thread in the past, I'm positive people have done the flash and then had the OTA pushed from AT&T so they could get up to 4.1.2 for the official JB and partitions. Like I said in the beginning, your call if you want to skip that and just lgnpst to 4.1.2 since you're there anyway. Also, keep an eye out for one of the recent restore to stock / RPM/TZ partition threads, I think shellnutt making a cwm/twrp flashable zip to do the same thing lgnpst teeny bin would without even needing lgnpst.
So, barring a complete hardware failure, dont be scared. Get your data for now, then on to the next step.
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed.
Sent from my Optimus G using Tapatalk 4
I agree also! feels great to have some help with this. attempting fixes I'll report back.
Sent from my LG-E970 using XDA Premium 4 mobile app
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
brionbey said:
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes that sounds fine, in that case I would just make the apps and messages backups with titanium/backup your mobile
I'm not 100% if the lgnpst flash to JB wipes user data or not, but after that you can flash pretty much ANY rom for our device, then just download titanium/backup your mobile from the app store and point it to the directories on the sd card, and restore selectively.
For the most part you can move everything from /sdcard to /external_sd and move it back over when you're done, I think the JB radio (or modem, both terms apply) works very well for everything I've used (and yes they play a significant part in wifi and gps also), and I was a pretty hardcore flash-a-holic for a really good while, still haven't tried the hybrid modems and people rave about how well they work. Sounds like a good plan you got going, once you're up with the partitions and the JB modem from 4.1.2 you really should have no issues, and once you have that freedom, and she will as well to try out all manner of ROM's, you'll find you get really good at backup/restore out of necessity. Happy flashing.
If you need any specifics, aside from the step by steps of the other threads I'm glad to lend advice, just let me know
-edit- you can make multiple backups with each program by the way, titanium and backup your mobile.
Titanium free says only one backup per app, but in reality just hit the batch button on the top right, looks like a check mark, have it get all apps and system settings, then just move the whole folder you set for titanium off of the device for safe keeping. This way you can backup everything running right now, then if you want to restore the other one, you could even do it again, if you just wanted to cherry pick some stuff, then flash, etc. Titanium free wont let you make multiple copies of the same app, but it also WONT delete extras if you already have them, so if you dump a few titanium folders into eachother and merge them, you can then choose any of the backup files or data or both from each date.
The reason I use both programs is as I said earlier, backup your mobile handles SMS/MMS very efficiently, and occasionally I'll let it grab a few user apps, and system apps, because when it restores them, it restores for example, flash player from LG stock rom, as a user app, and it continues to work flawlessly. Titanium can't get over it being a system app, and sucks at restoring flash.
However, titanium is GREAT for also saving user data, not just the program itself. ie.. savegame states for any app you have that doesnt explicitly sync online, or the login data for facebook, or adfree with the most current hosts so you dont have to redownload or even type your logins, very convenient.
My personal order of operations before I flash a new rom, or even upgrade to a new version with a clean flash instead of a "dirty" is to fully backup all apps/system data with titanium, then hit ByM for contacts/sms/mms/bookmarks/user dictionary/apps
then a nandroid backup, since it is basically a perfect snapshot itself, just like turning the phone off, and back on.
after rom flash / gapps, I boot, setup google real quick, goto app store and cancel the 5 million downloads, except for titanium/ByM
after those download I roll my messages/user dictionary/contacts/ selective apps I know i'll use, and the same with a few from titanium.
This way I'm less bloated with crap I probably don't use everyday, and if i need it, its a few taps away. It's a very painless process and a lot of peace of mind having everything safe, and allows you to try alot of unstable crap knowing how easy you can always roll your CWM/TWRP backup over to the device like you never left.
Sorry, I'm a fan of ranting. Pics for adb driver steps explained in previous post, and the backup part, for reference if you ever need them.
View attachment 2263477
View attachment 2263478
Ok, I'm keepin cool but it seems to be one thing after another
I made the backup before the original flash.
I see it in the folder. When I restored it, it is the same rom that I'm on CM 10.2
I'm not sure how that happened.
Thanks for the images, that really helped unstuck me.
Question: I've checked the threads looking for the stock [ROM] 4.1.2 and Gapps for E970 and can't find them anywhere.
At this point I just need a doOver. I have to get my wife her phone back, ASAP and if I brick by some chance, I'll never hear the end of it.
EVER.
Or how about just flashing the radio? Can I do that to at least get her Wifi?
Here is the flashable jellybean radio by g33k3r.
http://forum.xda-developers.com/showthread.php?t=2220048
I recommend still updating her to the jellybean partition layout when you get a chance, but this should get you working WiFi at the very least.
Sent from my LG-E970 using xda app-developers app
Flash the Radio
Thanks SnowLeopard.
So all I need to do is just boot into recovery using TWRP and Install the radio, or should I factor reset and install the radio at the same time as the rom?
Thanks Again Guys. (or gals)
Lgnpst doesn't touch the /data partition.
Sent from my Optimus G using XDA Premium 4 mobile app
the modem work great.
Sent from my LG-E970 using XDA Premium 4 mobile app
At gimp, followed instructions exactly, computer recognize device, only thing left to do is run teeny bit, but getting error path not found
Sent from my LG-E970 using XDA Premium 4 mobile app
This is a repost - the original is here but no one could forward me to a proper section of the forums.
Some update to the info below:
- on the initial 4.2.x version of the running android I had most of my apps moved to the external sdcard (sdcard0) - that was their location (.assec) when I did the adb backups
- in the meantime I checked more of my backups and they seem OK - I could uncrypt the ab to normal tar archives and see the contents of apps and shared folders
I would post more links to the device info but I am not allowed to post links.
Some forum posts related to the device:
http://forum.xda-developers.com/showthread.php?t=2639416
http://forum.xda-developers.com/showthread.php?t=2399708
#######
Hello there,
I need some info on how or if it is possible to make use of my full adb restore file or I just throw it away and restart fresh of my device.
Device is allview viper v1 (16Gb) -
NO ROOT and not interested in rooting it.
I believe I made a few versions of good back-ups including at least one good full backup including apks by using UBT (1.3.2 version if I am not mistaking).
My problem: I can't restore the phone by using any of the created ab files by using adb which drives me nuts.
It's worth to mention that in between I upgraded the phone software from 4.2 to 4.4 by using the producer's update images... I did a factory reset with 4.4 and re-installed most of the apps I had. I even copied most of the data from a file-sync backup...
Every time I try to use adb restore I get to the screen to input (now 2 passwords which basically are the same), I get the message "restore starting" and quite fast "restore finished" on the phone screen though while using the full back-up I definitely see that adb is still accessing / reading the file for longer time...
What I tried further: I used abe (android backup extractor by tweaking their .sh script) to create both standard individual .ab-s but also kitkat compatible ones (with abe pack-kk) with no luck in restoring the apps and their data.
It is quite annoying since after converting to .tar and un-tar-ing I can see that the backups seem ok and I can even see the sqlite data and xml settings for the apps but I do not know how to import those to the new OS running on the phone.
I tried this using both USB storage, picture mode, etc., input only the desktop pass and afterwards inputing both of the asked passwords.
So the question is: can I restore the data (about 32Gb including the pics and docs) or should I delete all the "working" files I created and put it on the "learn by error"?
Should I try to downgrade to 4.2. (if it is even possible..) and try the adb restore there?
Cheers and thanks in advance.
this is [not necessarly] a bump... but maybe a sad discovery...
are all the users of this portal just dumb script kiddies and no real user / developer of android (... use here all the smart-device-OS) apps and hackers?!
I am kind of disappointed that not even one "dev" tried to answer this post with valuable info...
i guess this is just a ad-catcher portal for the consumer-ignorant mass of users of "smart" devices...
sad, really sad.
take care and sleep well!
I'm hoping I'll run into a merciful soul who can help me with some stupid questions. I'm trying to backup app data from my old phone (stock, unrooted Android 8.0) and restore it on my new phone (stock, unrootedAndroid 13).
I previously used Helium to do this, with this exact same model of Android 8.0 phone (LG V20) with no issues. That was several years ago, though. Now I'm encountering two problems:
1. Several apps, such as Candy Crush, are listed as "backup disallowed" in the Helium backup menu. I definitely backed these up in the past, so I'm not sure what's going on.
2. Even with the apps I can backup, I can't get them to restore on the new 13 phone, as the Helium app doesn't seem to see them. It does see my older backups from several years ago, and I can restore from those, but that's not very helpful in this case. The only thing I can guess is causing this is it looks like the newer backups (which are in the same \carbon folder as the old backups that still work) are .ab format while the older ones are all .json format.
I have been researching for days on how to fix this, but I usually end up in threads that go into fairly complex (for me) cmd commands, and I just can't seem to follow them. I'm sure they're written quite well for someone who has some familiarity doing that, but I just don't. I've only ever used cmd when getting specific, step-by-step, dummy-level instructions from tech support.
If anyone can help me surmount these issues, whether through Helium or some other (non-root required) method, I would be really grateful.
If an app disallows backup of its data then no chance when using 3rd-party tools like Helium.
If you don't have root, you always can use the command-line program ADB to make backups with the help of a desktop computer - what requires USB debugging is enabled on both phones in question.
jwoegerbauer said:
If an app disallows backup of its data then no chance when using 3rd-party tools like Helium.
If you don't have root, you always can use the command-line program ADB to make backups with the help of a desktop computer - what requires USB debugging is enabled on both phones in question.
Click to expand...
Click to collapse
I really, really appreciate your response.
Do you know of any guides for doing this at:
1. Are written for complete idiots like myself? The ones I've found seem to presume a level of comfort with command line interfacing that I just don't have.
2. Go over backing up and restoring data for specific apps? The ones I've found focus on replicating the entire phone.
I'd be willing to root my old phone, but my understanding is that, since it's never been rooted before, this would delete all the app data I'm trying to save. Plus my new phone is a Samsung, and I've read that the newer Samsungs like mine simply cannot be rooted.
Edit: I probably should have mentioned that this is the thread I've found that has gotten me closest to understanding: https://forum.xda-developers.com/t/...me-between-phones-adb-shell-non-root.4378323/
The main issues I'm facing are:
It says to download the attached "adb.rar," but none of the other threads had mentioned any downloads, so I'm worried about doing that.
It talks about getting app info from "BS4/Pro," but there's no links. I have no idea what that is. So far as I can tell, I can just get the app name by looking at the folder name on my phone or from within the CMD adb commands, but I'm always worried about making assumptions when I already know I have no idea what I'm doing.
Also, I've seen some threads mention that even this method won't work with apps that have backup blocked, but I'm willing to try if I can figure out the other issues.
if the issue is with restoring helium backup, adb is worth a try. it's basically the same method, although helium backups aren't compressed.
if new phone is rooted, restoring backups is possible with more advanced methods.
for apps that have backup opted out, try phone clone apps.