Develop Bugs

Issue with Partitions on G2, Errors with CWM

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

[Q] i think i briked my Htc one x

Hi
Last year i was using Android Revolution custom firmware, after which i went back to stock, i stayed with stock about 1 year , then yesterday tried install Android Revolution HD, but i think i mess it up big time because i am stuck in boot screen . I tried looking for a RUU but apparently my phone is using a newer version of RUU which i can not find. I spent 1 day looking for solutions but none helped, now i am stuck. Please help. Sorry for my English , Thank You

give more info : hboot number ? what recovery ? flashed the boot.img ?

Mr Hofs said:
give more info : hboot number ? what recovery ? flashed the boot.img ?
Click to expand...
Click to collapse
version-main: 4.18.401.2, hboot 1.72.000 .recovery-clockwork-touch-5.8.4.0-endeavoru , 5.1204.167.31
. i think i flashed the boot.img , at least one of them, i did a lot of flashing , trying to recover from my mistakes

okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot

Mr Hofs said:
okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot
Click to expand...
Click to collapse
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks

ursache marian said:
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks
Click to expand...
Click to collapse
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !

Mr Hofs said:
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
I found that batch file in other post , and i just started charging now.

ursache marian said:
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
Click to expand...
Click to collapse
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours

Mr Hofs said:
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours
Click to expand...
Click to collapse
I can not access recovery , it's staying only in boot menu , but i found a batch file witch apparently if i run it it will charge the phone for me to be able to flash the recovery that you sent .

Yeah cool. How many mV is it ?

Mr Hofs said:
Yeah cool. How many mV is it ?
Click to expand...
Click to collapse
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.

ursache marian said:
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.
Click to expand...
Click to collapse
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache

Mr Hofs said:
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.167s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.377s
C:\New folder>fastboot erase cache
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.217s
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.169s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.378s

unlock the bootloader !

Mr Hofs said:
unlock the bootloader !
Click to expand...
Click to collapse
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help

ursache marian said:
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help
Click to expand...
Click to collapse
no problem, let me know the result

Mr Hofs said:
no problem, let me know the result
Click to expand...
Click to collapse
i managed to flash boot and flash android hd 31.3 with your recovery.img, on mine the touch was not working . Thank you again.

Okidoki !
CASE CLOSED !

[ROM][G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d

@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak

Thnkx buddy ...!!

thanks..Anyone tried it? it works?
Sent from my HTC Desire 300 using XDA Premium 4 mobile app

FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300

Is this confirmed working?

will this work on chinese 301e ....because these is no playstore in chinese version

aamszia said:
will this work on chinese 301e ....because these is no playstore in chinese version
Click to expand...
Click to collapse
Can I have a copy of your build.prop?

MameTozhio said:
@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak
Click to expand...
Click to collapse
i got status(0) error while flashing this rom :'( . what's wrong ?

MStevie said:
i got status(0) error while flashing this rom :'( . what's wrong ?
Click to expand...
Click to collapse
maybe this was created to kill your phone?

so i recieved another phone ... still no rom
chinese 301e

SPSPaWn said:
FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300
Click to expand...
Click to collapse
i got status(0) error while flashing this rom

I also have this error when I try to flash the HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox + init.d
Stock ODEX root 1.10.401.4 updated works without a problem.

what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....

maplegsm said:
what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....
Click to expand...
Click to collapse
You need to unlock the bootloader go to http://www.htcdev.com/ and click "Unlock Bootloader" select other device from the list and follow the instructions. Hope this helps.

where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????

RamHa said:
where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????
Click to expand...
Click to collapse
This is just a stock system dump I did about 2 years ago that was meant to be flashable with root but it doesn't flash properly for some, I won't be updating it any further.

Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy

Riski3Run said:
Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy
Click to expand...
Click to collapse
That's good! Just be sure to disable automatic receiving of MMS messages as this is vulnerable to all the stagefright exploits.

f
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
< waiting for device >
sending 'recovery' (6910 KB)... OKAY [ 1.463s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.563s
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.310s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.410s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.347s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 9.641s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.382s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.482s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>

Can't boot to recovery (no ROM installed...)

Hi guys, I would like to ask for a help. I was on New Layout (SlimKat 9.0). I wanted to try something at Old Layout ROM, so like a stupid I wiped everything (cache, data and system thru recovery), then I flashed fastboot flash boot boot.emmc.win (Old Layout Backup) and Old Layout TWRP.
But after that, I can't access recovery (I only see picture of TWRP for 1 second, then it reboots with bootloop). So I flashed New Layout TWRP again together with fastboot flash boot boot.emmc.win (I got backups from Old & New Layout).
Then I tried
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot erase cache
but nothing helps. I am simply without ROM and accessible recovery. Anybody has idea what to do please? Thx a lot!

lesmil said:
Hi guys, I would like to ask for a help. I was on New Layout (SlimKat 9.0). I wanted to try something at Old Layout ROM, so like a stupid I wiped everything (cache, data and system thru recovery), then I flashed fastboot flash boot boot.emmc.win (Old Layout Backup) and Old Layout TWRP.
But after that, I can't access recovery (I only see picture of TWRP for 1 second, then it reboots with bootloop). So I flashed New Layout TWRP again together with fastboot flash boot boot.emmc.win (I got backups from Old & New Layout).
Then I tried
fastboot flash boot boot.emmc.win
fastboot flash system system.ext4.win
fastboot erase cache
but nothing helps. I am simply without ROM and accessible recovery. Anybody has idea what to do please? Thx a lot!
Click to expand...
Click to collapse
Download this guide and follow it. It should get you back to old layout.
How do I get back to the Old Layout?
Guide on Going Back to Normal Layout
Updated link to old recovery.

teemo said:
Download this guide and follow it. It should get you back to old layout.
How do I get back to the Old Layout?
Guide on Going Back to Normal Layout
Click to expand...
Click to collapse
Thx for reply teemo. Already tried that. Still getting bootloop (blue image of TWRP appears for 1 second, then it reboots). Battery was fully charged (green LED). Even got this result from CMD:
C:\fastboot>fastboot flash boot boot.emmc.win
sending 'boot' (8192 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.675s]
finished. total time: 1.910s
C:\fastboot>fastboot flash recovery twrp-recovery-hox-2.8.1.0.img
sending 'recovery' (7720 KB)...
OKAY [ 1.136s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.623s]
finished. total time: 1.761s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.222s]
finished. total time: 0.223s
No idea what to do now

lesmil said:
Thx for reply teemo. Already tried that. Still getting bootloop (blue image of TWRP appears for 1 second, then it reboots). Battery was fully charged (green LED). Even got this result from CMD:
C:\fastboot>fastboot flash boot boot.emmc.win
sending 'boot' (8192 KB)...
OKAY [ 1.232s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.675s]
finished. total time: 1.910s
C:\fastboot>fastboot flash recovery twrp-recovery-hox-2.8.1.0.img
sending 'recovery' (7720 KB)...
OKAY [ 1.136s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.623s]
finished. total time: 1.761s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.222s]
finished. total time: 0.223s
No idea what to do now
Click to expand...
Click to collapse
Can you boot to recovery ?

teemo said:
Can you boot to recovery ?
Click to expand...
Click to collapse
Nope. I wish I could. I only see TWRP blue image for 1 second or so, then it goes to bootloop.

Did you try the famous:
fastboot erase cache ?

teemo said:
Did you try the famous:
fastboot erase cache ?
Click to expand...
Click to collapse
Sure I even pasted it in post I never forget to do this.

lesmil said:
Sure I even pasted it in post I never forget to do this.
Click to expand...
Click to collapse
Hmm everything look right.
Could you try the recovery from my link.

teemo said:
Hmm everything look right.
Could you try the recovery from my link.
Click to expand...
Click to collapse
The file was not found But I got this version of TWRP (from you) stored on external hdd as a backup, and on my D partition. It's still the same. Bootloop. I wish I could transfer some ROM zip to sdcard and install it lol.

lesmil said:
The file was not found But I got this version of TWRP (from you) stored on external hdd as a backup, and on my D partition. It's still the same. Bootloop. I wish I could transfer some ROM zip to sdcard and install it lol.
Click to expand...
Click to collapse
No not the link from the guide. The link I posted in post #2. Download and flash.

teemo said:
No not the link from the guide. The link I posted in post #2. Download and flash.
Click to expand...
Click to collapse
Still the same result :/
C:\fastboot>fastboot flash recovery twrp2810-HOX.img
sending 'recovery' (7720 KB)...
OKAY [ 1.157s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.638s]
finished. total time: 1.798s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.221s]
finished. total time: 0.223s

try this may help
also try adb push commands

dado323 said:
try this may help
also try adb push commands
Click to expand...
Click to collapse
Thx, but no progress :S

u can try one x click to install recovery ,like long time ago i **** everthing on my phone ,i didnt have anything on my phone so i use Philz 5.15.9 the SD card mount function work only on that recovery that was like 2 years ago

dado323 said:
u can try one x click to install recovery ,like long time ago i **** everthing on my phone ,i didnt have anything on my phone so i use Philz 5.15.9 the SD card mount function work only on that recovery that was like 2 years ago
Click to expand...
Click to collapse
I tried to flash every recovery now via One X click by now, no success to enter recovery. Always 1 second "blink" and reboot. No idea, maybe time for bed now lol
OH YEAH, at least managed CWM 6.0.4.8 WOHOO At least some progress... ^^

good luck

dado323 said:
good luck
Click to expand...
Click to collapse
Thx but I am stuck again lmao. As I was on New Layout, UMS doesn't work. Sideload - same. omg. Will do it tomorrow. But weird thing is, that only latest CWM and philz touch 6.19.3 were able to be installed.
After this, TWRP 2.8.1.0 installed. Everything's going to normal. Thanks both of u guys

M8 wont start anymore

Hi there,
Today i was trying to unlock my phone and install a custom rom.
I started the phone in fastboot and has used these commands:
Code:
C:\Users\laptop\Desktop\ROOTEN\UBTv1.3.2>fastboot flash recovery recover.img
sending 'recovery' (14826 KB)...
OKAY [ 1.627s]
writing 'recovery'...
OKAY [ 1.824s]
finished. total time: 3.452s
C:\Users\laptop\Desktop\ROOTEN\UBTv1.3.2>fastboot flash recovery recover.img
sending 'recovery' (14826 KB)...
OKAY [ 1.643s]
writing 'recovery'...
OKAY [ 1.030s]
finished. total time: 2.674s
The File, was "twrp-2.8.7.0-m8.img" and renamed to "recover.img"
After this my phone didn't start android anymore and i've downloaded HTCDev Unlock and installed it at the phone. When that was ready i've reinstalled the trwp image file but with no good result.
After this i've downloaded and installed a older image file, version 2.7.1.0 and used also the command:
Code:
C:\Users\laptop\Desktop\ROOTEN\UBTv1.3.2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.110s]
finished. total time: 0.111s
but the results are the same, I can't boot my M8 to android but also not in the recovery mode.
Can anyone give me some advise, to make my phone work again?
More info:
Software status: Modified
Unlocked
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio: 1.25.214500021.06G
opendsp: v48.2.2-00564-m8974_F0.1211
OS-4.19.161.3
eMMC-boot 2048MB
Aug 4 2015,21:56:12.14319
I don't now if the Fastboot option at Settings > Power is off.... and can't verify that.

Check md5 for the downloaded twrp-2.8.7.0-m8.img.
Mine is bd7a8c6a73cb9b8b6bac3ce9ec355c0c
The size 14826 KB seems too small, mine is 17020 KB
Code:
C:\Users\ckpv5\Desktop\Recoveries>fastboot flash recovery twrp.img
target reported max download size of 1826418688 bytes
sending 'recovery' (17020 KB)...
OKAY [ 1.828s]
writing 'recovery'...
OKAY [ 0.844s]
finished. total time: 2.672s

Mmm, that was a the size of the older file.... It was to show the command i've entered but not shows the right file info!
I've just used version "twrp-2.8.7.0-m8" and shows info below. Seems right.
Code:
C:\Users\laptop\Desktop\ROOTEN\UBTv1.3.2>fastboot flash recovery recover.img
sending 'recovery' (17020 KB)...
OKAY [ 1.835s]
writing 'recovery'...
OKAY [ 1.944s]
finished. total time: 3.779s

patje* said:
Mmm, that was a the size of the older file.... It was to show the command i've entered but not shows the right file info!
I've just used version "twrp-2.8.7.0-m8" and shows info below. Seems right.
Code:
C:\Users\laptop\Desktop\ROOTEN\UBTv1.3.2>fastboot flash recovery recover.img
sending 'recovery' (17020 KB)...
OKAY [ 1.835s]
writing 'recovery'...
OKAY [ 1.944s]
finished. total time: 3.779s
Click to expand...
Click to collapse
After you installed twrp-2.8.7.0-m8.img can you boot to recovery ?
If you can, then restore 4.19.161.3 stock backup.
You can get the stock backup in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If still can't boot to recovery, don't know much how to help you. One thing for sure, never use that 2.7.0.2 .. only 2.8.4.0 or 2.8.5.0 or 2.8.6.0 or 2.8.7.0
(you can try all of these to see whether you can boot to recovery after flashing them)

ckpv5 said:
After you installed twrp-2.8.7.0-m8.img can you boot to recovery ?
If you can, then restore 4.19.161.3 stock backup.
You can get the stock backup in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If still can't boot to recovery, don't know much how to help you. One thing for sure, never use that 2.7.0.2 .. only 2.8.4.0 or 2.8.5.0 or 2.8.6.0 or 2.8.7.0
(you can try all of these to see whether you can boot to recovery after flashing them)
Click to expand...
Click to collapse
Thx for your help. I was a bit busy yesterday and it was getting late when I want to resolve this issue.... Now after some sleep and GOOD looking... I saw that my external SD card was inserted. Pulled it out and there was the recovery and android OS again!!
I will wipe the card first.........
Case closed!