Develop Bugs

Cannot install Recovery 3.0

SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.

James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?

ianmcquinn said:
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
Click to expand...
Click to collapse
Yes I have flash_image in my tools folder :/
Does that answer the question?

James_Caliber said:
Yes I have flash_image in my tools folder :/
Does that answer the question?
Click to expand...
Click to collapse
Do you have an ENG. Hboot? If not, you can not use fastboot, youll have to flash recovery from terminal using flash_image.
Edit: See in your first post says you have HBoot installed, you mean ENG. Hboot right?
If you do have ENG. Hboot type
Code:
fastboot devices
Do you get a "serial # fastboot" ?
See if you have the right drivers installed. I had ADB up and running but when I tried fastboot it would not recognize my G2 so I had to install new drivers.

James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img

EdKeys said:
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
Click to expand...
Click to collapse
If you want to use flash_image, you need to place the binary on your phone and make it executable. The guide I linked to explains exactly what you are supposed to do.
For fastboot, do you have recovery.img in your tools directory?

I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.

PatrickHuey said:
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
Click to expand...
Click to collapse
Not exactly sure what you are saying about pushing things through terminal and the binary method, but if you want to use flash_image, you should follow the guide I linked to.
If you want to use flashboot, you need to make sure you have the engineering hboot (if you boot you phone while holding volume down, the first line should say something like ENG S-OFF instead of SHIP S-OFF).
If you want yet another method to flash the recovery, there is also the sticky at the top of this forum.

i found this to be the best and easiest way to flash CWM recovery 3.0.0.5
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
Click to expand...
Click to collapse

If you rooted using rage, the flash_image kernel should be on your phone.

blackknightavalon said:
If you rooted using rage, the flash_image kernel should be on your phone.
Click to expand...
Click to collapse
I don't think that's true. Temp rooting with rage doesn't install any apps for you by itself (and the temp root to perm root guides only install Busybox, SuperUser, and the su binary). It's just that most people flash a custom rom after rooting, and many of those roms include flash_image. If you rooted and then stayed on stock for example though, you would have to get the flash_image program yourself (and it's something independent of the kernel).

[Q] Incredible won't boot into Clockwork

Alright, I have been searching around for my problem and I have found no such luck. I am running Evervolv ICS ROM Preview 8 and I noticed they released Preview 9. So I decided to upgrade of course but I came across a snag. My phone just boot's into the stock recovery and not into Clockwork. I have found a similar problem in another forum but I am unable to post the link do the rules of this forum.
The problem being that I cannot turn off FASTBOOT, I have no selection to do so in my phones settings.
Any help at all would be wonderful.

Hadonka402 said:
Alright, I have been searching around for my problem and I have found no such luck. I am running Evervolv ICS ROM Preview 8 and I noticed they released Preview 9. So I decided to upgrade of course but I came across a snag. My phone just boot's into the stock recovery and not into Clockwork. I have found a similar problem in another forum but I am unable to post the link do the rules of this forum.
The problem being that I cannot turn off FASTBOOT, I have no selection to do so in my phones settings.
Any help at all would be wonderful.
Click to expand...
Click to collapse
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
If you can boot into the stock recovery then fastboot is not the issue. If fast boot is enabled holding vol down and power just boots the phone, you will not enter any recovery. The only way to enter recovery with fastboot enabled is to pull the battery truly powering off the phone, fastboot does not power of but hibernates for faster boot.

cmlusco said:
Are you s-off? If so flash cwm recovery thru hboot as a PB31IMG.zip
If you can boot into the stock recovery then fastboot is not the issue. If fast boot is enabled holding vol down and power just boots the phone, you will not enter any recovery. The only way to enter recovery with fastboot enabled is to pull the battery truly powering off the phone, fastboot does not power of but hibernates for faster boot.
Click to expand...
Click to collapse
Yes I am S-OFF, how do I flash through hboot? This does not fully answer my question of why I am unable to boot into Clockwork and how to fix this issue.

Hadonka402 said:
Yes I am S-OFF, how do I flash through hboot? This does not fully answer my question of why I am unable to boot into Clockwork and how to fix this issue.
Click to expand...
Click to collapse
Well if you are getting the stock recovery then i assume cwm recovery is not installed. Flashing the file above will install it.
To do so download the file and place it on your sdcard in no folders.
Power off the phone and pull the battery, then reinsert.
Hold vol down and power buttond till a white screen pops up (hboot). Wait a couple secs and hboot will find the file, parse it, and then prompt to press vol up to update. When its donr it will prompt to press vol up to reboot or vol down not to. Press vol down and then scroll to and select recovery. You should now be where you want to be.

cmlusco said:
Well if you are getting the stock recovery then i assume cwm recovery is not installed. Flashing the file above will install it.
To do so download the file and place it on your sdcard in no folders.
Power off the phone and pull the battery, then reinsert.
Hold vol down and power buttond till a white screen pops up (hboot). Wait a couple secs and hboot will find the file, parse it, and then prompt to press vol up to update. When its donr it will prompt to press vol up to reboot or vol down not to. Press vol down and then scroll to and select recovery. You should now be where you want to be.
Click to expand...
Click to collapse
I'm sorry I was not clear before, forgive me. Yes Clockwork is installed, I have reflashed it with the current version and older versions to attempt to fix the problem. I tried another recovery as well (One that I cannot recall at the moment) and I still boot into the stock recovery. My main problem is that I cannot boot into Clockwork. I'm sorry again for not being specific before.

Hadonka402 said:
I'm sorry I was not clear before, forgive me. Yes Clockwork is installed, I have reflashed it with the current version and older versions to attempt to fix the problem. I tried another recovery as well (One that I cannot recall at the moment) and I still boot into the stock recovery. My main problem is that I cannot boot into Clockwork. I'm sorry again for not being specific before.
Click to expand...
Click to collapse
Have you tried using rom manager to install cwm, and using the erase recovery before flashing option in its preferences?
What hboot version are you on?

cmlusco said:
Have you tried using rom manager to install cwm, and using the erase recovery before flashing option in its preferences?
What hboot version are you on?
Click to expand...
Click to collapse
Yes I have done that and still no luck. I am using, HBOOT-0.92.0000

Hadonka402 said:
Yes I have done that and still no luck. I am using, HBOOT-0.92.0000
Click to expand...
Click to collapse
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?

cmlusco said:
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?
Click to expand...
Click to collapse
No I do not, should I go ahead and get that setup? Before I forget thank you for being patient and helpful this far, I appreciate your help so far.

Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract it to C:\. You should now have an ADB folder on the C:\ drive (C:\ADB), which contains adb.exe and fastboot.exe. Then follow this guide to setup the drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Once that is setup and working download this zip file ( http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd_recovery.zip ), unzip it, and place the 2 files on your sdcard in no folders.
Make sure usb debuging is checked on in menu - settings - applications - development
Power off the phone pull the battery and reinsert. Plug the phone in to the pc and hold vol down and power till hboot comes up. Select fastboot, it should say in red near the top fastboot usb. Then type the folowing in a cmd prompt:
fastboot erase recovery
Once complete reboot the phone.
Set the phone to charge only.
Open a command prompt on your PC and navigate to the same folder as your fastboot.exe file, (example type: cd C:\ADB ).
Type the following into the command prompt pressing the enter key at the end of each line:
adb shell
(You should now get a pound sign #)
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
Then try to see if you can access cwm recovery.

cmlusco said:
Hmmm very strange. Do you have a pc with adb and fastboot setup on it?
Click to expand...
Click to collapse
cmlusco said:
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract it to C:\. You should now have an ADB folder on the C:\ drive (C:\ADB), which contains adb.exe and fastboot.exe. Then follow this guide to setup the drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Once that is setup and working download this zip file ( http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd_recovery.zip ), unzip it, and place the 2 files on your sdcard in no folders.
Power off the phone pull the battery and reinsert. Plug the phone in to the pc and hold vol down and power till hboot comes up. Select fastboot if not already selectef for you. It should say in red near the top fastboot usb plug. Then type the folowing in a cmd prompt:
fastboot erase recovery
Once complete reboot the phone.
Set the phone to charge only, and make sure usb debuging is checked on in menu - settings - applications - development.
Open a command prompt on your PC and navigate to the same folder as your fastboot.exe file, (example type: cd C:\ADB ).
Type the following into the command prompt pressing the enter key at the end of each line:
adb shell
(You should now get a pound sign #)
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
Then try to see if you can access cwm recovery.
Click to expand...
Click to collapse
I got an error called Segmentation Fault.

Hadonka402 said:
I got an error called Segmentation Fault.
Click to expand...
Click to collapse
Sounds like the recovery partition may be corrupt, nothing will write to it. Well if i were you i would do an ruu and see if that fixes it. Not much else you can do i dont think. Hopefully the ruu will fix it and allow you to flash cwm.

How do I go about doing ruu?

Hadonka402 said:
How do I go about doing ruu?
Click to expand...
Click to collapse
Download this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and here is a good write up on how to flash it. http://pvillecomp.com/?page_id=79. Its the same way you flashed the cwm file earlier in post 2, thru hboot as a PB31IMG.zip

cmlusco said:
Download this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and here is a good write up on how to flash it. http://pvillecomp.com/?page_id=79. Its the same way you flashed the cwm file earlier in post 2, thru hboot as a PB31IMG.zip
Click to expand...
Click to collapse
Note that doing an ruu will wipe yout phone and you will ne back to stock. If after doing so you still cant get a recovery to flash, you will be stuck on stock.

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

[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

I think I may have ruined my phone

Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Edit: In the fastboot screen at the top it says ***Tampered*** ***Relocked*** ***security warning**
also when i try to press recovery it shows the htc screen for 1 second then back to the same menu
i found this http://forum.xda-developers.com/showthread.php?t=2710735 but i cannot even get into recovery

haydenrbm said:
Hey there
I want to start off by saying I have very little experience with rooting, but am very familiar with jailbreaking apple devices so I figured i could manage.
I have a htc one m8 on rogers network locked. I rooted it and had super user and all that jazz, then flashed AOKP. Then I thought i actually liked the stock HTC sense better, so I tried to "get things back to normal"...lol.
Now im at the point where if i turn my phone on it goes straight to the fastboot screen(?) with all the "fast boot, recovery, factory reset, etc". Since I'm super new to all of this is there anybody that can write some instructions on how to get my phone back to stock? I would really appreciate it after panicking over this for 3 days.
Click to expand...
Click to collapse
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?

Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.

MattMJB0188 said:
While being an expert with rooting and flashing custom recoveries on Samsung devices, I am also new to the world of HTC. Out of curiosity, what happens when you hit factory reset?
Click to expand...
Click to collapse
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
ashyx said:
Unlock the boot loader again then install twrp recovery then head over to the stock backup thread and flash one of the nandroids for your cid.
Click to expand...
Click to collapse
I would...but when im trying to use ADB devices it isn't found

haydenrbm said:
When i hit factory reset it the screen changes to the HTC in green for 1 second then back to where i started
I would...but when im trying to use ADB devices it isn't found
Click to expand...
Click to collapse
Do fastboot devices ... adb commands itself won't work in bootloader, it has to be fastboot commands.

now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps

mushages said:
now you have a locked bootloader which means you cant do anything.. so your first step is to unlock it again then flash a custom recovery (TWRP) after that flash the stock rom+ boot.img ( to be safe) make sure it boots. RELOCK the bootloader then flash your firmware.zip.. hope it helps
Click to expand...
Click to collapse
How can I unlock the bootloader again without the device showing in adb?

haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
i think you have your unlock token. start from here
http://www.htcdev.com/bootloader/unlock-instructions/page-4/

haydenrbm said:
How can I unlock the bootloader again without the device showing in adb?
Click to expand...
Click to collapse
If it's in bootloader it should show in command prompt when you type fastboot devices after connecting it to PC. If it doesn't then there is a driver problem perhaps. Check to make sure you have HTC drivers installed, or reinstall them. Might as well make sure adb is up to date as well, can do that through the Android SDK Manager. Another possibility might be that the usb cable isn't working correctly, try another cable. Fact of the matter though is, if it's in bootloader and you connect it to the PC adb/fastboot SHOULD pick it up.
So check and fix those things. Also make sure you use the correct commands, in bootloader mode, it'll be fastboot commands, not "adb devices" but "fastboot devices" ... "fastboot reboot" etc etc. Also make sure you're running the commands from within the adb/fastboot folder path(just for in case yeah...)

mushages said:
i think you have your unlock token. start from here
Click to expand...
Click to collapse
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.

haydenrbm said:
Okay it is unlocked, but now it just stays on the AOKP boot screen
Thank you for the help btw, it must be very painful.
Click to expand...
Click to collapse
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups

BerndM14 said:
Press Volume UP + Power button, once the screen goes dead, press Volume DOWN + Power button to get back into bootloader. Then flash a custom recovery (Like TWRP) and start flashing the Stock nandroid backups, can be found from here Collection of Stock backups
Click to expand...
Click to collapse
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone

haydenrbm said:
Okay i have got into the bootloader now, thanks.
the adb devices will show it if i have it in recovery mode but not bootloader, why is that ?
Click to expand...
Click to collapse
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc

BerndM14 said:
You didn't read any of my posts about that, did you? lol
I already stated adb commands like "adb devices" "adb reboot" etc will NOT work in bootloader, it'll work in the system and yes, it'll work in recovery for sideloading etc, but NOT in bootloader. For bootloader you HAVE to use fastboot commands, "fastboot devices" "fastboot reboot" "fastboot oem lock" "fastboot oem get_identifier_token" "fastboot flash unlocktoken Unlock_code.bin" etc etc
Click to expand...
Click to collapse
Sorry I skipped past your first response, that makes sense now.
So I need to put the rom on my internal storage then go into recovery and install the zip using TWRP..but when I plug my phone into the computer the internal storage wont show up.
I do have sync manager installed also, and it wont show up in that either

haydenrbm said:
Okay i have got into the bootloader now, thanks.
I cannot put the rom into the internal storage because my computer wont detect the phone
Click to expand...
Click to collapse
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps

BerndM14 said:
With that adb devices command again in bootloader? Did you flash TWRP yet? If so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload.
Place the ROM.zip file in your adb folder then:
Connect phone to PC, while still in recovery mode type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. Next type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ flash as per usual then.
Yet somehow I don't think you even need to go to these steps
Click to expand...
Click to collapse
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much

haydenrbm said:
haha..thank you for baby steps
The sideload completed and i rebooted then went back into recovery and install but there isn't a zip file anywhere
Edit: wow..some how i reset it and it turned on and got into the phone... and now it connects to the computer so i should be able to follow the other tutorial now...man you are a life saver thank you so much
Click to expand...
Click to collapse
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:

BerndM14 said:
I made a small mistake with the sideload though, it actually installs automatically as such you don't have to go back into recovery to flash, as it did it already, sorry. Edited post to fix.
Well as long as you can get into phone now to copy the nandroid backup to the phone all should be in order, can flash back stock from the nandroid then.
Glad it worked out then.:good:
Click to expand...
Click to collapse
Hello BerndM14, thank you for this baby steps. Mine m8 is a gpe version, it's 4.4.2 google rom, rooted, cwm recovery, s-on. I was trying to flash the full google 4.4.3 zip rom under recovery, however, after that, my m8 automaticlly enter recovery everytime reboot. And I can manually enter the bootloader, my pc can find the m8 both in recovery and bootloader. I searched this post, and do it accordingly, I download the gpe stock backup KOT49H.H16 - 1.16.1700.16 - CWM Philz touch and use adb sideload gpe3.zip to the cell phone sucessfully, then the recovery automaticlly starts installing rom, then, I got below message:
-- Erasing & formatting /system as ext4 (Unmounted system)
system partition formatted!
-- Mounting system partition for writing
Writing rom system to system partition
Rom system written successfully!
@symlinking and permissions
--Creating toolbox symlinks
--creating additional symlinks
Symlinks Set!
--installing busybox
Set_perm: some changes failed
E:Error in /tmp/update.zip
(status 7)
installation aborted.
Install from sideload complete.
then, I reboot it manually. problem still there, still enter the recovery automaticlly.
do you have any comments on this? please.
thanks,