I'm very sorry if this isn't in the right spot. I've looked around a bit, and used the search engine, and I haven't been able to find anywhere that I think this belongs. Anyway, here's my problem.
Ok, so here's what happened. I was looking at my build.prop settings in rom toolbox. Out of curiosity, I changed lcd density from 240 to 160 just to see what it would look like. I planned on changing it right back immediately but Touchwiz kept force closing.
I then tried restoring my phone back to factory, but my recovery no longer works. I know how important it is to give as much detail as possible so here's the ENTIRE output from after rebooting into recovery, clearing user data, clearing cache, and then reinstall packages...
#MANUAL MODE#
--Applying Multi-CSC
Installing Multi-CSC
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I had previously tried installing ClockworkMod Recovery ( through Rom Manager ) and thought it had failed because when I rebooted, it took me into the stock Samsung Recovery Utilities. Now I'm thinking that it may not have actually failed, and that I had to select 'reinstall packages' and that would have finished the ClockworkMod recovery install. I'm now thinking that the failure to verify whole-file signature is happening because I no longer have root due to clearing user data, and clearing cache. I may be wrong, idk.
I know how to reset the build.prop lcd density setting to fix that issue, but I have to wait for my aunt to get her computer back to root again. She's currently having it fixed, and I have no other access to a computer.
What I'm asking for help with is to either get my recovery utilities to be functional again in case I ever need to do a hard reset, or get ClockworkMod installed. Whatever is safer is the route I want to go.
I'm kind of thinking that ClockworkMod not fully installing itself is stopping the recovery from functioning like normal. The reason I think that is because I've restored my phone to factory stock many times. The sdcard was NOT in the phone those times and now it's trying to use 'update.zip' from the root of the sdcard when I select reinsall packages. Kind of like ClockworkMod recovery is partially installed, enough to try to use itself instead of the stock recovery, but not enough to be a working recovery.
As I said above, I'd really like to have a working recovery on this phone. I'm actually homeless at the moment, and I have absolutely no money to buy a new phone. Shiiit, I have to bum money from customers at a shopping center every single time I want to eat even. This phone is basically the only thing that keeps me sane. Being homeless is REALLY, REALLY boring as you can imagine. This phone makes it much more tolerable.
Sorry for the length of the post. If there's any other details that may aid in fixing this, let me know and I'll post them. I'm pretty sure I've provided all the detail possible though.
Ok, I typed that up while I was away from wifi, and decided to do a little more research before posting. I'm seeing that I was right about the ClockworkMod recovery not being fully installed. I didn't do the last step of rebooting and then reinstalling packages originally. Now. I'm wondering if the signature verification is failing because I no longer have root access or if it's something else. If that's it, I'm going to finish the installation once my aunt gets her computer back unless there's some way I can get it to reverse the partial ClockworkMod install.
Again, I'm sorry if this is in the wrong place, and for the length. Thanks in advance for any help you can provide.
Related
I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Zerox12 said:
I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Click to expand...
Click to collapse
Clockwork
10 chars
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Zerox12 said:
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Click to expand...
Click to collapse
He is saying to install the Clockwork recovery in place of Amon Ra.
The 10 character thing is a limit to this forum - each post has to be at least 10 characters long. "clockwork" has only 9...
Well then that made no sense because I said in my first post that I am running clockwork recovery.
he us saying clockwork is the problem. many eris users have had many issues with clockwork.
amons ra FTW
Same problem except...
I have an EVO and tried to return it to stock condition prior to return. I can not get off of the Hboot screen, except into recovery. I have several "nandroid copies" on my SD card but none of them will load. I an getting the same "error while writing boot image" can you tell me step by step what to do?
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Zerox12 said:
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Click to expand...
Click to collapse
Repeat after me:
"I don't know what happened. I was charging it while I slept overnight, when I woke up the charge LED was off and the phone will not turn on. Yes, I tried charging it through both the charger and just the usb connected to a computer. No it hasn't worked at all since."
Also clockwork for Eris bricks phones. People need to stop friggin using it.
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
jfigura said:
I have a SF running on DI01. It is rooted using Z4. I installed Rom Manager and then flashed latest Clockwork Mod Recovery. When I reboot the phone into recovery, and then select update.zip to get into Clockwork, I am met with the following:
E: failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I originally got this phone this worked fine. The issues started AFTER I did a factory reset. I did the factory reset because I was unsatisfied how the phoen operated after doing a recovery with Titanium Backup and wanted to start fresh again.
I made sure to delete all traces of every file and folder prior, I even used a brand new formatted SD card and I am still getting this problem. I have been through 2 factory resets trying to get the recovery to work.
Anyone with any ideas would be much appreciated. Thanks in advance!
--JD
Click to expand...
Click to collapse
You cant flash clockwork recovery from the phone it has to be pushed in odin then you can flash it in rom manager
The thread is in the development section
Do a little searching around and you ll find all the info you need
Yet another reason not to use z4 root as you learn nothing about your phone
And really it aint hard to do things the" right" way
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Soba - Once I repushed from Odin it came back. Scratching my head a little but hey it's back. I used Z4 on this phone because I got caught by Verizon when I manually rooted the first model which went bellyup after having it for a week. I wanted to make sure I could quickly get rid of the root if I needed to go back into the store.
To the other responder, sorry for not being specifically "clear".
I've been tinkering with 6 different phones from this one to two Motos and 3 different HTC's. All the methods are beginning to run together sometimes.
I appreciate the assist and I thank you both.
soba49 said:
Actually it sounds like you did read.
My best guess is you went wrong when you installed the SD card and have the wrong update.zip on it, but it's just as likely you need to prime CWM again in odin. You'll be fine!
I do agree that the guides should give manual roots, not one clicks. The slow way is pretty quick:
http://forum.xda-developers.com/showthread.php?p=9443125
I don't think rooting was your issue in this case though. I think you may have missed how clockwork installs and works. It is persisting but not permanent.
In brief, you pave the way with the cwm odin flash, then use rom manager to place a current version of CWM recovery on your SD card in the form of update.zip, then 'install' that every time you need to run CWM.
Read post #179, then build a little shrine in the corner of your house for angel12:
http://forum.xda-developers.com/showthread.php?t=788099&page=18
Swyped from my i500.04 (bh &1129) using XDA App
Click to expand...
Click to collapse
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
woodaresick said:
So I'm getting stuck at the same place. I'm new, so could you explain how to pave the way with Odin? I think I understand the concept, but I'm looking for a detailed list of flashing things (such as the update.zip from cwm) in Odin to my phone.
Thank you for any input!
Click to expand...
Click to collapse
Here's Update.Zip file for CWM
Direct Link, I uploaded it by myself, couldn't find decent one
http://www.4shared.com/file/ReRrCtwV/update.html
Make Sure to thank me if it works
If it doesn't let me know.
MY TBOLT MUST DID THE OTA OR ATLEAST TRIED TO WHILE I WAS SLEEP NOW IT KEEPS POWERING OFF THOUGHT I HAD ROM MANNAGER TO RESTORE A BACK UP OFF MY SD BUT IT MUST DIDNT INSTALL AFTER LAST UPDATE I ONLY HAVE JUST THE PREMIUM LICENSE. I THOUGHT IT WOULD STAY POWERED LONG ENOUGH TO GO DL ROM MANAGER IN THE MARKET BUT IT WONT. I TRIED DL THE NEW OTA SO I CANN PUT IT ON MY SD AND FLASH HBOOT BUT IT KEEPS NAMING WITH THE .ZIP.ZIP EXT NO MATTER HOW MANY TIMES I RENAME IT WHAT CAN I DO I LOOKED HERE http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html BUT I NEED ROM MGR DO I NEED TO DL A STOCK AND UNROOT IT WHAT CAN I DO.... HELP PLEASE SAD PART I WORK FOR VZW AND I KNOW HOW THEY DO WITH EQUIP CHARGEBACKS
First, locate your caps lock and TURN IT OFF. Next locate your period key and put them on the end of your sentences. Making sense of your post is giving me a headache.
Now, on your computer you need to disable the "hide file extensions for known file types" option to fix the zip.zip problem. Can't give you exact directions since you didn't say which os you're using.
Sent from my ADR6400L using Tapatalk
Windows7 currently
I have the same problem and I tried to get in through the clorkworkMod adb shell, but the device is not recognized by adb...? When the device boots up it is recognized. with my DINC I could use the shell while in clorkworkmod.
Is it showing as device offline or not showing the device at all. If its offline, through cmd, close adb server, then start it back up, half the time that fixed that problem for me. If its not showing at all, try setting it to HTC Sync i believe was the one i had to do at one point for it to register. I've rooted 4 times using ADB method and each time its been a little different, so i can't narrow down what i'm doing wrong to help you more with the adb, sorry.
Similar Issue
Hi All and thanks to all the cats on here that willfully give their knowledge! I have a Tbolt - Rooted with Revolutionary, stock rom (removed VZ Bloat via Titanium ), but this latest OTA update is not leaving me alone. I try to reject it and magically a few days later I get out of nowhere reboot and then the android exclamation point with a triangle. I use the Clockwork Mod Recovery to wipe data cache and reboot which makes the update manager get upset saying it failed. The error I see in Clockwork is this:
CWM Recovery V5.0.2.1
E: Failed to verify whole file signature
E: Signature Verification Failed
Install Aborted
So how can I get this update (I am assuming it is to fix the HTC fail for new exploit out there) which I think would be a good thing. I am not ready to flash a custom ROM yet so please don't reply saying "Just flash with my favorite ROM"
Thanks ahead of time!
It pushes the update, and if you don't reject within 3 mins, viola, you have a nice new update. If you can still get into recovery, which it sounds you can, install a stock rooted either full or debloated. Thats the updated equivalent to what you have now. Make sure you grab the rooted though. Here is the full rooted (not debloated) http://www.multiupload.com/H06XI7W380
from this thread
http://forum.xda-developers.com/showthread.php?t=1312193
I'd probably wipe cache and dalvik cache, but you can probably leave data since you're staying stock.
Thanks for the direction nbdysreal!
(CM9 Build 20120502 dated 2012-05-03 06:19:39)
I'll start off acknowledging my idiocy...I started tinkering with things I knew too little about. I messed up my phone fairly severely today, but managed to get it up and running again...with one issue. I no longer have a cellular connection (voice or data). I was having trouble the last couple of days, as I couldn't access the "More..." settings under "Wireless & Networks", but I figured it was a bug in whatever release I was running at the time and would be resolved eventually. I semi-borked my phone early in the afternoon (I repartitioned the internal storage incorrectly), but it was still able to connect. I then really borked it by tinkering with the partition tables. I was able to get that restored via parted restoring the GPT and doing some magic I didn't quite catch. I had previously attempted to flash back to stock via heimdall at one point, so I had an unrooted kernel and whatnot. I managed to flash a kernel with CWM, which allowed me to restore my last nandroid image. I've tried flashing a new modem. I've tried a complete wipe (data, cache, dalvik cache), but I get no connection. I have wireless, so that's something...but definitely not optimal.
Is this fixable? Should I try re-restoring to stock (from a workable state this time) and starting over from scratch? I have a rooted stock nandroid that I'll probably try restoring tomorrow. Could this actually be a hardware issue that just happened to show up at the same time I borked the rest of the phone? Any help/advice you have is appreciated!
EDIT: I've flashed back to stock, including flashing the bootloaders and param file. On first boot after flashing, I get the following error:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
If I click "reboot system now" the system will boot, but without service. I can still hop on wifi if available, but I have no phone, and no data away from wifi.
EDIT 2: I fixed it, and I'm putting the info up here in case someone comes across this post. I downloaded [urlhttps://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&feature=also_installed]GSII_Repair[/url] from the market, and stepped through the first two steps of the repair process. After step 2, it tells you to reboot. Once I rebooted, I was up and running. I will be making a complete backup of efs.img and the rest of my system just in case I do some stupid tinkering again, and if you're here, I'd advise you do the same. It appears this can spontaneously happen based on a couple of other, less stupid methods (at least according to the comments on the app).
I would flash back to stock using odin or heimdall. Give yourself a clean slate to start over. I don't think that it is hardware related as it was working before you started tinkering.
So I flashed my original stock (rooted) image, which didn't help. I then heimdall-flashed back to pure stock. Still no go...however, it then booted directly to stock recovery with an error: "failed to mount /efs". After another couple of searches, it appears that normal flashing doesn't touch this. Given my phone is already pretty messed up, is there a good way to try fixing this?
The entire text in the stock recovery is:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
SUCCESS!!! I downloaded GSII_Repair from the market, and started stepping through the "repair" steps. After step 2, it said to reboot. I rebooted. I now have signal, and can make calls.
I was really starting to think I was screwed there for a minute.
Hey guys, first post. I'm sorry if this has already been done. I've searched and come up with some threads for other phones and I'm really, really getting nervous and need to just have a definitive answer to my problem because I got this phone less than a week ago.
So I rooted using this guide (I have a Telus i717) (I guess I cant post links) on rootgalaxynote .com for the i717
and went with this 'ics objection rom' found under i717 roms on rootgalaxynote .com
it was working fine until I restarted the phone, the screen went black but the capacitive buttons were still lit. Entered recovery and tried to recover,
keep getting these messages E: Can't open /cache/recovery/log - E: Can't open/cache/recovery/last_log
When I try to wipe cache it says Wiping cache... Formatting /cache... and just hangs there, nothing happens. The phone is functional now, I can boot it up and make calls and use it regularly and whatnot, but I need to fix this.
Also, my issue is that I need to be able to fix it on a Mac. Well, I don't NEED to but right now my PC is an hour train ride away and it would be much more convenient to be able to fix it with a Mac (that is, if the only way I can fix it is by using some sort of Odin-type thing that I used in the first place)
Again, sorry if this is in the wrong place or it's been covered before but I'm getting concerned that I've somehow caused some permanent damage? 5 day old phone...
Thank you in advance for any help!
Evan Watts
try to wipe dalvic cache first then wipe cach
Enter recovery with the buttons not by any app like Rom Manager.
Try flashing this touch recovery from your current recovery: http://forum.xda-developers.com/show...touch+recovery (the zip labeled CWM)
Then flashing the rom zips again after wiping data/cache.
I had the same errors happening when I updated my recovery to the latest version via Rom Manager. Then I reverted back to the original CWM touch recovery I had before, and everything wiped and flashed just fine.
just install a new version of CWM or re-install the one you last used... that was the only thing that worked for me
Lol... this post is from July of last year
Sometimes it takes a while for some members to get their answer together and post it.