A complete IMEI Backup and Restore solution for Samsung devices.
This app should work with almost ALL Samsung devices.
Prerequisite: SAMSUNG device + ROOT permission.
Make sure you own a SAMSUNG device and your device has been ROOTED before purchase.
DESCRIPTION:
This app will make a full backup for the EFS partition and all other IMEI-related partitions, e.g. MODEMST, MODEMST1, MODEMST2, M9KEFS, M9KEFS1, M9KEFS2, M9KEFS3... (these partitions will vary from device to device)
It will perform cross-checks to make sure a good backup was made and ensure the backup is suitable for your device before restoring.
DURING BACKING UP PROCESS:
- Auto detect which partitions to back up
- Check if all needed partitions have been backed up
- Check if all partitions are backed up correctly by comparing the file size to the partition size
- Generate and save MD5 checksum for backup files
- Save all the system properties for restoring purpose, e.g. phone model, product name, OS version, partition structure, partition size...
DURING RESTORING PROCESS:
- Compare saved properties with the current system properties: phone model, product name, OS version...
- Compare partition structure and partition size to ensure that the backup is suitable for your device
- Compare the MD5 checksum for the backup files
The good item will be marked with [✔] and the bad/mismatched item will be marked with [✘].
DOWNLOAD LINK on Play Store: https://play.google.com/store/apps/details?id=org.vndnguyen.imeibackup
NOTE: If you are using Android 4.4 (KitKat) and you cannot backup to the External SD card, you can use SDFix app to fix.
{
"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"
}
HOW TO BACK UP:
• From the main screen, tap Backup button to make a backup.
• You will be asked for backup location, if more than one storage location on your device.
• You can enter a short description for the backup.
• The app will automatically detect all partitions need to back up.
• After backup it will compare the file size and generate the MD5 checksum.
• It also save important system properties.
• The backup files will be saved in the folder in the following format: IMEI_Backup_yyMMddHHmmss
HOW TO RESTORE:
• Select the desired backup in the list.
• It will show you all information: Details, Properties, Backup Files and Status.
• Details: Backup location, size, date created and description.
• Properties: Manufacturer, Model, Product name, OS version, partition structure and partition size.
• Backup Files: shows all backup files and their status. It will show the file size if the file is in good condition. Otherwise it will show 'file not found' or 'bad checksum' etc.
• Status: Overall status of the backup. 'Unsuitable' means some properties do not match with the current device, but you still can use it to restore. 'Unusable' means you cannot restore this backup. This happens when the partition structure or partition size mismatched, file not found or bad MD5 checksum.
• Tap Restore button to restore. You must type 'Yes, Restore!' to confirm.
• Reboot your device after complete restoring.
WARNING: Only restore when you really need it. Do not play around with this tool. Use at your own risk.
Unlike other IMEI Backup apps that typically support only one specific model, this app supports almost ALL Samsung devices.
Tips: You can add the description to differentiate the backup from another.
Hi dev can this app restore my phone completely and remove my yellow triangle error that was caused by trying flash custom Rom let me know your thoughts thx.
Click to expand...
Click to collapse
Unfortunately I can not say for sure that this app can restore your phone completely, as I don't know what is your actual problem.
In the most cases, this app can restore your IMEI by backing up and restore the EFS and ALL IMEI-Related Partitions.
If you made a backup before flashing any ROM, you can restore your IMEI if any problem happens.
I just got the app, love it. But there is one thing that really bugs me. There is no way to change the default save location. It can go on either sdcard0 or sdcard1.
Each backup creates a separate folder on the sdcard. It would be nice if it could backup into a folder at say sdcard1/IMEI Backup. That way it is all consolidated to one folder location.
Click to expand...
Click to collapse
Thank you, this should be a nice suggestion.
I might add this capability in the future release.
Hello, first of all I want to thank you about this really great app, good job developers!
My question is if this app works with Samsung Galaxy S3 mini (GT-i8190/L/N), and if doesn’t work until now, will be possible to work in the future updates?
Many thanks!
Click to expand...
Click to collapse
Regarding Galaxy S3 mini, I didn't test on this phone, but I believe it should work with this phone.
From the user's feedback, I know that it works fine on S3 and S4 devices. And it should work with almost ALL Samsung devices, as I have stated in the app's description.
Best regards,
OK but... Tried the backup and restore. Worked perfectly. But then I needed to use it for real : the dreaded efs loss! And it didn't work. Why? License verification issue. It seems to me the app use some unique id data that resides, wait for it, in the efs partition! Kind of a catch 22. Good thing I also had a utility on my PC for efs backup.
Click to expand...
Click to collapse
Hello, sorry to hear about the problem.
Can you clarify some details:
- "OK but... Tried the backup and restore. Worked perfectly": that means it worked before? for both backup and restore?
- "License verification issue.... Kind of a catch 22": did you face with "license check error"? If so, try to uninstall and then reinstall the app from the Play Store. Or another error?
On Android 4.4.2 there is a problem with writable ability on the External SDcard.
To avoid the problem, please select sdcard as a backup location, do not select ExtSdCard. Sorry about that, I will find a way to fix it.
Update v1.2.9:
Add support for all Note 4 variants: SM-N910A, SM-N910C, SM-N910F, SM-N910FD, SM-N910FQ, SM-N910G, SM-N910H, SM-N910K, SM-N910L, SM-N910P, SM-N910R, SM-N910S, SM-N910T, SM-N910U, SM-N910V, SM-N910W8...
If you are using Android 4.4 (KitKat) and you cannot backup to the External SD card, you can use SDFix app to fix.
Hi,
If I made a backup file from my official note 4 firmware, Is the knox counter go up when I restore ?
Click to expand...
Click to collapse
Hi,
Good question. I have not faced with this question before, but I try to answer.
AFAIK, Knox counter only trip if you root the phone, or if a custom recovery or custom kernel are being installed.
Flashing the backup EFS partitions will not trip the Knox counter.
Hope that answers your question.
Made me feel safer . totally worth a shot
Glad you find it useful.
Please note that on newer Samsung devices, the IMEI is not stored in the EFS partition.
This app mades a backup for not only EFS partition but all other IMEI-related partitions.
If you backup only EFS, your IMEI will not be restored later.
<deleted>
I have Samsung Galaxy J (SC-02F) Japan.
Your application work with my device ?
Thank you!
duc2ht said:
I have Samsung Galaxy J (SC-02F) Japan.
Your application work with my device ?
Click to expand...
Click to collapse
Yes, it will work with ALL Samsung devices.
(except for some older models).
<deleted due to duplicated>
Related
{
"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"
}
I've put together an unofficial ClockworkMod Recovery 6.0.1.1 until Koush adds to ROM Manager, tested working for all features except SD card mount. Working on the latter at the moment.
UPDATE: This recovery does work for both GT-N8000 (3g version) and GT-N8013 (wifi version), just confirmed. (8/16/2012)
Notes:
v1 - Touchscreen is a bit if when you have to scroll, please use the volume buttons for scrolling otherwise you may get accidental presses.
Changelog:
v1 - Everything working except SD card mount. You can backup/restore/ROM to internal or external SD card and other CWM features functional.
Flash this in ODIN or Heimdall:
Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1
Also, here's stock recovery you can flash in ODIN or Heimdall to revert (and get OTA updates):
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Credits:
Of course to Koush! I used his builder then hacked graphics.c + other files to make it work.
reserved
reserved
Amazing! Can't wait to get my hands on my Note
Sent from my SCH-I535
Way to go buddy!
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
cdesai said:
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
Click to expand...
Click to collapse
I did initially but had to hack it to make it work.
zedomax said:
I did initially but had to hack it to make it work.
Click to expand...
Click to collapse
Hey Zedo! Check your PM !
I noticed it does not actually backup system.img on my device, nor did any of my attempts from the clockworkmod builder site either. It says it, but skips over in reality. This will be important to fix if indeed it is not backing it up...
EDIT: Nevermind... I guess the system.img was hiding from me
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
akxak said:
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
Click to expand...
Click to collapse
It's in your clockworkmod/backup directory. Now, with the new CWM, it stores backups as pieces of files under clockworkmod/blobs directory. This saves a ton of time when doing multiple backups as "blobs" store bits of your filesystem so when doing similar backups, it's not going to backup everything again.
Make sure you copy the whole clockworkmod folder to hard disk for moving though due to this new blobs feature. Your backup folder sizes might be much smaller because of this blobs thingee.
zedomax said:
I used his builder then hacked graphics.c
Click to expand...
Click to collapse
???
Please tutorial graphics.c ...Thanks by Notonlyeyes
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
gol-D said:
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
Click to expand...
Click to collapse
Did you do:
Code:
heimdall flash --recovery recovery.img
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Zedomax......greatstuff...root access on the N8010 no problem at all
....................................................................................................
Entropy512
Will try to do this now... But it'll be N8010.
Ive got the file for the N8010 on my desktop, but XDA isnt letting me upload the file keeps failing - any thoughts?
Dc
Sent from my GT-N8010 using Tapatalk 2
Entropy512 said:
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Click to expand...
Click to collapse
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
zedomax said:
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
Click to expand...
Click to collapse
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Entropy512 said:
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Click to expand...
Click to collapse
Well, I am just waiting for samfirmware to upload some official images, rather enjoy some of my note 10.1 first for awhile, it's pretty fascinating device, I've never used a tablet for a long time before getting this one, makes my life more productive. Yeah, what's up with Megaupload, that move by feds should have been illegal.
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
greenzkool said:
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
Flashing a recovery or kernel image in Odin will cause the binary counter to increase.
Flashing it using dd or Mobile Odin from a rooted system will not make it increase.
So the "safest" way to root is currently to flash that root-injected system image linked a few posts above, as it's fully unrootable and won't trigger the counter.
I have visitors most of this weekend so won't be able to do much work - once I get my kernel source tree properly set up I'm going to work on getting TriangleAway working on this device.
So, I've noticed after doing a factory data reset in TWRP (wipes data and caches), and installing Titanium Backup with the in app generated flashable zip; when I start TiB the first time I get a notice that my Android device ID has changed. TiB will offer me the choice to ignore this or restore the old ID. If I restore the ID, then restore system data, it breaks all sorts of things: Play Store, soft home button, quick settings buttons, wi-fi. If I ignore it no problems at all.
I guess the fix is just ignore device ID change.
Anyone else seeing this?
From which device & o/s version does the TB data come from?
It's normally recommended not to restore.system data only applications and associated data if from different Android versions
Sywepd form my DsereiS
ben_pyett said:
From which device & o/s version does the TB data come from?
It's normally recommended not to restore.system data only applications and associated data if from different Android versions
Sywepd form my DsereiS
Click to expand...
Click to collapse
From stock OTA Nexus 4 to Jellytime-AOSP+ built on 4.2
So, here, I made a TWRP backup of system and boot. Did a full wipe (factory data reset and /system) restored my backup, flashed TiB from the zip made in app, on the build I'd just backed up. Booted up, opened TiB, granted root rights, and this popped up.
{
"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"
}
I select restore and then it reboots. After I open TiB again and restore all system data, show below, and Wi-Fi Access Points is unseen. Reboot.
Now, when I try to download anything from the market I get this error. Did not bork soft buttons this time.
However, if I do all this again, and tell it to ignore the change, no issues.
USSENTERNCC1701E said:
So, here, I made a TWRP backup of system and boot. Did a full wipe (factory data reset and /system) restored my backup, flashed TiB from the zip made in app, on the build I'd just backed up. Booted up, opened TiB, granted root rights, and this popped up.
I select restore and then it reboots. After I open TiB again and restore all system data, show below, and Wi-Fi Access Points is unseen. Reboot.
Now, when I try to download anything from the market I get this error. Did not bork soft buttons this time.
However, if I do all this again, and tell it to ignore the change, no issues.
Click to expand...
Click to collapse
Do not touch system app, may be next time, it will screw your phone
nguyen47 said:
Do not touch system app, may be next time, it will screw your phone
Click to expand...
Click to collapse
As long as you are on the same device and the same build of android there are usually no issues from migrating system app data, I've been doing it for years.
I'm just trying to let people know, if you get this notice in TiB, select ignore to prevent errors.
If you restore from the same ROM all is working, tested myself yesterday. I just click on restore Id.
Sent from my GT-I9100 using Tapatalk 2
What if you wipe the app data for the play store?
Sent from my Nexus 7 using xda premium
So if I have no intention of restoring system app data, it's fine if I restored the ID?
But what other stuff will happen if I ignored? Would there be any potential problems elsewhere?
mlj11 said:
So if I have no intention of restoring system app data, it's fine if I restored the ID?
But what other stuff will happen if I ignored? Would there be any potential problems elsewhere?
Click to expand...
Click to collapse
nope. im always flashing new roms and use TiBu and yea i get that every time i start fresh. like what has been said, dont restore system data, just restore user data. and yea you can restore your ID from a previous rom without problems
Use this app:
http://forum.xda-developers.com/showthread.php?t=2109484
Sent from my Nexus 4 using xda app-developers app
USSENTERNCC1701E said:
As long as you are on the same device and the same build of android there are usually no issues from migrating system app data, I've been doing it for years.
I'm just trying to let people know, if you get this notice in TiB, select ignore to prevent errors.
Click to expand...
Click to collapse
BIG question here. I first install an app of a smart cover wich has a unique serial number i backed it up with titanium. after i change the rom wich is a ported rom of a different model i cannot get the data of the app do you have any idean on how to get it back?
I'm wondering if that was my problem
I did a factory reset and chose to reclaim my old ID nothing else now SVOX Victoria UK English won't load my data package
Unofficial release -TWRP recovery for the Galaxy A3 SM-A320F/FL/Y, Exynos7870
{
"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"
}
Update 11/9/2017
TWRP 3.1.1-1 MM build released.
Current status: BETA
Features:
MTP
ADB
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
TWRP Official APP support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-a320f_11917
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
Twrp Source : https://github.com/omnirom/android_bootable_recovery
Kernel source : http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-a320f
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Reserved.
If anyone has successfully installed this, I'd appreciate if they could post the recovery.log so I can look it over.
Log can be pulled in twrp under ADVANCED/SAVE RECOVERY LOG or on a rooted device go to cache/recovery/last_log
Thanks.
Blimey can no-one find the time to help out here?
I'd love to test this, but first I have to figure out why flashfire isn't working for me.
It only restarts after 20 seconds or so of white text and black background scrolling down, but no backups are written, only a log.
F157 said:
I'd love to test this, but first I have to figure out why flashfire isn't working for me.
It only restarts after 20 seconds or so of white text and black background scrolling down, but no backups are written, only a log.
Click to expand...
Click to collapse
It's already confirmed working I just need someone to post the recovery.log.
40 downloads since posting but no-one willing.
Hello, thank you very much, it worked for me. It was important so I can make a backup of the system. How can I post the recovery log? If you give me the procedure I'll do it.
patci32 said:
Hello, thank you very much, it worked for me. It was important so I can make a backup of the system. How can I post the recovery log? If you give me the procedure I'll do it.
Click to expand...
Click to collapse
Thanks, you're the only one to have made the effort!
You can save the recovery log from TWRP if you go to ADVANCED> SAVE RECOVERY LOG or you can boot to android and go to cache>recovery>last_log.
Please don't post the output here, post as a file or save the output on pastebin.com.
Thanks.
ashyx said:
Thanks, you're the only one to have made the effort!
You can save the recovery log from TWRP if you go to ADVANCED> SAVE RECOVERY LOG or you can boot to android and go to cache>recovery>last_log.
Please don't post the output here, post as a file or save the output on pastebin.com.
Thanks.
Click to expand...
Click to collapse
Here it is.
patci32 said:
Here it is.
Click to expand...
Click to collapse
Nothing there?
ashyx said:
Nothing there?
Click to expand...
Click to collapse
Yes sorry, it says network error when I try to attach the file!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
I can send it to you by email
patci32 said:
Yes sorry, it says network error when I try to attach the file!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
I can send it to you by email
Click to expand...
Click to collapse
You can post it here :
http://www.tinyupload.com/
ashyx said:
You can post it here :
http://www.tinyupload.com/
Click to expand...
Click to collapse
Here you go : http://s000.tinyupload.com/index.php?file_id=17704648158807479484
Thanks for your work. An information about my use : when I made a backup, I got a lot of errors like unable to mount the sd card and in the end "back up failed". But the 3 GB file has been created in the right folder, I think I got my backup.
patci32 said:
Here you go : http://s000.tinyupload.com/index.php?file_id=17704648158807479484
Thanks for your work. An information about my use : when I made a backup, I got a lot of errors like unable to mount the sd card and in the end "back up failed". But the 3 GB file has been created in the right folder, I think I got my backup.
Click to expand...
Click to collapse
No idea what's going on with tiny upload. Clicking the download link just downloads the html data of the web page not the actual file!
Thanks for trying any way.
By the way you can't back up data until you remove encryption.
ashyx said:
No idea what's going on with tiny upload. Clicking the download link just downloads the html data of the web page not the actual file!
Thanks for trying any way.
By the way you can't back up data until you remove encryption.
Click to expand...
Click to collapse
You mean I can't use the save file right now ? How do I remove encryption?
patci32 said:
You mean I can't use the save file right now ? How do I remove encryption?
Click to expand...
Click to collapse
See the OP.
ashyx said:
See the OP.
Click to expand...
Click to collapse
I dont get it I'm sorry. I got the save file, you're saying that I can't use it? I should be able to use the file with the restore section no ?
patci32 said:
I dont get it I'm sorry. I got the save file, you're saying that I can't use it? I should be able to use the file with the restore section no ?
Click to expand...
Click to collapse
If the data partition is encrypted then it wont have backed up. The rest of the partitions will have been backed up.
This is the failure you saw when backing up.
ashyx said:
If the data partition is encrypted then it wont have backed up. The rest of the partitions will have been backed up.
This is the failure you saw when backing up.
Click to expand...
Click to collapse
OK understood. Data partition is the sd card or the internal memory ? I assume that the encryption exists for security reasons. Is there anyway to backup everything without desactivating it?
patci32 said:
OK understood. Data partition is the sd card or the internal memory ? I assume that the encryption exists for security reasons. Is there anyway to backup everything without desactivating it?
Click to expand...
Click to collapse
It's internal memory.
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A810F/DS, Exynos 7420
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 17/4/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
How we got here: https://forum.xda-developers.com/sa...w-time-to-getting-support-a8-2016-sm-t3511148
Instructions:
Flash with ODIN 3.10.7.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-a810f_17417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, my testers(majinawaz, RootAgain)
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Awesome work dear if i able to buy a beer for you i must buy it
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
ivanox1972 said:
First, thanks boss @ashyx for great work. If you remember, I was first who asked yoi for twrp for this good phone. In meantime I bought it, and you make twrp. I tried it immediately and got this results :
Maybe it is important that I first done ota to newest offered AQA1 update.
Than odin flash twrp. All ok. Reboot to it and format data from wipe menu.
Hot error cant mount pcifs (maybe different name, I forgot, I can see again sorry).
Then flash supersu and patch and got same error, pcifs?
Root is working perfect but mount not. I back in twrp and see mount, it sees data. But tried some twrp install zip and got same error. And no app.
So obviously it is not mounted good...
Is there solution?
Thanks biggest
Click to expand...
Click to collapse
Post the recovery log file, so I can take a look.
How boss and which to do and to send result of it?
ivanox1972 said:
how boss and which to do and to send result of it?
Click to expand...
Click to collapse
twrp > advanced > save log
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
ivanox1972 said:
@ashyx boss strange thing, it seems it works with this error message? Look picture. I boot to twrp, data mounted, give classic backup job.
It did system and data and boot and on end message
Failed to mount cpefs.
Maybe actually it works, with this dummy message?
Click to expand...
Click to collapse
It's a protected partition so it can't mount. I should just remove it from the fstab.
You can just ignore it.
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
ivanox1972 said:
Thanks boss, so this is 100,% functional terp I can totally believe in backups and everything else?
Click to expand...
Click to collapse
I don't see why not, the main partitions are able to be backed up.
After phone user Super burn recovery and their code is the code?
I could not do it. Do you have a video? Mount data failed
Awesome work
@ashyx Hi buddy, adb doesnt seems to work in twrp
AL_IRAQI said:
@ashyx Hi buddy, adb doesnt seems to work in twrp
Click to expand...
Click to collapse
Disable MTP in TWRP.
ashyx said:
Disable MTP in TWRP.
Click to expand...
Click to collapse
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
AL_IRAQI said:
i already did that, it says device offline
BTW
did you think about pushing tree to official ?
Click to expand...
Click to collapse
I'd suggest installing the ADB drivers whilst in recovery mode.
Check device manager has detected it as an ADB device.
Hello ashyx adb is not working and shows adb device offline any solution please
[email protected] said:
Hello ashyx adb is not working and shows adb device offline any solution please
Click to expand...
Click to collapse
Disable MTP in TWRP first.
Thanks for your reply i will try it and reply you soon bro
{
"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"
}
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Extra Fixes :-
Switched To 60 fps from 30 fps
Variant Script Fixed
Boot Control Revision from 1.1 to 1.2
Added Fix for Transferring File Above 4GB
Added Recovery Recovery Variant Of Fastboot Client
Working :-
Decryption
Fixed TWRP Boot up time
Backup/Restore Fixed
ADB/MTP
Flashing Rom
stock rom flashing is now supported
fixed fastbootd and adb sideload
Both Ext4 & Erofs is supported
BUGS :-
Other Bugs You tell me that !!!
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
Hello, this is TWRP, for Oneplus 8T/9R
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
@TheIncognito
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Trees:
Device: https://github.com/ApexLegend007/twrp_device_oneplus_lemonades
Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_s_12.1
Download:
https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
Flashing Rom :-
Make Sure That you have OOS 13 firmware On both slots before flashing rom based on OOS 13 firmware
Copy Rom.zip in your internal Storage Take Backup if you want to take backup Data Backup instruction are given below
After Flashing rom format data and reboot
(!!!!! Warning After flashing custom rom zip The recovery will get changed to AOSP recovery in the inactive slot in which rom got flashed if you want to flash twrp in that same recovery you can do it in bootloader mode!!!!!)
TWRP for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T/9R are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
VBMETA
VBMETA_SYSTEM
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
As previously said by me "I took it down as per some Dev's my commits are not good so I have decided to pull it down for temporarily until I fix my trees with proper commits and do a clean so other can also utilize my trees for their own references" I have pushed new trees on github with recovery release also i hope you all try it and give feedback also and report any bugs you find
Reserved for me
Amazing, I know it was tough for the developers to get TWRP working for A12 and didn't think it would be done anytime soon. This is great as so many custom A12 Roms are being released with bug fixes. Many thank you's to all involved.
Is data backup and restore working on this build I made a backup of data and on restore it just kicks me back into recovery reverted back to oos11
scottlam1 said:
Is data backup and restore working on this build I made a backup of data and on restore it just kicks me back into recovery reverted back to oos11
Click to expand...
Click to collapse
Do you have OOS12 firmware on both slots? Are you using a custom ROM? If so, which one? According to the OP instructions, it says to copy the folder back over, so I'm assuming that means you don't use the actual restore button within TWRP. I'm not sure though 100% because I haven't tested yet.
parag0n1986 said:
Do you have OOS12 firmware on both slots? Are you using a custom ROM? If so, which one? According to the OP instructions, it says to copy the folder back over, so I'm assuming that means you don't use the actual restore button within TWRP. I'm not sure though 100% because I haven't tested yet.
Click to expand...
Click to collapse
I should I assume main upgrade from oos11 should have taken slot b and incremental update c21 should have brought it back to a
Can somebody point me to a thread that teaches how to theme TWRP yourself? I can't seem to find anything. I found many downloads of pre-made themes, but I want to do it myself.
scottlam1 said:
I should I assume main upgrade from oos11 should have taken slot b and incremental update c21 should have brought it back to a
Click to expand...
Click to collapse
Maybe it's because it's an incremental update. Maybe try manually upgrading and flashing the newest c21 to both slots. So assuming you are using OOS not a custom ROM?
Yes not using custom all stock
scottlam1 said:
Yes not using custom all stock
Click to expand...
Click to collapse
Did you try the second set of data instructions? Where you have to take the SIM card out and all of that stuff?
No I wiped data started redid all the setup steps with wifi Google auth then did backup maybe it's the sim pard didn't have to pull sims for oos11 restore I'll try that later
scottlam1 said:
No I wiped data started redid all the setup steps with wifi Google auth then did backup maybe it's the sim pard didn't have to pull sims for oos11 restore I'll try that later
Click to expand...
Click to collapse
Yeah I have never seen that as a requirement before until now either. For custom ROMs it looks like you don't have to do that, but for OOS You have to if I'm understanding correctly anyways from the instructions. @Siddhant221 or @BillGoss please correct me if I'm wrong
scottlam1 said:
Is data backup and restore working on this build I made a backup of data and on restore it just kicks me back into recovery reverted back to oos11
Click to expand...
Click to collapse
Data backup works, but not restore. It's a known problem with TWRP and Android 12.
Also, fastbootd isn't working.
Flashing roms may work, but I haven't tested it and I won't be testing it until backup/restore of data is working.
scottlam1 said:
No I wiped data started redid all the setup steps with wifi Google auth then did backup maybe it's the sim pard didn't have to pull sims for oos11 restore I'll try that later
Click to expand...
Click to collapse
Yeah I have never seen that as a requirement before until now either. For custom ROMs it looks like you don't have to do that, but for OOS Yo
BillGoss said:
Data backup works, but not restore. It's a known problem with TWRP and Android 12.
Also, fastbootd isn't working.
Flashing roms may work, but I haven't tested it and I won't be testing it until backup/restore of data is working.
Click to expand...
Click to collapse
So can we manually restore data then for now?
parag0n1986 said:
Yeah I have never seen that as a requirement before until now either. For custom ROMs it looks like you don't have to do that, but for OOS You have to if I'm understanding correctly anyways from the instructions. @Siddhant221 or @BillGoss please correct me if I'm wrong
Click to expand...
Click to collapse
From my extensive testing on TWRP 11 and OOS 11, I found that I had to remove the SIM card when restoring a backup or the phone boots ok but wouldn't start properly due to problems with , if I remember correctly, com.android.phone.
But the problem didn't happen on custom ROMs.
I don't yet know what the OOS 12 restore process looks like until the restore problem is fixed.
At this stage TWRP 12 is a WIP and not yet ready for general use.
Having said that, backing up partitions (eg, boot) and restoring the image works fine so you can use it to root a phone, restore a stock boot image, etc.
BillGoss said:
From my extensive testing on TWRP 11 and OOS 11, I found that I had to remove the SIM card when restoring a backup or the phone boots ok but wouldn't start properly due to problems with , if I remember correctly, com.android.phone.
But the problem didn't happen on custom ROMs.
I don't yet know what the OOS 12 restore process looks like until the restore problem is fixed.
At this stage TWRP 12 is a WIP and not yet ready for general use.
Having said that, backing up partitions (eg, boot) and restoring the image works fine so you can use it to root a phone, restore a stock boot image, etc.
Click to expand...
Click to collapse
Thank you very much for your reply, your time, and your work! If you need an 8T tester, I will gladly do that! Just let me know.
parag0n1986 said:
Yeah I have never seen that as a requirement before until now either. For custom ROMs it looks like you don't have to do that, but for OOS You have to if I'm understanding correctly anyways from the instructions. @Siddhant221 or @BillGoss please correct me if I'm wrong
Click to expand...
Click to collapse
BillGoss said:
Data backup works, but not restore. It's a known problem with TWRP and Android 12.
Also, fastbootd isn't working.
Flashing roms may work, but I haven't tested it and I won't be testing it until backup/restore of data is working.
Click to expand...
Click to collapse
Bill does orange fox have the same limitations do you know
scottlam1 said:
Bill does orange fox have the same limitations do you know
Click to expand...
Click to collapse
Well, it's based on TWRP, so I'm guessing it'll have the same problems. But I don't use Orange Fox.
parag0n1986 said:
Yeah I have never seen that as a requirement before until now either. For custom ROMs it looks like you don't have to do that, but for OOS Yo
So can we manually restore data then for now?
Click to expand...
Click to collapse
If you mean using an app like Migrate or Swift Backup rather than TWRP, then yes.