error; protocol fault (no status) - ZenFone 2 Q&A, Help & Troubleshooting

guys, my phone rooted by pre-root system
i want to unroot my phone, so i want to instal stock rom.
even i command "adb sideload (rom name)", always error (error; protocol fault (no status)
please help me for fix it.
thanks.
(sorry my english bad)

This might be an issue with the version of ADB you are using. Looking on the phone screen when you see this issue will give you/us more details.

try another adb

Related

[Q] Can't root v10f

Hi, I just flash my phone with FW v10f from v10a. It work fine with some issue..no wifi and screen rotation. I try rooting the device to install CWM to flash CM9 or ICS. I am not able to root with any method. Superoneclickv2.3.2, Superoneclickv2.3.3, DooMLoRD_v4_, Unlockroot, SU640_ROOT, Gingerbreak, Z4root, manual method with adb shell... nothing work. I tried with formatted sd card and without sd. It is on debugging mod. I can communicate with the phone via adb but it say "permission denied" on su command. All root's program recognize my phone but it always end with "no luck..failed"
There is another kdz firmware that can be rooted?
Im on Android 2.3.5
Kernel 2.6.35.11+
Build GRj90
Software LGSU640-00-V10f
I think the most important part would be letting us know where it fails with the manual root for instance. I rooted that firmware yesterday with Doom's v4 after failed attempts with superoneclick, rootunlocker, and the manual method. I would recommend restarting your phone and pc if you havent tried to already. If all else fails, try a different computer or maybe just a different usb port.
I get "permission denied" on all command i put in adb shell. Itried everything, with another pc in all usb port and no luck..
Bad luck, root did not success. Its what i get on all root attempt.
how much times have you tried in a succession ?
i had unbricked my phone after flashing ics leak and to root v10f, it took around 11 attempts !
i tried superoneclick 8 times and then i goot root via unlockroot in 2-3 attempts !
so its completely uncertain when you would get rooted !
you just need to try till you get rooted !
also i have attached a zip file, extract it and try to root with that !
good luck..
I tried your files but it doesnt work. It keep saying me "permission denied" and "read only file system"
It is the 13 attempt now with TPSparkyRoot with no sign of change.
I think i 've just get it. I have superuser in app list. I cant understand why it can take x attemps to get root but i cant complaint....its works now!
It is not root at all. su=access denied. Im lost
when you connect you device to the pc, does it show in "adb devices" ?
i mean pls verify whether all drivers are installed properly !
Yes, it show "Androidnet sooner single adb interface". Now when i try to root i get "No such file or directory" on almost each line.
In manual root i get this:
adb shell rm /data/local/tmp/boomsh
rm failed for /data/local/tmp/boomsh, no such file or directory
adb shell ./data/local/zergRush
cannot copy boomsh : permission denied
Rush did it ! It's a GG, man !!!!!!
Now it's real!!!
Settings\Privacy\Factory data reset
Followed by this guide: http://forum.xda-developers.com/showthread.php?t=1407076
4.0.4
Thanks for the extra root option.
I had my LG Optimus SU640 (same as Nitro HD) rooted and running 2.3.5, and just updated firmware to Android v4.0.4 today on the LG website. I'm in Korea.
I have tried everything under the sun to root my updated OS but i'm not getting anywhere.
Is it not possible to root this phone with the updated Android 4.0.4 OS at the moment?

[Q] hard problem with twrp 2.7

Dear everyone,
I have a problem with twrp 2.7.0.0
i using kindle fire hd 8.9lte and root it. so i install zip pa_jemlte- 4.4rc2 with pa_gapps-stock 4.4 but it not run
and Now, i cant go my OS,and i dont have any another rom in my kindle.
I just go TWRP 2.7.0.0. I try manything to adb sideload or adb push but it not connect with my pc.
my adb version is 1.0.32 but my adb devices is not thing, i can use more adb version but not thing change.
I try to USB OTA to take rom from usb but it doesnt work.
Any have idea?
I try more and more.
Thank you,
my email: [email protected]
ps: sorry for my english. that terrible. i think you know what I saying
addition
in addition, my devices manager has "!" beside kindle
I think this is case problems. when i use any commands adb ... it show: "error: devices not found"
I think if my devices connect to pc , i can use adb.
Thank you,
expect news soon
VietAnh
[email protected]

Protocol Failure

I've rooted my AFTV and blocked automatic updates, now I'm trying to downgrade so I can put on CWM using the guide on AFTVnews.com but during the command "adb push update.zip /cache" it comes back as protocol failure after about 20mins
Can anyone tell me what's happening?
Thank you

Fire TV 2 - stuck at b/w boot logo after flashing prerooted 5.2.1.0

Hi folks,
I having some problems here while I try to flash the latest prerooted rom from rbox. So here is the situation
FireTV was on Stock Rom 5.0.5.1
- I followed the Guide on aftvnews to install TWRP Recovery link
- everythink looked good, prerooted rom was installed without any errors
- reboot system -> stuck at black&white "amazon" logo
- I noticed that the LED completly turned off after 30 seconds (i guess) so might be looping
- back to twrp I did wipe /cache, then reboot -> same behavior
- tried over adb shell : mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
-> same result
- tried factory reset -> guess what, same as before of course
so what the hell can I do to reset it in some way?
One thing I also noticed is that when I open a local terminal or an adb shell I'm already root. Is this normal for prerooted rom?
And another thing is the supersu binary. I could remember that the bin was installed to /sbin/su ,but this is not the case here.
'which su' gives no result back
'find / -name su' give me /system/xbin/su
Is that the way it should be? I ask because adblink gives me an error when I try to run FS R/W
"root requiered"
Thats explainable cause adblink will run 'su' first.
I would be really happy if someone could give me some advice. I dont know what else I could try
!! Problem solved
It was the god damn HDMI cable -.-
Behind the boot logo it was waiting for paiing the remote
Maybe it could help some of you guys too
Kind regards
Thank you, had the same issue, never would have tried a new cable, as i was getting video from it.

Bricked M8? Flashed old TWRP via newer TWRP - can't enter recovery

Hey,
At Start: HTC One M8 with LineageOS 14.1, fully working, TWRP 3.1
According to go back to Stock Rom I did the following:
(1) Go into TWRP 3.1
(2) Do a normal Wipe with the prefilled boxes
(3) Install TWRP 2.8.7.0 with TWRP 3.1
(4) Clicked Reboot
Problem: Guess what, It doesn't reboot anymore. I can't get into recovery (nor the System I don't have).
What I did after this happened:
(1) Remembered: Never change a running system.
(2) Realized fastboot is not working (as expected)
(3) Realized adb is working.
(4) Following the guide to install recovery via flash_image described here http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
What I did not:
(3) in Guide: Enable USB Debugging since there is no System installed anymore.
Where I stuck:
adb shell
~# su (yeah shell looks like this)
~# /sbin/sh: su: not found
Checked - /sbin/sh directory exists
Did some research on the WWW - didn't find something useful
So, my Questions are:
(1) Is Flashing a old Version of TWRP via TWRP a bad thing you should never do? Since 2.8 you're able to update TWRP via TWRP, so I tried the same backward
(2) Is there a option to solve the /sbin/sh :su not found or is this a serious technical issue which can't be solved because of no usb-debugging enabled?
(3) Do I have other options I don't know yet?
Any help is appreciated. Thank you very much.
Kind regards,
wapdap <- my super cool new user name which prevents me from crying right now
wapdap said:
Hey,
At Start: HTC One M8 with LineageOS 14.1, fully working, TWRP 3.1
According to go back to Stock Rom I did the following:
(1) Go into TWRP 3.1
(2) Do a normal Wipe with the prefilled boxes
(3) Install TWRP 2.8.7.0 with TWRP 3.1
(4) Clicked Reboot
Problem: Guess what, It doesn't reboot anymore. I can't get into recovery (nor the System I don't have).
What I did after this happened:
(1) Remembered: Never change a running system.
(2) Realized fastboot is not working (as expected)
(3) Realized adb is working.
(4) Following the guide to install recovery via flash_image described here http://www.addictivetips.com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/
What I did not:
(3) in Guide: Enable USB Debugging since there is no System installed anymore.
Where I stuck:
adb shell
*~ su (yeah shell looks like this)
*~ /sbin/sh su: not found (or something very familiar)
Checked - /sbin/sh directory exists
Did some research on the WWW - didn't find something useful
So, my Questions are:
(1) Is Flashing a old Version of TWRP via TWRP a bad thing you should never do? Since 2.8 you're able to update TWRP via TWRP, so I tried the same backward
(2) Is there a option to solve the /sbin/sh :su not found or is this a serious technical issue which can't be solved because of no usb-debugging enabled?
(3) Do I have other options I don't know yet?
Any help is appreciated. Thank you very much.
Kind regards,
wapdap <- my super cool new user name which prevents me from crying right now
Update: will update the exact error message tomorrow, so you guys have valuable Information to help me. Nonetheless you might have a idea to share?
Click to expand...
Click to collapse
You could fix this easy by running an RUU probably.
USB debugging is still on if ADB works btw
@xunholyx
As I understand the process of RUU it requires working fastboot.
https://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
Oops, wait, they mentioned a second method. Didn't read that. Sry

Categories

Resources