EDIT: New problem I am using this root method:http://forum.xda-developers.com/showthread.php?t=1046855 However, no matter how many times I attempt to perform step 9, it keeps giving me the exclamation point. Any ideas?
The only way I could get root was to use super one click. Version 1.7 worked for me on two fascinates.
Sent from my SCH-I500 using XDA App
Were those two running 2.2.1? ED01?
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--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.
Looks like I wont figure it out today (too tired to think straight)
spartan.062 said:
Well, the problem that I'm having is that when I attempt to apply the "update.zip" file, I get a progress bar for a fraction of a second and then the exclamation point with the droid guy next to it.
I get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification failed
Installation aborted.
EDIT: Just realized the "update.zip" file was missing. But now I get this:
--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.
Looks like I wont figure it out today (too tired to think straight)
Click to expand...
Click to collapse
Sometimes I download multiple files at one time. For instance, to get the ED01 modem I downloaded the 2 update.zip's from adrynalyne's thread. The second update.zip had a "(2)" at the end of it. Erase that. On your PC the files needs to only say "update", not "update.zip". The phone adds a ".zip" to each file. Make sure you are doing that.
Sent from a depraved XDA junkie and flashaholic
superchunkwii said:
I am pretty sure that with the latest kernals from stock you won't be able to get a root to stick.
No matter what after running any root method, you'd have reboot back to recovery and flash some kind of kernal in order for it to stick.
If you plan on putting a rom on your phone, just follow my stickied guide in this forum and flash that rom in place of the kangbang community rom I linked to... or just flash your kernal of choice to keep the stock experience with root.
Click to expand...
Click to collapse
This isn't true. You are thinking about installing CWM recovery, that gets overwritten with the stock recovery by the stock kernels. I've used this method on many of the stock builds including ED01: http://forum.androidcentral.com/ver...d-post-1-before-posting-forum.html#post699944
I know of a VERY simple root method. If you want to know it, hit me back. It seems to me that no one is using it but it is posted in these forums.
Sent from a depraved XDA junkie and flashaholic
What method is that kidserious?
spartan.062 said:
Ok... Every time that I attempt the adb root, I get this in the command prompt:
'adb' is not recognized as an internal or external command, operable program or batch file
Click to expand...
Click to collapse
Are you on stock 2.2?
spartan.062 said:
What method is that kidserious?
Click to expand...
Click to collapse
Click on this and then once you are there download linked file. Then place it on your SD card. Let me know when you have done that.
http://forum.xda-developers.com/showthread.php?t=1045048
Yep. And I am still somewhat confused when it comes to flashing a kernel. And I already have the su file, however, when I try to apply the update to get to CWM, It won't take the update. I'll try adding .zip to the end of the name.
spartan.062 said:
Yep. And what was that method you were mentioning?
Click to expand...
Click to collapse
Yes, but I see you have had problems with this method already. Are you able to get odin properly set up on your PC? I mean have you been able to flash anything via odin? Did you see my link in my above post? And don't worry about a kernel just yet. Lets get this taken care of first.
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
spartan.062 said:
Yeah, it said that it was successful. But the update.zip WILL NOT apply no matter what I do.
Click to expand...
Click to collapse
Did you see a Green "Pass" when it finished in odin? And when you put the battery back in were you unplugged first? You may know this but you cannot allow the phone to boot normally before booting into recovery. Try using this recovery instead: http://dl.dropbox.com/u/36791/CWM3_Voodoo.tar.md5
Flash that the same way in Odin?
spartan.062 said:
Flash that the same way in Odin?
Click to expand...
Click to collapse
Yes, but boot into recovery FIRST before the phone turns on normally. Not trying to sound condescending but do you understand what I am saying about booting into recovery first?
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
spartan.062 said:
Yeah I understand.
Click to expand...
Click to collapse
The way it always works for me is I don't even boot into the blue recovery, it boots straight into red. Let me know what happens.
spartan.062 said:
Yeah I understand. Ok I got the voodoo lady's voice. Now I have the red CWM menu.
Click to expand...
Click to collapse
GOOD! With that menu find the superuser root package from nemesis2all on your SD card and install it. Let me know what happens.
Related
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
im guessing no ones had this problem before?
Re: E: cant symlink
I had this problem on clock work recovery and wasn't able to fix it had to get a me new phone
-------------------------------------
Sent via the XDA Tapatalk App
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
bigslanki said:
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or did you just accept it as a loss?
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
ok thanks i think im going to just sell the phone instead of trying to fix it, my MOTO Droid will be here tommorow :.
did verizon attempt to fix or
Click to expand...
Click to collapse
well I tried flashing the root rom see if that would work, when I did the system and boot.img failed to get flashed so when it tried to reboot it never turned back on at all.
I called them told them it wouldn't turn on and they sent me a new one.
Click to expand...
Click to collapse
Yep that's way happened with my first Eris. ... I'm on BACK TO Droid now as you can see. Going to limit my flashing for now on.
-------------------------------------
Sent via the XDA Tapatalk App
bigslanki said:
okay i had Rom Manager installed on my HTC Eris because i liked how easy it was to use on my DROID. My first BRICK came while in Clockwork recovery for eris. I had an error saying something like E: boot.img failure or something to do with the boot image. i proceeded to fastbot and attempt to update with original PB000IMG.zip. system failed to write as well as boot. After powering down the phone(i received a brick) no recovery no power indicator
my second came also while using clockwork recovery.im not accusing clockwork recovery of bricking my phone ( im lying DO NOT USE CLOCKWORK RECOVERY) but i am letting you know i lost two phones using it.
this time this is the result after flashing.
--installing: sdcard:update 2.1.zip
finding update package...
opening update package...installing update..
Delete files..
delete files..
formatting system..
copying files...
E: cant symlink /system/bin/cat
E:Failure at line 11:
symlink toolbox SYSTEM:bin/cat
installation aborted
so if anyone has any brick experiences please add to this post your experience along with detail of your process to get there
Click to expand...
Click to collapse
You over reacted
jetmclean said:
You over reacted
Click to expand...
Click to collapse
You bumped an old thread
jetmclean said:
You over reacted
Click to expand...
Click to collapse
how so? stating my experience and providing details for other users?
Old news......
Keep in mind that I'm brand new at this so please don't just say "do this ____" and expect me to know what you're talking about .
I finally was able to root my new fascinate and flashed CWM. The ROM installation guide says if you're already rooted with CWM installed to simply reboot into recovery, wipe everything and flash. Only problem is, when I boot into recovery I am getting this error message.
-- Install from package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Can anyone tell me step by step what I need to do to solve this? Also I was assuming the camera button would work as the 'OK' or 'enter' button but it does nothing. Is one of the soft buttons used along with the volume rocker to select choices in recovery? I have some experience hacking my og Droid but this fascinate stuff is all greek to me.
With the help of google I think I figured out what was wrong, needed to flash something from odin to get it to work beforehand.
http://www.mydroidworld.com/forums/fascinate/4786-how-flash-clockwork-recovery-fascinate.html
Rebooting now, will let you all know if it worked.
I have definitely messed something up.. after flashing CWMRecovery.tar (used PDA, not phone) my phone just stays in a bootloop now. I can get into stock recovery but reboot now and the apply option do nothing but throw out error messages. I'm pretty sure it's hosed so I'm going through the steps to flash it through odin back to stock. Can anyone explain to me what exactly I did wrong here?
It may help if you give details... what rom did you flash? What kernel? This could help us help you.
Sent from my SCH-I500 using XDA App
Shakes The AssClown said:
It may help if you give details... what rom did you flash? What kernel? This could help us help you.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I second this, from previous personal experiences with this it sounds like something has gone wrong with your odin/flashing or you may be using old/outdated/corrupt files.. if you could tell us what you are odin-ing/flashing and exactly how you're doing it we can give you specific answers
tapatalked from my KangBanged Fascinate
Ok peeps, completed S-off successfully and have Revolutionary CWM v4.0.1.4 as my recovery. Almost there and when I went to install su-2.3.6.3-efgh-signed.zip for ROOT, I received the following:
Installing: /sdcard/su-.3.6.2-efgh-signed.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/su-2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
Can anyone shed some light to my current situation? Thank you in advance.
I had the same thing happen the first time that I tried. I just retried and it we through the second time. If it doesn't work when you retry, try deleting it from your sd card, then redownloading it, and try it all over. you might have gotten an incomplete file
You have a good one you could send me in case that is the problem?
Sent from my PG86100 using XDA App
youre alright bro, just flash this one and you'll be all set...http://dl.dropbox.com/u/36719158/su-2.3.6.3-efgh-signed.zip
Odds are you had one that wasnt properly signed, youre 98% done!
So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Chubby_Skunk said:
So I rooted my phone (2.3.4) and put the MiUi on my SD storage. I have CWM installed and when I go to install the ROM this pops up:
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installing aborted.
So this happens when I try to install the file from the CWM app while on the phone, but it also does this when I just try to boot into CWM.
Any help???
Click to expand...
Click to collapse
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it. You'll find the option under the install from sdcard option then just toggle off your signature verifications.
Gutterball said:
What kernel are you running? Your not using the cwm from rom manager right? Using one from a kernel? You could try and shut off your signature verification setting in cwm that should let you flash it.
Click to expand...
Click to collapse
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Chubby_Skunk said:
Yeah im using Clock Work Mod... :/
Where is the one that i'm suppose to use? I just want MiUi :/
Click to expand...
Click to collapse
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Gutterball said:
Like I said you could actually probably flash it with that but you just gotta shut off your signature verification option. Though people have said its not advisable. If you wanna do it the right way? Flash a kernel from development it has the correct cwm built into it.
Click to expand...
Click to collapse
I'm still confused. So all I have to is flash a kernel and then it'll work???
Chubby_Skunk said:
I'm still confused. So all I have to is flash a kernel and then it'll work???
Click to expand...
Click to collapse
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Chubby_Skunk said:
Wow....................... I tried to install the Kernel in CWM like the dev said, and I get the same error message.... this is getting really annoying. The Atrix was less painful than this is being :/
Click to expand...
Click to collapse
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Gutterball said:
Its just a little different then the atrix was but definetly better! Just gotta get used to some new stuff a little bit. I love this phone! Did you try toggling off the signature verification option??
Click to expand...
Click to collapse
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Chubby_Skunk said:
uh, no. how do i do that? I just used Odin3 to flash the .tar file for that kernel.
Click to expand...
Click to collapse
Odins fine didnt realize you knew how to flash it that way. That'll work!
Gutterball said:
Odins fine didnt realize you knew how to flash it that way. That'll work!
Click to expand...
Click to collapse
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Gutterball said:
The correct kernel you need to flash is the siyaah kernel when you do this it will automatically install the correct cwm then you should be able to flash miui no problem.
Click to expand...
Click to collapse
SiyahKernel's included CWM has had a lot of problems lately.
The reference CWM kernel to use is codeworkx's CWM kernel - there is a thread on it in Development.
Chubby_Skunk said:
Just tried it and i didn't change. it was still the same -_-
This is frustrating. The Captivate was 1000000000000000000000x easier to root and flash.
Click to expand...
Click to collapse
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Gutterball said:
When you flashed it in odin? you flash it as a pda in download mode right? If you did then you should have the right cwm now and miui should install through cwm.
Click to expand...
Click to collapse
well ill try it again.....
Chubby_Skunk said:
well ill try it again.....
Click to expand...
Click to collapse
If that doesn't work then use entropys kernel found here http://forum.xda-developers.com/showthread.php?t=1289460. It kicks ass but you cant use it with miui or cm7. but this will give you the proper cwm then install miui.
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Chubby_Skunk said:
This is just f***ing ridiculous. So I tried it and when it works, when the phone boots up it shows:
Samsung Galaxy S II
GT-I9100
under than it shows an yellow triangle with a explanation point inside it. The phone boots up and CMW is nowhere to be seen.....
Click to expand...
Click to collapse
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax. That exclamation thing is nothing dont worry about it. Its perfectly normal!
Gutterball said:
Heres the cwm link that entropy said to use http://forum.xda-developers.com/showthread.php?t=1285823 You gotta calm down and do a little research lol relax
Click to expand...
Click to collapse
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Chubby_Skunk said:
Thats the one i did and when the phone is back up and running, there is no Rom Manager anywhere on my phone. -_-
Click to expand...
Click to collapse
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Gutterball said:
It doesnt need rom manager. You boot into cwm by holding your power button and volume up and down when the phone boots up. Thats your cwm.
Click to expand...
Click to collapse
tried that too and nothing happened :/
it just waits a second and then goes to the AT&T splash screen and goes to the lock screen....
ATT Samsung I777
History: Updated phone to ICS 4.03 using update from Samsung. Rooted phone using Odin 3V185 to Siyah-v3.4.2-nomswap-I777. Phone has been working fine other than I cannot install apps that my carrier doesn't approve.
Update: So I decided I was going to install Semi_V16c. Downloaded it to my computer then transferred to my SD card. Then I opened ROM manager that was already installed on my phone from what I did a few days ago. Once open I selected backup ROM and it asked for the file name to save backup as. Then my phone rebooted automatically and never came up again. If I remove my battery and hit the power button It will show the Samsung Galaxy SII screev and says GT-I1900 under it and the yield sign. Then when that screen goes away the screen is just black. Not sure how backing up ttriggered this but any help is appreciated. I couldn't find a recovery tutorial in the Q&A sticky.
Forgot to mention that the ICS update I put on was done with Kies
I'm going to say that it was ROM manager that did it. ROM manager does very very bad things.
keeperofthecode said:
Forgot to mention that the ICS update I put on was done with Kies
Click to expand...
Click to collapse
First problem, you used ROM MANAGER, big NO NO.
So you can't boot into recovery using VOL - + POWER , during boot?
Don't. Use. Rom Manager.
The End
Sent from Team Pirate running AOKP
jthatch12 said:
First problem, you used ROM MANAGER, big NO NO.
So you can't boot into recovery using VOL - + POWER , during boot?
Click to expand...
Click to collapse
I can get it into download mode if that is the same. I held the V+ & V- and plugged in USB cable and it goes to downloading... page.
I swaer to god this Is the 10 the ROM manager fail post in like 2 days
Sent from my SGH-I777
keeperofthecode said:
I can get it into download mode if that is the same. I held the V+ & V- and plugged in USB cable and it goes to downloading... page.
Click to expand...
Click to collapse
If you can get into download mode then your okay. Look for a guide on how to use ODIN.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1820112
122ninjas said:
I swaer to god this Is the 10 the ROM manager fail post in like 2 days
Sent from my SGH-I777
Click to expand...
Click to collapse
Sorry guys. I didn't know running a backup from ROm Manager could cause this. I was just going to run backup then follow instructions to install new one from the sticky.
jthatch12 said:
If you can get into download mode then your okay. Look for a guide on how to use ODIN.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1820112
Click to expand...
Click to collapse
So I ran Odin and went back with the same one (Siyah-v3.4.2-nomswap-I777.tar) I used a few days ago and phone still does the same thing.
Using the top directions you gave me I downloaded the file and when I run it (I777UCKH7 OCD With Root) the top left doesn't come up yellow like the directions state so I stopped there.
keeperofthecode said:
Using the top directions you gave me I downloaded the file and when I run it (I777UCKH7 OCD With Root) the top left doesn't come up yellow like the directions state so I stopped there.
Click to expand...
Click to collapse
Try to install samsung kies to get the drivers you need.
122ninjas said:
Try to install samsung kies to get the drivers you need.
Click to expand...
Click to collapse
I got it to go by not putting the phone in download mode until after odin was already running. Other version of odin I used prior didn't require that. It ran and said pass then when phone rebooted it went to this message in recovery screen.
Andriod system recovery <3e>
--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
installation aborted
keeperofthecode said:
I got it to go by not putting the phone in download mode until after odin was already running. Other version of odin I used prior didn't require that. It ran and said pass then when phone rebooted it went to this message in recovery screen.
Andriod system recovery <3e>
--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
installation aborted
Click to expand...
Click to collapse
Went ahead and rebooted phone and it came up. Kernel 2.6.35.7 baseband I777UCKH7 ANDROID 2.3.4.
Can I go ahead with installing Semi 16 using normal instructions. Thanks for all your help.
Doing ANYTHING from rom manager on this phone will have terrible repercussions. Please please do your research and do everything manually in cwm. It isn't that hard.
Sent from Team Pirate!
Nick281051 said:
Doing ANYTHING from rom manager on this phone will have terrible repercussions. Please please do your research and do everything manually in cwm. It isn't that hard.
Sent from Team Pirate!
Click to expand...
Click to collapse
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?
keeperofthecode said:
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?
Click to expand...
Click to collapse
Depends on what exactly you flashed
Sent from Team Pirate!
Do a factory reset if u aren't on the stock ics kernel anymore. Then boot it up and install super user. If you can gain root access you're rooted. Another easy way to check is if you look at the rom u downloaded the name should say whether root was included or not.
Edit: u won't even be able to get into cwm if you have stock kernel installed. Which kernel is installed right now?
Sent from my SGH-I777 using Tapatalk 2
keeperofthecode said:
I'm just confused where to start now. My phone appears to be like it was from AT&T but some of the apps I installed are still on there. The version is not ICS anymore so am I still rooted? Do I start at step 4 in the directions for installing the new rom or do I go back to step two which is rooting?
Click to expand...
Click to collapse
Check your kernel to see if you are still rooted.
122ninjas said:
Check your kernel to see if you are still rooted.
Click to expand...
Click to collapse
Please make sure you know what you are saying before you post.
@OP,
The easiest way to see if you are still rooted is to look in the app drawer. If superuser.apk is still there, then most likely you are still rooted.
If you flashed the stock one-click downloader from the return to the store thread, then you are not rooted, so root first, then install a Gingerbread custom kernel, and then the firmware of your choice. From re-reading your posts, it looks like you flashed the stock plus root one-click downloader, so you should be rooted. In that case, you need to install a Gingerbread custom kernel, and then the firmware of your choice.