I tried to manually update my HTC One's clockwork mod recovery using the command prompt. I downloaded the new .img file directly from the clockwork mod website. I made sure that I erased cache first. I then flashed the recovery I downloaded. The command prompt did not send the recovery and it failed to find the recovery. I could not get it to flash the new version of clockwork mod. I am trying to install android 4.4 and I need the new version of clockwork. I am going to give this phone to my father and I want him to have vanilla Android on it.
I am moderate Android modder. I have rooted several phones. I cannot get this to work the way I usually do. I am missing some step. Should I or could I flash TWRP Recovery instead of Clockwork?
Thank you for all of your help. Everyone on here has always been very helpful.
Flash it in recovery
Sent from my HTC One using Tapatalk
xcrazydx said:
Flash it in recovery
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Flash a new recovery from recovery ? that's a new one on me, I remember an old UPDATE.ZIP method does that still work ?
Rom manager and root toolbox can flash a recovery I think.
the only way I have ever done it is from fastboot usb
fastboot flash recovery TWRP.img
fastboot erase cache
or
fastboot flash recovery CWMT.img
fastboot erase cache
just make sure the TWRP.img or CWMT.img are in the same directory as fastboot
clsA said:
Flash a new recovery from recovery ? that's a new one on me, I remember an old UPDATE.ZIP method does that still work ?
Rom manager and root toolbox can flash a recovery I think.
the only way I have ever done it is from fastboot usb
fastboot flash recovery TWRP.img
fastboot erase cache
or
fastboot flash recovery CWMT.img
fastboot erase cache
just make sure the TWRP.img or CWMT.img are in the same directory as fastboot
Click to expand...
Click to collapse
That's what i do on all my Samsung phones. I don't remember if I've done it on this phone yet, actually. But yes, I always flash a new recovery from recovery.
Sent from my HTC One using Tapatalk
xcrazydx said:
That's what i do on all my Samsung phones. I don't remember if I've done it on this phone yet, actually. But yes, I always flash a new recovery from recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
interesting I was able to find a recovery flashable zip of CWMT
clsA said:
interesting I was able to find a recovery flashable zip of CWMT
Click to expand...
Click to collapse
If that doesn't work and you can't delete the recovery with fastboot erase recovery.
If you are soff find the 4.1.2 ruu exe and install it over. It'll fix the partitions and nuke recovery on its way by.
Sent from my One using Tapatalk
Related
I know pulling the boot.img from the rom is the old way to do things then wiping in recovery and flashing the boot img in fastboot... Then flash the rom in recovery....
Or you could just fasboot boot recovery.img and wipe and flash the rom... without pulling the boot.img
Doesn't these two methods work just the same minus the fact that fastboot boot recovery is just quicker to flash a whole rom....
This is for the hboot 1.5 users.....
I know about flash gui im just asking about using ADB and recovery flashing.....
Either way works fine doesn't it...>< ?
Yes, booting into recovery vía fastboot allows simultaneous flashing of kernel/ROM.
You may also flash a custom kernel zip file in the same fashion.
Sent from my PG86100 using xda premium
intrlude said:
Yes, booting into recovery vía fastboot allows simultaneous flashing of kernel/ROM.
You may also flash a custom kernel zip file in the same fashion.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Ya that is the advantage of using the recovery via fastboot.... But other then that they both get the job done... Minus that fastboot lets you flash the whole rom instead of taking the boot img out.... along with custom kernels....
One stop shop
There's also a app called Flash Image GUI that works pretty good...
I was so excited to flash viper on lte, i didnt install the kernel and cant get the phone to completely booy. Recovery and bootloader work fine. How can i flash the correct boot img or can I flash a stock rooted rom?
Should just be a fastboot flash boot boot.img
Sent from my EVO using Tapatalk 2
What do you mean? Viper comes with the kernel - if you're rooted and have recovery installed, you just flash the rom, and that's it.
@ Rx, what is your donation address. It worked and im going to try flashing the rom
This just happened to me over the weekend with CM10, so this is fresh in my mind. Completely power off the handset. Then, Power and Volume-Down to get into the bootloader. Connect the phone to your workstation via USB, and you will see a fastboot USB option. Then, download the ADB and Wintools ZIPs that are available here on XDA (PM me if you cannot find them via search, and I will send them directly to you).
After that, you will be able to execute the following commands to push the boot.IMG to your handset, etc.
http://wiki.cyanogenmod.com/wiki/Fastboot
Manual Nandroid restore
Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Flash Custom Recovery.img
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
Flash Custom boot.img
You should make a Nandroid backup first, in case you need to recover your boot.img
fastboot flash boot /path/to/<boot>.img
fastboot reboot
Alternatively, if you have CWM or TWRP installed as recovery options, you can flash from there. Just make sure you are pushing the correct boot.img for the ROM you want to flash.
HTH!
~ Mike
KaoMinerva said:
@ Rx, what is your donation address. It worked and im going to try flashing the rom
Click to expand...
Click to collapse
I pmd ya
Sent from my EVO using Tapatalk 2
I've tried everything I've found to get back to stock recover but I'm always greeted with red triangle. Only way to get to recovery back on line is to re-flash twrp. I've tried fastboot method, flasing new firmware, windroid toolkit... nothing works. I can't even flash CWM. So how do I get that damn leech out of my phone?
[edit]
Can't even flash twrp back on..so no recovery in this phone at the moment. Tried using goomanager, but it didn't do it either.
[/edit]
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
ethanon said:
FIrst of all Which phone do you Have (Int) or At&t , now if you have a stock recovery backup then in that case you can just use fastboot to push the image or use "recovery tool " to push it to the boot partition.
In case you are looking for the int stock recovery for the International version of the HOX+
http://forum.xda-developers.com/showthread.php?p=48470851#post48470851
Click to expand...
Click to collapse
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Wiper said:
I have wwe version of HTC One X+. That stock_recovery results the same red triangle. Fastboot pushes it okay but it just doesnt work.
Click to expand...
Click to collapse
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
ethanon said:
Stock recovery is not ment to do much , unless you have an official signed package to push. I feel you want to have a functional recovery like CWM , it can give it a go .
Click to expand...
Click to collapse
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
I got the same problem with RUU battery stat
Flashing a kernel solved the problem
Flashing another kernel didn't solve that porblem.
Wiper said:
Flashing another kernel didn't solve that porblem.
Click to expand...
Click to collapse
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
[email protected] said:
Flash the TWRP recovery.....
and erase the cache also using
this command
Code:
fastboot erase cache
Click to expand...
Click to collapse
Tried that as well..no go. Tried even fastboot boot recovery.img but the phone just turns itself off and doesn't load temporary recovery.
Wiper said:
Problem is that I've tried flashing TWRP and CWM but neither works. Phone boots up ok otherwise, but recovery is gone. Recovery Tool and Goomanager tells that the recovery image flash was completed but it's not or then something else got effed up. fastboot mode works just fine as the hboot.
Tried using RUU, but that doesn't work either because it keeps telling me that the battery level is below 30% and its at 91%. I remember trying RUU few months ago and I ran into the same problem. Back then I tried resetting battery status but that didn't help.
Click to expand...
Click to collapse
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Lloir said:
you are doing it wrong....goomanager and recovery tool CANNOT simply flash onto our devices,
you NEED to do ; fastboot flash recovery <insert recovery name here .img>
Click to expand...
Click to collapse
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
U tried every possible incorrect things.....and didn't even read Llior's post......
To flash a kernel the fastboot command is
Code:
fastboot flash boot boot.img
To flash a recovery the command is
Code:
fastboot flash recovery recovery.img
instead of this u had tried to write the recovery file in boot partition...
and the
Code:
fastboot boot recovery.img
is to enter into the recovery without even having to install it on phone....
and I haven't checked it in HOX+ so better flash the boot.img(Kernel) and recovery.img(Recovery) using the mentioned commands above. and erase the cache....(which you seem to do correctly)...
Wiper said:
The fastboot method doesn't work. It does say that the flash was successfull, but there's still no recovery.... and besides, when I had stock recovery months ago, I actually did install twrp with goomanager, not with fastboot.
What I have tried:
1. fastboot flash boot stock_recovery.img with fastboot erase cache (red triangle)
2. fastboot flash boot twrp_recovery.img with erase (phone turns off when entering recovery)
3. fastboot boot recovery.img and twrp_recovery.img (doesn't boot to recovery) (phone turns off when entering recovery)
4. Tried using RUU but that hasn't worked for me ever (always the battery level below 30% error)
5. tried fastboot flash recovery and then flash boot and then erase (and first boot, then recovery) (stock and custom kernels)
6. numerous other ways I cant even remember anymore.
If there only were a rom with all the needed img files, I'd try flash all (or flashing them one by one) but haven't found any.
Click to expand...
Click to collapse
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Lloir said:
ok i'll base my assumptions here on you using windows, and you don't have filename endings turned on.
i'm guessing you are renaming the files and adding in .img which is a bad idea, as .img is actually there but hidden. if i'm wrong, then try flashing the recovery with the PROPER file name without touching it.
so for CWMR it would be fastboot flash recovery recovery.img
for twrp it would be ; fastbootflash recovery openrecovery-twrp-2.6.3.0-enrc2b.img
Click to expand...
Click to collapse
I haven't actually renamed anything (just in here to keep it short). And that 1. & 2. was miswritten. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Ive tried it with All-in-one tool as well...The weird thing is that all fastboot flashes or with that allinone tool there are no errors ever, only successfull flashes.
Wiper said:
I haven't actually renamed anything (just in here to keep it short). And that 1. was typo. I haven't done fastboot flash boot recovery.img but fastboot flash recovery recovery.img.
I have tried exactly that file you posted but it's a no go (also tried other twrp versions and come cwm's too as well as stock recovery image).
Click to expand...
Click to collapse
are you sure your device is the enrc2b and not the evitareul?
Lloir said:
are you sure your device is the enrc2b and not the evitareul?
Click to expand...
Click to collapse
Yup... But anyway...decided to try that twrp one more time with all-in-one tool, flashed okay but this time the recovery worked and I was able to flash working rom and boot.img. Phone works now, but this was the last time I try to remove twrp.
How long, at least historically, does it take for AT&T to release an RUU for our device? I have unlocked my bootloader but I am hesitant to proceed without knowing I have a fallback to stock system image and recovery. Thanks for any input, and I understand that the releases are typically unpredictable but I suppose asking for a general ball park figure!
Sent from my HTC One_M8
wont be for awhile if at all... could do fastboot boot recovery nameofrecovery.img this should boot into recovery then make back up then youll have stock everything as a backup...
TheEmpyre said:
How long, at least historically, does it take for AT&T to release an RUU for our device? I have unlocked my bootloader but I am hesitant to proceed without knowing I have a fallback to stock system image and recovery. Thanks for any input, and I understand that the releases are typically unpredictable but I suppose asking for a general ball park figure!
Sent from my HTC One_M8
Click to expand...
Click to collapse
Wonders_Never_Cease said:
wont be for awhile if at all... could do fastboot boot recovery nameofrecovery.img this should boot into recovery then make back up then youll have stock everything as a backup...
Click to expand...
Click to collapse
So there is a way to make a full backup with the stock HTC Recovery?
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
TheEmpyre said:
So there is a way to make a full backup with the stock HTC Recovery?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
Click to expand...
Click to collapse
Ah, I see what you're saying, So I would need to place the TWRP.img into the directory from which I'm running commands yes?
Correct...reboot to bootloader and run the fastboot boot recovery nameofrecovery.img command
TheEmpyre said:
Ah, I see what you're saying, So I would need to place the TWRP.img into the directory from which I'm running commands yes?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Correct...reboot to bootloader and run the fastboot boot recovery nameofrecovery.img command
Click to expand...
Click to collapse
Sweet, I'll give it a try and make a backup, see how it goes
Wonders_Never_Cease said:
No the command i said temp boots into twrp doesnt actually flash it, and you can make a back up that way.
fastboot boot recovery nameofrecovery.img (temp boot into recovery)
fastboot flash recovery nameofrecovery.img (would flash a custom recovery)
Click to expand...
Click to collapse
So I tried these commands here and its giving the error "cannot load 'recovery' " so it looks like fastboot is looking for an .img to follow the 'boot' command:
fastboot boot recovery.img -
At least that is what I figured, I haven't tried it because I'm timid, but if I execute that command ^ will it get me to the recovery image for a backup without derping something?
Edit: Did a little bit more research / sacked up and went for it. Just booted up and rooted without installing custom recovery which is exactly what I wanted to do. Just wanna debloat the phone myself with root access!
Thanks for the help!
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.