[Q] fastboot flash system system.img FAILED <remote: Permission denied>, need fix - ZenFone 2 Q&A, Help & Troubleshooting

[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.

Related

[Q] Galaxy Nexus Root and Fastboot not working

My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250

Stuck in an infinite loop

Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!
Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime
Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app
Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!

[Q] Stuck in recovery with Fastboot and ADB failure

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

Galaxy Nexus reboot loop flashing error FAIL Exceed Buffer Size

My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
celeadyne said:
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
Click to expand...
Click to collapse
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
pattyboi:) said:
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
Click to expand...
Click to collapse
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
celeadyne said:
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
Click to expand...
Click to collapse
i mean not using toolkit,using actual fasboot. BTW: do you have a custom recovery? if so you could just adb sideload & if you can get the phone into fastboot mode and just flash a recovery then adb sideload after wiping all partitions && did you try using odin to flash back to stock (i dunno if there are odin images available,i apoligize if not)

my phone keeps booting into fastboot mode

hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
zsnorow said:
hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
Click to expand...
Click to collapse
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
XSL-FO said:
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
Click to expand...
Click to collapse
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
zsnorow said:
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
Click to expand...
Click to collapse
http://teamw.in/project/twrp2 and click on the upper right Get TWRP for your device.
Choose your device recovery and download the adb version. That is the .img
Once you have downloaded TWRP put it on your desktop.
Connect your device with your laptop/pc with the unknown sources checked also the usb debugging checked.
Move your mouse over a free space on your desktop, click once just to be sure there is no app or file clicked.
Then press shift and keep it pressed while you right click your mouse.
Press open command window here
in that command window type : adb devices
if you see a serial number type : adb reboot bootloader
then type : fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot reboot
openrecovery-twrp-2.8.1.0-m8 : This is an example, you will write the name of your recovery but it should be pretty much the same.
Good luck.
Are you familiar with
adb/fastboot commands?
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
spinninbsod said:
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
Click to expand...
Click to collapse
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
ive tried everything
jball said:
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
Click to expand...
Click to collapse
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
i honestly cant remember everything i did
jball said:
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
Click to expand...
Click to collapse
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
You say "pushing a ROM" with what?
You don't push a ROM with TWRP you just flash it.
Or are you talking about pushing the ROM with fastboot?
If you have TWRP than download a stock backup and flash it.
Take a long look at my profile man and if you look just right you will see I've done and asked some stupid things in my travels here on XDA.I can tell you I remember every phone and ridiculous thing I've done to each of them,I still feel crunchy when I think of the mistakes.
We really need more info about the full process.please I'm not trying to offend you and I'm trying to help
zsnorow said:
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
Click to expand...
Click to collapse
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
same thing happened with me but i remember what i did
redpoint73 said:
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
Click to expand...
Click to collapse
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
farhanakhtar39 said:
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
Click to expand...
Click to collapse
Your device is M8 dual SIM .. mm-su-boot is for M8 single SIM, won't work on your device.
Install custom ROM with support for Dual SIM or restore your stock ROM backup
please can you provide any link of the rom for dual sim addition
farhanakhtar39 said:
please can you provide any link of the rom for dual sim addition
Click to expand...
Click to collapse
Not so sure,
if Sense ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
maybe S.ROM too has dual SIM support, you need to ask in their thread
https://forum.xda-developers.com/ht...the-worlds-first100-m9-port-m8upload-t3064838
if non-Sense ROM
CM13 ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-cyanogenmod-13-0-experimental-t3259068
Nougat ROM -
https://forum.xda-developers.com/showthread.php?t=2753248
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
https://forum.xda-developers.com/ht...cyanogenmod-14-1-htc-one-m8-dual-sim-t3507192
There are a few more that support Dual SIM but you have to check & ask in their development thread as I'm not familiar with most of the available custom ROMs .. I don't try most of them
Thnks
Thanks buddy it worked
cm 13 worked for me !
God bless you
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
My phone is having similar issues
Stanna16 said:
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
Click to expand...
Click to collapse
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
pancho2009 said:
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
Click to expand...
Click to collapse
You only flashed TWRP onto the phone? Or did you root also?
Not nearly enough info to provide the proper help.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
What version TWRP?
What version SuperSU did you flash (if you got that far)?

Categories

Resources