I've used the full update guide for capitivate to update my phone running on the 2.3.3 version.
I've tried to install clockworkmod recovery through Hemidall, but I cannot load the file correctly in the last step: "Use the dialogue that appears to navigate to, and select, the Heimdall firmware package that you wish to flash."
Then i've been looking around for other solutions. I've tried to boot it through the recovery mode manually installing the clockwork through the zip mode. But doing this just gives this notice: "signature nortification failed"
I've also tried to downloaded rom manger from market and to flash it from there. But i cannot find the capitivate in the options. Therefore I chosed to use the one for Galaxy S. But when i'm trying to install the rom later through the recovery mode in clockwork it gives me the same message "signature nortification failed"
I've been looking for information all over google and different forums, but i cannot find anything.
Please help me solving this!
Check this here... Guide by TRusselo.http://forum.xda-developers.com/showthread.php?p=19425513
Sent from my SAMSUNG-SGH-I777 using xda premium
Thanks! I´ve seen this guide before, but is it working if i want to install android 4.0 as well, when i´m running my current 2.3.3? I thought this guide was just for installing the 2.3.3.
Edit:
I tried the guide and it worked! I had to reset it as well to wipe cache though! So many hours for figuring this out. Thanks for helping me out!
^
Just read the 1st sentence in the OP of that Guide thread. Ur answer is there.
Sent from my SAMSUNG-SGH-I777 using xda premium
Related
So I was using Darky's ROM v9.3 and everything was fine for a couple of months. I had a force close on a game that always worked in past so went to reboot phone. At this time my phone simply failed to finish rebooting. The phone got past the "GALAXY" screen title and then was caught in the "Darky's ROM" title.
I still had download and recovery mode (clockworkmod) so I tried to do a recovery. The recovery file was from just after I had flashed Darky's ROM. This time when I rebooted the phone did not even make it past the "GALAXY" screen title. Furthermore, on this title screen, it initially shows that it is a "GT-i9000 M" but then the "M" drops from the model description.
I have been trying everything I can to simply get a clean copy of the rom onto my internal sd card but no matter what I do Samsung Kies wont connect to the device so that I can copy the .zip to reflash.
I have tried enabling and disabling debugging, I have tried using "download" mode, I have tried mounting system etc and all to no avail.
Pleas help! Can anyone give a detailed description of settings needed to connect to the pc successfully so i can download a rom for a reflash?
If your download mode works flash rom via odin
Sent from my GT-I9000 using XDA Premium App
themate1987 said:
If your download mode works flash rom via odin
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
i have been searching all day to find a working copy of odin. can you point me in the right direction?
Search for darkys odin rom and follow instructions....everything you need is in one zip file
Sent from my GT-I9000 using XDA Premium App
thank you very much. one other question. im up to installing the ressurection.zip from recovery. although i have copied to my internal sd card, and I can see the file on my phone through the "file browser" app. when I enter recovery mode and try to , install zip, choose zip, i cannot see it in the list. any ideas why this is?
dangermouse87 said:
thank you very much. one other question. im up to installing the ressurection.zip from recovery. although i have copied to my internal sd card, and I can see the file on my phone through the "file browser" app. when I enter recovery mode and try to , install zip, choose zip, i cannot see it in the list. any ideas why this is?
Click to expand...
Click to collapse
never mind i found it. thankyou so so much for your help. i simply couldnt find what i needed though i searched all day.
thankyou again!
I have been trying to root my phone and seem to be having problems. I have searched and found some people having the same problems but could not find an answer.
I tried using AIO Captivate Toolbox 3.0 and when it reboots in recovery and I click on reinstall packages I get this error..
signature verification failed. Installation aborted
I tried super on click and it says its rooted and there is an superuser icon on my phone but when it asks to test to see if its rooted and asks me to check my phone, nothing happens. I then install rom manager and thats installs fine and I can install Clockwork Recovery but when I get it to boot in recovery it just brings me back to the recovery 3e and I will try to reinstall packages again and it gives me this error..
e:failed to verify whole-file signature
e: signature verification failed
So I dont know what Im doing wrong. I had a Sony xperia x10 and im use to flashing and installing roms on that. This phone is much different lol
ottawadad34 said:
I have been trying to root my phone and seem to be having problems. I have searched and found some people having the same problems but could not find an answer.
I tried using AIO Captivate Toolbox 3.0 and when it reboots in recovery and I click on reinstall packages I get this error..
signature verification failed. Installation aborted
I tried super on click and it says its rooted and there is an superuser icon on my phone but when it asks to test to see if its rooted and asks me to check my phone, nothing happens. I then install rom manager and thats installs fine and I can install Clockwork Recovery but when I get it to boot in recovery it just brings me back to the recovery 3e and I will try to reinstall packages again and it gives me this error..
e:failed to verify whole-file signature
e: signature verification failed
So I dont know what Im doing wrong. I had a Sony xperia x10 and im use to flashing and installing roms on that. This phone is much different lol
Click to expand...
Click to collapse
I had the same issue and I found this solution. Worked like a charm:
http://forum.xda-developers.com/showthread.php?t=833423
Download the 3e_recovery_installer.zip file only and unzip.
Put your unit in Debugging mode and connect to the USB cable on your PC
Run the Install.bat file from DOS prompt and wait.
A temporary root will be performed (Doesn't matter if you're rooted or not, I was already rooted and had no issues)
Once completed, reboot into CWR. You will probably get the standard recovery screen. Select Reinstall Package and let it go. Select Reboot. (If the machine boots to the OS, go back to Rom Manager and reboot to CWR again to test.)
If the E3 Recovery screen comes up again, select Reinstall Package again. (Yes, you have to do it twice!)
As soon as it's done the CWR screen will pop up. From here on out, it should work as normal when selected from the Rom Manager app.
Hope that helps,
Now if someone would just post the Captivate AT&T default Notification sounds for me, I'd be a happy camper! I miss my old sounds!
-maj
Are you running stock froyo? There is a fix for sign verification error in vibrant forums. Search it. I am on xda app or would have given you the link
Sent from my SGH-I897 using XDA Premium App
viny2cool said:
Are you running stock froyo? There is a fix for sign verification error in vibrant forums. Search it. I am on xda app or would have given you the link
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Umm I believe the link I posted above is to that exact thread you are referring to. I am running the captivate with the Stock (upgraded) 2.2 rom and this worked perfectly for me. Just follow the instructions.
-maj
Thanks. I will try that and let u know how it goes and yes im running stock 2.2
Sent from my SAMSUNG-SGH-I896 using XDA Premium App
Thanks for all the help. It worked and now my phone reboots in the proper recovery.
ottawadad34 said:
Thanks for all the help. It worked and now my phone reboots in the proper recovery.
Click to expand...
Click to collapse
Glad I could help.
-maj
It won't work for me, I'm on stock 2.2 (already rooted) and when Itry it I get:
"The system cannot find the patch specified"
"Temp root failed! install cannot continue"
Any idea how to make it work??
EDIT: My bad.. Wasn't doing it correctly lol - I wouldn't suggest this to a newb tho ^^
I got my phone back just 3 days ago and figured i'd finally customize it. I FINALLY figured out a safe and full-proof way of rooting my samsung galaxy s i9000M. I FINALLY figured out that I need to switch the <3e> recovery to <2e> recovery so that I'm able to flash custom ROMs.
Here's the annoying part...
I STILL can't set up Clockworkmod recovery instead of the stock recovery menu. The tutorial I'm following specifies that I need this recovery in order to get everything workin.
I have the phone rooted and I have ROM manager installed too.
Won't someone tell me how to install it on my phone?
I've tried this website:
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
didn't work many times
thanks in advance!
stacyluo said:
Hi, I'm new to this forum.
Click to expand...
Click to collapse
gotta start somewhere
I should point out, it keeps saying "can't open /sdcard/update.zip"
(no such file or directory) if that helps
You mean you don't have recovery yet or you can't install any zip files?
Sent from my GT-I9000 using XDA Premium App
You'll probably need to do it via Odin.
If you look at the guides here on XDA you'll see easily how to do this.
There are probably easier ways to do by now, but you can follow the more traditional method without much difficulty and not really with that many screw up chances.
Just grab a custom Kernel, like SpeedMod or so, for Odin installation.
Follow the steps that you'll see on the Odin guide to install just the Kernel. Once that is done the Recovery mode will be altered and you can start using CWM normally from there on (or until you install some other full ROM that replaces the kernel and recovers the official recovery mode).
Hi, first post here so if I screwup any of the etiquette please tell me.
Ok, so I've had my P1000 for about two years now, no contract, not locked to sprint / verizon etc.
I had 2.3.3 at the start, but after seeing mannnny people flashing to ICS successfully I had to give it a go.
Attempted to flash using overcome kernel for CWM, failed and I had to odin back to 2.3.6 (couldn't find a 2.3.3 rom).
I kept it on 2.3.6, but I was unhappy and so am trying again:
It's important to know that I am now on a mac, so will not had access to odin, and instead am forced to use heimdall. Please don't post any odin specific instructions.
In order to get CWM I had to flash the overcome kernel, which includes the recovery mod.
I successfully used heimdall for this, following a specific instruction guide.
I then downloaded "cm-9-20120703-NIGHTLY-p1.zip" from get.cm, and copied it to my externalSD on my gt.
Booted into recovery, wiped all data/factory reset, wiped cache, wiped dalvik, and went to install form an externalSD.
I chose my file, and the installation / flashing (not sure as to the terms. ) began.
It went through a few messages, but however once it said "Checking state of BML/MTD" it reboots instantly and shows the cm startup for about five seconds before going into recovery. Always does this on startup, no way to change.
The only way to fix this is to go into recovery and wipe all data, but this leaves me on my 2.3.6 rom.
I have NO idea what's happening, and I can't use most guides due to them being odin specific.
If anyone can assist me, please do.
Don't link to any odin threads, and don't tell me to search, for I have been doing so for eight hours.
Cheers,
Zero
EDIT: SOLVED!!!
After flashing once it failed at BML/MTD, so I opened recovery and flashed from "internal sd". Worked a charm, now installing gApps.
Cheers for helping Priyana!
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
priyana said:
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
Click to expand...
Click to collapse
That's the thing - when I boot to recovery after flashing (and failing) CM9, it is a different sort of recovery and doesn't allow me to install from an externalSD.
Cheers for replying,
Zero
just the name change.
the internal and external got swapped around in that newer recovery
priyana said:
just the name change.
the internal and external got swapped around in that newer recovery
Click to expand...
Click to collapse
As I just noticed.
Installed PERFECTLY!
It's up and running - however I can't see a market?
Cheers,
Zero
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
priyana said:
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I gave up on instructions after five hours of them failing.
Reread now and just about to reflash with gapps
Cheers,
Zero
Yeah. Believe it or not, early adopter has advantages because we have read up all!
Sent from my GT-P1000 using xda app-developers app
Yeah
Works so well, already have tapatalk and all gapps are working perfectly.
And the instructions - I was following them perfectly, but they did not go in depth when it came to reflashing with the newly installed rom-manager of cm9.
All works perfectly now, thanks for your help
Sent from my GT-P1000 using Tapatalk 2
I've got this exact issue coming over from Frankenclean 2.8 on the samsung fascinate. I decided to update my rom as it was falling behind the 'curve' if you will.
I'm now stuck at a bootloop "samsung" and "S-cyanogen(mod)" screen. they just go back and forth. I'm following this http://forum.xda-developers.com/showthread.php?t=1238070 to the letter and still getting the issue. I've tried flashing a newer kernel that is for 4.x.x builds and no luck.
When I install or attempt to install cyanogen10 it fails on the bml/mtd check and it just reboots to those two screens.
I followed the 'fix' at section 9 but haven't had any luck getting cyanogen to install... I'd really appreciate a little help, ideas, questions, anything.
I know it's an older device, I'm just hoping someone out there with more dev knowledge than I possess "read: none" can help me out.
bump...
Got it to boot into a stock rom, but have 0 luck getting my nandroid to load up and be functional using CWM 2.4 (red). Which is what I made the recovery with.
Might end up with a stock phone if I can't figure it out, I don't mess with roms often.
Luckily I do have titainium backup so all my apps are saved. Just sucks to not have a sleek rom anymore. Not to mention I want jellybean. Any help is appreciated!
fixed it, 4.1 didn't like my phone, got hellybean 4.2 on it without a problem .
Only issue is that google voice to text doesn't work, nor google search.
EDIT: Problem solved!
Hi all,
I just tried to install CWM Recovery on a Samsung Galaxy GT-I9000, and it didn't work.
The phone was (originally) running under Android Froyo (2.2), and unrooted. First of all, I used UnlockRoot to root it, and it worked fine. I checked the root access right after using dedicated apps (rootChecker, sdMaid, etc), to confirm.
Then I wanted to install a ClockWorkMod recovery. I followed this guide (on the CyanogenMod wiki). I downloaded and installed Kies to have the USB drivers installed. Then I downloaded Heimdall (my computer is running under Windows 7) + hardcore CMW Kernel. I booted into download mode, then installed the driver. (Step 2 on the tutorial). Then next step was flashing the kernel. It suceeded, and the phone powered off. Turning it on, it just starts to make endless boot loops. The system won't start running, and it is not possible to access to the CWM recovery menu. But the download mode is still available.
So, does anyone have pointers to help me fix this issue ? i would like to have CMW installed, and then install a custom ROM (the latest Jelly Bean based Cyanogenmod release).
Thanks in advance.
Just try again installing stock Rom with odin
See my post Here
http://forum.xda-developers.com/showthread.php?t=1994759
Hi Donovan,
Thanks for the swift answer. And yes, it definitely worked. I downloaded this stock rom, and I flashed it successfully with Odin v3 1.85. I am running now under Android 2.3.6, but I lost the root access. Rooting it won't be a problem, hopefully. I still have access to the download mode, and to the stock recovery. I'll try once again to dive into the ClockWorkMod Recovery, and then install a Jelly Bean rom.
I'm hitting the thanks button right after posting this.
Thanks back at ya. Cf root you can find here
http://forum.xda-developers.com/showthread.php?t=788108
Dont forget the wiping before flashing jb.
Most times u have 2 flash custom twice.
If first time hangs just pull battery out, get in recovery & flash second time or third if its needed.
If it says install completed then its done
Much pleasure flashing the i9000
Actually, I spoke to fast, the problem just got much worse.
Okay, just after flashing the stock rom (2.3.6), everything was fine. Then I downloaded the latest stable CM10 (direct link).
I booted into recovery mode (CWM Recovery,actually) and I did try to install (i din't not forget wiping data/cache, dalvik and batt stats), but it failed, saying the package was incorrect. I tried many times, copying again and again the zip file, same problem.
Then I downloaded a previous version, CM9. I tried to installed it, and i run into a very weird error, saying an assertion failed when trying to install the package.
Something like;
assert failed: getprop("ro.product.device") == "galaxys" || getprop ("ro.build.product") == "galaxys" ... getprop ("ro.build.device") = GT-I9000 etc...
Click to expand...
Click to collapse
And then installation program aborts (error code 7.)
My assumption, is that it looks like my phone is no longer being considered by a samsung gt i9000, according to the installer. Weird, though...
Now, I still have access to the recovery. But the phone can't boot, as everything was wiped. Much worse, I can switch to download mode, but i can't flash back the stock rom, Odin can't detect the phone (I tried with Odin v3 1.82, 1.83 and 1.87).
I'm getting desperate, any pointers ?
Thanks in advance!
Did u try to flash the custom more then 1 time?
Oh yes, I did it like a dozen of times.And I still get the same error.
Sent from my HTC Wildfire S A510e using xda app-developers app
gti9000 rooting
Hi Donovan, could you help me please:fingers-crossed:
I've purchased a unlocked galaxy s gti9000 and I want to root it. Something I've never done on any phone as I'm a complete noob. I managed to install XWJW1 FIRMWARE. I've now got as follows PDA:I9000XWJW6
PHONE: I9000XWJW1
CSC: I9000XSAJV8.
All the links to the file for rooting seem to be dead. I've found some for rooting XXJVU, But that's not right is it? I would really like to try ICS or Jelly Bean. I must admit I'm nervous about this as it's taken me a while to get a phone as good as this one!! Any help would be greatly appreciated. Thanks in advance
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Thanks
Roland_Y said:
@Nooga:There is a very complete and straightforward guide here (http://forum.xda-developers.com/showthread.php?t=1852546). You might want to take a look at it.
Now can we please come back on my topic ? Thanks!
Sent from my HTC Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Thanks Roland will give it a try tonight.
Well, that is now solved. I tried something silly that ended up working fine.
As the cm9-smtd update package couldn't run (because of the assertion fail), I just opened the zip package, then edited the file META-INF/com/android/google/updater-script.
I basically removed the assert statement at the top of the file.
CMW recovery installed it properly, without any err. I now have an ICS based rom (Cyanogen Mod 9).
Problem definitely solved now. Going to make a Nandroid backup.
Thanks all, again.