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.
Related
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.
Acer Predator 8 GT-810 system\etc backup please!
Make a backup folder etc
Do you still need it? I can send it you tomorrow or something like that.
p8tgames said:
Do you still need it? I can send it you tomorrow or something like that.
Click to expand...
Click to collapse
hey man if u able to send me a back up. Will that solve my problem ?
I made mistake to wipe everything in my phone and now i dont have OS ( i cant start my phone) i can only enter TWRP and thats all. i can use pc to transfer files to my phone and then install the files from there , so i wonder if any1 send me back up will that save me ???
i cand find anywhere OS for acer predator gt 810
there is official avolo zip on acers' page. flash that zip and you're safe
Flash archive corrupted
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware.
dvijetrecine said:
there is official avolo zip on acers' page. flash that zip and you're safe
Click to expand...
Click to collapse
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Alex_merser54 said:
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Click to expand...
Click to collapse
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
Code:
fastboot
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
Code:
fastboot devices
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
fastboot update <path to ROM .zip>
Click to expand...
Click to collapse
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
biorpg said:
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
Click to expand...
Click to collapse
Thank you, but I just entered EFI and load android.efi file, also I autorun it and reflash via recovery
IMPORTANT: It appearance that Huawei is no longer going to provide bootloader unlocking services for their devices. Because of this, this guide is of no use unless you can find a way to get a code or you just held onto the code.
Hello, this is a guide for unlocking the bootloader and rooting the Huawei Ascend XT. I am writing this because the current guide is not very well written and does not contain bootloader unlock instructions. This will be split into two parts: Part 1, unlocking the bootloader, and Part 2, rooting the phone.
PLEASE NOTE THAT FOLLOWING THESE INSTRUCTIONS WILL WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR AND DAMAGE DONE TO YOUR PHONE!
THINGS YOU WILL NEED:
1. A Huawei Ascend XT with at least 60% of battery left
2. A computer with adb drivers, fastboot drivers, and the Huawei USB drivers
3. A Micro-SD card for your backups (THIS IS VERY IMPORTANT! PLEASE MAKE BACKUPS!)
4. TWRP for this phone. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933 (credits to enigma2446)
5. The ZIP containing SuperSU. This can be found here: https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933
6. The SDK Platform Tools. These can be found on the android studio website.
PART 1: UNLOCKING THE BOOTLOADER1. Geting the Bootloader Unlock Code: You need to get your bootloader unlock code. You can get this by going to https://emui.huawei.com/en/plugin.php?id=unlock
(EDIT: It appears that this website is down. I have read that if you PM Huawei on Twitter or call them and provide all the details of your phone, they will give you a code. I have not tested this method, bit people have said it worked with the mate 10.) and signing into your Huawei ID. If you dont have one, create one. Then, follow the instructions given to you by Huawei to get the code.
2. Enabling the Enable OEM Unlock Option: To enable this option, you must enable developer options. To do this, go to Settings>About Phone and tap the Build number until it says "You are now a Developer". back out of About Phone, and go to Developer options. turn on "Enable OEM unlock" and press Enable.
3. Enable USB Debugging: While you are still in Developer options, enable the option 'USB debugging" and press OK.
4. Booting Into the Bootloader: once you have completed the first three steps, you can now boot into the bootloader. Connect your phone to your computer, and open the Platform Tools folder you should have downloaded and extracted. Shift-Right click, and press "Open Command Window Here" or "Open Powershell Window Here", depending on your version of windows. Once it is open, make sure your device is detected by typing "adb devices". If it displays your device, you are good to continue. If not, something is not set up right on your computer or phone. Once you verified that your phone is detected, type "adb reboot bootloader".
5. Unlocking the Bootloader: Once your phone has booted into the bootloader, you can now unlock the bootloader. YOUR PHONE WILL BE WIPED ONCE YOU TYPED THIS COMMAND. You can unlock it by typing "fastboot oem unlock <your bootloader unlock code>". Once it has finished, you can reboot your phone, and just run through the setup fast, because you will still have to wipe it again.
PART 2: ROOTING YOUR PHONE1. Move the TWRP image you downloaded (called
Xtrecovery) to your Platform Tools folder and rename it to "TWRP.img"
2. Insert Your Micro-SD Card
3. Move the SuperSU Zip you downloaded to the SD card
4. Re-Enable USB Debugging: Enable Developer options by going to Settings>About Phone and taping the Build number until it says "You are now a Developer". Back out of About Phone, and go to Developer options, and enable USB debugging, and press OK.
5. Boot Into the Bootloader: Type "adb reboot bootloader" into your open CMD window or Powershell window.
6. Verify That your Phone says that the Bootloader is unlocked
7. Type "fastboot boot TWRP.img"
8. TWRP should boot. Tap "Keep Read Only"
9. You should now be in TWRP. Go to Backup>Select Storage and choose your Micro-SD card and tap OK. Uncheck everything and check "Recovery". Then, Swipe the slider to back up your stock recovery partition.
10. Once it has finished backing up, reboot your phone to the bootloader.
11. Once it is in the bootloader, type "fastboot flash recovery TWRP.img" to flash TWRP as your recovery. (I believe this is the point where your warrenty will be invalidated by Huawei, so be careful.)
12. When it finishes flashing TWRP, reboot your phone to TWRP by holding down the power button and volume up
13. It should boot to TWRP. Tap "Keep Read Only", then go to (YOU ARE ABOUT TO WIPE IT AGAIN)Wipe>Format Data and type yes, and hit the enter button.
14. Once it finishes, go to Backup>Select Storage, select your SD card and hit OK, then check every box to backup all six partitions, and swipe to back them up. (At the end, it may seem to get stuck at 98-99%, DO NOT STOP IT! It is generating an MD5 checksum)
15. When it finishes backing everything up, go back to the home screen of TWRP, then go to Install, navigate to where you stored the SuperSU ZIP, select it, then swipe to flash it.
16. When it finishes flashing the SuperSU ZIP, tap "Clear Cache/Dalvik" and swipe to clear them.
17. Reboot your phone. IT WILL REBOOT MULTIBLE TIMES AND APPEAR TO BE STUCK SOMETIMES, BUT DONT TOUCH IT! This is normal and it will eventually boot like normal.
That's it!
Your phone should now be rooted and have SuperSU installed. Please note that this is a Systemless root, and will be removed if you factory reset your phone.Thanks to divineBliss for creating the original instructions.
What do we do after we get root to install custom ROMS? please advise
nedfred0 said:
What do we do after we get root to install custom ROMS? please advise
Click to expand...
Click to collapse
To install a custom ROM, you need the ROM you want to install, gapps depending on the ROM, and the proper firmware. The firmware you are on can be found under about phone and is the last 4 digets of the build number (in the format of B1xx). Once you are on the proper firmware, have your ROM and other things it may require, (every ROM is different), and a backup (just in case), you can flash the ROM from TWRP. Follow the instructions provided by the creator of the ROM to properly flash it.
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
BTJustice said:
Where do you get the USB driver at because I am not seeing it at
Click to expand...
Click to collapse
The drivers come with HiSuite. Download it and you should be good to go.
randomness725 said:
The drivers come with HiSuite. Download it and you should be good to go.
Click to expand...
Click to collapse
Thanks. I tried that but couldn't get it to go so I downloaded these instead which did the job:
https://www.androidfilehost.com/?fid=817550096634745788
does this work on the new h1711 huawei assend xt2
xaneth201 said:
does this work on the new h1711 huawei assend xt2
Click to expand...
Click to collapse
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
bricked 1711
randomness725 said:
It will not. The TWRP recovery image is device specific and might brick your device if you flash it to your phone.
Click to expand...
Click to collapse
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
You need a copy of the stock H1711 recovery image to use
"fastboot flash recovery H1711-stock-recovery.img" to restore the stock recovery. Until someone creates a working H1711 TWRP, I don't know where you'll find a stock H1711 recovery image file.
scrungydoolittle said:
Well I did not see that, so yeah, I have bricked it. IT comes up and says it is unlocked, it used to sit there then boot into the system.
So I downloaded the TWRP, tried to reboot to recovery and nothing.
Now, it just gets to the yellow warning screen, then goes black. Just bought this today on a black friday sale for 49.00
But did it for a reason. Now I would like to be able to recover it....
I was able to run adb and fastboot, so know that the drivers work, but it looks like it won't even get there now.
And it won't even go to the recovery, so I guess this phone is a real brick.
Can't seem to get the back cover off to remove the battery either.
Click to expand...
Click to collapse
download hisuite, enable oem unlocking and usb debbuginig, you gotta also get tha password or the unlocking, denn u run cmd and type:
adb devices
i hope i helped
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
BTJustice said:
Where do you get the USB driver at because I am not seeing it at http://consumer.huawei.com/us/support/phones/ascend-xt/
Click to expand...
Click to collapse
Here is the site for USB drivers for all Huawei models:
http://huaweiadvices.com/download-huawei-usb-drivers/
Good luck....
Does the phone even have a fastboot mode?
RomLord14495 said:
Does the phone even have a fastboot mode?
Click to expand...
Click to collapse
Sure it does
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Click to expand...
Click to collapse
Optionally you put phone into bootloader/fastboot or recovery modes by typing from an adb prompt "reboot bootloader" or "reboot recovery"
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
dominoes20 said:
Hi there. The website link for submitting your imei to get the unlock code doesn't work. Does anyone know how to get this code now?
Click to expand...
Click to collapse
You'll have to use DC Unlocker and pay to unlock until the page returns
Since unlocking the bootloader is no longer supported, I have a suggestion but am afraid to try myself.
So, download stock version of rom (aka fastboot rom). Extract, replace recovery.img with twrp (renamed to recovery.img). Restart phone in EDL mode, flash. In theory, edl is working fastboot mode so it shouldn't matter if bootloader is unlocked, correct?
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Imma try this out, I’m stuck in a weird situation where my sd card slot broke. When I sent it in for service, they said it was rooted and refused to fix it. I specifically did not root it so that I could send it in for warranty service. So it’s mission to try and root, unlock boot loader etc so that I can have more storage space
---------- Post added at 11:50 AM ---------- Previous post was at 11:36 AM ----------
ezopantyd said:
there is easy way to get unlock bootloader pass for all huawei
just by IMEI search on google "hardreset24 unlock bootloader" there is full info how to do it
Click to expand...
Click to collapse
Can you be a little more specific? I didn’t get that info on google
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
What ROM do you recommend for my needs? And could you provide me a link to the correct download/discussion board? I would prefer a ROM running at least Nougat that has long-term support planned. I read that “Fire Nexus ROM” is pretty basic, so I don’t think I want it. As of now, I’m looking at CM/Lineage 14.1, but I don’t know what ROM would work on my device from the website. AospExtended seems like a good option but apparently, there are wi-fi issues which are a deal-breaker.
Thank you so much for reading through this. Hopefully all my research and proves to be useful for anyone trying to help. If I’m able to get this working cleanly, I would be willing to make a cleaned up guide for this version and device to better aid future people.
hwwof said:
I’ve been lurking on these forums for a while and I have decided that I’m willing to take the risk to unlock my Thor’s potential. I have made sure to read through advised reading materials, and searching through other posts before posting. (I tried figuring out how to quote multiple posts to make this thread easier to navigate but I couldn't, sorry)
Device: Kindle Fire HDX 7” 3rd Generation running Fire OS 4.5.5.3
I will be using a Windows 10 Home machine to do this.
Purpose: Allow for the device to work well in Google’s ecosystem so I can have a useful device for medical school.
Click to expand...
Click to collapse
Hello @hwwof -
You have done your homework (thank you!) and presented reasonable questions. I'm going to answer the first five 'in-line' below. Responses will be brief to keep the thread serviceable for those accessing XDA content on small screens; don't read anything into that. Bounce back on any items that need further elaboration.
hwwof said:
I am currently trying to learn the steps outlined here, but I have some concerns:
Does it matter whether or not I factory reset my device before I begin?
Click to expand...
Click to collapse
No; however, it would be better if you did NOT reset the device.
hwwof said:
Will my computer’s OS cause any issues? According to this, there might be some driver issues? Should I download the “Motorola Device manager”?
Click to expand...
Click to collapse
Nope. Drivers installed via the Motorola Device manager are properly signed which mitigates any potential issues on 64-bit Win 10 builds (yet another reason to use the Moto drivers vs others that have been posted)
hwwof said:
Where is the “aboot_vuln.mbn” file? Do I obtain it once I follow the steps in order?
Click to expand...
Click to collapse
It's contained within aboot-13-thor.zip; just named differently.
hwwof said:
I want to use “Minimal ADB and Fastboot” instead of the attached “15 seconds ADB Installer v1.4.3” because the later has not been updated in a while and the former was updated this month. According to the install instructions for the former, I need to have my device already plugged in and the “kindle fire USB driver” already installed. Will this affect step 4 of the procedure or anything else?
Click to expand...
Click to collapse
Good idea. Your device does not need to be tethered while installing Minimal ADB and Fastboot. Take note of where the package is installed (typically "C:\Program Files (x86)\Minimal ADB and Fastboot") and practice opening a command window focused in that folder. To make life simpler you can direct the installer to place the files in "c:\work" which is a lot easier to type.
hwwof said:
On step 5, am I correct in my assumption that changing the driver will be a simple few click process?
Click to expand...
Click to collapse
Yes - but here's were it gets interesting and a bit frustrating. Even with the Moto drivers Windows can be very fussy communicating with HDX devices. To complicate matters there are two modes to deal with: ADB and Fastboot. You'll learn which is which as time goes on and will likely have to switch Windows drivers for each mode. Sometimes a reboot is needed to get everyone talking. Note there is no danger involved simply tethering your device and issuing basic queries.
To test basic ADB communications:
- execute step #2 (only) from the linked procedure
- open a Windows command prompt as outlined above
- boot HDX into FireOS and move past the screen lock
- tether device to windows; take note of any noises and/or confirmation messages
- in the window command prompt issue the command "adb devices" and press Enter. What happens?
Post back results and we'll go from there.
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Here are my results that you requested:
The kindle beeped, and the internal storage popped up on my computer. I ran the minimal adb and fastboot program, and got this output:
Code:
C:\adb>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
D0FBA0A0351401GB unauthorized
C:\adb>
And on the kindle, I got a “Allow USV debugging” popup on the kindle and it showed my computer’s RSA Fingerprint. I then pressed allow. I took note of the fingerprint just in case. I then tried ejecting my device but it wouldn’t let me because a program was still using it. I ran “adb devices” again and got this output:
Code:
C:\adb>adb devices
List of devices attached
D0FBA0A0351401GB device
C:\adb>
hwwof said:
Thank you @Davey126 . I appreciate you taking the time to help me out. Answers to the other questions would be very appreciated as well!
Click to expand...
Click to collapse
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Davey126 said:
Second response is positive. Next issue the following command: 'adb reboot bootloader'. This will place your device in fastboot mode. If you are very lucky a 'Ready' prompt will appear on the device below the word 'fastboot'. Most likely you will need to head to Windows Device Manager, identify which entry is associated with the tethered HDX and then change the device driver to 'Moto Composite' or something similar (might not have the wording exactly right). Once you get a 'Ready' prompt issue the following command: 'fastboot devices'. If you get a response similar to 'adb devices' then you are good to go.
Hints/tips:
- to help determine which entry(s) are associated with your HDX tether/untether your device while Windows Device Manager is open
- right click an entry to change the device driver; navigate 'Browse my computer ...' -> 'Let me pick ...'; do not choose any of the automated options
- if you can't get a Ready prompt and/or an response to 'fastboot devices' reboot both devices and try again
- if still no joy change USB ports and cables; the latter are especially problematic (people never believe that until trying 1821 other things - ugh!)
Report back and we'll go from there. I know you prefer the rest of your questions answered up front. Experience suggests an incremental approach is more productive - for you, me and future readers.
Click to expand...
Click to collapse
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
Code:
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
hwwof said:
Thank you! Now it says "ready" but I'm concerned about how to unplug it without messing anything up. here's the output:
{content removed}
You are correct that I would prefer having all the answers upfront, but it's only so I can then question the answers to get a better understanding before messing with the device. A quick reply would be appreciated!
Click to expand...
Click to collapse
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Davey126 said:
Great!! The purpose of this exercise was to validate connectivity in two different modes and, if needed, provide a safe 'test' environment for remediation. No worries about breaking the tether if there is no active data transfer taking place. Simply unplug and then long press <power> until the device shuts down.
In response to your other questions:
Q: On step 6, do I follow the directions as they are quoted, or the ones on the original forum? If the later, does “change to the directory with the extracted dd.exe” mean to type the directory or something else? Also, a poster here stated that he got error message on the second 2 commands instead of the first, is the concerning at all? Should I take any precautionary measures?
A: Follow the steps as quoted
Q: Once step 9 is completed, can the kindle run as normal if I don’t flash anything? And what does it mean “get into the TWRP”? I’ll simply be in the recovery menu on the kindle? How do I flash my chosen ROM using TWRP?
A1: You should assume all content on your device will be erased following completion of Step #9 (although it will likely remain intact)
A2: The two files you will be 'flashing' with the dd command should be located in the same folder as "Minimal ADB and Fastboot"
A3: Deal with that later (flashing ROM)
Q: ROMs:
A: All of the Nougat based custom ROMs for HDX are stable and feature complete. Nuances are subtle and probably not worth worrying about now; you can always change later. My personal preference is AEX (AospExtended). That said, Lineage 14.1 and Slim 7 are both excellent alternatives.
Click to expand...
Click to collapse
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
*deleted*
*deleted*
hwwof said:
So I completed the instructions, booted to TWRP, turned it off, booted up, did the unlock batch, but I didn't get "unlock code is correct". I got a lot of green lines "getvar slot-count...OK getvar:slot-suffixes...OK getvar:has-slot:unlock...OK getvarartition-type:unlock...OK getvar:max-download-size...[[0x20000000 ]] download:00000000..." Here's the cmd when I try running unlock.bat https://gyazo.com/a041dc49c786f9846d706c049eacbbf3
Did I mess something up or am I unlocked? I'm not sure what to do from here. I was still able to get back to TWRP. It's telling me to swipe to allow modifications or to keep read only. Where do I proceed from here? I'm reading in some places to wipe before installing, and a lot of other conflicting information. I downlaoded the AEX november build and would like to flash it. Do I have any need for rooting or SuperSU?
Again, Thank you so much for all your help
Click to expand...
Click to collapse
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Davey126 said:
Device is NOT unlocked. Tied up for the next hour or two; will respond then. Do not wipe or attempt to flash anything. Sorry for wait ...
Click to expand...
Click to collapse
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
hwwof said:
Thank you for being on top of this! I'm glad I was patient and didn't immediately try flashing anything. I'll try to wait up! I apologize if I fall asleep.
Click to expand...
Click to collapse
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Davey126 said:
Quick activity while you wait:
- boot into TWRP (power down; press <power>+<vol-up> for ~3 sec then release)
- swipe to allow modifications
- tap the backup option, select all partitions except cache, swipe to execute
- when complete tether device; should connect in adb mode
- from look for a new device/drive in Windows File Explorer
- click <device ID> -> Internal Storage; should see a folder named TWRP
- drag or right-click folder to a storage location on your Win 10 machine
- congrats! You have just made a backup of your device -and- placed a reserve copy on your Windows machine
Comment: prior to backing up you had completed the most risky tasks (stuff that could have yielded a soft/hard brick). It's all downhill from here. Will post more info on unlocking and installing a new ROM in a bit; real-life is calling . Fully understand if you need to sleep; post will be waiting in the morning. Penning this from Northeast USA; timezone UTC-5.
Click to expand...
Click to collapse
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
hwwof said:
I appreciate you so much! And I completely understand. I hope everything you're working on gets resolved!
I have backed it up as you suggested! Since the back-up is also on the internal drive, it will be deleted later, correct? It's 5gbs out of the already small storage space.
Click to expand...
Click to collapse
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Davey126 said:
With the 5GB TWRP backup folder safely copied off-device you can delete the local copy at any time...although there is no immediate reason to do so.
Next step is to unlock the bootloader:
- verify 'get_code.bat' & 'unlock.bat' reside in the same folder as adb.exe and fastboot.exe
- look around to see if you have a file called 'unlock.code' from a previous run of 'get_code.bat'; if so place it in the same folder
- tether device and boot into fastboot (easiest way: boot into TWRP and then use reboot menu to boot the bootloader) [<--what an awkward sentence!]
- enter 'fastboot devices' to validate communication between host and device
- execute unlock.bat; if you get a green 'OK' the bootloader is unlocked!
- if not boot into FireOS (get past unlock screen), tether, verify adb communication is working and then run 'get_code.bat' to (re)create the 'unlock.code' file
- repeat steps 2-4 (above)
If that doesn't work and/or you are unable to boot into TWRP then a bit of extra work will be needed to generate a valid unlock code. Brief outline:
- download legacy Fire Nexus ROM from here (it does NOT require an unlocked bootloader)
- tether device and into TWRP
- from Windows copy downloaded ROM to a folder on the device (suggest creating a new folder with your initials as the name)
- from the TWRP main menu tap Wipe then swipe to perform a 'factory reset'
- from the TWRP main menu tap Install
- navigate to the folder where you stored the downloaded ROM
- select the ROM zip and then click to install
- when complete allow the device to restart; after a 3-5 min it should boot into Fire Nexus; skip the Google config (not needed)
- enable developer options and adb bridge
- tether device and verify adb connectivity
- run 'get_code.bat' to generate a fresh unlock.code file
I will be traveling much of Sunday with irregular network access. I'll try to respond to an questions/problems as time permits. Apologies in advance for any delays.
Click to expand...
Click to collapse
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
hwwof said:
Welp, device won't boot into FireOS. It boots straight to Fastboot. I tried Installing nexus ROM but I got "can't install this package over newer build updater process ended with error:7".
Click to expand...
Click to collapse
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Davey126 said:
Error 7 is pretty generic and can be due to a conflict between install package and TWRP or an issue with the system partition. It's a solvable issue without too much work. They the following in the order listed.
1) In TWRP tap wipe -> advanced. Tick system, data, dalvik and cache; leave internal storage unticked. Tap the appropriate button to execute. Return to main menu and reboot back into recovery. Then try to install the Nexus ROM.
2) Download an older build of TWRP from here and transfer to adb/fastboot folder on Windows. Boot device into fastboot mode and issue the following command to install:
sudo fastboot -i 0x1949 flash recovery <recovery-image>
Will check back in 5-6 hours on progress.
Click to expand...
Click to collapse
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
hwwof said:
First one didn't work, second one put this out:
C:\adb>sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
'sudo' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Drop the sudo prefix ...
Davey126 said:
Drop the sudo prefix ...
Click to expand...
Click to collapse
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
hwwof said:
"
C:\adb>fastboot devices
D0FBA0A0351401GB fastboot
C:\adb>fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
target reported max download size of 536870912 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.361s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.424s
C:\adb>
"
Click to expand...
Click to collapse
This suggest the vulnerable bootloader was not properly installed. You will probably need to repeat the installation procedure from the point of placing the device in 'bulk' mode. Be sure to pay attention to file indexes and file identifiers that follow "if=".
@draxie - would you agree with this assessment? Poster is following this guide and using the files attached to that post.