Related
June 02, 2015
Edit: If anyone has a link to the stock ROM for the Ascend G7, please let me know. I would love to make a custom ROM that doesn't take up 98% of all resources 99% of the time.
Hello everyone.
Before I get started, here is everything you need to know about this post.
- This root works as of June 29, 2015
- This is a rooting process for the Huawei Ascend G7
- I did not make this, so please consider supporting all mentioned sources
- I am a new user to XDA, but I've been developing for over a decade. I will regularly check this post if enough people who view it have questions
There are two parts to this process.
First, we unlock the bootloader
Second, we flash a recovery, and subsequently, SU (root)
Let's get started. This will take at least 16 hours. User interaction 5 minutes, and about a 16 hour wait for an email response from Huawei.
Also, I have a new account, so I cannot post links. So please bear with me. I will upload photos in as best order as I can.
Before we get started, please note that your phone will factory reset in this process.
First thing's first. The Ascend G7 requires an unlocked bootloader, before any root can take place. This is obviously temporary, until someone finds a circumvention. But for now, this is how this needs to be done.
Send an email to [email protected], with this format:
Dear Sir/Madam
Please may I request the bootloader unlock code for my Huawei Ascend G7?
Here are some Details:
Serial Number: (Found under Settings --> About phone --> Status)
IMEI: (Found under Settings --> About phone --> Status)
Baseband version: (Found under Settings --> About phone)
Please could you send me the code directly, as I cannot access the product ID on my device.
Thank You
Your name
This part is important. Sometimes, they do not even reply to your email(s). It is recommended - nay, required - for you to put "URGENT" in the subject field of the email. Something along the lines of "URGENT Request Bootloader Unlock Code." It would also be best if you mark your email as urgent/high priority, as well.
Meanwhile, while you wait for the email from them with your unlock code, (expect it to arrive the day after), download the Android SDK and the Java JDK, if you haven't already. What you need most are the SDK tools, which you can also download by typing in "SDK tools android" in Google and finding a download for the stand-alone tools.
Make sure Android Studio is updated, if you already have it. To make sure you have everything you need, open up command prompt in platform-tools, by holding shift and right clicking somewhere on the white, in the folder, (explained in attached picture).
Then, plug in your phone. Make sure USB debugging is enabled. To do so, go to Settings --> About phone --> Tap "Build Number" 7 times in a row. Then go back, and you will see "Developer options." Click on that, and enable USB debugging. Also, this optional, but I like to enable the "Stay Awake" function.
Make sure to accept any prompts that your phone will ask.
Then, go to the command prompt and type in "adb devices" without the quotations.
If you've done everything correctly so far, you should see something similar to the attached command prompt image file.
If everything checks out, let's proceed. If not, post below, and I, or fellow XDA users, will help you out.
Proceed to type in, "adb reboot bootloader" without the quotations, into the command prompt window that you opened. Your Ascend G7 should reboot into fastboot, where you will see something like the attached picture below, of the bootloader screen.
Except, it will say Phone Locked instead of Phone Unlocked.
Now, go back to your command line, and type in "fastboot reboot," to have access to your phone and its functions, while you wait for the email from Huawei.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Everything below this line should be done AFTER receiving a reply email from Huawei, with your unlock code.
Now, download the "PHILZ-TOUCH-6.rar" file. I cannot attach it here because it exceed file size limit. No virus, no surveys, here's the link, https/goo.gl/sxPv7I. Just add a colon and a forward slash after https. It is not a virus, in case your firewall or antivirus software brings up red flags. I will post the whole ZIP that I've downloaded from another website. There's a bunch of redundant elements in the folder, but just in case you know what you're doing and might need the tools, I'll keep them there. But all you will need are 2 things from the folder. They're mentioned next.
Go to where you extracted PHILZ to, and hold shift and right click and open a command window in that directory, and type in "adb devices" one more time to make sure your device is listed and connected. Then, type in "adb reboot bootloader," give it a second, and then when fastboot loads up, type in,
fastboot oem unlock 123456789123
Replace "123456789123" with the unlock code provided to you from the Huawei email. Give it a second, and then you should be good. It should now say "Phone Unlocked" in red. Now, type
"fastboot reboot"
in the command line (that was opened in the PHILZ folder), without quotations. Then type,
adb reboot bootloader, one more time, and then,
Navigate to the PHILZ folder, and run "install-windows.bat" as administrator, if using Windows.
If using Linux, run "Install-Linux.sh," and if using a Mac, run "Install-Max.sh"
Now, in CMD type,
fastboot boot recovery.img
Then, again type in
fastboot reboot
Your phone will reboot.
`````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````````
Aaaaaaand that's it! You should now be rooted. I recommend going to play store, and downloading a Root Checker to ascertain root access.
The last picture, where it says I have root access now, is a program called Root Genius. It's a one click tool to root any android device - obviously except the Ascend G7, (knowing my luck). But it does work as a root checker as well, if you want to ascertain root access. You can also download Root Checker from the play store; works more or less the same way.
Any questions, feel free to ask. Re-reading this, I could see if the instructions bring confusion to some. I will be glad to clarify any questions.
Works
Root confirmed G7-L01
some point that I did not understood
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) open up command prompt in platform-tools
what is platform-tools? A specific folder? I was not able to find it
2) if I open the command prompt from any forlder using the shift+right button as you said and then write adb devices I get this message:
'adb' is not recognized as in internal or external command operable progrma or batch file. What should I do?
3) when I connect the phone by usb cable, should I do something more (like enabling device file manager, pc suite or other options) or just connect it in charge only mode?
thank you for your time!
and... by the way, I'm really impressed that I got the anwer from Huawei with the code, that's really cool! Thank you!!
---------- Post added at 04:09 PM ---------- Previous post was at 03:19 PM ----------
I found the platform-tools folder, now if I type adb devices from a prompt open from that folder I don't get the error message anymore, but I get nothing, just the flashing prompt line (the huawei phone is on and usb connected to pc)
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Frankleoni said:
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"?
Click to expand...
Click to collapse
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
<device offline>
Frankleoni said:
dear wertywhy,
your guide is really well done, but there are some points not clear to me
1) I had to install hi-suite to let the command adb work (before that adb was not finding the phone)
2) the file names of adb inside PHILZ_TOUCH is adb-windows and fastboot is fastboot-windows
3) when I input the command adb-windows devices inside the prompt inside the PHILZ folder the result is device offline, I could unlock the phone running the command from platform-tools directory (phone is unlocked now) but I can't run the command to root the phone until I have this "device offline"
Point 1 and 2 are not problem, just something that happened to me, but point 3 is stopping me, any idea how to solve point 3?
Click to expand...
Click to collapse
Hi Frank,
Let's troubleshoot,
If it lists your device as offline, open up cmd (Run --> cmd), and type in,
taskkill /f /im adb.exe
Then, restart your G7; when it boots up, turn off and then on USB debugging, then find PHILZ, and retry point 3. If device is still offline, please let me know. The issue sounds like it's within the phone, not within ADB.
Alternatively, if that doesn't work, please delete PHILZ off your computer, and wherever it says "PHILZ" in my guide, replace it with the attached folder, (attached with this reply).
Cheers
PS, please make sure to check that your phone is not only in USB debugging mode, but that you've approved/allowed your computer access to your phone, (a prompt will show up on the Ascend G7 that asks you whether or not you trust your PC). And also make sure your phone isn't just set to "charge" when plugged in - activate/select MTP when you connect your phone to computer.
<device offline>
lume12 said:
I'm having the same problem. I tried toggling usb debugging off and back on, tried another usb port and another PC (WIN 7 and 8) but none of that helped.
Click to expand...
Click to collapse
Please refer to my reply to Frankleoni below.
Thank you for replying chy_vak,
I tried your solution in both the PHILZ folder and the new folder you attached. The device shows offline in both of them. However in the build-tools folder it shows online. The command line taskkill /f /im adb.exe terminated adb but the device still shows offline. I did everything in the exact order you wrote.
offline
search Kings Root via Google Chrome, install it and run it Easy and without chat with Huawei support
Kingroot Works like a charm !
@chy_vak, Thank you for your Work. 1st Part works great. 2nd Part went wrong, i dunno why i`ve tried every thing. I hate this Kingroot think, don`t touch it you never will leave it.
I have connect my G7 because unlock works. When i use CMD from Adb Tool it is connected, when i use command prompt from Philz he cant see and find the mobile?? Something for you absolute clearly, isn`t for other. Sry cant do screenshot with notebook and Win 10. have fun
Another Working Method to Root Huawei Ascend G7-L01/L03
Greetings!
I got an Ascend G7 Recently and I needed to Root it as soon as I got it. That's why I kind of broke my head looking for the current methods to do it. I found this one very promising so I started working. I followed the steps that were given to us one by one. Everything was alright until I tried to install the Windos-Installer.bat as administrator, I tried to many ways to this method work, but as much as I tried, I couldn't go with it, that's why I started working for 11 hours until I got it. This Worked for me, and I want to share it with you.
Please read the following notes before you start by rooting your device:
-As usually, do it at your own risk, I'm not responsable of any brick, or issue that damaged your device.
-This Method is working great on Windows 10
-This Method is working at 04/08/2015
-This Method, was tried by me, the directions I give to you, are based on my work by rooting my device and my experience, the software and files included were made and posted by someone else including the person who wrote this post: http://forum.xda-developers.com/gen...-confirmed-t3125621/post61122491#post61122491
-You can find screenshots of the procedure below
-You will need a microSD
-I strongly recommend you to have at least 80% of battery to avoid risks of bricks
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here begins the directions:
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
After a while (Could take between 15 minutes and 16 hours depending on their time) A Huawei worker will answer you something like this:
Dear Customer,
Thank you for supporting Huawei device. My working number is ****. Your unlock code :************** , please keeping your unlock code properly.Thank you!
Huawei Terminal Company limited
1.1.- (OPTIONAL) As we are going to unlock the bootloader, we are going to make a factory reset, so I strongly recomend you to make a backup with the official huawei backup app in order to restore our settings, apps, and files.
1.2.- Once Again, as has been said, you will need to download the whole Android suite (Android Studio) the last version, update your java version, and download the last drivers for your device (A good way to do the last is by installing the HiSuite of Huawei).
1.3.- You need to activate the debug mode. You can find it in: Configuration->Developer Options->USB Debug (If you dont have the Developer options enabled, you have to go to Configuration->About the phone->Compilation And tap this last one 7 times)
2.- Download the .rar a the end of the page and extract it where you want, includes everything we are going to need. [You must put the file ''superuser.zip'' on your microSD (In the root of the microSD)]. After Downloading it, you must open a cmd window, running it as administrator. After that you will write:
cd (Here you should paste the ubication of your extracted File Ex: C:\Users\Josh\Downloads\Root Ascend G7)
Now you are in this ubication that includes adb. Write:
adb devices
You should see: List of devices attached, a code and the word device (There is a capture below). If you do, we can proceed.
3.- Type :
adb reboot bootloader
It should load a white page with the Android pet and the words FASTBOOT&RESCUE MODE Below there is the phrase ''PHONE LOCKED'' in color. Now type:
fastboot oem unlock *********** (The code Huawei gave to you)
Now your phone will make a factory reset. You will see how it reboots by itself and back to the default settings. You will need to activate the debug USB mode again. By this point its supposed your bootloader is now unlocked, to probe it, we will type again:
adb devices (To check it is correctly plugged)
Then we will type:
adb reboot bootloader
And now at the end of the page it should say: ''PHONE UNLOCKED''. If you do, we can proceed.
4.- At this point, you have two options: You can replace your stock recovery mode by a ClockWorkMod Recovery (I strongly recomend you to do that) or you can just ROOT the phone whithout replacing your stock recovery.
If you decided by replacing your stock recovery follow the next directions: We still have our CMD window opened and running adb while the phone it is on the bootloader mode. So now what you have to do it's to type:
fastboot flash recovery recoveryP.img (CMD will work and show a few commands)
And after that type:
fastboot reboot
Your phone will reboot again normally and we can proceed.
If you decided not to replace your stock recovery instead of typing ''fastboot flash recovery recoveryP.img'' you have to type:
fastboot boot recoveryP.img (This will send you directly to CWM recovery)
5.- You must acces to CWM Recovery.
If you installed it on your phone, turn off your device and then press the power button and vol+ until the Huawei logo appears, you should be in the recovery mode by now.
If you didn't install it, you already are in CWM recovery.
6.- With the vol and power buttons or the touch buttons at the end you should be able to navigate on the recovery. We go to:
Advanced Functions->Re-root System (SuperSu)->Yes-Apply SuperSu (You will see a few code at the end of the screen)
7.- Without leaving the recovery mode, go to the main screen and now we go to:
Install Zip->Choose zip from /sdcard->superuser.zip (The one that you previously putted on your microSD)->Yes-Install superuser.zip
(You will see again a few code at the end of the page) We go back to the main screen and Select:
Reboot System now
8.- It's supposed we are ROOT now. At first you will see the ''superuser'' app installed. To probe that works, Install ''android-terminal-emulator-1-0-70-multi-android.apk'' that it is included on the folder ''Terminal'' form the file you downloaded. Now open a new terminal window and type
su (If everything worked, superuser will ask for permissions)
8.1.- Restore your data with the Huawei Backup App
And that is all we have superuser acces now. If you have any question or issue let me know and I will help you.
https://mega.co.nz/#!Al9FxDBY!QHkljnnIbjURX01A59tJPNkAVQd3LbKTqRJHD_nNxrs
Thank you!
Cant boot into recovery
Hey guys so i tried following this procedure but it never works :/ if i flash the custom recovery and try boot into it, the phone directly goes to fastboot and rescue mood so cant boot into recovery, not even the stock recovery. if i try directly booting into the custom recovery it says dtb not found :/ can someone please help me?
the model is G7-L11 and the bootloader is unlocked
Engineer Mode Huawei Ascend G7 L03
Huawei Ascend G7 L03
Hi,
I have tried every thing to go into Engineer Mode.... Even Mobile Uncle Does not do that!
Please some one Help....
Huawei Ascend G7 L03
thanks for the translated philz touch
Hello everyone, I have a big problem with a Huawei G7. I did Philz Touch and Root. How can I go back to stock rom?
I've emailed Huawei 3 times now, left a week in between emails, and still haven't received my unlock code. Has anyone else had this issue?
Thanks
1.- As has been said, you will need to unlock your device bootloader in order to root your phone. So as they said, you will need to write an email to Huawei. The mail you will send should look like this:
To: [email protected],
[email protected]
Subject: (URGENT) Unlock Bootloader
Model: Huawei G7-L03/L01 (Depends on your version)
Serial Number: (The one that comes in your Huawei's box)
IMEI: (You can get it on your box or in the info included on Configuration->About the phone->State
Product ID: (You can get it by typing on the Dial the next code: *#*#1357946#*#*)
I appreciate your concern of reading this. Waiting for a response.
Sincerely: (Your name)
Does anyone have a good tutorial on how to flash twrp on the phone ? I've tried different things but it never works
any other method exept this email method? they wont answer me.
Dell Venue 7 BOOT PROBLEM
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
ManXXXX said:
Hello,
I replaced frameworks-res.apk, and others, for change design, but now i can't boot my tab ! , it just booting booting booting booting and booting, factory reset not helped?, can you help me please?
It's Dell Venue 7 3730
Click to expand...
Click to collapse
You need to flash again the stock rom, the factory reset won't work.
You can found it here http://forum.xda-developers.com/showpost.php?p=51090040&postcount=2 and flashing through fastboot
I don't know what frameworks-res.apk you used, but maybe you forgot set the right permissions, or maybe you took the files for other device.
DL VN 7
Is there some tutorial for flash with fastboot??, i never did it, and i don't want destroy some other..
Go here to Dell's opensource site.. http://opensource.dell.com/releases/...loper-edition/
Link
No working link
ManXXXX said:
No working link
Click to expand...
Click to collapse
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
ADB Driver
Isrks said:
first
sorry for the late reply.
In the dell's opensource page there aren't files for the 3730 (i don't know why)
but, may be i'm wrong, there aren't tutorials for flashing in fastboot, i only found posts in xda's dell venue general forum.
i'll write here a guide if you still without founding a tutorial and for any others if found this post
you need:
intel usb drivershttps://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices , read the instruccions if you are in windows 8 (i'm on win7 so i cannot tell you if is the same method or not)
The tools for fastboot (there are in a folder called "google") is a little confused so better download @social-design-concepts miKIT_BATCH HERE (before continue let's say thanks to @social-design-concepts for his useful tool that also works for root ),extract wherever you want in your computer.
the files to flash HEREdownload the package for your device and once donwloaded extract where you want in your computer
NOW FOR FLASH
1.-
Install the intel android usb drivers, if you did this before, skip
2.-
Open the myKIT_BATCH folder and run the "runme.bat" file, then type ACCEPT, after that type 2 and press "enter" (the option 1 is for update the driver, in myKIT_BATCH's post 1 is explained) the font should be red.
3.-
boot into fastboot (press button "power" and button "volume down" at the same time) your tablet's screen will display a blue android with gears inside and below it the "droidboot" text and your device info in your device's top|left screen corner , if yes connect your tablet to pc to recognize it (if is the first time).
4.- Open a command window
after the pc recognizes your tablet unplug and plug again the usb cable, should be faster the recognicion this time.
Then in myKIT_BATCH window press "enter" to refresh, the font will become green and will display your device's info, if is going fine in the window type 4 and press "enter", will appear another window.
IF everything still going fine in the new command window type:
Code:
fastboot devices
will display your device's info
5.- let's start with fastboot
BUT first ENSURE THAT THE BATTERY HAVE A CONSIDERABLE CHARGED LEVEL
Unfortunately i don't know what happens if the tablet power off when flashing and if fastboot will work fine after so check your battery charge first
i need to tell you that the 1-4 steps are the most difficult steps (you should have at this time the rom downloaded and extracted only extract the downloaded package (the .7z file)
after this explained so let's start.
5.1.- WIPING
fastboot have some wipe commands so i will explain the 2 that i used:
Code:
fastboot erase cache
This code explains itself, you can try this code to verify that your device is connected
Code:
fastboot erase data
easy to use but powerful, this will erase app's data and also your internal storage (the 11GB that the tablet have to store files), unfortunately i used this without know and i lost 8GB of files
5.2.- NOW TO FLASH
works almost equal with the wipping commands so it's easy to explain.
let's start with system
for a easy explain you ned to open a window where the rom's files are stored in your pc and in the command shell type "fastboot flash system" and after that drag the system file (system.img.tar.gz) to the command window after dragging the file will appear in the command window the full path of the file
I.E i have a dell venue 8 3830 and i want to flash the jellybean 4.2.2 stock rom so i downloaded the Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG and extract this in F:\VENUE 8 3830\stock rom folder so after type the command and drag and drop the system file in my command window will display this:
Code:
fastboot flash system F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.system.img.gz
after this the command press "enter" and you don't need to do nothing (maybe your window will turn off and maybe you try to turn on but will keep off, don't worry only let fininsh) the fastboot program will start to prepare the file for upload to the tablet and after that to flash.
this will finish in 1-2 minutes.
NOW THE BOOT.IMG
is the same way than system but faster.
after finishing flashing system (when the window diplays the elapsed time) type: "fastboot flash boot" and drag and drop the boot.img file in the command window
I.E. in my device will be like this:
Code:
fastboot flash boot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.boot.img
press "enter" and will do the same like system prepare,upload and flash the file.
there are in the download package more file but only with BOOT and SYSTEM flashed your tab should boot
but if you want to flash the other images you need to type
for recovery:
Code:
fastboot flash recovery F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.recovery.img
and for fastboot:
Code:
fastboot flash fastboot F:\VENUE 3830\stock rom\VENUE_8_WIFI_JB4.2.2v1.42.fastboot.img
for my example, for you will be change a little
thanks to all who read and understand this guide, bad english
you are free to comment this if i mistake
Click to expand...
Click to collapse
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
ManXXXX said:
When i installing the driver, always: Install failed, i have Windows 10 and i added language code
Click to expand...
Click to collapse
I found this around here, is for windows 8 but maybe useful for Windows 10
https://software.intel.com/en-us/android/articles/how-to-install-intel-usb-driver-for-android-devices-on-windows-8
ADB Driver
Nah nah this, i think ADB driver.
ManXXXX said:
Nah nah this, i think ADB driver.
Click to expand...
Click to collapse
unfortunately i don't have a computer with windows 10 so i can't solve easily.
i found this googling, so with a little of faith :fingers-crossed: , is the same error than yours http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opoit's for the OPO, but is about the same "intalling adb driver", so could work
in a dessesperate attempt, you can use the update usb drivers in "myKit_BATCH" typing "1" after typyng "ACCEPT"
I fixed it with 15 seconds installer!, i gng try to fix tablet
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
ManXXXX said:
But i found next problem, after connect tab to PC, just UNKNOWN, and tab is not showing in mykit
Click to expand...
Click to collapse
Ahh that's add driver not recognize your tablet, I suppose that you connect in fastboot mode,
Try using the option of update the adb driver in Mykit_BATCH, you don't lose nothing trying.
Other option is trying the dell's method http://opensource.dell.com/releases/Venue_8_3830_CloverTrail_plus/developer-edition/Download the pdf file and read the instructions from page 2 to page 9 if still not working
here is the sdk tools for windows that the pdf wants
I downloaded SDK tools, i installed Google usb driver, because it say not installed, when it was installing it said: Disable adb driver, ineffectual, error code -1, but after install it work good, so i will test with this, when no i will try another way, that u wrote here
Finally, tried method, no work, finally, update ADB no working for me, cuz installation always fail, next one DELL method, working but i found problem, dell wrote update driver via google extra with codes, BUT
My first code: USB\VID_413C&PID_B119&REV_????, ????, i think there is something wrong
My second code: USB\VID_413C&PID_B119, i think this one is alright, but then up
Finally with dell next page i'm in!, but my kit no working, in every command shut down, so i using windows cmd, it working too
Mhm bruh, no i'm in flash system, sending 'system' awesome, but it's more than 2 minutes , when it will work, omg u r awesome
Bruh, yay, i did it, thq u r master <33
ManXXXX said:
Bruh, yay, i did it, thq u r master <33
Click to expand...
Click to collapse
Are you telling that the dell method works?
The good new is that your tablet is back (with some problems in the way but work, ). after all now you know how to flash through fastboot. If anyelse goes wrong again, you know what to do
NOTE: Maybe your want to replace the framework-res again, but only will work if is for your device. So i recomend that you modify your stock framework-res by yourself (you can use images or xmls from other sources to your framework-res, this should be safer) using apktool manually or a program (there are some of them in xda, choose your favorite )
Yay 50% of dell method worked, just 50% because Dell have tutorial for setting up ADB service, after it i used your tut, thanks, and believe me i will not test it NEVER again.
<disclaimer> I take no credit for anything in this guide. A BIG Thanks goes out to @tennear, @Unjustified Dev, @DrakenFX and @Starvirus. They are the ones who figured out the process described below and provided the excellent LineageOS 14.1 ROM. I just wrote this all-in-one-guide because I think the information is way too cluttered and spread over these forums.</disclamer>
<disclaimer> If you're not 100% sure what you're about to do, please first scroll down to the bottom of this post to see a list of DON'T's, a few things you SHOULD ABSOLUTELY NOT DO if you want to keep using your device.</disclaimer>
After having had quite some phones (Moto Defy +, Oneplus One, Nexus 5x,...) and having flashed a lot of ROMs on them, I thought I had quite some experience in these matters. Alas. Unlike Oneplus, ZTE would rather not have users fiddling with their devices. There are also three versions of the Axon 7 called the A2017 (China), A2017G (Global) and A2017U (USA), each with some minute differences from the others. This makes unlocking BL, flashing a custom recovery and installing custom ROMs not so easy on this device.
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution. There's always a tiny chance this process bricks your device. By following this guide, you will lose all your data on your internal memory. Please backup before proceeding. The data on your SD card should be safe.
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4UVMBVpYdVwcnlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
15) Type "Fastboot oem unlock" and hit enter
16) Follow the instructions on your phone and use the volume and power buttons to confirm you want to unlock your bootloader
17) Boot into TWRP by holding both power and volume up button
18) Type "Wipe" and choose "Format Data"
NOTE: If you get a permissions denied issue, try doing these steps while your device is in TWRP.
C) Update bootstack, Install LineageOS 14.1 and update your TWRP to latest version
Q: Why do I need Lineage OS 14.1?
A: It's a custom ROM that's a lot smoother than any available stock rom for any of the Axon 7 versions. Aside from an audio bug (the speakers make a rattling noise when the volume is turned higher than 80-90%) it's perfect. You can however find quite some other decent ROMS here.
Q: Why do I need the latest TWRP?
A: Tenfar's signed TWRP version is the only one that will be accepted by a locked phone, so you need to flash that version first to unlock your bootloader. You should however not use it for backing up and restoring, since it contains fatal flaws that can lead to bricking your phone. Update it using the steps below.
1) Download the latest unofficial Lineage OS 14.1 ROM from here: https://www.androidfilehost.com/?fid=457095661767134540
2) Download the A2017G Nougat bootstack from here: https://www.androidfilehost.com/?fid=673368273298930583 (A2017U users: your bootstack is here
3) Download the latest TWRP .img from here: https://build.nethunter.com/twrp/zte/twrp-3.0.4-1-ailsa_ii.img
4) Download a Google Apps version from here: http://opengapps.org/?arch=arm64&api=7.1/ .You must use an ARM64 file since that is the type of the CPU in the Axon 7. You must use 7.1 Gapps since that's the android version Lineage OS 14.1. is based on. Which one you choose is up to you, the "smaller" you go the less google apps will be installed as stock. You can always download the ones you miss via the play store after having installed LineageOS
5) Put the bootstack, the LineageOS and the chosen Gapps zips on your MicroSD card. Also put the TWRP.img on there
6) Flash the A2017G Nougat bootstack: Flash -> select the bootstack file on the microSD card
7) Flash LineageOS 14.1, then flash the Gapps zip file (again via TWRP)
8) Update your TWRP recovery by choosing "Install" and then clicking "Install Image" (bottom right) and selecting the TWRP .img file
9) Wipe dalvik, cache and data
10) Reboot
11) Enjoy your phone
In the unlikely case that you're greeted by a screen that asks you for a password because your system is somehow encrypted, reboot to TWRP and format your data partition to ext4 instead of f2fs (wipe -> advanced)
If your phone doesn't pop up as QUSB_BULK in EDL, you probably installed the driver that came with the phone. The device will pop up below Ports (COM & LPT) on Device Manager as Qualcomm something-something USB device. Uninstall that driver and reinstall winUSB drivers through Zadig.
If axon7tool fails with a what() and STD-exception and whatnot - if you installed the Zadig driver
Go to Device Manager, right click QUSB__BULK and Uninstall, then use the "adb reboot edl" command. Install the winUSB driver via Zadig. Reboot the phone by holding the power button about 10 seconds. Enter the command adb reboot edl again. Enter "axon7tool -r gpt boot recovery" in command.
If LOS refuses to install and you get the error axon7.verify_trustzone, install the universal bootloader (A2017X_B15_UniversalBootloader) before the N Modem.
So, the steps after you get access to TWRO are: 1) Install univ. BL (A2017X_B15_... .zip); 2) Install A2017G_N_modem.zip; 3) Install LOS14.1 zip; 4) Optionally, install Gapps; 5) Flash TWRP img
DON'T's:
- DO NOT use the signed TWRP (3.0.2) to backup or restore, it might brick your device
- DO NOT use this guide when you're on locked stock nougat, you need to downgrade to Marshmallow first
- DO NOT flash the wrong N bootstack. There's a different version for G and U devices
- DO NOT use this guide if you're on an A2017 (Chinese) device
- DO NOT unplug your cable from your PC or Axon while axon7tool is doing it's magic
- DO NOT make a mistake or typo, it can be fatal
- DO NOT try flashing random zips or files or formatting this and that when your device doesn't act according to the guide, post your issue instead
- DO NOT wipe anything else than Data, Dalvik and Cache in TWRP
ADDITIONAL STEPS:
- You can opt to root your device by flashing the latest SuperSU zip file
- You can opt to upgrade your unofficial LineageOS to the latest official version to receive weekly OTA updates
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
PsyJoe said:
First of all, thanks a lot for this guide! But I saw the TWRP image is actually for the A2017U version. I read in the forum that flashing this on the G-version could soft brick your phone.
So the question is, can I just flash this on my A2017G or is there even a version for the european model?
Click to expand...
Click to collapse
Both the aboot.img and the TWRP.img come from A2017U versions. For the moment, we do not know if there is any difference in the aboot file between A2017U and A2017G, but it's highly unlikely. @tennear sent me a tool to read the partitions on my A2017G and the result showed the partitions were the same as those in the A2017U model.
For the moment, there's only one TWRP version, made for A2017U, but it seems to work on all models. I quote tennear here:
tennear said:
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.
Click to expand...
Click to collapse
I suspect nearly all bricks on A2017G devices happen when A2017G users use tenfar's tool to unlock the BL. There's a lot of margin for error, for example with the whole COM ports shizzle. I advise not to go down that route. I also advise against trying to flash a rooted image through TWRP without unlocking your bootloader. Especially the command "axon7root.exe -p 4 -b -r" (flashing both boot.img and recovery.img at the same time) seems to kill specifically A2017G devices, that seem to have an extra "DFU" mode, which the A2017 and A2017U devices don't seem to have. A2017G devices get stuck in that mode and there's no way to get them out again.
TL;DR I think the risk isn't in flashing TWRP, but in flashing both boot and recovery at the same time, in the axon7root tool and in flashing a rooted stock rom without unlocking BL.
Thank you for this one thread guide. Should make it a lot easier.
Maybe you can add a few words and links to the B03 files that allow a downgrade from higher versions.
You have a typo in step 14), should be adb not ab
Controllerboy said:
30) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
Click to expand...
Click to collapse
Hi,
So, the backup can be restored, even if we cancel the password? Isn't the backup encrypted than?
Also, when we do swipe to agree to modify the system partition, is flashing SuperSU enough to gain root?
I'm not so much interested in installing a custom ROM (yet) but do want a safe way to gain root.
Thanks for your time and efford,
Edit: And all this is safe (step A) when on B08?
Cheers,
/Cacti
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Znuf said:
For twrp. It work fine, i just flash it on my 2017G and everything is good.
Just the lastest version of SuperSU didn't work. I use 2.65
Click to expand...
Click to collapse
Hi,
Thanks Znuf, I'll give it a go then.
Cheerz,
/Cacti
Controllerboy said:
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QDL_BULK"
16) In command, type "axon7tool -r gpt" and hit enter
Click to expand...
Click to collapse
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
le_cactus said:
*sigh*
My device manager (Win7 x64) lists my A2017G as QUSB_BULK (and no red led, just a black screen) after reboot to EDL and the axon7tool sais not connected.
Anyone knows whats up with that and how to solve that?
TIA,
Cheerz,
/Cacti
Click to expand...
Click to collapse
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Controllerboy said:
Hi
I don't think "QUSB_BULK" is bad, nor the lack of the red LED. When I did the process on my device it also showed different states at different attempts. I also had to try multiple times before axon7tool detected it.
If I were you, I would try to shut down your device completely, restart and try to boot to EDL again by using command "adb reboot edl". Alternatively, you could try removing your device from USB, then shutting it down, then holding both volume buttons while connecting it to your PC. Some G devices don't boot to EDL this way, but some do.
Just keep trying multiple times. Axon7tool doesn't work in any other mode than EDL, so you can't do any damage by using the tool in a wrong mode.
Click to expand...
Click to collapse
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
le_cactus said:
Thanks for the tips, I'll keep trying both methods.
Cheers,
/Cacti
Click to expand...
Click to collapse
I give up. Or at least at this computer.
Just to be sure, the QDL_BULK/QUSB__BULK, shoild it be an unknown device, one with a yellow exclamation mark? Or should I install a driver for it, and if so where do i find it? Google didn't help me out today
I'll try another pc, see if that does work.
Cheers,
/Cacti
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Hi,
i unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Thanks in advance
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Killerdog said:
I unlock my A2017G b06 with a slightly different way (Starvirus + draken FX TWRP) but i forgot to make a backup of stock rom before flash cm13.
Can you please make a clean one and share it.
Click to expand...
Click to collapse
Here's the file from DrakenFX: http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Flash bootstack only once, then flash BO6 stock ZIP. In my experience it doesn't replace TWRP with stock recovery, even when you're not rooted.
DeJe63 said:
Thanks for the description.
For your information. As you can see in tennears thread, you can short cut steps 16 - 22 to "axon7tool -r gpt recovery boot". This saves a lot of time and reboots.
Also, in the BL unlock steps, "wipe data" most commonly not enough. You need "format data".
Click to expand...
Click to collapse
Thanks for the tricks. I didn't know you could do all three commands at once. I'll update my guide.
Will this work for B08 or should I go all the way back to "B03 (or others)" ??
Tutorial looks good and simple, big thanks!
In general it works.
For some reason I was not able to update from DragenFX B06 to OTA B08. So I flashed stock recovery, stock B06, OTA B08 and just flashed back TWRP with axon7tool...and it worked. But it may be that I make some mistakes on the way to B08.
I was at BL unlock before.
Controllerboy said:
I think we've found your problem. There shouldn't be a yellow exclamation mark, your PC should really have drivers for your device. On my PC, this wasn't needed, but can you try to download and open Zadig?
When connected in EDL mode, search for your device by ticking the box "show all devices" (in one of the options dropout links in the top bar). You should see "QUSB_BULK" again. Select "WinUSB drivers" and install those. See if your PC recognises your device in EDL after doing that and try finding it with axon7tool. A reboot of your phone might be needed.
Click to expand...
Click to collapse
Hi,
That worked flawlessly on my Win7 box, but I have general USB problems on that device. Got timeouts a few times during the axon7tool -r commands, so I don't dare doing a axon7tool -w command on that machine. So I stepped over to my Win10 x64 machine, but that machine it keeps identifying it as a "Qualcomm HS-USB QDLoader 9008 (COM3) device." :crying: axon7tool -r gives my a "Failed to connect"
Thanks for the help though, much appreciated.
Cheers,
/Cacti
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Controllerboy said:
I would agree that it's not a wise idea to write a custom recovery to a phone when the connection between the phone and the PC is unstable.
However, that doesn't solve your problem. Seems like your PC decided to install some drivers that are incompatible with the axon7tool.
Did you already try to uninstall the Qualcomm drivers via device manager and reconnect your device to pc? Did you try Zadig on your win10 machine?
There's a guide on the internet to (temporarily) disable automatic driver installation for new USB devices. Perhaps you could do that and then use Zadig to install WinUSB?
To be honest, if that doesn't work I don't really know other things to try. Except visiting someone you know with a Win7 64bit PC, that is
Click to expand...
Click to collapse
Thanks for the tips. I'll let you know how things work out.
Cheers,
/cacti
Hi,
I have encountered a suddenly dead old device. It was working long time without an issue, but one day it does not start and just a logo is displayed. It was possible to turn off the device or enter the recovery menu. I have found more posts about repairing with some unofficial flash tools or using unofficial ROMs.
I was able to revive the device finally with success and using official tools only, so I would like to share the steps I have used, basically it is about downloading the official ROM from Acer site and flashing it with ADB:
1. You will need Windows computer, I was not able to make the Mac recognise the phone properly, but maybe it is somehow possible.
2. Download official Android 4.4.2 ROM from ACER site: https://www.acer.com/ac/en/GB/content/drivers
enter SNID (check the phone under cover), look in OS category and download, the ZIP file is ~700MB large, do not unzip.
Download also the Drivers and extract it.
No need to download unofficial ROMs or drivers for this phone I think.
3. Download android platform tools from https://developer.android.com/studio/releases/platform-tools and unpack to some directory
4. Install phone Drivers manually from Device manager, use Action/Add device command and navigate to INF in the driver folder.
5. Turn on the phone and star recovery mode (Vol down+Power).
6. Connect the charged device with USB cable.
7. Start cmd.exe and navigate to platform-tools directory, start "adb devices" command, your device should be listed.
If no device is listed, return to driver installation step.
8. start "adb reboot bootloader", phone will reboot, hint about flashing the ROM appears
9. start "adb sideload yourpathto/officialROM.zip
10. wait few minutes until the installation is finished, phone reboots and should work.
11. you are happy
Hey,
2 Years ago my E700 dropped down, since then it does not work anymore. It shows no reaction if i want to start the device.
Could something be broken?
Do you have an idea to fix it?
Hello!
I need to downgrade Android 10 to Android 9 on my Oppo F11 Pro. I've flashed many roms till now on other devices. This one is a bit *cough*
I have the .ozip file of the Android 9 rom, need to flash.
Default recovery mode of ColorOS doesnt work ofc, doesnt support downgrading.
After converting .ozip to .zip and extracting the files, SP Flash Tool or such tools arent able to get the files somehow They dont load it up, even not the scatter files.
So I think I should first unlock the bootloader, which I've been trying to today.
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Neon111 said:
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Click to expand...
Click to collapse
Don't mix up USB-driver and ADB-driver and/or Fastboot-driver: totally different drivers.
A USB-driver is a file that allows an USB hardware device to communicate with the operating system of a computer. This driver is implemented in all operating systems by default.
ADB-driver and/or Fastboot-driver is a “bridge” for Android developers / hackers to work out bugs in their Android applications and/or modify existing Android OS. This is done by connecting an Android device that runs the software through a PC, and feeding appropriate commands in its terminal.
Don't use any ADB-driver and/or Fastboot-driver as they are hundreds of times published on the WEB - and even here on XDA. Only make use of those drivers officially offered by your device's OEM/Carrier.
Comment withdrawn by author.
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Neon111 said:
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
Click to expand...
Click to collapse
Generally speaking, the serial number as reported by ADB will be different to Fastboot as determined by:
Manufacturer
Make and model of device in question
Android version
Fastboot, on the other hand, since there's no ADB loaded, instead, uses a rudimentary USB protocol tied in with Android's boot-loader, the serial number will be different.
EDIT:
Neon111 said:
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Click to expand...
Click to collapse
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
jwoegerbauer said:
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
Click to expand...
Click to collapse
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Neon111 said:
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Click to expand...
Click to collapse
Were you able to unlock your bootloader? I found various tutorials of extracting boot image from the ozip files. But Veterans are saying oppo doesn't let people unlock bootloader.