Develop Bugs

[ROM | 1/5/2011] - NANDDROID - Android Froyo X Ginger Build

HTC Touch HD NANDROID Thread
!! Important !!
Guys i now jack-all at the moment for the Touch HD NAND Process, So dont even contemplate the idea of asking me !! Go to Tida8s forum, and ask there !
Although i already know YOU Will, But for those who have forgotten !!
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Change Log
- 7-7-2011 Vir Twitter
Hi, guys News on blackstone nand. Maybe Sunday I will have the new files for the testing team.
- 1-07-2011
- 23-6-2011 Vir Twitter
Just give it the final touch. So it's official NAND BLACKSTONE 7/1 GET READY GUYS. THANKS GUYS
- 13-06-2011 07:36 AM.
-i will be using froyo x ginger w/o gapps (READY)
-building nbh (ready)
-working with the recovery.img (now)
- 14-6-2011 05:11 AM
UPDATE
ok guys. maybe friday i will be uploading FROYO X GINGER NAND FOR BLACKSTONE
just take a look inside the build update. and let me know if everything is good or if we need to add anything. thanks guys. eta: friday. build only
- 12-6-2011 Vir Twitter
(build) FROYO BLUE CWM 2011.06.12. blackstone. ready.
Youtube NAND v2 on Tida8's Touch Pro 2
- 10-06-2011 11:15 PM
update nand build. OK GUYS, GREAT NEWS. WE HAVE DATA WORKING. OH MAN THIS IS GETTING GOOD NOW. SO WE HAVE WIFI AND DATA WORKING.
- 10-06-2011 04:56 PM
update on blackstone nand
1-froyo x ginger blackstone nand is ready (rom)
2-building the blackstone.NBH now
thanks
- 08-06-2011 04:56 PM
Update on blackstone nand
Ok guys, I just went online to track my phone it will be here tomorrow.
1- I already have froyo x ginger ready with w/o gapps. That's the build that I will be using
2- need you guys to relax. This take time.
3- please don't ask for eta. It will be done when is done.
3- I will keep you guys updated on the proccess.
4- remember thanks to the A TEAM we have nand. It just a matter of time till our devices can have it. But we need people for this to happen
5- eventually I will get more devices, cuz the the only way to start nand testing is to have those the devices
6- my goal is see every device with nand. And to tell you guys the truth I can't do it by myself. Yes it will take time
7- I'm going to talk with tracker to see if we can have an IRC for . maybe
Also remember guys. I have a family outside android. 2 kids and a wife plus a job and a house. I'm always super busy
It's official nand testing for blackstone it' here guys
Sent from my CDMA BLAZN 2.2.2 NAND VERSION using Tapatalk
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
- NAND Tutorial
Page 1 By Tida8
setup you sdcard. format your card to fat32 and add this 3 updates
-froyo blue blackstone nand build
- kernel update
-root update
1-first we need to get android sdk set up for you devices.
http://dl.google.com/android/installer_r11-windows.exe (this the exe files) (Recommended)
http://dl.google.com/android/android...11-windows.zip (this the zip)
2- create 2 folder on you C: driver
- RUU (already has the ruu_signed.NBH AND task29)
- ADB (already has the recovery.img)
-download BlackstoneAdvancedRUU and unzip folder.
http://www.multiupload.com/RLJEC2GRCH
for more info on this ruu http://forum.xda-developers.com/showthread.php?t=943851
-download adb and unzip it in your adb folder http://www.multiupload.com/NEEPYUDO6T
3- set up path for your adb and fastboot
right click my computer on your desktop pc. advanced system settings. environment variables. then system variables and double click on path. add this line at the end. just like that
;C:\adb
click ok everything
4- test adb
-boot any build (blue, ginger, frx06. etc....)
-download PdaNet http://www.multiupload.com/OVJ9V01M4F now install pdanet and follow the screen. pdanet will ask to connect your phone. let it finish. when done disconnect usb.
-on your android build go to settings/applications/development/ and check ubs debugging, stay awake, and allow mock locations. now connect you usb
-on your pc. start, run, type cmd, and type adb devices and enter
- you should see your device. you may see this 00000000000 device. that's ok that's your device ID
- great adb is working
5- set up fastboot (the set up for fastboot is done when you flash RHODIMG.nbh)
-when you see the blue screen with usb connected fastboot driver will install. that all
6- [TUT][HSPL] Hard-SPL Unlocker for Blackstone
http://forum.xda-developers.com/showthread.php?t=431217
7- task29 set up ( this will erase windows mobiles) this tool is very important to flash nand or if you want windows mobile back on your phone
-turn off your phone. press vol down and power. you will see the (tricolour screen!). connect your phone usb. it may install drivers so wait till finish.
-open RUU folder on your c: driver pc
-right click on BlackstoneAdvancedRUU.exe and choose run as administrator and follow the screen. then the phone will reboot. but it wont pass the htc boot screen, just take the battery out.
8- flashing LK bootloader ruu_signed.NBH
- turn off your phone. press vol down and power. you will see the (tricolour screen!). connect your phone usb. it may install drivers so wait till finish
- open RUU folder. right click on BlackstoneAdvancedRUU and choose run as administrator. follow the screen. then the phone will reboot. you should see the blue screen. it may install drivers so wait, when finish you will see fastboot mode at the bottom in small letters. if nothing happen just pull the battery. read guide 9 recovery.img
9- how to flash recovery.img
-put battery back and connect your phone usb
-click on power. you will see blue screen look for fastboot mode at the bottom.
-on your pc. go to run type cmd and type this command to get to adb folder on your c: drive
cd C:\adb
then type
fastboot flash recovery recovery.img
wait till it finished. then to get to recovery mode type
fastboot boot recovery.img
the end key is (enter) vol down and up is to move. install updates in this order
-froyo blue build update
-kernel update
-root update
10- when done reboot. take the usb cable out. and welcome to nand
good luck and god bless you all
GUYS, ANYTHING ELSE THAT YOU GUYS WANT ME TO ADD PLEASE LET ME KNOW
i'm still updating this page-----------------------------
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Page 2 by explicit
NOOB guide for blackstone nand BY explicit
IMPORTANT!!! If you don't have HARD SPL installed on your phone do not continue.You must have HARD SPL for Blackstone installed on your phone
More about HARD SPL in step 6.
Format your micro SD card to fat32.
Add this 3 files from NAND BLACKSTONE FULL PACKAGE
-update-blackstone-nand.zip
- kernel update.zip
-root update.zip
1. Download the android-sdk for your system and install everything on it. Android-sdk depends on Java SE Development Kit (JDK), so if you
don't have java Development Kit installed dovnload it and install it before installing android-sdk. Even after installing On x64 OS you still may get
Java not found during the installation of android-sdk.In that case click Back and than again Next. It should find it now.
Java Development Kit download: http://www.oracle.com/technetwork/ja...ads/index.html
Android-sdk download.Choose installer_r11-windows.exe (Recomended) http://developer.android.com/sdk/index.html
2. Create 2 folders on your C:\ drive
- ruu ( Here we need to have BlackstoneAdvancedRUU from the link below and ruu_signed.nbh from BLACKSTONE NAND FULL PACKAGE)
- adb ( here we need all files from the adb link below)
-download BlackstoneAdvancedRUU and unzip it un the ruu folder from above.
BlackstoneAdvancedRUU http://www.multiupload.com/RLJEC2GRCH
for more info on this ruu http://forum.xda-developers.com/showthread.php?t=943851
-download adb and unzip it. Copy all the files from the extracted archive in the adb folder above.
The path to adb.exe should be like this C:\adb\adb.exe
adb http://www.multiupload.com/NEEPYUDO6T
3. Set up path for your adb and fastboot
right click my computer and select properties. Now go to advanced system settings. Under the Advanced tab at the bottom select Environment Variables.
Under System variables find the line "path" For the Variable name stays path and for the Variable value at the end add this ;C:\adb
Close all windows with clicking OK.
4. test adb
-boot any build (blue, ginger, frx06. etc....)
-download PdaNet http://www.multiupload.com/OVJ9V01M4F now install pdanet and follow the screen. pdanet will ask to connect your phone. let it finish. when done disconnect usb.
-on your android build go to settings/applications/development/ and check ubs debugging, stay awake, and allow mock locations. now connect you usb
-on your pc. start, run, type cmd, and type adb devices and enter
- you should see your device. you may see this 00000000000 device. that's ok that's your device ID
- great adb is working
5. Set up fastboot (the set up for fastboot is done when you flash ruu_signed.nbh from NAND BLACKSTONE FULL PACKAGE)
-when you see the blue screen with usb connected fastboot driver will install. that all
6- [TUT][HSPL] Hard-SPL Unlocker for Blackstone
http://forum.xda-developers.com/showthread.php?t=431217
7. Task29 set up ( this will erase windows mobile from your phone) this tool is very important to flash nand or if you want windows mobile back on your phone
-turn off your phone. press and hold Volume down and power on your phone. you will see the (tricolour screen!). connect your phone to usb. it may install drivers so wait till finish.
-open RUU folder on your c: drive
-right click on BlackstoneAdvancedRUU.exe and choose run as administrator, select "Perform Task 29 only" and follow the screen. then the phone will reboot,
but it wont pass the htc boot screen, just take the battery out.
8. Flashing LK bootloader ruu_signed.NBH
- turn off your phone. press and hold Volume down and power on your phone. you will see the (tricolour screen!). connect your phone via usb. it may install drivers so wait till finish
- open RUU folder. right click on BlackstoneAdvancedRUU and choose run as administrator. Select Custom RUU (Task 32) and follow the screen. then the phone will reboot. you should see the blue screen.
it may install drivers so wait, when finish you will see fastboot mode at the bottom in small letters. if nothing happen just pull the battery. read guide 9 recovery.img
9. How to flash recovery.img
-put battery back and connect your phone via usb
-click on power. you will see blue screen look for fastboot mode at the bottom.
-on your pc. go to run type cmd and type this command to get to adb folder on your c: drive
cd C:\adb
then type
fastboot flash recovery recovery.img
wait till it finished. then to get to recovery mode type
fastboot boot recovery.img
the end key is (enter) vol down and up is to move. install updates in this order
-froyo blue build update
-kernel update
-root update
10- when done reboot.
Read more:
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
!! Important !!
Guys i now jack-all at the moment for the Touch HD NAND Process, So dont even contemplate the idea of asking me !! Go to Tida8s forum, and ask there !
Although i already know YOU Will, But for those who have forgotten !!
Click to expand...
Click to collapse

waiiiiiiiiiiiiiiiiiiiiting

mero0100 said:
waiiiiiiiiiiiiiiiiiiiiting
Click to expand...
Click to collapse
yeah, but i think it sahould be done by tonight or tomorrow

Really hope so.. I keep my fingers crossed about two weeks

NandDroid htc hd
I hope someone can make it.... i can't wait for it!!!! From C.R.

even more fun to know that he was also working on a nand version of gingerbread and honeycomb

Sounds interesting!
Sent from my MZ604 using XDA Premium App

Simon_WM said:
yeah, but i think it sahould be done by tonight or tomorrow
Click to expand...
Click to collapse
i didn't want to disappoint you but tiad say that he will buy blackstone to make trials on it till now he didn't have blackstone so not tomorrow
hope i am wrong and you are right as i want to play with android also

mero0100 said:
i didn't want to disappoint you but tiad say that he will buy blackstone to make trials on it till now he didn't have blackstone so not tomorrow
hope i am wrong and you are right as i want to play with android also
Click to expand...
Click to collapse
... would could be right, but either way if he is going to this is a massive step towards getting NAND !!

I love it. Keep it up. Waiting n waiting n waiting........
Sent from my HTC HD2 using XDA App

mel69hash said:
I love it. Keep it up. Waiting n waiting n waiting........
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yup, patients is the game

Entering lotus position, waiting...

Guys?
I am little bit off but why are u so happy? NAND means that we will have full android on our blackstone? withnout emulating or things like that? Will it actually work properly?
thank u for response

OMG Nice
And i think my Blackstone is Crap now if full NAND comes yeah Baby ;D

unstable_ said:
Guys?
I am little bit off but why are u so happy? NAND means that we will have full android on our blackstone? withnout emulating or things like that? Will it actually work properly?
thank u for response
Click to expand...
Click to collapse
Just because Android is flashed on the phone instead of WinMo doesn't do magic. It will probably perform the same as from SD-card in case of problems. I believe R/W speed is somewhat faster from nand (different type of ROM than SD-card).
Edit. Besides, isn't there still some problems with nand on GSM phones?
Please fill me in here...

i can see everyone is just waiting to be done,and almost no one is actually contributing...not even with a small donation,because the guy is going to buy the phone so he could provide us something we have eagerly waited for,so even one dollar would be appreciated i am sure

farukb said:
i can see everyone is just waiting to be done,and almost no one is actually contributing...not even with a small donation,because the guy is going to buy the phone so he could provide us something we have eagerly waited for,so even one dollar would be appreciated i am sure
Click to expand...
Click to collapse
Not that i would really be in android/nand/... but i noticed this debate. The problem is that there were just too many false prophets with no results. I would rather recomend a donation to download (like xming) so people can donate for results not for good wishes.

farukb said:
i can see everyone is just waiting to be done,and almost no one is actually contributing...not even with a small donation,because the guy is going to buy the phone so he could provide us something we have eagerly waited for,so even one dollar would be appreciated i am sure
Click to expand...
Click to collapse
Am waiting on the release, then will help with doing bug testing and so on =D

root said:
Not that i would really be in android/nand/... but i noticed this debate. The problem is that there were just too many false prophets with no results. I would rather recomend a donation to download (like xming) so people can donate for results not for good wishes.
Click to expand...
Click to collapse
true (10 chars)

farukb said:
true (10 chars)
Click to expand...
Click to collapse
Yeah, for Android development, i think that seems fair,
What do you guys think ?

newbies guide to rooting, actually lets go one step back..

...anyone care to write a baby step guide to rooting a N900T?

CF auto root is the easiest method.
Go original development section and take a look.

mingkee said:
CF auto root is the easiest method.
Go original development section and take a look.
Click to expand...
Click to collapse
I'm dumb and don't understand the procedure written about it - in a nutshell.

Limeybastard said:
I'm dumb and don't understand the procedure written about it - in a nutshell.
Click to expand...
Click to collapse
Google zeodmax galaxy note 3. He has a video and step by step how to do it. Screen shots as well
NOTE 3
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
http://galaxynote3root.com/
NOTE 3

It doesn't get any easier!

BACARDILIMON said:
Google zeodmax galaxy note 3. He has a video and step by step how to do it. Screen shots as well
NOTE 3
---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------
http://galaxynote3root.com/
NOTE 3
Click to expand...
Click to collapse
Thanks, will do.:good:

You should use ChainFire's method. This is much more easier and you don't have to care the bootloader.
http://forum.xda-developers.com/showthread.php?t=2466423
Prerequisites:
1. Samsung Kies installed
2. Your Note 3 has USB debug enabled.
3. Android SDK installed
Go to about device.
Tap Build Number few times.
Go to developer options.
Check USB debugging.
Make sure Kies is closed.
Steps:
1. Download and locate, and unzip the CF package, and open Odin.
2. Connect the phone.
3. Locate the Android SDK and go to tools where the adb.exe is. Copy the address on the address entry in My Computer.
4. Open command window by typing
cmd
in search (windows 8) or run (other windows).
5. type
cd\
6. Type cd and hit spacebar once, locate the mouse cursor to the command window, right click and paste. If everything goes well, you should see the address of the adb file.
7. Type
adb reboot download
8. Go to Odin, click and check PDA, and locate the .tar file (included in the package).
9. Press start when you're ready.
10. Your phone is rooted now.

I want to root but I'm on Ubuntu

I used Max's way. Two minutes and done. You don't need Keis. Just ODIN the file, flash the zip, and done.
http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/

bobbyphoenix said:
I used Max's way. Two minutes and done. You don't need Keis. Just ODIN the file, flash the zip, and done.
http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/
Click to expand...
Click to collapse
That is the safest and best way
NOTE 3

ramirez3805 said:
I want to root but I'm on Ubuntu
Click to expand...
Click to collapse
In the general thread for note 3 cf-autoroot someone posted how he did it with Ubuntu. Looked easy enough if you are familiar with Ubuntu, which I assume you are.
Sent from my SM-N900T using XDA Premium 4 mobile app

One of the Easiest
Check this YouTube Vid...
http://www.youtube.com/watch?v=dcWkKuU9Fyo

mingkee said:
You should use ChainFire's method. This is much more easier and you don't have to care the bootloader.
http://forum.xda-developers.com/showthread.php?t=2466423
Prerequisites:
1. Samsung Kies installed
2. Your Note 3 has USB debug enabled.
3. Android SDK installed
Go to about device.
Tap Build Number few times.
Go to developer options.
Check USB debugging.
Make sure Kies is closed.
Steps:
1. Download and locate, and unzip the CF package, and open Odin.
2. Connect the phone.
3. Locate the Android SDK and go to tools where the adb.exe is. Copy the address on the address entry in My Computer.
4. Open command window by typing
cmd
in search (windows 8) or run (other windows).
5. type
cd\
6. Type cd and hit spacebar once, locate the mouse cursor to the command window, right click and paste. If everything goes well, you should see the address of the adb file.
7. Type
adb reboot download
8. Go to Odin, click and check PDA, and locate the .tar file (included in the package).
9. Press start when you're ready.
10. Your phone is rooted now.
Click to expand...
Click to collapse
Been trying to find the dev options now I know how lol thanks brah..
Sent from my SM-N900T using Tapatalk 2

BLU Life One X 2016

My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)

WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!

Reserved #4

Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.

Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol

Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.

Do you have a link to the drivers
Sent from my 6045X using Tapatalk

I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.

OK thanks
Sent from my 6045X using Tapatalk

I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.

SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.

jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.

hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,

Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,

clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices

SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.

jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.

hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.

Unlocking Bootloader/ Magisk Attempt

MAGISK FULL GUIDE (APK for install and other mods coming soon!)
The bootloader unlock is pretty similar to any other phone.
Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer Options. Make sure to enable OEM unlocking.
(On PC) "adb reboot bootloader", "fastboot flashing unlock_critical", use volume to select unlock. THIS WILL ERASE ALL CONTENT ON YOUR DEVICE.
IF YOU DONT WANT TO DO THIS FROM SCRATCH, SKIP TO PART 2
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk Manager apk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
PART 2:
download the patched magisk_boot.img from here https://drive.google.com/file/d/1-7NWj8_jFH8AtpTTpXITOv1eh-wo7xlz/view?usp=sharing
adb reboot bootloader
fastboot boot magisk_patched.img
PART 3 - All right, lets make it permanent!
Place magisk_patched.img on your sd root
adb shell
su
cd /dev/block/by-name/
chmod 777 boot_a
chmod 777 boot_b
DEV=$(ls /dev/block/by-name/boot_b); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
DEV=$(ls /dev/block/by-name/boot_a); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
Reboot and we are good!
I am working on an app to streamline the process as well as provide additional mods and addons to the device. I hope to have something for you guys by the end of the week.
I do plan on streaming some of this stuff (twitch.tv/goingh0st), and am working on a section of my discord for the same thing (World of Gh0st)
https://www.patreon.com/GoinGh0st
Thank you for your support and I cant wait to get more stuff to you guys!

Would you mind sharing the patched Boot?
Everything you posted is spot on, try switching partitions.

Perseu5 said:
The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Select oem bootloader unlocking. Adb reboot bootloader, fastboot flashing unlock, use volume to select unlock. This will erase all content on your device.
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
Attempted to boot the patched boot image which resulted in a bootloop.
Out of town for the time being but will be attempting something different when I get back in a day or so.
Click to expand...
Click to collapse
I tried the same and I had the same issue. Seems the the boot partitions, both a and b, are not writable or erasable even with the bootloader unlocked.
I even went as far as unlocking critical and still the same issue.
Sent from my Surface Duo using Tapatalk

really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C

So anyone tried my method? Should work

avetny said:
really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C
Click to expand...
Click to collapse
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
u mean usb type A to C?

avetny said:
u mean usb type A to C?
Click to expand...
Click to collapse
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
avetny said:
So anyone tried my method? Should work
Click to expand...
Click to collapse
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
ok I'll try it tomorrow after work my self

I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!

Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
im still at work....
Please try it out....I remember in my pass that was a issue with many phones

Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
How did it go?

Just tried with a to c cable with same result unfortunately. Sending successfully, writing boot_b gives flashing not allowed to this partition. Also did a critical unlock and verified with fastboot oem device-info

wtf!!!!!!!!
---------- Post added at 09:21 PM ---------- Previous post was at 09:11 PM ----------
...... I will return this phone man.

I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?

panzercool said:
I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?
Click to expand...
Click to collapse
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
Would you post the patched boot image?
I want to try this myself without going through the prerequisite hoops.

Updating the main post now. I figured it out guys!

Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
oh broo tell us whats happening

Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
Tell us!!!

HOWTO: Install developer image for 2019 shield tv pro !READ WARNING!

!!WARNING!!
1st
You cant boot the 2019 Pro with a magisk patched boot.img. If you try to run the install script with a patched image it will brick the device!!!
The script re-locks the bootloader so if you want to try using any modified .img files you need to flash them individually or modify the script.
2nd
After you unlock the BL AI upscaling is disabled. Even after the BL is re-locked. Flashing back to the normal firmware should fix this but I am not sure of that.
3rd
After flashing the "developer" firmware the fact is it is no different than the standard firmware right now.. If Nvidia provides a rooted image in the future plz pm me and I will update this post.. I am leaving this post up for anybody who like myself is looking for shield pro 2019 info and was wondering if it could be rooted taking steps similar to the 2017 here
So with that said..
I just switched from a firestick 4k as my streaming device of choice to a shield pro 2019. I tried the cheaper $160 version first but when I looked at the specs and tried to do anything to it the lack of usb ports and 8gb storage made upgrading to the $200 pro a no-brainer.
So far I have gotten a few nice tweaks installed and Ill go into that in another post.
Things you'll need
A windows or linux PC with adb-fastboot binaries SDK Platform Tools
A male to male usb cable (my laptop has a usb-c input but It wouldn't work to connect to the shield)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image HERE
SHIELD Family Windows USB Driver HERE
USB keyboard (or shield game controller possibly?)
First thing I did was enable USB debugging. Its the same process as other android devices. Device Preferences> About > then tap build info 10x. Then Device Preferences> Developer Options> enable usb debugging.
Now I made my own male to male usb cable by just splicing two old cables together matching the colors to each other. No special wiring is needed.
I used windows but it's easier to use linux if you can since windows required me installing a driver for fastboot to work.
To put the Shield into fastboot mode. Attach the usb cable to the usb port furthest from the hdmi port. And attach a usb keyboard to the usb next to the HDMI-out. Also keep the device connected to an HDMI display during the process. If you are using a pc that shares a screen with the shield tv then I suggest using chrome remote desktop to run the commands on the pc while the shield is using the display.
Windows 10: hold shift and right click in the platform tools folder
select open powershell here
type .\adb devices
type .\adb reboot bootloader
Linux you can just open a terminal and as long as adb is installed type adb devices then adb reboot bootloader
When it reboots there is an option to unlock the bootloader. You just select that and let it reboot again. You'll know it is unlocked because when it boots up with an unlocked bootloader a warning telling you the firmware cant be verified comes up for about 10 seconds.
To flash the firmware you need to get back into fastboot. Either go through the setup again quickly to enable usb debugging once more or there's another way to enter fastboot using a key combination (A+B on the shield controller, I don't know the combination on a keyboard).
Once its in fastboot again if you are using linux
unzip nv-recovery-image-shield-atv-2019-pro-8.2.0-dev_rooted.zip and cd into the directory containing the flash-all.sh script
and run it.
In windows 10 I needed to install the nvidia fastboot drivers before fastboot would detect it.
In device manager action> scan for hardware changes there should be a device with Fastboot in the name
You need to choose the option to update driver then select "have disk" and select the android_winusb.inf file and the device type should be Android Bootloader Interface.
Once fastboot drivers are installed open the file manager to the folder containing the flash-all.bat file, hold select and right click to open powershell in this location and type .\flash-all.bat
After the script runs the device will flash the dev firmware and lock the bootloader again.
I patched the boot.img with magisk but it wouldn't boot with it. I may try again tonight with different settings to get magisk to work.

EDIT: edited post to remove quote per op request lol. apparently after they posted the dev os firmware and i reported it to nvidia they never fixed it.. the dev os firmware on nvidia site for nstv pro 2019 model is exactly same as stock lolol
last i dled the dev os firmware it wasnt actually dev os firmware and was regular firmware.. once bl is relocked also u cant root it since it will no longer allow custom firmware..
this instruction us flawed to say the least

Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
HTML:
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458

mrhamed said:
Thank you for start trying run magisk :good:
I didn't test patched boot-image, but when you can't boot, it maybe related to "vbmeta"
It seen nvidia don't like to provide root access to customers! because it remove vbmeta_skip.img from official 8.2.0-dev_rooted.zip package.
So may be you should try flash vbmeta_skip.img to achieve successful boot.
I attached vbmeta_skip.img from 8.1.0-dev_rooted.zip for you.
fastboot flash vbmeta vbmeta_skip.img
I suggest keep testing on @Steel01 LOS releases. If we achieve an stable custom rom open-source, it's much much better than vendor release! I prefer freedom vs AI-Upscaling.
LOS releases: https://forum.xda-developers.com/showpost.php?p=83587703&postcount=458
Click to expand...
Click to collapse
yes, disabing vbmeta should be a given lol.. theres already root and steps have been discussed spread out in various threads already.. its just not a simple "flash this and youre rooted" so ppl keep asking about it lol