I have to move to a new phone. I backed up my old one to the SDcard. I placed it in the new phone and booted into TWRP. When I enter the restore menu, I go to ext card and it doesn't show any backups. I am not sure why TWRP does not see my sdcard backups so I can restore my backup.
caseyatbt said:
I have to move to a new phone. I backed up my old one to the SDcard. I placed it in the new phone and booted into TWRP. When I enter the restore menu, I go to ext card and it doesn't show any backups. I am not sure why TWRP does not see my sdcard backups so I can restore my backup.
Click to expand...
Click to collapse
There different serial#s it dosent recognize that phone I had the same problems when I switched my s3 to another s3
Sent from my SPH-L900 using xda premium
Will it work with CWM or just start from scratch?
Sent from the Delta Quadrant using XDA Premium
caseyatbt said:
Will it work with CWM or just start from scratch?
Sent from the Delta Quadrant using XDA Premium
Click to expand...
Click to collapse
CWM backups can only be restored with CWM, and TWRP backups can only be restored with TWRP
CNexus said:
CWM backups can only be restored with CWM, and TWRP backups can only be restored with TWRP
Click to expand...
Click to collapse
Sorry, what I meant was, if I install CWM, will I have a better shot at a restoration or does CWM check serials as well?
caseyatbt said:
Sorry, what I meant was, if I install CWM, will I have a better shot at a restoration or does CWM check serials as well?
Click to expand...
Click to collapse
And that's what I'm answering. CWM won't even attempt to restore it (much less check the serial) because its in a different format than what it saves its backups as, you have to be on TWRP if you even wanna try it
caseyatbt said:
I have to move to a new phone. I backed up my old one to the SDcard. I placed it in the new phone and booted into TWRP. When I enter the restore menu, I go to ext card and it doesn't show any backups. I am not sure why TWRP does not see my sdcard backups so I can restore my backup.
Click to expand...
Click to collapse
Are you just trying to restore apps or what?
@OP I actually started a similar thread a while back that could have given you the solution make a backup on your new phone using twrp, then on your sd card within the twrp folder there should be two folders with different numbers, one will have the backup you just made and the other will have your old backups. Move the files with the old backups into the folder which contains the new backup, then delete the old, empty folder. Now you can restore your old backups
Sent from my SPH-L710 using Tapatalk 2
CNexus said:
And that's what I'm answering. CWM won't even attempt to restore it (much less check the serial) because its in a different format than what it saves its backups as, you have to be on TWRP if you even wanna try it
Click to expand...
Click to collapse
I meant install CWM, then make a backupwith CWM and use CWM on a new phone.
imaconeheadXD said:
@OP I actually started a similar thread a while back that could have given you the solution make a backup on your new phone using twrp, then on your sd card within the twrp folder there should be two folders with different numbers, one will have the backup you just made and the other will have your old backups. Move the files with the old backups into the folder which contains the new backup, then delete the old, empty folder. Now you can restore your old backups
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I tried that and it says it failed as it finishes the restore.
I decided to just restore from Titanium Backup and do the set it up over again.
WAIT
Do you mean to say that you still have the old phone? If so, there's a way to make an ODIN flashable tar of the exact state of your old phone so you can flash to your new phone
Here's a link: http://forum.xda-developers.com/showthread.php?t=1777579
Partitions are the same so you can use the script someone in there made
CNexus said:
WAIT
Do you mean to say that you still have the old phone? If so, there's a way to make an ODIN flashable tar of the exact state of your old phone so you can flash to your new phone
Here's a link: http://forum.xda-developers.com/showthread.php?t=1777579
Partitions are the same so you can use the script someone in there made
Click to expand...
Click to collapse
That is cool! Thanks. I have made the images, but making them flash-able seems a little less clear.
caseyatbt said:
I have to move to a new phone. I backed up my old one to the SDcard. I placed it in the new phone and booted into TWRP. When I enter the restore menu, I go to ext card and it doesn't show any backups. I am not sure why TWRP does not see my sdcard backups so I can restore my backup.
Click to expand...
Click to collapse
TWRP bases backups and restores on serial number in a couple places. I've only done this from same phone to other of the same phones I've gotten of the same model (e.g. S3 to S3, HTC One 32GB to HTC One 64GB). Not sure how it would work from different model to different model - spose it depends on what you are restoring., model, rom, etc.
TWRP backup directory is sdcard/TWRP/BACKUPS/[SerialNumberOfDevice]/[timeStampOfBackup]/
Change the directory name to the serial number of the new device you want to restore to. Then, go to /[timeStampOfBackup]/recovery.log and do a find/replace on all of the old serial number with the new serial number - I believe there are 8 or 9 instances.
If you change the directory name from w/in TWRP recovery console, reboot - then it'll show up as a recovery option... though, you'll need to update the log file another way -if it's on an sdcard (vs. an HTC One where there is no true sdcard) neither should be a problem.
cheers
hex90 said:
TWRP bases backups and restores on serial number in a couple places. I've only done this from same phone to other of the same phones I've gotten of the same model (e.g. S3 to S3, HTC One 32GB to HTC One 64GB). Not sure how it would work from different model to different model - spose it depends on what you are restoring., model, rom, etc.
TWRP backup directory is sdcard/TWRP/BACKUPS/[SerialNumberOfDevice]/[timeStampOfBackup]/
Change the directory name to the serial number of the new device you want to restore to. Then, go to /[timeStampOfBackup]/recovery.log and do a find/replace on all of the old serial number with the new serial number - I believe there are 8 or 9 instances.
If you change the directory name from w/in TWRP recovery console, reboot - then it'll show up as a recovery option... though, you'll need to update the log file another way -if it's on an sdcard (vs. an HTC One where there is no true sdcard) neither should be a problem.
cheers
Click to expand...
Click to collapse
I'm having a similar issue with TWRP not seeing backups but my device didn't change. I found my serial number but it's a long, 14 digit number and the folder you mention above is about 8 characters long consisting of characters and numbers. I tried to convert my serial number (is Hex I believe) to ASCII but it doesn't render the same name as the folder (not even close in terms of length). Any idea as to how I can convert it?
robertfah said:
I'm having a similar issue with TWRP not seeing backups but my device didn't change. I found my serial number but it's a long, 14 digit number and the folder you mention above is about 8 characters long consisting of characters and numbers. I tried to convert my serial number (is Hex I believe) to ASCII but it doesn't render the same name as the folder (not even close in terms of length). Any idea as to how I can convert it?
Click to expand...
Click to collapse
I think the easiest way of getting the "new" serial number is just to create a new TWRP backup for your phone (maybe something small like just recovery). It'll create a new folder with the name of your "new" serial number. That's the one you'd want to use.
robertfah said:
I'm having a similar issue with TWRP not seeing backups but my device didn't change. I found my serial number but it's a long, 14 digit number and the folder you mention above is about 8 characters long consisting of characters and numbers. I tried to convert my serial number (is Hex I believe) to ASCII but it doesn't render the same name as the folder (not even close in terms of length). Any idea as to how I can convert it?
Click to expand...
Click to collapse
Connect your phone to your computer (make sure drivers are installed)
Download the adb_windows.zip from my devhost here: http://d-h.st/qmi
Then unzip that and open a command prompt in the unzipped directory (Shift + Right click > Open command prompt here)
Type "adb devices", press enter, and you'll have your serial in the following form:
Code:
xxxxxxx device
Last step: profit
topherk said:
I think the easiest way of getting the "new" serial number is just to create a new TWRP backup for your phone (maybe something small like just recovery). It'll create a new folder with the name of your "new" serial number. That's the one you'd want to use.
Click to expand...
Click to collapse
Yeah I did that but once again, I couldn't see it through TWRP (but could through Root Explorer or Windows Explorer).
CNexus said:
Connect your phone to your computer (make sure drivers are installed)
Download the adb_windows.zip from my devhost here: http://d-h.st/qmi
Then unzip that and open a command prompt in the unzipped directory (Shift + Right click > Open command prompt here)
Type "adb devices", press enter, and you'll have your serial in the following form:
Code:
xxxxxxx device
Last step: profit
Click to expand...
Click to collapse
Thanks for this...after doing this, the serial number was the same, however, I ran across this thread http://forum.xda-developers.com/showthread.php?t=2178264&highlight=twrp+not+finding+backups&page=2 and found Post #14 to be very helpful and my possible solution.
As it turns out, when I connect my phone to my computer, I get the drive "SPH-L710" and the folders "Card" and "Phone" within that. Phone has a 0 folder in it and I copied the TWRP from Phone\TWRP to 0\TWRP and then I was able to view them and restore them in recovery.
So why isn't TWRP storing the backups in 0\TWRP? What is supposed to be in the 0 folder and the Phone folders? it looks like I have some duplicate folders going on:
Phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
0:
This actually worked for me. I bricked my LG G3, got Verizon to send me a replacement LG G3, and then I used the TWRP backup that I had made to restore everything. Thanks for this information.
How I got it to work was I made a TWRP backup on the new phone, transferred the backup that I had made on the old phone to the new phone, rename the new backup to something, and rename the old backup to to match the original name of the new backup.
TWRP backup directory is sdcard/TWRP/BACKUPS/[SerialNumberOfDevice]/[timeStampOfBackup]/
Change the directory name to the serial number of the new device you want to restore to. Then, go to /[timeStampOfBackup]/recovery.log and do a find/replace on all of the old serial number with the new serial number - I believe there are 8 or 9 instances.
If you change the directory name from w/in TWRP recovery console, reboot - then it'll show up as a recovery option... though, you'll need to update the log file another way -if it's on an sdcard (vs. an HTC One where there is no true sdcard) neither should be a problem.
cheers[/QUOTE]
Thanks I got it working like this
During the TWRP restore process (old phone backup to new phone but same model), should I restore every partition to have everything working properly? or maybe just system+data?
I mean about screen as below:
I am not sure if I should also restore partition as: modem, boot?
Related
I had to have my note2 replaced I did a twrp backup placed it on new phone in the backup twrp folder but it is not recognized. Anyone have any possible solutions? Really all I'm after is game data that was backed up,and I'm not sure where to find that particular file in the backup thanks.
pretty sure u wouldnt wanna do a full nandroid restore of your partitions to another device... but as far as your game data goes.... you can use titanium backup to recover the apk and the game data by extracting from the nandroid backup file.
I've tried to do this before. It won't work.
Sent from my SGH-T889 using xda premium
Hey buddy. New device just start fresh. Safest way...
Hey,
I was on the same boat as u. I got it to work. I can remember the specifics at the moment but gist of it is that twrp creates a specific backup folder unique to each device. Open up an file browser and navigate over to where u have your backup. If theyre o. Your sd card it should be TWRP > BACKUPS > (Here u should find 2 folders with a bunch of random letters and numbers)
Those 2 folders are your backup folders. One was from your old device and the other is the folder twrp created for your new device.
When u reeboot into recovery, twrp wont recognize the old backup folder since it was unique to your old phone.
Long story short. Lol. Just go into the old folder from the file browser and copy the backup to the new back up folder.
After that, delete the old backup folder. Your backup should then show up when you boot into recovery.
As for which is the old and which is the new folder. My best bet is tbat the new folder is empty and the old folder has your backup.
Hope that helps.
Let me know if you need more help.
I bought a 16GB a few weeks back from Amazon. I noticed there were some dead pixels so I ordered a replacement. I want to clone the replacement to be exactly like the old one. Both tablets are rooted and have TWRP recoveries. I did a nandroid on the one I'm sending back. I copied the TWRP folder that contains the backup files to the new one. When I boot into recovery on the new one and click on restore, there isn't anything on the list to restore. I browsed the SD card and verified that there are things in the TWRP folder.
One thing I noticed in the backup folder, there is a folder with the serial number of the broken device. Since the serials are different could that be why the new one shows nothing? Do I need to rename the folder to the current serial number? I need help getting the backup to show up on the new device.
After the nandroid restore, I plan on running adb pull /sdcard/ \sdcard\ and plan to push the data back so that all my data is exactly the same since nandroid doesn't backup /sdcard.
Thanks!!
I'd rename the serial #s like you suggested.
You don't need to rename anything. Just copy your old folder (e.g. 2013-08-25--14-50-44) to /sdcard/TWRP/CurrentDeviceNumber/
Hello, everyone!
After painful research I'm think I have found the location of IMEI in I9195 and have some understanding of IMEI preservation mechanics. Here are some things that users / developers might need to know. If I am wrong, please correct me.
IMEI is stored in nvrebuild1 & nvrebuild2 (partition labels are modemst(1 & 2), blocks 11 & 12).
Backups of these partitions are stored in partition labeled fsg and backup and in case partition is empty/corrupted, phone automatically makes backup on boot/reboot/shutdown.
Everytime phone boots, it automatically runs nvrestore command, so whatever is stored in fsg/backup partitions is automatically restored on modemst1 & modemst2. So, if you want to make any changes to these partitions, it is mandatory to reboot phone through adb / terminal emulator (while having su) using "reboot nvbackup" command after you have made changes to partition data, to push whatever changes you have made to take effect.
Also, both modemst1 & modemst2 contain IMEI. In case one gets damaged, it is repaired by gathering data from another.
Mind you, this system is very effective, it's almost impossible to trash your phone, cause I doubt that any rom will touch backup & fsg partitions. Yet, somehow (thanks to experimenting) I've manged to trash 2 I9195 :crying:
GUIDE
SIMPLEST WAY TO BACKUP YOUR IMEI IS RUN A COMMAND IN TERMINAL EMULATOR ADB - reboot nvbackup.
TO RESTORE - reboot nvrestore
BACKUP
Requirements:
Root access
Busybox
1.Download EFS Professional from thread in this forum.
2. Run EFS Professional and from main form select EFS Professional
3. Click Backup
4. In devices filter select All Partitions
5. Press Deselect all and manually select mmcblk0p11 & mmcblk0p12 (make sure the labels for these partitions are modemst1 & modemst2)
6. Click Backup.
7. Done
Backup will be created both on your phone and in EFSProBackup folder in your EFS Profesional folder. Now make sure you store copy of backup in place that never sees light and in some online source that doesn't occasionally decide to wipe it's data.
RESTORE - METHOD 1: EFS PROFESSIONAL.
Requirements:
Root access
Busybox
Terminal Emulator / ADB
1.Download EFS Professional
2. Run EFS Professional and from main form select EFS Professional
3. Click Restore
4. Select Backup
6. Click Restore
7. DO NOT MANUALLY RESTART YOUR PHONE! CHANGES WILL NOT APPLY.
8. In terminal emulator / adb type reboot nvbackup and hit enter.
9 Success!
THIS THREAD WILL BE UPDATED VERY SOON SINCE ITS NOT COMPLETE.
Nice info, thank you
farewellartist said:
Hello, everyone!
After painful research I'm think I have found the location of IMEI in I9195 and have some understanding of IMEI preservation mechanics. Here are some things that users / developers might need to know. If I am wrong, please correct me.
IMEI is stored in nvrebuild1 & nvrebuild2 (partition labels are modemst(1 & 2), blocks 11 & 12).
Backups of these partitions are stored in partition labeled fsg and backup and in case partition is empty/corrupted, phone automatically makes backup on boot/reboot/shutdown.
Everytime phone boots, it automatically runs nvrestore command, so whatever is stored in fsg/backup partitions is automatically restored on modemst1 & modemst2. So, if you want to make any changes to these partitions, it is mandatory to reboot phone through adb / terminal emulator (while having su) using "reboot nvbackup" command after you have made changes to partition data, to push whatever changes you have made to take effect.
Also, both modemst1 & modemst2 contain IMEI. In case one gets damaged, it is repaired by gathering data from another.
Mind you, this system is very effective, it's almost impossible to trash your phone, cause I doubt that any rom will touch backup & fsg partitions. Yet, somehow (thanks to experimenting) I've manged to trash 2 I9195 :crying:
GUIDE
SIMPLEST WAY TO BACKUP YOUR IMEI IS RUN A COMMAND IN TERMINAL EMULATOR ADB - reboot nvbackup.
TO RESTORE - reboot nvrestore
BACKUP
Requirements:
Root access
Busybox
1.Download EFS Professional from thread in this forum.
2. Run EFS Professional and from main form select EFS Professional
3. Click Backup
4. In devices filter select All Partitions
5. Press Deselect all and manually select mmcblk0p11 & mmcblk0p12 (make sure the labels for these partitions are modemst1 & modemst2)
6. Click Backup.
7. Done
Backup will be created both on your phone and in EFSProBackup folder in your EFS Profesional folder. Now make sure you store copy of backup in place that never sees light and in some online source that doesn't occasionally decide to wipe it's data.
RESTORE - METHOD 1: EFS PROFESSIONAL.
Requirements:
Root access
Busybox
Terminal Emulator / ADB
1.Download EFS Professional
2. Run EFS Professional and from main form select EFS Professional
3. Click Restore
4. Select Backup
6. Click Restore
7. DO NOT MANUALLY RESTART YOUR PHONE! CHANGES WILL NOT APPLY.
8. In terminal emulator / adb type reboot nvbackup and hit enter.
9 Success!
THIS THREAD WILL BE UPDATED VERY SOON SINCE ITS NOT COMPLETE.
Click to expand...
Click to collapse
Hey farewellartist! Thank you for all this and looking forward for more.
Like, how/where to find the two IMEIs in those backed-up partitions for a i9192 (dual sim).
We know that it was possible to find it in the nv_data files using a hex editor for some older phones, but it doesn't seem to work the same way with these new systems.
I'm just awfully curious. I'm not bold enough to play around with the insides of these phones
Cheers
Alkim
Hi, is it not enough to perform a full backup with CWM to have a backup of IMEI?
I've yet to try this guide, but I found an app in the play store "EFS MANAGER S4" which claims to backup and restore your EFS partition data, I've installed the app, one click 'make backup'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the files and file sizes created by the app itself
Sent from my GT-I9195 CARBON ROM KK 4.4.2
kamikaze702k said:
I've yet to try this guide, but I found an app in the play store "EFS MANAGER S4" which claims to backup and restore your EFS partition data, I've installed the app, one click 'make backup'
These are the files and file sizes created by the app itself
Sent from my GT-I9195 CARBON ROM KK 4.4.2
Click to expand...
Click to collapse
Thanks! It's really working here too!!
Tapatalk-kal küldve az én GT-I9195-el
radicspeter said:
Thanks! It's really working here too!!
Tapatalk-kal küldve az én GT-I9195-el
Click to expand...
Click to collapse
Your welcome, hope this can help other users, it's really important to make this EFS backup, esp if one is playing around with custom ROMS etc
Sent from my GT-I9195 CARBON ROM KK 4.4.2
kamikaze702k said:
I've yet to try this guide, but I found an app in the play store "EFS MANAGER S4" which claims to backup and restore your EFS partition data, I've installed the app, one click 'make backup'
These are the files and file sizes created by the app itself
Sent from my GT-I9195 CARBON ROM KK 4.4.2
Click to expand...
Click to collapse
Do you have the link? Can't find in playstore! Maybe it is not available to my country!
luisbraz said:
Do you have the link? Can't find in playstore! Maybe it is not available to my country!
Click to expand...
Click to collapse
Me neither. Can't find it in play store
Enviado desde mi GT-I9195 mediante Tapatalk
Hold on guys, it's available in play store but not in some countries, it's a free app, so I will upload it to Dropbox and share the link in my next post
Sent from my GT-I9195 CARBON ROM KK 4.4.2
---------- Post added at 11:04 PM ---------- Previous post was at 10:50 PM ----------
EFS MANAGER S4 1.1
https://www.dropbox.com/s/6jqkap0ti84v6su/EFS Manager S4-1.1.apk
(Hit thanks if this helped you)
Sent from my GT-I9195 CARBON ROM KK 4.4.2
Just found it searching in google. https://play.google.com/store/apps/details?id=com.kelzsoca.efsmanager.S4&hl
It says that is not compatible with all of my devices!
luisbraz said:
Just found it searching in google. https://play.google.com/store/apps/details?id=com.kelzsoca.efsmanager.S4&hl
It says that is not compatible with all of my devices!
Click to expand...
Click to collapse
Yea sometimes it will say not compatible as it's made for S4, and only available in few countries, I found it whilst doing a Google search for EFS backup and it came up, but when I opened it in play store it said "not available in your country" so I googled searched it and eventually found the apk file itself, but as long as it works it's all good, I don't know if it really does work example to actually restore the backup in full working order, but for the peace of mind at least we know we have some sort of backup and if ever the time comes to restore it, then we'll find out
Sent from my GT-I9195 CARBON ROM KK 4.4.2
kamikaze702k said:
I've yet to try this guide, but I found an app in the play store "EFS MANAGER S4" which claims to backup and restore your EFS partition data, I've installed the app, one click 'make backup'
These are the files and file sizes created by the app itself
You think this will work of you already tripped your knox?
Sent from my SCH-I435 using xda premium
Click to expand...
Click to collapse
It should be ok but I'm not 100% sure as I've not got Knox
Sent from my GT-I9195 CARBON ROM KK 4.4.2
farewellartist
Thanks for guide!
narkoman88 said:
farewellartist
Thanks for guide!
Click to expand...
Click to collapse
Did the EFS set-up work for you?
Sent from my SCH-I435 using xda premium
farewellartist said:
Hello, everyone!
After painful research I'm think I have found the location of IMEI in I9195 and have some understanding of IMEI preservation mechanics. Here are some things that users / developers might need to know. If I am wrong, please correct me.
IMEI is stored in nvrebuild1 & nvrebuild2 (partition labels are modemst(1 & 2), blocks 11 & 12).
Backups of these partitions are stored in partition labeled fsg and backup and in case partition is empty/corrupted, phone automatically makes backup on boot/reboot/shutdown.
Everytime phone boots, it automatically runs nvrestore command, so whatever is stored in fsg/backup partitions is automatically restored on modemst1 & modemst2. So, if you want to make any changes to these partitions, it is mandatory to reboot phone through adb / terminal emulator (while having su) using "reboot nvbackup" command after you have made changes to partition data, to push whatever changes you have made to take effect.
Also, both modemst1 & modemst2 contain IMEI. In case one gets damaged, it is repaired by gathering data from another.
Mind you, this system is very effective, it's almost impossible to trash your phone, cause I doubt that any rom will touch backup & fsg partitions. Yet, somehow (thanks to experimenting) I've manged to trash 2 I9195 :crying:
GUIDE
SIMPLEST WAY TO BACKUP YOUR IMEI IS RUN A COMMAND IN TERMINAL EMULATOR ADB - reboot nvbackup.
TO RESTORE - reboot nvrestore
BACKUP
Requirements:
Root access
Busybox
1.Download EFS Professional from thread in this forum.
2. Run EFS Professional and from main form select EFS Professional
3. Click Backup
4. In devices filter select All Partitions
5. Press Deselect all and manually select mmcblk0p11 & mmcblk0p12 (make sure the labels for these partitions are modemst1 & modemst2)
6. Click Backup.
7. Done
Backup will be created both on your phone and in EFSProBackup folder in your EFS Profesional folder. Now make sure you store copy of backup in place that never sees light and in some online source that doesn't occasionally decide to wipe it's data.
RESTORE - METHOD 1: EFS PROFESSIONAL.
Requirements:
Root access
Busybox
Terminal Emulator / ADB
1.Download EFS Professional
2. Run EFS Professional and from main form select EFS Professional
3. Click Restore
4. Select Backup
6. Click Restore
7. DO NOT MANUALLY RESTART YOUR PHONE! CHANGES WILL NOT APPLY.
8. In terminal emulator / adb type reboot nvbackup and hit enter.
9 Success!
THIS THREAD WILL BE UPDATED VERY SOON SINCE ITS NOT COMPLETE.
Click to expand...
Click to collapse
Hello,
How much of a risk is this method and will it work with a tripped knox (0x1l)? Oh yeah, thank you for the effort you have put in cause nobody has really done anything. I'm still new to all this but I'm learning. I wish I could fix my Pantech Marauder cause it is actually a decent phone I want to give to my daughter.
Sent from my SCH-I435 using xda premium
I have got error "Your device is NOT Perm Rooted! The application will now exit." from EFS Professional. But I am rooted. I have SuperSU and Stericson BusyBox installed and I have disabled knox by SuperSU.
So I tried app SA Manager and it works. It made backup of EFS folder and I also simply copied EFS folder with Root Explorer. If anyone have trouble with EFS Pro then use SA Manager.
miso00 said:
I have got error "Your device is NOT Perm Rooted! The application will now exit." from EFS Professional. But I am rooted. I have SuperSU and Stericson BusyBox installed and I have disabled knox by SuperSU.
So I tried app SA Manager and it works. It made backup of EFS folder and I also simply copied EFS folder with Root Explorer. If anyone have trouble with EFS Pro then use SA Manager.
Click to expand...
Click to collapse
I had also the same issue with EFS Professional. And also used SA Manager to get a backup of EFS partition.
However as the GUIDE mentions, on S4 mini the IMEI is not stored on EFS, but on 2 different partitions (modemst1/2) + 2 backup partitions. So having backup of EFS isn't sufficient...
3g/4g no signal
Hi,
does anyone know, if empty EFS and BACKUP partitions (according to the pit file) could cause problems with 3g and 4g signal? I'm having problems with signal/no network (only 3g and 4g) after flashing different modems on my GT-I9195. Would restoring QCN do the trick (as posted in https://forum.xda-developers.com/lg-g3/general/request-3g-2g-lte-d850-t3300908) or is there an easier way?
I did a search to try and find an answer but couldn't find anything, so apologies if it has already been asked/answered..
Alrighty, so I got my shiny new Nexus 7 Flo for Christmas, and rooted it straight away. Everything seems to be fine, but just realised i hadn't done a nandroid backup yet. Once the backup was finished, I rebooted so I could move the backup to my laptop to free up ~4gb from my Nexus, but the backup location is different from the normal /sdcard/ClockworkMod/Backup, and I finally found it (using a root file manager) in data/media/clockworkmod/backup.
SO, my question is this..
Since it is apparent that Nexus 7 doesn't support USB Mass Storage Mode, I cannot access said nandroid backup without using a root file manager to move it to my MTP-accessible /sdcard folder, then moving to my laptop. That being the case, if something funky were to happen to my tablet and require me to restore the nandroid backup, how would I be able to put the nandroid backup back onto my tablet, since it would require the root file manager to move (which I obviously wouldn't be able to use if I'm in a bootloop for example).
As i was typing this I thought that mounting USB storage in recovery might do the trick, but nothing appears in My Computer when I select mount USB storage in CWM..
Any ideas/suggestions would be greatly appreciated, thanks
-Nexus 7 2013, stock 4.4.2/stock kernel, CWM Touch Recovery 6.0.4.3
DrRuckingFetard said:
I did a search to try and find an answer but couldn't find anything, so apologies if it has already been asked/answered..
Alrighty, so I got my shiny new Nexus 7 Flo for Christmas, and rooted it straight away. Everything seems to be fine, but just realised i hadn't done a nandroid backup yet. Once the backup was finished, I rebooted so I could move the backup to my laptop to free up ~4gb from my Nexus, but the backup location is different from the normal /sdcard/ClockworkMod/Backup, and I finally found it (using a root file manager) in data/media/clockworkmod/backup.
SO, my question is this..
Since it is apparent that Nexus 7 doesn't support USB Mass Storage Mode, I cannot access said nandroid backup without using a root file manager to move it to my MTP-accessible /sdcard folder, then moving to my laptop. That being the case, if something funky were to happen to my tablet and require me to restore the nandroid backup, how would I be able to put the nandroid backup back onto my tablet, since it would require the root file manager to move (which I obviously wouldn't be able to use if I'm in a bootloop for example).
As i was typing this I thought that mounting USB storage in recovery might do the trick, but nothing appears in My Computer when I select mount USB storage in CWM..
Any ideas/suggestions would be greatly appreciated, thanks
-Nexus 7 2013, stock 4.4.2/stock kernel, CWM Touch Recovery 6.0.4.3
Click to expand...
Click to collapse
if you have adb set up correctly and the path variable set - just navigate to where you want to save your Nandroid and type:
Code:
adb pull /data/media/clockworkmod/backup/
To put it back on your device you can use adb push for single files or the entire directory contents to wherever you want to put the files on your device.
Code:
adb push /path/to/saved/file_or_directory /target_dir_on_device
Then restore using cwm or twrp as needed.
Alternatively you could also use fastboot to flash your recovery images.
hope this helps,
Cheers!
Ahh i didn't even think of using adb pull to work around this, thanks heaps!
Any ideas as to why I can't mount usb storage within recovery?
Sent from my Nexus 7 using XDA Premium HD app
DrRuckingFetard said:
I did a search to try and find an answer but couldn't find anything, so apologies if it has already been asked/answered..
Alrighty, so I got my shiny new Nexus 7 Flo for Christmas, and rooted it straight away. Everything seems to be fine, but just realised i hadn't done a nandroid backup yet. Once the backup was finished, I rebooted so I could move the backup to my laptop to free up ~4gb from my Nexus, but the backup location is different from the normal /sdcard/ClockworkMod/Backup, and I finally found it (using a root file manager) in data/media/clockworkmod/backup.
SO, my question is this..
Since it is apparent that Nexus 7 doesn't support USB Mass Storage Mode, I cannot access said nandroid backup without using a root file manager to move it to my MTP-accessible /sdcard folder, then moving to my laptop. That being the case, if something funky were to happen to my tablet and require me to restore the nandroid backup, how would I be able to put the nandroid backup back onto my tablet, since it would require the root file manager to move (which I obviously wouldn't be able to use if I'm in a bootloop for example).
As i was typing this I thought that mounting USB storage in recovery might do the trick, but nothing appears in My Computer when I select mount USB storage in CWM..
Any ideas/suggestions would be greatly appreciated, thanks
-Nexus 7 2013, stock 4.4.2/stock kernel, CWM Touch Recovery 6.0.4.3
Click to expand...
Click to collapse
USB is not native on the Nexus 7 Flo so USB only works with an stick mount type app. I don't know if any will do this without root but you can't mount USB in recovery regardless. As to how to get a nandroid to your tablet, adb is your friend. 4GB is a an unusually huge nandroid. I always recommend keeping a nandroid or at least a ROM zip on you internal memory to flash. It save some hassles.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
USB is not native on the Nexus 7 Flo so USB only works with an stick mount type app. I don't know if any will do this without root but you can't mount USB in recovery regardless. As to how to get a nandroid to your tablet, adb is your friend. 4GB is a an unusually huge nandroid. I always recommend keeping a nandroid or at least a ROM zip on you internal memory to flash. It save some hassles.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not referring to mounting a USB stick to the tablet, I already use stickmount for that. I'm talking about mounting the Nexus to the computer so files can be moved to it while in recovery.
As for the nandroid file size, it's 4gb because of my apps/app data backed up within it.. If there is a way to nandroid backup without also backing up /data folder I'd love to know how (but I'll also feel like an idiot because I've been trying to work out how to do that for a while lol..)
Sent from my Nexus 7 using XDA Premium HD app
If you are using Obackup ( Online Nandroid Backup ) you can select your partitions if you do a custom backup. You could also do it the hard way using the Linux dd command for the partitions you want in your backup
Sent from my Nexus 7 using XDA Premium HD app
oldsoldier2003 said:
If you are using Obackup ( Online Nandroid Backup ) you can select your partitions if you do a custom backup. You could also do it the hard way using the Linux dd command for the partitions you want in your backup
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That sounds like a great idea, but with an upload speed of 30kb/s to dropbox with my internet connection, I wouldn't even bother trying to upload a file this size lol...
Any other way to perform a nandroid backup without the /data folder included?
Okay so I actually just noticed the first line of the XDA post about it (whoops)-
:good:Make a backup, zip it and upload it on your Dropbox or Google Drive in ONE CLICK only !!! (upload is just a feature, you can make the backup and just keep it on your device)
Click to expand...
Click to collapse
I'll give that a go then since it will let me select partitions to backup, thank you!
Okay so I got the app, tried looking through the XDA thread for it to find an answer but it didn't really explain many of the options so here's my next n00b question(s)-
1. Backup type: use "CWM Full" or "CWM Incremental"? What's the difference?
2. Being that the CWM Recovery nandroid location is /data/media/clockworkmod/backup, should I set OBackup to save to this location or leave it at the default /mnt/sdcard, and if I do, will it still be recognised within recovery to restore said backup?
DrRuckingFetard said:
Okay so I got the app, tried looking through the XDA thread for it to find an answer but it didn't really explain many of the options so here's my next n00b question(s)-
1. Backup type: use "CWM Full" or "CWM Incremental"? What's the difference?
2. Being that the CWM Recovery nandroid location is /data/media/clockworkmod/backup, should I set OBackup to save to this location or leave it at the default /mnt/sdcard, and if I do, will it still be recognised within recovery to restore said backup?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
It appears I don't have permissions to upload an attachment...
https://plus.google.com/u/0/101829893094741883826/posts/SUMLDu313EG
The example here is for a backup without the data partition.
You can save the nandoid to the /sdcard/ directory - because I use TWRP mine go to /sdcard/TWRP/BACKUPS/<device serial number>
For CWM I am not sure of the option but it would be custom if you only want certain partitions.
regardless as long as you know where it is you can restore it. If you use nandroid manager it will scan and find your backup paths for you and restore them, or again you can just point your recovery to them.
oldsoldier2003 said:
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
It appears I don't have permissions to upload an attachment...
https://plus.google.com/u/0/101829893094741883826/posts/SUMLDu313EG
you can save the nandoid to the /sdcard/ directory becuae I use TWRP mine go to /sdcard/TWRP/BACKUPS/<device serial number>
Click to expand...
Click to collapse
If i selected /data/media as the backup directory, would that make the backup visible within recovery now wouldn't it? Tried using Obackup and backed up to /mnt/sdcard/clockworkmod but recovery didn't see any backups on the device..
Sent from my Nexus 7 using XDA Premium HD app
oh and I never bother trying to save uncompressed backups to drop box they take forever. I usually just adb pull them to my desktop then stash an archival copy on dvd . zipping and uploading to drive/box/dropbox are also good options but as you said they take a very long time. It is just easier for me to maintain multiple copies on different computers and media in the house...
---------- Post added at 01:55 AM ---------- Previous post was at 01:52 AM ----------
DrRuckingFetard said:
If i selected /data/media as the backup directory, would that make the backup visible within recovery now wouldn't it? Tried using Obackup and backed up to /mnt/sdcard/clockworkmod but recovery didn't see any backups on the device..
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think that cwm looks for the backup in a oddball location. Cant remember exactly where off the top of my head. Its late and I'm tired. Nandroid manager should be able to find it though.
oldsoldier2003 said:
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
For CWM I am not sure of the option but it would be custom if you only want certain partitions.
regardless as long as you know where it is you can restore it. If you use nandroid manager it will scan and find your backup paths for you and restore them, or again you can just point your recovery to them.
Click to expand...
Click to collapse
There's no option within CWM to select which partitions to backup, or to select backup/restore locations, but it has the advanced options to restore selected partitions, which doesn't really help for now..
I'm more concerned if I get into a bootloop, and my recovery can't find my nandroid backups to restore to..
Yeah I understand your concern. If I am not mistaken the reason you cant see the backup is because it is in protected storage. I think cwm does this by design now... Have you tired booting into recovery and looking for it in cwm?Once you figure out where cwm saves it you can tell online nandroid to save it there, or you could just boot to recovery and do your nandroid directly from cwm. Personally I prefer to do it "online" so I don't have to reboot...
I really cant be of much more assistance directly becuase I don't have CWM on the device right now, but It looks to me like you pretty much have it licked. I'll check back after I get some sleep and If you are still having issues I'll flash cwm and see if I can be of any further assistance.
oldsoldier2003 said:
Yeah I understand your concern. If I am not mistaken the reason you cant see the backup is because it is in protected storage. I think cwm does this by design now... Have you tired booting into recovery and looking for it in cwm?Once you figure out where cwm saves it you can tell online nandroid to save it there, or you could just boot to recovery and do your nandroid directly from cwm. Personally I prefer to do it "online" so I don't have to reboot...
I really cant be of much more assistance directly becuase I don't have CWM on the device right now, but It looks to me like you pretty much have it licked. I'll check back after I get some sleep and If you are still having issues I'll flash cwm and see if I can be of any further assistance.
Click to expand...
Click to collapse
Okay so I just did a custom nandroid within the app you linked me to, and set it to save in /data/media and booted into recovery, and CWM now sees the backup :good:
That's pretty much my problems solved now, seems i'll have to use adb as you mentioned to pull the backup from my device to store on my laptop/portable HDD, and then push it back if needed, thanks very much for your help!
You're very welcome. I'm glad you have it all sorted out
Sent from my Nexus 7 using XDA Premium HD app
I am stuck in a confusing situation I cant get out of and am in serious trouble.
My work Galaxy Tab Pro 8.4 LTE (T325), after more than 2 years of perfect service fell to the ground and broke in a million pieces this morning. I had CM11 on it and had done a TWRP backup just yesterday onto the external MiniSD Card. So, I went to a second hand shop phone shop in the afternoon and found another T325 just like mine in good shape with stock 4.4.2 Samsung TouchWiz ROM.. just white instead of white, but no matter. I immediately rooted it and flashed TWRP.. all good.
I booted into TWRP and first thing I did was to make a backup of the stock ROM to the internal SD Card and also the external MiniSD Card (just to be safe). But after I made the safety backup, when I went into restore, TWRP CANT find it the old backup of my other Tab on the external MiniSD Card. It can only see the new backup I had just made, both on the internal and external memory!
Confused, I booted up the Tab again, and using Root Explorer (with full root access) the first strange thing I noticed was that inside the TWRP folder on the root directory of the internal SD card, its "empty".. but the new backup I just made is actually there.. if I go to the root folders under MNT, there I can see perfectly the very same TWRP folder with the backup sub-folder inside! So why its not showing up when browsing \Emulated\0 TWRP folder? I dont understand this one. Anyway, next I went into my external MiniSD Card, and indeed I have now 2 backups inside the TWRP folder, the old backup from my old Tab that I want to restore and the new backup I had just made, each in their own sub-folder structure as they should be.
So, I rebooted into TWRP recovery and again and I can ONLY see both the new internal and external backups I just made, but NOT the old backup I need to recover from.. it just doesn't show up! Such a mystery has never happened to me before. This is the same Tab, same model, same old TWRP version (2.7.1.0) and using the original external MiniSD Card. Where am I going wrong? I can see the file names inside the new and old backup are different.. is this the problem? Why is the same TWRP version on a new Tab generating different file names than the same TWRP of the old Tab?
To be specific, the new (recoverable) backup folder has the following files:
\TWRP\10d401a5\2014-02-05--07-03-30 KOT49H.T325ZSU1B0B4\
boot.emmc.win
data.ext4.win
system.ext4.win000
system.ext4.win001
recovery.log
The old (not-recoverable) backup folder that I want to restore from, has the following files:
\TWRP\d59ee67a\2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00\
boot.emmc.win
data.ext4.win000
data.ext4.win001
system.ext4.win
recovery.log
Any advice on this is greatly appreciated and I apologize in advance if its me missing something obvious or just being plain stupid!
Thanks again!!!
I suspect the d59ee67a \ 10d401a5 are generated from the tablet serial number, so twrp will only look in the folder for the current serial number match, which is why it won't show the other backup.
I would assume you could copy the file contents from your old backup into the new twrp folder then restore, as long as you are sure the tablets are identical, have the same bootloader and same memory sizes...etc
so basically try to copy the folder "2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00" to TWRP\10d401a5\
otyg said:
I suspect the d59ee67a \ 10d401a5 are generated from the tablet serial number, so twrp will only look in the folder for the current serial number match, which is why it won't show the other backup.
I would assume you could copy the file contents from your old backup into the new twrp folder then restore, as long as you are sure the tablets are identical, have the same bootloader and same memory sizes...etc
so basically try to copy the folder "2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00" to TWRP\10d401a5\
Click to expand...
Click to collapse
Wow, yes, thank you very much for the reply! I had no idea that each hardware generates a specific number by which TWRP tags the folder. This is why the backup of the old Tab is not found because its inside the folder with the number of the older hardware. I followed your recommendation and simply moved the old backup into the subfolder of the new backup I had made and instantly TWRP could see it and I made a successful restore!
This is a very import tip to know and I cant thank you enough for sharing it with me! Thanks again