Related
I just successfully downgraded from COD6 back to NK4 in order to alleviate concerns that downgrading back to Kit-Kat was going to be an issue. Reference post found: HERE. I am outlining the method I used to downgrade below, but this can also be a guide on how to upgrade to later firmwares.
I don't recommend trying to downgrade past NK4 and only downgrade if your dev says you need to! downgrading is risky and can brick your device! You've been warned!
Downgrade to NK4 or Upgrade to COD6
1.) Download Odin v3.09
2.) Download full Odin NK4 (Found HERE) or COD6 found, almost everywhere
3.) Unzip the file and there should be a file called "N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5" or your COD6 tar called, "N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5"
4.) Open Odin v3.09 and click the button labeled "AP" and locate the tar file you unzipped
5.) Let it load, it will freeze for some time while checking the MD5 and then be ready to go
6.) Turn off your phone completely; after it is powered off hold vol down+ home + power until you see a warning message
7.) Hit Volume up to continue
8.) Plug in your device and and the it should light up blue under "ID:COM" and say something like "COM:1"
9.) Check to make sure your tar is loaded into the AP slot.
10.) Ensure that they only two boxes that are checked are: "Auto Reboot" and "F. Reset Time"
SHOULD LOOK LIKE THIS PHOTO: http://cdn.droidviews.com/wp-content/uploads/2013/05/galaxy-s4-odin-flash.jpg
11.) If you've verified that your Odin looks like the picture then click "Start" and be patient
*****************************************************************************************************************************
***If Downgrading You MUST wipe USER DATA following the steps below or your phone will boot loop on restart!***
***If Upgrading I Strongly Suggest wiping USER DATA to avoid potential issues from upgrading!***
*****************************************************************************************************************************
12.) Wipe User Data as outlined below by booting into recovery as soon as the download completes by holding power + volume up + home until it says, "Recovery booting" in blue in the upper left corner.
13.) After doing the factory reset and rebooting it will you can setup your phone like normal
These are the same steps if you want to upgrade with Odin, you just use the full tar of the upgraded firmware (COD6 in our case)
To Wipe User Data
1.) After you've clicked start and the file completely loads on your phone it will reboot and immediately enter recovery
2.) It will show and Android and a blue bar scrolling across setting up your system. It will reboot again after this
3.) As soon as the screen turns black hold vol up+ home + power to enter recovery again
4.) It will boot to the Android again and you should see THIS before the menu loads
5.) Scroll down to "factory reset/data wipe" with the Vol Down button and then hit the power button to select it
6.) Scroll down again and hit "Yes" so that it completes
7.) After it is done reboot and allow your phone to boot normally
8.) Setup your phone like normal
Done!
I vote for this to be a "Sticky".
Good job :good:
Thank you, I've been with 5.0.1 for the day and the battery was better on 4.4 and it looked better. I was going to try as soon as I got home but now I know.
I was googling how to downgrade and ran in to this. A lot of report saying it worked. I'm surprised this is possible with Odin. Thanks for the additional confirmation.
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
aznmode said:
Just wanted to add. Downgrading to NK4 will require a factory reset, otherwise you go into a boot loop.
Click to expand...
Click to collapse
I know it was a long time ago when you posted this, but it just now sank in that boot loop = bad
I will update the OP, thanks for pointing this out :good:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
CtJackHarkness said:
Makes no sense. It says must wipe user data....why on earth would you need to wipe / factory reset just to UPGRADE to COD6?
Guide needs proper writing...
Click to expand...
Click to collapse
Because doing an Odin upgrade or downgrade on your device does not wipe the data partition which is necessary when changing a letter versions of Android. For example, let's say you are going from Kit-Kat to Lollipop or perhaps Lollipop to Kit-Kat in a way similar to that presented in this "How to".
However, I get that new members need help sometimes so let me help you research your criticism.
Welcome to XDA.
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
KingBeef said:
Forgive my ignorance, but I am curious. When upgrading to a new letter version via OTA or a program like Kies, there is no factory reset done by default. The fact that a factory reset solved problems for many this go around aside, why is it a must when using Odin? I have upgraded ma few devices over the years to new letter versions without resetting so I am just trying to get a better understanding.
Click to expand...
Click to collapse
The reason OTA and Kies don't do the reset themselves is because they aren't capable of backing up the data you've accumulated on your phone since you've owned it. The average user only get an icon in the upper left-hand corner that tells them to update and they do it because T-Mobile says so. Imagine that same user installed the update and then they were looking at the Lollipop welcome screen like they had just taken the device out of the box. It would lead to an outcry from consumers because they lost months of data from the upgrade. However, we here on XDA are not average users and some of us know exactly what happens during these updates. You probably don't remember this, but there was a time when Odin wiped your phone automatically even on incremental updates. Because just like flashing a ROM, clean is the only way to truly ensure that residual files are not causing problems. But they eventually removed this behavior in later releases of Android. I don't know why this was done, I am only able to tell you the history of Odin as I know it. However, because Android changes have been so drastic lately (locked SD cards, addition of preload partition, removal of preload partition, SELinux policy updates, institution of Knox and protected files, etc etc etc.) not starting with a clean slate led to a myriad of problems for users. If you need specific examples just look at the Galaxy S5 Wi-Fi issues from taking the Lollipop OTA without doing a factory reset. If you format your hard drive before installing a new version of Windows then you should be capable of understanding why clean partitions for an OS upgrade makes sense. But you don't have to take my word for it, click the link I left with CtSomethingOrAnother up there. People almost unanimously support a factory reset for major upgrades. So you can take my advice or follow your own, but I promise that I'm going to get plenty of sleep tonight regardless of what you decide to do with your phone. You have to realize that I am giving advice as a senior member of a respected development community where new members come for answers. I make sure that I am giving them the best advice that I could possibly give them with my experience on these forums and with Samsung devices. If users decide to cut corners after knowing the proper way to do it, that is on them.
tl;dr -- I wrote this Howto so that I could help people; not waste their time. You don't have to believe anything I wrote above. In fact I encourage you to research this information yourself and come to your own conclusions about why factory resets are necessary. Until Google goes on record saying, "No more factory resets for upgrades" I'm going to keep my advice just the way it is written.
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
KingBeef said:
I appreciate you taking the time to explain this. I have been flashing and what not for a few years, but I am by no means completely aware of why I do things a certain way in all cases. It is nice to know the "why" behind things sometimes.
Click to expand...
Click to collapse
To me, the why is always the most important part. When someone posts a flashable file to fix a problem I open it up to see what it is doing. It took a lot of reading and some prior experience with Linux to be able to grasp a lot of what Android developers are doing when they change the files
CtJackHarkness said:
I think resetting the phone and having everything wiped should only be done if experiencing problems. Everywhere online this is the case. It is NOT required to wipe a phone. And again if you wipe / factory reset a CDMA phone - don't they have you call in to reactivate it? (little offtopic but just curious regarding verizon)
Click to expand...
Click to collapse
I truly don't understand how you could acknowledge that skipping the factory resetting could lead to problems for people but that you don't recommend it because people should just use it until they have a problem and then wipe all their data at that point. And as far as "everywhere online this is the case", I literally Googled for you tons of links with people saying to factory reset for Android upgrades and you're choosing to ignore the information. That's on you. As far as CDMA phones having to be re-activated? It's been years since I used a device on Sprint and doing a factory reset on Android led to the device activating itself. It isn't an issue, it's just part of the setup process. It's no different than updating the PRL and Profile on Sprint (CDMA) once a month to ensure roaming capabilities are working at peak efficiency. Verizon customers used to have to dial a number to update the PRL but now on Android it happens in the background just like it would during setup.
However, changing your mind isn't my job nor is it how I intend to spend my time on here. You can do whatever you wish with your phone and what I wrote is exactly how I handle my phone. I'm leaving your criticism and my responses in this thread for people who want to hear both sides and hopefully that will accomplish what you set out to do by posting here in the first place. If you still aren't satisfied, please take it to PM.
EDIT: Nevermind, I went back and edited the post to clarify that boot loop happens on downgrading and encouraged people to wipe user data while upgrading.
This method worked for me..
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
hacker904 said:
This was my solution to completely downgrade the N910T back to KitKat after a full Lollipop stock upgrade or rom.
Please do a nan droid back up before attempting this first?
*** I am not responsible nor accountable if you damage your android device when done incorrectly or attempting this***
Please understand doing this will and is going to trigger the knox count if attempted.
When I did this it worked for me to test Lollipop or roms and back to KitKat stock for example:
DARTHSTALKER_NOTE4_V2
InfamousROM_Note4_COD6_v1.8.1.
Just to name some good KitKat and Lollipop ROMs for the N910T that I use.
Four things your gonna need before you start:
1. The actual KitKat N910TUVU1ANK4 Firmware.
2. Odin3 v3.07
3. N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img (This contains 4 files: boot.img, modem.bin, NON-HLOS.bin, recovery.img).
4. WinRar or 7zip software.
What I found is that the baseband changes and does not allow to downgrade from stock N910TUVU1COD6 Lollipop back to stock N910TUVU1ANK4 KitKat with Odin it just wouldn't allow it. I've done this so I know this works since I wasn't ready for Lollipop bugs and battery consumption. From what I heard this couldn't be done.. Anyway after your nan droid backup Wipe every thing in your recovery TWRP: Advance wipe, Wipe the dalvik cach, System, Data, Internal storage, cache reboot back download mode. Now take the TMB-files-modem.bin-boot.img-recovery.img extract it with winrar or 7zip. Now go back into Odin Click Phone and search for the files you just extracted. They are 2 files needed and that's the NON-HLOS and the modem file. This needs to be installed one at a time on the Phone tab using Odin. Flash the NON-HLOS and reboot back into download mode. Now flash the modem file in the Phone tab using Odin and boot back into download mode. Now flash N910TUVU1ANK4 KitKat Firmware using Odin and let it finish and reboot completely. Check and make sure that Odin completes the flash and reboot completely to Tmobile setup screen. Done..
If the firmware feels weird at first just do a factory reset and cache in the stock recovery. Hope this helps out the XDA community. Don't forget to thanks please?
Here: N910TUVU1ANK4_N910TTMB1ANK4_TMB-files-modem.bin-boot.img-recovery.img
h t t p://w w w 10. zippyshareDOTcom /v/5feSbGgX/file .html
Click to expand...
Click to collapse
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Internal data
v2.2v said:
I'm going to wait on some testers for this one lol but if confirmed...I'm on it! Lol although I'm a little confused why I would nan and then immediately wipe internal data? I don't have a SD card yet though (just got phone today) so any nan I make goes right to internal :/
Click to expand...
Click to collapse
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
hacker904 said:
I wouldn't recommend doing any type of internal data wipe unless you have a SD card. Now take note of this when using custom (TWRP) recovery that you have to manually go into storage during the back up. Now go to the drive/storage and change the option in oder to back up on the Ext.SD card. I would be careful in the recovery when advance wiping the phone to reinstall another rom. It has the option to wipe the Ext.Sdcard...Do not do that take it from me I've done it rushing and it sucks. TWRP backs the nandroid on the Ext. in a TWRP file.
Hope this helps every one out.
Please thank?
Click to expand...
Click to collapse
Hey bud. and this by no means is trying discredit you, but the OP works just fine. Just did it. Odin 4.4.4 and wipe data after.
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Santos89 said:
@hacker904 did you do this from 5.0.1 or 5.1.1 because I am on 5.1.1 and have tried to return to Kit Kat and it will not allow me to. Also waiting for testers on this one
Click to expand...
Click to collapse
I guess tmobile changed some security policy that blocks phone users from downgrading.
Source:
http://forum.xda-developers.com/showpost.php?p=64548030&postcount=5
downgrading from cod6
Has anyone confirmed that you cant downgrade from Cog6? I am on one of the 5.1.1 ROMs I tried downgrading to 4.4.4 using ODIN but it keeps failing. Has anybody had any success with this?
The SUPER Custom Rom Guide and Troubleshoot
There came a new version, your droid got old school and there is no support from Samsung cause they have forgotten about you.
Service centers you looked upon, and to mention exorbitant fees plus service tax came along. Thank You ma'am. will see you around.
Your droid is lagging and hanging and Lo, stops working suddenly. Now you just want to try something new, cause you can't sell them or buy new.
You search on google,
find on Youtube,
Read between surveys and blogs,
tried it yourself,
sometimes got lucky sometimes got thorny.
Now you come to the XDA community. there is too much to absorb and you're kind a new, welcome to all of you.
Click to expand...
Click to collapse
Dealing with most of the trouble making bugs and useful insight into cornering them like a rat
1. Tab is Stuck on Charging Screen. Tab is not turning On, battery completely depleted/Not charging, Nothing is Working
2. Stuck On Samsung Logo Screen.
3. Stuck in a Boot Loop.
4. Stuck On Firmware Upgrade Encountered an Issue.
5. Bricked.Explained in Post number 2
Well that would sum up for me and most of the users will agree that these are the cases that really needs attention and no cussing about how your droid lags and hangs, doesn't makes it to the lists So, by the end of this guide, I would hope and expect at least so much from users to at least have a better knowledge and general idea of how things work here. so users don't just go on saying HELP HELP I am a NooB, Please read and understand first, dude. Thank you I will try to make it simple even if you're not so cool.
A few words about me if you're interested
OH!! you clicked!! wow. well what should I say here. ahem, hello gorgeous. I am Sam So, unlikely,
So guys, I wasn't lucky enough to get everything organised at one thread and spend a lot of time finding a perfect place for everything I would want to, so I thought this would be worth a share. It took me almost a month to write this stuff. yeah I was bored to the core, so put in some fun stuff
along with most of my learning experience and knowledge gained here on XDA in this Guide over the span of 3 years, I would just read and experiment it myself, kind of guy, I wouldn't have dared to put up this guide sooner, but now after successfully solving most of the cases even other people hard bricks and trivial issues that I get to see everyday and keeping myself safe from hard bricks with still not knocked out by one. all thanks to this community this is my gift that I would like to give in return, and I am just someone who likes to get to the edge of the world, exactly, on a round globe. Thank You
Android Broken into 5 parts, Worth a Look
Well not exactly broken but explained in 5 parts ( There are more but I choose not to, thank me for that)
1. Boot section(bootloaders/kernel)
This is droid's heart(accept it), responsible for the droid's birth and keeping it alive, sleeping, waking up, slowdown and speedup, overall working of the system, it has impact on every part of the droid. mess up things here, and droid won't start up at all and will stop beating and malfunction. then you will need a pacemaker and CPR(J-TAG) to revive it or it will keep the brain in coma. yes pretty much like our heart.
2. System section
This is a droid's mind, Its the place where all main work and processes are happening, with rooting and flashing you get a licence to open that mind and analyse, read logs, stats. that brain, heart and all your body is producing, you can see it all and make changes in it, put few things from outside. clean it, format it, wipe it, make amend(patches). So, imagine all that happening in your mind and the idea of cleaning your brains for once, wiping the mind, giving new and fresh experiences(newer and updated files) new interface(new UI), affecting the overall performance and changing to a whole new perspective with which you look at things.
So Clear your mind about this and remove your bad experiences and upgrade it with new stable ones. err not the custom beta and alpha ones, cause then you will give your headaches and put them in depression.
3. Data
This place is the memories part, and everything is stored up here. Everything. some would be overtly stored(on sdcard) and some deep inside you(under system/data/data). now overtly ones are not a concern here but deeper ones are hard to forget and lingers in your system, these won't go well if your heart and mind changed or aren't supposed to be the same, or in trouble will they? (i know I am good at explaining this)
4. Cache
Well, this one is the dreams part. damn I am right just admit it now. they come from your memories, keep it or forget about it, that's unto you. sometimes it can interfere with your old memories when you get new ones. so if unknown problem persist, with your heart and mind working nicely please clear your dreams and look into some of the memories. otherwise get the mind checked first.
5. Recovery
This is the soul part, whenever your heart or mind or data or dreams are feeling lost, you connect to it and revive them accordingly, or contact ODIN.
I hope you had some fun in the above part and a very clear and better understanding, So now you know where things are going wrong
The Beginning
Ensure your Charging Adapter, USB ports and your USB cable, are in good shape and working in accordance, Never depend on USB hubs or any USB port that is a faulty or slow performer, use original cables, or buy new ones, the cable does create problems in some cases. if you're sure that these are fine, then let it in charging for few hours to even a day. depending upon how fast the droid recovers.
So what do you do, when you have to go the custom way or solve your problems?
i. Press Power and Volume Up(right button) or
ii. Press Power and Volume Down(left button) or
iii.Press Power and Hold touch screen combinations.
iv. Press nicely and hold it for good few seconds there, no hurry, really.
v. Long press the power button, release the power button and, when you see a logo appear during boot-up, hold down both the volume up and volume down buttons. Continue holding the two buttons until the droid boots up with a safe mode indicator at the bottom-left corner of its screen.
vi. Plug it in PC with the USB.
vii. Remove the Battery blow air on it and pat a little and put it back inside.
So what happens after doing what I said above?
i. (a). The tab goes into download mode
ii (b). The tab goes into recovery mode
iii(c). the tab switch off/on again.
iv (d). Now the Combinations worked properly, beware cause many a times on droids this could be a seriously tricky part.
v (e). The tab goes into safe mode.
I know you got tired there holding the buttons and No you didn't had to press it so hard
vi (f). Your droid and PC responds and connects.
yeah, I know Nothing much of a Help, but it will make sense when it doesn't
vii(g).
this is an age old trick of which there is no proof of success, but it has been working since ages.
As long as you can enter download mode or recovery or safe mode you can walk the path of going custom and troubleshoot along the way. Piece of cake. Most of the ways including how to root, upgrades, lag free and better performance starts here
[if you're ready to take the plunge, remember there is no backing out.]
Click to expand...
Click to collapse
Choose your steps wisely here now, if possible just read the main points and see if you have done all those first. that will save your data in some case and in some save you from getting all messed up.
CORA, (CODE OF RECOVERING ANDROID)
For NON-ROOT USERS
Safe mode
Stock recovery
Download Mode
FOR ROOTED USERS
Custom recovery,
Nandroid BACKUP,
Download mode
Safe mode
Click to expand...
Click to collapse
WITHOUT MODIFYING SYSTEM FOR HARDCORE STOCK USER
1. SAFE MODE
This mode generally helps when the problem is arising from 3rd party apps and is making your droid reboot again and again, lagging, hanging issues, so whatever is causing problem, if you can reach here, you can uninstall them clear their data and cache, and yes, free up some internal space too and backup your data from settings-backup as well. then factory reset if you want to.
2. STOCK RECOVERY WAY
You have never rooted your droid and you don't want to root and you don't want to move away from stock, well pressing the Power and Volume Down(left button) will take you there.
try to clear cache/data factory reset(will lose you data stored on internal droid) and yes it does solve few of the cases, even if it doesn't look so promising, it has solved, and will solve quiet a few issues. no chance of getting that data stored on internal., phone book, messages, chats.
3. THE DOWNLOAD MODE WAY
Flash a stock firmware Explained in post the download way.
Code:
Now if you are already Rooted or want to Root to have a better option of saving your data, or reviving your droid
it's like performing a surgery on your body by yourself.
So be careful, you have been warned, Samsung voids the warranty,
and I don't give any Guarantees that these Instructions will work for all.
MODIFYING FOR PEOPLE WHO RISK IT
1. Getting Rooted
2. Custom recovery Way and (post number 4)
3. Download mode Way. (post number 5)
AND FOR THOSE WHO WILL BLAME ME
Seriously?
The most important and most essential part here is GETTING/HAVING a NANDROID BACKUP, the very FIRST THING that you MUST HAVE DID/DONE upon getting ROOTED. Make a Stable Clone guys.
You will need to get rooted and custom recovery to do that, not to forget enabling the USB Debugging Option from Settings->about device-> Build number-> press 7 times->back->developer->Enable USB Debugging and that's the beginning my friend.
Click to expand...
Click to collapse
Other threads with good post for the tab 2 series about rooting guides, containing firmware links, recoveries, Roms list, kernels, pretty much everything.
All about P51xx
All about P31xx
Latest Roms, Recoveries updated by Android-andi, the best developer around here
other droid users please look it up under your device thread tree, they will surely have a way, tailored and to the point.
Click to expand...
Click to collapse
Getting Rooted is only advised if you're going to stay on stock rom, debloating the system and making changes yourself.
if you're going to install a custom rom, which would be generally rooted, so you can skip to getting a custom recovery first.
CF auto Root are better option for any device to get rooted rather than other options
CFauto-root GT-P3100
CF auto root for GT-P51xx
or you can visit the chainfire homepage for your device which contains the root file for almost every device.
ROOT FROM DEVICE WITHOUT PC
in cases where you can't use ODIN for rooting or you want root your droid and there is still no method explained for Root on XDA then using framaroot, towel root, baidu, kingo or any other app(they can root some sets of droid) is advised, without ODIN or in case you couldn't connect your tab to the PC with the USB, only then these apps are good ways to get root. after that you can use flashify app or other apps for same purpose that has the feature to flash .img files, you can also use Mobile Odin app which can pretty much work when you can't use Odin from Pc.
then you can download a copy of the custom recovery image.(recovery.img) browse in the app and let it do the installation for you. this is useful for droids which doesn't have that much support like we and others have here
Click to expand...
Click to collapse
Common Issues faced
If you have read about my explanation of android's partitions in the OP(Original Post above), you would know where exactly to look for the problems. Moving on,
For other Geeks
Please remind me if I missed few things, you see I have put up this Guide mostly of the files I have in my system partition,I might have missed few that were stored in data or cache partition
1. Tab is Stuck on Charging Screen. Tab is not turning On, battery completely depleted/Not charging, Nothing is Working
Possibilities
* if the tab doesn't feels warm even after charging for a whole day,
F1. Battery dead,
F2. Circuit/Motherboard blown,
F3. Bad Charger/charging point
F4. No electricity
if it's getting warm and still not turning on
F5. Hardware buttons not working
F6. Motherboard needs replacement.
F7. Flashed a bootloader/kernel(along with a Rom/firmware), or something not meant for your device, which is the hard brick in this category please refer to case number 5. (process on post 2)
F8. Some Custom Roms have bugs that won't Charge, stay stuck on the battery icon, unless you remove the plug and turn on. always read before flashing a Rom, if there are no info, better ask the developer before you go flashing or post your Question in related thread where they would get noticed.
2. Stuck On Samsung Logo Screen.
This could be from various reasons generally not so serious ones mostly recoverable issues of which, some are
Flashed a incompatible Custom Rom zip or any other flashable zip containing files not meant for the exact device.
Flashed a kernel/ bootloader incompatible with the Rom, wrong kernel modules, messed up system lib files, (lucky enough to still not be in hard bricked section.)
Formatted system partition and there is no OS installed. (one of the silliest mistakes I have done)
Some other that I maybe forgetting just like I completely forgot about the above
Possible Solutions
Go to the stock recovery and wipe data/factory reset (this will make your precious data that you stored vanish, except data stored on SDcard) (explained further in post 3)
Get a working stable compatible kernel/Rom or flash stock firmware. (explained in post 2 and 3)
Download from a different source cause chances are the file got corrupted or infected while downloading or transferring. (post 3)
Find the file that is stopping the device from booting up, starting from the kernel, to the system files. duh?
Go to the custom recovery way.
Go to the download way
3. Stuck in a Boot Loop.
Boot Loops are crazy and they will make you mad, they can hit you anytime for even little of tasks, Root or not root, either you are testing a new app, modifying/copying/editing/deleting/overwriting files in the system or data that don't even look so dangerous, just flashing some mod, GAPPS, or just updates rolled out by devs(nothing against them) this will surely hit you, no matter how focused and diligently you work. boot loops will make you do hula hoops.
Boot Loop is generally solved by
Hello? whatever you did that I mentioned above, just roll it back.
if you can't figure it out, well then
Remember the CORA order Quoted above in the first post? Read on
Safe Mode?
Go to recovery and clear cache then reboot.
Clear data/factory reset from stock recovery(data stored will be lost) (root users can skip this and directly go to 7)
No, Recovery?, You sure pressed the button nicely?
Flash a custom recovery image(recovery.tar) from Odin
Repeat from 1-3
Backup/Restore from Nandroid backup
Don't sit for the next exams without memorizing your lesson.
Cleared cache/dalvik cache?
Flash a Compatible Custom kernel
Find the stock replacement of the file/app you messed up from a firmware or a custom Rom, put it in a flashable zip and flash it (advance users)
Clear/data factory reset either from custom recovery. (*loses data)
Flash the Custom Rom, first dirty flash then clean flash.
Flash a Stock firmware from Odin. (loses data)
4. Stuck On Firmware Upgrade Encountered an Issue.
Well this problems hits non-root users and root users too? why? because we wanted an update.
it was trying to upgrade and something got in between to make it stop
Battery/Power/Electricity - for non root users, the most common culprit would be the battery, seriously guys, please keep the battery in mind always. it's a very common mistake that cost many of users. For ODIN users, please see you have a uninterrupted supply of power to your device and you are using latest version along with Hi speed USB ports.
kies!!! I hate that thing and majority of others will support me here. I got rid of it the day I installed that thing on my PC.
interruption from the user side while the device was taking an upgrade. removed battery? fell down on the floor? no?
hardware issue, unlikely, rare I would say, in case the device did came out with a weak emmc card.
Bad/wrong firmware downloaded files.
In case you had a custom recovery and its still working, check the custom recovery way
I Know 1st didn't helped you,
Refer to the Download Mode way and get a custom recovery
Don't forget to clear cache, you do know that's where the device keeps the downloaded/image firmware file, and that's where it is installing/extracting from. the dream partition, no wonder you got errors. you got a nightmare now
try the download mode way
probably it's best that you either forget about the mobile, or give it to a service center for a J-TAG and get it repaired.
I knew you would look here, there is indeed a last ray of hope, explained at the last thing to do in download mode way
5. Bricked.
There are 3 types of Bricks, Soft Hard and The Brick, That's it.
Soft brick
well you are safe and sound, you can even recover from custom recovery mode.
Hard brick
skynet has fallen, just like it infected the droid Arnold Schwarzenegger of the terminator version 3.0, the codes were injected into his heart making the brain dis balance and resulting in partial heart seizure and a coma, but he still had the cache and data part intact along with recovery, so it went there, restored a nandroid backup and went online again. BAM!! so easy. but why? I mean ours droid having reached version 6.0 can't recover from the same way? Where only hope here is a CPR or getting J-TAGGED? not to mention, which should be done by expert surgeons who would charge exorbitant . So, don't waste time with a jig or any other miracle to happen and please don't go on the droid with a shocking therapy. I am more of a practical guy and prefer professionalism.
The Brick
err, that's the solid one, put that on your heart, and forget about this droid and shell out money for a new one. : that's what the company wants to tell you here and that's the reason it doesn't want to put the nandroid on the stock recovery cause they want the blame on you and not them. shhh, keep it hidden, don't say I told you their secret
General Overview of the Next Options we have.
a. The Download Mode Way
Before going this way I would suggest you see the recovery mode way, if it's not working for you, then go ahead here.
You have four things that you can do (other's I never needed to venture upon)
1. Flash a Recovery -
In case you want to change or update a Recovery or fix/access a Recovery again, to root, complete backup from recovery(nandroid), install new custom Rom, install stock Rom, plenty of options here. Probably the safest option here cause you don't lose your data unless you do something wrong here as to format it. whether you root your tablet or not, install a custom Rom or stay on stock, everyone MUST have a custom recovery, I don't understand why Stock recovery can't have this option as well?
2. Flash a stock firmware package -
in case you are on stock recovery never rooted,
can't reach or can't flash anything using custom recovery,
bootloops(applied in all cases), want to revert back to stock factory state. tab system is behaving weirdly, virus and Trojans attacked or you just want to upgrade or change your droid firmware.
Note Using this method, will result in the loss of all your data stored on the device internal card.
3. Flashing a Bootloader
Generally these are included in every stock firmware pack. if you had a ICS(4.0.4) stock Rom, and the device got an Official JB(4.2.2) update. you must update to that firmware first before flashing any later custom Roms[from kk to M(6.0)], the version which never got released officially. flashing this part separately is very risky and done with utmost care, remember it's your droid heart. don't fool around with it.
3. Flash firmware with pit file -
Warning : this is some high level flashing, it will re partition your device along with the stock firmware. in cases where NOTHING ELSE on the whole Internet worked for you, and you have tried almost everything, only then choose this path with clear mind. make mistake in this, and your tab will virtually turn into a paperweight. if you're not sure you could handle it, please send it for the service centers. this is going to flash every part of the droid's body
4. Flash the 4 files with pit
This is the secret way, where miracles can happen even when there was no hope of recovering yourself.
b. The Recovery Mode Way
Stock recovery - Here You can clear cache, there is nothing much happening in clearing cache, just clearing some temporary files and making you feel like you have got some space cleared out. it's just files that you most probably already used.
data/factory reset and reboot. Easy and simple solution . that does solve some of the problems you face without modifying your device much. so those of you who are afraid to flashing things and ending up on some bigger mistake, you can give this a try, but keep in mind, you will lose all your data stored in the device.
there is apply update from recovery, but that seldom has use in an average android user's life nothing much of a recovery.
Go to download mode way of flashing a custom recovery
or
If you have rooted your tab somehow using framaroot, towel root, baidu or any other app, without ODIN in case you can't connect your tab to the PC with the USB, then you can use flashify app or Kernel Adiutor(the latest one) or any other apps that has the feature to flash img from inside the device OS. you can download a copy of the custom recovery image.(recovery.img) browse in the app and let it do the installation for you.
Custom recovery - Here you have many things that you can do depending upon which recovery and which version you choose. CWM is past, philz is ok, TWRP is awesome. most of the options are common in these 3, but some are really better and fast than the previous ones. we will discuss only one, my favorite TWRP(Respect for the legend CWM though), the process is common on all but twrp is more feature rich.
Click to expand...
Click to collapse
Important files you must have NANDROID BACKUP, STOCK FIRMWARE, PIT FILE, and 4 FILES FIRMWARE PACKAGE, GET them even before you need to search for them
Click to expand...
Click to collapse
Setting Up Everything
Before proceeding Always keep device battery fully charged and NEVER go flashing on low battery. Very Risky. Don't forget.
Always check the files that you are going to flash on your device. generally files will have device model mentioned in their filename.
Be Sure that you don't lose electricity or laptop on low battery while working. the device takes time to update.
Click to expand...
Click to collapse
Things you need to Set up a 'Flashing Environment'
No, I am not going to talk about a flashy party setup
i. PC running Windows 7 and 8 (with 10 I haven't flashed anything yet, but it works.)
ii. A working data cable(some cables are bad and will not detect your device if you see unknown device better get a new one)
iii. Samsung USB Drivers it's much better than having samsung kies on your pc. I would personally suggest from my experience along with many people who have suffered from samsung kies, it's not worth the hassle. ODIN and KIES don't work alongside, so you will have to close.
iv. ODIN 3.10 (download plus instructions as well I used 1.85, 3.07, 3.09 All worked, and so will 3.10. if not, try different ones from Odin 1-85 to 3.07. these links have more step by step and detailed covering what I have left.
v. 7Zip better download this cause it can unpack most of the files.
Press and hold Power and Volume Up(right) button on your device for few good minutes until you see a download mode screen
Connect your USB cable to PC and press Up to Continue. sometimes there could be problem with the USB ports, you should check in all the ports available. avoid USB hubs or the front panel USB in case of PC, don't let a faulty port ruin this for you.
Problem/Failed with Odin? Refer to this thread Good Points here as well.
Click to expand...
Click to collapse
DOWNLOADING AND READING FILES
Believe it, this a very big problem that people tend to overlook
The file you need will look something like these
"P5100XXDMD1_P5100OJVDME1_P5100XXDLL2_EUR.tar.7z"
where
P5100 - Generally the first 5 letters/numbers means a device model number.
XXDMD1 this is PDA which will be 5 letters(much older devices)-6 letters denoting firmware build version.
OJVDME1 is CSC version these just contains regional wise APN, nothing much.
XXDLL2 is Modem version.
EUR is Country Code.
.7z means you need 7zip to extract this file.
Now see these 2 examples here
"S7562XXALJ4_S7562OXXALJ3_S7562XXLJ3_HUN.tar" and "S7562CZNUAMI2_S7562CCHUAMI2_CHU zip"
Sure it's S7562 device but wait the other one is S7562C !!! totally different device firmware. make mistake here and you are sure going to lose.
I Hope you can make out the difference now for every device now.
Now the real file that you need will always be inside a zip/tar/7z the correct format is "P5100XXDMD1_P5100OJVDME1_P5100XXDLL2.tar.md5 "
Remember to extract it and get the md5 file.
Click to expand...
Click to collapse
These are the known best sources
Enter and Download device model on sammobile
P5100 sammobile
P5110 sammobile
P5113 sammobile
P3100 sammobile
P3113 sammobile
*Bump Download firmwares available smart-gsm.net
Download firmwares available easy-firmware.comThe Only reason I am putting this here is while I was searching for genuine websites, I had a very hard time finding through sites that looks nothing else than scams and fakes and rarely had files that I needed and password protected. this websites has ads, but looks organized and for tab series, it had at-least all the firmwares downloading.
PHP:
Yes so, it will take time and require a good internet speed, there are other sites, but I don't recommend them unless they are from good source or sometimes the only option. Options are also available from GSMhosting site as well, its another good community but I feel XDA is much better. still if you have no options. you have to get it somehow. just stay away from the survey sites and bogus ones. specially the blogspot ones.
Recovery Mode Way
Recovering from a custom recovery
Important PartCreating Nandroid Backup - This is the most important thing that you will ever need, and will always regret not having it when you chose this path, should be the first priority.
Getting Inside
Switch off the device
Let it completely shutdown
Hold Power and Volume Down(left button)
This is how it looks saw that backup button? yes that is where you tap first (other recoveries will have different looks, but same "backup" and
This is where you do it . by tapping again or navigating through the volume up and down button in case of older recoveries this would not at all be same, this is the most latest feature rich recovery.
Those Running CWM older builds, won't find the options to select boot, system cache and data and instead there will be just "backup" and backup to external.
CWM by default will Backup boot, system, data, cache partitions. Philz will also do it. But TWRP has better features. although they do the same. You just select system, boot, data and cache. that would be all to recover using nandroid backup.
Now here it depends on what you are trying to do and what would you like to recover from, also depends on what you are comfortable with doing and how much space you can spare. if you have a lot, I would say skip this step and backup all for once.
Click to expand...
Click to collapse
Not Noob Friendly
if you have that same custom Rom zip that you would like to restore the backup of, then there is no need to copy/backup /system partition again, it will save you some space. so you can skip it in that case for TWRP.
if you're only going to modify device kernel - backup boot. or just data if you already have the custom Rom with kernel.
other than that twrp offers what CWM lacked, skip md5 generation during backup well this is a good option and saves some time while backup, on restoring you can also enable or disable it. the purpose of this is simple, md5 is like a security/seal on your backup file, so you don't mess up anything while restoring it on your device. after all you never know when a virus might attack or you might put the wrong files on it. if you are sure about your talents, you can skip it or else it's better to let it generate and verify while restore. CWM has this setup as default.
Now you have one? GREAT! GENIUS!! Now whenever you encounter a problem make sure you can use it like a BOSS.
Restore Nandroid Backup
Enter recovery mode by Pressing Power and Volume Down(left button),
you reach the main screen,
you see a "restore" option and tap it,
you will see folders name starting with the date you made a nandroid backup,
you recognize which one you want by the date and information listed there, and select it. CWM only offered dates, but twrp even offers more detailed info including OS version and Rom name. one more reason I suggest you to use twrp.
In case you want only data to be restored, then you choose advanced restore and check the data and restore. but before doing this part make sure you are not restoring conflicting data or system or kernel with incompatible versions.
you can't restore a data backup from a Jellybean Rom and put it on a custom Rom based on Lollipop, neither a kernel from Lollipop to jellybean.
Data should only be recovered on the same Rom you took the backup from.
In case the custom Rom developer rolls an update of the same fixing issues,(not some major changes) then you can in some cases think of getting this worked out smoothly. This is called a "dirty flash". which is the reason why sometimes users experience problems running certain Roms, even when they are good and stable Roms. So before complaining to devs make sure you follow the clean install method.
Note: System and data most of the times will cause problems. Kernels are not meant at all to play with. they are the biggest source of bricks.
Click to expand...
Click to collapse
Wiping Part - Steer Clear the problems away
this is where wipe takes place[PIC]
here are the wipes options on a custom recovery
Factory reset - Wipes cache, dalvik, data/ excluding your media part on the internal drive.(your pics, videos are safe)
this will generally clear you problems if they are not some big issues. but you will lose the apps and contacts messages stored.
Advanced wipe - Format system
you can try to do this first if you don't want to lose your data while troubleshooting.
format system if you're facing issues with the files on system partition, but remember to install the same Rom you had earlier. if you had stock, you will need a stock Rom zip not to forget keeping the file ready beforehand on the external SD card.
Beware while navigating in advance wipe menu, never wipe in a hurry, never drink and wipe, never take eyes off here, cause you might end up touching external SD card, USB-OTG, internal storage and lose your precious data
Format data - this wipes the data partition
problems arising from the data partition side could be solved here, but you lose your precious data on the internal and get rid of the bad, virus, trojans, trouble making apps.
How to perform A CLEAN INSTALL when you are going to update to a new Rom?
Factory Reset and Format System, Format CACHE
or
Format /System, Format /Data, Format /Cache, WIPE Dalvik Cache, Factory Reset.
This will Surely Solve Some Great & Average Problems of Day to Day Flashing.[/B]
Click to expand...
Click to collapse
What's a Dirty Flash then?
Format System, without Deleting Data partition. before doing this, please do a nandroid backup in case you mess things up. if not, format system again and flash the Rom that was initially running with that data.
Click to expand...
Click to collapse
Now Comes the Installing part
Installing Menu
You download a copy of a custom Rom or stock Rom, after following the developer's thread, reading through it's bugs and reviews. you don't want a unstable or alpha Roms.
There would be installing process explained on that thread follow it and always make sure that inside the zip file it contains a meta-inf and system folder with boot.img) always look inside before going to flash, don't trust me, don't trust anyone. although
if you tried to flash a firmware zip file containing a .img file, without Meta-Inf folder, it won't flash. cause the custom recovery needs instructions from updater-script. Now, I know this was mostly going on like this before, but now with latest custom recoveries, (twrp) you can even flash .img files without needing a zip.
You perform a Clean Install wipe stated in the wipe section above
Reboot to Recovery(Don't select reboot to system, there is no system after clean wipe)
You browse through the files list and external storage,
Find that zip file and
Swipe or press or touch to flash it.
You wait for it to complete the process then
You can wipe/cache/dalvik and reboot or you just reboot. depends on what you choose "clean install" or "dirty install".
You want to report any errors while flashing? you are free to do so on the Rom thread, don't expect me to solve those cases.
If all went well, reboot to system and your tab should be up running again. if not refer to the Download mode Way.
The Download Mode Way
The Download Mode Way
1. FLASH A CUSTOM RECOVERY
Find the recoveries in their respective threads. For P51xx and P31xx Recovery thread others can look in their respective device sections, XDA has development thread of most of the Samsung devices and people do post there.
it should look like this on your address bar
"http forum.xda-developers.com / galaxy-tab-2 / general"
xda website /__ (devicename)/ (sub-forum)
(development) OR (/general) section
You can always google it too.
remember you will need a recovery.md5 that will be inside a zip file extract from it.
Always check whats in the archive then go the recovery mode way, it should be .md5
Sorry I have not put up detailed step by step process here because my guide is covering a lot of things already and this is something each device specific, refer to this For General step by step instructions with pictures, this has very detailed process.
Click to expand...
Click to collapse
2 FLASH A STOCK FIRMWARE
These package contains files needed to update or revert to the same position where it was shipped to your country along with your android device. you can find all Samsung device firmwares released from all parts of the world, and yes, you can flash firmwares of other country/regions from the sammobile site just stay away from the carrier specific firmwares(unless you are on one) that should be used for the same specific carriers device only they are married to the carrier company and probably won't let you have your own ways with others.
You should also remember not to downgrade a stock firmware once you have upgraded, that will surely create problems
Run Odin as administrator
Browse PDA/AP and find the firmware .md5 file
This is how you should see on your ODIN screen. always be very very careful to uncheck the Re-partition. it's unchecked by default.
Click to expand...
Click to collapse
Code:
The yellow column/(Blue for other versions) means
your device is detected by the PC.
If it's not lit, you have messed up USB drivers
still not uninstalled kies Completely or
not connected the device properly.
try changing to different USB Ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press Start
Wait for the process to complete and let the device reboot from download mode
Remove cable when you see PASS written with green above the Yellow/Blue com port.
PHP:
Most Problems are solved here when you see success/PASS.
Except one The emmc bug. Replace the internal emmc, or J-TAG or
mysteriously something else done by professionals.
[*]if it shows failed, see if you can go to recovery mode and clear data, check Mount/Unmount System, data
Click to expand...
Click to collapse
if it still says failed, the downloaded file is corrupted, wrong Odin version(try with different Odin versions) you have flashed wrong device files which has messed up the partition table of your device. refer to other ways.
Threads with good post for the tab 2 series these contains firmware links, guides, recoveries, Roms list, kernels pretty much everything.
All about P51xx
All about P31xx
Click to expand...
Click to collapse
3. FLASH A BOOTLOADER
First ask yourself why you would want to do this?
Be extra careful with this part, if you have already flashed a updated firmware, you don't need this part.
Those who are using old stock firmware, please flash a stock last updated firmware. you won't need to do this.
Those who did not follow the above two, so it's now unto you, this a risky thing, you have been advised you are going further yourself
Those who are experiencing problems that are not solved even after most of my other instructions here, then it's onto you to decide you want to try this too or not. this could solve problems when device is in serious condition, after all it's the heart partition and remember no downgrades in this once you upgrade. thats it. this could seriously create problems, including bringing back the emmc issue as well.
Refer to this DETAILS AND INSTRUCTIONS to FLASH A BOOTLOADER for SAMSUNG TAB 2 SERIES follow safely by @Joery360 other users please be careful with these files and don't go on flashing others files? okay. Great!
Click to expand...
Click to collapse
4. FLASH FIRMWARE WITH PIT FILE
Wait!! You are sure that you want to try this part? this is the point of no return. Whatever happens to your device by following this guide, good or bad, it's your own responsibility. You can't blame me for it. so be sensible, if you're not sure please let this be done by someone who has the experience of dealing with this kind of stuff.
Now pit files are some serious files, they contain information about your device partition and they help flash erase and rewrite files on their correct partition, so better not take a wrong file, sometimes you have the same device but different internal space, so don't end up choosing a pit file for a 8 GB variant on your 16 GB variant of device, in that case your device will end up using 8gb only, or worse if it's other device, it might never boot up again.
Always remember don't flash pit files ever without a firmware file in place.
Download Pit files for Samsung tab 2 p51xx p31xx series
Click to expand...
Click to collapse
Run Odin as administrator
Browse PDA and find the firmware .md5 file
Browse Pit and select the pit file (reminder : file confirmed?)
Make Sure Re-partition is checked cause we are using Pit File to re partition again
Never flash a Pit file without a firmware placed in PDA/AP
Click to expand...
Click to collapse
Press Start
Wait for the process to complete and let the device reboot from download mode
Remove cable when you see PASS written with green above the Yellow/Blue com port.
Click to expand...
Click to collapse
if it shows failed while flashing, you did used correct files, right? after this if there is still a download mode running on your device. try the special case files.
this has happened with me on a unknown MTK device, the pit file was slightly different from the original one on device, so it failed, but that was at the start before it could flash. I did somehow managed to flash that different pit file, just lost some disk space. cause I used a lower variant pit but it got the device running up again.
The device takes a long time to boot while it's updating firmware, so you are required to have sufficiently charged battery, Take no chances here.
if even after a successful flash with Odin, you face problems, then that's a emmc bug case. motherboard replacement or emmc replacement, or tab replacement. nothing else.
5. FLASH PIT WITH 4 FILES FIRMWARE
Find the repair firmware files at this Website
it has the 4 files for most of the devices including the Tab 2 series
Instructions for using these 4 files, however please note that the only difference would be the ODIN versions, cause device needs specific ODIN version, some can flash all.
this is the only way, that I have seen working for numerous devices and it is most successful one among all options to recover an almost bricked device, on which you have tried everything.
For other devices
Find them here
Click to expand...
Click to collapse
you'll find these buttons on every post.
it's better to notify a user when you're asking that user a question or use @username of the user for mentioning in your post, that will give in a notification for you.
I think there could be more, i know it's already lengthy but who knows?
As I begin rooting process for my J710, and realize that the J710 is still fairly new so I thought I write this post and share my notes with everyone to help your transition goes smoothly.
First thing first, some safety tips.
Know your stock firmware. In this case SM-J710 is the min requirement
Have a stock firmware file downloaded on your PC. There's nothing for US right now, but J710 is not region lock so it matter not which version you chose on Sammobile
Make sure your current and new version match up as much as possible. So J710 should be the first 4 that need to match
Created a Folder on your PC for J710, and organize everything in one place. Samething with phone microSD card
Try to make a habbit out of keeping track of your process. It will help you out alot when things goes wrong and are looking for help. Or if you need to go back and see where you make mistake. Especially useful if you are new at this. Dev can't help you if you don't know what you did yourself.
10min rules. Always give the phone minimum 10 min to boot the first time before you disconnect the battery. Sometimes it just take longer, but 10min is a good start for first booth.
TOOLS you will need.
ODin newest is 3.10, but other version will be fine
Stock USB cable that came with the phone. This will save you the hassle of downloading USB installer, and it makes data transfer from ODin to phone alot safer.
TWRP for J710. right now it's only beta phase, but I beleive its 3.02.
Superuser zip files to be flash upon successful installation of TWRP
BACK UP DATA: With the app you can use ES explorer and back up to you microSD.
With the phone, just plug in to your computer, Copy the phone folder, and create a subfolder on your PC and name it System then paste everything onto that folder. After rooting is done. Re-install the app again, then copy your system folder onto the new system folder of your root phone. Restart your phone, and all your previous login and layout will there the way you left it.
Technically you only need to copy the ANDROID & BACKUP folder for your apps. But the above methods will back up all your media along with apps info, and it alot faster.
I recommend using ES explorer because it will does all the modification for without having to go through TWRP once you have rooted enable. Just enable root, and whatever you want to modify, place it in the correct folder of the phone SYS. Reboot and its done. You won't have to go through TWRP and risk bricking. You can save your modify rom in a zip file and share up here. It like being a developer for dummies.
So before you begin. The number 1 thing you should have is the firmware. SM-J710 from Sammobile. With that being said, I have found 2 links for rooting. They are both similiar process, but the one from XDA is for SM-J710F. and the link from Androidinfo is for SM-J710MN. Depend on your choosing you need to have a backup firmware from the method that you chose.
Now that you have the stockfirmware, and your phone is not the F or MN series. Flash the stock firmware of the method that you chose, and go with the rooting process for that method. here are the links:
XDA Video tutorial http://forum.xda-developers.com/galaxy-j7/how-to/video-root-samsung-galaxy-j7-sm-j710f-t3401790
XDA thread http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736
Androidinfotech: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-j7-2016-sm-j710mn.html
This rooting method is working mostly with ODin, odds of you bricking your phone is about the same as winning a lottery. With that being said, make sure everything that you plan on flashing is from J710 and you should be fine.
The J7 is more like an opensource phone from Samsung. It does not have a lot of restriction like the other models such as S series. But you are working with a beta version of TWRP so it might not work out the first time around. If that is the case, flash a different firmware model or wait for a stable version. It not the end of the world if you phone is rooted.
Backtrack to beginning: Flash the stock firmware to begin the process again. WIPING DATA before any process is always a plus.
using ODin: Flash Firmware on "BL" for new version, i forgot which slot it is for the older version
Flash: TWRP and SU on "AP" slot for new version
INTERESTING FACTS: I ran across a thread online that mention backing firmware via Odin is possible. Hopefully someone here on XDA might have an idea on the methods, if such a thing exist. I thought I share this. If only I remember where I ran into that post.
Last notes: During the rooting process, I recommend letting the phone reboot completely as you progress through each phase of the process. the reason for this, is so it will help you identify if the TWRP is not installing, or the kernels is incorrect, or the SU.
Your phone will bootloop if TWRP does not optain write priviledges.
Your kernels will always install, but if TWRP does not have privileges the phone will not boot.
Should you were able to get TWRP, and Kernel to install properly, but fail to get SU to install. You gonna have to play around with other SU version. I would do a TWRP back up should I was able to get it to install, before moving on to SU. This way you won't have to start from the beginning if it doesn't work out.
With that, I leave the rest in your hand. Goodlucks
Vi3tDroidz said:
As I begin rooting process for my J710, and realize that the J710 is still fairly new so I thought I write this post and share my notes with everyone to help your transition goes smoothly.
First thing first, some safety tips.
Know your stock firmware. In this case SM-J710 is the min requirement
Have a stock firmware file downloaded on your PC. There's nothing for US right now, but J710 is not region lock so it matter not which version you chose on Sammobile
Make sure your current and new version match up as much as possible. So J710 should be the first 4 that need to match
Created a Folder on your PC for J710, and organize everything in one place. Samething with phone microSD card
Try to make a habbit out of keeping track of your process. It will help you out alot when things goes wrong and are looking for help. Or if you need to go back and see where you make mistake. Especially useful if you are new at this. Dev can't help you if you don't know what you did yourself.
10min rules. Always give the phone minimum 10 min to boot the first time before you disconnect the battery. Sometimes it just take longer, but 10min is a good start for first booth.
TOOLS you will need.
ODin newest is 3.10, but other version will be fine
Stock USB cable that came with the phone. This will save you the hassle of downloading USB installer, and it makes data transfer from ODin to phone alot safer.
TWRP for J710. right now it's only beta phase, but I beleive its 3.02.
Superuser zip files to be flash upon successful installation of TWRP
BACK UP DATA: With the app you can use ES explorer and back up to you microSD.
With the phone, just plug in to your computer, Copy the phone folder, and create a subfolder on your PC and name it System then paste everything onto that folder. After rooting is done. Re-install the app again, then copy your system folder onto the new system folder of your root phone. Restart your phone, and all your previous login and layout will there the way you left it.
Technically you only need to copy the ANDROID & BACKUP folder for your apps. But the above methods will back up all your media along with apps info, and it alot faster.
I recommend using ES explorer because it will does all the modification for without having to go through TWRP once you have rooted enable. Just enable root, and whatever you want to modify, place it in the correct folder of the phone SYS. Reboot and its done. You won't have to go through TWRP and risk bricking. You can save your modify rom in a zip file and share up here. It like being a developer for dummies.
So before you begin. The number 1 thing you should have is the firmware. SM-J710 from Sammobile. With that being said, I have found 2 links for rooting. They are both similiar process, but the one from XDA is for SM-J710F. and the link from Androidinfo is for SM-J710MN. Depend on your choosing you need to have a backup firmware from the method that you chose.
Now that you have the stockfirmware, and your phone is not the F or MN series. Flash the stock firmware of the method that you chose, and go with the rooting process for that method. here are the links:
XDA Video tutorial http://forum.xda-developers.com/galaxy-j7/how-to/video-root-samsung-galaxy-j7-sm-j710f-t3401790
XDA thread http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736
Androidinfotech: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-j7-2016-sm-j710mn.html
This rooting method is working mostly with ODin, odds of you bricking your phone is about the same as winning a lottery. With that being said, make sure everything that you plan on flashing is from J710 and you should be fine.
The J7 is more like an opensource phone from Samsung. It does not have a lot of restriction like the other models such as S series. But you are working with a beta version of TWRP so it might not work out the first time around. If that is the case, flash a different firmware model or wait for a stable version. It not the end of the world if you phone is rooted.
Backtrack to beginning: Flash the stock firmware to begin the process again. WIPING DATA before any process is always a plus.
using ODin: Flash Firmware on "BL" for new version, i forgot which slot it is for the older version
Flash: TWRP and SU on "AP" slot for new version
INTERESTING FACTS: I ran across a thread online that mention backing firmware via Odin is possible. Hopefully someone here on XDA might have an idea on the methods, if such a thing exist. I thought I share this. If only I remember where I ran into that post.
Last notes: During the rooting process, I recommend letting the phone reboot completely as you progress through each phase of the process. the reason for this, is so it will help you identify if the TWRP is not installing, or the kernels is incorrect, or the SU.
Your phone will bootloop if TWRP does not optain write priviledges.
Your kernels will always install, but if TWRP does not have privileges the phone will not boot.
Should you were able to get TWRP, and Kernel to install properly, but fail to get SU to install. You gonna have to play around with other SU version. I would do a TWRP back up should I was able to get it to install, before moving on to SU. This way you won't have to start from the beginning if it doesn't work out.
With that, I leave the rest in your hand. Goodlucks
Click to expand...
Click to collapse
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Thanks
Sent from my SM-J710MN using Xparent BlueTapatalk 2
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Update: A new update was released for the Prime model, V6.6, which replaces the preloader and completely breaks SPFT. If you unlocked your bootloader (so you can use fastboot) in any capacity before taking that update, there may be hope for you yet, but as of right now V6.6 is unsupported. Update: If you used this method to safely* take* the V6.6* update*, this will still work.
Update: I just checked the stats, and this has been downloaded more than 3 thousand times. I never thought my humble little conversion guide would help out so many people. I have also added a new mirror at [REDACTED], so anyone in North America who was having trouble with the Europe mirror, give that one a shot. It should be faster! I have updated all links in the guide to use the new North America mirror, and added a separate Europe mirror link after each link.
Hello! This is a tutorial for converting the Amazon Prime Edition BLU R1 HD to the OEM BLU version. This will overwrite the relevant partitions on your Amazon version of the device with the non-Amazon version. The physical model number on your device will still be a tell (obviously), but besides that, there will be no way to tell your device apart from the regular model! You can also use this method to convert non-Prime to Prime version, and undo OTAs or system modifications. This will restore a 100% out of the box image from either edition on your device.
This will work if you have software version...
V12
V6.1
V6.4
V6.5
SAFE V6.6 FROM THIS THREAD
This will NOT work on software version...
V6.6
The V6.6 update brought a new preloader that breaks our ability to use SPFT. I am currently working on ways to reverse the damage, but as of right now, there is no way to convert (or downgrade) from software V6.6
You can use this on any 16/2 R1 HD with supported software version to...
Convert to the non-Prime OEM version
Convert to the Prime version
Remove ads (via conversion to non-Prime version)
Unroot
Downgrade to V6.1
Downgrade to V12
Undo system alterations/tampers
Restore the system image to the way it was when you first opened the box
Unbrick a device (if bricked because of bad system/recovery/boot image)
There are a handful of reports about this working flawlessly on the 8/1 model as well. I have not personally tested this, so there is still some risk factor.
This only overwrites the system, recovery, and boot partitions. Any other partitions that have been altered will not be restored. In most cases, other partitions should not have been altered, so this is not a concern. I have a full system backup of all partitions, but there is currently evidence to suggest that it is not safe to flash all of the partitions, so I will not release that backup until more is known.
You *should* be able to safely pull this off without wiping your data. This does not require your phone to be rooted or have any other modifications. You can pull it straight out of the box and do this process! If your phone is rooted, you'll lose it. This will make your phone EXACTLY like the non-Prime version comes out of the box! You can also convert a non-Prime device (or a converted Prime device back) to a Prime device using the same method, but I'm not exactly sure why you would want to. I did this all on Linux, but the Windows should work fine too as long as you have drivers dealt with. If you don't have drivers dealt with, I'm not your guy. I'll just tell you to use a better operating system. You'll also need an archive program that can deal with tar.gz files, because that's how my computer zipped them.
And the standard disclaimer: If this bricks your phone or makes it become sentient and plot with other sentient phones to murder your entire family, it's not my fault. That's all on you, buddy.
Ok, without further ado, on to the tutorial!
First, you need these things. Some of the files are quire large, so it might take a while to download:
You'll need the latest version of Smart Phone Flash Tools, or SPFT for short. You can download that from this site, or from [REDACTED]. Please use the latest version for your OS.
You'll need to download the system image. If you're converting to the non-Prime version, [REDACTED]. If you're converting to the Prime version, [REDACTED]
You need the scatter file. This will tell SPFT where the partitions are. This is the same for both variants, so just download [REDACTED]
Once you have those things, you can start actually flashing your phone:
Power your phone completely OFF! This will not work if your phone is powered on. SPFT writes directly to the phone's memory, bypassing all security measures the phone has, so it requires the phone to be completely OFF to get safe and exclusive access to the memory. DO NOT PLUG IN YOUR PHONE YET!
Extract SPFT into a folder on your computer. If you can't figure out how to do that, please stop tinkering with your phone. It's only a matter of time until you break something.
Extract the system image into the same folder you put SPFT in. The three files (boot.img, recovery.img, system.img) should be in the same folder as all the other SPFT files, including the binaries.
Run SPFT. On Windows, simply double clicking the SPFT executable should do the trick. On Linux, you must run the flash_tool.sh script as root. Open a terminal emulator, cd to the SPFT folder, and run `sudo ./flash_tool.sh`. If you recieve an error about permissions, run `chmod +x flash_tool.sh` and try the first command again.
Go to the Download tab in SPFT and click the Scatter-loading button on the far right side. DO NOT click the Download Agent button. When the file picker dialog pops up, find and open the r1hd-spft-scatter.txt file you downloaded earlier.
You should see a list of partitions. Only three of them (boot, recovery, system) should be checked, and the location should point to the files you extracted from the tar.gz file earlier. If this is not the case, double-click the location block of the boot, recovery, and system partitions, and select the boot.img, recovery.img, and system.img files from your filesystem respectively. After selecting the files, the boxes should check themselves.
From the dropdown in the upper left of the partition list, make sure Download Only is selected. Any other option could damage your device.
Click the Download button in the upper left.
While your phone is OFF, plug it into your computer with a data safe USB cable. The cable that came in the box from the factory is ideal, but any good quality cable will work just fine.
SPFT should start overwriting your phone. If you receive an error from SPFT, unplug your phone, close SPFT, and repeat steps 4 through 9. The whole process takes about 10 minutes, after which you should see a window with a large green checkmark. Once you see that window, you can safely unplug your phone and start it up. You're all done!
And as a bonus, I've also included a guide for unlocking the bootloader, getting custom recovery, and rooting the device after you've done this in post #2. That makes this your one stop shop for getting a brand new Prime phone out of the box!!
HUGE THANKS TO @mrmazak FOR THEORIZING THIS METHOD AND GETTING ME THE NON-PRIME SYSTEM IMAGE TO USE!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
{OUTDATED}[GUIDE][OEM][Stock] Bootloader Unlock, TWRP, and root!
Update March 8 2017: As you can probably tell, this is very old. I have not worked on the device in several months and I have no idea if these methods are still safe. Please proceed with caution. I will be using one of these on a daily basis in the near future, so I probably will get back into development, and hope to release new content for the phone to help out the community. Please accept this as an official warning that the following is probably out of date and that you should be very careful should you decide to try it. The original post in it's entirety is spoilered below. You have been warned.
Ok, now you've converted your brand new Prime phone to the non-Prime version. How do you unlock this sucker? The conversion process actually unlocks the standard unlock method from the factory, so it's VERY simple! No hoops to jump through or anything. You'll need adb and fastboot. You can get those as part of the official Android developer kit, your distro's repos (on Linux) or Homebrew (on Mac). Of course, this guide works for the normal non-converted non-Prime version as well. This WILL wipe your phone, so make sure you back up any important data before doing this.
This guide is for the OEM (non-Prime) version. If you have the Prime version, convert it to OEM using the guide above BEFORE doing this guide.
The standard disclaimer from above still applies.
This guide is broken up into two parts. Unlocking the bootloader, and rooting the phone. If you are preparing to install Magisk, do the bootloader unlock, skip the rooting part and move on to the Magisk guide. You do not need the files above if you are only unlocking the bootloader. If your bootloader is already unlocked, skip the bootloader unlocking part and skip to rooting the phone. If you are preparing to install Magisk and your bootloader is already unlocked, you shouldn't be here. Also please note that the bootloader can sometimes re-lock itself after completing a conversion/restore from the guide above, especially to/from the Prime version, so if you're not sure, play it safe and re-unlock your bootloader.
Part 1 - Unlocking the bootloader:
Boot up your phone. If you haven't already gone through the initial setup process, go through it. The bootloader unlock process will wipe your phone, so skip as many questions as possible so you don't waste your time.
Open the Settings app, go to About device, fine the Build number (it's toward the bottom), and tap on it 8-10 times (until it says you are now a developer. If it says there's no need and you're already a developer, you can skip to the next step)
Go back to the main Settings menu. You should see a new option where About device used to be, Developer options! Click on it.
Toward the top of the long list of developer options, there is an option called "OEM unlocking". If it's switched off, switch it on. If it's switched on, switch it off and back on again. You may get a warning saying that device protection features won't work. Click Enable and proceed. You may also be prompted to enter your password/PIN/pattern lock if you have one.
Scroll down a little bit to reveal USB debugging. Switch it on if it's not already.
Connect your phone to your computer using a data safe cable. Do not disconnect it until the very end.
On your computer, open a terminal emulator (or Command Prompt with ADB access) and run `adb reboot bootloader`. If you get a message complaining about keys or authorization, check your phone. There should be a window asking for permission for your computer to access the device. Allow it and run the command again.
Your phone will reboot into fastboot mode.
On your computer, run `fastboot oem unlock`. On the phone you will get a warning message talking about the implications of unlocking the bootloader. Press Volume Up to accept them. If everything goes smoothly, your bootloader should now be unlocked. You're not ready to flash quite yet! Flashing at this stage WILL brick your phone, so it's important that you continue following the guide carefully.
On your computer, run `fastboot reboot`. Your phone should reboot anywhere from 3 to 5 times. If it reboots more than that, your phone is bricked and you need to start again by following the guide above again.
Once Android starts up again, you should see the setup wizard. Your bootloader is now unlocked!
Part 2 - rooting the phone:
BEFORE YOU PROCEED: If you want your phone to be encrypted AND rooted, it's important that you unlock the bootloader using the steps above first, then use the encryption APK to encrypt your phone BEFORE installing TWRP and rooting your device. This device is an exception to the general rule of flashing TWRP first and then rooting afterwards. Repeat, if you want your phone encrypted and rooted, unlock the bootloader FIRST, then encrypt SECOND, then flash TWRP THIRD, and root your phone LAST.
This is the guide for rooting the actual phone. You must unlock the bootloader using the steps above before doing this part.
First, you'll need these things on your computer.
The TWRP image for the R1 HD. You can download [REDACTED]).
A copy of the latest SuperSU zip from Chainfire. You can get it from the official forum post, or Chainfire's website.
Linux Users: On Linux, you must add `sudo` to the beginning of all fastboot commands, because most Linux distributions will not give you enough access to the hardware without being root.
And finally, the guide:
Hold Volume Up and Power until the phone turns on with the boot menu. Once the boot menu appears, use the volume keys to scroll to [Fastboot Mode] and press the power button to select it. It's the middle option.
On your computer, cd to the folder where you downloaded twrp-3.0.2-1-r1hd-lopestom.img and do `fastboot flash recovery twrp-3.0.2-1-r1hd-lopestom.img`.
On your computer, do `fastboot boot twrp-3.0.2-1-r1hd-lopestom.img`.
Once TWRP boots up, dismiss the prompt about mounting the system, go to Reboot, then choose Recovery. Your device will reboot back into TWRP. I know this step seems odd, but just trust me.
Make a backup if you want. It's not a bad idea, but seeing how you just unlocked your bootloader so your data is gone and we have the images in case you somehow brick the system, I doubt you actually need it.
In TWRP, go to Advanced, then ADB Sideload. Slide the confirmation slider all the way to the right to confirm.
On your computer, cd to the folder where you downloaded SuperSU and run `adb sideload [SuperSU-zip-name.zip]`, replacing the last argument with the name of the SuperSU zip you downloaded, of course. If your computer says "waiting for device" for a long time, cancel with Ctrl+C, run `adb kill-server`, then run the first command again but with `sudo` in front this time.
Reboot the phone. If everything worked correctly, you should now have a rooted phone with SuperSU, bootloader unlocked, and custom recovery! Yay for cheap phones!
As always, if you have any questions, just ask in a thread reply or send me a private message on XDA. And by the way, hit the Thanks button in the lower right corner of the post if my guide helps you. It motivates me to keep this up to date and write more helpful guides. If you feel like giving me even more motivation and help fund future development, [REDACTED].
reserved 3
reserved 4
reserved 5
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
abs0lute said:
Can you verify the image you uploaded for the non-Prime version? I'm getting unexpected EOF errors when extracting in Windows using 7Zip and TarTool, and I'm also getting an "operation not permitted" error when extracting using the built in Archive Utility in OS X.
Click to expand...
Click to collapse
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
ColtonDRG said:
Yeah, that's because the image isn't fully uploaded. My internet is very slow, so it's taking a while to upload. Sorry about that. I was hoping it would be finished by the time I finished writing this, but alas, nope. I will have all files uploaded by tomorrow, along with .md5 files so you can verify the checksums, so come back then. Again, sorry. I guess I should have posted this _after_ I got those uploaded. Oh! And I have North America mirrors coming within the next couple months. It seems a little oxy-moronic to host files for a US only device on an EU server, but unfortunately, servers in the US are significantly more expensive.
Click to expand...
Click to collapse
No problem - thanks for your work on this!
abs0lute said:
No problem - thanks for your work on this!
Click to expand...
Click to collapse
Just finished uploading the non-Prime version. I will start the other upload before sleeping and update the post removing the warning when I awaken, assuming everything has gone well. You're free to attempt a non-Prime conversion now. Just don't do it the other way around yet.
Sent from my LG G4 using XDA Labs
Can't wait to give this a shot. Well, at least after someone else reports success first...
followed post 1 convert to non prime steps on windows, did not do the bootloader unlock steps.
phone booted up ok, followed by android is upgrading x of 37.
phone working and no ad's on lock screen
the amazon apps are still there but appear to be disabled, causing errors at first boot.
disabled or uninstall the apps. - used cleanmaster
everything seems ok now
Hello, I have now finished uploading the files, so you can now safely flash away! Enjoy! @abs0lute
bupkis said:
Can't wait to give this a shot. Well, at least after someone else reports success first...
Click to expand...
Click to collapse
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
ColtonDRG said:
I report success. Of course I did everything in the guide here before posting it. I'm not irresponsible. It's completely safe. I just finished uploading the files, so please go ahead and give it a shot.
Click to expand...
Click to collapse
ok, away we go! :laugh:
When I try to download the scatter file it just opens the file in a new browser window.
>nevermind, figured it out...success!
...on to bootloader unlock, TWRP, root...
bupkis said:
...
When I try to download the scatter file it just opens the file in a new browser window.
...
Click to expand...
Click to collapse
Yeah, that's a problem with my server configuration. I'll fix it later. For now, you can save the file by opening it in a browser window and pressing Ctrl+S
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
bupkis said:
I have completed the process successfully-TWRP, root, no ads but do still have all the Amazon apps so something is screwy but not the end of the world.
Click to expand...
Click to collapse
Nope, it's not screwy. The non-Amazon version does include a lot of the Amazon apps. You can uninstall some of them the normal way (they're pre-installed user apps), and others you can either disable or uninstall using your favourite system app remover.
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
When I try to load the scatter, SPFT says "Error: Initializing scatter file failed. Please check the name of scatter file which you load is legal." I downloaded it from both the primary link and your mirror, same error. Any ideas? Thanks.
EDIT: Looks like I downloaded the oldest version, not the newest version of SPFT. Whoops! I'll leave my mistake on here to help others who may assume the first link is the right one.
notfix said:
Anyone else missing Encrypt section in Settings > Security after converting to non-prime?
Click to expand...
Click to collapse
It is missing. How peculiar. I will attempt to implement a workaround in a little bit. Sorry about that.
Update: The Encryption activity exists on the phone, we just can't get to it from the settings menu. You can launch it by manually launching com.android.settings.Settings$CryptKeeperSettingsActivity using your preferred method for launching arbitrary activities. I will release an app that will launch this activity for you ASAP!
This is probably in the wrong section and I'm very sorry as I'm new to this forum and posting.
BUT! I've made a video and this tutorial to help others just fine their way around here I guess.
https://www.youtube.com/watch?v=K7eqUkueyyw&feature=youtu.be
How I Flashed My Note 4 Back to Stock! And then Root with Magisk and Having Working Mods or Some Minimal Extras!.
Just a tutorial for new people or in general to just felt like a help in need of doing this process.. and haven't seen anyone else post in exact details.
I haven't had any problems after I've done this and i will be posting a follow up video soon. .. But Yeah, I hope this helps everyone. :/
===
So, first off I'd have to say thank you for the support everyone, now let 's get down to business.
Also, please take this to a high acknowledge as this WILL! ERASE!! EVERYTHING!
Off your device, I'm not responsible for your misguided actions.
So, PLEASE! PLEASE! PLEASE! BACKUP! YOUR PHONE!
Let's Start Shall We
==Steps====
(... I'm Using Windows 10 64Bit ...)
1st.) DRIVERS!
Make Sure that you have Installed the Drivers for your Device.
the "SM-N910P" Varient.
What I have installed is "SAMSUNG USB Drivers for Mobile Phones - v1.5.63.0 "
You can find this on the sam-mobile website, or you're own provided sources. Google.
2nd.) BACKUP!
So, we're at the stage where we need to back the phone up.
After you had finished install driver's it's important that you Restart YOUR PC.
Just in case, so that you're able to Connect your Device and View your Files!.
I Typically Connect my phone either Usb 2.0 or 3.0 doesn't matter,
Allow Permissions to Access My DATA and then I just backup my "Internal Storage" by going inside and selecting everything
and then pasting it Onto a "New Folder" On My Desktop.
I Mainly Copy over everything that's listed on my device, except the folders called
.Android and Com.Facebook.Orca Folders.
As that's just a folder just for the app to function or the app data,
which doesn't even consist of anything from your picture or videos. Just app stuffs, rendered as useless.
After wards, I Highly recommend Downloading an app called "Easy Backup & Restore"
AS this app WILL! actually backup your Contacts, SMS and call Logs and even MMS in the text per contact.
All you have to do from there is set a save location, Allow the app to think it's the stock messages app, back it up.
it saves it as an XML File and then afterwards. Your Done, and just tap the button to switch it back to normal.
!!!!You Might need to back this file on your PC ASWELL! or else you will lose your texts in general!!!!
Moving Forward....
3rd.) Triple Checking!
AS a Side "Note" no pun intended.....
THIS WILL VOID ANY WARRENTIES! you have for your device.
Unless you had bought this from Online or Secondhand, like me
From Ebay for 120$ Used. Then You can bypass this part. as this step isn't covered by your
Mobile Insurances plans like "TEP". All they would suggest is to grab another phone or if you're lucky.
Like my old phone an S6, i literally tried flashing the OTA and it wouldn't boot, but that's all they know.
EFS issues..lol.... you know what i mean.
4th.) FLASHING!
Now! that you don't have any warrenties and have backed up your phone for sure, Made sure you remeber all your logins and passwords.
I"d Highly suggest to Safely Remove your SDCARD!, so it won't get formatted by accident, I'd know this.
Afterwards, you will Likely make sure your phone is at least 30% or 50% or Recommended 100% Battery Life to Coninute the process.
Without sudden power loss failure.
Another thing make sure you go into your "Settings" and then Select "About Phone" And then Tap the
"Build Number" Several of times until it says it's activated, Afterwards go Into "Developer Options" and select
"OEM Unlocking" so you won't have that nasty FRP LOCK issue. if that's the case. if it's not there then no need to worry.
AS soon as that's Completed. You're All Set!.
5th.) Let's Flash Baby! ;D
So, for this step you need to download these Files, "Odin" STOCK Image/Tar and Custom Recovery!.
I'm using "Odin3 v3.10".
and Download The Stock Image or in this case ".Tar" file.
I'm using, "N910PVPS4DPJ1_N910PSPT4DPJ1_N910PVPS4DPJ1_HOME.tar" for the day.
and Also Team Win Recovery Project "TWRP" V3.1.1.0 .img or .tar whatever you prefer for this one.
///Note ////
What I usually do but isn't recommended is, when This file is done download from one of your own sources.
I'd Extract the same label file but with ".rar" at the end of it with Winrar
and then GO INTO THE EXTRACTED FOLDER, look for the file and then I'd erase the extension "..md5" and keep
the whole "..tar" extension instead, to "SKIP" File Intergrity, from Odin. Makes flashing easier for me, Haven't had any problems.
///////////
Anyways, you would then Start Up ODIN with ADMIN RIGHTS, then Select the Label "AP".
Afterwards Select that TAR file you just extracted.
Then, Make Sure "Auto-Reboot" Is Selected and "F. Reset Time"... Don't Check the other labels, please.
Unplug Your Phone (if it's still connected and done being backed up and what not)
Restart the Phone into DL MODE or Download Mode,
via Powering Off the Phone or Taking out the Battery, Putting it back in.
Then Pressing Vol Down, Power And Home Buttons! Simultaneously! You Shoud Feel 1 small Vibrate and then let go of those buttons.
You should then see a Continue or Restart Phone text.
You would then select Continue, And then It should Prompt to a new screen saying "Downloading..."
Now at this point you may connect your Device, Your PC should be Installing New Drivers, wait for that to be Done.
And or By Then if it's already installed, Check back with Odin to See if anything's Listed under "ID:COM"
Mine was Com 3, Highlighted Baby Blue.
After you see that, go ahead and say bye bye and select "Start" to Flash your phone back to Stock!... this should take roughly 10 Minutes.
After this is all done and your phone may have rebooted 3 or 4 Times during the process.
6th.) Going through setup!.
You're now prompted with the "Welcome Screen" HOORAY! SUCCESS!! You're Now Back to Stock! but we're not done yet.
Now go ahead and skip this setup by just speeding throught like i always do.
Enabling Wifi of course, unallow data being sent to samsung or google , yada yada, add google account, don't restore apps
I will do that later, yada yada.
Once that's done, it should reboot or not.
What I alway before I commence the next step is to make Sure that I Installed Snapchat 1st and Logged into it.
As this now has ROOT detection, and if it's preinstalled or even just freshly installed you won't be able to login to it.
Unless you went ahead of this then well,
You need to erase the ROOT and try again, you might even need to contact the support team of snapchat because it can
lock your account from this issue *(goodluck)*
This method doesn't matter, as long as your google play services is updated and the play store.
Than you can intsall Snap from the Store or from your SDCARD saved APK File.
Now you're ready to move onto the next step.
7th.) CUSTOM RECOVERY!
Flashing Custom Recovery.
Okay so, after you have successfully logged into Snap, you may now, REBOOT your phone back into "DL MODE" again
So, This Time we're now going to flash your custom recovery.
I've always been using "TWRP v3.1.1.0"
So, what we do next is Open Odin back up again, or if you had it Open already Click the Reset Button,
SELECT the "AP" button again BUT THIS TIME!
Select the TWRP File as I mentioned earlier.
After that's been done, go ahead and Click Start.
Once that's done it should automatically BOOT into Recovery but if not, Go Ahead and as soon as it Reboots.
go ahead and holding the VOL UP HOME AND POWER Simultanesly
Until you feel the 1st Vibrate and then 2nd Vibrate with a Visual of Saying REBOOTING INTO RECOVERY.
Then You've successfully made it into "TWRP".
( Same sequence like DL MODE except, going ahead and holding the VOL UP HOME AND POWER Simultanesly )
Either by Powering Off UI or Battery Pull Method or Auto Reboot from ODIN.. anyways
At this point I inserted my SDCARD back into my phone because it has the necesarry files for this partm you should do the same.
8th.) ROOTING PROCESS!
Now onto the ROOT.
From Here this Is OPTIONAL...
What I do tho is... I Pop in my 16GB SDCARD, size doesn't matter as in space.
Now for this step you need to download another 3 files
As long as you have these 3 Files you're good to go,"Magisk v14.0", "Magisk Manager APK", and "UN7 Modset",
Slap those files onto your SD CARD or Internal Storage or OTG even, the choice is yours.
~~~~~~~~~~~~ Actual ROOT Process~~~~~~~~~~~~~~~~~
I'd then reboot My phone into TWRP and then
Allow Flashing in TWRP, then Selecting the "INSTALL" button, and Selecting MY SDCARD as the Storage Location.
I'd then Start by Selecting The, Magisk v14.0 and Flashing that file first, once that's completed go ahead and select.
"Reboot Back To System" and then Selecting "DO Not Install" so you wouldn't have to install TWRP to the System Partition.
Afterwards, it should Reboot, and then Vibrate once, and then Reboot again like a soft reboot,
and then the phone will be back to normal.
( optional battery pull, then holding power button )
I'd then go into the app called "My Files" and then I'd Go into my 16GB SDCARD and Installing the Magisk Manager APK, that's only
if it's not already insatlled... if it isn't do that and if it is.
Then I'd go into the APP to see if it's a Success with installation. Once It is. I'd then Press the tab and Select Magisk hide
then selecting the Snapchat app.
=====================================================================
Afterwards I'd then Reboot back into Recovery.
Flash the "UN7 Modset" for the, Beast mode kernal r61 ZL PJ1 Based by Freeza and then V4A 2.5.0.5 and then the Camera UHQ+ Tweak.
Everything else is up to you for the Boot Animation Changes, and or Dolby Atmos even tho I'm not sure how V4A and dobly will interefere.
Once you have selected those few tweaks, go ahead and let them flash and once that's done, go ahead and let it reboot....
======================================================
AS soon as the phones Back to normal, Check the V4A app to see if it's successfull, and if it is then you have Successfully.
ROOTed your device With a V4A Audio Mod, Camera Tweak and even a Custom Kernel.
LAST STEP!
Is to now go back into TWRP and Flash Magisk, one more time, and then Reboot The Phone Back to Normal.
Have fun with your customizations.
I take no credit for the following flash files, just a tutorial to install all of the above properly.
I hope this helped out you alot today, and as always take care and godbless.
Profit????.....
As a side note....
IF YOU HAVE THE MMC READ FAIL MESSAGE!!!
Which consists of Random Reboots, Heating Issues when theirs hardly no apps on, or even Lag or Glitchyness.
The Temp FiX that I've been using everyday and haven't had these issues since was downloading this app
WakeLock Manager and setting to PARTIAL LOCK! on Level 4.
====Links===
Anything Higher than 3.10+ will work.
And Making sur that your selecting AUTO REBOOT AND F RESET TIME THATS IT>>>> ONLY USING AP METHOD FOR TAR.
.
Odin3 v3.10: http://odindownloader.com/download/odin3-v3-10-7
TAR:
http://downloadmirror.co/1Ksy/N910PVPS4DPJ1.zip
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DPJ1/109071/
https://samsung-firmware.org/download/GALAXY Note4/7sk8/SPR/N910PVPS4DPJ1/N910PSPT4DPJ1/
http://samsung-updates.com/details/81541//SM-N910P/SPR/N910PVPS4DPJ1.html
TWRP 3.1.1.0 TRLTE: https://dl.twrp.me/trlte/
UN7 AROMA MODSET: https://www.androidfilehost.com/?fid=817550096634768841
DRIVERS: http://samsungusbdriver.com/download/samsung-driver-v1-5-63-0
Easy Backup & Restore: https://play.google.com/store/apps/details?id=com.mdroidapps.easybackup&hl=en
MAGISK!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Just click on Latest Magisk and Latest Manager, it should still be Magisk v14.0 and 5.3.0 for the Manager
hi thanks very much
thanks very much for explain ... oh l'm not understant