Database Users

Help with rooting my zenfone laser model ze551kl

Hello. I have a few questions on rooting this phone. (My first time rooting)
First off, Is this the same model as the ze550kl (I assume so but not 100% sure). I have attempted to root this phone through the instructions provided in posts on this website for model ze550kl but I must be doing something wrong with the programs ect. I have never rooted a phone and so this is my first try and I would really like a full in detail screenshot follow through if available to do with the programs once downloaded and any other programs you may need on windows 10 to get to where I need to be. I dislike the zenui so much that is my main reason to root the phone is to remove this and other bloatware as well as some of my friends have some apps that are pretty neat that I would like that are only available through root.. I have also tried other methods posted on YouTube but I think I'm doing something wrong on all of my attempts. I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.). In relation to the screenshots if there is any files that have to be placed on the phones hard drive from something I download off the internet please state this specifically, I believe that one or 2 ways I have seen required this but it seems vauge and I don't think it was done correctly by me. I am great at following detailed instructions but I don't know what exactly it is I need to do as I have never done this before so if something has to have a specific name please note that.
Thank you for the help.

My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.

HampTheToker said:
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
Click to expand...
Click to collapse
Thank you, I think I'm just missing an important step. The zenui just isn't my style. Will be nice to be able to remove

{
"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"
}
---------- Post added at 02:07 PM ---------- Previous post was at 01:28 PM ----------
Yeah, I think you just need more comprehensive instructions. It happens from time to time. From what I can tell so far, it's a pretty straightforward process for those that are familiar with root, but to a beginner it can be a bit much. As soon as mah lazah is dunna chargin' I'll walk you through the steps I took to root it, install custom recovery, and make a backup of your entire system just in case you ever need to restore your phone to a stock-rooted-but otherwise unmodified state. I should have something up in the next couple hours ?

Updated, rooted, and installed custom recovery. I'll post a short write-up shortly.

First off, I'm going to answer your questions since I didn't previously.
Sorvas33 said:
First off, Is this the same model as the ze550kl (I assume so but not 100% sure).
Click to expand...
Click to collapse
No, they're different, but I'm not entirely sure by how much. I'm 100% sure that they're probably maybe 90% or so compatible, but there are differences. I just don't know them without checking. I wouldn't go flashing anything that doesn't explicitly state that it's for the 551 or is compatible or has had a 551 user test and report success. There are some things that are kind of universal (and we'll get into that a little), but for now let's just stick with using caution.
Sorvas33 said:
I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.)
Click to expand...
Click to collapse
We'll make a backup using TWRP, but you'll have to be rooted. A TWRP backup (or nandroid backup) is like a snapshot of your current system. You can customize it and only backup certain parts of the system as well as restore certain parts, but I wouldn't worry about that. Most of the time you'll want a complete backup, anyway. But, to answer your question, no, you'll have to be rooted, but you can always unroot from the phone using the Supersu app. If the damage is physical an unrooted backup wouldn't matter anyway.

So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.

HampTheToker said:
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
Click to expand...
Click to collapse
Thank you man, I will try this when I get a chance (working 14 hour days ATM) but I will let you know how it goes.also what model member do you have. Because the box I have is we're I got my model number. I can't find the one listed on my box in the device itself.

Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.

HampTheToker said:
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
Click to expand...
Click to collapse
Exactly what I have. Sweet. I'll update you once I'm done. Thank you for your help and assistance. Any app advice? For uninstalling and cleaning hdd/ram. And theme?

Come on, bro...I gotta know if that's friendly enough to get you squared away...

HampTheToker said:
Come on, bro...I gotta know if that's friendly enough to get you squared away...
Click to expand...
Click to collapse
I should have time either tomorrow or next weekend all depending and I'll let you know then. Depends on how much I have to work. I check this post about once to twice a day. Thank you for your effort and time. I really do appreciate it.

Now I do have one more question on my mind. Does the Asus zenfone that we have keep a flash tracker? Meaning that it keeps track if a phone was rooted. The reason I ask is that I have a 2 year warantee and I know that this will "void" it unless I flash it back. But if they have a tracker then I need to make sure there is a way to reset that as well. From what I have read personally it is only Samsung that is keeping track in this way. Thanks for your help Mr.Toker

Yeah, that's mostly a Sammy thing. I'm coming from a Galaxy S4 that's been passed down to my six year old. I'm all too familiar with flash counters and KNOX security. Thankfully, I don't believe Asus has anything like that. That's one of the many reasons I chose this phone over anything Cricket had to offer. I don't care how good the hardware is, if it can't be unlocked and rooted, then I don't want it.
But, to answer your question more directly, no, I don't believe your warranty will be affected.

Also, I'm going to paste this warning from the developer that built TWRP for us.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
Click to expand...
Click to collapse

Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk

CKtheProblem said:
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.

HampTheToker said:
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
Click to expand...
Click to collapse
Yeah you're probably right. Luckily, I've never had to send a phone I rooted back in for repairs so I can't say anything about the process.
Sent from my ASUS_Z00TD using Tapatalk

Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?

tmjm28 said:
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
Click to expand...
Click to collapse
at present we have only stock rom, no custom rom is available for zenfone laser.

[SUPERGUIDE][P51xxP31xx] Installation Troubleshoot Guide

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.com​The 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 Part​Creating 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?

A2017G - Updates don't appear to be working. Still stuck on 6.0.1.

Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.

Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.

Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?

Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.

raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.

Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?

raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.

Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)

raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.

Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.

raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.

Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.

raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.

Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.

Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?

Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless

lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.

raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.

What ROM was on it before you flashed B09?

Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.​4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!

Is it possible to unlock a P8 lite 2017 today ?

Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !

Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.

RedSkull23 said:
Hi, yes it should be still possible.
DC-Unlocker is what you need. The operation has a cost in credits, 4$ are necessary to unlock the device since it's the cost that DC asks from retrieve bootloader code from your device.
If you're definitely motivated to do it, it's your only chance but luckily it's an acceptable prize.
Click to expand...
Click to collapse
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...

turboxav said:
Hi,
I'm French and my level in english is not very high.
So I try to unlock my wife's phone but I havbe understood that it is no more possible with the classic way with huawei support.
Does exist another way tu do this ? Or is it definitivly impossible ?
No french forum can explain this.
As I can see many custom Roms here I keep a hope !
Click to expand...
Click to collapse
What you mean by "unlock".

60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
With my p10 lite with emui 8 it worked. So why not

0

yes
I Have unlock my phone yesterday with dc unlocker

Seppppx said:
You can downgrade (idk if it is possible from emui 8 I don't even own this phone) and then you can follow this tutorial to unlock your bootloader (FOR FREE) https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
Edit : found this guide with HiSuite it may work https://youtu.be/xFCLpgGZEJM
Click to expand...
Click to collapse
Yeah, but not for Huawei P8 Lite 2017 version... I found this to be possible just for older phones (like the original P8 lite) which can be downgraded to Android 5. Newer ones can't be flashed with unsigned firmware (= firmware which is not straight from damn Huawei who decided not to provide the bootloader codes in the first place) so the only way apparently is to use paid software like DC-Unlocker as stated in this official XDA thread --> https://www.xda-developers.com/huawei-honor-unlock-bootloader-fee/
60nine said:
hi, does dc-unlocker work on Emui 8 as well? PRA-LX1 model, build 8.0.0.399 (C432)...
Click to expand...
Click to collapse
Unlocked the bootloader yesterday! I have Huawei P8 Lite 2017 PRA-LX1 and had latest Emui 8 build on it... Bought the code for 4€ from DC-Unlocker, and required around 2 minutes for unlocking. You can follow this guide --> https://www.youtube.com/watch?v=4xYybHAlWaQ
I tried so hard to get the code for free, and I know modding should not cost people money. But at the end of the day, I think those 4 euros were worth it

Yeah,4 Euros is ok and the only method!!!

-CALIBAN666- said:
Yeah,4 Euros is ok and the only method!!!
Click to expand...
Click to collapse
And also worth it if we consider fact that our phone is now EMUI free. ?

DunoCZ said:
And also worth it if we consider fact that our phone is now EMUI free.
Click to expand...
Click to collapse
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy

af1985 said:
Dear all,
sorry in advance for the silly question but in this regard I am dumb as a brick.
I run DC Unlocker, got the phone unlocked but now the only thing I have is the stock boot telling me the phone is unlocked and therefore cannot be trusted. From there on, I do not know how to procede in order to install TWRP recovery + LineageOS 17.1. I tried to install TWRP but it only runs after a factory reset with the "stock" Huawei eRecovery and every time I reboot (I even got to the point of installing LineageOS via fastboot) it is always back to square one.
Again, sorry, but the last phone I "worked on" was an HTC Desire HD some 8 years ago, therefore you can guess I lost some years of advancements
Thank you for any help regarding the steps I am missing, links to guides much much appreciated.
Best and ciao from Italy
Click to expand...
Click to collapse
Did you after fastboot oem unlock leave phone format yourself right?

DunoCZ said:
Did you after fastboot oem unlock leave phone format yourself right?
Click to expand...
Click to collapse
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks

af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".

af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget ???

Momin8454 said:
Just for your information, TWRP on this device is not fully supported. Every TWRP version you may find on XDA forums for this particular device is different. In my case TWRP back up doesn't work, wipe cache doesn't work, format data only breaks the system partition , flash GSI's from TWRP also doesn't work XDXD
The only thing I could do from TWRP was flash Magisk and hope that nothing will go wrong in the future ...XD got it? Flash and forget
Click to expand...
Click to collapse
Lol you are dumb...

DunoCZ said:
Lol you are dumb...
Click to expand...
Click to collapse
Well, I didn't had any knowledge of it. Turns out my EMUI version was more recent one that's why I had more issues with TWRP.
And I was just sharing my experience with Honor 8 lite.

DunoCZ said:
Yeah I get it now, the problem is if you wanna go to twrp sometimes you have to press volume up and hold it until logo shows up, sometimes you had to hold both volume buttons etc. It's kinda wierd but the factory format from erecovery is in twrp disabled due to this because sometimes it wont let you boot until format (that triggers almost anything like fastly restarting to and from recovery etc.).
So keep calm it's "normal".
Click to expand...
Click to collapse
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time

Some advice from a beginner
af1985 said:
Thank you for your support. To reinstate some order in the procedure, yesterday I reinstalled EMUI from eRecovery and now I am back to "zero-point-one", aka right after DC Unlocker: when I switch on the phone it says it is unlocked and then launches stock OS. From now on what should I do to have in the end LineageOS 17.1 installed? Again, thanks for your time
Click to expand...
Click to collapse
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
af1985 said:
Don't fully get your question. Current situation is: Phone unlocked with DC Unlocker. When I switch it on I get the "phone is unlocked" message and if I don't do anything it starts booting stock OS, otherwise goes into Huawei eRecovery. If from Huawei eRecovery I do a full wipe, it starts TWRP. But even if I work on TWRP, when I reboot it is all back to "phone is unlocked". And again, and again. Hope it is clearer.
Thanks
Click to expand...
Click to collapse
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)

Jujub said:
Hi!
So, I installed Lineage OS 17.1 on my sister's phone just two days ago, maybe I can give you some advice being myself a beginner. So, first of all, I guess you have enabled OEM unlock (otherwise you could not flash TWRP I guess? I don't think this is the point anyway) If not so, go to Developer Options --> Enable OEM unlock and you will see both the bootloader and FRP unlocked.
The try to follow the DarkJoker360's Lineage OS 17.1 install guide step by step (don't forget to flash the los_patches_prague.zip!). The right version of TWRP is important too for compatibility issues, so install the version he provided.
Anyway, as @DunoCZ pointed out, for entering TWRP recovery you have to press Volume UP button + Power button and keep them pressed until you get to the TWRP. Otherwise, what the device does is either booting up or go to the screen like "Press Volume UP for at least 3 seconds to go to erecovery" and if you do that, it will go into Huawei's own recovery.
Another thing is... Did you do a full wipe (system, data, cache, dalvik/art cache) in TWRP before trying to flash the new ROM? (don't just do the factory reset in Huawei's recovery, I read somewhere it doesn't wipe everything like the advanced one in the custom recovery)
Because as you wrote here, the stock OS booted up before you installed stock from again via Huawei erecovery. So my wild guess is that the wipe you did before flashing Lineage OS wasn't a full wipe?
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
By the way, after installing Lineage OS 17.1 I found out there were indeed some very important problems in the ROM as noticed by other testers too...
The reason why I changed the ROM on the device was mainly because of two reasons:
1) Short battery life
2) Not enough memory
And unfortunately, on Lineage OS 17.1:
1) Battery life not good enough. Unless you fix it by patching a new kernel, be always wary of apps running on your device etc., the battery ran short even after replacing the internal battery. Alas. Besides, I wanted something stable for my sis who threatened me to buy an iPhone if I couldn't fix her phone lol
2) Very big problem with memory: I couldn't find a way to write to the SD card as other users pointed out. It is read by the device, but apparently it is read only and even with root permissions I couldn't find a way to obtain write permission for the apps. Perhaps some options in fstab mount file should be changed, but honestly, I tried with my below-average knowledge of Linux and gave up :crying:
But then... I tried Lineage OS 15.1 and this one worked much, much better. Battery life is super good and has the adoptable storage option for the SD card! This way, instead of those 9 gigs of memory now the phone has more than 70! And honestly, this ROM solved both the most important problems of this phone
(PS: sorry for the long posts lol)
(PPS: if you decide to switch to 15.1, remember to decrypt the memory following this post otherwise you won't be able to install more that a bunch of apps on the phone. Besides, remember to flash Dil3mm4 's TWRP recovery)
Click to expand...
Click to collapse
Check out my SPECTRUM profile I wrote even simple tut how to flash kernel and enable adoptable storage

Trying to install TWRP and Lineage . . . vbmeta is in the way

I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.

vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!

vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.

Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).

MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it

I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM

I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.

vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.