Related
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
TR-909 said:
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
Click to expand...
Click to collapse
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
TR-909 said:
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
bk201doesntexist said:
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
Click to expand...
Click to collapse
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
TR-909 said:
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
Click to expand...
Click to collapse
Toolkit is a automated set of other people's command, programme are coded by humans and human errors are bound to happen, not to mention if something went wrong somewhere, you won't know what went wrong. By doing the steps yourself, you will know exactly what went wrong, and it will simplify things should you have to ask questions here, which you most likely don't have to once you know how to use adb and fastboot, trust me.
Typos while doing your commands won't hurt because it simply will fail and not do anything. Immediately you will know you typed something incorrectly and know you have to do it again. With the kit you will not know at which step it failed so figuring out something will become a task. Doing it yourself sounds like it's longer and difficult but once you do it you will see how easy and simple it is plus you will understand what you did and why.
Sent from my Galaxy Nexus
TR-909 said:
[snip]
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
Yes and yes.
TR-909 said:
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
Click to expand...
Click to collapse
I won't comment on the toolkit, but nandroid backups are stored in /sdcard/clockworkmod/backup/ on your device.
As for the efs partition, you could back it up, but I don't really see what the necessity of it is. That partition is never written to by any ROM (stock or otherwise), so the only way it will get messed up is if you do something to it.
If you want to back it up on your device, just open a terminal window and type:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
That will store it in /sdcard, and then just copy it off your device.
TR-909 said:
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Click to expand...
Click to collapse
Just pull the recovery.img file out of the version of the stock factory image that you are currently using, place it in the same directory where you have your fastboot.exe file, reboot your device into fastboot mode and type:
fastboot flash recovery recovery.img
Or, just save it to /sdcard on your device and type the following in a terminal:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
TR-909 said:
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Click to expand...
Click to collapse
Can't help you out with any toolkit, sorry.
Hello efrant.
Seems you are the n00bs hero in here! I was reading your FAQ and threw some basic ADB commands through cmd to see how it feels ,lol.
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
To clear a few things:
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
we don't have any custom bootloaders, as of yet.
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
not impossible, but many many users never had any issues. to be on the safe side, back it up.
TR-909 said:
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
Click to expand...
Click to collapse
glad you understand. just because something is convenient doesn't mean that it's the best for you.
TR-909 said:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
Click to expand...
Click to collapse
easy. you can't fail with fastboot. like said before, if you type it wrong, it won't go through. :good:
'fastboot flash recovery recovery.img'
done.
Regarding the nandroid, copy off the whole clockworkmod folder.
Will the next nexus have a longer screen?
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
TR-909 said:
[snip]
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
Click to expand...
Click to collapse
If you are using the 6-series CWM, it does backups a little differently (incrementally), and stores the backup in two locations in /sdcard/clockworkmod. I personally use 5.5.0.2, which does a full backup and stores it in one location.
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
As was mentioned above, all bootloaders available are stock bootloaders. A list can be found in the bootloader thread (link in my signature).
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
But if you have bad blocks in the efs partition, you would probably need to get a new device, at which point you have no need for the backup, no? But I guess yes, better safe than sorry.
TR-909 said:
In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
Click to expand...
Click to collapse
With a nandroid alone you can return to today's state.
TR-909 said:
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Click to expand...
Click to collapse
Wiping from CWM does not wipe the data you have on /sdcard, so no need to backup photos, music, etc.
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
TR-909 said:
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
Click to expand...
Click to collapse
The backup is just a shell, it's backed up in blobs, so you will need to copy the whole thing off.
You 're both right that in that the CWM recovery "image" is incremental and the base backup is the blops folder - now the total size is 1.75GB which is logical.
@efrant: thanks for clarifying on backup now it all starts making sense.I 've read Titanium Backup can pull individual files (may I call it selective restore) from a Nandroid backup, say a single app and its data.If that is so then the Titanium Backup could be used as a reserve app and that could save me some precious space.
efrant said:
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
Click to expand...
Click to collapse
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
@Mach3.2: You were right, my bad.The article I read was about CWM recovery 5.5.0.2 so now I copied the whole thing on PC. :good:
TR-909 said:
[snip]
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
Click to expand...
Click to collapse
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
efrant said:
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
Click to expand...
Click to collapse
Point taken.:good:
A bit more on the backup subject...
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Final steps I am going to backup SMS history and find a custom ROM to install.Any ROM recommendations for a "novice user" are welcome...
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Thanks a lot for your support and sharing of knowledge!
PS - So much reading!
Wow, that's a lot of questions for one post! I'll try to tackle some of them.
TR-909 said:
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
Click to expand...
Click to collapse
I don't think anyone knows what changes are in each new bootloader revision (given that they are closed source), but some have had issues with running Jelly Bean on bootloaders older than LA03. I guess "newer is better" holds true in this case.
TR-909 said:
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
Click to expand...
Click to collapse
Again, no one know what changes are made in each radio revision. I personally have not noticed much difference among a lot of the radios, but others have said otherwise. (And no, there are no "custom" radios. All radios are stock -- just from different versions of Android. (A list of radios can be found in the radio link in my signature.)
TR-909 said:
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.
Click to expand...
Click to collapse
Yup, it backs up the cache, boot, recovery and system partitions, and everything in /data except /data/media (which is /sdcard).
TR-909 said:
I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Click to expand...
Click to collapse
I also like 5.5.0.2. I found it to be the most compatible, i.e., it has no issues flashing anything (that I have tried anyway), whereas other versions have issues with certain things.
And I personally wouldn't use MTP to transfer files -- it is flaky at best. ADB is much more stable.
TR-909 said:
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
Click to expand...
Click to collapse
There is not much to do:
1) Download ROM to /sdcard
2) Reboot into recovery
3) Nandroid
4) Wipe /data and /cache
5) Flash ROM
6) Reboot
TR-909 said:
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Click to expand...
Click to collapse
I think so. I haven't use TB in a while, so I just checked and it looks like you are correct -- red.
TR-909 said:
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Click to expand...
Click to collapse
Have a read of the "basics" link in my signature. ADB is covered there.
Wow that's some great answers and a big motive for me to continue "digging".:good:
I will leave you in peace for the time being as here it's about to dawn.
Big thanks and have a nice day.
PS - To be continued...
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Mach3.2 said:
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Click to expand...
Click to collapse
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
TR-909 said:
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
Click to expand...
Click to collapse
With MTP, copying using FTP may just be faster
And just to mention, there's 802.11N on you devices, although it's only single stream w/ 1 antenna..
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.
Hello there,
I have just bought a Samsung Galaxy Tab S 10.5 LTE T805 and I am going to root it using the method described in
the thread below
[ROOT]Official CF-Auto-Root By Chainfire. [T-700][T-705][T-800][T805]
But I don't know which one is better for my tablet Helium or TWRP? And where can i find a tutorial on how to install either of them? If there is not a tutorial available, could you please guide me through the whole proccess?
I have read on another thread that I could use an app, by the name Flashify currently available on Play store, but i don't know how to use it and if it is safe to use it with the CF-Auto-Root method mentioned above?
(Lots of people that used this app were pretty happy after using it and without problems too, but i want your experience on the matter)
To tell you the truth :angel: I am a huge fan of TWRP and I would have been very glad if I could use it again on my new tablet also.
(I had it installed on my previous tablet an Asus Transformer Pad and it worked flawlessly).
So to sum it up
Could you please tell me what to do and how to do it in order to backup my tablet before i Root it?
Which one Helium or TWRP is safer to use?
Thank you all in advance for your time,
Heluim is to backup your apps/data. Twrp can make an image of your whole os and data so you can restore from bootloops. Installing twrp via flashify is safe with cfautoroot as cfautoroot just flashes root and reverts back to your old recovery. Just download flashify, pick install recovery, then hit twrp and pick twrp 2.8.1.0 and hit yup. Then reboot and youll have twrp. You must cfautoroot first to use flashify.
Dont use twrp 2.8.3.0 as it doesnt work.
I would perfer twrp over heluim becuase its a custom recovery. Not a fan of helium as I use titianuim backup.
I would use TWRP. Basically, root first, then install TWRP via Flashify. Version 2.8.4.0, the latest, works fine. I have used it to both back up and restore and there are no problems. It does have a tendency to enable MTP when you first run it which will throw an error when you do a backup (the error is meaningless and doesn't actually do any harm, but the red type will cause panic, so the first time you go into TWRP hit the mount button and make sure MTP is disabled).
I also use Titanium Backup for backing up and restoring apps and recommend it highly. Between TWRP and TB, I can wipe, install a ROM and restore all my apps in about an hour and the TWRP Nandroid backups mean I can always easily recover if something isn't quite right.:good:
Thank you!!! Thank you both so much, for the much needed advice, much obliged!!! :good:
I will do as you advised me and thank God you clarified everything about the differences between Helium vs. TWRP :good:
Hookmt said:
I would use TWRP. Basically, root first, then install TWRP via Flashify. Version 2.8.4.0, the latest, works fine. I have used it to both back up and restore and there are no problems. It does have a tendency to enable MTP when you first run it which will throw an error when you do a backup (the error is meaningless and doesn't actually do any harm, but the red type will cause panic, so the first time you go into TWRP hit the mount button and make sure MTP is disabled).
I also use Titanium Backup for backing up and restoring apps and recommend it highly. Between TWRP and TB, I can wipe, install a ROM and restore all my apps in about an hour and the TWRP Nandroid backups mean I can always easily recover if something isn't quite right.:good:
Click to expand...
Click to collapse
I usually just restore the data partition after installing a new rom instead of using TB then just wipe caches. . I only use TB for backing up and restoring certain apps or data. Doesnt take me anywhere near an hour, using either method.
ashyx said:
I usually just restore the data partition after installing a new rom instead of using TB then just wipe caches. . I only use TB for backing up and restoring certain apps or data. Doesnt take me anywhere near an hour, using either method.
Click to expand...
Click to collapse
Nice idea, thanks. In the case of a clean flash, however, which is the only time I'm using TB to restore, I often want to restore only some apps and use things for a while and not everything I was experimenting with before.
Hey, I want to root my device, and for that I need to go back to 4.4, but I didn't want to lose all my stuff.
Is it possible to do a full nandroid backup (or atleast the /data partition) so I can restore it when I'm back at bump'd 5.0?
I discovered a adb command called "backup", not sure how it goes though
DarknessWarrior said:
Hey, I want to root my device, and for that I need to go back to 4.4, but I didn't want to lose all my stuff.
Is it possible to do a full nandroid backup (or atleast the /data partition) so I can restore it when I'm back at bump'd 5.0?
I discovered a adb command called "backup", not sure how it goes though
Click to expand...
Click to collapse
You can save your installed apps and data with Helium (Pro) to the cloud or sdcard for instance. Copy pics/video`s and music to the pc and place it back after you flashed a rom later. A full backup cannot be done without root.
DarknessWarrior said:
Hey, I want to root my device, and for that I need to go back to 4.4, but I didn't want to lose all my stuff.
Is it possible to do a full nandroid backup (or atleast the /data partition) so I can restore it when I'm back at bump'd 5.0?
I discovered a adb command called "backup", not sure how it goes though
Click to expand...
Click to collapse
http://android.stackexchange.com/qu...es-adb-backup-and-how-do-i-restore-part-of-it
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
I hope these help you.
thanl you both, I'll try those methods
Bricked LG k540
gee2012 said:
You can save your installed apps and data with Helium (Pro) to the cloud or sdcard for instance. Copy pics/video`s and music to the pc and place it back after you flashed a rom later. A full backup cannot be done without root.
Click to expand...
Click to collapse
Sir i bricked my device LG K540/LG LS775 CRICKET USA and not backup but i took dump after brick the phone I have system.IMG file but and tried to remove the effected block using WINHEX but i dont know to make it flashable cause I am new to LG and nobody is helping me to provide the flashable system file ... When i turn on it with the lg logo it says Boot veryfication fail mismatch sig_lem can you help me out for LG device i am NOOB..
Please
Root my stylo 2 how
So this is the situation,
I have SPH-l710 Rooted with CWM, I THOUGHT I made a backup of my stock system.....It made a image.zip and an image directory. SOOOO I flashed the phone with CM121...........In light of all the issues I could not get my camera to work with any app, them CM121 updated, Google play got stuck in a error force close loop that could only be avoided by logging into a separate user account on lollipop. Which is where the camera began to work oddly enough. Anyways I use my camera constantly and wanted to revert back to my 4.4.2 kitkat. SOOOO I booted into recovery and when I selected restore it couldnt find anything. So I installed from the image.zip and everything appeared to be fine EXECPT I couldnt get passed the second samsung logo right after the animation. Just stuck........How can I restore my poor phone back to my system image I have saved?
I tried this multiple times, then just reloaded CM121. PLEASE HELP!!!!!
the wipe/factory reset
wipe cache
wipe dalvik x 3
You could Odin back to stock. What modem are you on? (Ex. nj3, nd8, etc)
Powered_By_Linux said:
You could Odin back to stock. What modem are you on? (Ex. nj3, nd8, etc)
Click to expand...
Click to collapse
L710VPUCNJ3
I did find an image.zip and an image directory with my full phone backup i assume minus the damn splash screen that started this whole thing in the first place. Would I just use odin to flash the image.zip file to restore my original os or would I use CMW and install from zip and use the image.zip file?
And thank you for replying, it's hard to get anyone to help sometimes.
aanddink said:
L710VPUCNJ3
I did find an image.zip and an image directory with my full phone backup i assume minus the damn splash screen that started this whole thing in the first place. Would I just use odin to flash the image.zip file to restore my original os or would I use CMW and install from zip and use the image.zip file?
And thank you for replying, it's hard to get anyone to help sometimes.
Click to expand...
Click to collapse
If you Odin to stock, you need a computer. You download the program (sadly Odin is leaked software so it's pretty shady; you could give Heimdall a shot but it didn't work for me, also Odin is Windows only and Heimdall is cross-platform) and then you download a .tar of a stock image and you plug your phone in in download mode and flash it.
However, there is no nj3 modem so you need to use an older one. Is your phone sprint, Virgin Mobile, boost, etc?
Edit: give this thread a look for info on stock .tars http://forum.xda-developers.com/showthread.php?t=3121212
---------- Post added at 11:46 PM ---------- Previous post was at 11:37 PM ----------
Here's a good thread on instructions for flashing the ndc modem. If you use sprint, flashing nj2 should be the same process, just a different .tar. http://forum.xda-developers.com/showthread.php?t=2774333
Powered_By_Linux said:
If you Odin to stock, you need a computer. You download the program (sadly Odin is leaked software so it's pretty shady; you could give Heimdall a shot but it didn't work for me, also Odin is Windows only and Heimdall is cross-platform) and then you download a .tar of a stock image and you plug your phone in in download mode and flash it.
However, there is no nj3 modem so you need to use an older one. Is your phone sprint, Virgin Mobile, boost, etc?
Edit: give this thread a look for info on stock .tars http://forum.xda-developers.com/showthread.php?t=3121212
Click to expand...
Click to collapse
I have Odin already from when I flashed cmw 6+ to the phone, but before I installed cm12.1 I used clockworkmod and made a backup image. It created a image.zip file, will this contain my original stock but rooted image?
aanddink said:
I have Odin already from when I flashed cmw 6+ to the phone, but before I installed cm12.1 I used clockworkmod and made a backup image. It created a image.zip file, will this contain my original stock but rooted image?
Click to expand...
Click to collapse
I would assume so, however, I'm not sure. I've only used TWRP and a little Philz for recovery. Afraid I can't help you there, but someone else (or Google lol) might know
Powered_By_Linux said:
I would assume so, however, I'm not sure. I've only used TWRP and a little Philz for recovery. Afraid I can't help you there, but someone else (or Google lol) might know
Click to expand...
Click to collapse
OK I understand thanks, one more thing if I assume its a full backup of the phone would Odin be better to restore with or use whatever software created the backup?
aanddink said:
OK I understand thanks, one more thing if I assume its a full backup of the phone would Odin be better to restore with or use whatever software created the backup?
Click to expand...
Click to collapse
I think Odin can only flash tars. Ideally, you'd want to restore the backup with the software that made it.
aanddink said:
I have Odin already from when I flashed cmw 6+ to the phone, but before I installed cm12.1 I used clockworkmod and made a backup image. It created a image.zip file, will this contain my original stock but rooted image?
Click to expand...
Click to collapse
Cwm recovery does not create zip files. If you made a full backup in cwm it should contain system, data, and boot img files. Restore it in cwm recovery.
But to go back to KitKat from lollipop you must wipe internal storage in clockworkmod recovery first .(if that's the recovery you are using).
By the way cwm is pretty crappy. After you fix it, install twrp recovery.
madbat99 said:
Cwm recovery does not create zip files. If you made a full backup in cwm it should contain system, data, and boot img files. Restore it in cwm recovery.
But to go back to KitKat from lollipop you must wipe internal storage in clockworkmod recovery first .(if that's the recovery you are using).
By the way cwm is pretty crappy. After you fix it, install twrp recovery.
Click to expand...
Click to collapse
Thanks for the reply, been tryin to get help for a while. So my version of CMW has the option to create an image backup & also create the same backup in zip format. Inside the zip and inside the image directory they have the boot img files and the system data and ect. I have 2 questions, 1 is what part of the internal storage needs to be wiped? I assume you mean format the system directory? which would wipe the os out at that point? And second since I have cmw installed if I wanted to put twrp on and not wipe the system yet would I need to just use odin and flash it to overwrite cmw? I installed cmw with odin to root the phone originally, cmw is not restoring my backups at all correctly so I would love something that would really work.
aanddink said:
Thanks for the reply, been tryin to get help for a while. So my version of CMW has the option to create an image backup & also create the same backup in zip format. Inside the zip and inside the image directory they have the boot img files and the system data and ect. I have 2 questions, 1 is what part of the internal storage needs to be wiped? I assume you mean format the system directory? which would wipe the os out at that point? And second since I have cmw installed if I wanted to put twrp on and not wipe the system yet would I need to just use odin and flash it to overwrite cmw? I installed cmw with odin to root the phone originally, cmw is not restoring my backups at all correctly so I would love something that would really work.
Click to expand...
Click to collapse
By wiping internal storage, I mean internal sd card (data/media) not system.
If you cannot restore your backup, and are not worried about losing your data, I would recommend using odin to flash the whole stock .tar and starting fresh from scratch. Then re root by using odin to install twrp.
If you are on boost or virgin Mobile use the ndc tar.
madbat99 said:
By wiping internal storage, I mean internal sd card (data/media) not system.
If you cannot restore your backup, and are not worried about losing your data, I would recommend using odin to flash the whole stock .tar and starting fresh from scratch. Then re root by using odin to install twrp.
If you are on boost or virgin Mobile use the ndc tar.
Click to expand...
Click to collapse
Thanks for the info, I will look into the tar I just need to make sure it's compatible with NJ3 and I am on Virgin mobile. I attached a snapshot of the file cmw created, Im pretty sure I saw a post on how to convert that into a flash-able tar file by combining them into one. That backup is clean except for a screwy boot splash screen and being rooted but besides that it was the first backup. Do you know if twrp has any issues with CM12.1? If I can flash my backup and un-root I would be able to start from scratch and do it the right way this time. I attached the snapshot just for your opinion on if I can use my backup from my phone if you dont mind, also to install twrp if I can use my backup I would need to unroot then re-root with twrp correct? Any thanks so much for the responses
aanddink said:
Thanks for the info, I will look into the tar I just need to make sure it's compatible with NJ3 and I am on Virgin mobile. I attached a snapshot of the file cmw created, Im pretty sure I saw a post on how to convert that into a flash-able tar file by combining them into one. That backup is clean except for a screwy boot splash screen and being rooted but besides that it was the first backup. Do you know if twrp has any issues with CM12.1? If I can flash my backup and un-root I would be able to start from scratch and do it the right way this time. I attached the snapshot just for your opinion on if I can use my backup from my phone if you dont mind, also to install twrp if I can use my backup I would need to unroot then re-root with twrp correct? Any thanks so much for the responses
Click to expand...
Click to collapse
If you put that back on your phone in the clockworkmod folder just restore it? If you flash the ndc tar in odin you will be stock unrooted. Ndc is the build before nj3. There is no nj3 tar so ndc is fine. If you manage to restore your backup and get going, you can just get the app flashify from the play store to install twrp. Get the image file of twrp 2.8.7.0 for sprint (d2spr) and install in flashify. Get it from twrp website.
Your backup only has system in it, it has no data. Next time do a full backup. System, data, and boot. You're trying to go from cm12.1 lollipop to KitKat touchwiz without a data wipe and restore. Won't work.
Honestly dude, you seem to have limited knowledge on this. Don't take that the wrong way at all. To save us both some time and get your phone working, just follow this
It's fine to flash over nj3. I'm on virgin Mobile and I've done it a couple times. Also do a factory reset to wipe data. Also wipe internal storage (data/media).
madbat99 said:
If you put that back on your phone in the clockworkmod folder just restore it? If you flash the ndc tar in odin you will be stock unrooted. Ndc is the build before nj3. There is no nj3 tar so ndc is fine. If you manage to restore your backup and get going, you can just get the app flashify from the play store to install twrp. Get the image file of twrp 2.8.7.0 for sprint (d2spr) and install in flashify. Get it from twrp website.
Your backup only has system in it, it has no data. Next time do a full backup. System, data, and boot. You're trying to go from cm12.1 lollipop to KitKat touchwiz without a data wipe and restore. Won't work.
Honestly dude, you seem to have limited knowledge on this. Don't take that the wrong way at all. To save us both some time and get your phone working, just follow this
It's fine to flash over nj3. I'm on virgin Mobile and I've done it a couple times. Also do a factory reset to wipe data. Also wipe internal storage (data/media).
Click to expand...
Click to collapse
Not taken the wrong way, I am limited knowledge on the subject and that's why I ended up with problems. I appreciate the help since I could not get anyone to respond.
madbat99 said:
If you put that back on your phone in the clockworkmod folder just restore it? If you flash the ndc tar in odin you will be stock unrooted. Ndc is the build before nj3. There is no nj3 tar so ndc is fine. If you manage to restore your backup and get going, you can just get the app flashify from the play store to install twrp. Get the image file of twrp 2.8.7.0 for sprint (d2spr) and install in flashify. Get it from twrp website.
Your backup only has system in it, it has no data. Next time do a full backup. System, data, and boot. You're trying to go from cm12.1 lollipop to KitKat touchwiz without a data wipe and restore. Won't work.
Honestly dude, you seem to have limited knowledge on this. Don't take that the wrong way at all. To save us both some time and get your phone working, just follow this
It's fine to flash over nj3. I'm on virgin Mobile and I've done it a couple times. Also do a factory reset to wipe data. Also wipe internal storage (data/media).
Click to expand...
Click to collapse
I appreciate the link, understand the process. Just wondering the link to the .tar file is broken (at least for the moment) I will continue to try it, do you know if the zip file from samsung-updates " L710VPUDND8 firmware version for Galaxy S 3 LTE (Sprint) "
will work also?
aanddink said:
I appreciate the link, understand the process. Just wondering the link to the .tar file is broken (at least for the moment) I will continue to try it, do you know if the zip file from samsung-updates " L710VPUDND8 firmware version for Galaxy S 3 LTE (Sprint) "
will work also?
Click to expand...
Click to collapse
Nd8 will work, however nj2 is the sprint equivalent to nj3 (latest update). It works fine. It's the last one I used. You may need to do the dialer activation code to get service working after you flash. I think it's ##72786# . I'll check.
here is nj2.