Okay I have been using theunlockr's site in conjunction with xda and droidforums to learn about rooting and such over the last month. I have been rooted for a week or so now and have been enjoying wireless tether and setcpu, but thats about it. I want to do more, ie a custom rom. So I got DL09 Super Clean 's .zip on my sd card, and went into Rom Manager and Flashed Clockworkmod Recovery, then reboot into recovery. I keep getting stone walled here. It says;
failed to verify whole file signature
signature verification failed
installation aborted
then at the top I have the options to;
reboot system now
apply sd card update.zip
wipe data/ factory reset
wipe cache partition
I tried a factory reset then re installed Rom Manager, seeing as super user was still in my app draw I didn't re root. What am I doing wrong? I know you guys hate people like myself but I'm at a loss.
CWM isn't fully installed. See what step you might have missed.
For DJ05 or DL09 http://forum.xda-developers.com/showthread.php?t=913470
For DI01 http://forum.xda-developers.com/showthread.php?t=788099
good day.
another quick question. When selecting update.zip from recovery the screen goes blank and the soft keys light up, how long should I have to wait for something to happen?
If you are in CWM recovery (green text).
Back or power = select (home will black screen but tap home again to turn back on)
Search = Back
To flash a rom/kernel/or theme you will use the "install zip from sdcard' option in CWM.
In stock recovery (blue text)
Home = select.
good day.
Your the man! Thanks!
I tried to install a new ROM on my rooted Droid 2 yesterday (can't remember which one it was now). Long story short, I believe my phone is bricked. Trying to figure out if there is anything I can to to undo it.
Yes, I did a Koush bootstrap recovery prior to attempting to install the new ROM. When I press the "x" key while powering on the phone, I get the android alien logo with the triangle next to it. I then hit the search key, and I get these four options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
And at the bottom of the screen, in yellow letters, it says:
E: Can't open/cache/recovery/command
My question is, how do I access the backed up nandroid and reinstall it? Shouldn't it be showing up on the aforementioned menu of options?
After you bootstrap recovery it should have said "sucess'' and then you hit the reboot recovey option. That take you into clockwork recovery.
Sent from my DROID2 using XDA App
After you install the bootstrap apk, you should hit bootstrap recovery, give it su access, and it should say success. To get into the recovery, go into the bootstrap apk and hit reboot recovery and you should be good to go.
I am running DL09, everything is stock. I rooted my phone, and flashed cwm via odin. Then I installed cwm from the market and from cwm flashed recovery. Via cwm i tried to flash an updated version of cwm, but it didn't work, then I tried to flash the leaked dl30 - it also didn't work. everytime i try to flash anything, i get the following error message:
E: Failed to verify whole-file signature
E: signature verification failed installation aborted.
the top of the screen (when i boot into recovery from the rom manager) says
Android system recovery (2e)
Samsung recovery Utlis
- for BML -
also, when I try to select anything, it only recognized the home soft key as enter.
my only options are
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
what has gone wrong?
I have the same problem. Adrynalyn said something about dl09 being sneaky and killing the cwm loader, so the first boot after running odin we are supposed to flash a clean kernel... I haven't tried it yet, been busy, but I will this weekend before flashing froyo.
Sent from my SCH-I500 using XDA App
I had the same blue text screen with those for options this morning when looking to wipe batt stats. I went ahead and selected the sdcard option, and next thing I know I'm looking at the gen text again with the complete list of options. Maybe try that?
Mmmmm...Froyo!
alright, I updated to 2.2 and I was going to make a backup.. but once I booted into stock recovery and tried to apply the update.zip I got this error
E:Can't mount /dev/block/vold179:9
(no such file in directory)
E:Can't mount SDCARD:bplib_delta_for_test.bin
then..
E:Can't mount /dev/block/vold179:9
(no such file in directory)
E:Can't mount SDCARD:update.zip
Installation aborted
any help would be appreciated. I couldn't find a fix anywhere I read.
thanks in advance!
I have the same issue...
Sent from my HTC Sensation 4G using XDA Premium App
I had this error when I was using imnuts recovery kernel (correct button mapping i.e. camera button selects) so instead I odin'd (haha) adryn's test_2 kernel from the "official" thread (the screwy button mapping i.e. press the menu softkey area) and it fixed the problem xP
I posted what happened in the ec04 stock thread too
Sent from my SCH-I400 using XDA Premium App
i had this problem when i first upgraded to froyo, but i started from scratch which probably wasn't necessary, well here's what i did:
-i odin'd stock dl17 full odin package
-rebooted phone, let it do its thing
-i put the blue(cyan) cwm update.zip file and rom/kernel for froyo on my sd card
-odin'd froyo modem
-odin'd cwm_recovery_test4_adryn.tar
-went to recovery mode and fakeflashed update.zip(cwm)
-wiped data/cache/dalvik cache
-flashed froyo rom/kernel zip file
-wiped data/cache/dalvik cache again
and out of nowhere it all worked again. hmm....again most of these steps weren't necessary but i like to start out from scratch sometimes(bad habit)
thanks guys, all I had to do was use adrynalynes .tar in stead of imnuts. and it worked fine.
Can someone post the dl17 Odin files? All of the links I've found so far are dead.
Sent from my HTC Sensation 4G using XDA Premium App
small warning
I just wanted to put out a small warning to those trying to update to ec03: Do NOT use the yellow version of CWM to attempt a data wipe/factory reset before OR after installing ec03. It will hang on formatting /data and cause all sorts of headaches.
If you ARE stuck at formatting /data already and just found this forum:
hold vol up+down+power for about 3-5 seconds to reboot
get back into yellow CWM
ensure the usb is plugged in and go to storage and mounts
mount the USB storage
copy the cyan CWM update.zip from your computer.
install the update.zip (replacing the yellow cwm's update.zip)
hold vol up+down+power for about 3-5 seconds to reboot
voila, cyan cwm!
continue to do a data wipe/factory reset from inside cwm, ignore the error msgs since the actual sucess messages get hidden by the cwm menu when format is complete.
then reboot & enjoy ec03 froyo
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!