Develop Bugs

[Q] Problems Restoring NAND Backup - BRICKED?????

Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks

wallendiaz said:
Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks
Click to expand...
Click to collapse
For a nandroid restore to work properly in CWM, the path to the images needs to be EXACTLY the same as it was when you created it. For example, if when you did the backup, the file was located in /sdcard/clockworkmod/backup/2012.06.30.07.30.00, then you need to make sure that that path is exactly the same. Otherwise, you will need to regenerate the MD5, and then it will work by doing this:
adb shell
cd /sdcard/clockworkmod/backup/2012-06-30.07.30.00
rm nandroid.md5
md5sum *.* > nandroid.md5
exit
EDIT: And please change your title. Your phone is not bricked. Bricked means it is as useful as a brick -- i.e., it does not work anymore and it cannot be fixed without returning it. You may have messed up the firmware, but your device certainly works just fine.

wallendiaz said:
Hi guys
Maybe i have a serous problems here, yestarday i install android 4.1 to test, but before this i do a NANDBackup and then i install android 4.1, but today when i want to back to ICS restoring my backup i have this alert in recovery ( MD5 mismatch ) and now i can restoring my backup and my phone dont want boot because i do a superwipe after install my backup, how i can fix this problem knowing that my phone dont want boot?????
Thanks
Click to expand...
Click to collapse
What recovery are you using and how exactly did you try to restore?

If you renamed the backup make sure there are no spaces
Sent from my Galaxy Nexus using Tapatalk 2

If you can get to recovery then you are definitely NOT bricked.
Sent from my Galaxy Nexus using xda app-developers app

[Q] unable to backup system!

hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA

saadislam said:
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
eventcom said:
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
Click to expand...
Click to collapse
yes, my phone is rooted and s-offed n work well before this and sorry guys previously I was using ClockWorkMod v3.2.0.0..i downgraded to ClockWorkMod v2.5.0.7 to flash radio..but it didn't succeed..So, i flashed through fastboot method and it succeeded.i was able to do a backup after flashing the radio..all went well and 1 day wen i try 2 make a backup in the same ClockWorkMod v2.5.0.7 it stucked in backing up system..

eddykuhan said:
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
(...)
i was able to do a backup after flashing the radio..all went well
Click to expand...
Click to collapse
I see. I already thought that it doesn't have to do with recovery - just wanted to make sure
I suggest you to try reflashing the ROM first - but better make sure that you avoid leftovers of your current "system":
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- reboot
try a nandroid backup again afterwards
if this doesn't help either my suggestion would be to do a complete wipe:
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- wipe all / factory reset
- (I usually do an additional format "system", "data" as well - just to make sure)
- wipe "cache"
- wipe "dalvik-cache"
- flash CM7
- flash gapps 20110828
- reboot
see, if everything went ok then reboot in recovery and do a partial restore of your data (backup & restore/advanced)
reboot again (see if everything works) and reboot into recovery again to try your nandroid backup
There's another thing coming to my mind: do you have enough space left on your sdcard? I never had that problem so I'm not sure if CWM spits out an error about that...

Just for the info, Cwm doesnt give any error if low on space. It just keeps going on with backup.
Sent from my HTC Wildfire using XDA

So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!

Agreed. This is very strange. Have you flashed anything else we should know about that has anything to do with the system partition? Tweaks ect?
Sent from my HTC Sensation using xda premium

slymobi said:
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
hi,
-after upgraded cwm to 5.0.2.0 and i'm still not able to backup
-im using custom mtd
-in matter fact i can restore my old nandroid backup
the story like this after i restore my old nandroid i cannot do backup same ROM again.
and i also tried to wipe dalvik cache from advanced and format cache from mounts and storage then tried a backup and it still fails..:crying:
guys thanks for your feedback im going to do a full wipe and reinstall Rom.!!

eddykuhan said:
-im using custom mtd
Click to expand...
Click to collapse
just to make sure: have you flashed the bravoboot file after the nandroid backup?
If you did, well, a full wipe might be a good idea anyway - but: have you tried my initial suggestion - to format just system? if this is the point where the nandroid backup fails this could be enough to solve your problem...
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- flash the bravoboot file
- reboot
If everything works again you could try to do a partial restore of "data" (in CWM / Backup and Restore / Advanced Restore)
But don't forget to flash the bravoboot file after that one again - and better don't try to restore system again - just data (and sd-ext, .android-secure whatever you like)

Maybe you can try to do backup in 3.x.x.x version of cwm? I had similar problem to yours (I was on 2.5.x.x v CWM) and after it everything worked

I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?

cweijden said:
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
Click to expand...
Click to collapse
Got it solved... I also use MTD partitioning (http://forum.xda-developers.com/showthread.php?t=1233340) and probably have forgotten to flash a required zip after restoring a backup. According to the instructions this should have left me with a white screen. That didn't happen, but it left me unable backing up my system for a while. After repartitioning as suggested by eventcom I was able to make backups again.

Backup Solution hassle free !!?

Hello guys,
I've been wondering how the google screwed us with so many JB 4.3 updates and here i'm still on 4.2.2 restoring to 4.2.2 after every 4.3 ROM flash as some are very sluggish and not so promising and with others the problem is TI backup as google doesn't restore my apps by default whatever the issue is...
After wiping factory data reset (System wipe + cache + data w/o wiping media) i flashed a new rom before that i did a nandroid of my Jul24 Euroskank with Trinity A3 build the last of 4.2.2 plus ti backup of my 101 apps...and after flashing 4.3 i could not restore my backed-up apps TI says error
:grrh : .
Please if any one knows a perfect and 100% tested method to backup user apps help me out with this issue ...thanks !

Ashtrix said:
Hello guys,
I've been wondering how the google screwed us with so many JB 4.3 updates and here i'm still on 4.2.2 restoring to 4.2.2 after every 4.3 ROM flash as some are very sluggish and not so promising and with others the problem is TI backup as google doesn't restore my apps by default whatever the issue is...
After wiping factory data reset (System wipe + cache + data w/o wiping media) i flashed a new rom before that i did a nandroid of my Jul24 Euroskank with Trinity A3 build the last of 4.2.2 plus ti backup of my 101 apps...and after flashing 4.3 i could not restore my backed-up apps TI says error
:grrh : .
Please if any one knows a perfect and 100% tested method to backup user apps help me out with this issue ...thanks !
Click to expand...
Click to collapse
If your 4.3 ROM is using Koush's superuser, go to TB settings - backup location - scan whole device. Then select the legacy foder and you should be good to go. Alternatively, you could flash chainfire's super SU 1.51 and TB will work without changes.

dsr13 said:
If your 4.3 ROM is using Koush's superuser, go to TB settings - backup location - scan whole device. Then select the legacy foder and you should be good to go. Alternatively, you could flash chainfire's super SU 1.51 and TB will work without changes.
Click to expand...
Click to collapse
Will try this asap :good: , could you please provide the link for the flashable zip ?
EDIT: i've got that CF SU v1.51 !

N4 DE, TWRP & root, stuck on VZW red screen. How to go back to stock?

Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.

inseek said:
Hi,
I have Note 4 DE that I've installed custom recovery (TWRP) and then flashed a SU.zip. Everything went smooth so I started installed my apps.
I also created a backup from TWRP (pre- and after root) and also full partitions backup using EFS Professional as described in this post so I should also have a phone-specific aboot partition backed up.
Today I booted up into recovery to show friend of myne how it looks like, then rebooted the phone and now it is stuck on Verizon red logo screen with slow blinking blue light. My attempt to hook up the cable and fire up EFS Pro ended up with error message saying that I do not have permanent root.
What should I do now? If there is no way to fix this and keep all installed apps, Is there a way to restore the phone to factory (while still keepping unlocked bootloader)?
Thank you in advance.
Click to expand...
Click to collapse
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.

jpcalhoun said:
Power your phone off. Pull the battery. Put the battery back in and boot into recovery (volume up, home and power). Wipe cache and delvek. While in TWRP recovery select boot system.
Click to expand...
Click to collapse
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..

inseek said:
Still on VZW red screen after booting up into recovery, selecting "Wipe", then "Advanced Wipe", checkmarking Dalvik Cache & Cache, wiping them out; and then going to "Reboot" -> System. ..
Click to expand...
Click to collapse
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.

jpcalhoun said:
Hmmm, Ok. Don't worry about your bootloader it is alright, not locked. I recommend you restore your backup, either a rooted backup or a stock backup that you made right after you installed TWRP. This time wipe cache, system and delvek. I'm trying to keep you have having to wipe data, but if this doesn't work then you'll need to do a complete wipe and factory reset and then restore your backup. You may loose root, if so then after restoring your backup flash the SuperSU.zip again to regain root.
Click to expand...
Click to collapse
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem​
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks

inseek said:
OK, once I wipe Delvik, Chache & System, then I have to do restore from a TWRP backup I did after flashing custom recovery, right?
I have these in the list:
Boot
Recovery
System
Data
Cache
EFS
Modem​
TWRP gives me a list of partitions above, which ones should I restore? "System" is probably the one since I've wiped it up already, do I need anything else?
Thanks
Click to expand...
Click to collapse
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.

jpcalhoun said:
Yes, select restore and then select the backup you made. The backup will contain whatever partitions you selected when you made the backup (the partitions you've mentioned above). You won't be given a chance to select the partitions once you enter restore, only the backup file name.
Click to expand...
Click to collapse
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?

inseek said:
It actually gives me an option to deselect any of partitions in the list. Which one(s) should I leave selected for restore?
Click to expand...
Click to collapse
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.

jpcalhoun said:
Ok, well it's been awhile since I restored anything and maybe that is a new option in the latest TWRP. Anyway, do not deselect anything unless you are worried about your apps then in that case deselect data, then restore.
Click to expand...
Click to collapse
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...

inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
The first backup you did after you installed TWRP through ODIN is a factory image with the exception of course of the factory recovery that was replaced by TWRP. Knox will always be part of any backup unless you uninstall Knox using something like Titanium Backup. So installing a custom recovery will not replace or uninstall Knox. I caution you not to flash any factory firmware. There is no factory firmware available for the Developer Edition. If you flash a factory firmware for the Note 4 you will lock your bootloader and what you have left is a very expensive Retail version of the Note 4...locked bootloader and all. The advantage of a Developer Edition is the unlocked bootloader...don't screw that up. As far as "Custom", I don't know how to get rid of that...there is a way I just don't remember how to do it.

I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app

athack said:
I just ordered my Verizon Samsung galaxy note 4.. is there a root method available for the retail version ( non developer edition ) if so can someone point me in the direction .. I'm coming from unlocked rooted note 2.. I've been searching XDA and googling the topic today and all I'm finding is just developer edition is root able .. even searched you tube.. thank you
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw

Thank you...
manbat said:
Currently no root for Retail/Consumer Edition Verizon Note 4.....
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / StarKissed / TWRP 2.8.1.1 trltevzw
Click to expand...
Click to collapse
Sent from my SCH-I605 using XDA Free mobile app

inseek said:
OK, I was able to restore backup to pre-root state (without any apps installed) and then from other backup that has some apps installed. So far, so good, thank you for helping me out.
I still have a question: how do I restore to factory? I guess I need a factory image that was replaced by TWRP, and then I will use Odin to flash it? Did flashing TWRP change the KNOX bit? Is there a way to completely restore N4 DE to factory the way it came from Samsung or once custom recovery is flashed and phone rooted, there is no way back (it is showing me "Custom" every time I turn it on)? I am still in doubt if I want to keep the phone as it is very similar to my rooted N3...
Click to expand...
Click to collapse
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911

jpcalhoun said:
inseek, let me correct a comment I made in a previous post "there is no firmware available for the Note 4". That's not entirely true. It is true that there is not a stock firmware .tar that you can ODIN that returns your phone to stock DE just like it came from Samsung. This thread http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 does provide a few stock .tar files that can safely be ODIN on the DE. These files do not provide the "safety net" that we would like in terms of a complete flashing of the DE back to stock, it only provides stock .tar files for several "pieces" of a complete stock ROM and bootloader. Read the OP and post 2 and 3 very carefully before you use any of those .tar files. There is no .tar for the DE aboot/bootloader. The only way you can have a backup of aboot/bootloader is to follow the instructions here: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Click to expand...
Click to collapse
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE

inseek said:
Thank you for this update, jpcalhoun.
I've followed these threads when I first flashed TWRP so I do have a backup made via TWRP (which doesn't include aboot) plus the one created via EFS Professional. I was just wondering if there is a dump of all partitions as they are coming from the factory. I am not a specialist but I was thinking that if I have aboot (which from what I read is unique for my phone), original boot partition + the remaining partitions in my backup then I should be able to restore the phone to factory state.
Is there a way to dump all partitions from a brand new N4 DE that just came from a factory? Obviously, for EFS Professional we need custom recovery + BusyBix + root to work. TWRP is capable of backing up most partitions but not aboot/boot. The way it is now, once we flash custom recovery, there is no way back as if there is something wrong with the phone, Samsung will see that "Custom" sign on the screen and from what I've read, will just re-flash a locked bootloader prior to sending the device back to the owner. I wish I knew all this prior to ordering my N4 DE
Click to expand...
Click to collapse
I'm not a Linux guru or a ADB guru, but I think you can do that using command line scripts, but I can't swear to it.

Revert From 5.1.1 to 4.4.2

[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help

I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right

Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup

lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?

After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D

Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^

Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.

lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title