Hey there.
First, I am new to this. I followed instructions on how to root my galaxy s2. Now, my phone is rooted. Tried to load clockwork version 5.0.2.7 by putting the zip file and loading it while in recovery. When I try, I recieve a exclamation mark inside a triangle. It tries to load, but stop.
I also recieved "E:failed to verify whole-file signature, E:signature verification failed."
I then tried downloading rom manager and doing it from there. Same thing. It will start and then I will ge the triangle again.
Love the phone. But, if I cannot put custom roms on it, imma return it.
Any help ia appreciated. Again, I am new to this. So, basic instructions for me please!
Thanks in advance!!!!
ssgferrrell
try maybe the right forums
Related
So here's the deal. I have A rooted Droid Incredible and i cant get past the splash image. I tried going into recovery and wiping everything and flashing a new rom but I keep getting the following message:
E: Can't mount dev/block/mmcblk0p1
It comes up when i try to flash a rom and says installation aborted about halfway through installing. It also comes up when i try to wipe and do a factory reset.
If anyone knows a way around this It would be immensely helpful, because as of right now i cant use my phone which is a problem. I'm running clockwork recovery v2.5.0.5.
Dr0pSh0t said:
So here's the deal. I have A rooted Droid Incredible and i cant get past the splash image. I tried going into recovery and wiping everything and flashing a new rom but I keep getting the following message:
E: Can't mount dev/block/mmcblk0p1
It comes up when i try to flash a rom and says installation aborted about halfway through installing. It also comes up when i try to wipe and do a factory reset.
If anyone knows a way around this It would be immensely helpful, because as of right now i cant use my phone which is a problem. I'm running clockwork recovery v2.5.0.5.
Click to expand...
Click to collapse
no clue how to fix, but didn't you make a nandroid? restore to that for now so that your phone at least works, until you get an answer.
Dr0pSh0t said:
So here's the deal. I have A rooted Droid Incredible and i cant get past the splash image. I tried going into recovery and wiping everything and flashing a new rom but I keep getting the following message:
E: Can't mount dev/block/mmcblk0p1
It comes up when i try to flash a rom and says installation aborted about halfway through installing. It also comes up when i try to wipe and do a factory reset.
If anyone knows a way around this It would be immensely helpful, because as of right now i cant use my phone which is a problem. I'm running clockwork recovery v2.5.0.5.
Click to expand...
Click to collapse
What you want to do is RUU. Go to the link in my siggy 3G drops, and d/l the RUU.
I'm not the most knowledgeable here by a long shot, but I feel your panic. First thing I would try is pulling the battery, waiting a few minutes, and then put it back in, boot to recovery, and try to restore your backup. Fingers crossed- at least this will hold you until someone who knows more than I starts asking the right questions.
Oh, and second, try searching for that error message maybe.
That's all I got. Good luck!
Edit: while I was writing this, two others gave advice first
I am a relatively newbie at rooting, but hopefully I am not as hosed as I think I am. Using the Zedomax Epic Touch Kernel method (http://www.youtube.com/watch?v=2qVcB9ktEwQ&feature=related), I rooted my Sprint SGS2. However, had trouble flashing Clockwork Mod. Recovery 3e requires signature verification for flashing external files, so it's puking when I try. Throws error can't read file signature, hard stop. SO, had the brilliant (?) idea to try replacing the ROM with Max's new one: SPH-D710_Zedomax_EpicTouchKernel-v2.tar. Flashed that, and now when I boot into recovery it gives me error (exclamation point inside triangle w android dude). However, when I then hold down power button for several seconds it actually _then_ goes into Clockwork Mod (orange menu). So something not quite right, plus install is a bit buggy (sometimes phone calls don't release when hang up and need to reboot phone, battery draining way too fast), so, should I try something from the ClockworkMod Recovery, have I gotten around my signature verification issue, how far do I need to backup to unwind this? Want to get a full Recovery going so I can start flashing ROMs. Big thanks to whoever thinks they can help...
Axilarry said:
I am a relatively newbie at rooting, but hopefully I am not as hosed as I think I am. Using the Zedomax Epic Touch Kernel method (http://www.youtube.com/watch?v=2qVcB9ktEwQ&feature=related), I rooted my Sprint SGS2. However, had trouble flashing Clockwork Mod. Recovery 3e requires signature verification for flashing external files, so it's puking when I try. Throws error can't read file signature, hard stop. SO, had the brilliant (?) idea to try replacing the ROM with Max's new one: SPH-D710_Zedomax_EpicTouchKernel-v2.tar. Flashed that, and now when I boot into recovery it gives me error (exclamation point inside triangle w android dude). However, when I then hold down power button for several seconds it actually _then_ goes into Clockwork Mod (orange menu). So something not quite right, plus install is a bit buggy (sometimes phone calls don't release when hang up and need to reboot phone, battery draining way too fast), so, should I try something from the ClockworkMod Recovery, have I gotten around my signature verification issue, how far do I need to backup to unwind this? Want to get a full Recovery going so I can start flashing ROMs. Big thanks to whoever thinks they can help...
Click to expand...
Click to collapse
Try the Epic Touch forum, you may have better luck.
Hi. So I was rooting my Note2 using the video from the tethering post. I used Odin and ran the openrecovery-twrp-2.3.1.1. It gave me the green Pass message. But when I boot into recovery, I don't get the nice interface, I get the Android System Recovery <3e> screen with text only options. With this I can apply CWM-SuperSU but it gives me an error, but says it installs fine. But when I run SuperSU, it errors out because there are no binaries installed. I even redid the Odin and use the 2.3.1.4 version of twrp, but same exact thing. I even tried flashing twrp from the Recovery but still the same.
Anyone have any advice or tips? I'm sure I'm just missing one step or something. THANKS!
I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny
Dannypolodown said:
I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny
Click to expand...
Click to collapse
did you install a custom recovery such as cwm or twrp?
Dannypolodown said:
I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny
Click to expand...
Click to collapse
Its easier just to odin a rooted version of the factory image.
You can find it at the link on the bottom. Just flash the latest JB or ICS root66. If you use ICS, it wont trip your counter. Rooting you way will, so be sure to use triangle away from the playstore to reset your flash counter. Heres the link
http://forum.xda-developers.com/showthread.php?t=1949687
Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.