Develop Bugs

[Q] Fastboot error

Recently, whenever I use the fastboot command from my PC with my Zenfone 2 (64 gb) I am getting responses that read ”FAILED (remote permission denied)".
As an example, I flashed the new TWRP recovery with fastboot and got these messages:
Sending xxxxx
OKAY
Writing xxxxx
FAILED (remote permission denied
The odd thing is, the command appears to have worked as the new recovery has been flashed as desired. Anyone have an idea what's happening and how to eliminate the supposed error?
I should add that the phone is rooted and bootloader is unlocked.

I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!

having the same issue.. any possible fix ?

stupid_productions said:
I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!
Click to expand...
Click to collapse
I had the same fastboot problem, but now is worse. I did a unthetered recovery and rooted by flashing superuser.zip. Now i can´t go to bootloader or recovery, but i have root access (phone is strangely working normal, i just can´t uptade, acess bootloader and recovery)
Why did you deleted folders in your phone? I think i have some issue like that. Can i solve my problems like you did since i have root acess and can do that with root explorer?

same issue here, any known fix so far?

JulioQc said:
same issue here, any known fix so far?
Click to expand...
Click to collapse
nothing for me, but once my phone is rooted and unlocked i flashed twrp recovery and use only that.

Today's CM14 bricked my H815 (no bootloader, no fastboot, no recovery)

Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?

bestouff said:
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
Click to expand...
Click to collapse
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?

Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)

Tycoon282 said:
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Click to expand...
Click to collapse
The OP has another issue pls do not hijack.

steadfasterX said:
The OP has another issue pls do not hijack.
Click to expand...
Click to collapse
Sorry, it's nearly the same issue though, CM14.1 broke phones today.

Today's update broke mine as well. Looking for solutions. Will follow your thread and progress.

Same for me. Tried download mode with lgup to flash stock which worked once - but I kind of bricked it again by trying to install cm14.1 again. Then i tried to go back to stock using lgup again, but now lgup it just crashes. The phone now goes automatically to download mode after turning it on, the progress bar stays at 0%, the phone says "633A B100" and lgup crashes after 9% "prepare dlmode" or something similar. any ideas? :/

Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.

thewild said:
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
Click to expand...
Click to collapse
After flashig the CM Recovery via TWRP, i can't use the recovery anymore. If i boot into CM-Recovery the display shows "Ereasing" and start the system. After that i got a bootloop.
Is it possible to use fastboot??

You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.

thewild said:
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
Click to expand...
Click to collapse
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.

onlyolli said:
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
Click to expand...
Click to collapse
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?

thewild said:
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
Click to expand...
Click to collapse
Yes, it was with cm recovery 20161130, if i remember correctly.
Sadly now, i can not go into fastboot. The phone goes directly into download mode. My windows vm detects the phone, and tries to flash a recent kdz, but lgup crashes at 9%. The phone still shows "0%".

Oh that's bad. What about another kdz ?

thewild said:
Oh that's bad. What about another kdz ?
Click to expand...
Click to collapse
Already tried like 3-4.... Its always the same. If the tool would at least give me a little bit more information, but it just stops.

I don't know then. Some users seem to have had the same problem (stuck at 9%) : http://forum.xda-developers.com/search/forum/4233?query=lgup 9%

I had the same issue, tried several things, my final solution was:
- Start in download mode (Volumen up and then plug in cable)
- use "LG Brigde" on Mac to install stock Rom ( Software update tab in APP ) guess should also work with Windows
- Boot original android
- enable usb debug
- Start bootloader via ADB
- fastboot flash recovery to twrp 3.0.2
- Boot in recovery via power and vol down (first factory reset from stock appears but after this twrp is starting)
- install cm nighty of 1 DEC via ADB sideload
- reboot and done
In the meantime i updated to twrp 3.0.2-1., installed gapps etc. everything is now working fine again.
Hope this is also working for you.

Which version of cm14 did u download and install? Can u please post the exact version?

Mmh ... LGUP is the Windows utility right ? How do I do if I only have a Linux machine ?

steadfasterX said:
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Click to expand...
Click to collapse
I'm trying to get to it via power+down, I get to the double "do you want to factory reset ?" question, but then :
- sometimes the CM recovery just says "erasing" for a few seconds and reboots to (non-working) CM
- sometimes it just plainly boots to (non-working) CM
I used to have TWRP installed but it didn't work with CM update, so I let CM install its own recovery.

Brick OnePlus 3

Hi and happy new year
I think there is a problem when i have update my OnePlus 3 on Nougat and root it because now the OnePlus3 don't work.
The twrp don't work, only fastboot work.
Now when i boot the OP3, i have a black screen with this lines :
md5 checksum
cache failed
boot failed
boot aging failed
system failed
recovery failed
modem ok
bluetooth ok
adp ok
sec ok
.....
I can boot to fastboot, i have on my pc the zip of OnePlus3.OS.3.2.8.zip and OnePlus3.Nougat.zip.
Do you think is there any issue or is blocked ?
Thanks for help

Use Brick Guide.

I had the same issue since updating to OOS 4. Caused me massive headache today and basically I thought my device was bricked. I had to use a 3.2.6 zip and corresponding Rom via MSKIP toolkit and fastboot/adb to get my device working again. After more than a decade of flashing ROMS this was my biggest fXXk up yet. I feel that TWRP recovery (even the modified ones) are not yet compatible with this update in some way. I constantly got encryption/dm verity issues even when using the modified software. Sadly for now I have gone back to pure stock (Rom/Recovery) to get my device working and updated to Android 7. To be honest I am afraid to go down the custom recovery root on this device for a while due to the headache it caused me today. I can see a few posts of people having issues so this cant be isolated.

Thanks for help
I will success to reinstall the OP3 with nougat and root is ok ^^
It was long but all is ok and i was afraid to send the phone on sav.
So i use the method 2 in this link : https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
And i install again the stock rom 3.2.8 with "adb sideload" on fastboot and i install the Maj OTA with vpn.
I install the last TWRP here : https://forum.xda-developers.com/devdb/project/dl/?id=21835 and the last Supersu here : https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip and all it's ok now
I will afraid too like you because my phone was brick when i root nougat.
But i tried and i'ts ok now, i don't know why the first time it's not working.

Troubles with booting TWRP via adb

Just as the title says, I'm having trouble trying to boot TWRP via adb.
As a quick overview, this phone arrived with an unlocked bootloader from the seller I bought it from at AliExpress. Because of that, I decided to flash Pixel Experience 8.0. I remember back then that it gave me a few issues as well when it came to trying to boot TWRP via adb but somehow managed to do so.
Ultimately, I was able to run the rom without a problem and it was smooth sailing from there. Fast forward to now, I thought it was time that I updated to PE 9. Again, I'm having issues trying to do the same thing. If you're wondering why I don't have TWRP installed, it's because I didn't want to root my phone
due to issues that's connected to Fate Grand Order. I remained unrooted, which meant that I had stock recovery.
My biggest problem is the (Command Write Failed [Invalid Argument]) text when trying to boot TWRP. If it's not that, then it's stuck at "Waiting for device." Both situations lead to "Press any key to shutdown" at the top left corner of the fastboot screen.
Any thoughts?

1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2

YasuHamed said:
1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after work.

OP3 bricked and now won't boot after MSM

Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX

AnnoyingZlatan said:
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
Click to expand...
Click to collapse
If you can get to bootloader, download and flash OOS 5.0.6. If not, try one of the MSM Tools on XDA. There are quite a few of them, search. Please also note that the Tool is different for 3 and 3T.
I had used one of the oldest Tools here on XDA a couple of times without any hiccups.

Did you get a solution to this? I am struggling with the same issue.

Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..

myserver57 said:
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
Click to expand...
Click to collapse
Did you try to sideload OOS using adb? Try the various versions of OOS.

TNSMANI said:
Did you try to sideload OOS using adb? Try the various versions of OOS.
Click to expand...
Click to collapse
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).

myserver57 said:
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
Click to expand...
Click to collapse
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.

TNSMANI said:
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
Click to expand...
Click to collapse
Thanks again for trying to help.
Sadly, bootloader is locked so flashing TWRP or even booting to TWRP is a no-go.
I don't think it's a hardware fault since it was working fine before the OTA update, but I guess you never know. Damn, if only sideloading would work, darn thing...