Database Info

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"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"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

[ROOT][FIRMWARE][BOOTLOADER][RECOVERY] RCA Viking Pro (RCT6303W87DK) One Stop Shop!

I am not responsible for anything that happens in your life. Including what happens as result of following steps in this thread.
Hello all. After a long journey here, we figured a new thread would be in order for new comers not to have to read through fifty pages of information. Here you will find firmware to fix or update your Viking Pro. You will also find root methods, bootloader unlock and custom recoveries for this tablet. Lets start with ROOT...
Method 1: Kingroot. Kingroot works on this device. you can find it here. It's pretty straight forward, just download and install the apk and root.
Method 1.5: SuperSu. Kingroot works but it's not the best root out there. once you have root, follow the instructions here and Kingroot will be replaced with SuperSu.
Method 2: Su flash-able ZIP. This method requires you to follow steps in posts No. 3 and 4. Once you have custom recovery installed, You can flash This.
This method is a bit redundant. However, it does allow you to make a completely stock unooted backup of your rom before making any changes.
Check out posts 2, 3, 4 & 5 for the good stuff.
I'm gonna go ahead and thank everyone responsible and If I forgot to mention you, please don't hesitate to tell me and I will correct the situation:
@Bogram (Edited the bootloader so it could be unlocked on x.12.x versions)
@Jacube22 (Duplicated the method from Bogram to make the bootloader on x.9.x versions unlockable)
@vampirefo (Compiled a compatible CWM recovery for us)
@ewilley2008 (Found most of the firmware)
@mayzemay (Initial root thread)
@NepoRood
@jerryvail35
@Sir Jaxxy
@Snigglez
@Spartan Legionnaire
@bobl61
@csla
@Chainfire (For root)

FIRMWARE
There are two main branches of development for this tablet. It is very important to know which one you have because they are incompatible with each other. I personally bricked my first one with firmware from a x.9.x while mine is x.12.x. How do you check? Simple. In your build number, you can find it in "About tablet" in Settings or in the text at the top of the recovery screen. It's at the end of the number and it will look like 1.12.30, 10.12.20, 2.12.20, 1.9.1, 1.9.5, 10.9.1...etc The number in the middle is the important one.
Steps(Windows): For step 2 you will have five seconds. Preloader mode is only active for five seconds. So read first!
1- Extract the drivers to the destktop and open the device manager.
2- Plug your tablet in as such: turn off the tablet. Plug a male to male USB wire from the computer to the USB port on the tablet. now plug the power wire into the tablet. now very quickly in the device manager locate the new device and right click on it. select "update driver software" then select "browse my computer for driver software" and "browse". Now navigate to the driver folder, select the "CDC" folder and click on "OK" the "Next". The driver should install at this point. Once that is done, unplug the power cable from the tablet.
3- Extract the firmware and the sp flash tools to your desktop.
4- Start the sp flash tools and where it says scatter file loading click and navigate to the folder where you have the firmware and load the scatter file. You will see the firmware get loaded and a checksum check.
5- Once that is done, uncheck the preloader from the list and click on the download button.
6- Plug the power cable into your tablet. At this point the sp flash tool will load the firmware into the tablet. DO NOT UNPLUG ANYTHING UNTIL THE SP FLASH TOOLS SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE OR YOUR TABLET COULD BE HARD BRICKED AND UNREPAIRABLE.
7- Press the reset button and turn it on. Done!
Drivers: https://drive.google.com/file/d/0Bz4bOoJ_E5XzRWJCbGFINndmVmc/view?usp=sharing
SP Flash tools: https://drive.google.com/file/d/0Bz4bOoJ_E5Xzb0g3ZnlEcHE0bEE/view?usp=sharing
Firmware x.9.x:
RCT6303W87DK-ANDROID5.0-V37-V10.9.21-NFC-V2.3LA-20150820
RCT6303W87DK-ANDROID5.0-V32-1.9.1-20150409
Do not flash the preloader for the Surf1001 versions!!
Firrmware x.12.x:
RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316
RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121
SURF1001-ANDROID5.0-V11-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151116 (Use method No.2 for root)
RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106
SURF1001-ANDROID5.0-V07-V7.15.0_T8515B_V6.3_SAMSUNG2G_20151016
RCT6503W87DK-ANDROID5.0-V66-V20.12.20-B-Camera-2M_PCDDR_V6.3-20150928
RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811
Sources:
http://laurentiumihet.ro/technology/...test-versions/
http://www.needrom.com/download/mtk-...er-v5-1453-03/
http://pan.baidu.com/share/home?uk=2...ategory/type=0
http://baiduyun.57fx.cn/so-result.ht...7DK&type=share
And Google of course...

Bootloader
So the bootloader on this tablet is locked. To unlock the bootloader, in a perfect world, you would usually boot the tablet in fastboot and type the command "fastboot oem unlock" and then follow the instructions on the screen. However RCA did not code in the volume keys in fastboot mode so it was impossible to unlock the bootloader that way. So our friend Bogram edited the bootloader and now the volume keys are not needed. What swell guy eh?
Unlocking your phone’s bootloader completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
So what you need is a scatter file like this one and a patched bootloader like these: x.12.x or x.9.x .
You will also need ADB & Fastboot and the drivers.
1- Just like in the FIRMWARE section, install drivers and SP Flash Tools.
2- Open SP Flash Tools and load the scatter file and in the line where you see "uboot" on the right click in the blank field and a window will pop up. select the patched bootloader. Make sure it checked and click on the "Download" button.
3- Now plug the male to male USB cable and then plug in the power. SP flash tool will flash the bootloader and then show you a nice little green check mark.
4- At this point you need to unpack the adb folder from the RAR file and place it in the root of you hard drive(C: ) then open a command prompt and nvigate to you adb folder (cd c:\adb) and leave it there for just a second.
5- On your tablet unplug the power wire, hit the reset button in the back and boot it into recovery mode by pressing and holding the volume up and power buttons together until the RCA splash screen comes up then release them.
6- In recovery, use the volume keys to navigate to "reboot to bootloader" and use the power button to select.
7- At this point your tablet will be in fastboot and your computer should detect it and install the driver. If not, the driver is in the "Android" folder in the driver files you extracted.
8- In your command prompt you left opened earlier, type "fastboot oem unlock".
9-Your tablet will do some magic, summon a demon, banish it to the depths of hell, reboot a couple of times and then it will have a unlocked bootloader.
10- Done. now you ca move on the next post and flash recovery.
Bogram also created a tool that patches the bootloader automatically should you have a different version we don't know about or what not...
Code:
RCA LittleKernel Unlock Patcher
By Bogram (http://forum.xda-developers.com/member.php?u=7182821)
Tested models:
RCA Viking Pro (RCT6303W87DK), RCA Maven Pro (RCT6213W87DK)
USE THIS TOOL AT YOUR OWN RISK, NO WARRANTY IS PROVIDED.
License: http://www.gnu.org/licenses/gpl-3.0.html
Input file:
W:/HaxeToolkit/projects/patcher/lk.bin
Wrote to:
W:/HaxeToolkit/projects/patcher/lk_patched.bin
Press any key to exit.
https://drive.google.com/file/d/0Bz4bOoJ_E5XzSnJ2R3d2NkxlU0k/view?usp=sharing

RECOVERY
This section depends on a unlocked bootloader. If you did not unlock your bootloader in the previous post, do so before continuing to this one.
So what you need is a scatter file like this one and a recovery.
CWM + Carliv compiled by vampirefo: (x.9.x)Clockworkmod recovery (x.12.x)Clockworkmod recovery
TWRP V3.00 compiled by Neporood: (x.9.x)TWRP V3.00 recovery (x.12.x)TWRP V3.00 recovery(Coming soon)
- Open SP Flash tool and select the scatter file.
- in the recovery line, on the right side in the blank field, click and select your downloaded recovery.
- Click on the download button.
- Make sure your tablet is off, plug the USB cable first and then the power cable.
- SP Flash tool will flash the recovery and show you a lovely green check mark.
- Once that is done your recovery will be flashed.
** The stock system has a file in the system folder called "recovery-from-boot.p". this file flashes stock recovery randomly at boot so with a rooted system, navigate to the folder with a root capable explorer and delete the file so that your new recovery stays there.
** When rebooting from recovery, cwm will tell you to fix root. Don't. Select no every time.
For thos of you who want a file explorer in recovery, You can download this Aroma installer flashable
It's a nice tool to have...
Aroma comes from here: http://forum.xda-developers.com/showthread.php?t=1646108

ROMS
Not yet but soon.....

I'd swear I've seen all this somewhere before... lol
Good job, brother!

Now , let the roms...begin.....

woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.

Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.

thevypr said:
Any plans to make a thread like this for the RCA Maven Pro (RCT6213W87DK)? It'd be really swell.
EDIT: Actually, with those sources you posted, I actually might be able to do this on my own.
Click to expand...
Click to collapse
I've got a Maven, and I've already done the porting. I'll be posting a guide tomorrow morning sometime. For now, I've sent you a PM with links to the firmware. Check your firmware version, mine is V36-1.9.21 (as long as you have the "9", you should be ok) The zip file has everything in it, preloader, scatter, custom recovery, etc...
Maven Guide is up, find it here

Synman said:
woot ... just in time as I brought my Viking Pro home from Wallyworld Saturday night.
Any thoughts on ADB? I couldn't make it all the way through the other thread and eventually just gave up.... ended up figuring out Kingroot on my own and then just enabled ADB over wifi. Would much rather have a wired ADB solution as moving an APK (I'm a developer, duh) over wifi can be somewhat s-l-o-w.
Click to expand...
Click to collapse
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..

smartmanvartan said:
Still working on adb... Trying to make a flashable ROM with the fixes... No timeframe tho..
Click to expand...
Click to collapse
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.

Synman said:
I can't get the port(s) to light up under OSX. I've tried a couple build.prop changes, plugging in micro usb, usb type a, power connector, and various combinations but none of them appear to trigger registration of a usb device of any kind on the host machine.
I can't even get simple stuff like MTP to work.
Click to expand...
Click to collapse
Time is my issue but I'm looking at two things. there is a firmware package i found on the Chinese server for a tablet with the model number rct6603w47dk with the same board as the viking pro but with a 8163 instead of the 8127. i think its doable to port over to our tablet. it is android 6. also the maven pro(rct6213w87dk) which is really close to our tablet with the same board but a larger screen, has adb working on it...

You should be getting a reaction through the micro usb port... on windows it shows up as a malfunctioning device.

i get nothing when sniffing the USB bus on my MBP.

Synman said:
i get nothing when sniffing the USB bus on my MBP.
Click to expand...
Click to collapse
I does the same thing on Ubuntu 14.04, absolutely nothing shows with "lsusb" in the terminal, unless it's in fastboot mode. You can use fastboot to flash the device, if you don't have access to a Windows machine...

I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work

Jacube22 said:
I tested the new 1.9.3 firmware on my tablet... and it just shows a black screen.
DO NOT FLASH IT. it didn't work
Click to expand...
Click to collapse
Ill find you guys some newer software that boots...

What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section

e923 said:
What's the difference between sp_drive_v2.0_finally & mtk_sp_drivers_v2.0
Because I got the sp_drive install but having a problem with the mtk_sp , it keep popping up as incompatible software.... I'm stuck on the boot loader section
Click to expand...
Click to collapse
What version of Windows are you running..the difference is the drivers are signed or unsigned.. This matters more on newer versions of Windows.

[Root] lenovo k4 note running on marshmallow (6.0) official rom

This procedure has been tested on LENOVO K4 NOTE MARSHMALLOW (S219) and it worked perfectly fine.
i posted this thread since the previous procedures only covers rooting prior to S218.
verified working on s219
DISCLAIMER:
I JUST FOLLOWED THE PROCEDURE PROVIDED BY "AYAN CHOUDHURY" ON YOUTUBE CHANNEL SO CREDIT GOES TO HIM.
IF SO HAPPENED THE PROCEDURE WAS MADE BY ANOTHER DEV AND WASN'T QUOTED PROPERLY BY MR. AYAN COUDHURY. MY APOLOGIES AND GIVE CREDIT TO THE ORIGINAL OWNER OF THE PROCEDURE
I WON'T BE RESPONSIBLE FOR ANY DAMAGE, SOFT BRICK, HARD BRICK, AND OTHER INSTANCES FOR YOUR DEVICES AS IT WORKED PERFECTLY FOR ME 3-4X BEFORE POSTING THIS THREAD.
original vid: https://www.youtube.com/watch?v=fPx8QWnYLNo
Before we start:
Here is the details of my handset
Model: Lenovo K4 note (PH) [MTK MT6753 8CORE 1.3GHZ 3.00GB RAM]
Model #: A7010a48
OSv: marshmallow 6.0
Android security patch level: April 1, 2016
Kernel ver: 3.18.19+ [email protected] #1, su jun12 18:27:10 CST 2016
Build number: A7010a48_S218_160612_ROW
Step 1:
download all necessary files.
all files and links are not mine and credit goes to the owner of the files
adb tools : https://drive.google.com/open?id=0B16daNyhWTx1djhqSkJ6QkFKaUk...
recovery(i.e TWRP) : https://drive.google.com/open?id=0B16daNyhWTx1RlB0U01sUkVHMjg...
aroma file manager: https://drive.google.com/open?id=0B16daNyhWTx1TmJqRmxIUUI3YUU...
Super Su : https://drive.google.com/open?id=0B16daNyhWTx1V2ZobTI0RVpKQ1E...
xposed installer : https://drive.google.com/open?id=0B16daNyhWTx1N2RDc2Y4TzlWaWM...
xposed framework : https://drive.google.com/open?id=0B16daNyhWTx1QmlRTHhXOUMydDQ...
step 2:
a. back up any necessary files from your handset.
b. since some computers doesn't show your lenovo k4 note while on recovery mode, it is imperative to put aroma file manager and supersu on your sd card. "do not extract. just copy them as it is"
take note that the next step will definitely hard reset your device.
step 3:
a. enable developer option on your handset. go to system settings/about and click build 7x or as it says "you are now a developer"
b. go to developer option do this two things
enable oem unlock
allow usb debugging
c. once you are done please connect your device to your laptop
step 4:
a. run adb server (go to adb folder, shift+right mouse click and choose open command window here.
b. it will prompt you to allow your pc to connect/control your devices just click YES
c. on your command window, type ADB DEVICES (it will detect your lenovo k4 note)
d. once detected type ADB REBOOT-BOOTLOADER (your device will reboot)
e. once rebooted, type FASTBOOT DEVICES to verify if you are already in fastboot mode
f. if connected proceed to step 5. if not please repeat procedure
step 5:
a. once connected go to adb folder on your computer. you will see a file named unlock recovery.bat
if not, copy this text
call adb.exe devices
call adb.exe reboot bootloader
call fastboot.exe getvar all
call fastboot.exe oem unlock
call fastboot.exe format userdata
call fastboot.exe erase recovery
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img
call fastboot.exe getvar all
call fastboot.exe reboot
echo done successful please press any key to continue
echo disconnect your phone and press power button untill phone reboots
pause
Click to expand...
Click to collapse
to notepad and save as batch file, name it as UNLOCK_RECOVERY.bat
b. click the UNLOCK_RECOVERY.BAT then it will ask you on your device to confirm, (will add screen shot later on) just press volume up button
c. once the process has been done, (will take few seconds) extract recovery.img to adb folder
d. go to your previously opened command window and type
FASTBOOT FLASH RECOVERY RECOVERY.IMG (the one you extracted)
step 6:
a. once flashed, disconnect your device (it will show a tiny text telling you transmission ok)
b. press and hold the power button for few seconds to turn off the device
IT IS IMPERATIVE THAT YOU WON'T TURN ON THE DEVICE UNLESS THE NEXT STEPS ARE DONE. IF YOU ACCIDENTALLY TURNED ON YOUR DEVICE REPEAT TO STEP 1.
c. press and hold vol up+vol down+ powerbutton simultaneously for few seconds, once you felt a vibration, release power button whilst still holding the vol up and down button
it will show the lenovo screen then go black. (don't worry it means you successfully flashed recovery.img)
d. connect the device to your computer
if lenovo shows on your device, now is the time to recopy aroma file manager and supersu. if not just wait for the screen to turn back on.
e. once twrp recovery is on, go to mount and check SYSTEM. (do not touch anything aside what i unstructed)
d. go back to previous menu and go to install
install aroma file manager and wait for it to finish
f. once installed it will go directly to aroma file manager, go to system folder and scroll down. look for recovery-from-boot.p and delet it
g. once deleted exit aroma file manager (button can be found on right corner)
h. go back and install beta supersu which you copied. (browse sd card)
i. once flashed, reboot system,
step 7:
a. if you made it this far, then you are almost done.
b. just finish the lenovo start up.
c. once done, connect your device again on your computer and copy xposed apk and xposed arm to internal or sdcard
d. install xposed apk
e. turn off your device
step8:
a. reboot to recovery (press vol up and down and power button simultaneously, once you felt a vibration release power button whilst holding vol up and down button. lenovo screen will show and it will eventually go to twrp recovery)
b. click install and install xposed arm
c. onced install. reboot system.
THERE YOU GO... YOU ARE DONE. YOU CAN VERIFY ROOT BY DOWNLOADING ROOT CHECKER FROM GOOGLE PLAY STORE.
WELL I WAS FORCED TO ROOT MY K4 NOTE JUST TO PLAY POKEMON GO.
I WILL UPLOAD SCREEN SHOT ONCE I ALREADY COMPILED THEM. THANK YOU
IF YOU LIKE AND HELPED YOU A LOT PLEASE HIT THANKS AND LEAVE A MSG.
IF YOU HAVE QUESTIONS, JUST COMMENT IT HERE.

Thanks it worked. I was about to complain when twrp recovery does not show up. BUT IT WORKED THANKS

xposed isn't necessary to root the phone. Am I right? Maybe you should explain that in the OP. You'll get people confused down the road if they don't already know what they're flashing.
Sent from my f320 using XDA Labs

Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?

infected_162k said:
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
Click to expand...
Click to collapse
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:

infected_162k said:
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
Click to expand...
Click to collapse
hi
will it erase internal phone memory (i mean after flushing ROM can i get my data using any recovery software)
i am also using same s219 Rom model lenovo k4 note phone.
Actually i deleted some files unexpectedly from internal memory but i want them back, so i tried many ways but no software is identifying internal memory as a drive. I tried to root using root apps but marshmallow not allowing.
i found this topic, but i have only doubt is after flushing the rom can i recover my data using any recovery software?
Thanks in advance

thank you so much!
now to answer some queries and give thanks...
@Duffy144: glad you like it.
@Bdwilk: thank you for the input, i will do that.
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
@anvesh.k yes it will delete all files as the procedure requires you to factory reset your handset.

Rooted K4 Marshmallow
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.

Can someone confirm if this works with 2 gb / 32 variant?

RK_D2502 said:
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Click to expand...
Click to collapse
Can you recovered old data after rooting the device?

anzei19 said:
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
Click to expand...
Click to collapse
Amm, about that memory leak thing, i basically know what that is cause it was a huge problem in my father's phone(gionee m3). But i exactly don't know how to know if it's still there or not as I use messenger hardly 2-3 times a week. guide me about this so I can tell you exactly.
Another thing that will help other users: I have to factory reset my phone due to a google error ( unable to communicate with Google server). I was not sure about root and xposed will be gone or not. But here is the result : lost both, root and xposed. Just flashed both again, super su and xposed framwork, worked

anvesh.k said:
Can you recovered old data after rooting the device?
Click to expand...
Click to collapse
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Sir Ansei, everything is fine except 1 minor issue, when rebooting to TWRP, I often get the black screen. Power cycling the phone works. Any ideas?

RK_D2502 said:
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Click to expand...
Click to collapse
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...

infected_162k said:
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
Click to expand...
Click to collapse
Thanks for understanding my problem

call fastboot.exe flash recovery recovery/recovery.by.gursewak.img - needs to be edited? make sure path is correct and image name.
call fastboot.exe flash recovery recovery.img
Just put recovery.img in the same folder

I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!

sujitmohanty2012 said:
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
Click to expand...
Click to collapse
you should install fastboot driver

setpam25 said:
you should install fastboot driver
Click to expand...
Click to collapse
@setpam25 Is there a specific driver for that.? If yes, could you please share the link to download that?
My system currently has the lenovo usb driver 1.16, windows 10 mtk vcom preloader & ADB interface driver (by google) properly installed!

Does this work on s230 update marshmallow

Please help me,
I am stuck there until I reboot system

[How-To] Root (Ulefone Armor 6)

Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.

Extosis said:
Story:
I recently bought the, Ulefone Armor 6 Android phone. Didn't do much research into rooting before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Rooting procedure:
1. Get a local copy of the boot.img file from the Ulefone website (To make things simpler for you, Ulefone.com/index.html > Scroll down and click on "download" > Select your device model "Armor series" "Armor 6" > Scroll all the way down and click the download button for "The latest rom".)
2. Now you are at the google drive folder from Ulefone, with the files you need. Select EU if you have the EU version, or Non-EU for any other country.
3. Download the compressed file of your choice EU or Non-EU. (Ex. I downloaded the one for Non-EU which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
4. Open the file in your favorite archiver software, 7-zip, winrar, etc.... open the first folder in the archive, and extract "boot.img"
5. Download, "Magiskmanager.apk" from their Magisk Manager, and install it in your, Armor 6 phone.
7. Pass the, "boot.img" file from your computer to your cellphone. Preferably the "downloads" folder.
8. Open up Magisk manager, and click install 19.3 (or what ever is the current version) then click "Select and Patch a File".
9. Find your "boot.img" file and patch it with magisk manager.
10. After magisk manager has patched your file, pass the patched file, back onto your computer.
11. Now, in your Armor 6 phone, go to settings, scroll down to system and click it, click on about phone, and then tap the crap out of build number, until you become a developer.
12. Go back from about phone, click on developer options, and tick on "OEM unlocking".
13. Scroll down and tick on USB debugging.
14. Download your ADB tools with fastboot from android/google.
15. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
16. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
17. Once you have unlocked your bootloader, reboot the phone "fastboot reboot", wait till the phone boots up, go through the set up process, enable USB debugging again (Step 13), install magisk manager again, adb reboot bootloader in adb command prompt.
18. Once in fastboot mode again, flash the patched boot.img file.
fastboot flash boot boot.img
19. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense.
Click to expand...
Click to collapse
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])

PoochyX said:
Nice work around for a phone that doesn't have Twrp
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
Upon doing a bit more research, the phone actually has TWRP & a TWRP fork.

How do we know we can trust you? I'm a nubee as I've said.

SteeleB89 said:
How do we know we can trust you? I'm a nubee as I've said.
Click to expand...
Click to collapse
Then this isnt for you and stick with stock... Stock honestly works just certain people want greater freedom with thier phones only issue is with that you yourself at greater risk of breaking something and wouldn't know how to fix it and in situations like that factory restores wouldn't even save you because the system partition doesn't go back to the way it was with a factory restore
Sent from my SM-J327P using Tapatalk

I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.

SteeleB89 said:
I understand and accept the risk. I'm asking if this is a legit fix or some attempt to put malware on my phone.
Click to expand...
Click to collapse
Well to start with, I didn't attach anything in this thread, only photos.
1. You bought the phone, a phone that is made from a Chinese company, odds are that it already has malware, backdoors, or things you don't want on the OS.
2. Like I said, I didn't attach anything for you to download, so I am not infecting you with anything. Fastboot even comes with Google SDK.
3. Magisk is a wide known group who release root for the public to download/install. Just like TWRP, clockworkmod, cynaogenmod, etc...
4. If you don't feel comfortable doing this process, then like stated above, you should probably feel safer staying with stock & no root.
As I am sure, everyone who mod their devices are fully aware of the consequences of exploiting their devices. Brinking, killing, or messing something up.
Cheers.

For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?

A.Fitz said:
For the life of me I cannot get the drivers to install. I've tried on Windows 10 and 7, but can't get fastboot to recognize the device. ADB works just fine, but Windows won't recognize the device when in recovery. I tried the official Ulefone drivers for Windows 10 and 7, as well as the MTK/VCOM usb drivers through manual installation.. How did you get it working? What other drivers are you using?
Click to expand...
Click to collapse
I have literally used the "driver installer" from the Ulefone website. Install the MTK/VCOM Drivers.
Adb gets detected in TWRP & Fastboot is found on my computer just fine.
My suggestion would be to check if your anti-virus (if you have one) if it's blocking the drivers from being installed.
Ps: I have the latest Windows 10 1903 x64 Edu and the drivers work perfectly.

Will try at end of month and tell you guys the result later.

Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.

Stabys said:
Hi!!!
Thanks for the tutorial. I managed to root my Ulefone Armor 6.
Just one thing, maybe it will be nice to add in the tutorial (suggestion): Magisk generates another boot.img file, called magisk_patched. That is the one to be used on step 17 (rename it before).
One question. If I do a factory reset, will the phone remain rooted? Can't remember for the life of me from past roots I've done.
Click to expand...
Click to collapse
Oh most definitely. I am actually going to add more detail to this tutorial once I have the free time to do so. This tutorial was mainly supposed to be like a rough idea on how to do it. However yes, I did a factory reset not to long ago and root was maintained.
Update:
Added more information and cleaned the thread up.

Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.

Stabys said:
Well, IDK if that's a common understanding or even if it's going to happen to everybody but.. Ulefone released an software update that undid the root and reinstalled every single native app that I had uninstalled. I tried rooting again, buuut they did not put the new rom in their website yet, so my phone got stuck in boot XD. So I reinstalled the ROM available using SP Flash Tool (thank god that worked, lost some information but that's fine).
I'm not sure if I'm going to root it again when they release the ROM in the website.. I wanted root so I could make Cerberus an native app, but even though I can do it, if the phone is reset Cerberus loses my account information, so it is no use to me.
English is not my native language, but I guess that's pretty understandable
@edit: They did not release the new rom in the official website.. I did not look into the Mega or Drive link actually.
Click to expand...
Click to collapse
Yeah, I think their new rom has a few security updates as well as other updates.
I haven't updated as of yet, because I fear I will lose root. However if I ever do, I'll update everyone if successful.
I understand you very well too.

Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.

Stabys said:
Hello again..
I've decided to stay on 2019.03.29 update.. Just to be able to uninstall those da** native apps..
I'd appreciate if you post here if or when you have any news about root in the latest wireless update.
Then again, can't say thanks enough.
Cheers.
Click to expand...
Click to collapse
Hello it's been a while.
I have updated to the latest version by Ulefone for our Armor 6's.
Version: 2019.06.05.
I was able to root it again, using the same method in this thread.
As for the native apps, I haven't tried to remove them, however I am sure it is possible to.

HELP!
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Extosis said:
Background:
So, I recently bought the, “Ulefone Armor 6” Android phone. I didn't do much research into rooting the phone before I bought it, however tonight I did and couldn't find any solution. So I made my own.
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
Prerequisites:
Make sure you have drivers installed, here.
Rooting process:
1. Obtain a local copy of the, “boot.img” file from the stock rom archive, which can be found on the, “Ulefone” website.
2. Download the compressed file of your choice, "EU" or "Non-EU." (Ex. I downloaded the one for, "Non-EU" which is, "Armor_6_RF1_V01_user_20190329.tar.gz")
3. Extract the downloaded file in the location of your choice, using your favorite archive extractor (7-zip, winzip, winrar, etc...)
4. To begin the root process, Download the android app or .apk file "Magiskmanager.apk" from the Magisk Manager website, and install it in your, Armor 6 device. (Note: the Play Store does not have the, Magisk Manager app.)
5. Now pass the, "boot.img" file downloaded earlier from your computer to your Armor 6 device. Place the "boot.img" file preferably in the "downloads" folder of your Armor 6 device.
6. Open up the Magisk Manager app, and click, "install 19.3" (or what ever is the current version is) then click, "Select and Patch a File".
7. Locate your, "boot.img" file you placed in your downloads folder, and patch it with Magisk Manager. (Note: This step will create another file named, "Magisk_patched.img" in your device.)
8. After Magisk Manager has patched your file, pass the patched file from your downloads folder, back onto your computer. (Note: Not necessary but customary, to rename the patched file to, "boot.img")
9. Now, in your Armor 6 phone, go to your settings, scroll down to system click it, click on about phone, and then tap the crap out of build number, until you have become a developer.
10. Go back from about phone, click on developer options, and tick on "OEM unlocking." also scroll down and tick, "USB debugging."
11. Download ADB tools with fastboot from Android/Google.
12. With the phone connected to the computer, open up the folder where ADB is located in command prompt and type, "adb reboot bootloader"
13. Now that you are in fastboot mode, type the following prompts into the command. (NOTE: the following commands will WIPE your phone clean to stock, so backup any important files/documents before you wipe.)
fastboot oem unlock
OR (if the first one fails, try the second one)
fastboot flashing unlock
14. Once you have unlocked your bootloader, reboot the phone, "fastboot reboot", wait till the phone boots up, go through the setting up process, enable USB debugging again (Step 13), install magisk manager again, and "adb reboot bootloader" in adb command prompt.
15. Once in fastboot mode again, flash the patched, "boot.img" file. (Note: This command will not wipe your device.)
fastboot flash boot boot.img
16. Reboot the phone once more, open up magisk manager, and enjoy root.
A lot of steps yes, but simple easy to do.
Note: that the basis of my instructions on telling you what to do is my assumption of you the end user having basic if not full knowledge of what I am talking about. Because I wont be providing help for basic knowledge, if that makes sense. I do not plan on making a video as this tutorial is mainly meant for users who already know what of the majority they are doing with the tools they are using. If anyone wants to make a video feel free to share it here, I will added to the thread. thanks!
UPDATE 1.0:
I organized a thread on this link, with everything needed to root, twrp, and stock image.
UPDATE 1.2:
Re-organized this thread. Removed a few steps. Added more detail to this thread specifying a few things.
Click to expand...
Click to collapse

babyboy_legolas said:
Guys, I need some help here. For some reason I'm not able to find the file in the downloads folder. When i go to Magisk, the file is there, however I cannot find it with any file explorer or through the PC. Any help here??
Click to expand...
Click to collapse
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?

babyboy_legolas said:
After I did the last flash with the boot.img, the phone keeps rebooting and rebooting. its like something on that image is wrong. the thins is, giving the fact the phone is continuing booting. How can i put it again to flash the original boot.img?
Click to expand...
Click to collapse
To put the phone in manual fastboot mode, you have to power off your device first. By pressing both, "power button + volume down button" until you feel the phone vibrate.
Once the phone vibrates, quickly press, "Power button + volume up button" to view the fastboot/recovery/normal boot menu options. To select fastboot use the volume buttons.
Volume up = select
Volume down = move down through options.

Hi!
Oh I tried it once more now and managed to do it.
I did it with the ROM from Mega (20190605).
Thanks again!

How To Guide The Complete Noob Guide to Rooting Moto G Stylus (2022) XT-2211 Mediatek Variant

This is NOT for the 2021 Moto 5G Stylus. This guide is exclusively for the Moto 5G Stylus 2022.
This tutorial is for people like me than just got the Moto 5G Stylus XT2211 (Factory Unlocked Mediatek Variant) running on stock Android 11. I got this phone literally Sunday brand new in the box from Best Buy (Yes, I took a Chance and copped it from them hoping it could be bootloader unlocked). This is a hand holding guide for the Noobs that really are intimidated by rooting their device, so even though there are other guides up, this one is for people like me that need every step explained.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I've been rooting Motorola phones now for five years, so I'm pretty handy as a script kiddie (I know bad word) in doing it. I also was pretty active with my last phone over at the Moto One 5G Ace Forums, so here's to hoping my progress with these phones continues.
Thanks to Android 11 being System As Root with all these new super partitions running amuck (like Android 10), you cannot get Write access in the actual system files. So even when you achieve root, you can't do much without getting a script and accessing those partions. @lebigmac and @munjeni have been constantly working on that. Drop by their respective threads on R/W access and beta test his script so he can get more knowledge about how Moto phones work so we can have easy R/W access like Xiaomi and Huawei phones.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Mediatek variant and NOT the Qualcomm variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similar Moto One 5G Stylus (2021) and it bricked. This is the MILAN version.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Firefox or Chrome (I used Firefox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Make sure the code you're copying and pasting is correct. If it is incorrect it will not approve you for bootloading unlocking and not tell you the code was missing a letter/number. They are getting sneaky.
***IMPORTANT NOTE ABOUT OEM UNLOCKING GREYED OUT***
If your OEM Unlock tab is greyed out in the Developer Options, just know that Motorola/Lenovo now have some weird timer on that to activate. I had to wait 3 days for mine to activate. Some report it takes longer. Others reported it was 3-4 days. I factory restored, reflashed the firmware, etc. day one just to make sure anything funky that could be put in there was clean and brand spanking new. Not saying you have to do this but there have been varying reports on Moto phones since 2020 about how long this takes. If you're not sure if yours can be bootloader unlocked, get the code from Moto. If it can it will email it to you and from ther ejust wait.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. The Command Prompt will tell you it is locked and you will see "flashing unlocked" on the phone in fastboot once it is done.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore and it will tell you if the bootloader is unlocked.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot OR Tiny ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2211-2_MILAN_RETUS_11_RRDE31.Q3-73-12_subsidy-DEFAULT_regulatory-DEFAULT_cid50_R2_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Milan.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 10 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter if you are flashing a fresh version of the stock firmware. I used Online Flash File Converter here. I recommend this just in case you're on a newer firmware - if not jump to Step 13.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot Factory Unlocked Moto 5G Stylus XT2211 [Mediatek Variant]
Hope this helps my fellow TMobile and subdiary acolytes and others. I'll be working on securing R/W access soon.
I will try and answer questions if I can or point you in the right direction.

Moderator Announcement ​This guide is only for the The Moto 5G Stylus (2022), and will be moved once the Administrators create a separate forum for this device.
-Regards: Badger50