N/M, managed to flash RUU and get back to fastboot recovery. I'm sure I can make this work from here.
I was attempting to updated my firmware and then flash a stock rom to correct some GPS and network issues I've had running Santod's 4.4.2 rom. The Firmware flash failed but because I'm an idiot I rebooted my phone. Now I can't access ADB, fastboot commands run but don't work and my phone is stuck on a black HTC screen with an error triangle in each corner. Can anyone suggest what I should do? Am I totally out of luck here?
OK, I think I'm in serious trouble here. This is where things stand. I've got updated firmware and recovery installed. I have fastboot, but no ADB. I've attempted reinstalling drivers, using different ports, the lot. ADB is just not going to happen as far as I can tell. I have no rom on my SD card because in the course of all this madness, my SD card was wiped. I have attempted to use fastboot flash zip commands to push sense and GPE roms, but I get the following error: FAILED (remote: 24 parsing android-info fail). I've been able to get CWM and TWRP recoveries installed but because I don't have any zips on my sdcard, they are useless. Since I can't get ADB to recognize my phone, the ADB sideload options don't work either.
This is now the chronicle of my attempt to get my phone back. After uninstalling/deleting all the HTC drivers as well as the complete Android SDK, reinstalling the SDK, installing the universal naked driver, I finally have ADP talking to my phone. Right now I'm pushing the latest stock rom to my phone. Cross your fingers, me!
How did it go? Are you up and running?
Related
Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?
You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse
After installing CM12, I got a random reboot and it asked me to enter my password. It accepted my password and said that my files were corrupt. I rebooted into recovery, and was unable to install any zip files or wipe anything. I tried installing stock recovery, locking bootloader, and installing the RUU (via the .exe and the .zip in hboot) and now I cannot get to a ROM or recovery. I also tried installing TWRP and was unable to boot that as well. I do have HTC Sync manager installed. I also tried the Windroid Universal Android Toolkit, which did not seem to do anything either.
If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.
FoxyDrew said:
If you have the proper drivers, and followed all the instructions in the RUU thread, and you still can't boot to system or recovery, your beyond screwed.
There's more than likely no hope. Maybe some other brilliant mind on XDA can figure something out.
Click to expand...
Click to collapse
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/
When trying to flash an RUU through fastboot I get: sending 'zip' (size) ...OKAY [time]
writing 'zip" ... FAILED: Remote not allowed
When doing fastboot update I get: Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '`√'
FroyoShark said:
It claims that installing recoveries and zips through fastboot is successful. Is there some kind of OEM recovery thing like there is with other phones? (i.e. what the OEM's use to initially flash the device)
EDIT: Here's a post on reddit that is exactly what is happening for me: http://www.reddit.com/r/AndroidQues..._recovery_wont_start_stuck_in_bootloader_htc/
Click to expand...
Click to collapse
A RUU is from the OEM, it's what they use.
In the RUU thread I linked you too try the download link from the original HTC site, and screenshots of the errors your getting would help.
[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.
Hi all, long time lurker, first time poster. Before I start, want to apologize for bringing up a regular problem. So I have a second hand one x. Last year decided to root, had a few teething problems but managed it, all was well. Then I got 'too big for my britches.' Decided to update my recovery, didn't check battery and it died halfway through. Thing wouldn't work for ages, no charging, wouldn't turn on etc. Gave it up as hard bricked. Decided the other day for some reason to try it on charger and it charged! Thought I was winning, wrong lol. Successfully flashed new recovery. Tried nandroid backups, (yes I actually did what instructed and made some, lol) seemed okay but when rebooting just kept throwing me to recovery. Then, like an idiot, stumbled across a post, (can't remember where) that gave the 'bright idea' of formating. EVERYTHING. yeah I know, idiot, right here. No more nandroid backups, no ROM. Can't flash a ROM now cos my sd card can't mount, and sideload doesn't work as when in recovery adb can't find device. Any help would be appreciated, been all over this wonderful sight and others and no fixes seem to work for me. So sorry for long post. Oh, its an international model, hboot is 1.73
Update: flashed twrp 2.8.0.0 last night, still can't sideload anything. When using command adb devices shows xxxxxx recovery, but when issuing command adb sideload filename.zip getting error:closed. This is so frustrating aaaah! Can flash any recovery no problems but since I'm unable to mount USB and sideload isn't working am unable to flash a ROM. Tried installing universal adb driver, it installed but changed nothing. Please help!
Solved!
Ganglore said:
Update: flashed twrp 2.8.0.0 last night, still can't sideload anything. When using command adb devices shows xxxxxx recovery, but when issuing command adb sideload filename.zip getting error:closed. This is so frustrating aaaah! Can flash any recovery no problems but since I'm unable to mount USB and sideload isn't working am unable to flash a ROM. Tried installing universal adb driver, it installed but changed nothing. Please help!
Click to expand...
Click to collapse
Okay, so I did it! I will leave this here in case it helps anyone.
I deleted htc drivers then reinstalled them. Manually installed adb driver from sdk, device was recognised in adb in sideload mode! I.E. instead of saying xxxxx recovery as mentioned above it said xxxxx sideload. Successfully sideloaded cm 11 nightly I had. Rebooted recovery, installed zip from SD under sideload.zip. rebooted to bootloader, flashed boot.IMG that was inside cm11 zip, then used fastboot erase cache command, rebooted, SUCCESS! CM ROM is on and working! Thanks to everyone who took the time to write the numerous tuts etc I perused before FINALLY fixing this mess. Just downloading compatible gapps now to install. Only problem I have now is its not recognizing my sim card..... *sigh* now to sort that out.