Database Info

[Guide] How to flash stock FW and CWM and Root i9103

Disclaimer: I will not be held responsible for any damage to your device. You are following this tutorial at your own risk (not to discourage anyone, though as safe as this process maybe I will not take blame for anyone's bad luck). Apart from the tutorial explanation and some pictures I do not own any of the methods/tools/ROMs/FW in this tutorial/guide, I respect the works done here by the developers and I have no involvement in there works neither am I claiming so
Optional: download the android SDK
BEFORE YOU BEGIN
Some Common Knowledge
Stock Firmware: Is needed when you get your phone stuck in a boot-loop(not getting past the splash/start-up screen) OR if you're having trouble updating through OTA updates or Kies (I had my share of both)
Odin: Is used to Flash a stock/Official FW and in Galaxy R's case CWM as well
CWM: This is needed to back up your device's current FW and to install custom ROMs
Super User: This thing gives you root access
Custom ROMs: For when the stock FW seems too dull or when you need to tweak your device to your liking. For the sake of keeping this guide simple and "streamlined" this would not be discussed in this post
This Tutorial assumes that you have little or no knowledge on flashing/modifying your phone's OS/Firmware
Things you'll need:
1. Odin
2. CWM
3. Super User
4. Flashable ROM/Firmware available here Courtesy of The-Droidster
5. A FULLY CHARGED Galaxy R aka Royale aka Galaxy Z (aka Galaxy S2's adopted brother aka Loki Get it cuz it's low key )
6. A USB data cable
7. A PC (I'm using a windows PC)
8. Patience and time
For Personal ease keep all downloads in a separate folder dedicated for Android "Hacking"
STEP 1A: Downloading/installing Tools
Extract Odin
CWM DO NOT EXTRACT
From the link above download Super User shown here: DO NOT EXTRACT
{
"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"
}
STEP 1B: Downloading Firmware
Open the Official ROM link provided and choose the Firmware you like (Depending upon region/languages and OS version)
After Downloading the zip file extract it
You Should get either:
1. Three additional .tar/.tar.md5 files DO NOT EXTRACT THESE
OR
2. A single .tar/.tar.md5 file DO NOT EXTRACT THIS
The extracted files should look like this:
STEP 2: Set up
Turn off your FULLY CHARGED phone (It's better to have a fully charged phone but above 50% is good too)
Open Odin from the folder:
.
.
Allow it run:
.
.
Set it up like this making sure everything else is unchecked
.
.
Now put the phone in Download Mode. On your phone press and hold the volume down, home and power buttons as shown (power button last)
.
.
The following screen would appear:
Press the Volume up button (Because you're a bad ass!)
Now connect the USB data cable with the phone and computer
After a few minutes (of downloading the drivers) you should see this:
Now everything is setup and you can start flashing/Installing a Firmware
STEP 3: Flashing the phone.
As mentioned before you would have either 3 or just 1 .tar/.tar.md5 files from extracting the FW
Here is how you put the extracted files in Odin.
For three files
The file containing the word CODE goes in PDA
The file containing the word MODEM goes in PHONE
The file containing the word CSC goes in CSC
AS Shown here:
For a single .tar/ .tar.md5 file, place the file in the PDA
Click Start and wait for the Yellow rectangle to go green and you're done.
The phone will start automatically and take a few minutes on first boot (so be patient)
And you've Flashed your phone! Hoorah!
Now on to CWM and Root!
Place the Super User .zip file and the Custom ROM .zip in the internal SD of the phone (not the SD card)
STEP 4: Clockwork Recovery Mod aka CWM
Launch Odin, keeping the previous settings
Click the PDA button and open the CWM file: it should look like this
Turn off your phone
Put it in to Download Mode using the volume down, Home and Power Buttons.
Connect the device and PC
Be a Bad ass again!
Hit Start on Odin
Wait for Reboot! ....aaaaand then turn off!
Turn the device ON
After seeing the GalaxyR logo immediately hit the VOLUME UP and HOME buttons
If you see this:
Congratulations! You just installed CWM
STEP 5: Super User/Root access
Note: Recovery navigates using power up and down and to enter the power button
From the CWM select "Install zip from sdcard"
Look for the Super User .zip file and select it
Select yes to install
Reboot!
Now you would have a super user icon in your apps!
Congratulations! You just rooted your phone!
Change log (01/09/2012):
Removed Custom ROM tutorial (it was too generic)
Some minor changes in the descriptions, thanks to The-Droidster
Thanks:
The-Droidster
Adam77Root
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you want to thank me help me find a nice place in Liverpool near the University
Just your average neighbourhood Potato :silly:

Thanks buddy for your extra effort. Unfortunately this thread has been made before.
Check this one: http://forum.xda-developers.com/showthread.php?t=1406880&highlight=guide

kataria.vikesh said:
Thanks buddy for your extra effort. Unfortunately this thread has been made before.
Check this one: http://forum.xda-developers.com/showthread.php?t=1406880&highlight=guide
Click to expand...
Click to collapse
I know for a fact that there are more than just one tutorial out there, I just tried to make a simplified and yet a more detailed Guide as best as I could
I even added pretty pictures

Very well written!
Good job buddy! This could just be the new one stop thread for flashing, rooting and installing cwm for Galaxy R!
However there are a few subtle changes that I would like to mention!
1. BEFORE YOU BEGIN
download the android SDK It is important for installing drivers and tools etc
Not so mandatory for the purpose of flashing and rooting! Drivers get installed automatically, when the device is connected to the PC(Be sure you have Internet connectivity just in case windows has to look up for updated drivers!)​
2. Things you'll need:
1. Odin
2. CWM
Use this link for the CWM recovery! It has been optimised by Adam and does not need to be extracted!
As such make corrections here as well:
Extract Odin and CWM (DO NOT EXTRACT the zip folder inside the CWM)
From the link above download Super User shown here: DO NOT EXTRACT
3. STEP 1B: Downloading Firmware
Open the Official ROM link provided and choose the Firmware you like (Depending upon region/languages and OS version)
After Downloading the zip file extract it
You Should get three additional .zip/.tar/.rar files DO NOT EXTRACT THESE
The extracted files should look like this:
You are being very specific here! The 3 files format is not applicable to all ROM's for Galaxy R. Rather almost all the Stock ROM's come as a single *.tar or *.tar.md5 package that is directly loaded into the PDA section of ODIN! No other files are required!
So please make corrections at relevant places like here:​As mentioned before you would have 3 .zip/.tar files from extracting the FW
Here is how you put the extracted files in Odin.
The file containing the word CODE goes in PDA
The file containing the word MODEM goes in PHONE
The file containing the word CSC goes in CSC
4. [*]Reboot! ....aaaaand then turn off!
Odin always Auto Reboots the device after flashing. So no need to manually do that.​
5. Now the most important thing:
I recommend that you completely remove the section for flashing custom ROM's.
Reason: Each Custom ROM developer will have his/her own method of installing the ROM. Though most of it is generic, still there are quite a few steps that are different for each ROM. So the discussion regarding installing a custom ROm better be kept confined to the thread of that particular ROM. As such it would be wise to remove all references to Customs ROM's from the guide. Keep it focused on the three imp. things...which you already have done very well!:good:​
Thnx!

Good Job
X-627 said:
I know for a fact that there are more than just one tutorial out there, I just tried to make a simplified and yet a more detailed Guide as best as I could
I even added pretty pictures
Click to expand...
Click to collapse
thanks a lot buddy, yes , old tutorial was there but your's is much more newbee friendly and elobrated :good:

How perfect of you to make this thorough guide right now!
I am having KIES issues and was just in need of this "three-step" procedure for flashing stock and restoring CWM. (I'm not sure if I can flash stock through CWM, therefore I just overwrite CWM and redo the whole thing).
BR, Martin

By the way, there's a mistake in the OP.
You are writing "After seeing the GalaxyR logo immediately hit the VOLUME UP and POWER buttons"
which should say VOLUME UP and HOME buttons.

And tbh why bother to do this, if someone is already repacking every stock firmware with CWM? So that everything is done on automatic basic?

UnknownzD said:
And tbh why bother to do this, if someone is already repacking every stock firmware with CWM? So that everything is done on automatic basic?
Click to expand...
Click to collapse
I don't understand brother! Can you be more clear?
---------- Post added at 12:46 AM ---------- Previous post was at 12:45 AM ----------
@OP: There's a problem with the screenshots. Plz re-upload to some other site!
Thnx!

The-Droidster said:
@OP: There's a problem with the screenshots. Plz re-upload to some other site!
Click to expand...
Click to collapse
What sort of problem? I checked using a different PC (I wasn't logged into) it seemed fine.
Here's the link. If you're having trouble with the images still let me know

Yup buddy, confirmed. There's definitely some problem with the images. I can only see the final CWM image. All other images are broken. Tried with different browsers. Why don't you re-upload them to a site like postimg.com?
EDIT: Scratch that! The images are back on Might be some temporary problem with the image hosting site!
---------- Post added at 01:28 AM ---------- Previous post was at 01:06 AM ----------
Ok I'm going to drop a tip to justin about this guide! Who knows maybe this becomes THE one stop thread for flashing replacing the current one!
But before that could you plz implement these few changes?
Things you'll need:
1. Odin
2. CWM
3. Super User
4. Flashable ROM/Firmware available here Courtesy of The-Droidster
5. Optional Custom ROM (Not Discussed in this post... sorry)
6. A FULLY CHARGED Galaxy R aka Royale aka Galaxy Z (aka Galaxy S2's adopted brother aka Loki Get it cuz it's low key )
7. A USB data cable
8. A PC (I'm using a windows PC)
9. Patience and time
Extract Odin
CWM :DO NOT EXTRACT
From the link above download Super User shown here: DO NOT EXTRACT
Open the Official ROM link provided and choose the Firmware you like (Depending upon region/languages and OS version)
After Downloading the zip file extract it
You Should get
3 additional *.tar or *.tar.md5 files DO NOT EXTRACT THESE OR
Get a single *.tar or *.tar.md5 file DO NOT EXTRACT THIS
The extracted files should look like this:
STEP 3: Flashing the phone.
As mentioned before you would have either 3 or just 1 *.tar or *.tar.md5 files from extracting the FW
[*] For a single *.tar or *.tar.md5 file, place the file in the PDA

The-Droidster said:
I don't understand brother! Can you be more clear?
---------- Post added at 12:46 AM ---------- Previous post was at 12:45 AM ----------
@OP: There's a problem with the screenshots. Plz re-upload to some other site!
Thnx!
Click to expand...
Click to collapse
Actually I have stated here already :
http://forum.xda-developers.com/showthread.php?t=1861954
The mmc_cap_erase bug can actually takes place at the very first time just after the device rebooted with ICS firmware. And if you just switch off the device after flashing the kernel in order to flash the CWM. There is a chance that your device is already bricked during this process. The only safe method to do this is to replace the recovery image inside the stock firmware with a secured CWM (which using a flawless kernel), such that you have a chance to immediately flash a kernel in CWM after the device rebooted.
When the device is rebooted automatically after using odin, it will get into recovery mode first before going any further, therefore no damage can be done as the device never booted with a flawed kernel.
Therefore the method OP mentioned is actually unsafe as well.
oh btw, it is funny to see how many people that are using Galaxy tab 10.1 have bricked their device after updating to ICS 4.0.4, it seems like none of their users / devs have found that MMC_CAP_ERASE is enabled on their device as well lol But I guess I will just make a thread in a minute or so to get them noticed.

When the device is rebooted automatically after using odin, it will get into recovery mode first before going any further, therefore no damage can be done as the device never booted with a flawed kernel.
Click to expand...
Click to collapse
Oh well! I think now I understand what u r trying to convey. I found it a bit difficult to understand by reading the original thread that you created.
So what you are trying to say is:
After flashing the repacked ROM that you have provided via ODIN, the device won't boot into the OS! Rather it would boot directly into CWM that you have packed into the ROM. This way you can flash a secure kernel before the first boot itself! So there's no risk of bricking bcoz the Stock kernel won't ever be loaded! Ingenious my boy! Great!:good: How long have you been playing around with this?
Having said that, the guide the OP has posted is not only about flashing ICS ROM's but also for GB ROM's. What the OP can do is add an exception for ICS ROM's and a link to your repacked ROM would fit in well I guess!

How to remove CWM??
Sent from my GT-I9103 using xda app-developers app

How to remove CWM??<br />
<br />
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
Flash back stock rom
Sent from my GT-I9103 using Tapatalk 2
---------- Post added at 07:53 AM ---------- Previous post was at 07:51 AM ----------
I req only thread should b made....
As it wld nly create a mess/confusion to any new bie..
I m personally confused to which thread to follow
Hope every bdy understands
Sent from my GT-I9103 using Tapatalk 2

How to unroot SGR???
Sent from my GT-I9103 using xda app-developers app

simran_57 said:
How to unroot SGR???
Click to expand...
Click to collapse
Flash to stock F.W

simran_57 said:
How to unroot SGR???
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
Either flash stock kernel back or flash back entire stock rom..
Sent from my GT-I9103 using Tapatalk 2

Problems!! D:
I tried to flash Stock Recovery (Singapore ROM, that's where I live), it gave me an error saying:
Partition size is small! [Bin:2059792(4KB) > Part:131072(4KB)]
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
Halp! What to do! Can't get past Samsung logo splash now. Stuck in boot loop. :crying:

shikhargpt said:
I tried to flash Stock Recovery (Singapore ROM, that's where I live), it gave me an error saying:
Partition size is small! [Bin:2059792(4KB) > Part:131072(4KB)]
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
Halp! What to do! Can't get past Samsung logo splash now. Stuck in boot loop. :crying:
Click to expand...
Click to collapse
Flash a stock ROM via ODIN.
Thnx!

[ROM][ROOT][CWM] Gionee Dream D1/GN878 - Stock De-odexed ROM with root and busybox

I no longer have this phone (GiONEE Dream_D1), I'm also going to stay away from Mediatek SoCs.
No more support for this device in this thread. If anyone wants to take over, please do. Thanks everyone who participated and encouraged me.
Link to the stock deodexed rom available in post #2 below.
For increasing the internal storage to 2GB from 1 GB, follow the instructions by @RickyGoldsmith here http://forum.xda-developers.com/showpost.php?p=41966897&postcount=3
-------------------------------------------------------------------------------------------------------------------------------------
Stock Factory ROM root instructions:
Download the zip file named motochopper.zip from the First Post of this thread here: http://forum.xda-developers.com/showthread.php?p=40747604
Thanks and Credits to djrbliss
YOU ARE DOING THIS AT YOUR OWN RISK.
Instructions:
Extract the entire contents of the zip file.
If you are using Windows, ensure you have installed the latest MediaTek USB drivers available for your phone. Download link for the MediaTek drivers here: http://goo.gl/A7gnp
Ensure USB Debugging mode is enabled on your device.
Connect your device to your PC via USB.
Run run.bat from the extracted folder.
Follow the instructions on screen, when everything is done, the phone will reboot.
Voila! Now your Gionee Dream D1/GN878 will be rooted.
CWM Recovery for Gionee Dream D1/GN878
Steps to install CWM recovery: YOU ARE DOING THIS AT YOUR OWN RISK.
1. Install the MTK USB Drivers for the phone. If you had followed the above steps to root then You have the drivers installed.
2. Download the SP Flash tool, with the scatter file and the recovery.img. Download link here: http://goo.gl/SD9kh
CWM Version 6 available here http://forum.xda-developers.com/showthread.php?p=43039475#post43039475 thanks to @deepak2111
3. Extract the zip file and run the Flash_tool.exe
Leave all the options as default, do not tinker with any settings, except pointing to the correct scatter file.
4. The scatter file and the recovery.img are placed in a folder named DreamD1 in the extracted folder.
In the Flash tool, click on scatter-loading button and select the file named MT6589_Android_scatter_emmc_PMT.txt
The recovery will be auto selected as shown in the image below: DO NOT CHECK ANY OTHER CHECKBOXES.
{
"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"
}
5. Click on the Download button. DO NOT CLICK ON Firmware->Upgrade Button, it will brick your Phone
6. Remove the phone from the USB cable
7. Switch off the phone, wait till you feel the vibration. Wait for another 30 seconds
8. Now plug in the phone to the USB cable without turning on the Phone.
As soon as the phone is detected, the recovery image will be installed.
Voila!, Now you phone has CWM recovery installed.
After the recovery installation, remove the phone from the USB Cable.
To go to Recovery Mode: KeepPressing Power + Volume Up Keys. You should now be greeted with CWM recovery menu.
Please HIT the Thanks button if you feel I deserve it.
Note: Just found out that the Chinese Model number for Dream D1 is GN878

Hybrid Stock ROM De-Odexed, Zipaligned rooted with busybox - best of Primo-X1 and Dream D1
Kernel aka boot.img is included in the rom zip as we now have the MTK6589 SoC sources.
Copy the downloaded Zip to External SD Card.
Reboot to CWM Recovery
Do Factory reset.
Flash this using CWM Recovery.
Download Link:: https://copy.com/frhv3
Known Bugs:
Selecting Wallpaper from Settings->Display->Wallpaper FCs.
Please let me know, if you come across any bugs here in this thread.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
GiONEE Dream_D1 Stock deodexed ROM with root and busybox.
Copy the downloaded Zip to External SD Card.
Reboot to CWM Recovery
Do Factory reset.
Flash this using CWM Recovery.
Download Link:: https://copy.com/yRrfRMDNBE4A
MT6589 SoC Kernel source: https://github.com/varunchitre15/MT6589_kernel_source
Credits to varunchitre15 for the kernel sources.

MIUI
How about porting MIUI to start with?
I am already running MIUI Home Launcher and it is a breeze. Do you have any experience with porting ?
I looked at: http://forum.xda-developers.com/showthread.php?t=1827256 and it looks straight forward. What I am not sure is how much these applications depend on the underneath framework.. I mean, If I take all these apk and libraries, will it work on this stock Gionee Dream D1 ROM ?

somberi said:
I'm also working on porting the CWM recovery to Gionee Dream D1. Once that is completed I shall share it here.
Click to expand...
Click to collapse
waiting for CWM ,have to get rid of this rom,every hd games opens after 10minutes

million thanks
I cant believe my eyes
I am going to root that right now, but first i am going to thank you
Great job and we will wait for your new roms
thanks

RickyGoldsmith said:
How about porting MIUI to start with?
I am already running MIUI Home Launcher and it is a breeze. Do you have any experience with porting ?
I looked at: http://forum.xda-developers.com/showthread.php?t=1827256 and it looks straight forward. What I am not sure is how much these applications depend on the underneath framework.. I mean, If I take all these apk and libraries, will it work on this stock Gionee Dream D1 ROM ?
Click to expand...
Click to collapse
I would wait for a CWM recovery / Factory Stock rom for Gionee Dream D1, before I start to working on ROM ports. Anyways good to see interest for this device.

protocolt fault
I am getting the protocol fault, waiting for device.
Any idea the cause for that?

somberi said:
I would wait for a CWM recovery / Factory Stock rom for Gionee Dream D1, before I start to working on ROM ports. Anyways good to see interest for this device.
Click to expand...
Click to collapse
How do you intend to get the Factory Stock ROM? Rip it from the device?
I am currently trying to play with the CWM process. Will update here how it goes...

ashishsoft said:
I am getting the protocol fault, waiting for device.
Any idea the cause for that?
Click to expand...
Click to collapse
Did you install the MediaTek drivers from the link above? Make sure you dont have the phone connected in the PDANet+ (Right click on the System Tray icon and click on disconnect. Also make sure you have USB debug enabled, under Settings->Developer Options.
If all the above fail try restarting the system and try to connect the phone to a different USB port on your computer.
let me know the results.

RickyGoldsmith said:
How do you intend to get the Factory Stock ROM? Rip it from the device?
I am currently trying to play with the CWM process. Will update here how it goes...
Click to expand...
Click to collapse
Currently looking at various Chinese forums to get a proper rom backup tool for MediaTek based devices. Also have contacted Gionee India asking them to release the Factory Stock ROM and the flashtool for the device. Micromax, Lava and many other manufactures give the Stock ROM for download.
At work now and do not have access to any of the resources here..

rooted it
sorry it got that rooted!
yeah!
now waiting for the ROMS
thanks

ashishsoft said:
sorry it got that rooted!
yeah!
now waiting for the ROMS
thanks
Click to expand...
Click to collapse
Nice to know

I am your fan somberi
You are a master, !
Great job done and keep that up
:angel:

somberi said:
I would wait for a CWM recovery / Factory Stock rom for Gionee Dream D1, before I start to working on ROM ports. Anyways good to see interest for this device.
Click to expand...
Click to collapse
Are you able to get the boot.img image dump?
MtkTools and others create a file which is just binary data.

our stock recovery is useless...pls gv us cwm and unroot.zip too....for safety...
Sent from my Dream_D1 using xda app-developers app
---------- Post added at 01:01 PM ---------- Previous post was at 12:48 PM ----------
somberi said:
Download the zip file named motochopper.zip from the First Post of this thread here: http://forum.xda-developers.com/showthread.php?p=40747604
Thanks and Credits to djrbliss
You are performing this at your OWN RISK!
Instructions:
Extract the entire contents of the zip file.
If you are using Windows, ensure you have installed the latest MediaTek USB drivers available for your phone. Download link for the MediaTek drivers here: http://goo.gl/A7gnp
Ensure USB Debugging mode is enabled on your device.
Connect your device to your PC via USB.
Run run.bat from the extracted folder.
Follow the instructions on screen, when everything is done, the phone will reboot.
Voila! Now your Gionee Dream D1 will be rooted.
Click to expand...
Click to collapse
i hv sucsfuly rooted my dvice...waiting for cwm n unroot...
Sent from my Dream_D1 using xda app-developers app

RickyGoldsmith said:
Are you able to get the boot.img image dump?
MtkTools and others create a file which is just binary data.
Click to expand...
Click to collapse
Could not get time to investigate, too much work.. Will have to spend some time this weekend.

how to install CWM recovery/4ext
hi there
after rooting the device, i have been trying to get in the recovery, i tried using CWM and 4ext both
but everytime i try go to recovery it only shows me default factory mode, that is it. nothing else
can someone tell me why and guide me
thanks

Finally managed to get CWM recovery ported to Gionee Dream D1. Testing in progress.
Works great.
The External SD card is detected.
Did a nandroid backup, restored the back up without any problems.
Did a Factory reset and worked great.

somberi said:
Finally managed to get CWM recovery ported to Gionee Dream D1. Testing in progress.
Works great.
The External SD card is detected.
Did a nandroid backup, restored the back up without any problems.
Did a Factory reset and worked great.
Click to expand...
Click to collapse
That's great news. Thanks

On my windows 7 ThinkPad, it has never been able to detect the phone over the serial console. Perhaps I'll try it on someone else's box.

BLU Studio Energy *Official Thread*

{
"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"
}
This thread is a work in progress. I'll post here info about our phone. How to root, how to backup, how to flash, etc...
A HUGE Thank you for your patience & your work @lopestom
INFO
This device is very similar (almost identical) to the Gionee M3 phone, so a lot of tutorials and ROMs for that device will also work for our device. However, as usual, READ first, before you end with a bricked phone.
It seems that the only difference between the D810L and the D810U is that the D810U also has a 1700 Mhz band, so, if you flash the wrong ROM and you're using that band, you'll loose connectivity. However, the modem drivers can be replaced cross ROMs.
LINKS
Official BLU Studio Energy Site
Unofficial Support Groups
BLU Smartphone Community Support Forum
BLU Products Development Team Group
RESOURCES
Adbd Insecure
MTK Droid Root & Tools (as the time of writing: v2.5.3):
Original russian thread, just click the link or use translator.
PdaNet+ [drivers] (Once you've plugged in your phone and everything works, you can remove the software).
Download from Official Website.
SP Flash Tool 3.1344.0.212.
MediaTek USB Vcom Drivers.
MT6582 Android Scatter File.
ROM
Gionee M3 ROMs
BLU Stock ROMs
Stock ROM MTKDroid Backup BLU_D810I_V07_GENERIC 2014-12-19 03:30 MD5: BC52037C013CAAE788E5100EA8150D61 This is a SPFT ready backup.
Stock ROM TWRP Backup Blu_D810u_V03_GENERIC_15-01-2015 00:03 by @jabe78This is a TWRP Backup. You must unzip it into the backups folder of TWRP and then restore it using TWRP Recovery on your phone. This is not a flashable zip.
RECOVERY (Flash them with Flashify)
TWRP 2.8.4.0 Jawad by @lopestom MD5: 9658c8377071cf936f95eb7ddb530f85 Please check on Mount that the external storage is selected, and also when you do backups, always check that the external storage is selected.
Philz by @lopestom MD5: a0b71f399200795ad662a2c2e083bbf8 You need to mount /sdcard1 and do backups there. Also, check on settings and disable sceen timeout, since when the screen goes off, it won't turn on again.
KERNEL
These are the kernel sources downloaded from the FTP provided in this post, and uploaded to MEGA. I don't know if this works or not yet, please if someone with proper knowledge can check it, let us know.
ALPS.KK1.MP1.V2.10_GIONEE92_CWET_KK_BUILDABLE_PACKAGE.tar.gz

ROOT
The only tool that works out of the box to root our device is KINGOROOT.
Download, install and run. If you have driver problems, you can try installing PdaNet+ software. This procedure does work on windows 8.
Please let me know if you have any problems or if some info is missing, since I'd experimented a lot until I could root the phone, and I installed a lot of crap in the process.

BACKUP
You can find the necessary links on the first post, under Resources.
To create backups, you'll need to do the following first:
Root your phone.
Enable USB Debugging on your phone.
Enable apps from unknown sources (under settings->security).
Install and enable adbd insecure on your phone.
Install PdaNet+ on your computer.
Install MTK Droid Root & Tools on your computer.
Once you've done those steps, you'll see your device information when you open MTKDroid Root & Tools, and you can proceed.
To create a backup, please follow this guide: LINK. Don't download anything from that post, it isn't necessary. Just follow the steps.
NOTE: I'm not sure if you need to install busybox, since I'd installed a lot of thinks to make it work. If this guide doesn't work for you, please install busybox from the play store and let me know, so I can update this post.
WARNING: THIS WILL NOT WORK UNDER WINDOWS 8 !! Use WIN7 or XP.

Flash ROM or Recovery
You can find the necessary links on the first post, under Resources.
To flash a backup, ROM or Recovery, you'll need to do the following first:
Install MediaTek USB Vcom Drivers.
Download an extract SP Flash Tool 3.1344.0.212.
Download the Android Scatter File (or you can get it from any MTKDroidTools backup)
Power off the phone
Once you've done those steps, open SP FlashTool and select the Android Scatter File in scatter-loading.
You'll see then the things you can restore. If you open the scatter file from a backup, it'll automatically prepare everything to restore that backup. Don't change ANYTHING, and click "Download".
When the software is ready, plug the phone and it will do the magic. You need to wait until a green circle pops up and says "Download OK".
Then you're good to go.
To restore a recovery only (or install TWRP for example), do the above steps but untick everything except RECOVERY. then click on the recovery word and it'll ask you for a new route. Search and select the recovery.img for the TWRP, and then proceed with clicking download and then plug the phone, and you'll have the recovery.
WARNING: All the things I've done where using the backup as a source for the scatter file. I've uploaded the file so if you know what you're doing, you don't need the full backup. If you don't know what you're doing, download the backup and select the scatter file from there.

RESERVED
reserved

Thanks for this, I needed the ADBD Insecure to get the MTK tools to work and make a backup. Shame this phone hasnt gotten its own spot on the forums.

I have flashed my death Studio Energy with an official Gionee m3 ROM, but its impossible to root it.
I have tryed with a lot of tools: KINGO Root, Kingroot, iRoot...
Saludos from Argentina.

Edibulho said:
I have flashed my death Studio Energy with an official Gionee m3 ROM, but its impossible to root it.
I have tryed with a lot of tools: KINGO Root, Kingroot, iRoot...
Saludos from Argentina.
Click to expand...
Click to collapse
Have you tried flashing the zip file located in post #12 of the Gionee M3 development thread http://forum.xda-developers.com/showthread.php?t=2977122 ? It works for me as well.

How do I recover my phone using one of these, I cant seem to get the SP Tools to do anything on my device!

Your stock image helped me, and I love you for it

dragid10 said:
Your stock image helped me, and I love you for it
Click to expand...
Click to collapse
Which backup helped you, so we can have verification that it works, beyond the original submitters?
---------- Post added at 01:42 AM ---------- Previous post was at 01:34 AM ----------
Moynia said:
How do I recover my phone using one of these, I cant seem to get the SP Tools to do anything on my device!
Click to expand...
Click to collapse
Do you have TWRP recovery on your device?

jabe78 said:
Which backup helped you, so we can have verification that it works, beyond the original submitters?
---------- Post added at 01:42 AM ---------- Previous post was at 01:34 AM ----------
Do you have TWRP recovery on your device?
Click to expand...
Click to collapse
How would I go about doing that, I havent seen any guides on how to do it.

Hi, I'm glad that it helped. Which backup have you flashed and with what tool? Thanks!
Sent from my STUDIO ENERGY using XDA Premium HD app

Moynia said:
How would I go about doing that, I havent seen any guides on how to do it.
Click to expand...
Click to collapse
We are working on getting an official TWRP recovery for the BLU studio Energy, the one I am using currently was built for the Gionee M3 device...its a little buggy in my opinion, but it does the job. You can look in the 1st post of that thread to see how it is done using the flashify app. If you need further help flashing it, just ask.

jabe78 said:
Which backup helped you, so we can have verification that it works, beyond the original submitters?
Click to expand...
Click to collapse
The D810l one. It works perfectly

jabe78 said:
We are working on getting an official TWRP recovery for the BLU studio Energy, the one I am using currently was built for the Gionee M3 device...its a little buggy in my opinion, but it does the job. You can look in the 1st post of that thread to see how it is done using the flashify app. If you need further help flashing it, just ask.
Click to expand...
Click to collapse
Ok thanks. I hope it comes out soon, I cant update to the newest build because I am missing the Amigo_Calender.apk and I cant seem to restore it without a full restore from TWRP.

Moynia said:
Ok thanks. I hope it comes out soon, I cant update to the newest build because I am missing the Amigo_Calender.apk and I cant seem to restore it without a full restore from TWRP.
Click to expand...
Click to collapse
If you're rooted, can't you use ES File manager and place it into /system/app and then fix permissions? I can upload it if you need the apk

Moynia said:
Ok thanks. I hope it comes out soon, I cant update to the newest build because I am missing the Amigo_Calender.apk and I cant seem to restore it without a full restore from TWRP.
Click to expand...
Click to collapse
What device do you have?
D810L or D810u? I have a link to both the Amigo calendar APK & Odex, but I have the d810u version. Like was just mentioned, you may be able to just copy and paste using a root browser.

jabe78 said:
What device do you have?
D810L or D810u? I have a link to both the Amigo calendar APK & Odex, but I have the d810u version. Like was just mentioned, you may be able to just copy and paste using a root browser.
Click to expand...
Click to collapse
Quick question, whats the difference between D810L and D810u?

dragid10 said:
Quick question, whats the difference between D810L and D810u?
Click to expand...
Click to collapse
Somebody correct me if I am wrong, but...
3G: UMTS 850 / 1900 / 2100 MHz (SIM 1) (D810L)
3G: UMTS 850 / 1700 / 1900 / 2100 MHz (SIM 1) (D810U)
The "u" has the extra 1700 baseband. That's the only difference I am aware of. So if you have a "u" and flash a backup for an "l" you would in theory loose the ability to receive signal on that band, and hope your carrier doesn't use it. I have already seen posts from those encountering that problem. Restoring a backup from "u" should correct it however. In theory... Lol

[TWRP][Root] Dragon Touch X10 [TabletExpress][Allwinner A83T]

This is a very nice budget tablet from Tablet Express. I found mine on eBay for $93.00, new + free shipping, and have been very pleased with it. I love that it came with Developer Options already on, had USB Debugging enabled right out of the box, and has a screen protector installed by the manufacturer. Add the fact that the bootloader isn't even locked, and you really can't go wrong with this device.
I used the AIO TWRP Compiler script by @yuweng, to build this recovery, it's a very efficient tool to work with and he put a lot of work into it. Many, many thanks there!!
Well, enough rambling, lets get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!!​ (Or ask for help, there's a lot of friendly people around here)​
Verify Partition Scheme
Over the past few months, it seems some devices have different names for the partition scheme, either "nand" or "mmcblk". So, the first step will be to check which type you have before installing TWRP and rooting the device. Here's how you check:
1) Connect the device to your PC, and open a terminal
2) Type the following:
Code:
# to make sure the device is recognized:
adb devices
# result should be:
List of devices attached
00000000000000000000 device
# Now type:
adb shell
# followed by:
ls -al /dev/block/by-name
# First Line should be 1 of the 2:
# This is a "mmcblk" device
lrwxrwxrwx root root 2016-07-20 00:08 UDISK -> /dev/block/mmcblk0p1
# This is a "nand" device
lrwxrwxrwx root root 2016-07-20 00:36 UDISK -> /dev/block/nandk
Once you know which device type you have, follow the below directions accordingly.
Root (Works for Android 4.4.4 and 5.1.1)
Rooting the device is easy, there are two methods that I know work:
1) Install TWRP, then flash Chainfires current SuperSu zip, find it Here (<-- recommend method)
2) Using Kingo Root for PC, find it Here (Use the Root Again option)
Install TWRP
You should already have ADB installed on your PC, or BusyBox and Terminal Emulator installed on your tablet, I will not cover installation of either of those. And you should know which type of mount partitions your device is using. To get the TWRP recovery on your device, you have a few options:
1) Use ADB to "push" the image (Android 4.4.4 and 5.1.1)
2) Use the included shell script, via BusyBox and Terminal Emulator (Android 5.1.1 and the device must already be rooted to use this option)
Download the appropriate zip for your device, located below, under Downloads, and extract it to a convenient location on your PC. If using your Tablet, the shell scripts and TWRP image must be in the root directory ( / ) to work properly.
Using ADB (Android 5.1.1) on "nand" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push X10_twrp3.0.2.img /dev/block/nandf
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 5.1.1) on "mmcblk" partitions
Put the X10_twrp3.0.2.img file in the same directory as your working ADB, then enter the following:
Code:
adb push x10_twrp_mmc.img /dev/block/mmcblk0p9
#After it finishes:
adb reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That was easy, yes?
Using ADB (Android 4.4.4)*As of now, KK uses "nand" ONLY
This is the only way I could get it to work right on KitKat, sorry, no Terminal Emulator for this one...
Put the X10_twrp2.8.7.0.img file in the same directory as your working ADB, then enter the following, one line at a time:
Code:
adb push X10_twrp2.8.7.0.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/X10_twrp2.8.7.0.img of=/dev/block/nandf
#After it finishes:
reboot recovery
Now, flash the SuperSU flashable zip and your device will be rooted, yay!
That wasn't too bad, was it?
Using Terminal Emulator (Android 5.1.1 using "nand" ONLY)
Put the X10_twrp3.0.2.img and twrp.sh files in the root ( / ) folder of your tablet, then open the Terminal Emulator, enter the following, one line at a time:
Code:
su
sh twrp.sh
The script will tell you when it's done, now, power off the tablet. Boot into recovery by pressing and holding the Volume Down and Power Buttons. When the Dragon Touch logo appears, release the Power Button but continue to hold Volume Down until TWRP boots.
I hope you enjoy my work, and keep in mind that I like to keep things up to date, when a new version of TWRP comes out, I'll build it and post it here.
Downloads
X10 TWRP for "nand" devices
X10 TWRP for "mmcblk" devices
~ Also see Extras Section Below ~
Credits
@yuweng (bunch of help there)
@MSF Jarvis
@trillwizzard (for mmc fix)
@amw2320 (for modified firmware)
TeamWin

Extras
Themes for TWRP
TWRP 3.x Themes for Tablets (Landscape Devices)
Factory Firmware
TabletExpress.com
Modified Firmware
X10-V2-5.1-amw-TWRP_SuperSU.img (Created by: @amw2320, has TWRP (nand) and SuperSu already installed)
Using PhoenixUSBPro
My "short" guide on using the PhoenixUSBPro tool can be found here
X10 Device Tree (For Android 5.1.1)
GitHub

Change Log
Change Log (Newest First)
Added modified stock firmware (8-20-16)
Added info about devices using "mmcblk" instead of "nand", provided TWRP for each (7-23-16)
Added TWRP 2.8.7.0 for KitKat (Android 4.4.4) users and flash instructions (5-19-16)

@NepoRood, great work! One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
I am sure the flag has dir rather than folder in its name, but you can easily confirm that from the thread and you have to use an absolute path for folder name, so include the device/vendor/codename also, before rootdir.

MSF Jarvis said:
One suggestion, instead if using the PRODUCT_COPY_FILES, you can simply add DEVICE_RAMDISK_(DIRS|FOLDERS) += rootdir
Click to expand...
Click to collapse
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:

NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
That's what I'm here for, no?

Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk

Franzferdinan51 said:
Great job tested with backup and cache cleaning and it worked great now I just need to find a custom rom any of you know of any?
Sent from my SM-G530T1 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.

NepoRood said:
Unfortunately, no, I've never had any luck building a ROM. However, I'm going to give it a shot with this tab (I might as well try, lol) IF, I come up with anything, it will be posted here.
Click to expand...
Click to collapse
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time

MSF Jarvis said:
I can lend you my Jenkins server if that's what is bothering you. I'll even fix errors occasionally when I get time
Click to expand...
Click to collapse
Thank you for the offer my friend!
I've only tried to build for one device, well 2 actually, both RCA (MT8127), both failed miserably. Even though I got a "successful" build (ie: no errors/make completed) CM12.1 wouldn't boot. Come to find out, the zip and system.img had limited files, I can't remember which, but not enough for a complete rom
So, I decided to learn everything I could about building TWRP (thanks for your help with that too )
I'll pull all the vendor blobs from the X10 and try to put together the device tree for rom building and get back to you.
Thanks Again,
Nepo

marshmallow
you think this tablet is able to be upgraded to marshmallow?
i found a rom for 6.0.1 that has the same processor A83T
it has the same processor so do you think it would flash?
Thanks!

the firmware is
A83T_N106_N1061L6BC_20160309

NepoRood said:
Thanks for more great advice, I've read the first page of the OP a dozen times or more, and never noticed that flag (until you pointed it out!). Would have saved a lot of typing, lol, I'll definitely use it for future projects :good:
Click to expand...
Click to collapse
The flag is actually this
Code:
RECOVERY_RAMDISK_DIRS += device/<vendor>/<codename>/ramdisk
As seen in this reverted commit

stickz42o said:
the firmware is
A83T_N106_N1061L6BC_20160309
Click to expand...
Click to collapse
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it here
PS, you can also use Phoenix Card to boot from External SD just to test

Ahhh Please Help?
@NepoRood
All images from TabletExpress Dragon Touch X10 10'' Android 5.1.
X10-HT-PW-V1-AL-5.1-A83T_N106_N1061L2BC_20151126
X10-HT-PW-V1-AL-4.4-20151104
X10-HT-PW-V2-AL-5.1-20150115
X10-HT-PW-V2-AL-4.4-20160116
A83T_N106_N1061L6BC_20160309-ok NOT WORKING. RED/WHITE BOOT SCREEN.
I have downloaded and flashed all these images and I cannot get TWRP to work? I have installed Via Adb and Terminal, but it will not flash the recovery.
All I get is the factory recovery. I can confirm it pushed it to device, but will not work.
Can someone else verify.
Regards
Paxster
For Users: The Best and Easy App to use is the PhoenixSuit (Just Google lol)

I'm using this one:
Paxster said:
X10-HT-PW-V2-AL-5.1-20150115
Click to expand...
Click to collapse
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes

NepoRood said:
I think it may work, post a link and I'll test it. Or, you can try it and let us know if it works. Do you have the current firmware already? If not, get it
PS, you can also use Phoenix Card[/URL] to boot from External SD just to test
Click to expand...
Click to collapse
I am going to try it tonight. I didn't know about the phoenixcard boot to test it. I will try that method and post my results if someone doesn't beat me to it
thanks for the info about the phoenixcard
I can't post a link till 10 posts for the firmware btw :/ i'll try to message it to you.

NepoRood said:
I'm using this one:
If all you have is 3e recovery, then you're doing something wrong somewhere. Make sure the TWRP image is in the proper directory.
PC: should be in the same folder as your adb.exe file
Tablet: should be in root directory, which is just a backslash " / "
Please let me know how it goes
Click to expand...
Click to collapse
{
"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"
}
Yes Recovery is in the same Dir as ADB. It confirms being sent in the Adb Window to my booted Tablet.
Also if I use a Terminal app, it is also confirmed as being flashed, but I still get a 3e recovery? So strange.
Its driving me nuts lol..
Q:Should it work with any V5.1 Android Firm? I am using X10-HT-PW-V2-AL-5.1-20150115 from tabletexpress.
Can you confirm what version yours is working on please.
UPDATE... 5 Hours later.. I managed to flash the TWRP on Android V4.4 using Rashr. and when in recovery the screen is corrupted, unable to use? and Twrp is in Landscape mode. Shall try this method on V5.1.
Regards
Paxster
PS: @stickz42o A83T_N106_N1061L6BC_20160309 Does not work. I posted above.. Red/White Stuck Boot.

@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment PAXSTER.LOG So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster

Paxster said:
@NepoRood
Ok.. I used RASHR to install TWRP. A lot less hassle for people i recon matey. Plus it worked.....ADB refused to install lol...
It works ok on the Android V5,1, (X10-HT-PW-V2-AL-5.1-20150115) but unable to backup any partitions. The Twrp Log reports Unable to mount or find the partitions?
Plus you cannot boot the tablet again after rebooting out of twrp hehe..
Here is a Log File after Flashing a Image from PhoenixUSBPro. The Partitions are there View attachment 3747215 So maybe TWRP does not know where they are ekk? Maybe it will help from the log file to sort his out? Im new to creating a Twrp File.
Regards
Paxster
Click to expand...
Click to collapse
When building, I ran into problems of only TWRP booting, turns out it was an init.rc and recovery.fstab issue. But, I had that fixed for the final release I'm using the exact same firmware as you are, and TWRP works perfectly.
Could you attach your TWRP log?

[root] ulefone armor 2 - easy rooting procedure [SUPERSU]

Hello mates! What a heck of a problem rooting this fancy brick, right? Not anymore ! The guides available in here are very confusing and lack of simple information. I'm just trying to help.
Special thanks goes to sumec100 who made me into the first steps of this process.
Rooting the Brick
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
- SuperSU: https://mega.nz/#!t2wGDbhL!H07JxlbmLH2tFQD7Frx2BKlJp0AyDthXkbEj6sw4z08 (this one worked out) (Leave it in your SD Card before start the process)
- TWRP ported by Jemmini from 4pda and translated to English by TuksOID. : https://drive.google.com/open?id=1Uwkl_2vqHfXkbLGmF-gKbs63UxVKmw_T
- ADB Driver Installer: http://adbdriver.com/downloads/
- ARMOR 2 Latest Drivers: https://drive.google.com/folderview?id=0B8NC4kBpjQhYdDNhdzdUdTRsRFE&usp=sharing
0) Go into your Ulefone Armor 2.
Settings >About phone > Tap ''build number'' 8 times until you see ''now you are a developer''.
Developer options> OEM unlocking (yes) >USB Debugging (Yes)
After all drivers are installed in Driver_Auto_Installer you downloaded from ulefone.com keep ADB Driver Installer open and plug in your phone on your PC. It will auto detects your MediaTek device. Just click ''Install'' wait until it finishes and close it. Now you are properly connected to your phone.
1) Open ''cmd.exe'' as an administrator.
Type: cd (path you unziped plataform-tools inside SDK tools folder) kind of looking like this: ''X:YOUR PATH\tools\platform-tools''
Put the recovery image you downloaded (I suggest you to rename it as ''recovery'') in ''plataform-tools''
2) Back to the cmd in the way you leaved it do it:
adb reboot bootloader Press Enter. The phone will reboot in fastboot mode. (I suppose you did not shut it down, please don't)
fastboot flashing unlock Press Enter. The phone will prompt you. Read the content of the text if you want. To keep going press ''Volume Up'' DO NOT INTERRUPT THIS PROCESS
fastboot flash recovery recovery.img Press Enter. Now the TWRP will be flashed. Note that I used ''recovery'' as file name.
After the successful flash:
fastboot boot recovery.img Press Enter. TWRP will now start.
3) Unplug your phone.
Your TWRP will show a ''Enter Code'' prompt since your device stills encrypted. Press ''Cancel''
Drag the bar to allow modifications;
Press ''Wipe'' in the main menu;
Drag the bar to do a Factory Reset (THIS IS NOT OPTIONAL);
Press ''Install'';
Select the SuperSU file you downloaded in the above. (I hope you copied it in your SDCard. If you did not, You can plug your phone in your PC, mount your Storage via TWRP, copy the zip file and keep going);
Drag the bar to flash SuperSU zip file (DO NOT select any parameters)
Press ''Wipe Dalvik/Cache''
Press ''Reboot System''
Wait for it.
If you had a successful boot, now your device is rooted. Cheers !
Did your device don't boot in 15 minutes? I'm quite sure you messed up but keep calm, don't panic!
Unbricking the brick
*What will you need:
SPFlashtool: https://spflashtools.com/windows/sp-flash-tool-v5-1728
Latest Ulefone Armor 2 ROM: https://drive.google.com/open?id=0B8NC4kBpjQhYdEJTdTdpazVGQjg
The software is quite of auto-explained. Please, Do not use the Ulefone's SPFlashtool, use the one I provided. (I DID NOT CREATE IT)
Shut off your phone
In SPFlashtool set the ''scatter-loading file'' inside the ROM zip, Click ''choose'' and locate it.
Keep it ''Download Only''
Click ''Download'', SPFlashtool will be waiting for your device. (REMEMBER YOU NEED THE DRIVERS I QUOTED ABOVE FOR ALL PROCESSES)
Plug your phone.
Wait until SPFlashtool say it is finished.
[*]After that your phone is brand new. If you want to try again just go up and follow all steps again (Correcting mistakes, of course)
Known Issues
-Latest Magisk is not working with our Stock ROM. It bootloops.
-Latest Nougat Xposed Module Bootloops our phone too.
Any doubts or corrections please, say it !

TheReal V said:
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY
Click to expand...
Click to collapse
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO

Have you tried the new ROM that came out last month on needrom?

TheReal V;76285584[FONT="Arial Black" said:
*What will you need in a first moment:[/FONT]
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
Click to expand...
Click to collapse
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
{
"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"
}
Thank you

enzovic said:
Have you tried the new ROM that came out last month on needrom?
Click to expand...
Click to collapse
No, I did not. I'm not messing with this system anymore (not enough time ) since I made my last format and root I decided to not try anything else since he is my daily driver and I need it workin 24/7

kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
That's right ! Inside this zip and inside sdk tools folder it should be a plataform-tools folder. If not, tell me !

Daugl said:
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO
Click to expand...
Click to collapse
You can go ahead and download it. I guess my attach was erased

kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
Quick Remember ! Plataform-tools is a tiny folder (15~30mb) The huge one is the sdk tools !!

Hey, everybody ! Plataform-tools is attached again ! You guys can download it again !

hey guys... sorry to comment in the old thread but I followed the guide and... my phone is booting always in the recovery I really don't know what I have to do now lol

Hi,
I have flashed successful the latest Ulefone Armor 2 Firmware from their site h**p://ulefone.com/download/armor2.html
Then I did all the necessary steps to root the phone. But when I first time start the SuperSU app, get a popup message "SuperSU needs to update"
and hit "OK". After a while get this failure:
"SU Update unsuccessful"
Regards...

After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?

rafaelsenna said:
After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?
Click to expand...
Click to collapse
Fixed. I restored my original ROM using this this tutorial: https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
Now, Super SU is installed but is asking for update.

Hi all,
I managed to root my Armor 2 but after that I cannot install Netflix from Play Store. It says that device is not compatible.
Does anyone know if the app is restricted to rooted devices?
Thanks in advance

flashed the wrong recovery now stuck ( I used "one click" program )
phone constantly restarts and gives the following error
"
orange
state your device has been unlocked and can't be trusted your device
will boot in 5 seconds
"
the following video is someone else who has the same problem as me
( I didn't have a camera, so I used another video)
I can't do "fastboot and recovery" in any way. Always gives me this error
https://www.youtube.com/watch?v=LJRqMPtKKX4

The best way to root armor 2
1) copy boot-verified.img from firmware folder to internal
2) install magisk
3) download any update in magisk
4) press install and select "select and patch a file"
5)select boot-verified. Img
6)after operation comlate copy magisk-patch. Img file in download folder to pc
7)flash it with sp flash tool