Related
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).
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 wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
I just got my OnePlus 3 last week and I am having some issues trying to root it. Initially, I was using Win7 and could not get anything to work (phone was never recognized - yes drivers were installed). I went to my laptop with Ubuntu 16.04 and had some success. I was able to unlock the phone; however, when I tried to flash twrp.img (and recovery.img), I kept getting a fastboot permissions denied error. I was using sudo and fastboot devices worked. Also, if I try "sudo fastboot boot twrp.img" nothing happens on the phone (or pc for that matter). I am totally perplexed. The OS on the phone is Oxygen 3.2.4. Thanx for any assistance.
Bill
Install all driver (1+ Mobile Usb driver and Adb)
Than Follow Toolkit Method On Xda.. Its work Fine For me... ? and Follow their Video
I had a similar problem with mine. I could flash TWRP but it wouldn't stick. Reboot the phone and try again, the factory recovery would be back. I tried every version of TWRP, adb, fastboot and the toolkit -- same result.
Finally fixed it by using the toolkit to flash the previous version of TWRP, then using TWRP to flash the latest version without rebooting the phone. With that done, no problems after rebooting system.
Now I can flash new ROMs.
How old does twrp have to be before you get positive results?
Hello, I have a huuuuge problem.
Every time I try to flash TWRP through cmd, nothing happenes. I have all needed files, my phone is being recognized in adb devices, reboots on command, is on fastboot devices list, reboots on fastboot reboot command, but it totally do nothing when I use fastboot flash recovery twrp.img command. Maybe it's my drivers fault, because last time i uninstalled my device through Device Manager, somehow it worked and I flashed TWRP. But then I switched to MIUI and as expected TWRP was removed. And I cannot flash it, please help
Did you update to latest MIUI?
Yes, right now I'm on Global Stable.
Turn your pc into a new one then you will.
Why turn your PC into a new one? resetting?
Isn´t there another solution?
Removes old data such as adb,platformtool, twrp.then can do it.I've come across and solved this way Do not know why
xx
Posted another tread:
I struggled a lot installing TWRP. I did not succeed flashing TWRP from my PC. My solution was:
Starting up TWRP: fastboot boot twrp.img / boot command only boot and does not flash.
Thereafter installed Magisk 17.1 from TWRP for rooting
Thereafter flashed TWRP / I tested flashing both by using Flashify and TWTP Manager and both worked.
Maybe by using Flashify I had to use an older version of TWRP. Think TWRP Manager let me install 3.2.3-0 direct without problems.