Hi,
I'm trying to partition my SD card (8G class 10) using the RomManager without any success.
After I chose all the parameter for the partition, the phone reboots and I receive a black screen with a droid and an orange exclamation mark.
The phone will stay like that (I left it for the whole night) unless I'll enter the recovery screen by pressing PWR+VOL UP.
If I do that I get the following error messages:
ClockworkMod Recovery v2.5.07
finding update package
Opening update package
E: failed to seek in /cache/update.zip (invalid argument)
E: signature verification failed
instalation aborted.
I'll get the same errors if I'll enter the recovery from using the RomManager option.
If I'll enter the recovery via HBOOT these errors are gone.
My HTC desire is rooted, S-ON
Hboot 0.93.0001
Android 2.2.
Besides that I don’t have any other problems and the phone is working fine (or so I think )
Thanks in advance
Markiz
markiz83 said:
Hi,
I'm trying to partition my SD card (8G class 10) using the RomManager without any success.
After I chose all the parameter for the partition, the phone reboots and I receive a black screen with a droid and an orange exclamation mark.
The phone will stay like that (I left it for the whole night) unless I'll enter the recovery screen by pressing PWR+VOL UP.
If I do that I get the following error messages:
ClockworkMod Recovery v2.5.07
finding update package
Opening update package
E: failed to seek in /cache/update.zip (invalid argument)
E: signature verification failed
instalation aborted.
I'll get the same errors if I'll enter the recovery from using the RomManager option.
If I'll enter the recovery via HBOOT these errors are gone.
My HTC desire is rooted, S-ON
Hboot 0.93.0001
Android 2.2.
Besides that I don’t have any other problems and the phone is working fine (or so I think )
Thanks in advance
Markiz
Click to expand...
Click to collapse
ROM Manager is not an ideal solution to partition your card. I've found that the easiest solution is to use a dedicated partition manager like Gparted or use the partition manager of a Ubuntu LiveCD. If you have a spare blank cd, create a bootable cd with gparted, and use it to partition. Anyway, ROMmanager has a lot of limitations with partitioning, it's not at all flexible with sizes.
Hi,
Thanks for the quick reply.
One more noob's question.
After creating the partition (btw any recommends regarding optimal partition sizes ( is there anything else I should do to activate the a2sd+ option or it will be done automatically ?
Anything around or above 512 Mb should be fine. Dont go above 1.5Gb though. A2sd+ is automatic
You have to turn signature verification off in recovery. Boot in to recovery, then select "install zip form SD" there is the option to toggle signature verification, do that and reboot. Now you can use rom manager.
If you feel that you are not sure about using Gparted and stuff, continue with Rom Manager. In the Rom Manager menu, click flash ClockworkMod recovery and then select the options to partition your SD Card
Thanks,
I used Gparted and it worked like a charm
markiz83 said:
Thanks,
I used Gparted and it worked like a charm
Click to expand...
Click to collapse
Good to know..
Gparted and its sibling in Ubuntu are really great if you want to play with your partitions, like resizing them.
Originally posted here:
This happened to me yesterday; my phone told me I had some updates from the market, and it froze mid-updating an app (don't remember which one).
I pulled the battery and the phone went directly into recovery, and it has stayed there ever since.
I tried everything, wiping the cache, the boot, dalvik, EVERYTHING. I even did the factory reset/data wipe, and in the end it tells me the same thing:
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
Is there something that I overlooked? My phone isn't even able to be "seen" by my computer, the only way I can turn it off is by doing a battery pull, and when I put the battery back in, it goes straight into CWMod's recovery.
Click to expand...
Click to collapse
jrizk07 said:
re flash your ROM since you're in recovery. otherwise restore a nandroid backup and that'll get you up and running again.
Click to expand...
Click to collapse
I 've tried flashing trinity 2.6 and it aborted the installation citing a (status 7), I had tried to previously install coredroid multidevice (3.5) and it had aborted it as well, citing a (status 1); I downloaded clockwork 5, as well as 2 other roms; miui.us vivow 1.12.30, which was also aborted with a (status 1) and JmzRunyInc2v1, this one managed to go through "deleting stuff", "Installing stuff", "Symlinking stuff", "Installing bussybox stuff", "Flashing kernel stuff" and then "done" followed by "Install from SD card complete", but when I chose "Go back" it gave me the same message:
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
So, when I rebooted, it went again into CWMod.
Is there anything else I'm missing?
Doing some reading it looks like your recovery image is corrupted. You'll need to re flash your recovery manually.
You can get into the bootloader correct?
Noob's Guide #6: I just HTC Unlocked, what now?
Thank AgalychnisCallidryas
yeah, when I turn on my phone, it goes directly into CWMod, but I can go into Hboot, and select fastboot, recovery, etc., but the problem is my computer isn't able to identify the phone when it gets plugged in.
EDIT: I tried HBoot USB, and it tells me the drivers aren't correctly installed, something about android 1.0.
Do you have any access to a Linux/Mac machine?
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Edit: I was able to get the android dsk and platform tools from an old backup, I'll try to give this a go with it.
cowboyv said:
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Click to expand...
Click to collapse
Use a windows computer, it's pretty simple. You'll probably need to uninstall the current drivers on that computer (Control Panel> Add Remove Programs or Programs under windows 7, Make sure all HTC Drivers are uninstalled)
Then go here
http://forum.xda-developers.com/showthread.php?t=1298990
Install the HTC USB drivers and go from there.
LOL. I just use mac, no drivers required.
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
cowboyv said:
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
Click to expand...
Click to collapse
Read this and take note http://forum.xda-developers.com/showthread.php?p=18016711#post18016711
You need to be in the bootloader and not recovery in order to do what you need to do.
You cannot re flash the recovery from CWMod. Remember the white screen with the android guys skating? That's where you need to be.
Either hold down the volume down button and hold power, or if you have your device detected by adb you can
adb reboot bootloader
This is where you flash the recovery image via fastboot.
http://forum.xda-developers.com/showthread.php?t=1134520
Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
That worked, but...
jrizk07 said:
This is where you flash the recovery image via fastboot. Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
Click to expand...
Click to collapse
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
cowboyv said:
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
Click to expand...
Click to collapse
Right, Just follow this procedure and start over from scratch completely. Do not restore a backup because it seems to be corrupt.
http://forum.xda-developers.com/showthread.php?t=1298990
Ok, I downloaded the zip file vwhk-12102011-c and have extracted it to my C: root, however, when I try to do the first code
Code:
adb shell rm -r /data/local/tmp/*
ADB tells me "error: device not found".
Now, apologies beforehand, as you may have noticed this is my first android phone and I am a noob, so some of my questions may seem a bit obvious to you.
1. I read that I rename the ruu to PG32IMG.zip, is this true?
2. Should I continue and flash the RUU zip via adb, or should I push the RUU?
3. Should I simply put the zip in a microsd and then restart the phone in bootloader?
EDIT: Nevermind, went ahead and did 1. and 3. and that worked. I still have the root access, but I need to re-install a recovery.
Once again, thanks.
So I received an update for the phone and figured it should be ok given that it's a security update, first one in ages for HTC One m8 and my phone got stuck in boot screen. As I understand it this is what happens as a result of Lollipop and a rooted device, binary and all that rubbish. This I knew AFTER doing the update. Honestly didn't think it would be a problem with an official update but ok...
So this is how it went thus far.
Tried installing back older firmware - nothing.
Tried to RUU but can't, doesn't detect my phone.
Can't even install HTC MTP driver on windows, error code 10...
Device has been fully wiped.
Tried to put the ruu in .zip form on SD card 0p6bimg etc, SDCard it claimed was damaged and needed to be formatted. SDCard is wiped completely.
Stuck in boot screen, no way to flash custom recovery, custom rom etc as my device cannot be detected.
I've been trying to do the usual for close to 10 hours now that I've been busy with this phone and I'm about 1 minute away from thrashing this P.O.S to pieces against a wall. Before that happens I figured I might as well come on here and ask for anymore suggestions.
Thank you.
Additional details about phone: S-OFF, Originally used to be HTC_203 EU device, converted it to Developer Edition. MID/CID are still correct, never changed that after the initial conversion.
Don't know if it's of any relevance or not but in recovery screen(stock recovery of course) it shows following message at the bottom:
E : missing bitmap oem_unlock_bg
(Code -1)
E : missing bitmap oem_unlock_bg_yes
(Code -1)
E : missing bitmap oem_unlock_bg_no
(Code -1)
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
ckpv5 said:
Hey old mate !
That's normal in stock recovery but what is written after those line is important for the error reading.
Have you tried to use a card reader to read your microSD ? Or you use that mount with TWRP ?
Which RUU.zip ? Is it the ROM.zip that you got from TEMP folder on PC ?
Click to expand...
Click to collapse
It was ROM.zip from temp folder yes. I sorted the issue out though, for one or other reason it read the rom.zip after a huge struggle. I tried it at least 7 times and for some reason it took on the 8th, not that anything changed at all. It was the same .zip renamed to 0p6bimg.zip, don't know what changed to have it work after so many tries. The only real thing that "changed" was my frustration in it and I ended up hitting the phone against the desk Yes...it picked up physical damage on the side too, right by the volume buttons it "bent" out a bit :crying:
So the phone is working again but not very happy lol I lost all my data I had on my phone, lost all the data I had on my sdcard... Physical damage of course.
First OTA in ages and this is the nonsense a person has to deal with. Honestly I didn't expect it to give this problem as I haven't been to the forums in ages I didn't read up on this issue. Thought it would be fine lol. Quite disappointed but what can you do.
Hi, maybe your SD card has reached the end of its life? How old is it? Phone said it was damaged and then took a really long time to read.
Could be time for the 128gb upgrade...
I have an ASUS ZenFone 2 (550 model), and I got a Push Notification about an OS Update, so I went ahead and installed it. After the phone installed the Update and rebooted, I got in a Bootloop. I can get into the Bootloader, the Stock Recovery, and the Temporary ClockworkMod Recovery mentioned here:
Code:
http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063
ADB also works, thankfully.
My phone is rooted, and I'd like to unlock my Bootloader, and install CyanogenMod, after I get out of this Bootloop.
Could someone please help?
EDIT:
Silly me, I forgot to mention the problems I actually had while trying t solve the bootloop.
So,
Problem #1: If I try to flash Firmware, the stock Recovery stops at 25% (It continues going until 50% in ADB), and then i get this error:
"E: failed to verify whole-file signature
E: signature vertification failed"
Problem #2: CWM cannot use my MicroSD. If I go to "Install zip from sd card", it doesn't show the actual SD card, jus three empty folders. I tried to mount "ext-sd" in the mounting options, but it fails to mount. (My MicroSD is 32GBs and formatted in Fat32, so it should work. :/ )
My phone is on official software and has been stuck in a boot loop for probably nearly a year. It's been collecting dust and I'm looking to use it as at least a media player. I don't know why or how this happened, since I haven't even flashed a custom ROM on it (this isn't the one in my sig, I broke that one and this is the replacement).
Anyways, to get to the point. How can I make this phone usable again? It's S-ON, HBOOT 3.19.0.0000.
Can I still use ODIN to flash a stock rom, even though it's S-ON and not rooted?
Also, if it helps, in the stock recovery it says:
Android system recovery <3e>
LRX22G release-keys
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
Factory resetting doesn't do anything at all.
xLoveHateLegend said:
Can I still use ODIN to flash a stock rom, even though it's S-ON and not rooted?
Click to expand...
Click to collapse
ODIN is Samsung specific, it doesn't work on HTC devices.
The most you can probably do is run the RUU, if there is one for your M8 version. If RUU doesn't fix it, you are probably looking at a hardware (emmc) failure. Which the symptoms also suggest to me.
redpoint73 said:
ODIN is Samsung specific, it doesn't work on HTC devices.
The most you can probably do is run the RUU, if there is one for your M8 version. If RUU doesn't fix it, you are probably looking at a hardware (emmc) failure. Which the symptoms also suggest to me.
Click to expand...
Click to collapse
Crap! You're right. Can you tell I've switched devices way too many times? Haha.
I'll give RUU a shot tonight. I'm hoping it's not hardware failure, because I feel like with Sprint, it's way too late to make a claim now (also screen has a hairline crack, so they wouldn't replace it due to physical damage).
If its the Sprint version M8, the RUU is here (near the bottom of the webpage): http://www.htc.com/us/support/htc-one-m8-sprint/news/
Unless you have the Harman Kardon Edition, in which case, its here: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/