I need some help. It seems like I am in a circular conundrum and have tried almost everything. A quick summary of how far I've gone (and searched): gone as far as successfully performing a stock reflash, but the boot loop is still there. I realize this could be a hard failure, but even so, shouldn't there be a log stored somewhere to tell me what failed?
An abbreviated list of things I've tried (many times w/ varying parameters where possible):
- wipe cache
- factory data reset
- reflash stock using ODIN
- flash TWRP (failed: Complete(Write) operation failed)
Here's what I CAN do: boot into download mode, connect with ODIN, boot into recovery mode.
Here's where I get into some circular issues. The next thing to try was unlocking, rooting and installing a custom ROM.
Any of those things seems to require being able to boot or have USB debugging enabled. So to summarize my last known configuration:
(1) USB debugging apparently disabled
(2) Samsung reactivation lock enabled
(3) Encryption probably enabled
So how do I get a custom ROM installed with all these not in my favor?
Unlock bootloader: root and/or adb push access required.
--> I can't adb push because USB debugging disabled.
--> I probably can't adb push to that location/chmod because I don't have root
--> I can't root because it seems all the root methods require a booting device to start with
I CAN/should be able to adb sideload (I have been able to get the device to show up with adb via going into stock recovery then apply update with adb, but not sure what to sideload)
Thanks in advance for any help you can provide!
termiflyer said:
I need some help. It seems like I am in a circular conundrum and have tried almost everything. A quick summary of how far I've gone (and searched): gone as far as successfully performing a stock reflash, but the boot loop is still there. I realize this could be a hard failure, but even so, shouldn't there be a log stored somewhere to tell me what failed?
An abbreviated list of things I've tried (many times w/ varying parameters where possible):
- wipe cache
- factory data reset
- reflash stock using ODIN
- flash TWRP (failed: Complete(Write) operation failed)
Here's what I CAN do: boot into download mode, connect with ODIN, boot into recovery mode.
Here's where I get into some circular issues. The next thing to try was unlocking, rooting and installing a custom ROM.
Any of those things seems to require being able to boot or have USB debugging enabled. So to summarize my last known configuration:
(1) USB debugging apparently disabled
(2) Samsung reactivation lock enabled
(3) Encryption probably enabled
So how do I get a custom ROM installed with all these not in my favor?
Unlock bootloader: root and/or adb push access required.
--> I can't adb push because USB debugging disabled.
--> I probably can't adb push to that location/chmod because I don't have root
--> I can't root because it seems all the root methods require a booting device to start with
I CAN/should be able to adb sideload (I have been able to get the device to show up with adb via going into stock recovery then apply update with adb, but not sure what to sideload)
Thanks in advance for any help you can provide!
Click to expand...
Click to collapse
You'll definitely have to get your device booted in order to root / unlock your bootloader. You need su permission during the adb part of the unlock process which is where the temp root from kingroot comes in to play. I would recommend trying to download and install the full official firmware of BPA1 and flash it in Odin. You won't be able to flash TWRP or anything else until you get your bootloader unlocked and that will require you to be on the BPA1 firmware. So that's where I would start.
Related
Hey guys/gals, I have an Evo 4g with the digitizer and screen removed. I recently RUU'd it to 4.67.651.3 and have unlocked the bootloader via HTCDev. I have fastboot access, and only have adb access via a custom recovery. I don't actually have a custom recovery installed, Note that I am just booting one with "fastboot boot custom_recovery.img".
I am aware that a flag is set in "/data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml" when the box is checked (Debugging) in the gui. And I have been able to mount the data partition in recovery and push that file to the phone (with "<boolean name="enable_adb" value="true" />" set). I then set the ownership and permissions based on what they are in the android emulator, but when I boot the phone I don't get adb access.
I also have a userdata.img backup for when it was on 3.70.651.1 with adb enabled. However it is a backup made inside android via "mkyaffs2image -f /data /sdcard/userdata.img" and is not flashable via fastboot or flash_image. I'm not even sure it will work if I did manage to flash it back.
So my question is, how would I go about enabling adb in the actual rom? Or how could I flash the userdata.img backup I have?
EDIT: As an alternative, could someone provide an absolutely stock (with adb enabled) 4.67.651.3 userdata.img that I can flash to my phone?
I found a solution.
I flashed a custom boot.img that has adb enabled by default. The persist.service.adb.enable flag in default.prop needs to be changed from "persist.service.adb.enable=0" to "persist.service.adb.enable=1". Adb will remain enabled even after completely wiping the data partition.
It was a good thing that the bootloader was unlockable without a functioning screen, otherwise this wouldn't be possible.
It's just too bad there isn't much I can do with the phone in its current condition.
Hi I have the same problem but have not been successful in enabling the debugging mode. Any chance you can share the custom.boot.img you used to enable adb?
lmntone said:
I found a solution.
I flashed a custom boot.img that has adb enabled by default. The persist.service.adb.enable flag in default.prop needs to be changed from "persist.service.adb.enable=0" to "persist.service.adb.enable=1". Adb will remain enabled even after completely wiping the data partition.
It was a good thing that the bootloader was unlockable without a functioning screen, otherwise this wouldn't be possible.
It's just too bad there isn't much I can do with the phone in its current condition.
Click to expand...
Click to collapse
yangkx said:
Hi I have the same problem but have not been successful in enabling the debugging mode. Any chance you can share the custom.boot.img you used to enable adb?
Click to expand...
Click to collapse
Sure. You must be HTCDev unlocked though. Then you can "fastboot flash" or "fastboot boot" the boot image.
Also, just saying...I shall not be held responsible for any damage resulting from improper use of fastboot and/or the provided boot image.
[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix
Hey,
I have a ZE551ML and want to install CM. I am following the guide here. I have run into a problem on the first step which points to the guide here. At step 7 of this guide it has me use the command: fastboot flash system system.img. This fails with the error in the title of this post: FAILED <remote: Permission denied>. I have been googling this and no one has a concrete solution. Currently my phone will not even boot as the three fastboot commands before this one worked just fine and replaced the files. Any help would be greatly appreciated!
Cheers,
Eric.
Even though it'll say permission denied, flashing recovery WILL work. From there you can either flash a custom ROM (from twrp) or reflash stock firmware (through stock recovery).
That's the only fix I've found. To flash a usable ROM and boot into it. May need to turn on USB debugging in dev options. But after doing those two things, fastboot will stop with the permission denied issues.
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
eric_lensherr said:
Hey, thanks for the quick reply.
Currently the phone does not boot at all.
What do you mean by flashing recovery?
When I enter recovery mode at the moment it says applying update and then gives me the android on its side with the red triangle and error! below it.
So i can't currently flash though recovery mode as far as I can tell.
Click to expand...
Click to collapse
Found a guide here dealing with this error, working on it.
Hey,
So I got my phone unbricked by flashing the recovery with the stock ASUS firmware "ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V2.19.40.22 for WW SKU only" available at the ASUS official website and following a guide at an outside link that I can't post.
Now, I have enabled developer mode and turned on USB debugging but am now getting the permission denied on all fastboot commands of the OTA guide, step 7.
Does anyone know a good next step?
Hey, managed to root the phone with: Temporary CWM
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
rlaw said:
After setting USB debug on did you connect the phone to PC via USB and authenticated the PC? When you connect the phone to PC via USB with debugging on, it should pop up a window on the phone after a few seconds asking you for permission for the PC. You can checkmark the box that says always trust this computer's RSA fingerprints or something along those lines.
Hope this helps!
Click to expand...
Click to collapse
Yes, I did do this but I have now checked the check mark to make it always trust my computer. I then booted into fastboot but still get permission denied despite having root through CWM and having this checked off.
When I got root through CWM by the fastboot tethered recovery it gave me permission denied on all steps but it still booted into CWM recovery. I was then able to install SuperSU to root it, though it gave me an error, and I used Root Checkerr to see if the phone was rooted. It says it is but I am still unable to flash any images onto the phone since I re-installed the stock firmware.
I'm super confused about this whole thing, IDK what to do now.
Flash stock recovery again and adb sideload the stock firmware all over.
This is the latest up-to-date 2.20.40.59 firmware: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.59-user.zip
If that doesn't work then idk. You can Google the permission denied errors for fastboot like I did and there are various possible problems/solutions.
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
rlaw said:
You can still flash recovery via fastboot even though it'll say permission denied it works. That's all you really need to do as you can install stock firmware via stock recovery or flash ROMs and whatever else through twrp recovery.
Click to expand...
Click to collapse
How can i tell if twrp recovery is successfully installed?
Hey, took a few days to cool off.
So it does seem I can replace recovery even though it says permission denied. I do this by using fastboot to flash the recovery, then from the bootloader on the phone I select restart bootloader and then when the bootloader re-appears I enter recovery mode ( I do this to prevent the possible replacing of the custom recovery by the stock OS). However recovery mode never boots when the latest twrp recovery is on the phone, I just end up back in the bootloader. When I flash the stock recovery back on this method successfully enters recovery mode. This also occurs if I just directly enter recovery mode after flashing twrp recovery.
Any thoughts?
eric_lensherr said:
So, none of this is working.
I installed the latest firmware as you suggested and got root again by using Temporary CWM. However despite anything I try (been googling for hours with little help found) I cannot get the phone to let me flash anything I always get the permission denied error.
Click to expand...
Click to collapse
Same here. I'm using elevated cmd, and fastboot is recognizing my device. But I can't flash anything, can't erase cahce, can't reformat partitions. Always failed due to permissions. And I'm stuck in a bootloop, and can't get to recovery (it just goes back into the bootloop when I try). Literally the only avenue I have to interact with this phone is fastboot, and I can't do anything with it.
Ok so I easily flashed the modded boot image, unlock bootloader, installed twrp, rooted and everything.
When my phone is on and I have usb debugging enabled on, and I do adb devices I see the serial number and my phone is detected
I can even do adb reboot bootloader and works
but when I reboot to bootloader that's when my phone isn't found
what's weird was I tried following the Return to stock thread (long way because BAT wasn't working) I was manually able to flash a few of the files but when I got to fastbooting system.img, that's when it kept giving me an error
Can anyone help? I don't understand how it detects it and then it doesn't :crying:
Mini fastboot installs cause system.img to fail, downloaded full android sdk and worked!
PLEASE CLOSE
To address the initial query though, the answer is no - one cannot return a device with a custom recovery/ROM etc. installed. The device must be returned to stock in order to be acceptable for return.
Hi,
Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled.
This tutorial works for Beta Android O bootloop too.
You will need:
ADB + drivers installed: https://forum.xda-developers.com/showthread.php?t=2588979
Nexus toolkit: DL.- http://www.wugfresh.com/nrt/
STOCK image archive, older than you have now - https://developers.google.com/android/images#bullhead
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
screen: https://postimg.org/image/kkk9h92oz/
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope, this tutorial is useful for you, if yes, please hit thanks button.
And sorry for my english.
GREAT!!! Saved my phone. Thank you very much!
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Ins1d3r said:
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
Click to expand...
Click to collapse
You not need usb debugging enabled in system.
Communication with pc is working in fastboot and recovery.
Redmi Note 3 - Tapatalk
any idea how to do it in mac?
What do you mean with: "Copy downloaded OTA ROM archive in ADB folder."
Just sideloading doesn't work.
ADB cant find my 5x...
Thank you OP for this i am need of help and it appears your solution has found me. Im on holiday atm and my nexus 5x just got the dreaded bootloop! Alll i see is the spinning colors for android logo after pin code is inputted.
Im very anxious to backup my photos of my son and family, so want to ask is this method safe? I dont want to risk losing data.. i can get into recovery mode and my phone is boot locked and not rooted, so can someone also tell me if adb backup will allow me to backup my pictures and video reliably? I will do a full backup and then try and flash the OTA.
serving: 'bullhead.zip' (~47%) * failed to read command: No error , what im doing wrong ?
ok succeed after dozen attempts , phone booted to main desktop work for like 5 mins and then frozen , looks like it went back to bootlooping ;(
Hi guys, same situation, since yesterday I could boot with a bit of effort (like waiting 15 minutes of bootloop) but now the 5x doesn't boot at all and so neither in recovery. My phone is locked and never modded so I will send in warranty when I will be back home ( 10 days). So now I would like to fix it to use it at least in this week, but how can I do if I can't boot in recovery?
I can just boot in the bootloader so use fastboot command...if I unlock the bootloader I will get the little lock in the bottom part of the screen, when I will lock it to send it to LG will it disappear?
How exactly is this toolkit's fastboot flashing supposed to work if you have a locked bootloader?
How is using this toolkit any different from running the "flash-all.bat" that's included with factory images?
This did nothing at least in my case.
I get the feeling that the flash operations are failing and the toolkit just disregards this.
Cannot enter recovery
I completed the first step in fastboot but when i try to enter recovery it goes to bootloop again....what should i do?
Nope, not working. Rebooting again and again. Issue not resolved. Please help!
Hi I need help,
what do i choose when i click 'system' tab?
[/QUOTE]
rockhardy said:
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Click to expand...
Click to collapse
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
jcfortunato said:
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
Click to expand...
Click to collapse
It's been a while since I tried it. But as far as I remember it was due to phone not being in recovery mode. I hold the power button until the phone screen went off. And while holding the power button I instantly pressed volume down button to bring back the fastboot mode and then recovery mode.
i'm sorry but i don't see my latest build (currently running on 7.1.2)
i've tried using 'any build', it said that i have to choose one of the build listed :/
thank you
-----
edit
found them!
but it says that my OTA is out ouf date
I downloaded the latest one though (August)
where did I go wrong? :/
Anyone still doing this ha? I've just run into this issue with my wife's phone, and there are things on there she needs..
The ones with issue with the big cores causing bootloops, use this guide to unlock device then proceed with following guide
https://forum.xda-developers.com/showthread.php?t=3641199
Sent from my Nexus 5X using Tapatalk
Hello, I've done all the procedure until reboot recovery, but I've didn't find the button for select apply update from adb in NRT.
Edit: Issue resolved
Hello everyone,
Pardon my lack of knowledge on rooting devices and all the related things. This is my first time attempting to root a device and I am having a lot of trouble understanding how to go about things. Through my research, I'm finding a lot of different ways to do things and I want a direct opinion on my process so I don't mess up my phone. (Through as much research as I could) My end goal is to have TWRP flashed to my phone, root my device and install a custom ROM. My understanding is that I first need to unlock the bootloader, flash TWRP, install SuperSU, then flash the custom ROM. I won this phone from a raffle and I'm trying to root from a Windows 10 laptop.
I have the TWRP and SuperSU files at the ready and have also installed Kingo root. I enabled USB debugging and allowed the bootloader to be unlocked in developer settings. I tried to boot into download and bootloader and successfully recognized my device, but when trying to use "fastboot flash recovery twrp-3.2.3-0-hima.img" it gave me the error message "FAILED (remote: cannot flash this partition in s-on state)" and "FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)"
I'd assumed my phone was already unlocked but that's obviously not the case. Doing some more research I found a lot of people needed to get a bootloader unlock from HTCdev.
Is this what I need to do now to continue?
What about this "s-on state" how can I turn it off?
Will unlocking the bootloader wipe my device?
Could I just use the "root" button in the Kingo root main app?
Can anyone verify my theoretical steps and give quick notes on how I should be doing them properly?
Any help is greatly appreciated
dont worry i will help you
Download all in one Android toolkit for your PC...
https://www.google.com/url?sa=t&sou...FjAAegQIBRAB&usg=AOvVaw0sohDTlAE3UaLSgUihYhS3
and connect your phone to PC and allow USB debugging after that
go to Android all in one toolkit and select unlock bootloader....on the screen of your phone it would ask you if you want to unlock bootloader press volume up for yes
volume down for no
Select yes...but
Note:It would reset everything on your phone so back up your necessary files
Make sure you download the right twrp image for your phone (Google search)
Move the Twrp.img to your PC local directory folder and rename it to TWRP.img ....next step is to:-
next step is to go to windows command prompt on your PC and type the following commands:-
Adb devices
Adb reboot bootloader
Fastboot devices
Fastboot flash recovery TWRP.img
Note:make sure you reboot your phone to recovery before normal reboot so that it would replace your previous stock rom
Go to twrp and install the latest version of super su
https://download.chainfire.eu/696/supersu/
This steps worked for me it can work for almost all types of phone
my name is Iduh Winner
I was a root struggler like you...all thanks to God ....I love you all for more info contact me on the following social media
facebook:Iduh Winner
YouTube:Iduh Winner