[Q] Issues flashing new recovery - Droid Incredible Q&A, Help & Troubleshooting

I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox

droxpopuli said:
I have been running MIUI flashed via clockwork app/recovery for the past few months. Today, suddenly a bunch of my apps were not working and I was getting a load of force closes. I figured I reboot and I find myself in a bootloop.
At this point, it isn't a huge deal. I figured, I would boot into recovery and load up my backup from CM7. Only problem is I can't seem to get into my recovery, as thought it is gone. Also no big deal, I'll just try to reflash my recovery via fastboot. I load up on hboot and run it with the latest version from clockwork:
Code:
D:\Desktop>fastboot devices
HT08JHJ04373 fastboot
D:\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm looking several places for this exact problem, but I can't seem to find anything that works for me. My SD is backed up and while I would like to be able to keep my other stuff and/or just get up and running again without a wipe, any suggestion would be helpful right about now.
Thank you,
Drox
Click to expand...
Click to collapse
Have you tried flashing recovery thru hboot with a PB31IMG.zip? You can get it here http://pvillecomp.com/?page_id=28

I got it installed from there. I loaded up the recovery and it must have done a restore since I booted and it was fresh miui like when i did a backup from before. Nothing to be done there sadly :/ But thanks for the help and the link. I didn't even know this site existed.

Related

[Q] Help: Can't relock, can't flash via fastboot

UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad
did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?
You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium
i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681
Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you
tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681
Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad
Bump.
Nobody any more ideas?
Bump. Still no solution after many month
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.
help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS
aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!
BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that
Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:

Bis Problem with a GNexus and Factory Reset

Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Shizophren said:
Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Click to expand...
Click to collapse
I flash a lot of time on this type of device so far doesn't give a problem to me. Maybe something wrong with your device or maybe you can try to flash it via GNex toolkit and download the .tgz file from program first maybe you will have a luck.
sounds a little like bad flash ROM but I'd leave that to the pros to diagnose... mabye there was a cause why somebody put it on ebay ^^
Instead of flashing the factory image zip you could extract the system.img, boot.img, and data.img from that zip and flash them one by one.
Follow this guide: http://forum.xda-developers.com/showthread.php?p=25477039
Sent from my Nexus 7 using xda premium
@compuzones thanks for your answer. I tried this already. But no success.
@Hannes The Hun you could be right, but whats could cause the problem? I have no clue
@El Daddy I'll give it a try.
Edit:
So this is what happend. Would appreciate some expert thoughts on it.
I extracted the factory image and tried to flash the seperate files manually.
First the bootloader:
In fastboot mode my device shows me, that theese bootloader is on it:
PRIMALA03
So i pushed the newer one on it - fastboot flash bootloader bootloader-maguro-primelc03.img
sending bootloader - OKAY
writing bootloader - OKAY
the operation seems to work. But, when I'm restart-bootloader again, I have still PRIMELA03 as my bootloader.
Ok, I thought that unimportant. So tried to go on with the system.
fastboot flash system system.img
sending system OKAY
writing system..............
So here we go. It writes the system for over 20 minutes. Don't know why it exactly happens.
This happens wether I try to flash a factory image with the toolkit here from xda, or the google way or just this way.
Whats strange too.
Wanted to flash via CMW a custom rom. Just to trie it, if this woul work.
I flash CWM via the toolkit. The operation went fine. When I trie to boot in recovery, I get still the little Android with the red triangle and nothing happens.
Althouh the rom, that I put on the sd is gone after restart! Nothing there. Everythings wipe the whole time I start the device.
Edit2: After 25 Minutes it says system write ok. Here what i did:
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash system system.img
sending 'system' (396675 KB)... OKAY
writing 'system'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)... OKAY
writing 'userdata'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash boot boot.img
sending 'boot' (4366 KB)... OKAY
writing 'boot'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fsatboot flash recovery recovery.img
Der Befehl "fsatboot" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (4708 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot reboot
rebooting...
Click to expand...
Click to collapse
But still the old rom on my device ^^ can't figure out whats all about. The device saves absolutely nothing.
Is there a possibility to check the file system or sdcard for errors or something?
Even factory reset over the android option doesn't work. It reboots and then appears the Android with the red triangle again. After some time, the rom boots again^^

No access to Recovery and HOX doesn't boot

Hello
i have some problems with my HTC One X. Until 2 hours ago it worked perfectly and without problems. i didn't flash anything in the last few weeks, but theres ARHD (ICS) installed. But then suddenly it had a freeze, so i had to restart it with pressing the powerbutton for 10 seconds. Since then, it doesn't boot anymore and also i can't access the Recovery, i get a blackscreen if i try, But i come into the Bootloader, Fastboot is possible but doesn't work...
I tried to reflash the Boot.img, but there was an error: erasing cache FAILED (remote: 19000008)
I also tried to reflash the CWM Recovery but there was another error:
5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.904s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (00030000))
finished. total time: 1.150s
So can anybody help me? All that I want is access to my virtual SD Card for saving my data, and can anybody tell me how and if I can "repair" my One X? And sorry for the bad english, i'm no native speaker...
you can try this, http://forum.xda-developers.com/showthread.php?t=1609190
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Achsoistdas19 said:
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Click to expand...
Click to collapse
what the error mate?
Hm, i don't really know. There are these Error-Codes, mostly "remote: 19000008" or "remote: 00000004" also with a 5 at the end, and it says "remote: not allowed" sometimes.

Botched my old recovery, and can't flash a new one...help?

I've been playing around with some of the JB ROMs, and was using Goo Manager and TWRP to do it. Then, because I'm an idiot, I decided I wanted to upgrade TWRP to 2.3.3.0 (I think I was running 2.3.1.0).
That's when I ran into the "TWRP doesn't always install properly" problem. I've now tried updating TWRP from within Goo Manager more than 5 times, but it's not working.
So I decided I'd install the new recovery via the FASTBOOT method.
I have HBOOT 0.92. I have ADB and FASTBOOT loaded on my laptop. (I'm pretty sure this is the way I originally installed CWM 5.0.2.0 when I first rooted my phone ages ago.)
When I boot the phone into the bootloader and choose FASTBOOT, then plug it into my laptop, I get the "FASTBOOT USB" indication that it's connected, so that's good.
However, when I open a terminal window on my laptop, navigate to my miniadb folder (where the fastboot.exe and recovery images are located), and try to flash the recovery image, I see the green bar in the upper right corner of the phone, but on the laptop I get this:
c:\miniadb>fastboot flash recovery openrecovery-twrp-2.3.3.0-inc.img
sending 'recovery' (3642 KB)... OKAY [ 11.235s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 11.268s
So then I decided to give up on TWRP and go back to CWM, but there's no joy there, either:
c:\miniadb>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 12.370s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 12.402s
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Does anyone have a suggestion for a foolproof way to get a recovery (either CWM or TWRP--at this point, I'm not picky!) back on my phone?
Thanks!
MC
Check the last two pages of the tarp thread for a twrp hboot PB31IMG.ZIP or see my direct link below.
http://goo.im/devs/tiny4579/mods/PB31IMG-TWRP-2.3.3.0.zip
This method works without fastboot.
Sent from my Galaxy Nexus using Tapatalk 2
Many thanks, tiny! I'll give that a shot.
MysticCobra said:
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Click to expand...
Click to collapse
For what it's worth, I think you need to upgrade HBOOT to 1.02 or 1.07 and unlock it through htcdev to be able to use the fastboot flash commands. But the flashable zip for TWRP should fix it for you too and that way is easier and just as reliable.

Unable to Boot to Recovery with TWRP

I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.
i had the same problem, i just left clockwork on there, i gave up after flashing it like 30 times. I did all the exact same things as you. Also checked the MD5 and verified what i had was what it was. Just letting you know i had the same problem as you, id love to find a answer myself. BTW you can still flash clockwork back on it to do recoveries.
I've come across more than one person online who has the same problem too but no definative answer.
I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...
What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.
Chilidog said:
I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...
Click to expand...
Click to collapse
I'll give that a shot this afternoon.
brymaster5000 said:
What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.
Click to expand...
Click to collapse
Which thread are you referring to?
I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .
cbrown245 said:
I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .
Click to expand...
Click to collapse
Hmmmm, now you got me.... Still doesnt explain why it works for some and not others
cowmoo32 said:
I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.
Click to expand...
Click to collapse
You're using the wrong image for TWRP on the HTC One. What you want is
"openrecovery-twrp-2.6.3.0-m7vzw.img".
I had a problem while trying to flash TWRP as well (I got my root and s-off with rumrun) , I'm just going to stick with CM, its much simpler anyway.
cowmoo32 said:
I'll give that a shot this afternoon.
Which thread are you referring to?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Oney Bone.

Categories

Resources