Database Users

samsung galaxy note 3 sm-n900 restore

I just want to make sure im doing this right.I deleted some bloatware using titanium and now i want to restore all of it back. To do this i will have to flash stock rom using odin right?If so are the firmwares on this site safe?http://samsung-updates.com/device/?id=SM-N900
Also my Baseband ends in ucmk1 while my build ends in ucmk2 so which version of the firmware do i download?

The site is OK. Flash with Odin the mk2. Next time freeze the apps you don't want with TB, don't delete them.
Sent from my N9005

What region for the firmware do i choose?

demon09 said:
What region for the firmware do i choose?
Click to expand...
Click to collapse
bump

demon09 said:
bump
Click to expand...
Click to collapse
Your region. Or use samsung info from playstore to check csc

Ok everything went great. Managed to download twrp too. I have question about the backup files for twrp and titanium backup. Where do these 2 store there backup files?When flashing roms, dont you do a wipe, which wipes everything including the backup files for twrp and tb? I'm confused about this. And also one last question. How do i download cyangenmod? I went to the site and i cant seem to find it for my n900(international)

demon09 said:
Ok everything went great. Managed to download twrp too. I have question about the backup files for twrp and titanium backup. Where do these 2 store there backup files?When flashing roms, dont you do a wipe, which wipes everything including the backup files for twrp and tb? I'm confused about this. And also one last question. How do i download cyangenmod? I went to the site and i cant seem to find it for my n900(international)
Click to expand...
Click to collapse
If you choose advance wipe, you could wipe everything except internal and sd card..
So your backups of twrp shoud be in twrp folder, so does TB(depends where you choose to save them either internal or sd).
Afaik there is no cm11 build for n900.

Oh lol i went through all that searching and research just to install cm only to find out they havent released it yet Ty for answering all my questions.I have learned a lot in the past 2 days since getting my phone

TWRP restore - Error 255

Hi everybody...
I'm an old user but new member of XDA...
I'm use 3.24.40.87 Rom + 2.8.7.0 TWRP recovery...
My phone was restarted when I was working with it A few days ago then it stayed on Asus logo...
I flash boot but it does'nt work!! so I flash TWRP and backup from my files and I was forced to reflash Rom (With great difficulty)
but now my backup will not restore and it shows Error 255!!
what should I do now?

same thing happened with me, what I did I flashed the same ROM and then used Titanium Backup to restore my apps and app data into the ROM from the TWRP backup.

R_Seen said:
Hi everybody...
I'm an old user but new member of XDA...
I'm use 3.24.40.87 Rom + 2.8.7.0 TWRP recovery...
My phone was restarted when I was working with it A few days ago then it stayed on Asus logo...
I flash boot but it does'nt work!! so I flash TWRP and backup from my files and I was forced to reflash Rom (With great difficulty)
but now my backup will not restore and it shows Error 255!!
what should I do now?
Click to expand...
Click to collapse
This thing happens to me when I select "Enable compression" and "Skip MD5" options in TWRP 3.0...

kloroform said:
same thing happened with me, what I did I flashed the same ROM and then used Titanium Backup to restore my apps and app data into the ROM from the TWRP backup.
Click to expand...
Click to collapse
thanks bro...
how should i restore twrp backup with titanium bachup?

R-seen said:
thanks bro...
how should i restore twrp backup with titanium bachup?
Click to expand...
Click to collapse
Goto Menu in Titanium Backup you will find an option Extract from Nandroid Backup

255 error due to no space in your Internal Storage , try to wipe Internal Storage after that copy your backup to Internal Storage and restore

S7 edge With s8 port

Hello.
I am sorry for dumb question.
But i dont understand very well
I am on sac23 rom s8 port
My question is that when if I wanted to flash a mod Like air command etc.
Will i have to download it of s8 or s7 edge
I mean like i had selected my device as s7edge in xda app
Should i stay on that or because of the port i should change it to s8 for mods ?
Sorry if i didnt explained well.
Thanks in advance

junniscorpio said:
Hello.
Should i stay on that or because of the port i should change it to s8 for mods ?
Thanks in advance
Click to expand...
Click to collapse
Stick to S7
Also do not forget to make a backup in TWRP might save you a lot of hassle if one flash goes wrong
:good:

EasyAndroidPro said:
Stick to S7
Also do not forget to make a backup in TWRP might save you a lot of hassle if one flash goes wrong
:good:
Click to expand...
Click to collapse
1st thanks alot for rep .
2nd. Yes i always take a backup cause i already had much mess lol. Now i always take a backup
One more question. I tried to find answer but get confuse.
1.When taking backup in twrp. Is it posibl to just take backup of data without rom ?. I mean if i need to change rom . Wipe and flash rom and restore my data ?.
2. In twrp what contains the kernal
3. Can you explain me shortly
What does efs. Recovery. system . Data. Efs etc contains.

junniscorpio said:
1.When taking backup in twrp. Is it posibl to just take backup of data without rom ?. I mean if i need to change rom . Wipe and flash rom and restore my data ?.
Click to expand...
Click to collapse
it is not reccomended to do this (its called a dirty flash) you can choose to do this anyway when installing a custom ROM most of them come with an option in the AROMA installer letting you do a fresh wipe or "dirty flash" it will just install the ROM over your current leaving your settings/apps there. Or if there is no AROMA installer with the rom just dont do a wipe before you install. no need to restore using a backup
dirty flash should be fine if you are upgrading ROMS to a later version but you should always check the thread if that is okay. you may run into problems if its a huge update.
junniscorpio said:
2. In twrp what contains the kernal
Click to expand...
Click to collapse
the kernal is boot.img
junniscorpio said:
3. Can you explain me shortly
What does efs. Recovery. system . Data. Efs etc contains.
Click to expand...
Click to collapse
heres some info on EFS > http://www.naldotech.com/galaxy-s7-s7-edge-backup-restore-efs-imei-partition/
recovery is TWRP itself
system is the ROM
Data is your apps etc..
a standard backup is already seleted in TWRP which is
Boot / System / Data
you may as well backup EFS as well its only a few Kb

EasyAndroidPro said:
it is not reccomended to do this (its called a dirty flash) you can choose to do this anyway when installing a custom ROM most of them come with an option in the AROMA installer letting you do a fresh wipe or "dirty flash" it will just install the ROM over your current leaving your settings/apps there. Or if there is no AROMA installer with the rom just dont do a wipe before you install. no need to restore using a backup
dirty flash should be fine if you are upgrading ROMS to a later version but you should always check the thread if that is okay. you may run into problems if its a huge update.
the kernal is boot.img
heres some info on EFS > http://www.naldotech.com/galaxy-s7-s7-edge-backup-restore-efs-imei-partition/
recovery is TWRP itself
system is the ROM
Data is your apps etc..
a standard backup is already seleted in TWRP which is
Boot / System / Data
you may as well backup EFS as well its only a few Kb
Click to expand...
Click to collapse
A bundle of thanks mate. Thumbs up

twrp restored Samsung stock ROM backup won't boot

Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred

fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.

Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.

fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.

fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?

Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info

can't extract apps from nandroid made otg with twrp

My phone was stuck in a bootloop where it could only get to recovery. Using the recovery I created a nandroid backup to the a USB stick using an OTG cable. I flashed the stock firmware and got things setup but I can't restore individuals apps from the nandroid. I copied the nandroid from the usb to sd card but it still doesn't work. I tried restoring apps using Nandroid Manager but when the app is launched it gives the error "app has stopped, close app". For some reasons sms succesfully restored but no user apps. I tried restoring with AppExtractor but it gives the error "unable to generate apk listing"
I also have titanium backup pro but couldn't get it to find the location of the nandroid to try extracting with it.
Any ideas? I really just want my messages back from Whatsapp.
My phone had stock Nougat with busybox installed and elementalx kernel. It should be the same environment now as when the backups were made.

@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)

____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?

twoplustwo said:
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
Click to expand...
Click to collapse
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?

I am unable to copy the nandroid to internal storage. I tried using usb to computer and it just does nothing. I tried root explorer and it says 'copy failed' and file manager says 'cannot load'. This only happens with the TWRP folder inside the internal memory specifically.

____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
____Mdd said:
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
Click to expand...
Click to collapse
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.

twoplustwo said:
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
Click to expand...
Click to collapse
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..

____Mdd said:
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
Click to expand...
Click to collapse
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?

twoplustwo said:
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
Click to expand...
Click to collapse
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..

____Mdd said:
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
Click to expand...
Click to collapse
Just want to confirm everything is working perfect now. Thank you again!