Develop Bugs

Micromax A57 - All Things Thread

This thread is for sharing stuffs for Micromax Ninja 3 A57 like Custom ROMs, Recovery, Kernels, etc.
Warning: These stuffs are not for newbies. Rooting and installing custom ROMs,etc are not for everyone. Rooting your phone will void your warranty. There are risks like bricking your phone and making it useless. Proceed at your own risk. You and only you are responsible for anything you do to your phone. With that said, lets proceed..
Micromax A57 Clone: Coolpad A7019
Driver Installation:
Download the drivers from here: http://www.mediafire.com/?eqvpdk6d2e1u4ne
Extract it to your desktop (or any other place, it doesn't matter)
Download and install Android SDK from here if not already done and install Android SDK Platform Tools and Google USB Drivers
Download UnlockRoot from here :http://www.unlockroot.com/
Download the given attachment. Extract adb_usb.ini from it and place it in C:\Users\(your username)\.android . Create the folder if not found.
Now enable USB Debugging in your phone through Settings->Applications->Development
Connect your phone and PC through USB
Go to Device Manager and right click on Micromax A57.
Right click on it and go to properties.
Go to drivers tab and click update driver
Click on Browse my computer for driver software and then navigate to the folder containing the downloaded drivers.
Make sure "Include subfolders" is ticked
It will search and install drivers
Rooting Guide:
First install drivers
Install and open UnlockRoot.
Click on root and then choose your device name
It will begin rooting and your phone will restart
Congratulations, your Micromax A57 is now rooted
To boot into recovery mode, switch off your phone. Press and hold vol+ and power key.
To boot into fastboot mode, switch off your phone. Press and hold vol- and power key.
Here are the Rom dumps of this phone for developers:
boot.img
checksum.md5
config.gz
recovery.img
system.info.gz
system.tar

__reserved__

micromax A57 rooting
tauquirahmed93 said:
This thread is for sharing stuffs for Micromax Ninja 3 A57 like Custom ROMs, Recovery, Kernels, etc.
Warning: These stuffs are not for newbies. Rooting and installing custom ROMs,etc are not for everyone. Rooting your phone will void your warranty. There are risks like bricking your phone and making it useless. Proceed at your own risk. You and only you are responsible for anything you do to your phone. With that said, lets proceed..
Micromax A57 Clone: Coolpad A7019
Driver Installation:
Download the drivers from here: http://www.mediafire.com/?eqvpdk6d2e1u4ne
Extract it to your desktop (or any other place, it doesn't matter)
Download and install Android SDK from here if not already done and install Android SDK Platform Tools and Google USB Drivers
Download UnlockRoot from here :http://www.unlockroot.com/
Download the given attachment. Extract adb_usb.ini from it and place it in C:\Users\(your username)\.android . Create the folder if not found.
Now enable USB Debugging in your phone through Settings->Applications->Development
Connect your phone and PC through USB
Go to Device Manager and right click on Micromax A57.
Right click on it and go to properties.
Go to drivers tab and click update driver
Click on Browse my computer for driver software and then navigate to the folder containing the downloaded drivers.
Make sure "Include subfolders" is ticked
It will search and install drivers
Rooting Guide:
First install drivers
Install and open UnlockRoot.
Click on root and then choose your device name
It will begin rooting and your phone will restart
Congratulations, your Micromax A57 is now rooted
To boot into recovery mode, switch off your phone. Press and hold vol+ and power key.
To boot into fastboot mode, switch off your phone. Press and hold vol- and power key.
Here are the Rom dumps of this phone for developers:
boot.img
checksum.md5
config.gz
recovery.img
system.info.gz
system.tar
Click to expand...
Click to collapse
Thanks for providing rooting procedure with stuff.I successfully rooted my A57 in first attempt. Now expecting CWM RECOVERY for A57.THANKS AGAIN,GREAT WORK!!!

hey dude..micromax a56 is the clone of coolpad a7019. see this.
http://s8.taobao.com/search?spm=a23...l&m=parm&cat=1512&ad_id=&am_id=&cm_id=&pm_id=
Micromax A57 has 1ghz processor rather tha 800mhz so it can't be the clone of coolpad a7019 cuz it has 800mhz processor.
What name do you get when you connect your device to pc in fastboot mode.(fastboot devices)>>> it will be the clone of your device.
I got the name of coolpad a7019 when i connected my device in fastboot mode to pc.

Hello dude i rooted and increased ram using swapper from anshubham's tutorial,i can play temple run n all, but i failed to install any of the asphalt versions from blackmart it said phone does not support but i heard many guys playing asphalt6 on a57,saw on youtube too,can u guys pls get me the link or way to install it pls
Sent from my calculator using Ginger Garlic paste

download it from other source over internet with sdcard files
Sent from my A56 using xda premium

anshubham said:
download it from other source over internet with sdcard files
Sent from my A56 using xda premium
Click to expand...
Click to collapse
Ya i installed bro,
Thanking you,
Yours faithfully,
Alien
Sent from my calculator using Ginger Garlic paste

anshubham said:
hey dude..micromax a56 is the clone of coolpad a7019. see this.
http://s8.taobao.com/search?spm=a23...l&m=parm&cat=1512&ad_id=&am_id=&cm_id=&pm_id=
Micromax A57 has 1ghz processor rather tha 800mhz so it can't be the clone of coolpad a7019 cuz it has 800mhz processor.
What name do you get when you connect your device to pc in fastboot mode.(fastboot devices)>>> it will be the clone of your device.
I got the name of coolpad a7019 when i connected my device in fastboot mode to pc.
Click to expand...
Click to collapse
I remember in shaktimaan dr.jackall made clone of geetha vishwas, thanx for ur info
Sent from my calculator using Ginger Garlic paste

Can anyone help me to get root on A87? I am facing an unique problem regarding android composite driver? If intereste pm me.

Till now no update on port cwm for mm a57 v.sad
Sent from my Micromax A57 using xda premium

Please help me unable to root Micromax ninja a 57
I tried all u said but unable to root my micromax ninja a57.
Unlock Root says no device detected. I hv installed a57 drivers, adb devices shown in device manager, usb.ini has been copied in the specified folder. But in fast boot mode my device is shown as coolpad a1709 . Do i hv to download the drivers of this device.

azhar2k7 said:
I tried all u said but unable to root my micromax ninja a57.
Unlock Root says no device detected. I hv installed a57 drivers, adb devices shown in device manager, usb.ini has been copied in the specified folder. But in fast boot mode my device is shown as coolpad a1709 . Do i hv to download the drivers of this device.
Click to expand...
Click to collapse
Have you enabled USB Debugging in Settings>Applications>Development ?

Device Bricked !! Flashed Stock ROM of Micromax Ninja A87 on Micromax Ninja 3 A57
Flashed Stock ROM of Micromax Ninja A87 on Micromax Ninja 3 A57
Well When I changed Folder Properties of '/phone/system' Folder as RW-R-R using SE File Manager my MMX A57 got crashed after Reboot.
It directly lead me to Recovery Interface on reboot.
I used Wipe user data/Factory Reset.
Data wiped successful but cant lead me to Factory Reset option.
I thought of Flashing Custom ROM of A57 but
but ihave mistaken and flashed A87 Custom ROM and all it end up into Crash/SoftBrick.
No what I can see on my screen is as below...(splash Bluish screen with particle like blinking)
{
"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"
}
Please help me out to restore my Micromax Ninja3 A57.
It was Rooted. SU/Busybox/Link2SD/Titenium Bckup/SE File manager Installed with Root Access.
Was in USB debugging Mode (ADB not working)
Issue Solved: (My friend had this Issue: Got Million 'Thanx' in person !!!):highfive::highfive:
Used Fastboot erase options-->Flashed Stock Recovery & Other partitions but failed at 'system' mount using fastboot-->Reased all partitions except Recovery-->Assumptions Worked--->Flashed using Recovery Boot-->Nothing on screen-->one time Vol- and then 2 times Power button (that allowed flashing Stock ROM from SD card)-->Hurrrah !!! Done !!!

@azhar2k7: First u understand problem-->you get solution.
The only problem is enabling your PC to communicate with your Android. If you using Windows XP you have to place adb.usb.ini file (choose the right one-as it has got modified as per need of various devices as well. You can find d Specific attached here)
1. Install Drivers for Micromax A57 (I guess you already had on your PC).
Check 'Android Composite ADB Interface' must be listed under Androd Devices in your Device Manager, while connected in USB debugging mode.
2. Download the attached Android ADB USB driver. Put the 'adb.usb.ini' into your Android-SDK directory i.e. in platform-tools (folder) where you must find 'adb'.exe and 'fastboot'.exe as well.)
3. Place the same adb.usb.ini in .Android folder in Documents and Settings in C:\
4. Now (Must) Reboot your PC
5. Now connect Device using USB cable in 'USB Debugging-Enabled' Mode and let all the drivers load. Confirm 'Android Composite ADB Interface' now be listed under Androd Devices in your Device Manager. Done.
6. Now open Command Prompt using run cmd (follow below example)
Now as if your SDK directory is: C:\Android-Sdk/Android/platform-tools
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\XperiaTipoDual>Cd Android-Sdk/Android/platform-tools (HIT ENTER)
C:\Android-SDK\sdk\platform-tools>
C:\Android-SDK\sdk\platform-tools>adb devices (HIT ENTER)
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
Micromax-A57 device
C:\Android-SDK\sdk\platform-tools>exit
Now your are done with your preparation.
1. To Root A57 Install & Run Unlockroot
2. Click ROOT
3. If will say Your phone is already rooted-IGNORE and click YES
4. Process will complete and your MMX A57 is now a Rooted device.

can't this be made into a flashable zip
Sent from my GT-I9103 using xda premium

Hey can you give me Antutu benchmark Device detailed specification for me?
please...!!!

ICS theme for a57
Hii,
I'm da devp'r of MicroFire Rom series for mmx a60...... (more than 3000 downloads....!!!! which is huge for this device... )
I'm interested in A57 also, to extend ma developments.....
does A57 has CWM ????
if yes, i'll try for rom,mods many things in future.....
Cool ICS Themes for now......... check these screenshots....
I also need one tester for theme..... (i dont have this device).....
A57 guys, im waiting for +ve replay from ur side..............

we don't have cwm
Sent from my GT-I9103 using xda premium

Well I'll try
navinkumar1892 said:
we don't have cwm
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
K i ll try to make one....do u test da recovery i built???...

I shall but if there is way to back up the os will be better
Sent from my GT-I9103 using xda premium

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?

[GUIDE][BR][LP]Complete guide for unlock bootloader and flash TWRP in H442F DUAL SIM

Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.

A really good job, I'm sure a lot of your fellow countryman will find this very useful!

Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!

Valeeeu dms irmao, ajudou dmss

Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.

Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).

How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana

Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?
Thanks @mrhamed
By the way, Do you know if this method also works on a 2017 Pro 16gb version?

This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
{
"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"
}

mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
Click to expand...
Click to collapse
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?

cHECKjAM said:
awesome.
by the way what is that screenshot?
If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse
It's my device screen.
I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626

@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.
So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.
However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..
---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------
The steps I took:
I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.
Then reboot to system.
Now bootloop...
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..

cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse
-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
I hope it works.

If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk

mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code:
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.
- Flash vbmeta_skip.img:
Code:
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.
If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse
I dont get any method working..
The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..
So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode
From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.
I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.
Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..

Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.
Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..

Is there anyone out there except for @mrhamed that has got this method working?
If so please share any real tutorial/steps/guide or whatever that can help.. thanks

mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse
Are you MIA?

EDIT: oops. wrong thread.

8.2.3 - 2019 Pro here, removing ethernet works like a charm.

LifelessLife said:
8.2.3 - 2019 Pro here, removing ethernet works like a charm.
Click to expand...
Click to collapse
Maybe you can explain a bit more?

mrhamed said:
*** You should unlock bootloader ***
-In fastboot mode:
Code:
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! F.ck the spy.
For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.

jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system

mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED

[GUIDE] 8.2.3 + Magisk root + MagiskHide + TWRP

Based on the work done in https://forum.xda-developers.com/t/how-to-root-and-install-magisk-on-nstv-2019-pro-v8-2-0.4189567/
User friendly guide written for Windows. Bash script for Linux flashing edited as well, but guide is focused on Windows users.
Enhanced upscaling is confirmed to work, have not been able to confirm AI upscaling (Unsupported content). Dolby Vision unconfirmed as I do not yet have a TV that supports it. If someone can verify if this works or not I will update this post accordingly.
Prerequisites:
USB-A male to USB-A male cable.
USB mouse.
USB drivers: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Android SDK: https://developer.android.com/studio/releases/platform-tools
Premade archive: https://drive.google.com/file/d/1XDzQyWviwVbjxNRsWJ8pG-HPSKW-Kzyl/view?usp=sharing
Unlocking the bootloader:
Go into Settings > Device Preferences > About.
Select "Build" several times until "You are now a developer!".
Go into Settings > Device Preferences > Developer options.
Activate USB debugging.
Connect one end of your USB-A to USB-A cable into the port furthest away from the HDMI on your SHIELD TV and the other into your computer.
Open a command shell (command prompt, powershell, bash, etc) on your computer.
Navigate to where you extracted the Android SDK.
Run command:
adb devices
Confirm that your device appears in the list of devices. If not this may be due to:
USB cable not connected properly. Check cable.
Device not recognized. Reinstall drivers/restart computer. Generic Android USB drivers may work if NVIDIA doesn't.
Run command:
adb reboot bootloader
Wait for fastboot to start.
Run command:
fastboot devices
Confirm that your device appears in the list of devices. If not see above reasons.
Run command:
fastboot oem unlock
Flashing:
On your computer navigate to where you have extracted the archive from the post.
Run command:
flash-all.bat
If all goes well you should be rebooted into TWRP recovery once the procedure is done.
Connect your USB mouse to the USB port closest to the HDMI port on your SHIELD TV.
Slide to unlock.
Go into Mount.
Select "Enable MTP".
Move "Magisk-v23.0.zip" from the downloaded archive to your SHIELD TV.
Select "Disable MTP".
Go into Install.
Select "Magisk-v23.0.zip" and install it.
Go into Reboot.
Select "System".
Getting Magiskhide to work:
Install Termux from Google Play.
Open Termux and run:
su
cat >/data/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d.
Run:
chmod +x /data/post-fs-data.d/bootfix-post.sh
cat >/data/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d.
Run:
chmod +x /data/service.d/bootfix-service.sh
Open Magisk (Settings > Apps > See all apps > Magisk > Open)
Select the shield icon on the bottom bar.
Enable MagiskHide
Reboot system
ALL DONE!
Sources of the premade archive contents are the following:
Android SDK: https://developer.android.com/studio/releases/platform-tools (fastboot)
The following Shield ROMs from https://developer.nvidia.com/gameworksdownload#?search=2019&tx=$additional,shield:
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.0 (mdarcy.dtb.img)
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.2.3
Latest TWRP recovery from https://twrp.me/nvidia/nvidiashieldandroidtv2019.html (recovery.img)
Latest Magisk from https://github.com/topjohnwu/Magisk/releases

reboot to recovery command fails with error and doesnt reboot to twrp. manually booting twrp from fastboot via fastboot boot recovery.img works

can someone explain the "MagiskHide" section of the guide? i dont have those .sh files present in /data/ . Should i just create them with the resetprop commands as the content? i just dont see where you even got those from

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes

Can this work on the 2017 model?

Is this the most updated guide also for the magisk hide section whats the easiest way to copy and paste this all in terminal .

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

albinoman887 said:
View attachment 5402781
I revised some steps and am now passing CTS fully... AI upscailing still says unspoorted content but i dont know if thats cuz i dont have a 4k TV, enhanced works.... i'll write up a quick and dirty guide later tonight... I need to look through everything and make sure i didnt install unneeded ****... but mainly just some props changes
Click to expand...
Click to collapse
Did you get around to make that guide?
Im struggling getting around the cts check.

bolme123 said:
Did you get around to make that guide?
Im struggling getting around the cts check.
Click to expand...
Click to collapse
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed

albinoman887 said:
Ahh crap... I'll be totally honest I completely forgot . I'll get that done by the time I go to bed today. . to be honest though I think what might have done it was I changed my device fingerprint using MagiskPropsConfig module and chose the one for sheid that's included with your IPTV service ... Other than that I just made sure there was no like things exposed that didn't need to be and removed
Click to expand...
Click to collapse
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.

bolme123 said:
Thank you man, you nudged me in the right direction.
I was able to successfully pass the ctsCheck, and i accumulated new knowledge, thanks man!
Have a blessed day.
Before i go along with my day, did you have any success with LSPosed?
I''m gonna check now if i'm able to disable the SECURE_FLAG without tripping the SafetyNet.
Click to expand...
Click to collapse
has anyone gotten AI- Upscaling to work ?

tokoam said:
has anyone gotten AI- Upscaling to work ?
Click to expand...
Click to collapse
no just the enhanced

Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk

So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?

jamiethomaswhite said:
So, any idea what to do when having diligently followed along and the result is those errors and now a Shield that can't boot and doesn't respond to ADB/Fastboot calls...
I can't believe I just blindly followed along and now my favourite thing in existence is bricked. I use it literally 24/7. Any ideas?
Click to expand...
Click to collapse
its not bricked, and you didnt follow along else you wouldn't be in your current state. I literally just did this on my 2019 shield pro coming from the private beta without issue. The OP instructions need a few updates but most of those steps you should be familiar with anyway if you're going to be modding your devices
I lied, infinite loop, seems some derpy protection is getting tripped
0bin - encrypted pastebin
0bin is a client-side-encrypted alternative pastebin. You can store code/text/images online for a set period of time and share with the world. Featuring burn after reading, history, clipboard.
0bin.net

aouamed said:
Nvidia Shield TV pro 2019 :
I did all the steps and I have this error
I start again several times the same problem
Pasteboard - Uploaded Image
Simple and lightning fast image sharing. Upload clipboard images with Copy & Paste and image files with Drag & Drop
pasteboard.co
in start there is the following message...
Photobox | Online Photo Printing & Personalised Photo Gifts
Make stories from your photos. Print photos online or create personalised gifts with Photobox, the photo specialists. Photo Books, Prints, Canvases, more.
www.photobox.co.uk
Click to expand...
Click to collapse
its because Android is retarded and the script needs modified. After that error it should have booted into system setup, simply reboot into bootloader and `fastboot boot recovery.img` then continue onto installing magisk

Thank you for your reply...
I succeeded rooted my NSTV 2019 Pro v8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image 8.2.3
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image 8.1.0 (vbmeta_skip.img)
TWRP : twrp-3.5.2_9-0-mdarcy.img
Magisk : Magisk v23.0 'beta'
Tested :
Safetynet checks pass fine...
reboot with magiskhide without probleme script 'bootfix-post.sh' 'bootfix-service.sh'
Demo mode work only Enhanced Mode
Other work well ...
Thank xda

Any solution for unlimited loading android splashscreen after enabled MagiskHide in Magisk after reboot shield?

Enable MagiskHide :
open PowerShell :
adb shell
su (confirm permission with remote control )
cat >/data/adb/post-fs-data.d/bootfix-post.sh
resetprop ro.boot.verifiedbootstate orange
Press Ctrl+d:
chmod +x /data/adb/post-fs-data.d/bootfix-post.sh
##############################
cat >/data/adb/service.d/bootfix-service.sh
resetprop ro.boot.verifiedbootstate green
Press Ctrl+d:
chmod +x /data/adb/service.d/bootfix-service.sh
Reboot system

do i need to have the nvidia controller/gamepad for this? everything that needs to adb or fastboot, so far, works but ill get to a screen and itll ask to confirm something and so on. except i dont have the gamepad. if you guys say i need one, of course ill go buy one but in the mean time, if not, how are you going through it?
edit:
also, does 8.2.0 or 8 .2.3 matter? the first time, i did do it on 8.2.3 but had to restart because i didnt have a gamepad.