Related
Salutations folks,
Just posting some preview screenshots of some work I've been doing on the Alpha2.
CyanogenMod9 (ICS) and ClockWorkMod Recovery 6.0.1.1
It's still a work in progress as I fix various issues and bugs I've come across, but it's
slowly but surely getting to the point of being stable and usable for daily use. When
it gets stable enough, I will post the rom and install files for public consumption/testing.
Running:
CM9 ICS 4.0.4
3.0.36 custom kernel w/modules specific to alpha2 and feature testing usb gadgets (bluetooth, etc.)
NOTE: currently working on upgrading to 3.0.38/3.0.39 kernel
CWMR 6.0.1.1 (koush's latest) w/fully working menu options, backup/restore, key use for menus
NOTE: currently working on implementing touch menu control
Tested/Working:
Camera (stills, video)
Microphone
Rotation sensor
Wi-fi
Hardware keys (VOL+, VOL-, POWER)
Video (software accelerated, 720p)
Touchscreen
Internal/External sdcards
USB Storage mounting
ADB access/control
Bugfixing:
Camera Zoom controls
Video (hardware acceleration possible on cedarx?)
Touchscreen capacitive buttons (MENU, BACK, HOME)
USB Storage Mounting in CWM6 (adb works fine tho)
Screenshots (click to zoom):
custom compiled CWMR 6.0.1.1 (latest) with custom background, menu colour and clockwork icon
CM9 info menu - little fuzzy, sorry about that
in-UI screenshot of CM9 info menu
CLOCKWORKMOD RECOVERY
(Updated to 6.0.1.2), Install scripts updated to Version 1.1
As mentioned in another post, I'm releasing the CWM install for public consumption. Please be aware that due to the issues with my SSA2, that
I will probably not be updating this much. This CWM install is mainly for nandroids, etc. Support will be LIMITED, but this recovery mode should
work fine as is. I will NOT be taking requests for features or my CM9/CM10 roms until I can get my SSA2 working 100% again or another one
falls in my lap. (sorry). BUT, github access to the kernel, recovery and CM9 is publicly available. Get coding, if you want it.
The ClockworkMod recovery install files are located below: (hosted via Dropbox)
7zip (.7z) of ClockworkMod Recovery Install files - 6.6MB
MD5: 5cd49a048ce941d478a84343b228ec18
Ver1.1 MD5: 0e225bc31c5fc523a210753744b19834
7zip executable extracter (.exe) of ClockworkMod Recovery Install files - 6.76MB
MD5: ab74d12fe6a48e877c52cad8cad606d8
Ver1.1 MD5: aa9e75ef70d39aa18cf916b3455f657d
README/Install Instructions:
ClockWorkMod-based Recovery by [email protected]
[ DISCLAIMER ] --------------------------------------------------------------------
First and foremost, please note that by using or installing these files that
you will not hold me ([email protected]) responsible if you brick/ruin
your device in any way. Although every attempt has been made to prevent
this from happening, there is always a chance something can go wrong.
(Luckily, if something does go wrong Livesuite reflashing can usually
fix it, although you will most likely lose any data/settings stored on your
device).
[ CHANGELOG ]--------------------------------------------------------------------
1.0 - 11/03/2012 - Initial CWM install release
1.1 - 11/04/2012 - Add Version A/B script.bins since there are gyro differences
- Consolidate batch install files/add a little choice logic too
- Menu system for install, backups, reboot
[ INTRODUCTION ]-----------------------------------------------------------------
These are simple install scripts and files to install ClockworkMod Recovery
into your SSA2 (Skytex Skypad Alpha2). If you don't know what CWM is for,
please do NOT proceed; you don't need it then (except for maybe nandroid
backups.. but seriously.. if you don't know what it's for. STOP)
This recovery requires the following things:
1. You have USB drivers properly installed for accessing your SSA2
2. You have already upgraded to Skytex's ICS (4.0) via Livesuite
Upgrading your SSA2 to Skytex's ICS will cover both #1 and #2.
If you have not already upgraded, you MUST do so now or the recovery
install will FAIL and/or screw with your SSA2 settings. If you have not
already done so, go to: http://goo.gl/WqZTi
(that's just a shortened link.. if you don't trust it.. go to skytex's site
yourself and go to the firmware download area for the SSA2
and install the appropriate 4.0 firmware/livesuite for your device)
PLEASE NOTE: Upgrading your SSA2 to ICS is beyond the scope of this
document and something YOU need to take care. Have fun!
IF YOU DO NOT HAVE SKYTEX ICS INSTALLED, STOP! YOU CANNOT USE THIS!
Rule of Thumb: Backup your settings/files using TitaniumBackup or some
other app before starting big installs like this!
[ INSTRUCTIONS ]---------------------------------------------------------------
Firstly, settle on WHERE you want to install everything. You have a choice of
the internal SDcard or the external (removable) SDcard. Please be aware that
if you install to the internal SDcard, there's a chance you might have to
reinstall everything if you wipe/reflash your device as the internal SDcard is
usually wiped too. The external SDcard is usually left untouched. I'd
recommend the external SDcard if you have a removable card installed.
Based on that choice, run the following:
Note: The install process is fairly documented and verbose, please note
any errors that may arise if something goes wrong.
1. Run the "INSTALL-RECOVERY.bat" batch script
a. Select the appropriate menu options and submenu options.
That's it!
HOW TO ACCESS CWM RECOVERY
-------------------------------------
Please note that ADB REBOOT RECOVERY command will NOT work with
Skytex's ICS (sorry).. it should work fine with AOSP, AOKP, CM9 and CM10 tho.
From ADB (your PC):
With your SSA2 on, Open up a command prompt, if you don't have adb installed globally,
adb has been provided with the install scripts, just go to that directory and run:
adb shell sh /system/bin/reboot-recovery.sh
From a Terminal (your SSA2):
With your SSA2 on, Open up a command prompt (must be in root, su):
sh /system/bin/reboot-recovery.sh
Hardware Keys access (if installed via install scripts):
With your SSA2 OFF (and recommended unconnected to power or usb, as being in charge
mode sometimes disrupts the recovery mode boot process when using the hardware keys.
Otherwise.. if you are in charge mode (shows big battery icon in middle of screen), just
hold down the POWER button until it goes off/away)
1. Hold down the VOL UP key for 5 seconds
2. While holding the VOL UP key, hold down the POWER button for 5 seconds.
3. While still holding the VOL UP key, release the POWER button. Keep holding the VOL UP
key for 5 more seconds.
4. Release the VOL UP key.
Your SSA2 should already be or should start booting into recovery mode shortly thereafter.
If you SSA2 boots back into ICS, it did not succeed (duh), try again.
[ FEATURES ]---------------------------------------------------------------
Current version: 6.0.1.2
- Menu traversal using VOL UP and VOL DOWN, POWER button to select
- install rom/update zip files
- data wipe/factory reset
- cache wipe
- basic/advanced nandroid backup/restore (to internal or external sd [default])
- partition mount/access/format
- usb mount access via CWM
- dalvik cache wipe
- battery stats wipe
- key testing
- permission fix
[ CONTENTS ]---------------------------------------------------------------
adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll - Easy adb access files
install-recovery-ext/int.sh - android shell script for recovery load
INSTALL-RECOVERY.bat - windows batch script for recovery install
README.txt - this file (duh)
reboot-recovery.sh - android system script to reboot into recovery mode
recovery.img - the actual recovery image
versa/versb-ics-script.bin - uboot settings for bootloader to enable recovery mode access keys
Click to expand...
Click to collapse
Looking good, anyway we can get involved?
Yes... I have an Alpha2 sitting right here just dying for some CM9 goodness...
rosehipzero said:
Looking good, anyway we can get involved?
Click to expand...
Click to collapse
Anyone still interested in doing some dev work on this. I bought two of them last night.
i would love to collaborate with someone on this.
Me me me me!!!
PM sent and the alpha2 is out and on the charger....
Sent from my SAMSUNG-SGH-I717 using xda premium
Sorry for the lack of updates on this one folks.
I ran into an issue with my alpha2 where I somehow flushed the ft5x (touchscreen) EEPROM and was not able to to get a proper firmware flashed in there to get it working 100% again. Tried contacting Skytex and Focaltech with no luck. (even disassembled the alpha2 to get full model info on the chips in there.. have lots of pics if anyone is interested in seeing the insides of the alpha2). Finally got touchscreen back using a firmware designed for another model of the touchscreen controller in the alpha2, but having issue with needing to calibrate it properly since all touches are showing up 50 degrees off. Focaltech and their docs don't have any info on calibration so I'm kinda stuck for now til I get a chance to hack through the ft5x kernel drivers. Since I'm kneedeep in college studies and exams, I haven't had time. Compounded with the fact that I also have an Acer Iconia Tab a500 now, development on the alpha2 will probably grind to a slow drip.
In the meantime, I've updated all my github repo's (http://github.com/thesawolf) with the device setup for cm9, specific cm9 build stuff as well as working kernel. So if someone is willing, you can "easily" work off of that. I'm hesitant to release the cm9 rom I put together as it is unfinished and in a very functional, but still raw form (need lots of framework tweaks and some more build.prop tweaks) but the cwm recovery works fine and fully functional and a good place to start working from (and if anything for the nandroid backups). I can put that up on dropbox later if anyone interested. Please be aware that there are LOTS of good guides and writeups for compiling your own cm9 roms. Please don't ask me to tell you how. Search and Google is your friend.
Anyways, good luck folks. Hopefully I'll have some better news for everyone once I have more time to goof around on my alpha2 (when I'm not working on my a500 too)
CLOCKWORKMOD RECOVERY
(Updated to 6.0.1.2)
As mentioned in another post, I'm releasing the CWM install for public consumption. Please be aware that due to the issues with my SSA2, that
I will probably not be updating this much. This CWM install is mainly for nandroids, etc. Support will be LIMITED, but this recovery mode should
work fine as is. I will NOT be taking requests for features or my CM9/CM10 roms until I can get my SSA2 working 100% again or another one
falls in my lap. (sorry). BUT, github access to the kernel, recovery and CM9 is publicly available. Get coding, if you want it.
The ClockworkMod recovery install files are located below: (hosted via Dropbox)
7zip (.7z) of ClockworkMod Recovery Install files - 6.6MB
MD5: 5cd49a048ce941d478a84343b228ec18
7zip executable extracter (.exe) of ClockworkMod Recovery Install files - 6.76MB
MD5: ab74d12fe6a48e877c52cad8cad606d8
README/Install Instructions:
ClockWorkMod-based Recovery by [email protected]
[ DISCLAIMER ] --------------------------------------------------------------------
First and foremost, please note that by using or installing these files that
you will not hold me ([email protected]) responsible if you brick/ruin
your device in any way. Although every attempt has been made to prevent
this from happening, there is always a chance something can go wrong.
(Luckily, if something does go wrong Livesuite reflashing can usually
fix it, although you will most likely lose any data/settings stored on your
device).
[ INTRODUCTION ]-----------------------------------------------------------------
These are simple install scripts and files to install ClockworkMod Recovery
into your SSA2 (Skytex Skypad Alpha2). If you don't know what CWM is for,
please do NOT proceed; you don't need it then (except for maybe nandroid
backups.. but seriously.. if you don't know what it's for. STOP)
This recovery requires the following things:
1. You have USB drivers properly installed for accessing your SSA2
2. You have already upgraded to Skytex's ICS (4.0) via Livesuite
Upgrading your SSA2 to Skytex's ICS will cover both #1 and #2.
If you have not already upgraded, you MUST do so now or the recovery
install will FAIL and/or screw with your SSA2 settings. If you have not
already done so, go to: http://goo.gl/WqZTi
(that's just a shortened link.. if you don't trust it.. go to skytex's site
yourself and go to the firmware download area for the SSA2
and install the appropriate 4.0 firmware/livesuite for your device)
PLEASE NOTE: Upgrading your SSA2 to ICS is beyond the scope of this
document and something YOU need to take care. Have fun!
Rule of Thumb: Backup your settings/files using TitaniumBackup or some
other app before starting big installs like this!
[ INSTRUCTIONS ]---------------------------------------------------------------
Firstly, settle on WHERE you want to install everything. You have a choice of
the internal SDcard or the external (removable) SDcard. Please be aware that
if you install to the internal SDcard, there's a chance you might have to
reinstall everything if you wipe/reflash your device as the internal SDcard is
usually wiped too. The external SDcard is usually left untouched. I'd
recommend the external SDcard if you have a removable card installed.
Based on that choice, run the following:
If you chose Internal SDcard, run: INSTALL-RECOVERY-INTSD.bat
If you chose External SDcard, run: INSTALL-RECOVERY-EXTSD.bat
1. Run your preferred installation batch script
Note: The install process is fairly documented and verbose, please not
any errors that may arise if something goes wrong.
That's it!
Please note that ADB REBOOT RECOVERY will NOT work with Skytex's ICS
(sorry).. it should work fine with AOSP, AOKP, CM9 and CM10 tho.
HOW TO ACCESS CWM RECOVERY
-------------------------------------
From ADB (your PC):
With your SSA2 on, Open up a command prompt, if you don't have adb installed globally,
adb has been provided with the install scripts, just go to that directory and run:
./adb shell sh /system/bin/reboot-recovery.sh
From a Terminal (your SSA2):
With your SSA2 on, Open up a command prompt (must be in root, su):
sh /system/bin/reboot-recovery.sh
Hardware Keys access:
With your SSA2 OFF (and recommended unconnected to power or usb, as being in charge
mode sometimes disrupts the recovery mode boot process when using the hardware keys.
Otherwise.. if you are in charge mode (shows big battery icon in middle of screen), just
hold down the POWER button until it goes off/away)
1. Hold down the VOL UP key for 5 seconds
2. While holding the VOL UP key, hold down the POWER button for 5 seconds.
3. While still holding the VOL UP key, release the POWER button. Keep holding the VOL UP
key for 5 more seconds.
4. Release the VOL UP key.
Your SSA2 should already be or should start booting into recovery mode shortly thereafter.
If you SSA2 boots back into ICS, it did not succeed (duh), try again.
[ FEATURES ]---------------------------------------------------------------
Current version: 6.0.1.2
- Menu traversal using VOL UP and VOL DOWN, POWER button to select
- install rom/update zip files
- data wipe/factory reset
- cache wipe
- basic/advanced nandroid backup/restore (to internal or external sd [default])
- partition mount/access/format
- usb mount access via CWM
- dalvik cache wipe
- battery stats wipe
- key testing
- permission fix
[ CONTENTS ]---------------------------------------------------------------
adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll - Easy adb access files
install-recovery-ext/int.sh - android shell script for recovery load
INSTALL-RECOVERY-EXTSD/INTSD.bat - windows batch script for recovery install
README.txt - this file (duh)
reboot-recovery.sh - android system script to reboot into recovery mode
recovery.img - the actual recovery image
script.bin - uboot script settings for bootloader to enable recovery mode access keys
Click to expand...
Click to collapse
Install scripts and files have been updated to acommodate the fact that the SSA2's have a Version A and Version B difference that was resulting in an issue with gyroscope use on VersB boards with the VersA-based bootloader settings. Have corrected it and created a menu system for the install scripts to handle backup, internal vs. external install options, rebooting into recovery, etc. with the new bootloader settings too. Please re-download the newer version of the install scripts if you are having any issues (and just to have them handy). Enjoy. (updating main post)
Great work. Installed it on this old tab!
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.
I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.
I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.
works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.
This is an awesome post! Thak you very much.
Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.
Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!
I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!
Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...
Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...
Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".
Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?
So by today (22.09.2014) is your phone oficialy renamed from "ZTE Red Bull V5" to "ZTE V5"
POSTING A PROBLEM
If you have some sort of problem with your device please please get us this info, so we could help you:
1-what rom/firmware are you using
2-what recovery
3-if you have rooted your device
4-what caused the problem
5-step by step description what you did before the problem shows up.
Hi i just made this thread to make a base for everyone who bought this (form me) superb phone.
So far we got root, custom recovery, and many chinese roms (based on Nubia UI, Color OS, LEWA OS, FROG OS...).
There are Mokee AOSP 4.4.4. rom in develpoment and CM11 in development, CM12 also.
2015.02.13 - Latest firmware is 1.17 (andorid 4.4.2, nubia UI2.5.1)!!!
Changelog(google translation from chineese):
-optimize the signal problem
-solving open U disk mode or restart the phone, ringtones revert to the default issue
into the video again, this video from one schedule to start playing the video
-update time management software, to solve the problem of the shutdown alarm clock does not ring
-media library interface, Pictures Pictures folder appear as a blank
-to use the gallery under OTG open unsupported file error
-switching to the media library interface, multiple exposure, suggesting that language View screenshot untranslated
-save the video recording status suspended again after recording, the Pause button to display the error
-optimization manually Focus
-video recording in the recording pause again, long display of detailed information is incorrect
-horizontal screen - portrait - horizontal screen operation, not full screen
-video player interface to open the USB mass storage press the return key error
here is link to my google drive. It contains stock roms from 0.50 to 1.12, GAPPS ect. Also contains tools to root and flash custom recovery.
MY GOOGLE DRIVE ZTE V9180 FOLDER
In my Google Drive there is also two custom recovery CWM and TWRP (thanx a lot to FAZERGOO from 4PDA.ru, here on XDA it is fazerg, so please thank him for his work)..the script in my root+recovery folder is updated, so you have option to flash CWM (6.0.5.1) or TWRP (2.8.0.0.)
here is list of commands you can dial in dialer and get some hidden menu and settings:
*#06# - displays IMEI
##36 - update server settings for OTA
*#*#4636#*#* - display phone information, battery information, battery history, usage statistics, WiFi information
*#406# - touch screen calibration
--proximity sensor calibration--
*#777# - no cover of proximity sensor
*#776# - cover proximity sensor with hand 2-5 cm above..so the bar is in the green
*# 405# - MHL test
to go to recovery you have to poweroff the phone and hold "vol+" and "power" for 2 sec
to go to safe mode....???
best resources for ROMS (chinese sites):
bbs.anzhi.com
www.tdbeta.cn
www.ztehn.com
And of course our friends from Russia thread:
www.4pda.ru
proDOOMmans mega drive where you can find all Mokee, CM11, PAC roms:
HERE! and dont forget to hit THANKS button for everyone who develop and help us to use this device!!!!
TIPS & TRICKS
-HOW TO CHANGE LCD DENSITY and switch to phablet UI!!! Beware, the camera app is little bit smaller then the screen, becaouse of the density, but still works well.
-HOW TO ADD ONE HAND FEATURE
-did you know that when holding home button on locked screen lights a flashlight?
-when you double tap home button on locked screen the time changes to media player controls?
-when you tap several times on any home screen your glas will broke?
-when you zoom out with two fingers on any home screen you will get into screen manager?
-in alarm clock app there is setting "power of alarm", when turned on, you can turn off your phone at night and the phone turns on by itself in the alarmclock time and wakes you up?
complete guide by navin_n
People always asking again and again on flashing ROMs, Recovery, GApps, Root etc. So, I have made detailed step by step guide for this. Hope now it will be clear to everyone for these processes:
BEFORE YOU DO ANYTHING FROM FOLLOWING, PLEASE MAKE ANANDROID BACKUP, BEST WITH TWRP!!!BECAUSE TWRP CAN MAKE BACKUP INCLUDING PRESIST AND MODEMST PARTITIONS!!![/CENTER]
GUIDE TO FLASH STOCK ROM:
NOTE:
1. Be sure to backup all important data (contacts, messages, call records, etc.) before proceeding
2. Ensure that Phone Battery is at least 40%.
3. Downloaded required STOCK ROM.
4. Phone with Stock Recovery.
STEPS:
1. Copy the downloaded zipped STOCK ROM to the root directory of External SD card or Internal SD card.
2. Power-off the phone.
3. Put the phone in the Recovery Mode and for this you need to press Vol+ and Power button at the same time for few secs and then release the Power Button.
4. In the Stock Recovery, perform wipe data/factory reset and wipe cache partition (In the menu, use +/- volume keys to scroll up/down & power button for confirmation).
5. Depending on which SD card you have copied the zipped STOCK ROM, choose "Apply update from /sdcard" or "Apply update from external /sdcard" accordingly.
6. Select the zipped STOCK ROM to flash.
7. Wait until you get the confirmation of successful flashing.
8. Reboot the phone by selecting "reboot system now".
9. DONE. (Initial boot may take some time so have patience.)
GUIDE TO INSTALL CUSTOM RECOVERY + CUSTOM ROM:
AS FOR CERTAIN REPORTS IT IS STRONGLY RECOMMENDED TO FLASH CWM RECOVERY IF YOU HAVE 1/8 VERSION
REQUIREMENTS:
1. Be sure to backup all important data (contacts, messages, call records, etc.) before proceeding.
2. Working Windows PC with ADB Drivers installed - without proper installation of drivers the process will not be successful.
3. Ensure that Phone Battery is at least 40%.
STEPS: (If you need only Custom Recovery, then follow the steps from 2 to 7, other steps you can skip)
1. Download the required zipped Custom ROM and copy it to the root directory of External SD card or Internal SD card.
2. Download the Recovery Tool zip file. (Link to download the Tool) . Make sure to download whole files. After that copy the zipped file to the root directory of C:\ or any place you prefer and then unzip the downloaded file.
3. Enable USB debuging mode. ("Menu Button" >> System settings(Settings) >> About phone(On the phone) >> Tap 6 times on Build number>>"Back button">> More >> Developer options >> Enable USB Debugging)
4. Connect the phone to the PC.
5. Go to the folder where you have unzipped the Recovery Tool file, and then execute the batch file "run.bat".
6. In PC, new window will open. Input your choice of Custom Recovery accordingly.
7. Follow the steps on-screen until all completes.
8. After completion, in the Fastboot menu, select "Boot recovery".
9. If the Custom Recovery was flashed succesfully, you will get CWM or TWRP recovery menu.
10. Perform wipe data/factory reset and wipe cache partition.
11. To flash the firmware: Select "Install ZIP" >> "choose zip from sdcard0 or sdcard1" depending on which SD card you have copied the ROM, external or internal >> Select Custom ROM >> Click Yes to flash selected ROM.
12. Wait until you get the confirmation of successful flashing.
13. Reboot the phone by selecting "reboot system now".
14. DONE. (Initial boot may take some time so have patience.)
GUIDE TO INSTALL GAPPs & ROOT:
REQUIREMENTS:
1. Backup all important data (contacts, messages, call records, etc.) before proceeding, if necessary.
2. Requires CUSTOM RECOVERY.(Mandatory)
STEPS:
1. Download appropriate flashable zipped GAPPS & ROOT files and copy it to the root directory of External SD card or Internal SD card.
2. Power-off the phone.
3. Put the phone in the CWM or TWRP Recovery Mode and for this you need to press Vol+ and Power button at the same time for few secs and then release the Power Button.
4. Flash the zipped files (one at a time): Select "Install ZIP" >> "choose zip from sdcard0 or sdcard1" depending on which SD card you have copied the file, external or internal >> Select Zipped File >> Click Yes to flash selected file.
(No need to do wipe data/factory reset and wipe cache partition)
5. After successful flashing, reboot the phone by selecting "reboot system now". If it ask to fix the permission when you reboot, select Yes.
7. Wait until you get the confirmation of successful flashing.
8. DONE. (Your phone will have GApps and Root Permission)
and don´t forget to hit thanx button to @navin_n, @fazerg and me maybe @DallasCZ
APPS taht can be remover (thanx navin_n)
If you have already Rooted your device then you can easily uninstall the system apps using "Root Uninstallers" available in Google Play.
However, for me , i prefer to use Root Explorer and delete the apps from system folder. The following apps are safe to delete but still i advise you to backup the files before deleting. If you use Root Explorer, make sure to change attribute of the system folder from Read Only (R/O) to Read Write (R/W) when deleting.
Be ware you make it on your own!! If there is also odex file, delete them too!!!
APPs that can be deleted:
folder --> /system/app
nubia_account.apk - only if you log in in nubia account (maybe you need this to use themes)
nubia_Calculator_v1.2.1.apk - calculator app (i dont like it so i installe another one and delete this)
nubia_Calendar_v1.0.apk - nubia calendar app
nubia_ClockWidget.apk - clock widget
nubia_Music.apk - nubia music player
nubia_myfile.apk - nubia file manager
nubia_NBSecurity.apk - nubia antivirus and system cleaner
nubia_NotePad_v1.1.5.apk - nubia notepad
nubia_zbiglauncher_v2.0.apk - nubia launcher for old people (everything is biiig)
NubiaPlatLogo_V1.0.0.apk - nubia lanim showing when you tap on NUBIA version in "about phone"
ZAppDataBackup.apk - nubia main app for backup your phone
ZDataBackup.apk - nubia backup app
ZQuickSearchBox.apk - nubia quick search box (if you install GAPPS it contains original google search box)
ZVideo.apk - very basic media player
If you dont use Live Wallpapers you cen delete the main app:
LiveWallpapersPicker.apk
and of course all livepaper apks
BasicDreams.apk
HoloSpiralWallpaper.apk
LiveWallpapers.apk
MagicSmokeWallpapers.apk
NoiseField.apk
PhaseBeam.apk
folder --> /system/preset_apps
TP_360AppStore_1.9.203.apk
TP_360Video_1.2.0_Nubia.apk
TP_BaiduInput_1000541a.apk
TP_baidumap_6.2.0.apk
TP_baiduvideo_5.3.0.apk
TP_gowhere_1044_131118_150501.apk
TP_iReader_2013122410.apk
TP_JdAndroid_2.6.0.apk
TP_QQ_4.2.apk
TP_QRCodeScaner_v1.0.apk
TP_tieba_5.5.2.apk
TP_Weibo_4.0.0_602.apk
TP_weixin_502.apk
Hi, I'm interested in buying this phone.. Could you tell me your first impressions?
It seems very good but I can't see any support for it, even if it has a Snapdragon 400..
Sent from my VOTO X2
DallasCZ said:
ROOT
the only way to root it so far is to run an Chinese exe, which will root your phone and install superuser (chinese one). Then you need to uninstall the superuser and install one from google play.
CWM
so far there is only chinese CWM 6.0.4.6..looking for someone who can make it english.
Click to expand...
Click to collapse
Hi, can you please provide me the exe file to root and explain me the process to root? I would be really grateful for your help! Thanks
I have WCDMA/GSM V5 3G 9180
ROOT CWM
Hello,
i made a simple bat file, which will root your phone, install custom recovery or original recovery.
here is the link: Dallas Google Drive.
you made everything on your own ..i am not responsible for any phone software/hardware damage.
jday17 said:
Hi, I'm interested in buying this phone.. Could you tell me your first impressions?
It seems very good but I can't see any support for it, even if it has a Snapdragon 400..
Sent from my VOTO X2
Click to expand...
Click to collapse
Hi,
there ar ea lot of Chinese phones, this phone is ment to be sell china only.
There are many forums but in Chinese.
I wrote a little review on gizchina.cz (is in Czech language,so use google translator)
TIP
For new users i recommend do this:
-boot your phone and see vhich version of formware you have (latest at this time is 0.50).
-If you have 0.44, then go to dialer and dial ##36. You get to the menu where you can select which server will be used for updates (at this time is 0.50 only for few people for feedback). then go to ybout phone and tap serach for updates and you get the update.
-after update is installed, go to about phone and tap 5times "build number" line , go back and go to "more" and "developer option" and turn on usb debugging.
-launch my root.bat, select root your phone and th ephone will reboot to bootloader and will be rooted.
-now you can install custom recovery (from my bat.file) it is bilangual CWM 6.0.4.9 recovery. Everything works fine as i used it.
-now after root and cwm recovery installed, make backup of your 0.50 rom and then you can proceed to delete bloatware (a lot of bloatware).
for rotted phones with CWM recovery:
if you want to make update from ZTE OTA, you have to load original recovery, the one in my package is not functional with update to 0.50 and above, so you have to flash from CWM recovery this package, then reboot and get the proper stock recovery, which will be functional with the update 0.44-0.50 and later.
DallasCZ said:
For new users i recommend do this:
-boot your phone and see vhich version of formware you have (latest at this time is 0.50).
-If you have 0.44, then go to dialer and dial ##36. You get to the menu where you can select which server will be used for updates (at this time is 0.50 only for few people for feedback). then go to ybout phone and tap serach for updates and you get the update.
-after update is installed, go to about phone and tap 5times "build number" line , go back and go to "more" and "developer option" and turn on usb debugging.
-launch my root.bat, select root your phone and th ephone will reboot to bootloader and will be rooted.
-now you can install custom recovery (from my bat.file) it is bilangual CWM 6.0.4.9 recovery. Everything works fine as i used it.
-now after root and cwm recovery installed, make backup of your 0.50 rom and then you can proceed to delete bloatware (a lot of bloatware).
for rotted phones with CWM recovery:
if you want to make update from ZTE OTA, you have to load original recovery, the one in my package is not functional with update to 0.50 and above, so you have to flash from CWM recovery , then reboot and get the proper stock recovery, which will be functional with the update 0.44-0.50 and later.
Click to expand...
Click to collapse
Thanks for the info! I'm currently updating to 0.5 and will let you know if I manage to root it too.
I`ve read the review and mine phone too has the squeaky back cover. It started squeaky after just few back panel removals. This is not a concern for me, but I wanted to ask you something else: How is you call quality? When I do calls the other side can hear me perfectly but the sound through my ear speaker is muffled and not very clear. Increasing the volume make it even worse. Do you experience such an issue?
-the back cover is really squeaky (i allready ordered another one)
-I am very happy vith the call quality. I had a nexus s whos volume vas up to 100%. Now i am about 60% and everything is loud and clear as i can hear
root and installing cwm is like a charm..i made it in the las 2 weeks (as i own the phone) about 10times
one Question: If you reboot the device do you also have the message "android is upgrading" every time no matter what you do or not do with the system?
DallasCZ said:
-the back cover is really squeaky (i allready ordered another one)
-I am very happy vith the call quality. I had a nexus s whos volume vas up to 100%. Now i am about 60% and everything is loud and clear as i can hear
root and installing cwm is like a charm..i made it in the las 2 weeks (as i own the phone) about 10times
one Question: If you reboot the device do you also have the message "android is upgrading" every time no matter what you do or not do with the system?
Click to expand...
Click to collapse
- I tried updating to 0.5 both through FOTA and with direclty downloaded update from the chinese official site to the sd card, but I always get some error (forgot what it was), will try tomorrow once again.
- My apps are upgrade after each reboot too. I was hoping that 0.5 will fix this issue, but It seems this is not the case.
- I'm on the hunt for a new back cover too, but I will wait for the official blue ones Share your thoughts on the one you purchased after a few days of usage
My only problem with the phone I experience is the bad incoming sound quality during calls. I will have try another sim card.
ps: boy this phone is a beauty
HuKuTo said:
- I tried updating to 0.5 both through FOTA and with direclty downloaded update from the chinese official site to the sd card, but I always get some error (forgot what it was), will try tomorrow once again.
- My apps are upgrade after each reboot too. I was hoping that 0.5 will fix this issue, but It seems this is not the case.
- I'm on the hunt for a new back cover too, but I will wait for the official blue ones Share your thoughts on the one you purchased after a few days of usage
My only problem with the phone I experience is the bad incoming sound quality during calls. I will have try another sim card.
ps: boy this phone is a beauty
Click to expand...
Click to collapse
Hi, can you please tell the name of chinese official site for our phone? thanks!
SITES IN cHINESE LANGUAGE
Hello,
so there are many sites. To see attachments you have to register to the sites, which is a little bit tricky due to instatnt need of translation in the registration process, but it can be done.
official with a lot of new information also from ZTE service:ztehn.com
the best for custom ROM and Recovery (development):anzhi.com
to see anzhi.com you need to add two adress in your windows hosts file see here
also some good information can be found here on myzte.cn
another tip
-If you get the "android is upgrading" on every boot, then you have to uninstall titanium backup, reboot, wait 3 minutes and let the system settle down, then install titanium again, reboot, and its done.
-if you want to restore WIFI access point and passwords form Titanium Backup, use backup from tar file, not from XML!!!
Waiting on a custom rom
Hello everyone,
I used the method I found at needrom.
It did the trick; the device was rooted, gapps installed, an multilangual.
But I didn't manage to install the latest update (50). I thought it was because the device was rooted, so I removed root, whitout succes, I am still not able to install the update.
Also I think the contact manager is buggy; newly added contacts dissapear after rebooting the device, it doesn't matter if I sync the device. I have to import my contacts from my SD card every time this happens.
So, I hope there comes a good custom rom for this device with this excellent hardware! I have Miui unofficiall on my Xiaomi Mi2s, it works like a charm. I hope soon this device appears on the list one of these days
update
-if you installed the ROm from needrom, i think you cannot upgrade to 0.50.
-on www.ztehn.com you can download the full 0.50 rom (only english and chinese language) this rom you can flash.
-contacts: If you are in contacts, press "more" and "advanced" and check the "default storage" it must be set to your google account. Then go back and check "display settings" and check which accounts are to show in contact list.
I had same problem and the problem was, that all new contact automaticly save to local storage and i have the local storage unchecked to display..so i havent seen my newly added contacts!!!
I have same issue
I have same isse. I dont hear anyone. But everyone hear me. i think that built in speaker doesnt work.
ZTE v5 DualSIM v1.06 beta released (4.4.2 + Nubia UI 2.0, package contains new recovery, H106 update package and G050 restore package)
http://pan.baidu.com/share/link?shareid=2878143782&uk=2436317143 Pass: [COLOR=#0640]j7cb
MD5:[/COLOR][COLOR=#0640]3C318AE402AC5424444F5862B540AF2D
[COLOR=#0640]Uploaded to my MEGA acc: link (1.06 unzipped too)
[COLOR=#0640]BETA release [COLOR=#0640]but seems stable (according to chinese forum feedbacks) I will try thi[COLOR=#0640]s next week, when i receive my v9180 2/8G. [/COLOR][/COLOR][/COLOR]
[/COLOR][/COLOR]
I sucessfully installed 1.06 and its looking good so far. The problem Im facing is the "No connection to google servers" error when I try to add my google account. There is no playstore and I tried to manually install it trhough .apk but again no luck. Have you guys managed to run the playstore with this new firmware?
install my gapps package trough cwm recovery.
Any way to disable soft keys without rooting? Immersive Mode doesn't work because it disables the keyboard.
I'm Possible
mimin0 said:
Any way to disable soft keys without rooting? Immersive Mode doesn't work because it disables the keyboard.
Click to expand...
Click to collapse
So,
Here is the way,
Note-Do it at your own risk!! I'll not be responsible for anything!!
It is not actually rooting your device...:silly:
I'll just tell you the method...
Rest you have to figure it out how to do it because I'm not an owner of Honor 8!!! , Currently my device is Lenovo A6000 Plus
Requirements:
1. PC
2. ADB Files
3. Custom Recovery ( I recommend - TWRP above 3.0 because I've done it same way on my device)
4. Unlocked Bootloader / Fastboot (You should have it)
5. One working Data Cable
6. Minimum Knowledge of editing Build Prop
7. The flashable zip in the attachment below...
8. You with your Phone!!!....
Now Let's Start... (But 1st Try to understand carefully)
1. Download the Flashable zip & put it in your PC
2. Boot your phone into Fastboot/Bootloader ( In whatever process you want - i) Manually or ii) adb reboot bootloader)
3. Now try this cmd - fastboot boot (name of the recovery).img [But before this step you must put your recovery into the adb folder]
After this wait for few seconds... you must be booted into your recovery...
4. Go to Advance > File Manager > Navigate to system > Select build.prop > copy it to where ever storage you want (I prefer internal)
5. Hope you have mtp enable in the recovery mod, if not then reboot the phone into the normal mode then send the extracted file to your pc ( You can also use es file manager/explorer but I will tell the pc method because it is more perfect)
6. Open the build.prop with notepad ++ and try this method which is given by The Hard Gamer in his "[ROM][32bit][port]OCTOS 6.0.1 for lenovo a6000/+" post
EVERYTHINGS WORKING FINE
TO DISABLE NAVBAR EDIT YOUR BUILD.PROP......
-First obviously you need be a Root user
-Backup your build.prop to your PC or anywhere (but backup it!)
-Edit build.prop with a Root Explorer using this line:
qemu.hw.mainkeys=1
you have to add this at the END of the .prop, save and reboot.
[FOR Marshmallow/Android 6.0]
If you're on Marshmallow (Android 6.0) the process is exactly the same, add the line at the end of the build.prop EXCEPT that you must leave 2 spaces after you added the line.
7. Put replace the build.prop file with the new edited build.prop in the flashable zip.... and put it into your root directory of internal/external storage.
8. Now repeat step 2-3.
9. Mount System, if it is already mounted then unmount it then remount it.
10. Go to install > navigate to the flashable zip > Then flash it.
11. Reboot system & Enjoy (If you Can) :angel:
Another Note :-I was here to participate in Honor 8 wining contest so, I can not exactly tell you the right process because you know (I don't own one of the amazing device)... So, If this method works then please hit like :good: & reply me with your experience... Atleast I can deserve this much..
& One important thing...
Sorry For My BAd English!!
pijushsen94 said:
So,
Here is the way,
Note-Do it at your own risk!! I'll not be responsible for anything!!
It is not actually rooting your device...:silly:
I'll just tell you the method...
Rest you have to figure it out how to do it because I'm not an owner of Honor 8!!! , Currently my device is Lenovo A6000 Plus
Requirements:
1. PC
2. ADB Files
3. Custom Recovery ( I recommend - TWRP above 3.0 because I've done it same way on my device)
4. Unlocked Bootloader / Fastboot (You should have it)
5. One working Data Cable
6. Minimum Knowledge of editing Build Prop
7. The flashable zip in the attachment below...
8. You with your Phone!!!....
Now Let's Start... (But 1st Try to understand carefully)
1. Download the Flashable zip & put it in your PC
2. Boot your phone into Fastboot/Bootloader ( In whatever process you want - i) Manually or ii) adb reboot bootloader)
3. Now try this cmd - fastboot boot (name of the recovery).img [But before this step you must put your recovery into the adb folder]
After this wait for few seconds... you must be booted into your recovery...
4. Go to Advance > File Manager > Navigate to system > Select build.prop > copy it to where ever storage you want (I prefer internal)
5. Hope you have mtp enable in the recovery mod, if not then reboot the phone into the normal mode then send the extracted file to your pc ( You can also use es file manager/explorer but I will tell the pc method because it is more perfect)
6. Open the build.prop with notepad ++ and try this method which is given by The Hard Gamer in his "[ROM][32bit][port]OCTOS 6.0.1 for lenovo a6000/+" post
EVERYTHINGS WORKING FINE
TO DISABLE NAVBAR EDIT YOUR BUILD.PROP......
-First obviously you need be a Root user
-Backup your build.prop to your PC or anywhere (but backup it!)
-Edit build.prop with a Root Explorer using this line:
qemu.hw.mainkeys=1
you have to add this at the END of the .prop, save and reboot.
[FOR Marshmallow/Android 6.0]
If you're on Marshmallow (Android 6.0) the process is exactly the same, add the line at the end of the build.prop EXCEPT that you must leave 2 spaces after you added the line.
7. Put replace the build.prop file with the new edited build.prop in the flashable zip.... and put it into your root directory of internal/external storage.
8. Now repeat step 2-3.
9. Mount System, if it is already mounted then unmount it then remount it.
10. Go to install > navigate to the flashable zip > Then flash it.
11. Reboot system & Enjoy (If you Can) :angel:
Another Note :-I was here to participate in Honor 8 wining contest so, I can not exactly tell you the right process because you know (I don't own one of the amazing device)... So, If this method works then please hit like :good: & reply me with your experience... Atleast I can deserve this much..
& One important thing...
Sorry For My BAd English!!
Click to expand...
Click to collapse
Thanks. I was also looking for solution of this issue and your solution helped me a lot
I was looking for a method which does not involve custom recovery and unlocked bootloader, should've probably mentioned that. If I go the TWRP way then may as well root it, but then I'd lose OTA.
Don't feel comfortable doing that just yet.
Rickyzx said:
Thanks. I was also looking for solution of this issue and your solution helped me a lot
Click to expand...
Click to collapse
wow
I'm glad to help you!!
Please hit thanks if you really liked it!!
---------- Post added at 10:46 AM ---------- Previous post was at 10:28 AM ----------
mimin0 said:
I was looking for a method which does not involve custom recovery and unlocked bootloader, should've probably mentioned that. If I go the TWRP way then may as well root it, but then I'd lose OTA.
Don't feel comfortable doing that just yet.
Click to expand...
Click to collapse
I can understand what you want to say!!
But listen,
You can do the whole process without boot the phone in normal mode...
Just unlock the bootloader before the process and relock it after it...
It's that simple..
And It will automatically do a factory reset after unlocking..
My Previous phone was MMX CAnvas A1
I have done many experiments on it like these...
But At the end I still got the OTA updates... Even my SuperSu (By systemless flashable zip) is installed
And you must take some risk in your life to get better results!!
Hope you understand!!!
And press thank button if it helped!!
So recently I was browsing Wish and discovered phone's could be bought and ordered two devices out of pure curiosity.
This guide probably will apply to a LOT of devices out there, if it works for you and you aren't on one of these devices, let me know! More than interested to see how many
devices this will work on apart from these 2 Wish specials I do plan on buying a few more Wish devices in future to see which one's are the best to go for in terms of price/performance.
This guide will go through rooting them and restoring a few parts of Android.
This applies to the following devices:
-Alps R10
-Alps S93
I'm not responsible for any damage done by following this guide, please do so at your own risk.
I don't like using Kingoroot and don't suggest it at all, but for this guide we will use it, following by replacing it entirely with SuperSU.
Things you'll need:
-Kingoroot APK (Not to mix up with Kingroot)
-SuperSU 2.79 APK (2.79 is required for rooting after Kingoroot, any newer versions will give you the error 'Binaries occupied')
-Root Browser
-Root Uninstaller Pro (or a similar app)
Let's begin!
1. Start off by installing the following Apps: Kingoroot, Root Browser Classic (optional, not needed for root), Root Uninstaller Pro
2. Launch KingoRoot and allow it to root the device, you might need to restart it once complete.
3. Once rooted, open up Root Uninstaller Pro and confirm that you have root access. (OPTIONAL: Remove the preinstalled Facebook and WhatsApp apps. I can't confirm if these apps are legit so it's best they go)
4. Install SuperSU 2.79 from the downloaded APK file.
5. Open Root Uninstaller Pro, switch to 3rd party apps, select SuperSU, and push "To system app", reboot the device and allow android to start back up. You'll get a message saying "Android is upgrading" Sit tight as this can take a few minutes.
6. Open up Root Uninstaller Pro, switch to System Apps and locate SuperUser (Ensure you get the KingoUser one and not SuperSU which we just installed) and remove Kingouser. DON'T REBOOT THE DEVICE.
7. Close Root Uninstaller Pro and open up SuperSU. You'll get a message that binaries need to be updated, push YES for this and select NORMAL installation. Wait up to 10 minutes for this to install. It'll take a while on these devices. Restart the device once complete.
8. Open up SuperSU and confirm everything it no longer asks for binaries to be updated.
9. Open up Root Uninstaller Pro, head to System Apps, and remove Kingoroot.
10. Reboot device.
11. Go to the Google Play Store and install the latest version of SuperSU. Launch it and update the binaries again once prompted. Reboot the device once this is complete.
The device should now be rooted and Kingoroot/Kingouser free. You can remove Root Uninstaller Pro here if you wish!
Enjoy your rooted device! Everything after this is optional, but just helps restore a bit of Android.
Optional steps:
-Increase screen resolution
For this you'll need ADB.
1. Head to settings, unlock developer mode by going to About Phone and spam click Build number until it says "You are now a developer"
2. Go back to settings, into Developer Settings and Enable USB Debugging.
3. Download the Android platform tools.
4. Load up a command prompt in the directory of your Android Platform tools.
5. Set the new resolution:
-For Alps S93, enter: 'adb shell wm size 960x1920'
-For Alps R10/R11, enter 'adb shell wm size 1080x1920'
6. Update the density. Your taps might be a little off, and some things might not look right without this. These are the best I've found so far for these two devices:
-For Alps S93, enter: 'adb shell density 280'
-For Alps R10/R11, enter 'adb shell density 320'
7. Reboot and confirm with an app like ResInfo.
-Replace boot animation and shutdown animation with stock Android or a custom one
1. Head into SuperSU, Go into the Settings tab and un-check "Mount namespace separation" (This is required, otherwise you'll get issues writing to root. You can turn this off later.)
2.Launch Root Browser/Root Browser Classic
3. Swipe left to reach the root directory, navigate to the following path: System > Media
4. Delete/Rename/Replace bootanimation.zip. If you remove or rename it you'll get the original Android boot animation.
5. Delete/Rename/Replace bootaudio.mp3. If you remove this, you'll have no boot-up sound.
6. Delete/Rename/Replace shutanimation.zip. If you remove this we'll get the stock Android shutdown animation, which happens to be the same as the boot animation.
7. Delete/Rename/Replace shutaudio.mp3. This will make the shutdown silent.
8. Reboot the device and confirm you have the stock Android boot animation!
-Speeding up the devices a little.
For this one you'll need to install No-Frills CPU Control. It's a great little app and will help us out here especially with the R10/R11.
1. Go to the Google Play Store and install No-Frills CPU Control.
2. Launch No-Frills CPU Control and grant SuperSU permission if prompted.
3. Apply the following Settings:
Max Clock Frequency: (Alps-S93) 1.3GHZ and for the R10/R11 set it to 1.001GHz
Min Clock Frequency: (Alps-S93) 1.001GHz and for the R10/R11, 1.001GHz
Governor: Performance
I/O Scheduler: noop
Apply on boot: This one is completely up to you, however I've turned it on and not experienced any issues.
4. Push Apply and grant root access if prompted.
Other modifications I've made that aren't covered in this post:
-Removed the clone Samsung theme from the R10/R11. This can be done using Root Uninstaller Pro and locate the theme app and just remove it. Reboot and it should be gone.
-Replace Launcher3 with stock CyanogenMod. To do this you'll need to install Nova Launcher, Load up Root Uninstaller Pro and Remove Launcher3 under System Apps. Install CyanogenMod's Trebuchet Launcher and set it as a system app. Reboot and choose default launcher as Trebuchet. You can pull Trebuchet's APK from any Android 4.4 ROM on the internet. I used one from a Galaxy Young.
-Enabled the Navbar at the bottom. This can be done with Root browser, head to System, Build.prop and add the line 'qemu.hw.mainkeys=0' Save and reboot.
Hopefully this can help some of you out there who buy one of these devices, whether it was for fun, by accident or on purpose.
Let me know if this worked for you or not!
Hi, on my "ALPS R10" kingoroot failed to root. Error code 0x142222.
Tried with apk and PC version.
Any idea ?
Thx
roms
Hi, Any way to upgrade the version of android with a custom rom and any suggestions?
globren said:
Hi, Any way to upgrade the version of android with a custom rom and any suggestions?
Click to expand...
Click to collapse
Without unlocking the bootloader or flashing a custom recovery, I don't think it's possible to upgrade the version of Android. This guide is just for gaining root access.
roms
"Cobs" said:
Without unlocking the bootloader or flashing a custom recovery, I don't think it's possible to upgrade the version of Android. This guide is just for gaining root access.
Click to expand...
Click to collapse
Thanks for the quick response. I already unlocked the bootloader but can't find any custom recovery for that particular phone (R10). I bought it just as a spare in case one of my four daughters breaks or has her phone stolen, but it seems to have ingrained malwares (the browser for one) and I don't trust it as it is. If I find a solution I will let you know.