Hello,
I visit this forum every day to stay up to date with all the ROMs. Im trying to help fix a friend's phone and I apologize if this is in the wrong forum but I think this forum contains the audience who can help with this. Basically my friend brought me his G2 (which I rooted and put CM7 on it for him) and it wouldnt boot. I know all the regular ways to recover it but when booting into recovery I get these errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Here is a Pastebin with the recovery log:
http://pastebin.com/qT4KMrUj
Cannot update to the newest recovery using fastboot (CWM version is 3.0.0.5) but i booted to CWM 3.0.2.4 with the fastboot boot recovery.img command. I cannot restore a backup, cannot format /boot or /system (get the "error formatting /system" message). I wiped cache and data and this didnt help. Tried loading a new cm7 zip. If I try to flash the latest recovery in fastboot it doesnt work:
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.760s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.780s
I tried loading a PC10IMG.zip from an RUU and I get a failed update on the first item. Im thinking this is some kind of partition issue. Does anyone have any ideas? Ive been searching the whole morning and there are a few threads in other forums regarding this and the best luck someone had was flashing with the PC10IMG.zip to fix it. The phone has the engineering hboot.
Code:
c:\download\android-sdk-windows\tools>fastboot oem listpartition
... INFO[merge_mfg]:(MERGEMFG, 10) block start=0,
size=0 (0 KB)
INFO[radio]:(OTHER, 4) block start=0, size=163840 (0 KB)
INFO[merge_emmc]:(RAW, 4) block start=0, size=4194304 (655360 KB
INFO)
INFO[fat]:(RAW, C00) block start=0, size=0 (0 KB)
INFO[local]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[spcustom]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[microp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[cpld]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[rcdata]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[a1026]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[tp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[wimax]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[htcdata]:(RAW, 7404) block start=143363, size=2048 (1233216
INFO KB)
INFO[radio_reserve]:(RAW, 7504) block start=145412, size=17915 (
INFO1661741 KB)
INFO[dzsystem]:(DEZERO, 8) block start=197122, size=851453 (4257
INFO26 KB)
INFO[dzdata]:(DEZERO, 8) block start=1048576, size=2723841 (1361
INFO920 KB)
INFO[misc]:(RAW, 7601) block start=163328, size=512 (256 KB)
INFO[hboot]:(RAW, 4701) block start=163841, size=2048 (1024 KB)
INFO[sp1]:(RAW, 3401) block start=165890, size=2048 (1024 KB)
INFO[wifi]:(RAW, 3601) block start=167939, size=2560 (1280 KB)
INFO[recovery]:(RAW, 7101) block start=170500, size=17402 (8701
INFOKB)
INFO[boot]:(RAW, 4801) block start=187903, size=8192 (4096 KB)
INFO[mfg]:(RAW, 7301) block start=196096, size=512 (256 KB)
INFO[misc2]:(RAW, 3101) block start=196609, size=512 (256 KB)
INFO[system]:(EXT3, 8301) block start=197122, size=851453 (42572
INFO6 KB)
INFO[userdata]:(EXT3, 8301) block start=1048576, size=2723841 (1
INFO361920 KB)
INFO[cache]:(EXT3, 8301) block start=3772418, size=419431 (20971
INFO5 KB)
INFO[devlog]:(EXT3, 1901) block start=4191850, size=40960 (20480
INFO KB)
OKAY [ 0.153s]
finished. total time: 0.153s
Thanks!
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yep, I fixed that with the code box. LOL
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
1wayjonny said:
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
Click to expand...
Click to collapse
Yep I tried this. I booted into the CWM 2.5.1.3 and tried to wipe and format /boot and /system but I get errors just like in CWM3.
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
1wayjonny said:
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
Click to expand...
Click to collapse
Can you recommend a particular file to use? Im looking at a list here:
http://shipped-roms.com/index.php?category=android&model=Vision
I would try these:
http://shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_test_144460.zip
If that doesn't work try this one
http://shipped-roms.com/download.ph....09b_26.02.01.15_M2_release_149459_signed.zip
If these dont work I would be surprised and yes something more may be messed up.
I'm glad that this issue is getting more attention today. It has been occurring with more and more frequency since the release of the new CWM Recovery and CM7...
Well I thought I was the only one, this happened from using a specific build of the CWR 3 series.
Nice to know its wasn't just me but I def think its has to do with formatting of the partition but could be wrong.
Well, neither of those PC10IMG.zip worked. Im looking at another thread here to hopefully help out. Looks like a partition issue like I thought. Only thing is how to fix it?
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Hopefully this isn't too off topic, but is there a tool that can be used to perform a health check of the internal and external storage of our phones? Everything on my phone is working just fine, but would love that guarantee that it's in good order.
Thanks.
amazinglarry311 said:
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
Click to expand...
Click to collapse
Where can I issue these commands? I cannot get a shell.
Stupid question about the PC10IMG.zip method...
It probally is but confirm the card is formatted as FAT32 for fastboot
Also is there any swap partitions etc..
If the SDCARD has partitions redo it as one FAT32 partition or use an alternate SDCARD with one FAT32 partition
popokrew said:
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Click to expand...
Click to collapse
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
nvm found it. for those who might be following this thread and also need it you can find it here
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img
open1your1eyes0 said:
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
Click to expand...
Click to collapse
I can't use adb because I can only get to fastboot and thus, I can only use the fastboot command. Unless I'm missing something? I do have the device in device manager with the driver loaded. I have loaded many radios through fastboot so I know the connection is working. The trick is to get an adb shell, but what state do you want the phone in? Right now I can only get to fastboot or recovery (can't do adb there either).
Sent from my HTC Vision using XDA App
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.
. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.
Did you try to wipe your HOX including /data as well as /system partition? This - in the guide if how to achieve new storage layout - is one of the important prerequisites and done prior to flashing the TWRP.BIG
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).
dsnunes said:
. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.
Click to expand...
Click to collapse
I use this program and it works well. http://we.tl/8gYJ8tgcer
So I decide to do a full wipe and install NMF26Q then install WETA 2.2. I got stuck in a bootloop at the google screen and did a full wipe/flash of NMF26Q but I still can't get past the google screen and I'm getting the following errors in fastboot.
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
Failed (remote: unknown command)
(Bootloader) Erasing active slot "_a"
FAILED (remote: partition table doesn't exist)
airmaxx23 said:
So I decide to do a full wipe and install NMF26Q then install WETA 2.2. I got stuck in a bootloop at the google screen and did a full wipe/flash of NMF26Q but I still can't get past the google screen and I'm getting the following errors in fastboot.
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
Failed (remote: unknown command)
(Bootloader) Erasing active slot "_a"
FAILED (remote: partition table doesn't exist)
Click to expand...
Click to collapse
Problem solved: I had to ADB sideload one of the OTAs to get up and running again.
airmaxx23 said:
Problem solved: I had to ADB sideload one of the OTAs to get up and running again.
Click to expand...
Click to collapse
No you need to update you're SDK.
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
twrp doesn't work for android 10. please be specific about versions of android and twrp you are using
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
As already noted, TWRP has never worked with 10. If you are on 9 then head over to the dedicated TWRP thread and get yourself up to speed.
if on android 9 it would be fastboot boot twrp. img. (if on Pie)
A/B slot devices don't have a dedicated recovery partition. (reason why flashing to recovery didn't work)
Android 10 doesn't have working TWRP yet. ( can't decrypt data or something)