Related
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?
Hi all, I'm a new I9195GT owner (for a week already) and have been researching and having some satisfaction rooting and restoring all my apps with Titanium from my previous smartphone.
The phone works fine and I'm quite happy with it. I've already done a full backup with CWM recovery for any trouble I might come across in future but I don't know if a full backup from recovery contains all important and sensible data like EFS and NV data. Those two things are totally new for me as I'm coming from a HTC Desire which didn't require attention to those sensible points.
So I would be very grateful if anybody clears some doubts I have relating EFS and NV data:
- Does a full backup from recovery contain EFS and NV data, so in case that flashing a custom ROM results in corrupted EFS data, I would fix it just by restoring the full backup from recovery?
- What is the best and safest way for backup EFS and NV?
I've seen this post from arco68 which states a command I guess should be executed from Terminal directly in the smartphone, but I don't know how should that .img file restored to the phone in case it becomes corrupted.
I've also seen this post about the EFS Professional tool from lyriquidperfection but in the whole post I havent found anybody confirming it works in the S4 Mini i9195.... so it sounds good but I don't want to brick my new device being the first one to run the tool with the i9195
Thank you very much
As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107
Thanks for the idea. I'm ready to install TWRP recovery but, before installing it and replacing CWM,
Is it possible to launch TWRP recovery from CWM recovery, as temporary? And when rebooting CWM is back.
I remember doing something like this in my previous device: from 4EXT recovery launching a CWM recovery for some particular reason I don't remember
Sent from my GT-I9195 using xda app-developers app
batareikin51 said:
As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107
Click to expand...
Click to collapse
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it. This concerns specifically I9195, which I own too and am researching this issue and also lost IMEI issue.
farewellartist said:
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it.
Click to expand...
Click to collapse
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Good question, I've been looking for answer for weeks.
sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?
radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
sergiosch said:
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?
Click to expand...
Click to collapse
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.
farewellartist said:
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.
Click to expand...
Click to collapse
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....
sergiosch said:
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....
Click to expand...
Click to collapse
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.
farewellartist said:
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.
Click to expand...
Click to collapse
Great news! looking forward to read that guide :good::good:
sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".
deliog said:
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".
Click to expand...
Click to collapse
Don't mount, just backup.
Through terminal emulator, enter commands
su
dd if=/dev/block/mmcblk0p11 of=/dev/block/mmcblk0p12
And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app
sergiosch said:
And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
See this: http://forum.xda-developers.com/showthread.php?t=2569532
sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.
farewellartist said:
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.
Click to expand...
Click to collapse
I haven't done yet any of the backup processes you explain, so I don't even have the files you're asking for, but with all the gratitude and admiration I feel for the developers I wouldn't feel any confortable sending sensible data from part of a nandroid backup.... speaking just for myself of course, if I could choose how to help a developer I would preferr doing a donation to help him recover the hardware he has broken to help others. Some months ago I heard a friend telling that he had been scammed with a phone he bought in some cash converter and only worked for one day, then it became with null IMEI, and he suspected someone had "stolen" or "shutdown" his IMEI for unknown reasons...
sorry to say that, maybe I'm an ignorant but I just don't feel confortable with what you are asking directly to me
My HTC ONE M8 battery died and all SMS messages disappeared.
I badly need them back.
So my idea was:
1. to have a block by block backup of /data partition to a Linux or Windows box.
2. use some standard tools trying to find missing or corrupted or deleted files there. Find the one which has the messages.
3. extract the messages using something like mmssmsxml.py in the SMS Backup/Restore format and bring it back to the phone.
Unfortunately at this point I am still at #1 since this requires Rooting the device and rooting according to all posts is going to delete all data. So my questions are:
1) Can I do a "partial rooting" to just unlock /data partition?
This would give me opportunity to dd all data from the partition.
2) are there any other methods? Maybe the standard Unix/Linux way of booting a limited OS image (consisting of: boot, mount, parted, dd ...) so I could boot from SD and run the dd command and copy /data partition to the SD card and then bring it to the Linux computer.
Please help.
No way to do this that I know of, unless you happen to already by s-off: http://forum.xda-developers.com/htc-one-m8/help/root-losing-data-s-off-t3457817
redpoint73 said:
No way to do this that I know of, unless you happen to already by s-off: http://forum.xda-developers.com/htc-one-m8/help/root-losing-data-s-off-t3457817
Click to expand...
Click to collapse
So, is there a way to S-off the phone without wiping it out?
You can use ADB to make a backup without root.
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab to backup everything. Replace "NAME" with your Windows username.
adb restore C:\Users\NAME\backup.ab to restore the backup, replacing "NAME" again, of course.
You can read more about it in this thread.
I have not used the adb backup but I was told, that it backs up only files. The new mmssms.db exists in the file system and currently has no messages. I need to have the full image of the partition in order to search all block marked "empty" which could potentially be blocks of the damaged (and disappeared) mmssms.db file in order to re-construct the file and get all sms messages from it. The new mmssms.db exists in the file system and currently has no messages.
Please correct me if I am wrong and I will be able to search the adb backup for missing blocks.
Regards.
Vladimir
rubashev said:
I have not used the adb backup but I was told, that it backs up only files. The new mmssms.db exists in the file system and currently has no messages. I need to have the full image of the partition in order to search all block marked "empty" which could potentially be blocks of the damaged (and disappeared) mmssms.db file in order to re-construct the file and get all sms messages from it. The new mmssms.db exists in the file system and currently has no messages.
Please correct me if I am wrong and I will be able to search the adb backup for missing blocks.
Regards.
Vladimir
Click to expand...
Click to collapse
I really don't know. I've never had a problem like this myself, but I thought I would suggest it as it's the only way to backup without a custom recovery that I know of. To flash a custom recovery you need to unlock your bootloader first, and that will wipe your phone.
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
Following a recent custom ROM flash, my N5120 had 3 faults:
1. No phone function (No IMEI, No SIM, No Network, No Baseband......nothing)
2. No Bluetooth
3. It rebooted itself after about 20 minutes (unless it was exercised eg running a timer/countdown app)
I tried many, many suggestions from this forum and elsewhere. I tried 3 local phone fixing shops (mostly "No fix, No fee"). All to no avail. I had just about resigned myself to selling it as faulty on EBay. Last night I thought I would have one last try. Clearly the main problem was to do with the EFS. And I had previously taken a FULL backup.
Step 1:
Flash back to an early stock ROM (eg 4.4.2 N5120XXSDQA2 in my case)
Step 2:
Assemble the following (backup) files and transfer them to your tablet....
efs_backup.img [This will be restored into partition mmcblk0p3 .....see below]
radio_backup.img [Ditto partition mmcblk0p13]
radio-cdma_backup.img [Ditto partition mmcblk0p12]
m9kefs1_backup.img [Ditto partition mmcblk0p4]
m9kefs2_backup.img [Ditto partition mmcblk0p5]
m9kefs3_backup.img [Ditto partition mmcblk0p6]
....you may not really need all of these but I had them as a set.
Step 3:
On your tablet, go to Google Play Store and get/install/run "Partitions Backup" by Wanam (Thank you Wanam!!!!).
Step 4:
Using Partitions Backup, click on the box left of EFS (on my system this line was highlighted in yellow).
Press the 3 dots (top right) and select, "Restore a partition" and choose the default method and the correct partition location
After "Success" is indicated, repeat this process for each of the other files making sure you select the correct partition location
Step 5:
Reboot
...and smile
This method worked for me. I hope it might help someone else who loses their phone function.
I have copied the files I (or you) might need here:
https://drive.google.com/file/d/1Z93DZnLrBXwZuPBb91M0bLE7aBXoWa2V/view?usp=sharing
GaryTG said:
Following a recent custom ROM flash, my N5120 had 3 faults:
1. No phone function (No IMEI, No SIM, No Network, No Baseband......nothing)
2. No Bluetooth
3. It rebooted itself after about 20 minutes (unless it was exercised eg running a timer/countdown app)
I tried many, many suggestions from this forum and elsewhere. I tried 3 local phone fixing shops (mostly "No fix, No fee"). All to no avail. I had just about resigned myself to selling it as faulty on EBay. Last night I thought I would have one last try. Clearly the main problem was to do with the EFS. And I had previously taken a FULL backup.
Step 1:
Flash back to an early stock ROM (eg 4.4.2 N5120XXSDQA2 in my case)
Step 2:
Assemble the following (backup) files and transfer them to your tablet....
efs_backup.img [This will be restored into partition mmcblk0p3 .....see below]
radio_backup.img [Ditto partition mmcblk0p13]
radio-cdma_backup.img [Ditto partition mmcblk0p12]
m9kefs1_backup.img [Ditto partition mmcblk0p4]
m9kefs2_backup.img [Ditto partition mmcblk0p5]
m9kefs3_backup.img [Ditto partition mmcblk0p6]
....you may not really need all of these but I had them as a set.
Step 3:
On your tablet, go to Google Play Store and get/install/run "Partitions Backup" by Wanam (Thank you Wanam!!!!).
Step 4:
Using Partitions Backup, click on the box left of EFS (on my system this line was highlighted in yellow).
Press the 3 dots (top right) and select, "Restore a partition" and choose the default method and the correct partition location
After "Success" is indicated, repeat this process for each of the other files making sure you select the correct partition location
Step 5:
Reboot
...and smile
This method worked for me. I hope it might help someone else who loses their phone function.
I have copied the files I (or you) might need here:
https://drive.google.com/file/d/1Z93DZnLrBXwZuPBb91M0bLE7aBXoWa2V/view?usp=sharing
Click to expand...
Click to collapse
Hello,
I have your problem.
I did, before losting imei,a backup with "Partitions Backup" by Wanam.I tried to restore my imei but the app seems not working.
If I use your file will my imei change?
Thanks if you want to help me
I will try to help if I can.... A few questions spring to mind:
1. Have you flashed an early stock ROM? [Step 1]
2. Were your 6 backup files in the .img format?
3. When you say the app is not working, do you mean not showing "success" after each individual img file is restored or is there something else that indicates "not working"?
4. Are you restoring the correct img file to the correct partition (as listed above)?
5. Do all of your backup files fail to restore individually?
Regarding changing the IMEI (using my files), the truth is that I don't know. I suspect that my backup files will only work for EXACTLY the same model as mine (N5120) and that it WON'T change your IMEI. I think the IMEI is "hard coded" in your phone and can't be easily changed. If it were easy, there would be a HUGE market in stolen phones!
But before you try my files, I would persevere with your own backups individually. You should be able to use your own backups. If you are desperate, you could try restoring just one of my m9kef files. When you can successfully restore one file, we/you might think about restoring the rest.
Hope that is of some help.
Regards
GaryTG said:
I will try to help if I can.... A few questions spring to mind:
1. Have you flashed an early stock ROM? [Step 1]
2. Were your 6 backup files in the .img format?
3. When you say the app is not working, do you mean not showing "success" after each individual img file is restored or is there something else that indicates "not working"?
4. Are you restoring the correct img file to the correct partition (as listed above)?
5. Do all of your backup files fail to restore individually?
Regarding changing the IMEI (using my files), the truth is that I don't know. I suspect that my backup files will only work for EXACTLY the same model as mine (N5120) and that it WON'T change your IMEI. I think the IMEI is "hard coded" in your phone and can't be easily changed. If it were easy, there would be a HUGE market in stolen phones!
But before you try my files, I would persevere with your own backups individually. You should be able to use your own backups. If you are desperate, you could try restoring just one of my m9kef files. When you can successfully restore one file, we/you might think about restoring the rest.
Hope that is of some help.
Regards
Click to expand...
Click to collapse
My tablet is a N5120
1)Yes
2)yes
3)it show "success" but no imei appears when i dial *#06#
4)yes
5) all backup files are restored successfully
If you extract "efs_backup.img" you can see a folder named "factoryapp".In this folder there is a file called " serial_no. if you open with notepad you can read your own serial number which is different form mine.
So, if I flash your file my serial number will change
I did a backup file with wanam app before losing imei.The app says "success" but no imei is displayed.
Never mind.Everything works.I can call or send sms.It's just strange that my imei is not displayed.
Thanks for your support
Giowi said:
My tablet is a N5120
1)Yes
2)yes
3)it show "success" but no imei appears when i dial *#06#
4)yes
5) all backup files are restored successfully
If you extract "efs_backup.img" you can see a folder named "factoryapp".In this folder there is a file called " serial_no. if you open with notepad you can read your own serial number which is different form mine.
So, if I flash your file my serial number will change
I did a backup file with wanam app before losing imei.The app says "success" but no imei is displayed.
Never mind.Everything works.I can call or send sms.It's just strange that my imei is not displayed.
Thanks for your support
Click to expand...
Click to collapse
OK.
I'm glad you can call and send SMS. Like you, I am puzzled by the missing IMEI. Hopefully someone more knowledgeable might be able to help you with the missing IMEI. One thought would be to reboot (but I'm pretty sure you would have tried that after the restores). The IMEI must be there and valid or I don't think you would be able to make calls......
I note what you say about the serial number.
Good Luck
you saved my life!!! fortunately i had my own files of backup but i didn't kwow how i can restore it. thanks thanks
GaryTG said:
Following a recent custom ROM flash, my N5120 had 3 faults:
1. No phone function (No IMEI, No SIM, No Network, No Baseband......nothing)
2. No Bluetooth
3. It rebooted itself after about 20 minutes (unless it was exercised eg running a timer/countdown app)
I tried many, many suggestions from this forum and elsewhere. I tried 3 local phone fixing shops (mostly "No fix, No fee"). All to no avail. I had just about resigned myself to selling it as faulty on EBay. Last night I thought I would have one last try. Clearly the main problem was to do with the EFS. And I had previously taken a FULL backup.
Step 1:
Flash back to an early stock ROM (eg 4.4.2 N5120XXSDQA2 in my case)
Step 2:
Assemble the following (backup) files and transfer them to your tablet....
efs_backup.img [This will be restored into partition mmcblk0p3 .....see below]
radio_backup.img [Ditto partition mmcblk0p13]
radio-cdma_backup.img [Ditto partition mmcblk0p12]
m9kefs1_backup.img [Ditto partition mmcblk0p4]
m9kefs2_backup.img [Ditto partition mmcblk0p5]
m9kefs3_backup.img [Ditto partition mmcblk0p6]
....you may not really need all of these but I had them as a set.
Step 3:
On your tablet, go to Google Play Store and get/install/run "Partitions Backup" by Wanam (Thank you Wanam!!!!).
Step 4:
Using Partitions Backup, click on the box left of EFS (on my system this line was highlighted in yellow).
Press the 3 dots (top right) and select, "Restore a partition" and choose the default method and the correct partition location
After "Success" is indicated, repeat this process for each of the other files making sure you select the correct partition location
Step 5:
Reboot
...and smile
This method worked for me. I hope it might help someone else who loses their phone function.
I have copied the files I (or you) might need here:
https://drive.google.com/file/d/1Z93DZnLrBXwZuPBb91M0bLE7aBXoWa2V/view?usp=sharing
Click to expand...
Click to collapse
!! Warning, file efs backup.img-mmcblk0p3 contains Trojan:Script/Wacatac.B!ml malware...
MOD Edit: https://www.virustotal.com/gui/file...cb2e7801e93c61abf823a6773769bb10466?nocache=1 for the file from OP. Most likely false alarm.