Hi, I have a SGH-317M Samsung Galaxy Note 2. I attempted to flash a custom kernel ontop of the factory ROM now only the phone boots up to Samsung logo screen. In factory recovery mode it says:
E:failed to mount /efs (invalid argument)
The phone has been reinstalled the factory rom for this phone, thats the state the phone is in now. It is unlocked and rooted. The
problem its stuck at the samsung logo wont boot into the OS.
Do you know how i can restore the EFS without any previous backups made?
here is a link to a picture of what it looks like when i wipe data/factory reset and reboot still sticks to the samsung logo, wont boot in.
https://www.dropbox.com/s/248p2ehe7m...105_184844.jpg
Tony
Try a factory reset in your recovery
Sent from my SAMSUNG-SGH-I317 using xda premium
I have thats what youre seeing in the pic link.
any other ideas?
I would say grab a fresh copy of the odin stock image for your device. Also wipe data/factory reset doesnt do anything?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
I would say grab a fresh copy of the odin stock image for your device. Also wipe data/factory reset doesnt do anything?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
It doesnt change a thing, problem persists. Its very frustrating, sorry.
Id say try reflashing the stock kernel ..
Sent from my SAMSUNG-SGH-I317 using xda premium
Yea that's where I would start flash kernel try to reboot after then go for a factory reset
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Tried everything, everyone suggested up til now. I've exhausted all my ideas on where to take this next.
All I can say is try again
Sent from my SAMSUNG-SGH-I317 using xda premium
Odin again then power off reboot into recovery then do a factory reset again then try to boot up
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
if pulling the battery and reattempting a fresh flash with odin yields no results, try a different usb port (mabe even one in the back) or a whole different computer to be safe
Correct. Trouble shoot with odin first. Eliminate that odin is the problem(probably not though) if nor results yeld form that then its a problem with the download or the way u are doing it. Keep trying all, I can say is if u can go into dl mode ur still ok
Sent from my SAMSUNG-SGH-I317 using xda premium
Thanks for all the attempts in sharing ideas but i've made many attempts with Odin. So many different types of ways, with no positive results. Being totally frustrated and exhausted without any optimism, i gave up. Didnt want to send it away but my feelings are it has to be jtagged to restore the EFS memory. Thats the problem android wont boot in cause it cant see my internal memory cantaining the EFS info. Jose @ the www.mobiletechvideos.com says he can restore and do the service. At this point i just need my phone back operating as soon as possible. I just cant believe how just dependent i am on the android smartphone. :crying:
spinrite said:
Hi, I have a SGH-317M Samsung Galaxy Note 2. I attempted to flash a custom kernel ontop of the factory ROM now only the phone boots up to Samsung logo screen. In factory recovery mode it says:
E:failed to mount /efs (invalid argument)
The phone has been reinstalled the factory rom for this phone, thats the state the phone is in now. It is unlocked and rooted. The
problem its stuck at the samsung logo wont boot into the OS.
Do you know how i can restore the EFS without any previous backups made?
here is a link to a picture of what it looks like when i wipe data/factory reset and reboot still sticks to the samsung logo, wont boot in.
Tony
Click to expand...
Click to collapse
I am not responsible for your Actions But it has worked for me
O.K. don,t know if you found a salutation but I had the same problem Factory recovery won't fix it.
Here is what I did this corrects IMEI Number and Serial Number.
You need a backup copy of the EFS I was lucky have 2 SGH-I317.
1. If you can get into Recovery (Recommend latest TWR) which you can install.
2. Boot recovery make a backup of your present rom including efs we know efs is bad Please Note and make sure you save to external SDCARD remove SDCARD place in good phone Backup that includes efs from another SGH-I317. save to SDCARD IMPORTANT.
3. You will need to mount on your PC and find TWR folder inside you will find backup of bad phone and good phone when you create backup you might want to consider naming your backups to make it easy. in twr folder you will see backup folder in that folder you will find your numbered folders open them find your bad and replace with good backup see why its important to choose proper names when you backup.here you will delete the bad backup and replace with good backup put the SDCARD from the working copy into your damaged phone.
5. Go to Recovery hit restore now we have a working phone problem its a Clone? Don't worry about IMEI OR SERIAL.
6. Now you need root explorer (get it on Play Store) Your phone should be rooted for this step.
start root explorer go to root directory click on efs folder then click factory app folder then click serial_no menu pops up click TEXT EDITOR
Now You see serial number enter correct number and save you will get message saved a backup of original file now open the backup and correct the number now save again same message delete the last backup of a backup you can tell you will see wrong Serial number.
7. Restart wait go to settings if everything went well hit about phone then status check EMEI Number and Serial Should be correct.
8. NOW MAKE A BACKUP USE TWR AND INCLUDE EFS IN YOU BACKUP THEN TRANSFER IT TO A SAFE PLACE.
Let Me Know How It Goes.
Related
Ok so I used to have a Samsung Captivate and knew how to root and flash ROMs, was pretty used to it.
I tried to do the same on my HOX, but ran into a bootloop and subsequently I think I've deleted everything on my phone. I used Hasoon2000's All in one kit and unlocked my bootloader, flashed TWRP v 2.3.3.0, but my problem arose after I tried to flash the kernel. It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Anyways, I thought maybe I just needed to wipe things. I looked around and found a source that said to wipe cache, dalvik, factory reset, and system. Wipe those 4, but not external storage or android secure. So I wiped those 4 and I intended to try the backup again but it turns out that cleared everything on my phone. Now when I hit "restore" there is nothing to select. I also used to have a custom rom on the virtual sdcard, but that's gone too.
When in TWRP and I go into "install" the only thing in /sdcard is now TWRP. After looking around, it looks like my only option is to mount the phone to my computer via TWRP and somehow download the standard OS for my One X again. Also in the Mount menu it lists "mount system, mount data, mount cache, mount sd card" I can only check the first 3 options and when I do my computer asks me if I want to format it. I guess I can't mount the sd card because I deleted everything?
If anyone has the time to help me out that would be AMAZING. Right now I don't even care about being able to flash my custom ROM, I just want to get my phone back to functionality. I would love a conversation and would be willing to gmail chat if willing.
Also my phone is the ATT version, 2.20 (or I guess it was before I deleted everything).
Thank you in advance for any help.
I guess the fastest way to get your phone working again is using RUU file, you ll find how to do it here (method 2) or here
It stayed in bootloop so I figured I'd back out and just restore back to the backup I made before flashing the kernel. However, after "successfully" restoring back I was still stuck in bootloop somehow. I know this isn't supposed to happen, it's supposed to restore back to the exact state of your phone at the time.
Click to expand...
Click to collapse
Restoring backup doesnt restore kernel ( boot.img ), you have to flash it manually with fastboot.
Dude. U think htc offers same freedom as Samsung . U are WRONG. If u flash a rom or restore a backup. U also need to flash boot.img separately from pc. Use fastboot flash boot boot.img. i assume you know the basics. Htc don't have s-off , so writing to nand protected system storage is restricted. If u read a little you might have got this. This will solve boot loop prob
Sent from my HTC One X using Tapatalk 2
Fixed
Thanks Yasounet. I managed to flash viper in the end.
OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.
update your CWM.
Zepius said:
update your CWM.
Click to expand...
Click to collapse
It doesn't matter, I flashed back to stock and rerooted. How can I avoid this in the future. It seems that if I wipe data I lose my back ups. How can I save my back ups in the future?
Zepius said:
update your CWM.
Click to expand...
Click to collapse
.....
If you just put your backup in data/media/ then CWM might not see it. Mine are in data/media/clockworkmod/backup/
This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.
deleted
akira02rex said:
This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.
Click to expand...
Click to collapse
I've never once had any errors or failed operations or issues of any kind since using CWM Recovery. Even with my old phone (which was not technically CWM, but based on it). Its hard for me to blame CWM and say that those issues are NOT user error.
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.
Do you have cwm making a md5 for your backup? If not hat is the only time I've had trouble restoring. I've switched from 4.2 to 4.1 and vice versa multiple times without problems.
Also are you using cwm touch or non touch?
Sent from my Galaxy Nexus using xda app-developers app
Also, like others have said, make sure you are using the latest CWM. You can easily get it by downloading ROM manager and selecting "Flash ClockworkMod Recovery". It will also tell you what version you have and what version is the latest.
Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.
spillner said:
Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.
Click to expand...
Click to collapse
In Titanium Backup, select menu then preferences. Scroll down and select backup folder location. Tap the "detect" button then whole device. It should find it.
Also I'd grab a cheap otg adapter... And a 32gig min flash drive to backup to. I have mine run overnight (otg w/charging port) it's basically like having external just deciding when you need it
Sent from my Galaxy Nexus using Tapatalk 2
pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
an up to date version of CWM or TWRP will 'move' (actually rename with the new path) your file system for you so you don't have to do it manually - that's why peeps keep on telling you to update your recovery...
help!
spillner said:
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.
Click to expand...
Click to collapse
I have the same exact problem. When I try to move the backup to the main sdcard directory (a 3 gig file) it fails halfway through. No matter if I use adb push or windows/mtp to copy/paste the file.
Any ideas? Please help, I just want to restore my old rom with all my data. I dont care about 4.2 if I dont have my data.
EDIT:
I FIXED IT! This is how I did it. I had backed up my SD card (including clockwork backups) to my computer using adb pull. So I used clockworkmod recovery to format the SD card and /data/media. Then I started up the phone. I used windows to copy the backups to the phone. Now when I went to clockwork and tried to use the restore backup, it worked correctly. I'm now back to my old phone
I have a solution
spillner said:
OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.
Click to expand...
Click to collapse
I was able to solve this problem. Check my post (above this) and the edit! Goodluck!
Reviving this thread
I am reviving this thread because I would like to know if there is any way to preserve CWM backups and Titanium Backup files when wiping data for a new ROM install.
Is it possible to create a symlink using terminal and link to a static directory which could be protected from wiping data? This is granted the shell permits symlinks.
Thoughts?
I have a problem with my cellphone,
I install cyanogenmod but i am stuck with the boot logo and its not moving from here.
I tried to go to the recovery mod but I cant access it
I did to a backup of my rom but whitout the access to the recovery mod i d'ont know what to do ?
Can you help me ?
Thanks
(sorry for my english)
How are you trying to access CWM ??
pull the battery. ..then after placing it back in. .
Hold volume up / home button / and power button all at the same time. ..
You should boot the recovery. ..
If not. ..your recovery may be gone. ..
If so. ..boot into download mode. ...volume down / home button / and power. ...then odin push the recovery again. ..g
Thanks for your help, I finnaly access the recovery mod.
But I still have a problem. When I am trying a complete reboot from my external card it say: «Error while flashing backup image»
What can I do for that ?
Remove the SD card...
Place it into the PC with a card adapter.Then download a fresh rom and place it on the card..
Then put the card into the phone and flash using recovery. .
You may have a bad copy. .
Odin could also push a factory build via PC as well. ..g
If you can access download mode Flash your rom using odin from link below and do factory reset in recovery.
http://forum.xda-developers.com/showthread.php?t=2004650
Sent from my SGH-I317M
Thanks for everything, i finnaly recover my cellphone but in the process i lost my titanium backup and at the same time some contact.... but its a small price
Last question: Do you know a good program for the backup, I tryed rom manager, rom toolbox and nandroid online and all of them wasn't able to do a backup with my note 2 N-I370m....
Try MyBackupPro
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I was more thinking about a backup of the rom for having a working rom if the same thing appen to me again but thanks
Oh... Why not just make a nand in recovery?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
aslan001 said:
Thanks for everything, i finnaly recover my cellphone but in the process i lost my titanium backup and at the same time some contact.... but its a small price
Last question: Do you know a good program for the backup, I tryed rom manager, rom toolbox and nandroid online and all of them wasn't able to do a backup with my note 2 N-I370m....
Click to expand...
Click to collapse
Make a complete backup from within your recovery....then you will be protected if this happens again in the future.....g
Hello! I am posting this because i'm new to this rooting/custom roms thing. OK. So i have a Galaxy Note 2 GT-N7100. I rooted it using odin, then tried to install new rom. Downloaded CWM, booted into recovery mode and installed new rom. After this, i accidentally pressed 'Reboot' instead of installing gapps & wiping cache and that stuff. Now, my phone starts with the new rom, but i can't get back into recovery mode to start over. When i press vol-, home and power button, after pressing vol+ it goes into download mode (i can't do anything here). Any help will be appreciated!
UPDATE! I tried to flash odin recovery, and now my phone is stuck at the bootscreen. The only thing i can do is get into download mode. PLEASE HELP!
I've managed to get rid of the problem above by installing original firmware from samsung (android 4.3) and worked. The problem is, after that, i installed X-note rom (v2.1) and i think my imei is corrupted now. When i installed x-note, it asked me if i want to make an efs backup, and i accepted. If this is the problem, does anyone know how to restore the backup made? I found it on phone memory (i know it exists) but when i go into recovery mode in cm and i click restore from /sdcard nothing happens (no files to restore). Can someone tell me how could i restore the efs backup?
P.S. I checked phone's IMEI and it starts with 0049.
darkn3ss88 said:
I've managed to get rid of the problem above by installing original firmware from samsung (android 4.3) and worked. The problem is, after that, i installed X-note rom (v2.1) and i think my imei is corrupted now. When i installed x-note, it asked me if i want to make an efs backup, and i accepted. If this is the problem, does anyone know how to restore the backup made? I found it on phone memory (i know it exists) but when i go into recovery mode in cm and i click restore from /sdcard nothing happens (no files to restore). Can someone tell me how could i restore the efs backup?
P.S. I checked phone's IMEI and it starts with 0049.
Click to expand...
Click to collapse
Alright so what is the back up extension ? Is it efs.IMG? Is it 20 KB ?
Please note that restoring efs backup has nothing to do with CWM recovery, its a program you download on PC that backs up and restores your device.
With regards,
Overdub
Sent from my GT-N7100 using Tapatalk
Hi! My efs file is .tar and it is <1kb, somewhere around 20 bytes. When i open it, it doesn't show any items in the archive.
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.