Related
Hi XDA geeks , pros and fans !
I'd like to start this new threadline concerning the freshly-appeared TCT MOVE handheld device marketed for the budget segment.As i understand it appeared in march or later this year and has quite good specs for the approx. 100 euro category.
Some details can be found on
http://alcatelonetouch.com/products/smartphones/move
Contrarily to some beliefs IT IS NOT a branded OT-908 ,rather a cosmetized one .It comes in black or silver / white , a bit heavy for it's size , and higher specs than the OT-908.
Concerning the hardware specs, i'll be coming back later with some accurate chipset and sensor details.For now
OS is Android Froyo v2.2.2.Looks like there will be official ROM updates,at the time being there is the OneTouch Upgrade v1.2 ,which downloads about 540 Mb chunked firmware files, and exits with error.
Memory is 512 Mb RAM , for user space is available about 300 Mb
512 Mb ROM flash, available to user about 160Mb.
SD card slot supports up to 32Gb MicroSD, the phone comes with a 2Gb one.
Camera is a 2.1Mpixel one.There is no secondary one,but the main camera is available for video calls,with Yahoo! Messenger i tested it myself.How to use it this way i will explain later.
GPS is amazing , if assistance software is used , the lock-on takes only seconds.
Sensors - linear acceleration sensor
- 3 axis orientation sensor
- 3 channel magnetic field sensor (digital compass)
- light sensor for illuminance detection
- optical proximity sensor , it seems not in use by operating system(or rather poorly)
Processor - 600 MHz Qualcomm ARMv6 compatible, min frequency is 122 Mhz, and deep sleep capability.Qualcomm MSM 7627 chipset
rooting ?
hi djada80.i should like to ask if you managed to root your phone ?
Yeah , it's quite simple.There are in the Android Market some free apps , i think the best which i also use is the one named Ginger Break.Just download and install it.Detailed usage info can be found here
http://forum.xda-developers.com/showthread.php?t=1044765
firmware upgrade
it seems that the branded ones somehow cannot be upgraded ! at this point i need assistance , so PLEASE , if there is anybody experienced in debranding Acatel smartphones, then YOU ARE MOST WELCOME !.I saw guys having problem with debranding T-Mobile Move , so let's DO IT !
cannot sync with windows
i cannot sync my tmobile move with windows.have a toshiba satellite c665 with win 7 .pls help !
connect phone to computer,enable usb tethering.install alcatel android manager on computer. Can be found here
alcatelonetouch.com/contents/download/T-Mobile_AndroidManager_2.2.1108.1645.rar
This should work,instead of Android Sync Manager WiFi ,the last has some issues with this phone ,do not use it.
Yahoo! messenger front camera
Contrarily to some beliefs THERE IS POSSIBLE TO MAKE VIDEO CALLS with front camera only on Froyo 2.2.It is quite simple:
1.) if you have any version of yahoo apps , remove them all
2.) install Y!Messenger v1.3.2 , the afferent audio and video plugin and
optionally Y!Mail v1.3.2
Nothing fancy with it , just works.Remember, DO NOT UPDATE from Market.
Might also check this,if it doesn't work
http://forum.xda-developers.com/showthread.php?t=1087769
remove bundled apps ?
Hi !
Is there a way to remove some of the unnecessary factory shipped apps ?
RE
Yes , there is. So the smart method vould be to remove them from phone memory , and eventually install it on SD Card , if they are (and they are) UNMOVABLE.
Or just leave them ,anyway a factory reset will restore all the shipped applications.
1.) [optional] install Android SDK with platform 2.2 , sdk tools and eventually drivers.Enable USB debugging on device.On PC launch command prompt and change directory to \Android\android-sdk\platform-tools\.Run command
adb shell pm setInstallLocation 2
This enables SDCARD installation by default.Prerequisits to have ROOT ACCESS.
2.) with RootExplorer simply delete unwanted applications from \custpack\apps\ on device.Optionally you can make backups.
3.) if you made backups , the backed-up apk can be used to be reinstalled , NOW ON SD CARD
Good luck.
RE again
A reboot of the device is required to cleanup the junk after a forced delete.Or it can be done manually , BUT USE CAUTION.
i have an alcatel move branded Cosmote Move, i like this phone very much but i`ve managed to brick it the second time, first time i bricked and took it to waranty, they reinstall the software free of charge, now it has the same simptoms (pass the carrier logo and get stuck to carrier animation) and i need to send it to waranty again. i dont manage to get it unbricked. i`ve root it with gingerbreak but this phone doesnt go to recovery mode. i`ve searched the internet and google it for hours, but nothing.
if anyone knows how to do it please tell me, in the user manual says hard reset vol - and power, get stuck whit touch buttons light up and screen black!!
thanks in advance
re Themaster
it's not a brick yet i suppose , though you didn't specify how you managed to "brick" your phone.a nice clean reflash would solve the problem , probably you deleted some system files while in root mode.again did you use root explorer or something similar ?
try a factory reset as it follows:
1.) turn off the phone
2.) press vol up and the power on and hold the buttons pressed for about 1 minute
3.) the phone boots up , android logo appears and then an animation with some sort of thrashcan or whatever
4.)wait until it finishes , then the phone shuts down automatically.power on the phone and it will be restored
Beware ,battery must be at least 70 % charged or kept in charger , NOT USB connected to PC.
This restores phone to factory state , but not all the applications from /custpack/apps
Best regards !
Useful Key Combinations
These keypress modes apply on a shut down phone
Hard Reset - reinstalls android core system from ROM , deletes user data and misconfig
key combo : vol up + power on long pressed until trashcan animation appears
Flash Mode - used for ROM update , useless momentarily
key combo: vol down + power on long pressed , black screen appears and touch buttons lit up
Root access , mount filesystem with root access ,DANGEROUS !
key combo : home + power on long pressed until boot
build environment under Ubuntu
Lately, there has been some problems setting up an Android build environment under Lucid Lynx, as i've seen many have been complained for the missing java5 jdk.
For Romanian users: seems to be a problem with the Romtelecom DNS servers , when adding Jaunty or Dapper repositories to Lucid.
Use Google DNS as alternatives 8.8.8.8 and 8.8.4.4.This works.
From what I've been able to determine. The move and 908(s) are the same hardware with with only cosmetic differences. Something is different in software, I've been unable to root my 908s with ANY tools I've found.
I was also unable to use ADB under windows. The handset apparently requires four drivers, I was only able to find three of them. I got the Alcatel tools to work, as well as tethering, but no ADB. i didn't have any such issues under Ubuntu, but without root it isn't helpful.
I could not locate a stock rom or source anywhere on the Alcatel sites, so I sent a GPL request, i'm waiting to hear back.
UPDATE
After a long night I managed to root my 908s. I'll write out the jist of it, but I was flying by the seat of my pants, fueled by caffeine and sleep depervation. DON'T consider this a HOWTO.
First off, to the best of my knowlage there is no one click solution as of yet. As I said before still missing the driver that makes ADB work in windows, and handset based solutions didn't pan out. A little reasearch showed that the OT-990 has the same chip/ram and ROM space as ours. The screen is bigger, and I don't know what board is in it, but on a hunch I figured it was close enough. So I went here: http://forum.xda-developers.com/showthread.php?t=1164391 in the hopes that some sort of combined effort in future ROM development would be possible.
Yes that's right folks its a guide to MANUALLY root you handset with ADB. So not for the faint of heart. I didn't have high hopes, as issuing ls -l on either the sqlite folder or data threw a permission denied. So blindly I tried to push psneuter, busybox and su to /data/local. I almost fell off my chair when it worked! from there I used psneuter to get ADB into root, and managed to get the su binary to /system/xbin, and Superuser into /system/app. Superuser was installed, but still no root. So I checked out Root Checker to see what was going on. There are three places that su typically lives; /system/xbin, /system/bin, and /sbin. So I tried to put su in those folders. I got it into /system/bin but sbin is mounted read-only. I did not remount any directories, as the instructions are lacking syntax (I'm a little rusty with advanced mounting commands). I think things are mapped a little differently anyway. I still did not have root on the handset, so I then fired up Superuser to see what it could see. It saw the su binary, even though it wasn't working right. Then I thought well if it can see it, then maybe it can update and fix it. Sure enough after running the update to su in Superuser, (drumroll please...) I had working root.
So that's my story so far, I'm gonna give Alcatel a week or so to reply to my request. Then we'll take it from there. (Hey it worked on Huewei right?)
If a real dev should come across this, feel free to jump in. Its a solid little phone and has the potential to work on a range of handsets.
Gratitude
Thanks snkiz for your attention ! I am pleased that someone 'heavy' noticed my efforts of dedicating this threadline to the newcomer ! Indeed a small little phone with potential , maybe in time we get it gingerbread , cupcake ( or whatever ),even wm6.5 or 7 ...
As of ADB drivers , i had ADB from the first by these steps:
1.) http://www.alcatelonetouch.com/contents/download/move upgrade 1.2 Setup.rar , package contains the drivers
Now i noticed that when i try firmware upgrade , the utility downloads about half a giga of *.bin files and then exits with 'download failed error'.
2.) installed Android SDK , platform tools and Google drivers (i am not sure if necessary), the 2.2 platform (api 8)
Under Win7 cmd in platform tools , adb shell , su and on device pops up 'unknown has been granted superuser rights' and voila! in cmd shell i have '#'.Previously installed Gingerbreak.
My device is a Cosmote Move.
Ya, no I got that file too. I think they are "consumer drivers" because like I said I got all the Alcatel tools running but on my win 7 one driver was still missing, and I have pretty good googlefu. effin hate windows, this is why. I'm by no means a "heavy" but I am comfortable in a Linux environment, that helps alot. As to you being able to get gingerbreak to work, i'd bet that comes down to carrier firmware.
---------- Post added at 06:53 PM ---------- Previous post was at 06:39 PM ----------
djada, seeing as your the op could you please re-tag the thread with the model numbers to make it easier to find? cosmote, 908, 908s, and qualcom should do.
perhaps a mod could move this thread to the android hacking forum where it can get the proper attention please?
ADB driver
Driver files are from WHATEVER.\android-sdk\extras\google\usb_driver\ , if does not install automatically , can be forced.Anyway Win$ux 7 detects ADB interface , installs some sh.t from windows update server , and you'll have an ADB interface in Device Manager (working or not).Try to force the google drivers.
On the other hand ,i'm sorry but dunno how to move the thread , maybe i should start a new one in
http://forum.xda-developers.com/forumdisplay.php?f=565&order=desc&page=552
Just looked at it and they don't have Alcatel
Mod
Just started workin on a Cyanogen build , if i manage to build at least a kernal img , maybe i can lure in the Koush guy from github.We are in need of flash , backup , recovery tools.Not as lucky as the Samsung or HTC guys ...
I AM NOT RESPONSIBLE FOR ANY NEGATIVE IMPACTS OR CONSEQUENCES ON YOUR PHONE IF YOU SO CHOOSE TO USE THIS GUIDE.
I own the ZTE U950 and had realized that there is very little information (in English) on how to do anything beyond stock for this incredible phone. After hours of research and translation I was able to figure out everything needed to get this phone to a "better" state. Since then I - and other XDA members - have been trying to keep the ZTE U950 alive...
ZTE U950 SPECS
NVIDIA TEGRA 3 (1.3MHz)
1GB RAM
4.3" Display (480x800)
5MP Front Camera/0.3MP Back Camera
Android OS 4.0.4
DRIVERS
Here are the "Join Me" drivers so that your PC can recognize the ZTE U950.
KERNEL
Stock - This is the stock kernel's source file.
Custom - This is a custom kernel for stock ROMs that can be OC'd to 2.5GHz.
ROOT
1) Make sure you have USB Debugging Mode and Unknown Sources checked in your phone Settings.
2) Connect your phone to your PC.
3) Download and open Genotools.
4) The program will open, click the 4th tab (last tab on the right).
5) Ensure that your phone is plugged into your PC.
6) Click the 2nd ROOT button.
7) A popup window will appear, press OK.
8) Your phone will then have a popup window, click the "Restore My Data" option.
9) The phone will restart several times, leave it for a few minutes.
10) This is the odd part... The phone will likely not stop restarting, and when you try to click the unlock key for the screen, it will automatically restart. Disconnect the phone. It should continue to restart.
11) Force the phone off.
12) Restart the phone.
13) If you have SuperUser, you are then rooted. If not, repeat these steps.
ROOT - NEW VERSION #1 (UNTESTED!):
1) Download the file here.
2) The instructions read verbatim are, "1 If your phone is not acquired before the ROOT privileges, we choose 1 root [next line] 2 after enter". Which I assume means click root, then enter...
ROOT - NEW VERSION #2 (UNTESTED!):
1) Download the root kit here made for the ZTE U950 (it uses the Chinese recovery), and extract to your desktop.
2) On your phone, go into Settings and enable USB Debugging under Developer options.
3) Connect the phone to your PC (Windows OS should fail to recognize the device).
4) Run either DrvInst_x64.exe or DrvInst_x86.exe. If you are unsure what you have, run both, the wrong one will fail with an error message.
5) After installation, unplug and replug your phone.
6) Go into Device Manager. You should be able to see a "ZTE TD Handset ADB Interface" under the "Android Phone" section. If you don't, reinstall the drivers again.
7). To root, simply run the U950_Root.bat file, and follow the instructions.
RECOVERY (CWM/TWRP)
1) Download the Chinese CWM or English TWRP recovery.img and place it into the root folder of your external SD card.
2) Download a terminal emulator. (If you are unable to download one, use the APP TRICKS described near the bottom to install a terminal emulator onto your phone.)
3) Open the terminal emulator.
4) Type in "su" then hit the return button.
5) Now type in the following:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
(and press the return button)
6) There should be a few lines beginning with something like 14052 or 14272, if not, then the above input was not typed correctly. If so, the recovery should now be installed.
GET INTO RECOVERY
1) Turn the phone off.
2) Hold the Power button + Volume Down button. When the ZTE logo comes up, count two seconds and then let go of the buttons.
3) The phone will enter into recovery. Use the Volume rockers for up and down and the power button to choose (if on CWM), or simply touch the buttons (if on TWRP).
4) I will describe the standard processes here if using CWM - the menus are top-to-bottom on the phone, which are written left-to-right here:
The Main Menu:
[*] Reboot system now
[*] Select zip to flash/install
[*] Wipe data
[*] Wipe cache
[*] Backup and restore
[*] Flash memory/Format
[*] Advanced setting
[*] Turn off phone
The Zip Menu:
[*] Install from zip
[*] Install from internal
Wipe Date:
[*] Confirm wipe data
[*] Do not wipe data
Wipe Cache:
[*] Confirm wipe cache
[*] Do not wipe cache
Backup and Restore:
[*] Backup
[*] Restore
ROMS (ALWAYS MAKE A BACKUP BEFORE FLASHING ANY ROMS TO THIS PHONE!)
Factory ROMs (in order of release)
U950V1.0.0B02
U950V1.0.0B14
U950V1.0.0B18
U950V1.0.0B22
U950V1.0.0B04
U950V1.0.0B05
Custom ROMs (in no particular order)
6240-jingjian
MIUI3.3.7
CustomRom-B14
DeodexedMIUI3.3.7
EN&CN-MIUI3.3.7-msdfyc4zwg
MIUI3.2.8-ysdfyc4zwg
Signed-121223-MZECN-CookedROM
SignedROM
V2.0.0-Hiapk-XC-iSignFile
12-21ROM
4.2CameraROM
RandROM
MIUI1220
V2-MaunJ
CM10/.1 - HeatSka Edition
This should be listed under ROMS, but I felt that it needed its own section. Ska and I worked on this for quite some time getting all the kinks worked out. We did not create the original version of this unofficial Cyanogenmod port, but the original had many issues and was not maintained after its initial release. All the major problems have been worked out in our HeatSka edition.
The ROM was initially CM10 (4.1.2), but it has been mixed with files that list it as 4.2.2 (CM10.1) under the information section. In either case, it is Jelly Bean! Aside from the fixes we have implemented, there are also numerous tweaks and mods for UI speed, network speed, battery consumption, app installs, and much more. There is almost no theming, just enough to know that this is our enhanced (and better) variation.
The only known issue that may arise is CPU throttling. We have included an app called, "LGP880 Booster". This app will allow a CPU speed boost when turned on, with a temperature threshold to prevent overheating. If you wish to save battery, only enable this app when playing a game or using CPU-intensive apps.
DOWNLOAD: CM10.1/2 - HeatSka
FLASH A ROM
1) Download a ROM.
2) Place the ROM in the root of the phone's SD card.
3) Enter into recovery.
4) Wipe data.
5) Wipe cache.
NOTE: Wipe data and cache are the Factory Reset button in TWRP.
6) Follow the menus to get to the ROM in the SD card.
7) Click the power button to choose the ZIP if on CWM (or just push the designated button on TWRP).
8) The ROM is being flashed.
9) Follow the left arrow (the last selection) on the menus to get back to the main menu.
10) Choose the first option on the main menu to reboot on CWM (or click Reboot followed by System in TWRP).
NOTE I: The ROM will probably be in Chinese. Find the Settings icon and click it. Go down to the Language & Input setting and click it (there is a capital "A" next to it). Click the top setting and choose the desired language.
NOTE II: There may not be an English keyboard available, so download this 4.2 keyboard ZIP file and flash it in recovery.
INSTALL GOOGLE PLAY
1) Download and install a file explorer like ES Explorer (free) or Root Explorer (paid). (If the phone is unable to download a file explorer, use the APP TRICKS described near the bottom to install one onto the phone.)
2) Download and take the three files from the RAR file for Google Play and place them in a folder on the phone that can easily be reached with a file explorer.
3) Open up a file explorer.
4) Move the three files to the "/System/App" folder on the phone.
5) Give the three files each the same permissions (Read for all three groups, and Write for User).
6) Restart the phone and Google Play should now be installed.
Notes: a) There are cases where two Google Play store icons may appear. They should both work and not cause problems.
b) If the store does not show, redo the process above.
c) This trick does seem to work on other Android devices as I have successfully done this on a Galaxy Note N7000.
INSTALL FACTORY ROM
1) Download a Factory ROM from above and place the "update.zip" file in the root of your external SD card.
2) Go to Settings.
3) Go down to About Phone and click that.
4) Click on System Updates.
5) Remove the check mark.
6) Click OK.
7) The phone should restore to whichever factory update file was used.
APN FIX (MOBILE DATA FIX)
If your mobile data is not working then use this method to fix your APN:
1) Revert to stock ROM (or any custom ROM where mobile data does work).
2) Download and open a file explorer like Root Explorer or ES Explorer.
3) Go to /system/etc
4) Copy "apns-conf.xml".
5) Go to /sdcard/
6) Paste "apns-conf.xml".
7) Flash ROM.
8) Download a file explorer and open it.
9) Copy "apns-conf.xml".
10) Go to /system/etc
11) Paste "apns-conf.xml" (overwriting the existing file).
12) Reboot the phone.
13) Mobile data should now work.
GAME SUPPORT FOR ZTE U950 (WORKS ONLY FOR U950V1.0.0B02)
Note: I have not tested this. Apparently the first firmware version of this phone is not recognized by Google Play for certain Tegra games. If this occurs, try the following method.
1) Make a backup of the System folder. (It is easier to make a Backup of the entire ROM in recovery...)
2) Insert the build.prop file from this file.
3) Clear the Data for Google Play store (Settings > Apps > Google Play > Clear Data).
4) Reboot the phone.
5) When opening Google Play it should make give their agreement again. If it doesn't, then Data has not been cleared.
6) The rows modified in the build prop is as follows:
Desire ro.product.model = X
HTC ro.product.brand =
Desire ro.product.name = X
Desire ro.product.device = X
...
HTC ro.product.manufacturer =
AGAIN, I HAVE NOT TESTED THIS SO USE AT YOUR OWN RISK!
APP SUPPORT FOR ZTE U950
Note: Some apps will throw package errors after downloaded and then will not install. This method will help a lot of these errors from occurring. It doesn't work for all, but it will for some [tested with Dead Trigger 2].
1) Download this file.
2) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and put com.google.android.maps.xml in /system/etc/permissions
3) Put com.google.android.maps.jar in /system/framework
4) Reboot the phone and now apps should install without issue.
DEAD TRIGGER 1
1) Enable graphics details to High in Setup/Others.
2) Exit the game.
3) Use a file explorer like ES Explorer (free) or Root Explorer (paid) and go to /data/data/com.madfingergames.deadtrigger/shared_prefs/
4) Edit the com.madfingergames.deadtrigger.xml file.
5) Change <int name=”UnityGraphicsQuality” value=”1″ /> to <int name=”UnityGraphicsQuality” value=”2″ />
6) Change <int name=”OptionsGraphicDetail” value=”2″ /> to <int name=”OptionsGraphicDetail” value=”3″ />
7) Save the com.madfingergames.deadtrigger.xml file.
8) Remove all write permission on User, Group and Other for the com.madfingergames.deadtrigger.xml file.
9) Delete the com.madfingergames.deadtrigger.xml.bak file.
Note: This technique works on any non-Tegra device.
APP TRICKS
If apps cannot be downloaded normally (from Google Play), this guide will show an alternative method on how to install them:
1) Download the necessary apk file online.
2) Open the 4.2LatinIme.zip with 7zip or WinRAR and delete the keyboard APK (or keep it if not installed yet).
3) While the ZIP is open go into "/Sytem/App" and place in it any APK you want installed.
4) Boot into recovery.
5) Flash the ZIP file.
6) Reboot and the app(s) should be installed.
Note: I have noticed that certain apps do not flash properly so an alternative APK needs to be downloaded. However, once you have the right apps to install Google Play, you should be able to download any apps from the store.
HARDWARE FIXES BY SKA
NOTE: Always work without the battery attached to the phone.
SIM Card No Longer Works
INFO: There is a diode which provides voltage to the SIM card. Somehow it has become loose, which disallows current to the SIM. Thus, the baseband cannot recognize the SIM card any longer.
FIX: The easiest way to fix and check something is to "re-flow" the PCB (printed circuit board). The modem soldering must be re-flowed in order to reconnect the loose diode and re-allow voltage back to the SIM card.
Touchscreen Not Displaying
Open up your phone. If you don't know how, then you won't be able to continue...
There are three connectors on the left soc side. Check the upper connector near the audio jack and try to seat with a pair of tweezers very gently.
There is a white line on every connector - apart from the battery connector - pull up straight. It must be exactly at the of the beginning of the brown clip when pulled downwards.
MISC
I have successfully paired this phone with a PS3 controller using Sixaxis. This is not unique to my phone as I have verified that there is support within the Kernel for this.
It does seem that Wii controller support can be turned on according to the kernel...
There are no known custom kernels for this phone, however, the incomplete Cyanogenmod ROM available does seem to use its own kernel.
The phone is "stuck" on ICS 4.0.4 with almost every ROM. The incomplete Cyanogenmod ROM upgrades the OS to JB 4.1.2.
The phone is known to have heating issues on different (all?) firmware versions. While these do not seem to attribute to hardware failure, it is an annoyance.
Different firmware versions apparently produce varying levels of GPU performance: The best in GPU performance is U950V1.0.0B14, but this build may produce issues in some games. The worst in GPU performance is U950V1.0.0B18, but it is stable. The U950V1.0.0B22 is stable as well but has better GPU performance than B18. I have found no information on how well the first and last firmware versions perform in terms of GPU.
To disconnect the battery connector you need to place a spudger beneath and lift up. It is the same method used for the connectors of fans, temperature sensors, and the battery in a MacBook Pro 2006/7/8.
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
cmoegele said:
Thank you for this Tutorial.
Do you know a method to change language in CWM ?
Best regards
Click to expand...
Click to collapse
Unfortunately I haven't found anything that would suggest that you can. The best I could do is have one of my friends tell me what each section states, but that may be a long while from now.
The menus I have figured out and listed are the most necessary. The others are just icing I suppose.
Unable to switch it back on
Hi,
first of all, please excuse me if this is not exactly related to this post, but I see there is not much discussion around this device so I figured this would be an okayish place to ask.
I got my ZTE U950 just today, put my SIM and MicroSD cards in it, turned it on, all OK. I played with it for a while, changed the language into English, tried some apps, deleted lots of default installed Chinese apps (such as Baidu, QQ, Baidu maps, etc).
I run Debian on my machine, so this guide wasn't working for me. However, I tried to run Genotools on Wine and followed the first steps, but no pop-up showed in my phone and I decided that probably Wine wasn't forwarding the USB dev properly. The phone kept on working normally for a while, I even recieved a phone call.
Then I turned it off just to switch the SIM back to my old phone and, after that, I haven't been able to switch the ZTE back on again. At first I thought it'd be the battery running out (although it reported 50% left while it was on), but I've had it connected for about 30 minutes now and I still can't turn it on...
Do you guys know if there is something I can try?
Thanks a lot and excuse me again if I posted in the wrong place... (and if I have, could you please point out where should I post it?)
Bernat.
EDIT: Today I woke up, I pressed the power button and... surprise! It just worked!
No Popup on phone
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
raoyasir said:
Hello
I have tried to follow the steps as you have mentioned.
Root>2nd Button>Popup>ok
But nothing appeared on my phone.
Can you guide me what should I do.
I have USB debugging and Unknown Source checked but no popup appeared on my phone.
Click to expand...
Click to collapse
Do you have the usb-drivers installed ? (doublechek in device manager for windows ) Sometimes Win7-64 or Firewalls block uncertified drivers to install correctly. For 7-64 you can press F8 during early boot and choose "force unsigned drivers" or something simiar. On linux you should go through an Android adb installation howto, to correctly get debuginterface running.
Once you have installed chinese recover you can install some prerooted images from the hungarion or chinese sites.
br
cm
PS: has someone skills for implementing other languages or removing the chinese letters on some menues ?
I just bought ZTE V985 which is also tegra 3 device. Can anyone help how to root it?
Sent from my HTC Desire using xda app-developers app
how to root zte v985
someone please tell us how to root zte v985.
3G
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
alz_uk said:
someone please tell us how to root zte v985.
Click to expand...
Click to collapse
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
suunnittelija said:
I was able to root my ZTE V985 couple days ago. Download root installation package from:
http://pan.baidu.com/share/link?shareid=68344&uk=2753639880
1. Install ZTE USB driver first: Goto Settings -Developer options - enable Driver CDROM. Connect your phone to the computer and install driver package from ZTE. 985root.7z package has also ZTE USB driver but it didn't work on my Win 7, so I installed drivers from phone.
2. Turn off CDROM mode and enable USB debugging mode and Unknown sources
3. Unzip 985root.7z file to any folder
4. Run xxxroot.bat and command window appears. Script will stop and ask you to press any key (in Chinese)
5. Check that your phone is connected and press any key. Script will upload files to your phone
6. There will be popup window on your phone. Click Restore my data
7. Phone will then boot up but keep it connected to PC and wait until it is fully booted
8. if there's nothing going on in command window, press any key and command window closes. If your are rooted, you have SuperUser app
Original instructions from here:
http://bbs.gfan.com/android-5226211-1-1.html
And Google translation:
http://translate.google.com/transla...=http://bbs.gfan.com/android-5226211-1-1.html
Click to expand...
Click to collapse
Thank you very much my freind, you are a kind and intelligent person.
---------- Post added at 12:31 AM ---------- Previous post was at 12:27 AM ----------
nabax said:
Hi guys,
does anybody know if/how it is possible to connect to a 3G network with this terminal? In the specs it says it can only connect to Chinese 3G networks, so I'd like to know whether this is a software or a hardware restriction.
If it's a hardware one, I guess the solution must be pretty complex...
Cheers!
Click to expand...
Click to collapse
Hahaha you silly billy, i know whats happened to you! You got the ZTE U985 instead of the V985. The ZTE U985 only supports TD-SCDMA 3g network which is CHINA only. You should have bought the ZTE V985 which is WCDMA 800/1900/2100 mhz which supports western 3G networks. LMFAO. I feel sorry for you fella.
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
cmoegele said:
Where did you buy the v985 ? I only can find offers from 350-400$ and for this pricing I can´t find any real advantages buying a chinese phone , there is also no DualSim,and normally very limited languages ( chinese cwm?),....
Click to expand...
Click to collapse
Dont get it wrong my mate the zte v985 is a beast of a phone + a smart piece of hardware. Only downfall i see is the limited rom/root/customization support since its new (october 2012)
Reasons why you should purchase the zte v985:
1. really supports APP2SD (install apps to external sd so you never run out of space and you dont have to throw away your phone when internal memory of 4GB gets full like most other android phones)
2. quad core cpu + 12 core NVIDIA gpu (theres websites full of games made only for this cpu + gpu)
3. USB OTG (using your superfast cpu and gpu together with usb otg you can turn your phone into an high class gaming system using two usb game controllers playing arcade roms and 3d games ON YOUR PHONE!). This is an awesome feature that not all phones support even some high performance quad core phones dont have this function.
4. 720P HD screen + 1080P HD Playback/Recording
5. Full MHL support (usb to hdmi)
6. Cheapest all round high performance quad core. Awesome price (£190) for a phone compared to other quad core high performance phones e.g galaxy note 2 @ £500
NOTE: if you would like to buy this phone for the price mentioned leave a message with your email or contact me i know a seller in china.
NOTE: Or you could wait another month or two and buy the new mtk 6589 quad core phones such as the UMI X2 which is quad core, DUAL SIM, usb otg, 2GB RAM, 32GB ROM and dirt cheap (£200!!!)
I get my ZTE V985 today through the post, cant wait till i get it!
Recovery in english language?
Hi
Anyone found Recovery in English language?
Google play
I can install google play, but if i open it, it immediatly shuts down again...
Any idea's ?
cwm zte u950 test 1 (build, 28 nov 2012) by me.
===================================
(cwm-u950-6.0.2.3-permanent)
-------------------------------------------
CRC32 : D2CD4005
MD5 : A1C6B72375B2E79100AA9BE52D0F30C2
SHA-1 : C7B3165D1E1F7463BFF16C0DE7747E6B3EC3F807
xxx.media*fire.com/download.php?0411sb2m1kkyrv4
(cwm-u950-6.0.2.3-temporary)
------------------------------------------
CRC32 : 830121A8
MD5 : 8239E70CB81548FE4427C505A5184749
SHA-1 : 9CF9CED3EC6CA2B79AE174E03A423435BB0FFFAC
xxx.media*fire.com/download.php?m90c896m17u0o9p
sorry.. i still need to learn..
please report cwm zte u950 test 1 (build, 28 nov 2012).
suunnittelija said:
I bought it from fastcardtech.com, only 275 USD with free delivery.
From hardware specs point of view this is a really good phone, fast as my Asus TF700T tab with Tegra 3. It also supports WCDMA 900/2100MHz which are the most used 3G frequencies in EU. It does have only English and Chinese languages, but I used MoreLocale 2 to get more choices. More Locale does not change system language (like settings, caller app etc) so those will remain in English, but for example now other apps like Google play, Chrome etc. supports the language you have chosen in MoreLocale.
Sent from my ZTE V985 using xda app-developers app
Click to expand...
Click to collapse
ZTE Grand Era V985 Recovery (support English)download link: pan.baidu.com/share/link?shareid=372147&uk=973327405
If you have any problems,please sent a email to me ,my email address is '[email protected]' ,i can help root your ZTE Grand Era V985,and install the recovery,the recovery includes English language.At last,the Android 4.2 for V985 will coming soon,maybe in April,if anyone need ,i will send to you.Thank you.
i found twrp for the zte u950 in english in this package, it is in the folder recovery_3 :good:
what do you think? is it possible to make the zt3 u980 to work with european 3g network? i thought to flash the baseband from zte v985 on the zte u950... do you think its possible?
More stuff in English
hey Heatshiver...u can add these in your OP
I found some roms HERE for U950 which support english language..and atleast instructions are in english
2 or 3 of them are based on MIUI ...
I've tried the 1st one...works perfectly so didn't flash others
Extracted img file of twrp recovery (english) from the package provided by superpfpf - attached in the post
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Unlock OEM in developer mode and try it whit Kingroot
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs
Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(