Related
NABI LAB v2
{
"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"
}
NOTE: The program is becoming long in the tooth and not as useful with Jellybean on Nabi. For Jellybean TWRP installs check this repackaged version of Nabilab http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
This is a tool for performing various automated tasks on the Nabi 2. It's written as a windows command line batch file, and v1 has been tested by a few members of the forum with positive results. Hopefully this means all the bugs are worked out, most issues have been typos on my part. It's an attempt to include all recent developments in Nabi 2 rooting, Gapps install, recovery methods, and modding and provide and all in one experience. Alot of this is my own original work, and other parts are creations of others intact or modded for Nabi use. Using the latest known working methods, it hopefully prevents users from having to install, break things, uninstall, recover, try new method, ask forum questions, try another method, and all the while for those with kids having them ask why you broke their toy.
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
A test version of NabiLabGUI is here: http://forum.xda-developers.com/showthread.php?t=2391449
Overview
Video Overview of Nabi Lab v1 mostly the same as v2
-Install ADB/Fastboot digitally self-signed drivers.
-Root the Nabi 2
-Install Gapps(Play Store, etc)
-Fix Android is upgrading message
-Make a stock backup of unrooted device
-Install a stock 1.9.37 in the event of loss of backup.
-Install stock, or TWRP recoveries
-Tablet Information
-Lockscreen modding tool
-NabiLab patching system to install updates to this program
-Fix TWRP touchscreen issues
-While not a built in function using the tools to fix broken Wifi
Download
Read the installation section below to determine which version you want.
File names:
NabiLabFull.zip 1.1GB
Download
NabiLabLite.zip 97MB
Download
Download Mirror
NabiLabv2Update.zip 10.1MB(upgrade patch for v1 users)
Download
Download Mirror
Installation
There are 2 versions of Nabi Lab: Full and Lite. The full edition is 1.1GB and includes a stock 1.9.37 backup of the system, data, and boot partition. It's usefulness is really only of interest to those that need to restore to a stock backup. It should be a rather limited group of people as you should have a backup of your system already that you could use in lieu of this. However in the event you have lost your backup, or have mangled the system to the point you aren't sure what to do, the option to restore to stock 1.9.37 is in the full edition. The likely download of choice is the Lite edition at a more manageable download size of 97MB. It has all the tools of NabiLab just without the ability to restore a stock backup(which of course you have one of your own). The upgrade patch zip is for v1 users.
NEW INSTALLS
1) Download Nabi Lab
NabiLabFull.zip 1.1GB
NabiLabLite.zip 97MB
2) Extract the zip files to a location of your choosing. Run the NabiLab.bat file.
PATCH INSTALLS(For version 1 users)
1) Download NabiLabv2Update.zip 10.1MB
2) Extract the zip IN to the directory NabiLab is in not FROM the directory. What ever your unzip program it should be extracting to X:\somefolder\somefolder\yourNabiFolder\ If you do it right there will be a file RunOncePatch.bat in the same folder as NabiLab.bat, and a NabiPatch.zip in a new folder called patch in your NabiLab folder.
3) Run RunOncePatch.bat
note: This is only necessary this time, any future patches will be applied by downloading a NabiPatch.zip, and installing inside the NabiLab program.
Prerequisites
1) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
2) Unsure you are on version 1.9.37. Enter Mommy/Daddy mode. Open settings->About Tablet->Product Version. If it's at something less then 1.9.37 go up to the "Update" selector and check update and install. You may have to do this more then once.
Notes: At this point it is believed that the Madagascar Nabi 2, and UK version have product versions of 1.9.34, and 1.9.35/6 respectively. You can attempt to use NabiLab at those versions but I cannot guarantee results. Most things should work however.
Usage
Obviously using this product on your Nabi 2 voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Installing drivers
The provided drivers are for Windows XP,Vista, 7 and 8 32bit and 64bit. They are modded version of the drivers by 1wayjonny found in this thread. The mod to those drivers are adding the Nabi, and the HP Touchpad Tenderloin(only because I have one). The are digitally self signed by "NabiLab".
Menu Option 1 - Auto Install
Check in the top left corner under Detected OS to see if it matches your configuration. The most important part is if it says "x86"(32bit) or "AMD64"(64bit) this is what the auto installer is going to install. If you don't know right click "my computer" and look under system type. If everything looks right proceed. An installer will launch and guide you through install.
Menu Option 2 - Manual Install
If you want to manually install, an explorer window will launch allowing you to pick the NabiDriver32.exe or NabiDriver64.exe. In case it needs stating the NabiDriver32 is for 32bit OS, and NabiDriver64 is for 64bit.
Notes: The driver can be uninstalled by going into control panel and add/remove programs, select Nabi Driver and click uninstall. The digital certificate for Nabi lab is installed in Trusted Root Certification Authorities. Probably the easiest way to view is internet explorer. Go to tools->internet options->content->certificates. It can be removed from here should you feel it's a security risk. I don't think it installs properly on XP, so if you want to add it go to your program files folder->NabiLab->driver and find the NabiLab.cer, right click and select install. When you come to option of where to install manually select Trusted Root Certification Authorities.
MENU 2 - Root, Gapps, Recovery
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android and upgrading to 1.9.37. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps, and/or getting rid of the Android is Upgrading message. It is the immensely popular t499user Gapps with the 2 stray .odex removed. No sense in reinventing the wheel. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
Note: The layout of this is based on the original work by jmztaylor, modified for what we currently know about the Nabi and tweaked accordingly.
MENU 3 - Return Nabi to Stock Condition
The menu options will only be available if you have downloaded Nabi Lab full. If you have a stock unrooted backup you should try that first.
Menu Option 1 - Return Nabi to Stock 1.9.37. Android can boot.
This is useful if you just want to return your Nabi to stock for regular use, sale, or warranty(morals aside). This is the mode to use if you can boot Android. This operation will take some time to run, so let it. Upon completion TWRP is still installed, to entirely restore to stock you will need to install the stock recovery(see Menu 4). You have the option to put on external or internal storage. Although I don't think I compiled TWRP to use "in place" install, which would mean it still copies to internal. I'm not sure on this one, so internal is probably the best bet, but I have performed it on external and it works fine. You will need space on internal storage to do it.
Menu Option 2 - Return Nabi to Stock 1.9.37. Android not booting.
This is useful if you are in a situation that has left Android unbootable and you have no backup. Otherwise it's the same as Option 1. You will boot to TWRP and then perform the restore. Again TWRP will still be installed afterward, no be completely at stock you will have to remove it by Main Menu 4. I have it this way in the event you plan to immediately reroot it.
Notes: If you want to view this menu in the lite version, you need to open the file havefiles.txt, it is located in the stockimage folder. Change the line backup=false, to backup=true. You can then view the menu. You can then copy files you wanted to the stockimage folder and restore. Since the restore portion is manual I'm not sure why you would ever use it this way but if you want to play around that's how to enable it.
MENU 4 - Install Recoveries
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.9.37
Installs TWRP 2.3.3.0. This is the version that everyone should be trying to use first before trying other versions. This is the version that has symlinked paritions since it is thought currently their might be different partition structures for various Nabi's. Newer Nabi kernel and fixes touchscreen issues for some people that were using 2.2.2.1.
Menu Option 2 - Install TWRP 2.3.3.0 for Nabi Versions prior to 1.9.37
Use this option if Option 1 didn't work for you. Older Nabi kernel, otherwise same as Option 1.
Menu Option 3 - Install TWRP 2.2.2.1
This is the original TWRP from the first Nabi rooting thread. Use this if the other 2 don't suit you, or you just trust my compile skills, which may be prudent... :silly:
Menu Option 4 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Menu Option 5 - About Recovery Installer
A leftover from my initial recovery installer, I was too lazy to remove it.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 5 - Tablet Information
Nabi Information, serial, version, build date, device mode, internal/external size, detected backups.
Note: This only detects if a backup folder is present, not if there are backups actually inside the folder. The only way this would be the case is if you manually deleted them or just made a empty folder in there, so be aware. Also if you have made a ramdisk modifying init.rc, used creative symlinking to swap internal and external SD, or used a prebuilt app to swap this screen may be incorrect.
MENU 6 - Lockscreen Mod Tool
Don't use this if you have updated to v2.0.5, I haven't tested but the framework-res.apk was updated in the 2.0.5 update and if you are using the old one you could throw yourself in to a bootloop
Menu Option 1 - Install custom lockscreen
Use this to install a custom lockscreen. You will need a picture that is in .png format and is 1440 x 903. A explorer window will open up showing you the location to put the picture. The file MUST be name lockscreen.png, there is one there that is black, you can overwrite it be there MUST ALWAYS be a lockscreen.png file in that folder if you use the tool. Bad things could possibly happen if it doesn't. You have the option to manually install the lockscreen, or automatically install it after the zip is built. In either case it copies whatever you named the zip(you are prompted for a name) to the internal SD, along with a file called lockorig.zip. The lockorig.zip is there if you mess up and Android won't boot you can manually install the lockorig.zip in TWRP to put it back to stock.
Menu Option 2 - Install stock lockscreen
Use this to return to stock. Remember if you used Option 1 there will already be the stock lockorig.zip on your internal storage.
Notes: If you make a custom lockscreen, while it copies the installable zip to your device it also copies it to your picture folder so you can share with others. Make sure you visit in share your creation over in this thread.
MENU 7 - Patch NabiLab
Menu Option 1 - Install Patch
For any updates to Nabi Lab this is where you can automatically load them. Basically you will download NabiPatch.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Note: Since this option wasn't in NabiLab v1, we have to do some trickery when coming from version 1 to install, so the procedure is different, all subsequent patches will be the above method however. Coming from version 1 you will need to download NabiLabv2update.zip and extract it into the NabiLab directory such that RunOncePatch.bat is in same directory as NabiLab.bat, and the other file NabiPatch.zip is in the folder "patch", then run the RunOncePatch.bat If you extract into your NabiLab directory it won't be a problem, the hint you didn't do it right will be if the RunOncePatch.bat isn't right there with NabiLab.bat
Credits
jzmtaylor - Original Nabi root. Nabi device code from which to build newer TWRP
t499user - Gapps fix
Dees_Troy - TWRP build tutorial
Eric Karz - Lockscreen Modding, NabiLab scripting
1wayjonny - Universal Driver base code
TeamWin - They are the guys that make TWRP possible
In all honesty everyone that has participated in the main Gapps thread has indirectly made the program what it is from testing, to information, to troubleshooting and everything else Nabi.
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Sent from my EVO using xda app-developers app
DarkAngel said:
Hmmm just for giggles I installed Nabi Lab on my Computer to change the Lock Screen and it does not want to read my Tablet.
Click to expand...
Click to collapse
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
strive53 said:
Thanks for this! Driver install didn't work for me on any of my computers...well it did install a driver but didn't read my nabi. Uninstalled nabilab driver and used PDA.net and all was good. Nabilab worked great installing recovery root n gapps! Thanks agn.
Click to expand...
Click to collapse
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
aicjofs said:
So it's saying error Nabi not detected or no driver? Is the device seen in Device Manger? Really can be only 2 thing, adb conflict or device driver.
What operating systems and did you have any previous Android devices connected to the computer? Sometimes I noticed it will conflict with any previous driver installs, and not while installing the driver is successful it won't use it. I guess it doesnt matter if it's working for you with PDAnet. If you are on vista or later you can try running pnputil -e from command prompt and look through all the oemxx.inf's and see how many google,inc android drivers there are.
Click to expand...
Click to collapse
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
DarkAngel said:
Sorry should have been more specific. It detects it via Device Manager but not via Nabi Lab. I am running Windows 7 x64
Click to expand...
Click to collapse
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
aicjofs said:
Is it detecting 2 Nabi interfaces in Device Manager? I can see it's detecting the MTP interface, but what about the ADB interface. Usually ADB appears under Android Device and MTP under Portable Devices. Is there anything under "Other Devices"? NABI2-NV7A something or other? Only other thing I could think is that there is a hung up ADB process running, kill it in task manager or reboot.
Click to expand...
Click to collapse
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
strive53 said:
sorry knew i should have stated my operating system. my main computer is a macbook and i have a old xp laptop n xp netbook that i use for flashing. i also tried it on my moms win7 desktop and a friends win8 desktop without luck. never changed in device manager from NABI2-NV7A with yellow exclamation point. ive flashed a bunch of phones from my laptop and probably do have drivers installed from who knows what.. it did install the driver but nabi wasnt detected as adb interface. rebooted computers n nabi after installs. i didnt have any other device attached at the time.
Click to expand...
Click to collapse
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Yes it's detecting on both. The only thing that has been baffling me for some time is back when I had a Windows phone and after I switched to android, what appears to show in "Other" looks like my old TouchPro2. I can not delete that.
Click to expand...
Click to collapse
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
aicjofs said:
I had trouble with computers that has previous drivers installed sometimes, other times not. I tested fresh installs on XP 32, 7 32, 7 64, 8 64 and everything went fine, but it was much more hit and miss with computers that already had a slew of drivers. I'm more concerned that NONE of yours would work, although I guess it's offset by the fact that PDAnet driver worked and that NabiLab itself worked fine.
Well you have me baffled too! haha. If you run "adb devices" from cmd prompt what is the output? You have a modified cmd processor, that opens batch files? Seems like everything is in place. It case it's something with the program did you come from v1 NabiLab and patch or just v2?
f you want to play with the lockmod while we figure it out, the pic zip you made will still be in "pictures" folder, just let that portion of the program run until it errors when it tries to adb transfer. You can manually transfer to SD and flash TWRP.
Click to expand...
Click to collapse
This is the first time installing it actually since I Rooted and installed GApps through Ubuntu. I just wanted to try it so I can try and change the lockscreen image and update TWRP while I was there also. I downloaded v2 with the backup. I was going to try v1 to see if that made a difference or try the PDAnet driver.
Sent from my NABI2-NV7A using Tapatalk HD
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
kieronw3 said:
Worked fine as soon I realised I wasnt waiting for the files to transfer :banghead:
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I could add a line that says, go check the mail, run to 7-11, trim the dogs toe nails. Hehe. Glad it worked eventually. 58 or so downloads and not many complaints, I can live with that, better then a brickfest. :laugh:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Eric Karz said:
Nice job on lab update. Good use of the colors
i have a Request
could you add 'upgrade Twrp to the latest version'
maybe under Advanced User tool.
then if for some reason there is changes in the future you could just put the image file down load in that folder and update by click of a button ?
Click to expand...
Click to collapse
I need something for a version 3, so why not?
delio77 said:
Win 8 64bit... Never had other android drivers installed on this machine. I dont see it listed in device manager at all. But the machine definitely sees it in my computer, and I also see it go into debug mode on the tablet. Confused,,,
Click to expand...
Click to collapse
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
bradleyw801 said:
When I try to install recovery, root, gapps, I get stuck on waiting for device. My device detects just fine. I think it may be an issue with fastboot drivers, not ADB drivers? Because ADB reboots the device into fastboot just fine. But once it's there, it just sits on "waiting for device". Any thoughts?
Click to expand...
Click to collapse
Have you verified that your fastboot drivers are working? If you navigate to the folder where adb.exe and fastboot.exe are you can just iddues the command fastboot devices to see if the device is connected while in fastboot.
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
aicjofs said:
I need something for a version 3, so why not?
Are you using NabiLab or just the drivers I linked in another post? Is it detecting it in NabiLab? If it is the drivers have to be there under Android Device.
Click to expand...
Click to collapse
I am using NabiLab and it said not detected. I eventually got it to work with PDAnet
Ken Esq said:
1. How would you update a Nabi that has been originally rooted on .23 with jmz's work. I'd also like to clean up the optimizing android apps issue?
2. Would it be possible for you to add a "Clone Nabi" option to the Lab. Many people have more than one Nabi to tend to and it would be nice if you could duplicate the setup across multiple devices. I did it by hand for a dozen and let's just say it's a bit painful.
Mostly, though I wanted to thank you and all of the other developers for their work. There is a classroom full of 1st graders that use the Nabis everyday. They used to be stuck with nine-year-old Dell computers that would take 15 minutes just to boot...now things are easy and fun. You guys have really made my donation of the Nabis a great project. Thanks!
Click to expand...
Click to collapse
So is the device still on .23? Probably 3 ways to go about it if that's the case,
1) backup apps with something like Titanium backup, restore the original backup "stockunrooted" of Nabi, reinstall stock recovery, update to 1.9.37, reapply root and gapps, restore app backups, or
2) backup apps, restore a stock 1.9.37 from NabiLab, reapply root, gapps, restore app backup. or
3) you can try updating the safe OTA's people have posted, I came late to the game so I didn't study those, I know there is the wifi issue between kernel and modules if you don't do it right. If you already are on .37 but just rooted back on .23 the only thing to do is gapps to fix android upgrading. The optimizing android is fixed by flashing the fixed gapps.(Gapps only, option 2 then option 3 in NabiLab)
How would you like to see cloning? It just loops through the procedure and you just keep plugging Nabi? Or a restoring image to all of them. Help me visualize what you think would be best.
I'm not sure how you are doing it. How I would do it currenlty for Nabilab if I had 20 brand new Nabi's is like this. Once all Nabi's are at version you want (1.9.37)
Take one Nabi and do a recovery, root, gapps, backup(Option 2, Option 1)
Grab the backup it made and move it to computer.
Take remaining Nabi's
Install TWRP 2.3.3.0(Option 4, Option 1)
Install Root Only(Option 2, Option 4)
Install Gapps Only.(Option 2, Option 3)
What you accomplish here is making the backup only once. So first Nabi takes 15 min, the remaining maybe 3 min.
No thank you for popping in with some feedback.
New OEM Factory Release firmware for the Allwinner A10 LY-F1, A10 LY-F1HD A13 LY-FI
Hi all
Update - New jelly bean 4.1.1 released 20130319 (thanks TaitoUK)
The following two post have been updated as applicable.....
Warning–make sure you obtain your original supplies firmware image before you upgrade i.e. Just in case you have a clone with slightly hardware and you can go back if all goes wrong
If the image works in your device please post back make / model
For your info the company http://lyxfsz.com/en/index.htm
Download page for F1’s http://lyxfsz.com/en/downs.htm?sortid=0_22 Also other downloads F2’s etc
Summary of images of the above link today are:-
F1HD(A10)4.1.1 Updated firmware 20130319.2.0.6 (FY-F1HD i.e. screen 1024x600)
F1(A10)4.1.1 Updated firmware 20130319.2.0.6 (FY-F1)
F1HD-4.0.4 Updated firmware 20121129.1.1.1
F1(A13) 4.0.4 firmware 20121129.1.1.1
F1-2.3.4-20120312-0.9.1-a721
F1(A10)4.0.4 Updated firmware 20121129.1.1.1
How to install – you need LiveSuitePack_Version_1.09 – for a guide see this post
2.0.6 update
This ROM fixes (1) youtube issues.... lip sync is now in sync from the start... (2) battery stats now report info ... (3). a general bug up date..
Issues
Apps like Angry Birds are not displayed in the play market - "you device is not compatible with this version"
……………………………………………….
The above issue can be fixed (one line to added).....see post below
……………………………………………….
Also note that ClockworkMod does not seem to working correctly at this time, I will post back when this changes
I hope this helps R
The factory downloaded jellybean firmware, “F1HD(A10)4.1.1 Updated firmware20130319.2.0.6” and
“F1(A10)4.1.1 Updated firmware 20130319.2.0.6” has the following issues:
A. Firmware not rooted
B. Many apps missing from the market, like chrome, angry birds etc
C. AnTuTu Benchmark scores a very low mark compare to 4.0.4 (i.e. drops by 1000)
However all of the above is easily corrected by the following…
1. Install 4.1.1 firmware on your device using LiveSuitePack_Version_1.09 (i.e. see link above) reboot the unit.To fix A…..
2. For the LYF1-xx we have to correctly root the device using a slightly modified version of superoneclick from
www.manzanavirtual.com/tutorial-rootear-desrootear-tablet-prolink-peru-superoneclick.html
Install the drivers before you try superoneclick, as you can tell this is in spanish use a translator
Now restart the unit, the device will be correctly rooted, and supersuer app installed
It also has been reported that ZhuoDaShi works as well (unroot first... then root)
Update For the A13 LY-F9 see MW-Core post below http://forum.xda-developers.com/showpost.php?p=38531971&postcount=9
To fix B & C…..
3. From the market download ES file Explorer, in the setting menu go to root settings and make
sure all boxes are ticked. If superuser app pops up, select yes / allow.
4. Goto the root directory i.e. / then selected the system directory (/system) edit the file “build.prop” to
add the following line at the end of the file
ro.opengles.version=131072Yes only one line to add, Save File, exit ES file Explorer
5. In the tablets settings menu go to manage apps, find “Google Play Store” and “Google Play services”
and select clear dataReboot tablet
Know issues… none
If this helped post reply
R
It isn't the most important thing, but it would be nice if cifs.ko and md4.ko were available so that NFS exports could be mounted.
Best wishes,
Bob
PS Whoops. There is nothing lacking the ROM, but something a bit slow in me. The mount command needed an "nolock" option for it to work.
RLF
rickwebtest said:
The factory downloaded jellybean firmware, “F1HD(A10)4.1.1 Updated firmware 20130110.2.0.3” and
“F1(A10)4.1.1 Updated firmware 20130110.2.0.3” has the following issues:
A. Firmware not rooted
B. Many apps missing from the market, like chrome, angry birds etc
C. AnTuTu Benchmark scores a very low mark compare to 4.0.4 (i.e. drops by 1000)
D. YouTube stops when trying to play a video with the message…
"Unfortunately. Youtube has stopped"However all of the above is easily corrected by the following…
Note.. I can't post links as I have less than ten posts.... so remove spaces and post in browser
1. Install 4.1.1 firmware on your device using LiveSuitePack_Version_1.09 (i.e. see link above) reboot the unit.To fix A…..
2. Now we have to correctly root the device using a slightly modified version of superoneclick from
www .manzanavirtual.com/tutorial-rootear-desrootear-tablet-prolink-peru-superoneclick.html
Install the drivers before you try superoneclick, as you can tell this is in spanish use a translator
Now restart the unit, the device will be correctly rooted, and supersuer app installed
It also has been reported that ZhuoDaShi works as well (unroot first... then root)
To fix B & C…..
3. From the market download ES file Explorer, in the setting menu go to root settings and make
sure all boxes are ticked. If superuser app pops up, select yes / allow.
4. Goto the root directory i.e. / then selected the system directory (/system) edit the file “build.prop” to
add the following line at the end of the file
ro.opengles.version=131072Yes only one line to add, Save File, exit ES file Explorer
5. In the tablets settings menu go to manage apps, find “Google Play Store” and “Google Play services”
and select clear dataReboot tablet
To fix D…..
6. The latest version of youtube does not work, the previous version works YouTube_4_1_47.apk i.e. from here
www .androiddrawer.com/7215/download-youtube-4-1-47-app-apk/#.UP2jVfL7HxU
Know issues… youtube app…. when a video starts the lip sync may be out, select pause, then play and its back in sync
ClockworkMod does not work at this time, I will post back when this changes
If this helped post reply
R
Click to expand...
Click to collapse
i have an A13 LY-F9 UPDATE TO 4.1.1 JB . HOW CAN I ROOT ?
JB 4.1
JUNEBUG-1 said:
i have an A13 LY-F9 UPDATE TO 4.1.1 JB . HOW CAN I ROOT ?
Click to expand...
Click to collapse
I flashed the manufacturers latest JB rom and used 'superoneclick' prog to root, worked ok on my versus 7" LY-F1
Hi OP, any news on CWM recovery?
Updated the first two posts.... The latest update of the youtube app, February 22, 2013 now works
killall said:
Hi OP, any news on CWM recovery?
Click to expand...
Click to collapse
I believe flowish who ported CWM for Allwinner A10 LY-F1/TREQ Tablets has exams at the moment
thanks man worked a treat on my cnmtouchpad/ly-f1
JUNEBUG-1 said:
i have an A13 LY-F9 UPDATE TO 4.1.1 JB . HOW CAN I ROOT ?
Click to expand...
Click to collapse
Hi mate..
i have the same tablet as you... and i have succesfully manage LY-F9 4.1.1, how to install, Root, Edit and give a little tweak on build.prop.. I have unsucces with SOC method... but finally found a very Good Tool from HcH.. Uberizer 1.4 and its work perfectly...
If you want to try just follow link on my Local post, it's Indonesian, maybe you need Google Translate..
Find the Tutorial Here ..h*ttp://w*ww.kas*kus.co.id/show_post/512ae71beb74b4746b000008/463/tutorial-install-root-edit-dpi-pada-ly-f9-jellybean-411-utk-pp9-gie (delete the * on link)
MW-Core, thanks for the info, I've added this to the instructions
rickwebtest said:
MW-Core, thanks for the info, I've added this to the instructions
Click to expand...
Click to collapse
Sure... hope it will help..
sorry about the link, my post less than 10, can't give outside link..
Invalid IMG File
IMAGE FILE INValid..
huhu
it takes my 3 days life to flash my tab but unfortunately i haven't got a single luck.
i tried it from 5 different computer(win8 and winXp) and it never detects my tab..;
when i tried it from my computer(Windows 8). my device detect but invalid image file.. i already downloaded the different kind of images from the site you given but non of it are working on me ;(
yesssshh thank you so mcuh..finnaly i found the firmware http://lyxfsz.com/en/downs_view.htm?id=89
for this tablet that im fixing..is this posible to root?
Newer JellyBean release for LY-F1HD (F1HD-4.1.1-20130319.2.0.6-A721_V4.2.img)
TaitoUK said:
Newer JellyBean release for LY-F1HD (F1HD-4.1.1-20130319.2.0.6-A721_V4.2.img)
Click to expand...
Click to collapse
Cheers - updated the first two posts
rickwebtest said:
Cheers - updated the first two posts
Click to expand...
Click to collapse
Thanks (fellow HUKD'er) :good:
Friends, I have a10 LY-F8AS tablet with android 4.0.4 .how can i root it ???
and also how to install CWM ??????
hariraj96 said:
Friends, I have a10 LY-F8AS tablet with android 4.0.4 .how can i root it ???
and also how to install CWM ??????
Click to expand...
Click to collapse
just flash the latest custom 4.1 stock-based firmware, it will be rooted and will have cwm installed.. actually TWRP recovery with touch enabled..
links for download are on the other forum topic, look here
http://pandawillforum.com:8081/show...2-0-6_Seby-for-LY-F1-Alldro-Speed-E200-Update
it will work great on your LY-F8..
aldinezi said:
just flash the latest custom 4.1 stock-based firmware, it will be rooted and will have cwm installed.. actually TWRP recovery with touch enabled..
links for download are on the other forum topic, look here
http://pandawillforum.com:8081/show...2-0-6_Seby-for-LY-F1-Alldro-Speed-E200-Update
it will work great on your LY-F8..
Click to expand...
Click to collapse
can u give me the link to twrp ???
my tablet is LY-F8AS NOT LY-F8S.
THE DIFFERENCE IS THE FORMER HAS DUAL CAMERAS...
hariraj96 said:
can u give me the link to twrp ???
my tablet is LY-F8AS NOT LY-F8S.
THE DIFFERENCE IS THE FORMER HAS DUAL CAMERAS...
Click to expand...
Click to collapse
you don't need twrp, you just need to download the IMG file and flash it with livesuit.. you will find more info on the topic i provided above. good luck
Hello Everyone
I am starting this thread as a COMPLETE GUIDE FOR YOUR DEVICE which would include almost all aspects for your device.
BASIC ANDROID DEVELOPMENT
REFER TO THIS GUIDE FOR BASIC ANDROID KNOWLEDGE AND DEVELOPMENT PROCESS
ALL ROMS,GUIDES, MODS, TUTORIALS LIST CLICK
ALL ROMS,GUIDES, MODS, TUTORIALS LIST
TABLE OF CONTENTS
1. UNLOCK BOATLOADER
2. ROOT YOUR DEVICE
3. FLASHING TOOLS AND GUIDE
4. DRIVER ISSUES
5. MEMORY PROBLEMS
6. TA BACKUP
7. OFFICIALLY UNLOCK YOUR BOOTLOADER (Not available now)
8. FAQ
9. GUIDES LIST
All Credits to the developers for their tools!
HTML:
I take no responsibility for world wars, broken phones, flying machines,
UFO invasions, bricked phones, dead sd card . If you agree to go ahead with this,
it is your choice and no blame should come to any developer/contributor whatsoever
PREREQUISITE
-USB DEBUGGING
For this guide to work, make sure usb debugging is enabled.
Go to Settings> About>Build Number> tap it 7 times and "Developer Options" should appear in settings.
In Developer Options> Enable USB Debugging.
-USB DRIVERS
For these I suggest use Flashtool. Check Drivers guide below for more information
REFER FAQ
New Method to Root M4 Aqua Dual E2363 *26.1.B.1.85 Found on Locked Bootloader. Please click on new method under Root How to root 5.0 Lollipop with RootkitXperia AND CHECK HIS TWITTER FOR UPDATES
STEP BY STEP NOOB GUIDE FOR TWRP AND ROOTING
BOATLOADER
YOU CAN UNOFFICIALLY UNLOCK YOUR BOOTLOADER HERE
You first need to unlock your bootloader before you can root your device.
@lucaszell for the amazing guide. @Sam205 for pointing it out in M4 Aqua forum
1. Go to Sony Website HERE
2. Choose M2 or M and complete the steps to get your KEY
3. Install Flashtool
4. Go to Settings - About phone - Status
Scroll to down to see serial number. (device name)
Amended for clarifications
1.: Go to the folder where Flashtool is installed. Usually C:/Flashtool
2.: Open the folder named "Custom"
3.: Open the folder named "Mydevices" (if it exists, in my case Flashtool version 0.9.18.4) (You may create if it doesnot)
3b.: In the newer Flashtool, you need to put the folder in "C:\Users\<username>\.flashTool\registeredDevices" in step 3.
That is, if you've picked the default for your flashtool home folder or you can choose manually.
4.: Create A New Folder and Rename the folder with your device code. Refer to Obs2 how to find your device code
5.: Open the folder created previously
6.: Create a new text file and rename it as ulcode
7.: Paste your unlock code and save it in the text file
8.: Open Flashtools and try the BLU option again.
Obs 1: the step #3 I think it depends on your Flashtool version, because it wasn't mentioned at the solution
Obs 2: at the step #4 is mentioned your device code. your device code is showed in the log when you click the button BLU, at the "Current device", after your device model.
Search a line like:
09/045/2015 23:45:08 - INFO - Current device : C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17
in this case, the device code is AB100C2DE3 and this should be the new folder name (step 4)
ROOT
NEW METHOD by @cubeundcube for locked bootloaders
OLDER METHOD
@husam666 Successfully found how to root the device. Please refer HERE
WORKING ON DEVICE MODELS
[E2303, E2353, E2333, E2306]
husam666 said:
TWRP Recovery for M4 Aqua (No gui, command line only)
This is for E2303 I didn't test on other models, feel free to do so but I take no responsibility whatsoever if anything happens
This will disable OTA updates, if you want them back you can flash the FOTA kernel with FlashTool
Confrmed to be working on those variants:
E2303, E2306, E2333, E2353, E2363
Ok here it is thanks to @jeffreyvh kernel we can finally flash zips however we have 3 catches:
1. No GUI (Sony's fault until they provide full sources for our phones, we're stuck here)
2. You have to mount /system, /data and /cache manually (Working on it)
3. No external SD card support (working on it)
No problem? Cool..
Ok here's how to do it:
0. You need unlocked bootloader <-- Click here to see how
1. Download the recovery.img
2. Flash the recovery file with fastboot
Code:
fastboot flash recovery recovery.img
3. Pull the cable turning off your phone.
4. Press the power button + volume down, when the phone vibrates, press the volume down button repetedly.
5. The Sony logo will disappear and you'll get a black screen (It's okay, congrats you've now booted twrp)
Now for the magic:
Connect your cable, make sure you have ADB and drivers installed.
In your terminal or dos window type:
Code:
adb shell
you'll get a prompt like ~ #
type these three commands:
Code:
mount -w /dev/block/platform/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/7824900.sdhci/by-name/cache /cache
Now that you have the partition mounted you can flash your zip files:
We don't have external SD card support so for now we're going to stick with sideload
type:
Code:
twrp sideload
adb shell will exit, it's okay now we can install the zip file like this:
Code:
adb sideload <path_to_zip>
path to zip on your computer without the < >
so if you downloaded superSU on C:\Downloads\SuperSU.zip
you type
Code:
adb sideload C:\Downloads\SuperSU.zip
when you're done type:
Code:
adb reboot
and pull the cable
For Rooting:
Download SuperSU flashable zip from here https://download.chainfire.eu/696/SuperSU
and flash it like explained before
good luck
Special Thanks:
@jeffreyvh
@alby_var
@Hnk1
@zw3n
@S7relok
@dexter93
@babydolll @Sam205
The TWRP team and everyone who made this possible
Download Links:
http://d-h.st/wuGD
XDA:DevDB Information
M4 Aqua TWRP, Tool/Utility for the Sony Xperia M4 Aqua
Contributors
husam666
Version Information
Status: Testing
Created 2015-09-11
Last Updated 2015-09-17
Click to expand...
Click to collapse
Last Updated 22-2-2016
SONY OFFICIAL TOOLS
Sony PC Companion
This tool is officially from Sony and can be used to repair your drive.
You can also use this for your phone backup.
http://support.sonymobile.com/global-en/tools/pc-companion/
It is for those who do not prefer unofficial ways!
EMMA
Refer to it here for instructions and download:
http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
FLASHTOOL
This tool is used to flash stock/custom kernels/recoveries to your device
Download link
http://www.flashtool.net/downloads.php
Instructions
I found this guide very helpful and thus you can refer it here :
http://forum.xda-developers.com/showthread.php?t=928343
SOME CONSIDERATIONS :
1.Make sure you choose the FTF file for your device or you can risk bricking your phone forever.
At the moment, there are no FTF files so you will need to be patient.
2. Make sure all drivers are properly installed
3. To boot into flashmode/fastboot, you will need to turn off device.Hold volume up OR volume down and then connect your device while holding the volume key.
Volume up would take you to flashmode while volume down would take you to fastboot mode. Remember, you will need fastboot/flashtool drivers before you can flash anything.
here is another guide for you just as reference.
http://forum.xda-developers.com/xperia-l/general/xperia-l-how-to-flash-tool-unlocking-t2337955
However if you have still issues , I can rewrite the guide.
ALL DRIVER PROBLEMS SOLUTIONS
I have seen some posts where users are having difficulty connecting Xperia M4 to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
UPDATE (EASIEST METHOD) :
Use flashtool drivers to install adb/fastboot/flashboot drivers. This is the most simplest and easiest method I have come across lately.
Simply download flashtool
http://www.flashtool.net/index.php
Go to folder where you have downloaded it. Usually C:/flashtool/drivers.
Select the drivers for your particular device. I use universal for all three types of drivers. It is helpful to boot into fastboot/Flashtool before installing the drivers but not necessarily.
FOR LINUX DRIVERS :
(No drivers required)
In your Xperia go to :
Settings > Xperia > usb connectivity > usb connection mode
Select Mass storage mode (MSC) > Press OK
Then plug your phone with your SDCARD inside
Try this guide if that does not work,LINUX DRIVERS GUIDE
Good Luck
Still problem ? Quote me back
IMPORTANT
On windows 8 and above you will need to disable DRIVER VERIFICATION in your windows settings to successfully install your drivers
Memory, Storage and Debloating Problems
INSTRUCTIONS
LIST
SD MAID
ADVANCED TASK KILLER
TITANIUMBACKUP
GREENIFY
HOW TO KEEP RAM CLEAN AND KEEP YOUR PHONE BUTTER SMOOTH :
The phone MUST be fully rooted and all the recommended applications isntalled. They can be easily found on the Google Play. Links are provided for reference. In this guide I have used all the PRO (paid) applications. The Free versions will do fine but It is expected that some options are disabled in the free version. You can help developers by your contribution to their work
ADVANCED TASK KILLER
Advanced task manager is used to kill tasks running in the background.
Add advanced task killer widget to your home screen. Every time you need to kill background applications, just tap it once. This way all the applications in the background are periodically killed and thus, more RAM is available to your system and thus increased performance.
GREENIFY[ROOT]:
This application/system basically looks for applications running in the background. These background processes might slow down system. Furthermore, these increase the battery usage and reduce battery time. Greenify detects the background applications and hibernates them. This not only speeds up the phone but also saves battery.
SICK OF BLOATWARE?
TITANIUM BACKUP [ROOT]
Titanium backup is used for backing up your applications and system files. This can also DELETE applications from your ROM permenantly.
I recommend you make a backup with Titanium backup before uninstalling the files. REMEMBER, IF YOU UNINSTALL A SYSTEM FILE, YOU WILL NEED TO REFLASH YOUR ROM and you will end up in BOOTLOOP.
I will paste a screenshot to tell you which applications can be deleted easily.
OTHER SETTINGS :
Go to your settings>developers tools> background limit> use as less as you want. THIS WILL INCREASE USER EXPERIENCE
HOW TO SWAP EXTERNAL MEMORY & INSTALL AS MANY GAMELOFT GAMES AS YOU WANT
Many of you are having problems installing many games in your internal memory and can only utilise 4 gb of your memory. This means only 3 gameloft games. Thus I will briefly help you with memory issues related to Xperia M4
This one is very easy. Install Folder Mount and it will do the rest. Remember with free version, you can only mount 3 folders. The application is frequently updated and it has great support for Xperia M4.
Basically this application creates a link folder in your SD card which is detected by games automatically once fully setup. It also moves your files into your SD card and this saves your EXTERNAL MEMORY FULLY. You can install as many games or applications and link them to your SD card. Its that simple.
Use App analyzer option to mount folders. Manual folder mounts are not recommended!
Go to app analyzer>Select Game> Creat pair(s)>Move files as well> Mounted
Make sure Folder Mount is ticked green before running games.
INTERNAL MEMORY PROBLEMS
Internal memory not adding up? Unknown files hogging your space.
This can be managed by SD MAID and TITANIUM BACKUP.
With SD Maid, you can free a lot of space. It has many cool features. I use the Corpse finder and System cleaner, App Cleaner.
You may also try app cleaner if you like.
Go to CORPSE FINDER>FIND FILES>DELETE ALL FILES. It will take some time looking for files.
SYSTEMCLEANER>FIND FILES>DELETE ALL FILES. It will take some time looking for files.
TITANIUM BACKUP IS USED TO RELOCATE THE MEMORY THAT IS MISSING.
Titanium backup> MENU > clean up the dalvik cache
This will also give you back some INTERNAL MEMORY BACK.
LIST OF APPS SUCCESSFULLY REMOVED WITHOUT ANY PROBLEMS
Active Clip
Calculator (small app version)
Email
Movie Creator
OfficeSuite
PlayStation Video
Sketch
Small App Framework
Small App Launcher
Small App Widget
Small Apps Manager
Smart Connect
Support
Timer (small apps version)
Touch Block
What's New
Music
Music Visualization Wallpapers
Podcast
Video
Visualiser (has same icon as Sony's Music in Titanium Backup)
Refer Screenshots
{
"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"
}
HOW TO MAKE A TA PARTITION BACKUP.
1. Download the latest version of Backup TA from here DOWNLOAD HERE
2. Extract the ZIP file to a folder location of your choosing.
3. Navigate to the folder location of Backup TA.
4. Make sure no other script or application which is using ADB is running.
5. Make sure the device is booted in normal mode (the way you normally use it).
6. Run Backup-TA.bat
7. Read the last paragraph of the license before continuing.
8. Read the information and follow the instructions given by the tool.
Someone pointed out that the script needs root to work.
UNLOCK bootloader from Official Website[ Sony doesnot support unlock bootloader of this device yet
However, Once supported, the following method MUST work!
OFFICIAL SONY WEBSITE TO UNLOCK BOOTLOADER
Please note! It will only be possible to unlock the boot loader for certain releases of this model. You can check if it is possible to unlock the boot loader of your device by checking the service menu.
Open the Contacts app.
Click the menu button in the top right.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above soft key bar, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Enter *#*#7378423#*#* in the dialler.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked(bootloader).
If your bootloader can be unlocked, proceed to the above website and follow the on screen instructions. You do not need to download full adb , just download the platform tools attached with this guide.
FOR MY REFERENCE. IGNORE
Just for my reference. Ignore it
These do not work.
Refer to first post for prerequisites.
ROOT CONFIRMATION
It was false root confirmation. You are more than welcome to try to find which method works for you from the following.
I have few confirmations of root working on Xperia M4 using this tool. Ignore what it says about kitkat or anything. Just make sure you got USB debugging enabled and drivers installed.
http://rootgenius.com/
Other methods that might work.
METHOD 1 (Kitkat/Lollipop. Unlocked/Locked Bootloaders)
This method has been implemented many a times by me and it has yeilded high results on different devices I have worked on.
We will replace the KingUser (chinese app like SuperSu) with SuperSU so you do not need to worry. You can also factory reset in order to be completely certain that no extra scripts are left in your system if you have any doubts about privacy.
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user. Maybe you be successful with full root. Check Root Checker.
METHOD 2
It is also a chinese method and it also has been used by me for few devices. Many people have problems trusting it, but it installs superSU so I think I would not be concerned much. Feel free to try
1.Install KingoRoot
http://www.kingoapp.com/
2. Run the script and see if it helps. Wait about 15 minutes .
METHOD 3
1.After running iRoot for explort, run KingoRoot. Wait about 5-15 minutes as it would go on forever if it is not successful in rooting your device.
2.Close afterwards.
3. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser.
The trick here is the moment, System is being restarted (device), Kingoroot pushes some scripts and together they are a deadly combination.
To GET SUPERSU if you got any other app instead for ROOT
1.Install supersu from market.
2.Update binaries
3.Restart.
Does not work ?
Use Beta SuperSU instead versions 2.48/2.49.
Install apk and try updating binaries.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
METHOD 4
1.Download towelroot apk.
2.Install and run
Check FAQ
https://towelroot.com/
METHOD 5
SUPERONECLICK ROOT
Check FAQ
http://forum.xda-developers.com/showthread.php?t=803682
METHOD 6
Try the z4root app
Check FAQ
Download here
http://z4root.en.uptodown.com/android/download
METHOD 7
http://www.oneclickroot.com/
Install the programme on the PC and run on screen instructions.
METHOD 8
Download Motochopper and try it
http://forum.xda-developers.com/attachment.php?attachmentid=2004316&d=1369929448
You will need to update SuperSU in these cases as well
METHOD 9
Use DoomLord Tool Kit.
Enable USB debugging and run the script. Start with the latest script v17 and carry on with older version scripts. You may need to update SuperSU/Superuser file to latest 2.49 Beta. Link in FAQ
PLEASE DO NOT MIRROR MY FILES!
NEW:
DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit.zip
OLD:
DooMLoRD_Easy-Rooting-Toolkit_v16_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v15_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v14_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v13_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v12_perf-event-exploit.zip
DooMLoRD_Easy-Rooting-Toolkit_v11_perf-event-exploit.zip
FAQ
In some scripts, you might find outdated version of SuperSU and it would not work unless you change the file with the latest SuperSU. Make sure you keep the name of the zip same, for example if the folder contains update, rename superSU 2.48 or 2.49 or2.47 or 2.46 to update as well. If it contains superSU, rename it to SuperSU.zip from supersu beta 2.49Beta etc.
You can find the superSU zip here :
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
Guides List
This would contain all the guides for your device. I have added the basic problems already but I hope more users contribute to this thread
ROOTING
ROOT/TWRP
ROOT ALL MODELS
[TUT] BLU, TWRP , ROOT Xperia M4 Aqua [complete step]
ROMS & DEVELOPMENT
Unofficial CyanogenMod 12.1 by ProjectMarshmallow
[BL LOCKED][ROOT]TWRP Touch Recovery for BL locked M4 Aqua
ANDROID OPEN SOURCE G-OS PROJECT
5.0
[RECOVERY] TWRP Touch Recovery for Sony M4 Aqua
[ROM][Flashable ZIP] STOCK FLASHABLE 26.1.A.2.167
[ROM][E2303]Debloated ROM[v0.0.3]
[5.1.1_r26] [UBL] Temasek's Unofficial Build
Aosp 6.0 - e2303 / e2306
[5.0.2] [WIP] AOSP for E2303 [By: Beta Team]
[5.1.1][E2303] AOSP by Beta Team [WIP]
[ROM] De-Bloated Stock 5.0 (E2303) LITE VERSION
[RECOVERY] Cyanogen Recovery Touch for Sony M4 Aqua
[STOCK][5.0] Xperia M4 Deodex
REPAIR /BRICKED/RETURN TO STOCK
MEMORY GUIDES
DRIVER GUIDES
OTHERS
Fix Camera Stock Retrieving after installing Xposed
[ROOT] Change CPU temp. limits ("Manage" overheating) (Updated 10/11/15)
[xposed] how to install xposed on rooted m4 aqua
MODS
SOUND MOD STEREO SPEAKERS - V3
BOOT ANIMATION CHANGER
[MOD][5.0][M4 Aq][PORT]TeleService: CallRecorder + Disabled Notification Data Traffic
xperia music mod black dark theme by iandroidx
[THEME][TWRP] DARK TWRP beta by alby_var
Ad Blocking without Root
Please quote me if I have missed any important guide and you think it deserves to be here.
SUGGESTIONS ?
Kindly give your suggestions and your feedback
CONTRIBUTIONS AND MY HEARTY THANKS TO
@husam666 for the first person to root the device and make a working recovery via adb commands @lucaszell for the guidance how to obtain ulcode. @Sam205 for pointing it out in M4 Aqua forum
XperiaRootKit developed by cubeundcube and pointed in the thread by @AndroPlus
@TheShadow523 for his support and providing screenshots of apps list.
IF A MISSED SOMEONE, PLEASE PM ME AND I BE HAPPY TO ADD YOUR NAME
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
MetalOllie said:
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
Click to expand...
Click to collapse
i tried almost everything... but no method is working for me... if one works i let you know^^
I don't see a prerooted ftf working either, until there is a recovery method for the phone. As far as I know, only a true stock ftf can be flashed using flashtools.
M4Aqua said:
i tried almost everything... but no method is working for me... if one works i let you know^^
Click to expand...
Click to collapse
I will update the SuperSU so it might be helpful. Will update you when I am done with the guides
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
MetalOllie said:
Kingo root doesn't work, and there are security concerns about iRoot/vRoot. I wouldn't recommend either. Towelroot doesn't work on any Lollipop device to the best of my knowledge. SuperOneClick and Z4Root are both for Gingerbread devices, so neither of those are even worth trying.
Click to expand...
Click to collapse
M4Aqua said:
i tried almost everything... but no method is working for me... if one works i let you know^^
Click to expand...
Click to collapse
Desakato said:
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
Click to expand...
Click to collapse
The guide has been completed. It is upto you to try and find an exploit. At the moment, this is your best bet and I have used many methods for recent devices on Lollipop to root my devices and these tools have been successful. At times, you only need to update SuperSU in the script usually. Give them a try and post your valuable feedback.
I hope you are all aware of USB debugging needs to turned on and you have all the latest drivers installed!
If any script can not find your device, it means either USB debugging is turned off or you do not have drivers installed
Hnk1 said:
The guide has been completed. It is upto you to try and find an exploit. At the moment, this is your best bet and I have used many methods for recent devices on Lollipop to root my devices and these tools have been successful. At times, you only need to update SuperSU in the script usually. Give them a try and post your valuable feedback.
I hope you are all aware of USB debugging needs to turned on and you have all the latest drivers installed!
If any script can not find your device, it means either USB debugging is turned off or you do not have drivers installed
Click to expand...
Click to collapse
I know USB debugging has to be enabled. Updating or installing SuperSu is only useful once the device has been rooted. Unfortunately none of the methods posted are capable of doing so. If you post a guide to rooting, it shouldn't be up to me to find the solution; respectfully, it rather defeats the object of "a guide". Some of the methods proposed haven't worked since Gingerbread. Which script are you referring to, and how does one update it to include SuperSu?
MetalOllie said:
I know USB debugging has to be enabled. Updating or installing SuperSu is only useful once the device has been rooted. Unfortunately none of the methods posted are capable of doing so. If you post a guide to rooting, it shouldn't be up to me to find the solution; respectfully, it rather defeats the object of "a guide". Some of the methods proposed haven't worked since Gingerbread. Which script are you referring to, and how does one update it to include SuperSu?
Click to expand...
Click to collapse
I understand your point mate. No offense!
The problem is that I do not own this device, if I had this device or you can provide me an FTF file, maybe I can work something out. For now, you can try these methods. I have successfully rooted LG devices/ Xperia and even samsung using the above 8 methods.
For your other questions, look at this. Also, Sometimes when i was trying to root my device , supersu 2.46 was not able to root it with the same script yet when i replaced it with 2.447 beta. It did
http://forum.xda-developers.com/showpost.php?p=61228366&postcount=6
Hnk1 said:
I understand your point mate. No offense!
The problem is that I do not own this device, if I had this device or you can provide me an FTF file, maybe I can work something out. For now, you can try these methods. I have successfully rooted LG devices/ Xperia and even samsung using the above 8 methods.
For your other questions, look at this. Also, Sometimes when i was trying to root my device , supersu 2.46 was not able to root it with the same script yet when i replaced it with 2.447 beta. It did
http://forum.xda-developers.com/showpost.php?p=61228366&postcount=6
Click to expand...
Click to collapse
FTF files: http://www.xperiablog.net/forum/resources/categories/xperia-m4-aqua.78/
banciii said:
FTF files: http://www.xperiablog.net/forum/resources/categories/xperia-m4-aqua.78/
Click to expand...
Click to collapse
Desakato said:
Very nice work sir, Appreciate it very much.
As I said on other thread, I cant wait for my device to be rooted and get all the blootware away
When any method works, I'll post my feedback right here!
Click to expand...
Click to collapse
MetalOllie said:
I don't see a prerooted ftf working either, until there is a recovery method for the phone. As far as I know, only a true stock ftf can be flashed using flashtools.
Click to expand...
Click to collapse
I have few root confirmations. Check root post for details!
Hnk1 said:
I have few root confirmations. Check root post for details!
Click to expand...
Click to collapse
im at the moment trying to root the phone with geniusroot....
when its finished i give u a response
EDIT: Geniusroot is not working.... still without root^^
M4Aqua said:
im at the moment trying to root the phone with geniusroot....
when its finished i give u a response
EDIT: Geniusroot is not working.... still without root^^
Click to expand...
Click to collapse
Can you post screenshots and you have proper drivers and usb debugging on ?
Have you tried any other method from my guide ? I think first 3 ones should work!
Please provide your feedback
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
dummyaccount said:
Someone posted a tutorial on YouTube, the title of video is "MIBOX 3 MDZ-16-aa ROOT + Install Android TV English".
@[email protected], did you get Netflix to work on it?
Click to expand...
Click to collapse
I tried all the steps.
No google play videos, no voice search and most of all no netflix.
=(
I hate the ****ing Chinese that sold me MDZ-16-aa saying it was the international version.
dont work password androidtv rom....... is Mibox2015?
mdz 16-AA
I faced the same issue.Wrong password.
Thanx for your post [email protected] I am going to use this method for my Mi box3.
As I am going to root any device for the first time, what precautions should I take
that I don't brick it?
Does the Microphone and and Ok button on Remote work normally after rooting by your method ?
Thx in advance....
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I tried to downgrade my MDZ-16-AA device with the MiBOX3_jurassicpark_gitv_1.3.106.386 file ... but it brings it down only to 1. 3. 114 and not to 1. 3. 106.
Secondly I do not get "ADB Debugging" option. Hence I cannot connect my Mi Box to my laptop.
Can anyone help ?
the correct password is : '@'mibox2015
the quotes are only to avoid mention to xda user "mibo" in xda forum...u don't have to write it in...
mibox v1.5.1
I've troubles to root my mibox, I've the 1.5.1 version.
Can you help me, please ?
Mi box 3C v 1.5.1
Can it possible to do the same for version 1.5.1?
I have Mi box 3C v 1.5.1 and I can't even boot into recovery yet.
Add widevine drm in MDZ-16-AA
To complete your notice, I found a way to launch MyCanal and molotov.tv (not tested for netflix yet).
As you know these apps requires widevine drm.
First download
extractor 4.0 and Xiomi 3S official rom
Then extract update.zip and add in root folder of extractor: system.new.dat + system.transfert.list.file_context
Use Extractor.bat to uncompact system.new
On folder go on system\vendor and copy paste lib folder on USB key.
Does anybody know how to go to recovery mode?
HOLD Back + OK and Home + Option doesn't work for my MDZ-16-AA
the system has been automatically updated yesterday.. :crying:
Thank you so much, I got it installed.
Step 1 can be hard because of the chinese language therefor I used this link:
https://www dot cnx-software dot com/2016/04/12/how-to-change-language-to-english-and-install-apps-remotely-on-xiaomi-mi-box-3-enhanced/
at step 2 I made the mistake that I extracted the update.zip aswell. while I needed to keep it zipped.
I used the app RUFUS to make the usbdrive a FAT32 drive.
at step 3 Kingoroot worked for me, although I needed to restart several times to make the ADB debugging connection work.
at step 4 sending the TWRP files, was a bit of a hurdle. It wwas not possible for me to copt them from the USB stick with ES file manager to the device. I needed to use the USB cable to my computer (ADB off) password: "@mibox2015"
At point 5 I was not able to use my remote or keyboard, I needed to turn off ADB!
At the end allot works, but there is still some bugs:
- MIUI still present. eg. when connecting an usb stick you get a chinese menu. and you are able to get into the old system menu
- unable to get NETFLIX to work
- allot of bloatware, apps I can not disable or delete.
- im unable to disable search by microphone in the UI, which is not supported by the remote of the 16-AA
- im unable to edit the tiles in the homescreen to eg. hide the supersu, market etc. and to put PLEX of KODI more in front
Thanks!!!!
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
weiabroad said:
I have rooted my mibox 3c and installed TWRP app
I copied img to device and flash drive, but I can't choose any img in TWRP app...
any method to replace custom recovery?? THX
Click to expand...
Click to collapse
Go through each step carefully, if stuck be clear about what you have done
Sent from my A0001 using Tapatalk
Arquivo converter ROM chinesa para global 3C-16AA
Olá, gostaria dos arquivos para converter a ROM 3C-16AA, você tem whats para contato?
Hey,
Im' trying to get mycanal to work on my mibox MDZ-16-AA.
I copied the lib folder on my usb stick.
it's still not working, isn't any steps missing ?
Thanks.
Secure Check failed error while downgrading
I Got "secure check failed." error while downgrading. What did i do wrong ?
[email protected] said:
Hi everyone, I recently bought a Xiaomi Mi box3c and was very disappointed with custom rom and the interface that it came with on it. So surfing the web there are a few tutorials on how to change it and I tried a few but they are not that great either, till finally someone patched the stock android TV Lean back Launcher for it, it took some tinkering but I got it working, this may not be the best way but this is how I did it form the start. This is not my work, I just followed instructions and I have gathered them here. As I am lazy Im not gonna provide pictures for every step but it’s pretty straight forward.
For using some the apps during the process you will need usb mouse cause not every apps supports Mibox remote configuration
As I am a new poster I am not allowed to post any links so change every dot word to an actual . for the links.
1. Turning on the Box and Changing to English
1.1 Download this apk provided by Xiaomi veterans on forum, it’s a shortcut to the stock android setting
drive dot google dot com/open?id=0B16bkj0QSkYnc0k2UUFTU05vSHM 1.2 copy the apk to a normal usb flash drive and connect to mibox and install the apk
1.3 Run it and now you can change the language as in any android device.
2. Downgrading Firmware
All of the root options available for this device are for the older firmware so you need to downgrade the device. (it’s much easier than it sounds.)
2.1 Download the original firmware for MDZ-16-AA from this link: (both are the same thing)
yadi dot sk/d/Yvr1jYflm6GZR androidfilehost dot com/?fid=745425885120695554 2.2 Extract the contents of the downloaded zip file to a formatted usb tick (Fat32). (There should be two files: xiaomi_update and update.zip)
2.3 Put the USB flash drive in your Mi Box and boot in recovery
(How to boot into recovery: Unplug power > press and "hold back + ok" button while plugging the power back in. The remote should be nearby and facing the box. Do not let go of the buttons until it booted in recovery. for some devices its "home + menu" button instead of the previous one.
2.4 the flashing should start and finish automatically. don’t connect the device to WIFI after this step until you have disabled the intelligent update.
(Credits to passerby on xiaomi.eu forums for the guide)
3. Rooting the device
I tried almost all of the rooting apps, none of them worked for me but I have seen people insisting that permroot works for them so I put the link for that, using it is pretty straight forward, download, install on device and try to root with it.
but in case that doesn’t work Kingoroot Windows app will definitely work. this is how to root with kingoroot. For this method you need a USB type A --> USB type A cable.
3.1 First download the kingoroot desktop app from their website
3.2 Install the app on your windows desktop
3.3 Go to your mibox device setting (mibox setting not android stock from part 1) and in Security setting and Enable USB/ADB debugging, device will restart for this setting to change.
3.4 connect your mibox to your desktop and wait for the device to be installed and recognized by windows. (If you are using windows 10 it will detect the device by itself)
3.5 Run the kingoroot app on the windows and let it detect the device, as soon as it detects the device root option will appear, click on root option it and wait
3.6 Kingoroot will try to install an app on your mibox, allow it and then this will continue and finish the rooting process.
3.7 Disable USB/ADB debugging, so you can connect USB Flash drives to the device again.
3.8 Check for the root stastus with rootchecker.
(Credits to passerby on xiaomi.eu forums for the guide)
4. How to flash TWRP to device
4.1 download the TWRP App from this link:
dl dot twrp dot me/twrpapp/me.twrp.twrpapp-18.apk 4.2 Download the android ROM and TWRP image together from this link:
goo dot gl/q5DGED password : Mibox2015 4.3 open the zip file and copy this image file to your USB Flash drive
MDZ-16-AA-AndroidTV-V1\TWRP-RECOVERY\twrp-mdz-16-aa.img
4.4 Connect the USB flash drive to the box and copy the image to device storage
4.3 Install the TWRP app on the device using the USB flash drive
4.4 Run it and select first two boxes.
4.5 Go to flash TWRP option and wait for app to ask permission from SU, grant permission.
4.6 Select TWRP flash and select flash from image. Select the image that you copied to device storage.
4.7 Boot into recovery (by this time you have root access and it’s better to boot to recovery with one of the reboot apps ex. Quick Reboot)
(Now you have TWRP, but the problem is every time you reboot the box, the stock rom overwrites the TWRP files and it goes back to Default recovery, to solve this we need to replace the Rom itself too)
5. Replacing the Rom
5.1 While still in TWRP page, make a small boot backup just so TWRP makes a folder in storage of your device.
5.2 Reboot the device from TWRP (reboot system)
5.3 Now using a File manager (I used X-plore) copy the Rom folder to the same backup folder that was created by TWRP in your storage.
Copy This folder:
MDZ-16-AA-AndroidTV-V1\TWRP\BACKUPS\11608V180037788\2014-12-31--18-01-42_6.9.7.949
To this folder: (Which is already should be there created by TWRP)
Internal Storage\TWRP\Backups\ (your device’s Serial number)\
5.4 Repeat steps 4.6 & 4.7 again to Flash TWRP again, after booting to TWRP go to restore and select file (2014-12-31--18-01-) to restore, swipe to restore and wait for 10-15 minutes
5.5 After restore is done don’t reboot, go back to TWRP main page, go to Wipe then advanced wipe, select Dalvik, Cache and Data to be wiped. After wipe is done reboot system
5.6 When android system boot is complete, go to setting down below and change the language to English and its done.
I hope it helps
Click to expand...
Click to collapse
I successfully rooted my mibox 3c (MDZ-16-AA) and installed TWRP app and Android TV.
Now I want to go back to the Xiaomi Original Firmware (1.5.25). I tried to use TWRP and the Update.zip, but it did not work. How can I do it? Many thanks!
---------- Post added at 09:59 AM ---------- Previous post was at 09:53 AM ----------
I read from a Chinese forum that the 1.4.32 can also be rooted. As far as I know the Android TV is based on the 1.3.106. Does it make any sense to root the MDZ-16-AA with the firmware 1.4.32 and install the Android TV then?
Hello.
I was forced to reinstall firmware due to phone issues.
Now I'm again with root and TWRP.
Firmware is on nougat, version c900b300 but many files are missing.
In particular, themes cannot be applied even if I can download them.
I followed a procedure suggested for the Mate 8 but with no results.
Is someone able to help me?
I think this is not a post for q&a section.
Otherwise please move it.
Thanks.
Ah, even the ringtones folder is empty, but this is not a big issue...
Try these 2 methods
1 - https://forum.xda-developers.com/honor-6x/help/solved-huawei-gr5-2017-honor-6x-problem-t3606037
2 - https://forum.xda-developers.com/honor-6x/help/theme-issue-5-0-upgrade-t3579812/page2
First method pushed FM spk in data folder, I rebooted but no FM radio app shows up.
Regarding second method, Google drive file doesn't exist.
I hope to be able to install Oreo when available through TWRP.
Now I don't have the updater and I'm not receiving ota update from Huawei. Unfortunately I'm stuck with March security updates
Dammit, I'm out of ideas at the moment. Plus, i didn't knew that even updater was missing... You wanna try with an apk of mine extracted?
of course mate.
Now I'm more relaxed, as I understand that is better just playing with this phone. I'm not gonna put job related files anymore in, so if something happens, I can recover easily.
Baaaaaaaaad phone...
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Diamantes said:
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Click to expand...
Click to collapse
For Huawei bloatware it's surely a positive thing if you don't care, since that those results "well" radicated into system and aren't easy to remove. For all the rest, looks like you are on a firmware build that was created to another build, and so causes various incompatibilities... But it's the worst case that i saw, except bricking related cases maybe a rebranding to an other variant, with the flash of another firmware could solve at least the missing apps issue. Anyway, i uploaded the updater apk; after all i don't think it'll works sincerely neither making it a system app with apps or modules like systemizer, if all those issues are present already... But in the worst case here, you'll just get an install failure due to an apk version that doesn't match your first, initial build. Try for fun, i would say.
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
You can use apps like Link2SD, but if the file looks corrupt (had this problem too when i accidentally deleted compass app time ago) it means that doesn't matches your build number. You could try by installing a version that matches your actual build.
Diamantes said:
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
Click to expand...
Click to collapse
Yes, with dload method, you need to flash all files available in zip to get everything working, i tries this and everything worked for me without anything missing.
For flashing zip, yes it is PV files that can be flashed via Twrp
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Diamantes said:
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Click to expand...
Click to collapse
They are still getting it. Not sure how
Solution
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Will it work on honor 6x? The hw data is only for p9 ,isnt it?
starkeeper2018 said:
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Click to expand...
Click to collapse
Will it work on honor 6x..the hw data is showing only for honor p9 ,etc but not 6x