I'm preparing to flash a custom rom to my girlfriend's I9000, but if anything goes wrong I want to be able to just reflash a nandroid backup and not need to change any settings or reconfiguring anything. I need some advice about how to make a nandroid backup in the least invasive way possible, i.e., preventing tinkering to the current (stock) rom. The problem--I think I need to use a custom recovery to make a nandroid backup. How do I do that with the least tinkering to the current ROM? Premise, I'm using Linux and I do not have access to a windows machine. I have the android sdk installed (fastboot, adb) and I'm comfortable using the commandline. I don't know much about android, but I _do_ like to know what I'm doing She currently is using stock, unrooted I9000XWJW5_I9000XENJV6_XEN.
I considered (and tried some of) the following options.
1. Boot a CWM recovery image with fastboot, without flashing CWM to the device. Unfortunately, I don't seem to be able to boot to fastboot with the I9000.
2. Boot to existing recovery and flash CWM recovery image in the form of an update.zip file. Unfortunately, recovery complains about some signature problem with the update.zip and refuses to install it. I think it is 3e recovery--too new?
3. Use adb shell to upload an exploit, then remount /system rw, install su, reboot, install superuser.apk, install CWM manager, flash CWM recovery. Just like all the oneclickroot scripts. Unfortunately, _none_ of the exploits I found gave me root?! I tried zergRush ("Hellions with BLUE flames !"), psneuter, GingerBreak (let it run for over 15 minutes, no result) and motofail. Is there any exploit known to work on this stock rom?
4. Flash a new kernel with heimdall that includes a recovery (e.g., cf-root 4.4 or semaphore kernel). I'm not looking forward to doing this because cf-root and semaphore are not just kernels but all kinds of other stuff as well that I don't necessarily want to be there when I make a nandroid backup. In other words, these options, to me, seem quite invasive, and I wouldn't know very well what I was doing anymore.
5. Unpack the correct fs-image from a stock rom, add su and superuser.apk, repack it, flash with heimdall. Install CWM via CWM manager. I did not find information about how to do this or whether it even works.
The best would be that it actually _is_ possible to boot to fastboot on I9000. Let me know if it is, but I couldn't find any information about this. Also, I really hope that someone can advise a different exploit for option 3. Some pointers for option 5 would help as well. If nothing else works I'll flash cf-root or semaphore. A prerooted stock kernel image with only su and superuser.apk would be preferable, but that I haven't found that either. Anyway, I hope someone can lend me a suggestion or give me a pointer!
find ur own cf root, its da easiest way to attain 2e recovery, 3e recovery activate signature check,no need for adb, juz find ur own cf root.
or juz switch rom to stock jvu latest.
so many way to attain solution available if u can reach download mode, so why messing with adb? u wanna lose ur internal sd partition?
Sent from my GT-I9000 using xda premium
compacity said:
find ur own cf root, its da easiest way to attain 2e recovery, 3e recovery activate signature check,no need for adb, juz find ur own cf root.
Click to expand...
Click to collapse
Okay, that rules out flashing CWM from stock recovery
or juz switch rom to stock jvu latest.
so many way to attain solution available if u can reach download mode, so why messing with adb? u wanna lose ur internal sd partition?
Click to expand...
Click to collapse
As I said, I want the least invasive method, and I want to understand what I'm doing. Installing a kernel image with an initrd that I know little about, that I do not understand very well. Logging in via adb, running an exploit and doing some basic Linux commandline stuff, that I _do_ understand. So to me, adb is less messy than flashing some modified kernel (although I might end up doing that). Regarding the sd partition--is there any real risk losing one by using adb? Anyway, I'll use dd to back up the sd partition.
PJBrs said:
Okay, that rules out flashing CWM from stock recovery
As I said, I want the least invasive method, and I want to understand what I'm doing. Installing a kernel image with an initrd that I know little about, that I do not understand very well. Logging in via adb, running an exploit and doing some basic Linux commandline stuff, that I _do_ understand. So to me, adb is less messy than flashing some modified kernel (although I might end up doing that). Regarding the sd partition--is there any real risk losing one by using adb? Anyway, I'll use dd to back up the sd partition.
Click to expand...
Click to collapse
there s always risk when u altering somethin, juz be sure to know what ur doing.
Sent from my GT-I9000 using xda premium
I ended up flashing the semaphore kernel and making a nandroid backup from the included cwm. First though, I did find various more exploits, but none of them worked. Apparently JW5 stock rom is quite invulnerable. I also found out that it should be possible to modify the factoryfs.rfs directly, but you need the rfs kernel model, which is not part of the mainline kernels. There are Samsung patches for rfs floating around, but they don't compile on recent kernels. In fact, the easiest way to modify a stock factoryfs.rfs image would be to loop-mount it on another rooted Samsung device. So, that was too much a hassle.
Anyway, girlfirend now is using CM10 and is an awful lot faster than stock JW5 Should have done that ages ago!
PJBrs said:
I ended up flashing the semaphore kernel and making a nandroid backup from the included cwm. First though, I did find various more exploits, but none of them worked. Apparently JW5 stock rom is quite invulnerable. I also found out that it should be possible to modify the factoryfs.rfs directly, but you need the rfs kernel model, which is not part of the mainline kernels. There are Samsung patches for rfs floating around, but they don't compile on recent kernels. In fact, the easiest way to modify a stock factoryfs.rfs image would be to loop-mount it on another rooted Samsung device. So, that was too much a hassle.
Anyway, girlfirend now is using CM10 and is an awful lot faster than stock JW5 Should have done that ages ago!
Click to expand...
Click to collapse
so....when will ur girlfriend gonna treat u for ur success?
Sent from my GT-I9000 using xda premium
compacity said:
so....when will ur girlfriend gonna treat u for ur success?
Click to expand...
Click to collapse
That's rude, not appreciated.
PJBrs said:
That's rude, not appreciated.
Click to expand...
Click to collapse
juz joking thou
Sent from my GT-I9000 using xda app-developers app
Related
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, I am a new user on the xda forums (although I have read countless threads). I am a little confused as to what I should do with my captivate. I am debating between flashing 2.3 (to which I see only one drawback: there are not many stable roms out there and flashing them can be a struggle as my recovery image is not very functional in 2.3), or sticking to 2.2 and finding a nice rom that I enjoy (only drawback: it's 2.2 and not 2.3! ) So can anyone advise what to do? Thanks in advance!
My opinion: If you're new to flashing, flash a 2.2 rom. There's less chance of things going truly wrong (less true brick chances). Then, once you feel comfortable flashing (and know a little more), make the jump to 2.3.
I'd say go with 2.2, unless you are feeling brave. CM7 and MIUI (both 2.3) have pretty short battery life. Some people talk about having good battery life, but I think those people are in the minority.
thanks for the quick responses. Well I have flashed roms before (not really new to it), it's just that I haven't done it through the clockwork mod recovery because I am not able perform functions in recovery mode when running 2.3 (which is what I am currently running). Is there a stable 2.3 recovery image for the captivate out there? (none of the options in rom manager seem to work for me...) Have others been able to successfully use rom manager on a Captivate running 2.3?? If so, could someone please provide detailed instructions on how to do so?
What are you NOT able to do in recovery mode for 2.3 that you CAN do in 2.2? I mean I have been from 2.1>2.2> 2.3.4>2.3.3>2.3.4 via clockworkmod without any issues.
What exactly are you trying/wanting to do? If you are just trying to change roms? A little more info might be helpful.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
sharma_akarsh said:
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
Click to expand...
Click to collapse
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Pirateghost said:
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Click to expand...
Click to collapse
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
sharma_akarsh said:
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
Click to expand...
Click to collapse
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Pirateghost said:
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Click to expand...
Click to collapse
Ohhhh I see.... I don't think I clarified this, but I am currently on stock 2.3 using this method mentioined by: nakedninja42
I personally always remove my external memory and sim card before using odin. It is not needed as people will post but neither is doing master clear. I do these steps just to make sure I eliminate any possible issues that can occur during flashing.
1) Download Firmware from http://www.samfirmware.com/WEBPROTECT-samsungusa.htm
2) Flash back to stock JF6 w/ odin one-click and did a master clear.
3) Flash Gingerbread KF1 using Odin (see image in post link for reference) http://forum.xda-developers.com/show...9&postcount=75
4) Flash fugu kernel http://forum.xda-developers.com/show....php?t=1010141 Look for the step two that says download odin or heimdall, select the ODIN (well the version your going to use).
5) Flash stock kernel (see post link) credit to lownox for helping me on that http://forum.xda-developers.com/show...&postcount=116
6) Settings>Applications> enable Unknown Sources (AT&T finally got something right)
7) Install busybox from market
8) ENJOY!
Click to expand...
Click to collapse
So from here, do I need to do anything additional with bootladers in order to flash other roms - how exactly do I flash roms from this point? Thanks!
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Pirateghost said:
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Click to expand...
Click to collapse
Sorry to sound extremely noobish... but I thought cwm was through rom-manager?? How do I go about flashing solely through cwm?
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Pirateghost said:
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Click to expand...
Click to collapse
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
sharma_akarsh said:
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
Click to expand...
Click to collapse
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Pirateghost said:
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Click to expand...
Click to collapse
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Nevermind I think I got it...
sharma_akarsh said:
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Click to expand...
Click to collapse
Do you just want to get CWM recovery somehow? If you already have GB BL flash a custom kernel using ODIN which has CWM. For how to flash GB try to see installation instructions from Apex
got it-thanks!
Folks,
I have one issue with one SGN which i couldn't solve, and, would like to seek help from all the good fellas out there
Basically in one liner... i can not flash any file from CWM after upgrading to ICS - as of now. It will always kind of 'hang' when I/O performs write. I/O read is OK.
What i have done so far ;
-- Reverting back to Stock Gingerbread --
a1.) PC ODIN back to Gingerbread w/ PIT. Re-root and CWM.
Gingerbread boots all good.
a2.) Reboot to CWM and perform wipe.
Gingerbread boots all good and back to "Default'.
a3.) Enable "USB Debugging" and proceed to root and installation of CWM.
Gingerbread boots all good, with verified Root and CWM.
Flashing any ZIP from CWM from either internal or external SDcard has no issue.
-- Upgrade to ICS --
b1.) Reboot to CWM, flash Abyss safe kernel, wipe and format all mounts.
b2.) Reboot again to CWM, flash custom ICS ROM, JBroid, and kernel.
ICS boots all good, with verified Root and CWM.
-- Flash a ZIP via CWM --
c1.) Reboot to CWM
c2.) Flash any ZIP from either internal or external SDcard.
It will read the ZIP successfully, but, when I/O starts to write, the operation will just "hang".
Thinking it could be a lost root access issue, i boot back to ICS to check the root access, which unfortunely has no problem.
I have also tried "Set Permissions" from CWM, but to no avail.
Lastly, I have replicated the exact same process mentioned as above to another SGN, but the latter does not pose such issue
j.wong said:
Folks,
I have one issue with one SGN which i couldn't solve, and, would like to seek help from all the good fellas out there
Basically in one liner... i can not flash any file from CWM after upgrading to ICS - as of now. It will always kind of 'hang' when I/O performs write. I/O read is OK.
What i have done so far ;
-- Reverting back to Stock Gingerbread --
a1.) PC ODIN back to Gingerbread w/ PIT. Re-root and CWM.
Gingerbread boots all good.
a2.) Reboot to CWM and perform wipe.
Gingerbread boots all good and back to "Default'.
a3.) Enable "USB Debugging" and proceed to root and installation of CWM.
Gingerbread boots all good, with verified Root and CWM.
Flashing any ZIP from CWM from either internal or external SDcard has no issue.
-- Upgrade to ICS --
b1.) Reboot to CWM, flash Abyss safe kernel, wipe and format all mounts.
b2.) Reboot again to CWM, flash custom ICS ROM, JBroid, and kernel.
ICS boots all good, with verified Root and CWM.
-- Flash a ZIP via CWM --
c1.) Reboot to CWM
c2.) Flash any ZIP from either internal or external SDcard.
It will read the ZIP successfully, but, when I/O starts to write, the operation will just "hang".
Thinking it could be a lost root access issue, i boot back to ICS to check the root access, which unfortunely has no problem.
I have also tried "Set Permissions" from CWM, but to no avail.
Lastly, I have replicated the exact same process mentioned as above to another SGN, but the latter does not pose such issue
Click to expand...
Click to collapse
Are you trying to flash cf root, because it cannot be flash in CWM recovery. I cannot flash cf root myself in recovery.
Make sure you have checked unknown sources under Settings--> Security..
When you flash a custom ICS rom don t flash jbroid after flashing the rom. Reboot Recovery and try to install applications .
Sent from my GT-N7000 using XDA Premium App
j.wong said:
Folks,
I have one issue with one SGN which i couldn't solve, and, would like to seek help from all the good fellas out there
Basically in one liner... i can not flash any file from CWM after upgrading to ICS - as of now. It will always kind of 'hang' when I/O performs write. I/O read is OK.
What i have done so far ;
-- Reverting back to Stock Gingerbread --
a1.) PC ODIN back to Gingerbread w/ PIT. Re-root and CWM.
Gingerbread boots all good.
a2.) Reboot to CWM and perform wipe.
Gingerbread boots all good and back to "Default'.
a3.) Enable "USB Debugging" and proceed to root and installation of CWM.
Gingerbread boots all good, with verified Root and CWM.
Flashing any ZIP from CWM from either internal or external SDcard has no issue.
-- Upgrade to ICS --
b1.) Reboot to CWM, flash Abyss safe kernel, wipe and format all mounts.
b2.) Reboot again to CWM, flash custom ICS ROM, JBroid, and kernel.
ICS boots all good, with verified Root and CWM.
-- Flash a ZIP via CWM --
c1.) Reboot to CWM
c2.) Flash any ZIP from either internal or external SDcard.
It will read the ZIP successfully, but, when I/O starts to write, the operation will just "hang".
Thinking it could be a lost root access issue, i boot back to ICS to check the root access, which unfortunely has no problem.
I have also tried "Set Permissions" from CWM, but to no avail.
Lastly, I have replicated the exact same process mentioned as above to another SGN, but the latter does not pose such issue
Click to expand...
Click to collapse
Please make sure you have full root before flash anything at recovery. For your cases, should be involve in partial root issue.
Please report back, and we will guide you how to gain full root again.
Please using "root explorer" copy and paste some file into system.
Sent from my GT-N7000 using xda premium
cant flash from CWM
i think your prob is mainly because of the partial root like what lee mentioned. i personally experience that before..the only solution for u is to flash the stock ICS <pls download fr dr.ketan's post> thru ODIN PC. After u flashed the stock ICS, root it and u r free to flash any ICS rom u like..cheers..
if this guide is useful..a Thank ll nt cost u a buck..:good:
Doesn't flashing a custom kernel through PC odin give you full root? In that way he can flash a custom kernel to resolve the problem.
Sent from my Android Rocket using xda Premium
Akilesh said:
Doesn't flashing a custom kernel through PC odin give you full root? In that way he can flash a custom kernel to resolve the problem.
Sent from my Android Rocket using xda Premium
Click to expand...
Click to collapse
For partial root problem, flash rooted kernel thru pc odin wont able to 100% solve the problem, but cant give it a try.
Sent from my GT-N7000 using xda premium
lee yun khong said:
For partial root problem, flash rooted kernel thru pc odin wont able to 100% solve the problem, but cant give it a try.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It'll also raise your counter.
Sent from my GT-N7000 using xda premium
But kernels with rooting ability gives us full root. I rectified a similar problem when i was running Ginger bread. Used Speed-Mod k2-12 to get full root.
Akilesh said:
But kernels with rooting ability gives us full root. I rectified a similar problem when i was running Ginger bread. Used Speed-Mod k2-12 to get full root.
Click to expand...
Click to collapse
Flash AbyssNotekernel42CWTouchOriginalLogo ( attached file ) using pc odin (pda slot ) . Its a .tar file so you can flash it using pc odin . You will get a functional clockworkmodrecovery after this step allowing you to flash any rom .
Caution it will raise your flash counter and you will get yellow triangle
To remove yellow triangle and and reset flash counter to 0 follow these steps
1. Flash AbyssNotekernel42CWTouchOriginalLogo using Odin 1.85 since the kernel is a .tar file .
2. Do full wipe and install RocketRom ICS with the ClockWorkMod Recovery( or other LPY ICS roms).
3. After successful boot , flash DAFUQ_N7000_05272012 Kernel( triangle away works on this kernel ) , which is again a .tar file , so flash it with Odin 1.85.
4. Check if the supersu app is installed , if not download from play store.
5. Install triangleaway.apk .
6. Reset the count
7. If the Samsung logo Screen is not visible then flash param.tar , with pda slot in Odin 1.85.
Hit thanks if i was any help to you
It might be worth running emmc check from play store also, make sure you haven't damaged a section of the chip
Sent from my GT-N7000 using xda premium
Folks... thanks for all your valuable inputs!
I have retry what i have mentioned, but this time round, i did a change of the ROM and Kernel to Criskelo and SpeedMod, and somehow the issue dissapeared
Still pretty much unsure what's the root cause, but, i believed like what you guys have mentioned - partial root
j.wong said:
Folks... thanks for all your valuable inputs!
I have retry what i have mentioned, but this time round, i did a change of the ROM and Kernel to Criskelo and SpeedMod, and somehow the issue dissapeared
Still pretty much unsure what's the root cause, but, i believed like what you guys have mentioned - partial root
Click to expand...
Click to collapse
Download busybox from playstore to get full root.. Just update binaries and stick to the instructions.
Sent from my GT-N7000 using XDA Premium App
@Archangel919
New Triangle away(v1.70) works on stock ICS ROM too
PS. Cf have said not to distribute apk, so just to respect developer post only link to his thread.(which also have newer apk).
I have a Samsung Captivate and it is running Gingerbread stock rom. I am very new to this thing and I don't know what a boot loader is.
I cannot seem to root this phone I have tried
Odin
Super one click
One click for all galaxy models
Update.zip
The update.zip method is very peculiar, it gives a message when I try to apply update from the zip "signature verification failed" and the reinstall packages does not show
The options are:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
That's it
My real question is, how to I install cyanogenmod 10 without rooting. If not possible, how do I root this thing.
BTW I have already tried to restore and still nothing happens
If u r running Gingerbread then u have the GB Bootloaders.
Get Root and/or KK4 Corn Kernel that has CWM Recovery included so that u can move on to flashing Dev Roms here...[Utility] KK4 Easy Root.
Read carefully. Read some more. Understand what ur doing and the risks involved. Proceed. Enjoy. Be sure to at least hit the Dev's thanks buttons because they have worked hard and spent a lot of time doing what they do.
4-2ndtwin said:
If u r running Gingerbread then u have the GB Bootloaders.
Get Root and/or KK4 Corn Kernel that has CWM Recovery included so that u can move on to flashing Dev Roms here...[Utility] KK4 Easy Root.
Read carefully. Read some more. Understand what ur doing and the risks involved. Proceed. Enjoy. Be sure to at least hit the Dev's thanks buttons because they have worked hard and spent a lot of time doing what they do.
Click to expand...
Click to collapse
I have already tried that, when i put it in download mode, Odin does not recognize it. It does recognize it when at launcher/lockscreen.
See the Captivate - PC Connection Issues...stickied thread in this forum.
Sent from my SGH-I777 using xda premium
I want to root my samsung captivate and install CM on it but i do now own a computer, and i do not want to "BRICK" or damage my phone. is there a way to manually Flash cm to install the recovery. Also could someone give me the "update.zip" that i have to flash to my phone to install CM.
I am a seriouse Noob at this.
Help.
thx,
dd
In my experience the 3e recovery that prevents the flashing of unsigned zips has to be replaced by the previous version. If you can get access to a computer with admin rights, it takes no more than 20 mins.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
davis the droid said:
I want to root my samsung captivate and install CM on it but i do now own a computer, and i do not want to "BRICK" or damage my phone. is there a way to manually Flash cm to install the recovery. Also could someone give me the "update.zip" that i have to flash to my phone to install CM.
I am a seriouse Noob at this.
Help.
thx,
dd
Click to expand...
Click to collapse
Here would be a good start: http://forum.xda-developers.com/showthread.php?t=1350266