• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CWM Recovery v5.0.2.8 can't mout help please

papo12 said:
I tried to do the first part to run ph44img.zip on hboot, and it parses asks to update recovery then once I accept it tried to update and says
-Fail PU
Partition update fail!
Update Fail!

its what I keep getting when I try to push thru full stock too. Thanks for trying to help. I think its officially bricked!
Click to expand...

wow im sorry i shall do some more research on this
 
Does anyone know if the reason why I keep getting PU-Fail when I try to run ruu or full stock on hboot and signature fail on fastboot is because my phone is unlocked with s-on?
If so does anyone know how I can turn it off?
 
papo12 said:
Does anyone know if the reason why I keep getting PU-Fail when I try to run ruu or full stock on hboot and signature fail on fastboot is because my phone is unlocked with s-on?
If so does anyone know how I can turn it off?
Click to expand...

s-on basically means security measures are in place and i think it has something to do with switching carriers...s-off would most likely mean u can travel from phone carrier to phone carrier...so i believe...but we as a community are trying to achieve s-off but to no prevail...

one of the most renowned on this sight (2fast4u88) was toying with some files to achieve s-off and bricked his phone so we must wait for any further news on that...As far as not being able to flash or root it has nothing to do with that seeing as i achieved root with s-on...your bootloader and what files you're uploading make the difference here why dont you walk me through what you did after unlocking your bootloader or trying to flash the PH44IMG.zip and before you got here...keep in mind that ive been following some of your posts so i know that you manually tried to push files though but yet again to no prevail
 
ddubhotness said:
s-on basically means security measures are in place and i think it has something to do with switching carriers...s-off would most likely mean u can travel from phone carrier to phone carrier...so i believe...but we as a community are trying to achieve s-off but to no prevail...

one of the most renowned on this sight (2fast4u88) was toying with some files to achieve s-off and bricked his phone so we must wait for any further news on that...As far as not being able to flash or root it has nothing to do with that seeing as i achieved root with s-on...your bootloader and what files you're uploading make the difference here why dont you walk me through what you did after unlocking your bootloader or trying to flash the PH44IMG.zip and before you got here...keep in mind that ive been following some of your posts so i know that you manually tried to push files though but yet again to no prevail
Click to expand...

I successfully rooted my phone (with firmware 1.11.653.0 on August 3) following the Flash CWM, Get the latest update to 1.11.653.0 AND Root (BOOST ONLY) I didn't have any problems at all and it was quite easy. I did backups on CWM and never rooted a new rom. I just stayed with my regular stock, the difference was it now was rooted. Never had any problems. Every time I noticed the phone was lagging a little (which was rare) I used to go clear the cache only and reboot the phone and it would operate great. Last week I was just reading in a forum in babycenter application on my phone and it restarted. It just stayed hanging on the HTC screen nothing more. I have to stay, I really don't like messing and playing with different roms on a phone that is complicated for me like this (the samsung prevail I did it all the time with no worries) so believe me when I say I didn't do crap for it to restart and hang. I was too uncomfortable to mess with it being fairly new.

The first thing I did was take out the battery and press power + down lead me to the hboot screen I pressed recovery it sent me to cwm and it gave me those errors #1. I tried to restore my backup and it looked like it was going thru but it hanged and again gave me those errors again.
So I tired to get on fastboot and use the recovery file from the link above and got an errorr message FAILED (remote: image update error)

with the help of Travis (thank you for helping) to restore full stock and it was a hit and miss. Tried using full_stock on hboot and got

1 System fail-pu
2 boot fail-pu
3 recovery fail-pu

-Fail PU
Partition update fail!
Update Fail!

So then 2fast says to find ruu and that should help recover my phone back but every time I try it won't even parse it does nothing but act like its parsing and it doesn't give me any options like the others did. I found it as an exe file then converted it to a zip file changed the txt file to updated firmware.

and then finally tried what you gave to me and it acted like it was gonna work to but gave me the same message

-Fail PU
Partition update fail!
Update Fail!

I just don't understand why it is rejecting everything I try to push thru. I even tried to lock the phone and it rejected that saying something like it didn't have that file. Its acting like it locked me out being in an unlocked position.

I just want to take the chance and thank everyone that has taken time to help me. I really do appreciate your time and help.

 
papo12 said:
after unlocking bootloader I added CWM in fastboot and rooted though CWM by flashing the root zip.
Click to expand...

you might have to start the process over as in installing cwm again and flashing the fusion rom everything should read ok with some of the updated files
 
I tried installing CWM through hboot but I get

*** UNLOCKED ***
KINGDOM PVT SHIP S-ON
HBOOT-1.30.0000
RADIO-1.11.00.0418_2
eMMC-boot
Mar 26 2012, 16:07:45

HBOOT
parsing...[SD ZIP]
[1] RECOVERY -Fail-PU
Partition update fail!
Update Fail!
Press <POWER> to reboot.

it won't accept anything.
 
ddubhotness said:
I wouldve had he been a mean man lol how can you say that about your own partner...lol....well lets just say well known for lack of a better word;)
Click to expand...

I just wanted to use the movie line when I saw that....my definition of course being "more than famous" as in the movie....

:)
 
Failed pu I am not sure and shouldn't be happening if you are unlocked in a way. You also aren't doing what I said to do. You need to relock then run the ruu. Ruu's or ruu in pd42img.zip won't run with out relocking. If you get security errors in fastboot it means you aren't allowed to write to that partition via fastboot, but there is other ways hence how I bricked.

Which means you need to relock, download ruu and try to run. If it fails go to $temp$ via search in windows and then search temp for rom.zip. Copy rom.zip somewhere and rename it to pd42img.zip. Place it on the card and see what happens. If you get firmware to new then the misc image needs changed.

Keep in mind I don't really want to read all these posts to see what you are actually doing or why. So I am unsure of the issue you are really having.
 
2fast4u88 said:
Failed pu I am not sure and shouldn't be happening if you are unlocked in a way. You also aren't doing what I said to do. You need to relock then run the ruu. Ruu's or ruu in pd42img.zip won't run with out relocking. If you get security errors in fastboot it means you aren't allowed to write to that partition via fastboot, but there is other ways hence how I bricked.

Which means you need to relock, download ruu and try to run. If it fails go to $temp$ via search in windows and then search temp for rom.zip. Copy rom.zip somewhere and rename it to pd42img.zip. Place it on the card and see what happens. If you get firmware to new then the misc image needs changed.

Keep in mind I don't really want to read all these posts to see what you are actually doing or why. So I am unsure of the issue you are really having.
Click to expand...

I'm sorry If I'm being a pain, Well I guess that's the main reason nothing is happening at all.... I'm trying to lock and it won't let me lock the phone in fastboot: [FONT=&quot]


C:\Android SDK\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 1.022s

I'm getting now
[/FONT]
[FONT=&quot][FONT=&quot](bootloader) Lock successfully...
FAILED (status read failed <Unknown error>>
finished. total time:1.281s

it reboots and stays on htc screen. How long does it stay like this? I waited like 20 min and still on htc screen. going to keep trying to lock it.
[/FONT] [/FONT]
 
What did you exactly do to cause all of this? As it wouldn't have been turn on the phone and tada you are screwed. Generally when that happens and is a hardware fault, the phone won't power on or do didly really at all.

Which leads me to believe the cause of this is the end user. Also don't take that the wrong way as it isn't meant to be. Just trying to figure it out what caused it to fix it.

Edit: Have you tried to flash any roms via cwm? Or restore some form of backup via cwm? As you say it sets one the htc screen, you have a messed up boot.img/kernel I would say which is fixable. That your the system partition that hold the rom is screwed up or wiped.
 
2fast4u88 said:
What did you exactly do to cause all of this? As it wouldn't have been turn on the phone and tada you are screwed. Generally when that happens and is a hardware fault, the phone won't power on or do didly really at all.

Which leads me to believe the cause of this is the end user. Also don't take that the wrong way as it isn't meant to be. Just trying to figure it out what caused it to fix it.

Edit: Have you tried to flash any roms via cwm? Or restore some form of backup via cwm? As you say it sets one the htc screen, you have a messed up boot.img/kernel I would say which is fixable. That your the system partition that hold the rom is screwed up or wiped.
Click to expand...


I'm not taking anything the wrong way but I wasn't messing with my phone at all. Like I said before I was reading on babycenter and it restarted and tadaaaa...I am screwed. I'm sorry that you don't believe me, or its hard to believe for you but that is exactly how it happened unless there was a virus or something that came in or something else went wrong. The only time I ever did anything was the first time I unlocked the bootloader, installed cwm, and made backups and that was a month ago.

Yes I have tried using CWM to restore my backup, and even tried to install roms but it will stop and give me errors. It won't go thru at all.
E:/ can't mount/ cache/ recovery/command
E:/ can't mount/ cache/ recovery/Log
E:/ can't Open/ cache/ recovery/ log
E:/ can't mount/ cache/ recovery/last_log
E:/ can't open/ cache/ recovery/last_log

I'm sorry I have no idea what has caused this but thanks for at least taking the time to help when you don't have to.
 
It shouldn't stop with that error, when you boot cwm it probably shows that at the bottom. It will still restore the backup or rom.zip. As the the 4 log errors will not affect the operation of cwm. The commands one I am not sure about but doubt it as cwm doesn't live in cache.

So is there another error that shows up after you try a restore or install zip?
 
I will just make another post so you see it instead of a edit. But in cwm go to I believe mounts. Mount all the partitions, then plug the phone in and do adb shell. Then followed by mount or mounts. Can't recall which is right off my head. Paste the output here.
 
2fast4u88 said:
It shouldn't stop with that error, when you boot cwm it probably shows that at the bottom. It will still restore the backup or rom.zip. As the the 4 log errors will not affect the operation of cwm. The commands one I am not sure about but doubt it as cwm doesn't live in cache.

So is there another error that shows up after you try a restore or install zip?
Click to expand...


on trying to restore backup
checking MD5 sums.....
erasing boot before restore
restoring boot image...
restoring system...
it goes black and goes back to the main CWM recovery menu

Installing a rom (xFuZiiOnZz-4.3.2)
formatting system and data

E: error in /sdcard/kingdom_xFuZiiOnZz-4.3.2.zip
(status 1)
Installation aborted

going to try a different sd card just in case
 
2fast4u88 said:
I will just make another post so you see it instead of a edit. But in cwm go to I believe mounts. Mount all the partitions, then plug the phone in and do adb shell. Then followed by mount or mounts. Can't recall which is right off my head. Paste the output here.
Click to expand...

ok on the phone it only let me mount sd-ext
cache, data, system would not mount I would get error

with phone attached on adb


C:\Android SDK\platform-tools>adb shell
~ # mount cache
mount cache
mount: mounting /dev/block/mmcblk0p28 on /cache failed: Invalid argument
~ # mount data
mount data
mount: mounting /dev/block/mmcblk0p27 on /data failed: Invalid argument
~ # mount sd-ext
mount sd-ext
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: Device or resource busy
~ # mount sdcard
mount sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
~ # mount system
mount system
mount: mounting /dev/block/mmcblk0p26 on /system failed: Invalid argument
~ #


I gave in and so I'm having a Boot Mobile Tech unbrick my phone. Should be getting back tomorrow will let you know what the issue was. Thank you all for all the help you have given me.
 
Just wanted to let you guys know, the tech said that the problem was the custom recovery that had not gone thru all the way (or installed completely) and that's what was causing the issue in not letting anything go through at all. I don't get how it just stopped working after a month but oh well.... Wish I knew it wasn't completely installed, everything even the backup worked throughout the time. All in all I'm glad its fixed.
So in a half hr I will finally have it in my hands and working!!
Thanks again for everyone's help!!! This forum rocks.

update:
So the tech couldn't get it to flash because there was water damage and the only time my phone saw water was the same day I bought the phone, the salesman installed an invisible-shield on it and drowned my phone with it. I read the instructions he should have never sprayed the phone at all! Well the store wouldn't do anything so I reported them to BBB and their headquarters contacted me so fast.
All and all I got me a brand new spanking phone today, because of their employee's huge error.
Just wanted to share my experience in case this happens to anyone of you.

Thanks again and have a great day!
 
Hi All,

My Evo Design 4g on boostmobile is exhibiting all the same symptoms as papo12's. I had used apache thunder's stock root method to get root in September after unlocking the bootloader. I haven't updated my rom, it's been at stock. Everything was working fine until I noticed my phone was in stuck on the white htc boot screen when I woke up to use the restroom two nights ago. I have noticed that previously, when applications are auto updating, it'll reboot the phone. I tried to reboot a couple of times, but it kept getting stuck at the boot screen. I then rebooted into cwm and did a restore, but it didn't make a difference.

The next morning I tried to fastboot flash boot and recovery, but it comes back with FAILED (remote: image update error). I've tried to flash oem lock and it reboots the phone. I've tried to put the full stock back on, but it comes back with PU failed, (assuming it's due to bootloader not being locked)

I've tried using HTC's RUU b(in fastboot usb mode) but the phone locks up at some point and the utility will time out.

I'm not sure at this point if there's anything else I can do, any pointers would be greately appreciated.

Here's the hboot info:
*** UNLOCKED ***
KINGDOM PVT SHIP S-ON
HBOOT-1.30.0000
RADIO-1.11.00.0418_2
eMMC-boot
Mar 26 2012, 16:07:45

RUU tells me that the image on my phone is 1.10.653.3

I have access to cwm and hboot only.

Thanks in advance
 
You need to re-lock to run a ruu as you will get a error doing so. What the exact error is though I can't recall as it has been so long. As for your issue I am not sure what is causing this but I would venture to guess it is something you guys have flashed in some shape or form. That or just a hardware failure.

If you can use dd in cwm you should be able to edit the misc image, relock then run the stock ruu. It may fix it or it may not.

How ever I have got the cache issue more then a number of a times, where it never borked my phone. Nor did it ever not boot from it, usually a reflash of cwm would fix the issue for me. I've been through 3 or 4 heros over the past year due to issues I caused.

Lost one, broke one, borked hboot on the last and the one I have now. In turn I am pretty sure that the issue isn't files I have put up. Others files I can't say for sure as I don't flash others stuff.
 
Would you be able to point me in the direction of the specifics of the dd command? Are you recommending trying dd to replace the current recovery? Which device/partition should I write to?

Thanks for your hlep.

FYI: Under cwm, I was not able to mount anything except /sdcard. /cache,/data, /sd-ext and /system all came back with Error mounting which ever mount points.

From adb, I get:

~ # mount /cache
mount /cache
mount: mounting /dev/block/mmcblk0p28 on /cache failed: Invalid argument
~ # mount /data
mount /data
mount: mounting /dev/block/mmcblk0p27 on /data failed: Invalid argument
~ # mount /sd-ext
mount /sd-ext
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
~ # mount /system
mount /system
mount: mounting /dev/block/mmcblk0p26 on /system failed: Invalid argument
~ # mount /sdcard
mount /sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
 
Did you flash anything or wipe anything before this happened? It sounds like a issue I have seen in the past with bad/corrupted blocks. How ever if you did none of the two that caused it I don't see it being that. Nor do I seeing it be that with all the partitions messed up.

As for mounting anything in cwm, that isn't needed but writing to the specific partition using dd. As for the command you will have to wait a bit till I can put something together.
 
I woke up to the white HTC boot screen in the middle of the night. It has been restarting itself when applications auto update. I believe what I did next was to reboot, then tried restore via cwm. When that didn't work I pulled the battery and went back to bed. The next morning I tried to restore again, then started wiping cache partition, wipe data/factory reset, etc. I don't recall the exact steps, I probably did the wipe a few times.
 
You must log in or register to reply here.
Back
Top Bottom