Database Info

[GUIDE] Beginner's guide - first steps with a MTK phone

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
This guide may be obsolete now for the new MTK SOC's powered phones, but it will give you some ideeas about how MTK phones world works (especially if you are new to this).
Why this thread?
- Because of all those PMs I receive with questions about how to do this or how to do that.
These things aren't they covered here on XDA?
- Some of them are, some don't, or they are spread over the forum in different sections, different threads. Also I will present here my vision about how to do things, and in some parts is different than the others existent.
I tried to document all steps with images for a better understanding, and to make it easy for people who don't understand well English (also I don't claim that my English is very good, but I'm trying).
1. If you want to use your phone as you buy it, then this thread is not for you, but if you want to use a custom recovery, to install a custom ROM, or some modds, keep reading.
2. First big step in our journey is to root your phone, which most of you know that means to get root (administrator) access to your phone's OS - just a simple definition. With an unrooted phone, you can't do much, and that means you will use it pretty much as you buy it - see first point.
There are multiple methods to root your phone, through an application from your phone, with an executable software from your PC or by flashing a zip modd from recovery (only for custom recoveries).
A. The best rooting application at the moment (in my opinion), is Framaroot.apk, developed by alephzain - please stop by his thread and drop a thanks, or if you can buy his donnation app from Playstore to support his work. You can download this app from official thread.
B. For rooting with a software from PC, I know three big candidates: oneclickroot, kingoroot and srsroot. I know there are more, but I mentioned only the best known.
C. Rooting zip archives are two, to choose from: chainfire's and koush's. Although, these require to have a custom recovery installed.
Any method you choose, be sure to check the phone models reported to work for, and look for your model.
Next, I will present step by step what I call "the beginner's routine":
root the phone;
make a nvram backup;
make a stock ROM backup;
generate a custom CWM and flash it;
patch to unsecure the boot and flash it;
get a Root File explorer;
create a custom recovery by porting one.
Prerequisites:
you must have an account on XDA; if you don't, then create one - and remember, at beginning you will not be allowed to post but you can hit Thanks for people I will mention here.
use a computer with Windows XP or 7 (I don't know if it will be any problem in vista or windows 8, but I didn't tried them, so I can't tell).
a phone with MTK CPU, obviously!
these tools:
MTKDroidTools of rua1's - download it from his thread and hit Thanks or donate to him, please
SPFlashTools or MTKFlashTools.
MTK USB Drivers and your phone manufacturer's USB Drivers if they provide that.
For MTK USB Drivers, there are many sources, but I couldn't find any official source. Few known sources: here and here.
* ADDED: For windows 7 and xp I repacked all MTK needed drivers, bundled with latest google usb drivers and using windows driver installer. Some of the drivers are not digitally signed, so when the prompt window ask you if you want to install unsigned driver (it will be several times) select yes or ok. The advantage is that this method is easier than manual method and also will create an entry in installed programs, and later if you want you can uninstall them in control panel uninstall program. Before installing this you need to remove old drivers installations - use usbdeview (download it x86 or X64), and look for VendorId 0bb4 and 0e8d, and uninstall every device with these Ids. Packed drivers are attached to this post; take what corresponds to your windows version. Unpack the archive, open the folder and run dpinst.exe. More info inside: read info.txt (especially for XP).
Install all needed drivers.
A good text editor (Notepad++ or Geany) installed.
Adb installed in your computer from Android: here, here and here you can learn how.
Credits and Thanks:
@alephzain - Framaroot developer
@rua1 - developer of MTKDroidTools
@Chainfire - SuperSU developer
@Koush - so many things!!!
@michfood - developer of Boot Recovery pack/unpack tool
and, even if it is not presented here, but because I use a lot his tools in Linux:
@bgcngm - for his Unpack/Repack scripts

1. Root the phone.
For this step I choose to use Framaroot.apk, first because I don't like to install unnecessary software on my computer, and second because it supports a very large number of MTK phones. So, go to alephzain's thread and download the apk, then connect your phone to PC with USB debugging enabled, turn on USB Mass storage and copy Framaroot.apk to your sdcard root, or in internal storage if you don't have a sdcard in your phone. Eject phone's USB storages from PC, and turn off USB Mass storage from phone.
{
"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"
}
Go to apps drawer, find File Manager, open it, navigate to location where you placed Framaroot.apk touch on it and install it. After that go back in apps drawer and open the newly appeared Framaroot. In that window you have to specify which exploit to use for getting root access. If you don't know it's not a problem, you can try each one until you see the Success message (for me was Barahir). If none of them works, then you have to find a different method to root. After success patching, reboot the phone and then you will see SuperSU.apk in your apps drawer. Now you have root access!
2. Install a Root Explorer.
I prefer ESFileManager, but you can choose what you like. This can be installed free from Playstore, or if you have it downloaded in your PC, use same steps as in Framaroot case, and install it.
Then open the app and let's activate the Root Explorer in it.
But, here you can choose a different view style instead of default big icons - I like Medium Icon view.
Touch on Globe symbol from upper left corner to open Advanced Tools menu, and select Tools (last one). In the list that opens, scroll down until you see Root Explorer entry and touch "OFF" button to activate it. You will be prompted to Grant Superuser access - Grant it! Then, touch on "Root Explorer" text and in the popup window select Read/Write, and in next window select all radios from RW column.
That's it, ESFileManager is now a powerfull Root Explorer.

3. Make a backup.
This means actually make two backups, one for nvram and one for the whole stock ROM. Why to make a backup for nvram? Because it is very easy in MTK phones to mess up with it, and you may loose IMEI, mac address or to have other connectivity issues. This backup will be your insurance.
For this you need MTKDroidTools. Download it from rua1's thread (link in OP) and unzip it in a folder named "MTKDroidTools" on your primary (system) partition - this is important, and in other locations you may experience errors and malfunction.
Connect your phone in usb debugging mode to PC, then start MTKDroidTools as administrator and wait untill you see that MTKDroidTools recognize it and loads its data. The following pictures will show you how to check if you have usb debugging activated, and how MTKDroidTools looks with loaded phone data. In most of the phones, adb gets root access immediately, but in some "branded" ones that has to be achieved by click on the "ROOT" button next to "Adb Terminal" - Notice that if you don't see that ROOT button, that means you have already "root in shell". Also, if you have chainfire's SuperSU you will be prompted in the phone to grant root access to adbd, but if you have koush's Superuser, adbd gets root access by default.
Now, as I said first thing is to do a nvram backup. Click on "IMEI/NVRAM" button and next select both methods (bin and zip folder) and click on "Backup".
After that, it's time to do a stock ROM backup. This is important if you are going to try different custom ROMs and modds. This will assure you that you always have a way to start from the beginning in a clean state. Also makes easy to unbrick your phone if you have the misfortune to brick it.
Click on "root,backup,recovery" tab, and click on "Backup" button, then wait to finish. Be patient, this will take a while, and you can see progress logs in side window. At the end, a popup will prompt you to pack the backup. Now you know it is finished. I don't pack these backups, but you do what you think.
In this stage first thing I do is to generate a scatter file. You have one in that backup made before, or you can get one from stock firmware archive if the phone's manufacturer provide that, but let's see how to do it as it is, to understand the process, or to learn how to get one if we loose it or we are unsure if the one we have is good for our phone (this is important, because using a wrong scatter file it may damage your phone).
So, return to "Phone Informations" tab and click on "Blocks Map" button. A window opens with your phone partition structure. Click on "Create Scatter File" button and save it somewhere in your computer.
Mission complete for backup; you are assured now.

4. Generate a custom recovery.
This is mandatory if you want to use an easy way to backup, restore, flash or wipe ROMs and modds. Fortunately, rua1 has included in his tool all you need to generate one for your phone. This method is successfull for almost every MTK phone, but not for all. There isn't an universal method for anything.
So, enter again in "root, backup, recovery", select the radio "To choose the boot.img file" - by default is selected "Install already prepared files" - and click on "Recovery and Boot" button.
When prompted, select the boot.img from previous backup folder and click Yes to make CWM recovery automatically. First you will be prompted to flash a patched boot.img in your phone - click Yes to get an unsecured boot, then next message will ask you to install the new created recovery in your phone. Click Yes and Yes to reload the phone in recovery mode.
The phone will shut down and reboot in recovery. Now you can see your custom recovery in place.
GOOD TO KNOW: you can't generate a recovery everytime you want to flash one, to use MTKDroidTools for flashing, and the adb method may not work for many MTK phones.
The most known method to flash a new recovery is by using SPFlashTools or MTKFlashTools, and an alternative method is with MobileUncle application from phone, but I will show detailed the FlashTools method. One thing though: if you want to use MobileUncle application, you have to use it from /system/app folder, not from /data/app. Many users say that the MobileUncle doesn't work to flash recovery: it show success, but rebooting to recovery reveal the old one. The reason? They installed MobileUncle from market, and that place the app in /data/app as a user app. In custom ROMs where the app is placed in system by ROM developer, the problem won't manifest. So, if you want to use MobileUncle, make it a system app not user app.
In order to do that, grab a copy of any of these tools from DR_MOOSAVI's thread (link in OP), unzip it in a folder "MTK_Flash_tool" in your primary(system) partition (C in my case), and notice the name have to not contain any spaces or special characters. In that folder create a new folder "Resources" or ROM or whatever name you want, also without spaces or special characters, and place in it your scatter file and recovery img you want to flash. Open Flash_Tool executable as administrator.
IMPORTANT: Your phone is not connected to the PC now. Swtich it off and wait, you will connect it later.
Continue in next post.

In Flash_Tools program window click on load scatter file, navigate to that folder you created and select your scatter. Now you can see your phone's partition structure. If the recovery you want to flash is named "recovery.img" it will be selected automatically, if not you have to click on recovery row in Location column and select your recovery from that folder.
Then click on "Download" button.
Now connect your phone to PC, just like that in power off. Some models enter automatically in download mode and the flashing process begins, but others don't. For some it is necessary to connect them without battery (battery removed), other need to press briefly Power and Vol Down button at same time and release them immediately. That you have to find for your phone from forums, other users, or by trying. When the phone enter in download mode you will see a red bar down in Flash_Tool window, followed by a yellow or other color one (that means the flashing process is taking place).
At the end a popup with a green circle or green checkmark will let you know that the flash was a success. Deconnect the cable and reboot the phone, or reboot it in recovery to see if the wanted recovery is installed. The most common method to boot in recovery from power off is to press Power and Vol UP at same time, and keep them pressed untill you see the logo, then release Power but keep pressing Vol Up untill the recovery UI appears. If Power and Vol Up doesn't work for you, start the phone normaly and connect the phone to PC, then open a command prompt window, and type " adb reboot recovery", then hit Enter during bootanimation. The phone will stop loading and will boot in recovery.

5. How to port a custom recovery.
Check my new guide.

Check my new guide.

Awesome Tutorial!!! U did it again....
Thanks!!!

Thank you sir I will try to port cwm to my mtk mobile
Sent From MTK-MT6572
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
Sir now my mobile with ext4
Now in your thread about porting carliv cwm.. there is only custpack and ubifs ...!! Where is for ext4
Sent From MTK-MT6572

carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376

[email protected] said:
carliv grt work hope u add this post too http://forum.xda-developers.com/showthread.php?p=49081376
Click to expand...
Click to collapse
Thanks, but that is not something for begginers. Maybe meteos method with his app will be, but I'm not sure. Though, if someone want to procede to do that, you can edit your post and give more details, for people to know what is about, and to follow your link if they are interested.

Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.

iZLeeP said:
Great guide @carliv.
Just a bit confused, as I usually flash custom recovery first before rooting my MTK phones (same goes for all my android devices). So, maybe, rooting and flashing custom recovery is interchangeable as the first step for MTK phones depending on their availability.
Click to expand...
Click to collapse
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.

carliv said:
Yeah, well the next step in my guide is "do a stock ROM backup", and if you flash a custom recovery, that will not be a complete stock backup. With my method, any time, after flashing the stock backup, unroot and you will be in stock initial state.
I hope it's more clear now.
Click to expand...
Click to collapse
Got it. So this is more suited for those who do not have the original firmware for restoring their devices in case something goes wrong which is so like MTK phones. In any case, your guide is spot on. Hope the moderators would give this a sticky, if possible, since MTK phones are scattered all over xda.

How to Port to Device that have recovery-from-boot.p
Hello Everyone, and hello to @carliv,
Thanks to this Tutorial I have Manage to port in on a MT6582 and MT6572 Device with ext4 partition, but I just want to share some tips when porting the latest build of the carliv the tutorial here is complete except for one thing just in case you are ending up on a custom recovery not booting up and when you use the MTK Droid Root and Tools you will see this
-->Connect Device<--
there is a file blah blah - recovery-from-boot.p <----
Now that mess up the things but before we dig into that let me first share on how I got my Carliv Custom Recovery to Bootup
on the Tutorial there is a section that you need to use the MTK Unpacked tool right now once you have done that do all the other things that is written in the tutorial it will guide you on the whole process but on my end even though I followed the tutorial and all are correct I still end up on a Bootloop well I discovered that you need to copy the init file from the RUA1 CWMR that you got from the MTK Droid Root and Tools and overwrite the one on the Carliv Recovery after that once you have finish until on the Overwriting of the Kernel and Kernel header pack your Carliv Recovery using the MTK pack tool and now Flash it on your Device it will now boot :highfive:
BUT WAIT!! yes! it will boot but it will boot on the STOCK RECOVERY and that is because like what I said the recovery-from-boot.p is the culprit of the issue now you need to root your device which is on my end I used framaroot and then download the ES file manager and also follow the instruction of carliv on how to have the full ROOT R/W access and on your device, once your have done that got to this folders and delete this 3 files.
Be sure you have the R/W access or else this files will not be deleted
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
and now once you have rebooted your smartphone to recovery mode it will now boot to the Carliv Custom Recovery.
But also take note that if you don't have that 3 files on your device your just good to go and it will boot to Carliv Custom Recovery without any issues.
it's just that 3 files makes the custom recovery always boot to stock recovery even though you do something else
hope this tip helps for some people having issue on a bootloop carliv custom recovery on doing the manual porting
and don't forget to hit the thanks button if this helps :victory:

rnovino said:
/system/recovery-from-boot.p
/system/etc/recovery-install.sh
/system/etc/recovery-resources.bin <--- I am not just sure if this is the right filename but it is almost the same will check it once again once I got to stock rom again :fingers-crossed:
Click to expand...
Click to collapse
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.

iZLeeP said:
Removing recovery-from-boot.p is enough, I think. Besides, CTR asks if you want to disable recovery-install.sh. That prevents the ROM from flashing stock recovery.
Click to expand...
Click to collapse
it depends on the unit, I just deleted the recovery-from-boot.p and still it boots up on the stock recovery that's why I needed to trace other files that still makes it boot on stock recovery, but then again not all units will have the same issues as mine

Thanks for your help, it works with my Huawei Honor 3X (mtk6592) !

Thanks Man!

Error
Please help me in porting recovery.I am getting error "the syntax of the command is incorrect " in all four files.
View attachment 2654172
View attachment 2654177

Comprehensive Guide for Rooting + Flashing C3 devices (D2533 and D2502)

ANYTHING THAT HAPPENS FROM HERE ON WE WILL ATTEMPT TO SEE WHAT CAN BE FIXED BUT DO TAKE NOTE THAT BRINGING IT TO A SERVICE CENTER AFTER MODIFYING ANYTHING AND THEY WILL TELL YOU THE PHONE NEEDS A NEW MOTHERBOARD FOR THE PRICE OF A NEW C3. YOU HAVE BEEN WARNED, SO TAKE EXTRA CAUTION
Hi everyone, this is a general thread for those wishing to break into your new C3 device now that a window has opened in terms of firmware.
Be advised, Sony has stated there will be no rear camera fix and no Marshmallow for the C3​
This guide will assume your bootloader is unlocked, if you do not have any idea what it means or how to get about it, you must divert your attention HERE for a bit. Use that link for know-how to unlock your bootloader, and only proceed after successful unlocking. For bootloader codes, select the Z3 Compact as your device, because it shares the same unlock key generation algorithm.
------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Now, first thing's first, let’s get root + custom recovery. This is important, because people have been recommending KingRoot and as far as I'm concerned that is the most asinine way to provide system privileges. You wouldn't believe the pain I endured just to remove it and install SuperSU, which is far more reliable. Anyone who wishes to disagree or feels offended by this preference may kindly sod off, no offence.
STOP!
This section is only for Lollipop 5.1 firmwares, anything else and we can't guarantee safety.​
Now that you read the warning, let's continue with recovery.
Head HERE for the D2533 files, and HERE for the D2502/D2503 files.
D2533:
1. If you want root as well, get SuperSU and copy it to your SD (Internal/External)
2. Unzip the .zip archive, this contains everything you need.
3. Turn off your phone and plug it into your PC/Laptop while holding the VOLUME DOWN button. It will install a driver first.
4. Double-click the .bat file in the folder of the extracted archive.
5. Read and accept the T’s&C’s
6. The recovery will now install XZDR. When your phone reboots, hold VOLUME DOWN. The green LED should turn PURPLE.
7. You will now be in TWRP recovery. At this point, you can install SuperSU, Custom ROMs, or anything you may otherwise want.
8. Once done, reboot your phone.
D2502/D2503:
1. You need these files first. If you want root, get SuperSU as well.
2. Add the .img file into your fastboot folder.
3. Now, turn off your phone and plug it into your PC/Laptop while holding the VOLUME DOWN button. It will install a driver first.
4. Right-click the space inside the folder while holding SHIFT then click 'Open Command Window Here'
5. You will see a command prompt window so just type
Code:
fastboot flash boot boot.img
6. It will send the .img files and let you know when done
7. Now type
Code:
fastboot reboot
to reboot your phone
8. When your phone turns on, a green LED will light up. Hold VOLUME DOWN, the LED should turn PURPLE.
9. You will now be in TWRP recovery. At this point, you can install SuperSU, Custom ROMs, or anything you may otherwise want.
10. Once done, reboot your phone.
Soooo, what now?
If you are a dev or would like to become a dev for this device, head HERE to restart CM12.1 development.
Come to THIS THREAD for information on deodexing your device and give it a fresh look. This is a relatively new development so be patient and check in once in a while for forum news.
Check out the custom stock kernel for the 5.1.1 stock ROM here.
In addition, with a recovery you can now instant reinstall your system for your D2533 or D2502 via zip flashing without adding root and recovery all over again.
Did you know that our phone is missing the Bravia Engine? Yes, a Sony without Sony's best feature. Fortunately it can be fixed, with your recovery just download and flash the files provided in this thread.
This thread is a work in progress, any questions are welcome. It is encouraged and we'll try our best to help so anyone can learn on what to do and what to improve.
Credits:
• @wwwhana
• @Riccorbypro
• @Gaurav007
• @cezer kiran

Upgrading and downgrading your firmwares
Warning:
Code:
Your bootloader must be unlocked.
Doing this has the potential to brick your device if not careful.
All your data and settings will be wiped as well.
So now you realise you prefer the simpler and uglier KitKat version, or miss the horrible camera in Lollipop 5.0, or you just want to use the weirdo Lollipop 5.1 for the LOLZ.
This is simple enough but will require some a lot of internet bandwidth so be prepared.
Download Xperifirm and find your phone model, it will tell you what are the available firmwares you can download for your country. Just download them, remember where you place those files.
Next you will need Flashtool by Androxyde, just unpack it and install.
Running it will synchronise the updates so just wait a while for it to load. Once done, click the lightning symbol and select Flashmode.
A window will open up asking you to select firmware, which is the .ftf file you downloaded using Xperifirm a while ago.
The only options you modify is Wipe: Tick all and Exclude: Untick all. After that, click flash and it will instruct you to insert your phone.
Make sure your phone is turned off, then plug in while holding the VOLUME DOWN button.
The process will automatically start so you just have to wait until it's done then it will auto reboot and start setting up your phone like new.

Optimising your device​
First off, download Kernel Adiutor and grant it root access. Open it, and look in the Build Prop Editor section.
Look for this code and edit it to this value:
Code:
ro.min_freq_0=300000
Now reboot your device, this will make your phone unlock minimum speed to save some battery.
All good?
Now, let's look at the CPU section. Set the CPU maximum frequency to 1190 and the minimum to 300, then set CPU governor to Interactive. Open up CPU Governor Tunables and edit the values according to this picture:
{
"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"
}
That completes the CPU section, now we have to edit the Kernel Samepage Merging. Go into that tab, and enable KSM. Set Page scans to 100, and Sleep to 500.
After editing each tab here, make sure you tick Apply on Boot so the settings will stay there.
This section is still under construction.

awesome!

RE
Thank you for the reply in my email sir. :good: :good: I will try this method but i want to wait for other replies.
It's not that I don't trust your thread but I just want to have a little bit safety. I hope you understand....

E-Bin said:
Thank you for the reply in my email sir. :good: :good: I will try this method but i want to wait for other replies.
It's not that I don't trust your thread but I just want to have a little bit safety. I hope you understand....
Click to expand...
Click to collapse
I don't mind. First time I came here to root the C3 I trusted nobody.

Install TWRP XZDual
Hello. I have a Sony D2502 with 5.1.1. Used Kingroot to root my phone so I can disable annoying Sony Bloatwares and without having to unlock the bootloader. So I am not sure if bootloader got unlocked as well. I have 3 concerns and would to ask for your assistance and proficiency.
1. Is possible to install TWRP with a locked bootloader? If so, how? I'd like to request for the procedure without the android tech jargons.
2. If it can't be done, what is my contingency plan in installing twrp without having to reformat my phone.
3. Tried several methods on how to enter default/stock recovery mode on my Sony D2502. Tried, press and hold Volume Down and Power, Volume Up and Power, Pressed All 3 at the same, it only vibrates. No problem with rebooting to safe mode and normal mode. How do I enter the stock android/experia recovery mode?

RK_D2502 said:
Hello. I have a Sony D2502 with 5.1.1. Used Kingroot to root my phone so I can disable annoying Sony Bloatwares and without having to unlock the bootloader. So I am not sure if bootloader got unlocked as well. I have 3 concerns and would to ask for your assistance and proficiency.
1. Is possible to install TWRP with a locked bootloader? If so, how? I'd like to request for the procedure without the android tech jargons.
2. If it can't be done, what is my contingency plan in installing twrp without having to reformat my phone.
3. Tried several methods on how to enter default/stock recovery mode on my Sony D2502. Tried, press and hold Volume Down and Power, Volume Up and Power, Pressed All 3 at the same, it only vibrates. No problem with rebooting to safe mode and normal mode. How do I enter the stock android/experia recovery mode?
Click to expand...
Click to collapse
1. I think it's possible with the T2U Dualrecovery, it contains TWRP already. I was perturbed at first about android lingo as well, but most guides are simplified enough and there will be people who are willing to answer your questions.
2. You can use the guide you found in the nut-xperiafiles website. Other than that, there's no other way.
3. The C3 does not come with a stock recovery. Sony hates anything that isn't their flagship phone.

T2U-lockeddualrecovery2.8.26-RELEASE.combined.zip <--- Is this the correct/compatible release for Sony D2502? If so, I would like to write down the steps as I understand them:
1. Extract Zip file and Run .bat file
2. Connect Phone, with USB Debugging Enabled. (Should the phone be turned off or leave it on?)
3. Select 1 from the CMD Menu? Follow the process and it will reboot for the first time to TWRP?

RK_D2502 said:
T2U-lockeddualrecovery2.8.26-RELEASE.combined.zip <--- Is this the correct/compatible release for Sony D2502? If so, I would like to write down the steps as I understand them:
1. Extract Zip file and Run .bat file
2. Connect Phone, with USB Debugging Enabled. (Should the phone be turned off or leave it on?)
3. Select 1 from the CMD Menu? Follow the process and it will reboot for the first time to TWRP?
Click to expand...
Click to collapse
Yes, the phone should be left on. Just select 1, it should be the same though I've never used KingRoot.

AutumQueen92 said:
Yes, the phone should be left on. Just select 1, it should be the same though I've never used KingRoot.
Click to expand...
Click to collapse
Ok. Many thanks. Several apps would tell me I am rooted. Not sure if XZdual would work on Kingroot.

Thanks. I was ablt o install TWRP. How Kingroot is still installed. I thought SUPERSU was going to delete annoying kingroot.

RK_D2502 said:
Thanks. I was ablt o install TWRP. How Kingroot is still installed. I thought SUPERSU was going to delete annoying kingroot.
Click to expand...
Click to collapse
Kingroot will stay until you do a full reinstall or brute force uninstall. It would be better to just do a full wipe, and flash the prerooted stock roms instead. Just make sure to backup any apps you might have.
Sent from my Xperia C3 using XDA Labs

AutumQueen92 said:
Kingroot will stay until you do a full reinstall or brute force uninstall. It would be better to just do a full wipe, and flash the prerooted stock roms instead. Just make sure to backup any apps you might have.
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
I was able o install XZDUAL easily but had to install SUPERSU with a different approach though. KINGROOT was blocking it somehow. Used Terminal Emulator apk to install SUPERSU and updated via Play store. and it worked. Uninstalled KINGROOT. Restarted/Rebooted phone about 10x just to make sure it wasn't a fluke. All up and running at the moment. Thanks.

RK_D2502 said:
I was able o install XZDUAL easily but had to install SUPERSU with a different approach though. KINGROOT was blocking it somehow. Used Terminal Emulator apk to install SUPERSU and updated via Play store. and it worked. Uninstalled KINGROOT. Restarted/Rebooted phone about 10x just to make sure it wasn't a fluke. All up and running at the moment. Thanks.
Click to expand...
Click to collapse
No problem. I forgot about the terminal emu method lel
Sent from my Xperia C3 using XDA Labs

LTE Unlock
AutumQueen92 said:
No problem. I forgot about the terminal emu method lel
Sent from my Xperia C3 using XDA Labs
Click to expand...
Click to collapse
Hello Autumn. Have you tried unlocking the LTE aspect of D2502? If so, how? I have 5.1.1 Os, XZdual and SUPERSU. Good riddance to kingroot.

RK_D2502 said:
Hello Autumn. Have you tried unlocking the LTE aspect of D2502? If so, how? I have 5.1.1 Os, XZdual and SUPERSU. Good riddance to kingroot.
Click to expand...
Click to collapse
I've no idea, my D2533 came with LTE already.

Kernel Adiutor Optimal Settings
Hello Autumn.
Based on your snapshot below, is this a balanced setting? if so, then i'd most likely replicate this. Phone is working well so far after the twrp installation and SUPERSU replacement on Kingroot., feels like brand new when i got the D2502 about 2 years ago. I'd like to make some speed improvements while having stability at the same time. thanks

RK_D2502 said:
Hello Autumn.
Based on your snapshot below, is this a balanced setting? if so, then i'd most likely replicate this. Phone is working well so far after the twrp installation and SUPERSU replacement on Kingroot., feels like brand new when i got the D2502 about 2 years ago. I'd like to make some speed improvements while having stability at the same time. thanks
Click to expand...
Click to collapse
It worked for me, but I'm in the midst of testing out a new setting so hopefully it can be updated soon.
Sent from my Xperia C3 using XDA Labs

Kingroot Leftovers
Hello Autumn, after fiddling around with my settings, came across CPU Processes and ran into KINGRot. I am all set, I have XZDUAL, SuperSU. Everything is running great except having the remnants of Kingroot. Please see attached file. How can delete this? Is it safe without bricking my phone? If so, how?

[GUIDE to ROOT] for new users, step by step, main aspects clarified

INTRODUCTION (don't skip it if you want understand what you are reading)
Here we are, as promised.
A guide for beginners who hardly understand all the brief steps described in guides: root Galaxy S5 G-900V, unlock-bootloaders, etc. thanks for everyone who helped me with big patience (jrkruse, Bryanx86, XeCuTioN, youdoofus and all other guys) and who developed the scripts/guides. This guide is to help you keep focusing there
I'll try to be as brief as possible, remembering me when I entered in theis world without knowing this phone, and eager of flashing quickly the desidered ROM. I admit I've spent different days and a bounch bad words around figuring out all the obstacles that appeared time by time: you should know from the beginning that a small variation of the process described here may force you start from zero, loosing an amount of time, and that there are different phone models and also with different chipset, so you need carefully understand which phone you have before learning the process or losing time with wrong experiments, they will not work.
Anyway this guide will help many figuring out different aspects of phone, useful to everyone who is appraching flash the S5, it's a collection of important things I've read arond and experimented myself.
PHONE:
I have a S5 G900V with Toshiba chipset "CID11", and I tested all the following only on this phone, for questions/explanations read this article:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I'm not going to give any support to other versions, but post me if I forgot something
DEFINITIONS:
PHONE: unfortunately there are a moltitude of Galaxy S5 released, they are dedicated to particular geographic areas and particular service operators, the 900V is created for Verizon brand and it has a native ROM with SIM locked. If you bought one with SIM unlocked (and you may even read under "about" it is a 900F for example! check the right one starting the download mode) and you want root it/upgrade you should consider that the first rom uploaded to begin the following process is Verizion original, and it contains SIM lock: you will not use your phone later till you flash the final desidered rom! Chances are also, if you have like I do a CID11 chipset, the SD card will stop be recognized, and that's a boring thing. EDIT: the SD card will work, it was my phone with the SD gold contacts spoiled, accurately I lift them up and sd worked always later.
CHIPSET: as I know there are two variants around, one with Chipset Sasmung "eMMC" and one with Toshiba "eMMC". Before you start you need to read the file /sys/block/mmcblk0/device/cid under the root path, the first two bytes will be 11 or 15, if you have 15 you're lucky and you may even remove the locked bootloader, if you have 11 there are not solutions yet for unlock, but you can install Marshmellow 6.0.1 (unrooted/without root). To check the file CID I suggest to install xplore from Lonelycatgames (you may find a copy around, google it and download apk, open the folder root, the path /sys/block/mmcblk0/device/ and at file cid push long and use the hex editor.
BOOTLOADER: The Verizon phones accept ROMs only containing their certificate (it's more complex but let's say it's like that), they are called stock ROM (ROMs coming from brend, original, untouched). To load other custom roms you need to unlock the Bootloader to avoid checks on certifications, and this is possible only if you have a CID 15 and only after rooting phone, and unlock bootloader. Then you will you are able to flash TWRP which is a nice console for upload any kind of rom.
Anyway, anyCID, there is a "workaround" called Safestrap that loads a TWRP console instead of the classic Android operative system (OS).. and it happens when you will reboot from its Safestrap applications: the console will load instead of Android on next reboot, and when you will reboot from Safestrap console, itself will restores Android the next boot. It's the only way to load ROMS when your CID is 11, but only very particular releases (read about down); and the way to unlock bootloader on CID15. We're waiting that someone in future will unlock also the CID11..
the "bootloader" or "download mode" can be opened only from phone switched off by pressing VolDwn+Home and when u sure u're pressing them correctly then press power keeping them pressed(!) until u see the bootloader, press then volume up.
"recovery console" or "recovery" is reached from phone switched off in the same way, but pressing Volup+Home (the power) until u see the recovery.
ROM: it's a file containing usually the kernel, the system with main applications (excluded google apps), some scripts (commands) to cancel datas before installing.
GOOGLE APPS: you have to flash them after flashed the rom (if the rom asking explicitly for them because made without (it means it doesn't contain inside any google apps that may be crucial for booting), or.. you have to flash them if you're targeting the final result (the last flash) and you want have apps updated in your "new flashed phone". It's not necessary when u're in process of root phone/unlocking.
FLASH A BOOT IMAGE/package: it's a file used to replace the bootloader, when it's needed, for example if you are upgrading from Lollipop to Marshmellow the bootloader can't stay in lollipop version, the versions should match, be sure to have both compatible already downloaded.
ROOT: it means gain the administrators privileges to edit system files on phone.
TWRP: it's a smart console to manage the phone with full control, allows to change the Android versions and many other things.
RECCOMENDATIONS:
1) have battery on phone around 100%, looks because it seems that at lower values make the phone react sometime unexpectly (power safe) during operations, that means you may loose after a lot time to figure out what problem occured/process skipped.
2) During the flashing, in download mode, the phone may not be charged from USB, and the PC power is much less powerful then the charger, you may see a quite impressive battery draining even when connected to PC, this is why is better to start near 100%.
3) During update, the USB up/downs may use lot of CPU of your PC due to driver recognition, keep then your Windows "clean" for the process, no apps in backgroud which use lot of RAM and CPU (for example browsers with many tabs opened), so the driver detection could be faster, avoid programming interruptions (for example installing apps in root.bat)
NOTICE: any time u'll use Odin you don't need to change its flags/settings (for example auto reboot), leave them as they are. If you uploaded something wrong/not certifed under download mode and the phone refuses that, you need to switch off the phone and restart in download mode again, it's not up to software Odin in your PC; you can leave it opened.
Odin will check the checksum of files that are loaded, so for big rom files you have to be patient and give it time to read all file.
When Odin is open and USB connected, you have to see the phone connected by COM, if it doesn't connect the phone may be bricked or you have to install the latest Samsung drivers (!! **you can't forget installing them if it's the first time using a Samsung device!!)
HOW IT WORKS:
useful to understand how is reached the goal here to prevent bricks, solve easier problems, find yourself an overcome. This root kit targets to install 3 applications on the phone, then use a temporary "bricked" kernel to allow edit system files and root the phone before it loads all Android, then restore the previous kernel working, and it ends by using applications installed before to install Safestrap into boot, to have a TWRP console even if the phone is locked.
As the Safestrap substitute the normal Android boot, if there is any problem on the process (=Safestrap will not boot when it's supposed to boot = you started it from its application) the phone may brick here, because when Safestrap stars it need to restore Android normal usage: if it will hapen the Android won't load again, the phone is bricked, read in that section how to solve it.
The first application, Kingoroot,it's made for allow the root permission into other two applications, it's a supervisor. If you use it gently and its installation succeded ok in the beginning of root.bat it will be enough for do all the job (even if the main Guide author suggest to buy SuperSUme).
Busybox it's a software that allows Safestrap to install, whothout it Safestrap won't work.
Safestrap it's a simple application, that if used in right way (I failed lot of times, but I always recovered my phone) permits to have a powerful console on next reboot.
IMPORTANT:
Whne in process, wait always that the USB drivers finishing detecting phone and become "stable" (CPU and hard disk aren't working, keep check them to be sure, as well the icon of the phone should appear in Windows resouces). You may need to start from zero if u miss this, a really stupid reason to lose time.
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
PROCEDURE:
1) Open OK3_ROOT_V5.exe in one folder, if you use windows with particular language and not latin chars avoid to extract it on desktop, prefer a path like C:\galaxy for example.
2) Switch off phone, remove SIM card and SD, switch on in recovery mode and wipe data system and cache, then boot to bootloader
2) open Odin, open under AP G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 and wait until it finished read file, connect phone USB, be sure phone is recognized, start flashing. Wait until phone boots, wait until it shows the beginning screen.
3) choose english, then wi fi button down, then skip the connetcion and everything else asked, insert any fake name.
4) When setup ends don't activate Wi fi, go to settings, about, press 8 times build number, get the development menu active, go into it and enable usb debug, wait for popup and allow your PC always, then disable the verify usb application installation in the same menu. The driver may set itself again after this, wait some seconds befor go over and be sure the phone is seen by Windows resources, when you see the icon of the phone on Windows file explorer and the CPU is low again it's time to run root.bat, not before! Go into OK3_ROOT folder, run root.bat, a black old DOS window will open (this is not Odin! Not confuse this window and what you read there with Odin messages, please!) and follow the steps you read in this new DOS window..
it will install apps, reboot in download mode and show you a new Odin window, select NK2_kernel.tar and flash it, now put your eyes over DOS window of root.bat, it should recognize your firmware and after some seconds display a full page of ########, if it doesn't something went wrong, you need to go to recovery console, wipe everything, and flash again the main big flash (=start from zero).
If succeed, and you will read it in the DOS window, as the last step, you have to disconnect USB, pull battery, switch phone on in download mode and flash VZW_BOK3_KERNEL_ONLY.tar with Odin
5) After reboot open KingRoot application already installed, Click The Up Arrows a couple of time until you get to Try It and yes click Try It, then on the main circle, go back with arrow and you will have confirm that is rooted. Close Kingroot, open busybox free app, allow the root access, click on install (even if it start scannig) and wait some seconds, when it say it completed close it. Open Safestrap, allow root, click on install, the app will quit itself, open it again and click on install, it will quit again. Now reboot phone by the power key, hen rebooted open again Safestrap and now you'll be finally ready to click on the button "Reboot to recovery". Before doing it be ready to organize the next step, like files for unlocking bootloader or flashing a locked phone to 6.0.1.
END rooting phone procedure.
BRICK/RECOVERY: if it happens during root, before you upload any other ROM, there may be three ways to solve that:
Pull the battery out (it's almost safe) and:
1) Light: go under download mode and flash VZW_BOK3_KERNEL_ONLY.tar, see if the phones later boot up normally.
Chances are, with "dirty" chache data that lead the phone to brick, you can't start the root.bat procedure again succesfully (use root2.bat to avoid the install of the three applications that supposed already installed). Then you may try to:
2) medium: go under recovery console, wipe data and cache, boot fom there to download mode and flash again VZW_BOK3_KERNEL_ONLY.tar.
Or, if still not successful:
3) Strong: go under recovery console, wipe data and cache, boot fom there to download mode and flash flash full G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 (that means start from zero)
SAFESTRAP WORLD:
WARNING: you should follow at the letter the above process above, any difference may result in a fail of Safestrap recovery to open and phone bricked at samsung logo (+custom). If so don't worry, you have just to start the download mode and flash VZW_BPB1_KERNEL_ONLY.tar.md5 again to see the phone working. But chances you probably now have to repeat all the procedure from zero because your phone is "dirty" and Safestrap won't work more, proceed to what I called "strong" reflashing in brick section.
NOTICE: when you reboot to Safestrap, after Samsung logo, you need to wait 5-10 seconds to see Safestrap.
FLASH FIRE METHOD:
You may prefer to use FF (Flash Fire) to flash your room, it is a app (apk) that needs t be installed on phone when the phone works in normal mode, it allows you to create a list of different "orders" to execute exactly one after the other after you give it the final "ok". The app reboot the phone and starting itself to flash. It may be faster then Safestrap, but when I tried once it didn't work for me, it flashed partially and rebooted before it finished, I had a soft brick and I should restart from zero. Probably it was me pretending to flash something wrong, there is only one way to upload 6.0.1 on a CID11 phone and I did only once with Safestrap.
For dealing with FF you need the phone rooted, after you followed the process above you don't need to install Busybox, neither Safestrap, but you need to find and install SuperSUme.apk, which is another "root manager" program as Kingoroot is, but FF doesn't work with Kingoroot.
After loading kingoroot copy the Flashfire apk and SuperSUme in your phone, install both of them, start first SuperSUme, allow the root, and let it remove Kingoroot in its procedure, when it finished launch FF and let him the root as well.
You need to find these two apk, google them, since SUperSUme is available only paying you should know what you are doing. I used these versons and they worked: supersume-6.0.apk, flashfire-0-50-android-apk-download (notice there is 0.52, but I tested 0.50)
PS: if you feel this useful, please thank me pressing the button

For uploading 6.0.1 to my locked phone I folowed this guide:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I would just add that having the SD card "not recognized" I simply copied files of ROM and GAPPS into the phone folder accessed by Windows resources. And when I reboot to Safestrap I flashed as last step the GAPPS, nothing more to add.
When you wipe Data you actually don't delete the /sdcard folder, so the ROM files are safe there.
if you accidentally delete files under safestrap you can upload them by adb, but it will be really slow (around 500KB/s), here is the command: adb push /path/to/local/filename.zip /sdcard/filename.zip
You may evaluate to flash also this before GAPPS:
Tethering_Fix_Knox_Removal_Slight_Debloat_V2.zip to remove Knox and useless apps from this ROM
If you need to put your default system language (the ROM is in english) download from google MoreLocale 2, open a DOS windows with the path to the folder of root.bat, activate the developer menu (point N°4 of post above), connect the USB, and type
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION

Do you know any details about the new pf4 modem?

no, Im not that expert, here is just a guide to help people into the process..

thank you for the great guide. I was able to root my phone with the clear instruction.
However, I am running into one trouble.
When my phone is setting up the language and etc, it requires me to insert sim or wifi. I can't skip that step without doing one or the other. When I do turn on the wifi, the phone then upgrades itself to android 5.0 but the root is still there. I am using T-mobile sim card.
Is there a way to get around the check up? I made sure to follow all the steps correctly too.

if u're talking about the first beginning steps, after the first big ROM loaded, yes you can skip. Select wi fi button, but after skip all the rest. I've never had to connect to internet or inserted a sim card for the process.
I connected/inserted sim only after the flash to desidered rom

thewebsiteisdown said:
Do you know any details about the new pf4 modem?
Click to expand...
Click to collapse
What kind of details did you want to know? Mine works fine.

Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this

Bryanx86 said:
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Click to expand...
Click to collapse
I added the FF guide

Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?

nachoalt said:
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
Click to expand...
Click to collapse
you didn't read well the first post. Read it back.

Barabba11 said:
INTRODUCTION (don't skip it if you want understand what you are reading)
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Seems like the file name for OK3_ROOT_V5.exe changed. They call it GS5_LOLLIROOT.tar.gz now (must unzip twice to get all the files) but I looks like what is needed is in this zipped file.
Might take the plunge tomorrow so wish me luck, and thanks again for the explanation!

By "run root.bat" in point 4 do you mean "3 - Root Process.bat"?
Thanks for clarifications

Barabba11,
Since you seems to have a genuine desire of helping people, (and because I want to have my phone rooted), I want to comment your instructions and also try to find what I did wrong, since my phone is locked in the black “Samsung Galaxy S5” screen when trying to accomplish step 4 (no worries, I have been there before…).
Here I go…
FILES YOU NEED
Samsung Drivers: No comments here, straight forward thing to accomplish.
From the original post Here, under “Installing PB1”:
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
{
"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"
}
From the same previously mentioned post, now under “Rooting Instructions”:
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
Then, under “crc” folder you will find:
And finally, “System” folder is empty.
At this stage my series of comments:
1. I don’t see anything called OK3_ROOT_V5.exe mentioned in step 4 of your procedure. I assume you’re referring to the zipped file GS5_LOLLIROOT_BLACKCAT.7z but since almost every suggestion here indicates to read thoroughly, I don’t want to miss any detail. Can you please confirm if what you call OK3_ROOT folder is the unzipped GS5_LOLLIROOT_BLACKCAT.7z?
2. I don’t see anything called root.bat in the unzipped folders above, mentioned in the same step 4. Can you confirm which one of the .bat files are you referring to? Is it 1 - Install APK's.bat, 2 - Flash NK2.bat, 3 - Root Process.bat or 4 - Flash PB1.bat?
Since my phone got stuck in the black screen when reaching this point and I had to get back to square 1, I’ll wait for comments.
Warmest regards, it is really appreciated what you do here, it is just my humble opinion that detailed instructions in plain English, with proper file names, punctuation etc, would save this world a lot of time and frustration, leaving you developers more time to deal with the important stuff, I’ll be happy to help rewriting or reviewing anything in this regard.
PD: Not sure if the images are going to appear, I don't see them in the preview. If that's the case, you can check here

This thread is out of date since the rooting method has entirely been changed

Can you please indicate where can I find the updated method? Rgds

I'm sorry for the inconvenience, since they changed the main files I'm disoriented too. If they removed the bat files it means everything is different now, and honestly I'm hearing now about that..
Would know too why they changed the process, it was working, complicated but working, and I still have my phone at unrooted Android 6 waiting for a major update, like root or Android7.. I don't have enough time to experiment something that may appear useless for me later.
Anyway reading the instructions may warn you about different aspects to consider.. and reduce the waste of time if some conditions happened.
Kindly write in this thread they way you proceed and I'll have care to edit the first post reminding it. Thank you

Great thread, need some help still
How do I check my chipset when I don't have root access? I downloaded xplore but I need root access to check the root folder.

go into the xplore settings and change the root inside, I've no-rooted phone and I can see it. In the beginning, it's just a way for them to push you install rooting apps

If I root my S5 900V using this method can I then reflash it with 4.4.2?

Nextbook Ares 8A with Android 6.0.1 root solutions

UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"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"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks

@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks

Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks

Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.

How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.

adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"

Would love to see some break throughs with this device aswell. Cheers to any one working in it.

Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en

Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.

martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:

This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk

vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???

cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk

vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?

cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk

Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it

[GUIDE] [K06NTC_A] Just5 Freedom X1 - Flashing Nougat (7.0) & Rooting

Just5 Freedom X1 - Flashing Nougat (7.0) & Rooting
Continue at your own risk, I am not responsible for any damages done to your device.
Some notes before we start off; I've done this on a device with unlocked bootloader, and fall into category of accidentaly formatting everything. Purpose of this thread is to help people who can't find any resources from Google due to lack of any developers or support on it.
First, obtain the firmware for Nougat from NeedROM (requires registration). Unrar the archive using your favourite archival utility such as 7-zip or WinRAR.
Obtain SP Flash Tool, as you'll be needing it to flash your firmware. Choose the "Download" section, and power off your phone entirely. Choose the scatter file from where you extracted your firmware, in this case MT6753_Android_scatter.txt. MAKE SURE YOU SELECT DOWNLOAD ONLY SO YOU WON'T LOSE EVERYTHING INCLUDING NVRAM. Use the "MTK_AllInOne_DA.bin" Download-Agent, and click "Download", and connect your phone via usb to your PC. The tool should start flashing. If you've failed this step, you can retry it with different DA's, or reach out to me.
Once you've flashed, it should take a little while longer to boot than usual, that's okay, as you've just installed a whole new system. If you managed to screw up your NVRAM by formatting everything and have "Invalid IMEI", get MAUI Meta (v9) and attempt to boot into META mode. Select "IMEI Download" from dropdown menu, and from here on it should be super obvious what to do.
OH NO! Modem exception with META tool and can't detect SIM! (unknown baseband)
Remain calm, reflash the firmware with Format All + Download, this will reflash your baseband. Once it's finished, boot into META mode and rewrite IMEI, and you're ready to relaunch your phone. You can do it before or after first boot, doesn't matter.
That's great, but I miss my root!
You may already be aware, that easy root methods such as KingRoot or Framaroot aren't working on these NeedROM firmwares, fortunately you can still root (and without breaking SafetyNet!). You need to obtain Magisk from XDA (get the apk version). Insert your boot.img to your phone's SD card, and select it using the app. Pull the patched image from your phone's SD and boot into fastboot. From here, I suggest you test if it won't brick your device first. To do that, type in fastboot boot patched_boot.img and you should now have temporary root until you restart. You can verify root by either getting a third-party application from the Play Store, or checking the Magisk application. If you got root, you may reboot into fastboot, and type following to make it permanent; fastboot flash patched_boot.img. Congratulations! At this point you've just rooted your device using Magisk, and it doesn't even trigger SafetyNet!
Should you have additional questions, feel free to ask me.
Thank you for reading, hope it helped you either save or update your phone (or root ).
Here's proof of it working;
https://i.imgur.com/lmYC3dr.png (yes I'll spare your bandwidth, by not making it load a huge image)