Something went wrong during an ODIN revert to stock, and now when I plug in the phone to the computer or wall it shows the battery charge image for a few seconds, then it says the "Samsung Vibrant" splash and goes straight into recovery mode. I've tried holding down the volume keys, adb doesn't recognize the device. IDK wtf to do. Any help would be so appreciated I'll paypal the person a six pack that can help me fix this.
When it goes into recovery mode it says...
Movi_check Start...!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed!!...
Movi_checking done!..
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
did you try holding down volume up/down, and just plugging it into your computer?( so you can get into download mode)
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
red96turbols said:
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
Click to expand...
Click to collapse
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
wildklymr said:
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Did you try to flash 2.2 by any chance? Easy way to fox your problem is just adb reboot. It will boot up your phone past the recovery screen, and then you can use odin to get back to stock.
Sent from my Samsung Vibrant
red96turbols said:
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Click to expand...
Click to collapse
There is no updated rom available. That function of rom manager is currently unused by vibrant devs. It allows them to make updates to roms and streamline the process, but they simply move on to the next rom. Renaming the update.zip that is used to root to whatever it is is ok for cw recovery, but once you have clockwork recovery flashed since it doesnt replace samsung recovery. When something goes wrong you need its update.zip it puts in root to stay right where it is. By reinstalling packages in samsung recovery is the only way to get to clockwork recovery when you cant load up the phone. If that update.zip is gone or renamed, you're s.o.l.
Sent from my SGH-T959 using XDA App
So if I had kept that update.zip file that CW put on, chances are I could have fixed it? Since I clicked the "Repartition" check box on Odin, would it have even mattered? I used the 512.pit file and the Phone file from the "Unroot" thread by Koush I believe. That worked wonderful, and then I did it a second time and I think something went wrong.
Related
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.
THIS THREAD IS NO LONGER RELEVANT AS IT IS FOR A DIFFERENT ISSUE FROM THE PAST... IT GOT BROUGHT BACK TO THE TOP. DONT CONFUSE THIS WITH THE 3E RECOVERY "ISSUE"
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Update from koush:
@clockworkmod Hey all, flashing recoveries through ROM Manager is busted. We hit a bandwidth/CPU quota on Google App engine.
If you are trying to flash Clockwork Recovery for the first time, it appears that a lot of users are having issues over the past 24 hours.
Normally, you would:
download Rom Manager
Click Flash Clockwork Recovery
it will ask for root privelages
you would select the Vibrant as your phone
after it downloaded CWR you would get a successful pop-up....
you could then click on reboot into recovery (and since it was the first time you would go to the stock recovery, click reinstall packages, and THEN you would go to Clockwork Recovery)....
well.... people can't seem to get there now. I am NOT having issues as I already have CWR. However, if you are, please download this file on your phones browser (just so you dont have to mount your phone to your pc.... which you can do if you prefer)
FILE DOWNLOAD HERE: View attachment update.zip
Move this file to the root of your internal memory. If you have any other update.zip file you can just overwrite it, or delete it prior to moving this file over, your choice....
NOW, go back to your stock recovery and press reintall packages.... you should go to CWR, if not, press to reinstall again... still no luck? blasphemy.
With all of that said, I need someone to post that this successfully works (it should, and you really can't lose anything)
I am contacting koush for an explanation of what's wrong....
i will check this out
everytime i boot into recovery and press reinstall packages my just restarts phone and i can't get into clockwork.
You generally have to tell it to reinstall packages twice.
^ that has not been the case for me.. but try it twice if if doesn't work the first time!
Yeah, it may depend on the ROM being run or something, but I've noticed it quite a bit.
yeah, something happened when rom manager updated in the last day where flashing recovery isnt compatable with galaxy s devices anymore. drove me freakin crazy cuz i just dl'ed nero and went to install and couldnt.
thank you again. +10 internets to u.
I started having an issue after flashing eugenes super kernel. I did a.clean install of axura and problem went away.
Powered by Axura
^ the rom would have nothing to do with it.
Koush has fixed this, it was server related.
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW (NORMAL STEPS STILL INCLUDED BELOW). I KNEW THIS WOULD BE A QUICK FIX FOR KOUSH!
As of 10mins ago i was having this problem.
But thanks to this post and installing the downloaded update I'm back up!
Rom manager gave me errors when flashing the clockwork recovery
so had to go to the update.zip and i'm now back!
Dont think rom manager in the market has been updated
[i was coming from a odin[ed] JFD stock.
hope this helps someone else!
Thanks... this works for me :\
I flashed to JL4 and had a freaking wifi boot loop and gotta go back to Eugene's does not brick ROM and found out can't install CWM via ROM manager
I don't know if its supposed to fix it, but even after flashing this Im still having issues with ROM manager. Get an error every time I try to update the recovery. Also, I can't remember the last time fix permissions actually worked (eclair maybe?).
Anyone else feel my pain?
This is a fix, and you trying to update the recovery is no different than those who have issues not even using my .zip....
I updated the op with a tweet from koush. He has a fix on his site too (might as well download it from here though?
I downloaded the new update, still can't get into clock work. When I hit reinstall packages it says ... E: error /cache/update.zip
(bad)
Installation aborted
Sent from my SGH-T959 using XDA App
^^^ I'm having the same problem as well right now.
reinstall off market and it works
I thought I was sunk until an hour of searching found this post. Thank you all so much!
I have after upgrade to K6 the error messeage:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I've try the update.zip from the 1st post,
reinstalled via market
update und select the Vibrant modell
everytime the same...
the phone is rooted via SuperOneClickv1.5.5-ShortFuse
Any help ?
None of this works because none of it addresses the real problem ,3E signature. Way to much trouble to go thru.
^ This thread was created when the Clockwork servers were down... it has absolutely nothing to do with 3e recovery... as that didnt even exist when this thread was created... hopefully others are not confused now that it was brought back to the top.
I didn't update it yet, because the thread was dead.
And to be fair the OP did have this:
THE BELOW ISSUE HAS BEEN ADDRESSED BY KOUSH. YOU SHOULD BE ABLE TO FLASH CWR VIA ROM MANAGER LIKE NORMAL NOW. IF YOU STILL HAVE ISSUES, THERE IS A FIX POSTED BELOW, THANKS!
Click to expand...
Click to collapse
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
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!
I have a Galaxy S 2, I777 from AT&T. I had been running UnNamed 2.0 for a while. I started messing around with different modem files trying to get my data rate a little higher. When those failed to work, I decided to go back to stock and start from scratch. This is where my trouble begins:
I flashed with ATTGalaxyS2Unroot_SGH-i777.tar using Odin 1.85. I've used that before and all was well. After this flash, I'm stuck in a boot loop. The galaxy s 2 logo just keeps recycling.
I have tried a lot of other items I've found on here in various threads about getting out of a boot loop, but have not been successful. I was able to get to the stock recovery mode, chose to wipe user data and did the "yes I'm sure" option. The phone rebooted and I have not been able to get back to it. When it tries, I get in yellow "deleting cryption meta data" and then the phone reboots.
My last attempt was flashing with i777uckh7-cl503881 full. Odin writes everything, says pass and the phone reboots. After it restarts, it quickly goes through some items:
-- Intalling package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfuly installed package...
-- Copying media files...
successfully copied meida files (yes, media is misspelled on the screen)
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
--Updating application...
Successfully updated application.
--Appling Multi-CSC...(again yes, applying is mispelled on the screen)
installing Multi-CSC
Can't access to '/system/csc/02U/system/'.
Successfully applied multi-CSC
Rebooting.
then I get the boot loop all over again. I am still able to get to download mode using the volume button, and my jig still boots to download mode too, so I think there's still hope, but I don't know what to do next.
Any help would be greatly appreciated.
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Creepyncrawly:
Thank you for your post. I didn't find anything searching for that, but, I downloaded and flashed siyah kernel and was able to get to a recovery mode.
I am now restoring the nandroid backup that I made (luckily I was smart enough to do that) before I started messing with modems and stuff.
We'll see how this goes
you sir are a life saver. I was able to restore the nand backup and boot into the os again.
creepyncrawly said:
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Click to expand...
Click to collapse
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Entropy512 said:
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Click to expand...
Click to collapse
I did not think of that, but it makes sense now. At the time, I figured I would stop and get help before I made it worse. Why I didn't restore to my backup to begin with is beyond me.
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
For those who are experiencing the "Deleting Cryption Meta Data" problem, creepyncrawly is correct, it is difficult to solve, but the following steps seem to solve it reliably:
Download and install the I777UCKH7-CL503881 Stock Binaries from creepyncrawly's download repository. Use heimdall or odin to load the stock binaries. You may need to load the param.lfs and/or the bootloaders. However, it may work without loading these files (and loading the bootloaders can be in the "danger zone")*.
With the stock binaries installed, the device will be in a boot loop, and entering recovery mode will either indicate that the device is installing CSC (unsuccessfully), or indicate that it is "Deleting Cryption Meta Data". In either case, you will be unable to actually access anything in the recovery.
In order to get to a working recovery, load the SGH-I777_ClockworkMod-Recovery_5.0.2.3. You'll need to untar this file to get to the zImage kernel file*.
With the CWM kernel installed, you should be able to actually enter recovery mode by holding down Volume Up + Volume Down + Power until the Samsung logo appears for a second time. Note: In this version of CWM recovery, the home button is the 'select' button and the power button acts as the back button. This is different than most versions of CWM.
Using the recovery run both clear data/factory rest and format sd card (in mounts and storage).
Finally, install the Siyah Kernel, using either heimdall* or CWM.
At this point, the phone should be restored, and you can re-flash the I777UCKH7-CL503881 stock kernel (on any other compatible kernel).
onecoolpilot said:
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
Click to expand...
Click to collapse
You can re-flash any kernel you like.
Thanks everyone who directed me to the steps for solving this problem!
* To load these kernel files, put the phone in ODIN mode by holding down the "Volume Down" button while the phone is connected to USB. Use either the ODIN or Heimdall tool to actually flash the device. See this post for complete instructions on flashing the files.
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Red_81 said:
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Click to expand...
Click to collapse
Is this the "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII that you bought on ebay for cheap, or a different phone?
Do you know the history of this phone? Knowing it can help with troubleshooting.
Did you ever see the "Deleting cryption meta data" error message?
As far as having vulnerability to the eMMC firmware bug, you are safe as long as you don't use the buggy kernel, which is pretty much out of the picture by now.
LOL, you read my other post. It is one and the same. The standard story from the seller. "I gave it to my Brother in Law and now it is like this." He stated it did boot properly before. Liquid indicator checks out (haven't pulled the back off to check the full indicator).
I don't get the "Deleting cryption meta data" but I do get the "multi-csc error". Wiping data doesn't seem to take care of that one.
It's really odd because I can flash ICS roms with no problems, but the GB ones stick at the bootscreen every time. Even CM7 stuck there.
I may have to try to rule out hardware damage at this point
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
creepyncrawly said:
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
Click to expand...
Click to collapse
The one from the repository with bootloaders. I tried the one without bootloaders first, but it did not fix it.
Currently I flashed over to ShoStock2. However, I'm getting alot of problems on that too (Com.android.phone not responding).
I can try to flash back to stock at any moment because I have no data on the phone.
I did try using the latest version of Heimdall, but it kept crashing at 42% (from what I read that is a known bug)
So the one thing you have not tried is flashing PIT? I wouldn't try that next if it was my phone, however, since it is the area I know the least about. There is not a whole lot of information available about using PIT with the I777 (as in nothing I could find).
The behavior of flashing to ICS and running OK but bootlooping on Gingerbread is new to me.
If you have a jig, does the jig boot the phone to download mode?
The phone should be recoverable. If it was mine, I would start by flashing the full stock package with bootloaders and param.lfs again. Then wipe data/factory reset from 3e recovery. Then flash the Gingerbread Siyah kernel. And then wipe data/factory reset from CWM Recovery.
Actually, I thought I typed that before.
I did flash the PIT file at one point out of desperation.
I have a jig that works beautifully (wipes the counter too) and has been a big help through this whole thing. That tells me I should at least have the correct bootloaders.
Do I need to let it attempt to boot between each flash or just go directly one to the other?
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
creepyncrawly said:
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
Click to expand...
Click to collapse
I actually found and tried that a few days ago. Never got that error message before. But I flashed the repair anyway. No change.
I did manage to just let the phone run for a while and all the process error messages went away, but the dialer refuses to start. I also noticed I don't think I'm getting any sound out of the earpiece.
I think I'm going to have to take the back off to check for water damage and to make sure they didn't bleach the dot.
I'll attempt to do some more flashing later tonight if the wife lets me.
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
creepyncrawly said:
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
Click to expand...
Click to collapse
Lol. Under normal circumstances indeed. I appreciate all the help so far. I wonder if there is something borked with the chip.
Sent from my SAMSUNG-SGH-I897 using XDA
Not sure if it helps much since you said you think the correct bootloaders are there but I had the exact same problem as you a couple months back. Like an idiot I flashed the original "one click" ATT ICS leak from Rootzwiki that updated my bootloaders. After this attempting to go back to CM7 resulted in me soft bricking the phone. The ONLY rom that would flash and work was that same ICS one click. Everything else Odin just failed on. Eventually I managed to get the complete stock GB back on it by flashing the full package in creepys guide several times. I gave up on Odin on my pc and had to remove Kies from my Mac so Heimdall would work but it flashed finally and I was saved. If you search through my posts here and find that thread maybe there's something in there that will help cause it sounds like you're having a bootloader issue like I did..
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks. I'll take a look.
On a side note.... I can't get any sound from the device. I'm thinking now that it might be hardware related.
Sent from my SGH-I777 using xda premium