Like the title says, I am currently unlocked, and have CWM touch installed and all that's left to do is flash SuperSU so that I can get root access. I just tried flashing the most recent zip for SuperSU (1.86) and I get the error when I open up the application for some reason.
"There is no SU binary installed and SuperSU cannot install it. This Is a problem!
If you upgraded to Android 4., you need to manually reroot - consult the relevant forums for your device."
I am on 4.3 and I have tried this. but I cannot get my One to be recogized as an adb device. I mean, when I run ADB Devices command in cmd prompt, it shows up with the ID number and everything, but when I send a command in Hasoon 2000's toolkit, it just shows an error: device offline.
USB Debugging is enabled, tried many different USB ports, rebooted phone and PC, nothing. What can I do to get my device online again!?
Please, If there is anyone that can help me fix these two problems, I will love you forever.
On T-Mobile HTC One 4.3
-Thanks
Related
So I was trying to set up the old OneX+ with a new ROM.
Phone already had TWRP 2.7.1, unlocked.
When in Fastboot USB my system does not recognize the phone, it is simply listed as "Fastboot" under "Other Devices" in Device manager... I can't set the drivers manually as I did last time.
The main reason why I need Fastboot working is because I keep getting "error executing updater binary in zip" when trying to install a new rom, I read somewhere TWRP 2.3.3 may be the solution, would appreciate if anyone could confirm this as well.
sens1r said:
So I was trying to set up the old OneX+ with a new ROM.
Phone already had TWRP 2.7.1, unlocked.
When in Fastboot USB my system does not recognize the phone, it is simply listed as "Fastboot" under "Other Devices" in Device manager... I can't set the drivers manually as I did last time.
The main reason why I need Fastboot working is because I keep getting "error executing updater binary in zip" when trying to install a new rom, I read somewhere TWRP 2.3.3 may be the solution, would appreciate if anyone could confirm this as well.
Click to expand...
Click to collapse
Sometimes I am having this problem too. Try to replug your usb when the phone is in Fastboot mode. It works for me.
Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
This week Verizon pushed a firmware update for Kyocera Brigadier to Lollipop. We have two. One processed successfully.
Mine did not. Once the firmware downloaded and ran, my phone ended up stuck in the endless boot loop.
I can get it to the:
Android System recovery <3e>
LMY47V
recovery screen.
I run OpenSuse 12.3 on my computer. No Windows available. I installed ADB tools.
When I open a shell I get:
[email protected]:~> adb get-dev-path
unknown
[email protected]:~> adb usb
error: device not found
[email protected]~> adb root
error: device not found
[email protected]:~>adb start-server
[email protected]:~> adb root
error: device not found
[email protected]:~>adb reboot-bootloader
error: device not found
[email protected]:~> adb get-state
unknown
I had previously installed Kingroot on my phone and rooted it. Then uninstalled that and has SUuser for root access. When I started the update I had root access for the user not active and I did have the USB option for debugging active on my phone.
So I have a phone that I can move through the wipe data/factory reset successfully and the wipe cache partition successfully. I can power down. I can reboot to bootloader. When I select view recovery logs I get a lot flying through the screen, but most of that seems available.
Help Please! I haven't found a thread that helps me understand not finding the phone with adb. I haven't found a thread that answers whether TWRP, Fastboot, ADB, or what can assist me with restoring it.
Kyocera wants me to send it to them for 10 to ??? days for $20-$50??? bucks for an answer.
Thanks in advance, for directions to the right threads, the right answers, even if it means throwing it off a bridge.
Ken
Well, tried computer as root doing lsusb. The phone does not show up at all. It seems that answers that, eh?
I realize this thread is two years old, but for anyone else who may stumble across this:
Kingroot is Chinese government spyware. DO NOT USE KINGROOT.
I have an answer to this. I had the problem, then I found the solution and now I'm sharing it:
Problem: I tried to put SuperSU on my M9 with CM-13 because I thought I needed root (you don't, under developer options there is the ability to turn on root essentially). So I flashed SuperSU from an apk and then it auto-updated itself then rebooted and got in a start up loop! Now I couldn't access the phone via adb, I'm not sure why. I think USB Debugging was off, but I'm not sure. AND I had not installed SuperSU from a zip so I didn't have that file laying around! So I went and got the latest SuperSU which I heard would work (it did) here: http://download.chainfire.eu/969/SuperSU/ THEN....how do I get it on my phone? I mean, who has a micro-SD reader laying around...not me today.
I DID have fastboot working but not adb. SO....I went into my phone and launched recovery mode then I chose this new thing called "adb sideload." That turns ON MTP so your phone comes up technically on your PC via USB but it doesn't show under my computer. But then I was able to go to my command prompt and type "adb-killserver" then "adb sideload NewSuperSU.zip" and it loaded!!! And I could then boot in!
Now I'm sure I shouldn't have SuperSU running but at least now I can put all the needed binarys (like CM and gApps to get started if I needed to from scratch) on !!!
So it works now.
Hello.
This post describes how to reboot the Alcatel OneTouch Pop Icon A564C Yaris5NA into EDL mode. This can be achieved without root. It can happen on both Windows and Linux computers. It requires ADB to work.
1. Go into settings and "About phone" and tap the build number "01001" for about seven times.
2. Go into "Developer options" and enable "USB Debugging".
3. To install ADB drivers on Windows Vista, look for "Minimal ADB and Fastboot" on XDA and download extract and run the exe file. Do not forget to install Google drivers. On Linux, just install adb through terminal.
4. On Windows, go into "Device Manager" in Windows and look for "Android device" with a yellow triangle with an exclamation point. You may have two of these on your computer, so be sure to install drivers to both devices to avoid any error.
5. Right click on these devices and the menu appears hit "Update driver", than select browse my computer for drivers and eventually show all devices. Find the Google Inc. drivers and install one of three drivers; the "Android ADB interface" should work, but you may have to use the "Android Composite interface".
6. Go open CMD or Terminal and type adb devices. You will receive "Enable USB Debugging?" on your A564C phone so be sure to check the box and press Enable.
7. Now check adb connection by typing "adb devices", and the device should appear in the terminal; there should be letters and numbers on the left and authorized on the right.
8. Now type "adb reboot edl" to send the device into Emergency DownLoad mode. When you look on Windows a box appearing with QualComm HS-Loader 9000 (COM4) drivers will have installed. Look into Device Manager under ports (the serial cable icon)
Well, if you have this phone A564C and would like to develop on it, this guide may have motivated you to do make custom software. I think the only way to flash firmware is through QFIL program on Windows. Now we are looking for a FireHose programmer for the device in an attempt to unlock the bootloader the way the new ZTE method is described. My goal is to find the right FireHose programmer and to examine the partition manager and edit the bootloader to unlock it, or perhaps a way to somehow put the su binary in the /system/bin folder, or put a custom recovery on the device. That is my goal.
Here is my background on my device:
I have owned the Alcatel OneTouch Pop Icon A564C for over a year. I have read the posts describing many users who do not have enough space on their internal storage and that is why they need root. I have also read KingRoot can root but for me it is the opposite. I had tried rooting many times with the KingRoot. When the metre reaches a certain point, usually 18% or 70%, the phone crashes and reboots automatically or freezes and requires holding the power button to reboot. The phone is seemingly unable to root. Last week I acheived a true temp root that was lost upon reboot; the way I did it I installed KingRoot apks I downloaded from AndroidFileHost in order from oldest to newest, ran them once for reboot, then proceeded to uninstall each one and reinstall the newer KingRoot. I had noticed a phenomenon when using a newer KingRoot than going to KingRoot 4.1 I received root failed and it went back to 70% and I achieved temp root that way. I than restarted the phone in order to restart the method after a data wipe.
I then thought if there were other ways to root a phone other than using one-click rooting methods such as KingRoot. The phone was manufactured about six years ago, so it is old enough that exploits could potentially root it. I had tried Framaroot and Towelroot; both did not work. I installed a DirtyCow checker apk and it said the phone was patched, so I assume an exploit based on DirtyCow would not work. There may be one more method to finally allow root; it is called QuickRoot a Proof-of-Concept root for Android devices. It may work on older devices, but I do not know how to compile for Android 4.4.2.