-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor isues with the linux script for ZTE Open #19
Comments
Hello, I'm in the same situation, could you help me on the step to replace the adb binary? I don't know how to do that. Also for installing inari you used fastboot in command line ? |
you remove the adb file from the folder where you unpacked this installer and make a link I used this on a phone updated to 1.1 with official package from ZTE |
Thanks! It works but at the end it was useless because I've moved 2h after to 2.2. On January 27, 2015 12:21:03 PM CET, Zbyszek Tenerowicz [email protected] wrote:
Eluc |
On a ZTE? Give me a link please ;) |
oops, wrong button. Sorry for the mess. |
I've followed this tutorial on XDA: |
Hi,
I just rooted and flashed my ZTE, but it took some time.
I was using a zip package from the main page, hope it was the latest version.
First of all, the provided adb binary couldn't load libncurses and wouldn't run on my xubuntu14.04 (libncurses installed), had to replace the binary with a link to one installed from repo. You might add a switch to the script to use adb installed in the system.
The inari images were swapped. I had to install the signed first and the not-signed later, opposite to what the script told me to do.
After rooting, the script would just try and try to root again, and wouldn't progress to installation. I stopped it and updated through "advanced" menu.
The update didn't work too, because it tried to install
/sdcard/update.zip
while the file was in your specific folder not in the root of sdcard. But installing manually did the job.Hope this helps. Unfortunately I didn't save console output (thought about it watching the system shut down...).
The text was updated successfully, but these errors were encountered: