This is a new updated guide on how-to flash roms found on XDA > Captivate > Development section from a stock phone out of box running 2.1 or 2.2 (or anything else). This method skips using the (out-dated for captivate) Rom Manager App CWM install and the 3e recovery "signature verification" crap and includes gingerbread bootloader update.
These instructions are the same for the i896 (rogers) and i897 (at&t) captivates. There is NO DIFFERENCE! ALL ROMS/KERNELS WORK ON BOTH PHONES!
ODIN METHOD (windows only)
If you have or EVER have had Gingerbread you can skip steps 4 - 6
If you have CWM already you might be able to skip 7 - 10 ( if rom wont flash you have wrong cwm type kernel (cwm2/3), and will need to do 7-10 with correct kernel type)
If skipping 4-6 AND 7-10 you can also skip 3 !!........and... 1
Take phone out of box (should be done)
Find a neat-o ROM from Captivate Development Section and get it onto your internal SD card (the one you cant remove) download using phone internet browser or download and copy to phone using PC.
Download and Run Odin Flashing Utility (not Odin one click) Odin3 v1.7.zip
Boot phone into DOWNLOAD mode (instructions below)
Click PDA button in Odin and find the .tar file --> i897 gingerbread bootloader upgrade (DO NOT USE BOOTLOADER BOX in newer odin versions!) ONLY DO THIS ONE TIME EVER! Only if phone has never had Gingerbread running on it. No need to downgrade bootloaders if going back to froyo!
Click "Start" in Odin
Reboot phone into DOWNLOAD mode (instructions below)
Click RESET button in Odin (beside START)
Click PDA button in Odin and find your kernel.tar file (speedmod kernel (this kernel isn't too important as it will be replaced by custom rom's kernel, but speedmod kernel understands both froyo (amend) scripting and gingerbread (edify) scripting so is great for this purpose to install any rom cwm zip file next.)
Click "Start" in Odin
Reboot into RECOVERY mode (instructions below) ** Use volume buttons to navigate up/dn and pwr for enter.
Select "flash zip from sd card"
Find your rom of choice on your SDcard and select Yes
WINNING! DONE YOUR FIRST FLASH!
Now you have CWM and a ROM....
Click to expand...
Click to collapse
Heimdall Method (Any OS) thanks to AdamOutler
AdamOutler said:
Ensure you have the lastest version of Java here
Download Easy CWM and Bootloaders Gingerbread here
Take phone out of box (should be done)
Find a neat-o ROM from Captivate Development Section and get it onto your internal SD card (the one you cant remove) download using phone internet browser or download and copy to phone using PC.
Boot phone into DOWNLOAD mode
Start Heimdall One-Click "EasyCWM and Gingerbread bootloaders"
follow directions (if any) given to install Heimdall drivers and dependencies (if required on your platform). On windows, the USB port your device is plugged into will now use heimdall drivers, if you have Samsung drivers installed, they will remain on all other USB ports.
Click "flash". Note: if you wish to upgrade bootloaders, hold Volume+ and Volume- so as to reboot into Download Mode after the flash otherwise skip the next step.
Check the Flash Bootloaders checkbox and flash again to upgrade to Gingerbread bootloaders (this only needs to be done once, EVER)
Reboot into RECOVERY mode ** Use volume buttons to navigate up/dn and pwr for enter.
Select "flash zip from sd card"
Find your rom of choice and select Yes
Click to expand...
Click to collapse
Odin flashing a kernel is only needed when switching from Froyo (cwm2) to GingerBread (cwm3) or vice versa.
**If staying on "froyo" based roms (or GB based roms) to flash a new rom or .zip kernel, just boot into cwm recovery and flash! no odin needed~!
**Froyo CWM kernels/roms use CWM2 with amend scripting
**Gingerbread CWM kernel/roms use CWM 3 or newer with edify scripting
**If flashing a froyo or earlier cwm.zip rom you must have a froyo cwm2 kernel first
**If flashing a Gingerbread or later cwm.zip rom you must have cwm3 or newer kernel first
**or just use Speedmod kernel with CWM 2.5 which understands BOTH amend and edify to change rom versions.
Instructions for download mode: (more help in post 2 if needed...)
plug USB cable into computer
have phone shut off
hold both volume buttons
plug USB into phone
let go of buttons when you see an android digging "down"
Instructions for recovery mode:
have phone shut off
hold both volume buttons
press and hold power button
KEEP ALL 3 BUTTONS HELD for 3-5 seconds
after kernel bootscreen you will see clockwork recovery menu
An advanced flashing guide (slightly oudated for gingerbread and more info than noobs need) here by a REALLY SMART GUY AdamOutler Again!
If windows doesnt find and install the drivers automatically here they are: (Win 7 has found them for me EVERY TIME, ive never had to install these but others have)
Windows Drivers - select the proper driver for your setup
32 bit: http://www.mediafire.com/?0b45zo7o75rc5d5
64 bit: http://www.mediafire.com/?3dh4d6up72me9re
other great guide is my NEW USER GUIDE in my sig. make sure to read it and find out what STICKIES are and make sure to read them in each forum section!
TO GET BACK TO STOCK:
ATT : [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
ROGERS : Rogers Captivate Stock ROMS 2.1-2.3
Advanced Download Mode Help
Originally Posted by jmtheiss
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try (many thanks AdamOutler and Pirateghost), sorted in a "where are you now" setup:
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+ and Vol-, then insert your USB cable.
- Press and hold Vol+/Vol-, Insert Battery, Insert USB cable
- Press and hold Vol+/Vol-, Insert USB cable, Insert Battery
- Use a 301Kohm jig between USB pins 4-5 (can be manufactured jig or homemade chain of resistors)
FROM A BATTERY CHARGING STATE
- With USB cable inserted into Android device, press and hold Vol+/Vol-, then press Power
- (Advanced Method) Use UART, and during battery charging, type "reboot download"
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", Plug in USB cable, press and hold Vol-, then hold Vol+, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
ADVANCED METHODS - REQUIRE HARDWARE MODIFICATIONS OR MORE IN-DEPTH TECHNIQUES
I'm presenting these largely unedited, as I don't want to incorrectly type an important detail of something that I don't understand myself.
- Apply UnBrickable mod to your device, then remove the battery, insert the battery, and click the "Download Mode" button on the computer
- Use UART (619Kohm resistor between USB pins 4-5, D+=RX, D-=TX, 192500bps 8n1 comms), press and hold ENTER while booting, then type USB
One additional thing - your download mode screen should, normally, look like the yellow triangle with the Android guy digging. However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen. If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Oh, and thanks mrhaley30705 for suggesting this thread.
Click to expand...
Click to collapse
END ALL DRIVER ISSUES WITH WINDOWS 7
Step 1 - Right Click " Computer " > Properties (aka system information)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Freakin awesome guide! Been confused about this lately. Now, I'm ready to flash! Thanks!
Can't wait to try this. My wife just got a captivate that replaced her HTC aria through ins. her aria was running current cm7 nighties. Can't wait do root her phone and run some custom roms and kernels on her bare stock froyo. wish me luck!
Im kind of confused on step 5. When i open up the i897 gingerbread bootloaders program and run it and click PDA where do I find the bootloader? Do I select the PDA.tar.md5 file that came with it? and if Im on Froyo and afterwards im going to flash current cm7 nightly, do i use the gingerbread kernel or the one Im CURRENTLY on? So sorry. Id greatly appreciate any assistance. my wife cant wait to have a snappy captivate.
Edit: The phone is completely 2.1 out of the box.
@ TRusselo.......
Great job !
One tip: PLEASE, PLEASE post the difference between CM7 and MIUI, and ROMs generally found here. Many first-timers don't realize that they are different beasts !
And you already have a question about CM7.......!!!!!!!
well.... I went for it and I can now have CWM 5.0.2.6 and I put the latest nightly and gapps on sd card and for some reason I cant see it on sd card anywhere? Ive done complete wipe and now ready for a rom but cant read anything on external_sd/? What do you think the problem is? PLease help....I ll hit the thanks button for like the next ten 10 days or something
I do eventually want my phone SIM un-locked, should I do that while I'm still on 2.2 or is it the same type of deal on 2.3 if I do it later?
NM, already did it.
tommyguns818 said:
Can't wait to try this. My wife just got a captivate that replaced her HTC aria through ins. her aria was running current cm7 nighties. Can't wait do root her phone and run some custom roms and kernels on her bare stock froyo. wish me luck!
Click to expand...
Click to collapse
tommyguns818 said:
Im kind of confused on step 5. When i open up the i897 gingerbread bootloaders program and run it and click PDA where do I find the bootloader? Do I select the PDA.tar.md5 file that came with it? and if Im on Froyo and afterwards im going to flash current cm7 nightly, do i use the gingerbread kernel or the one Im CURRENTLY on? So sorry. Id greatly appreciate any assistance. my wife cant wait to have a snappy captivate.
Edit: The phone is completely 2.1 out of the box.
Click to expand...
Click to collapse
bootloader program??? its a tar file you use with ODIN program. click PDA button. find the tar file that downloaded when you clicked the "i897 gingerbread bootloader" link above. Dont un-tar it.
tommyguns818 said:
well.... I went for it and I can now have CWM 5.0.2.6 and I put the latest nightly and gapps on sd card and for some reason I cant see it on sd card anywhere? Ive done complete wipe and now ready for a rom but cant read anything on external_sd/? What do you think the problem is? PLease help....I ll hit the thanks button for like the next ten 10 days or something
Click to expand...
Click to collapse
INTERNAL SD. NOT EXTERNAL. it says THE ONE YOU CANT REMOVE.....
holy heck slow down and get one question answered before moving on, and slow down and read. this is how you get into trouble.
edited moved
*deleted* moved to Q&A
tommyguns818 said:
*deleted* moved to Q&A
Click to expand...
Click to collapse
awesome! you're learning!
chappatti said:
@ TRusselo.......
Great job !
One tip: PLEASE, PLEASE post the difference between CM7 and MIUI, and ROMs generally found here. Many first-timers don't realize that they are different beasts !
And you already have a question about CM7.......!!!!!!!
Click to expand...
Click to collapse
umm, no difference in installation instructions.
this is an installation information thread. not "what is a rom? thread"
TRusselo said:
awesome! you're learning!
umm, no difference in installation instructions.
this is an installation information thread. not "what is a rom thread?"
and as said in post 10 of last page:
THIS IS A DEVELOPMENT THREAD. NOT Q&A
Click to expand...
Click to collapse
Yeah, but you cannot just get up and flash CM7 on top of a Captivate ROM.....That's what I meant.
chappatti said:
Yeah, but you cannot just get up and flash CM7 on top of a Captivate ROM.....That's what I meant.
Click to expand...
Click to collapse
I dont use CM7. i dont like it. from what i just read in the instructions. it is the same. AND I QUOTE:
Harder way:
Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
Root your device and install ClockworkMod Recovery.
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Click to expand...
Click to collapse
if you have information, share it, rather than asking others to post what you know.
post deleted by author, in the interest of maintaining peace !!
all i wanted, was for you to share what you know about installing cm7 as you said its different
and the post i read said its the same. I know nothing about CM7. if YOU DO, share it
TRusselo said:
awesome! you're learning!
umm, no difference in installation instructions.
this is an installation information thread. not "what is a rom thread?"
and as said in post 10 of last page:
THIS IS A DEVELOPMENT THREAD. NOT Q&A
Click to expand...
Click to collapse
The reply I got, quoted above, was totally uncalled for. I just see very angry responses happening way too often, even with newbies.
In my first post, I only just suggested the fact, very politely, since I believe that I must give you all the credit as the OP. But I got attitude.........maybe because you thought I was criticizing your post......which I don't see anywhere in my comments.
Anyways, peace.......!! I will delete my "hissy fit".
ANyways, coming to the point. The CM7 debate is discussed here:
http://forum.xda-developers.com/showthread.php?t=1130879
If you do NOT have AT&T GB bootloaders, you MUST flash them whether you want CM7 or Captivate ROMs.........this is the SAFEST for both ROM types.
Note that the repartition issue needs to be considered,in which case flashing complete stock GB WITHOUT bootloaders (once you already have ATT bootloaders) then installing Captivate ROm may be required.
Ok i read that post you mentioned and others and it does NOT matter what bootloaders you have. they both work fine.
so install instructions arent affected.
and the re-partition to come off cm7 is covered in the return to stock links
Quite frankly, while the thought of a guide is great, the bickering and arguing on all sides isn't helpful - nor does a guide to flashing belong in development, mainly due to the fact that people are going to read the guide, try to follow it, and, no matter how well written, ask questions - receiving arrogance isn't going to help them if they're in trouble. Developers don't need this guide, users do - thus moved to Captivate Q&A. Further argumentative posts will be removed andwill get the thread closed.
I hardly see how myself being ignorant to the installation of cm7 and asking someone else who knows about it, being arrogant. And asking that someone to provide the information that they say they know, "arguing from both sides".
Related
NOTICE 10/18/2010:
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47
I can vouch for this. It worked exactly as described.
Thanks!
Just to make sure after I do this I can flash any rom through odin without problem?
bobby915 said:
Just to make sure after I do this I can flash any rom through odin without problem?
Click to expand...
Click to collapse
I have flashed JFD, JI6, JI6 unofficial, JI6 OTA after flashing this and have had
no problem's
in general these files are written to parts of the phone that are usually never
written again after manufacturing and are responsible for getting the hardware
ready to load the kernel and then loading the kernel and booting the phone and
should not have any issues loading any ROM you care to flash.
Right now I can access download mode intermittently (maybe 1/10 times) by holding vol-up-down + power with usb plugged in. I cannot access recovery mode at all. Will this flash ruin my ability to access download mode? I feel like download mode is more important than recovery in case of a brick, but I would like the ability to go to recovery without adb or rom manager.
I've tried this 5 times, ODIN says failed everytime,EDIT Apparently 3rd times the 3rd time is the charm cause the 9th time it worked, Second Edit, The 9th time it started but its been 10 minutes so I assume it froze, Dammit.
Persanity said:
I've tried this 5 times, ODIN says failed everytime, Apparently 3rd times the 3rd time is the charm cause the 9th time it worked
Click to expand...
Click to collapse
So your recovery works now? Can you also get into download mode?
I'll add my Vibrant to the list of previously hardware locked phones, fixed by this.
I'd like to send out a HUGE thanks. Recovery and Download mode work every single time now. I can start playing around with roms safely.
Thank you so much
STEP BY STEP GUIDE
**UPDATE**10/14/10
STOCK RECOVERY VERSION OF HWLOCK FIX
untermensch has created a UPDATE.ZIP version of the fix
1) Download UPDATE.ZIP from OP or here http://www.megaupload.com/?d=2R2XOZ0X
2) Place UPDATE.ZIP in root of /sdcard not /sd
(If you have a previous UPDATE.ZIP file in root of /sdcard move it to another folder untill you have unlocked)
3) Use ADB to get into recovery
(use step posted below if you dont know how to use ADB)
(use command "adb reboot recovery")
4) Use vol down to navigate to reinstall packages press power to select
ODIN VERSION OF HWLOCK FIX
**NEW**
untermensch test file
(download from OP)
Everything you need minus drivers(or download individually in steps below)
http://www.megaupload.com/?d=66SSG9VR
step 1) go here and get the drivers and install them
http://forum.xda-developers.com/showthread.php?t=728929
step 2) download this zip file
http://forum.xda-developers.com/attachment.php?attachmentid=415810&d=1286579010
(load tar file from this zip in PDA section of odin after step 4)
step 3) go here download and follow guide to setup adb
http://forum.xda-developers.com/showthread.php?t=502010
(use "adb reboot download" to get to download mode)
step 4) go here get odin v 1.3
http://forum.xda-developers.com/showthread.php?t=790026
(run odin load tar in PDA make sure com4 or similar pops up click start)
FOR THOSE WHO NEED ADB HELP
REBOOT TO DOWNLOAD MODE WITH ADB
*must have drivers installed*
1) download androidSDK from here http://developer.android.com/sdk/index.html
2) extract the folder to root of your harddrive and rename it something short like ADB
3) on phone go to settings , applications , development and click USB debugging
then plug your phone into the computer
4) open windows command prompt and type this (hit enter after each line)
cd c:\
cd ADB\ (or whatever you renamed the folder in step 2)
cd tools\
adb reboot download
5) flash tar with odin
Sent from my SGH-T959 using XDA App
No, It did not work, The 9th time it actually started instead of saying failed immediately, But after 20 minutes nothing had changed and then odin cr5ashed and now my phone is soft-bricked/bricked whatever it is. All I know is im ****ing pissed. Can somebody point me in the direction of a complete restore thread? EDIT: Yeah I finally got it, Thank god I have never had a problem getting into download mode, When I say got it I mean restoring my phone to work not getting recovery to work, If I flash J14 first then J16 am I gonna lose the ability to go into recovery mode if the J14 update does actualy let my phone go into recovery?
untermensch said:
The leaked JI4 firmware contained the files needed to get the our phones unlocked
attached is an odin flashable tar with sbl.bin, boot.bin when flashed your phone wont ignore
the vol up + vol down + power buttons and you will be able to access recovery.
if you haven't used odin before follow AgentFour20's instructions http://forum.xda-developers.com/showpost.php?p=8541107&postcount=35
note:
1. the port wont be com4 for everyone as long as odin shows a com port you should be fine.
2. you might not need adb this method worked on my locked phone http://www.youtube.com/watch?v=rqxearzXrVY
you can flash this over any ROM or firmware and will probably never have to flash it again because boot.bin, sbl.bin are rarely included in firmware.
as usual use caution when flashing your phone, I am not sure if you can get back into download mode if this flash fails, So flash at your own risk!
for more info check out the I9000 thread:
http://forum.xda-developers.com/showthread.php?t=785201
and the original thread:
http://forum.xda-developers.com/showthread.php?t=802763&page=3
Good Luck!
md5 for tar file = d18f9d23d3060260a4e7edc1b6321941
Click to expand...
Click to collapse
Gonna put in my vote for one recommendation for you people who have a dickens of a time getting into download mode and are afraid of Odin3 leaving you stranded.
Try using Odin3 v1.30 instead of Odin3 v1.00 (it's linked in the Bible thread). My failure rate on flashing with v1.30 so far is zero. My failure rate when I was flashing with v1.00 was more to the tune of 50% of the time. I'm not hardware locked, so this is less scary for me than it is for you.
Just a safety tip...Best of luck!
sounds like solution is simple, but why did this occur on some vibrants in the first place?
SamsungVibrant said:
sounds like solution is simple, but why did this occur on some vibrants in the first place?
Click to expand...
Click to collapse
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Awesome....used odin 1.3 and this took a few seconds and worked flawlessly
if you follow the instructions in the posts above, don't see how you can go wrong
I can now access download mode and recovery...and I can sleep a lot easier knowing that if something happens I can fix it now
Yes! Masterotaku thank you so much for posting about odin3 v1.3, 1st time it work for J14 over J16, I can now boot into download and recovery mode. Sweet.
masterotaku said:
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Click to expand...
Click to collapse
hmmm interesting, seems like samsung isn't consistent with their screen tints also. They need to get quality control under quality control
Wanted to add that this worked for me as well. Thanks for the info.
Worked on first try, Odin 1.3. Thank you so much for this fix! I knew holding out on replacing my vibrant would pay off =)
Now I got into recovery by both vol + power then release power, but how do you guys get into download mode? I used to be able to get there occasionally by doing that same key combo, but with usb attached.
EDIT: Wow that was easy.
RECOVERY MODE: Hold both volume buttons and power, once vibrant logo shows up, release power.
DOWNLOAD MODE: Hold both volume buttons (no power) and plug in USB. Instant!
EDIT: Honestly I can't thank you enough. This is so amazing!
Thanks so much, this really works, my 1st time ever using odin 1.3
and finally figure out what adb is. Before even pulling the battery would
not get me into download,and the only way to get into recovery was using
clockworkmod. This really works!!! thanks you thanks you.
Everything is not as good as it seems. I managed to flash the fix all right and now I have download mode. But my friend had done the same steps as myself but odin FAILED to flash the fix. It just said:
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
And his phone is totally bricked now.
It is really dangerous to use ODIN on hardware locked phones... Too high chance of failure to flash. ((
First of all, nice work. Looking forward to 4.5. This was my first custom ROM install, so I have a few questions.
1. I didn't notice the auto-lagfix being applied when I installed. I am getting a quadrant score of about 1060 and it seems most people are getting much higher. Not that I am experiencing a lag, but just curious.
2. I am guessing I should start over when 4.5 comes out. I didn't try anything different than what came with it.
3. I love the orange theme, but would prefer the stock phone dialer buttons. How would I change that?
4. I did notice some issues with internet connectivity using the modem and not wifi. I shouldn't need to enable roaming, right? GSM only should work too? Why would WCDMA even be an option? Is GPRS an option or is it 3G only?
Thanks.
gokartracer5 said:
First of all, nice work. Looking forward to 4.5. This was my first custom ROM install, so I have a few questions.
2. I am guessing I should start over when 4.5 comes out. I didn't try anything different than what came with it.
Thanks.
Click to expand...
Click to collapse
I think Adam usually provides a statement whether or not you can flash 4.5 over 4.1 or whether one requires a wipe, flash to stock, and fresh install. I'm hoping 4.5 can be flashed over 4.1. Unfortunately, I don't have any answers for your other questions.
gokartracer5 said:
1. I didn't notice the auto-lagfix being applied when I installed. I am getting a quadrant score of about 1060 and it seems most people are getting much higher. Not that I am experiencing a lag, but just curious.
Click to expand...
Click to collapse
I was wondering about that myself. I couldn't find the voodoo folder that is supposed to exist to disable/enable lagfix. Any body have any ideas if the lag fix is actually installed with 4.1 or if there is other work required?
It seems to be just fine without it. That makes upgrades alot easier.I hear the folks who have official 2.2.1 overseas don't use a lagfix anymore.
Phoenix is based on 2.2.1 jpy.
As for the lagfix questions, with the included kernel you need to boot into recovery and choose advanced ulk, then enable/disable there.
thanks. ill try that later. looks like a new version of the market and google music might be announced tomorrow.
newter55 said:
Phoenix is based on 2.2.1 jpy.
As for the lagfix questions, with the included kernel you need to boot into recovery and choose advanced ulk, then enable/disable there.
Click to expand...
Click to collapse
Went through these steps and it appears to be working just fine. Thanks. So if I need to disable lag fix, I have to go back into recovery and not create the disable-lagfix folder like on the www.phoenix-hq.com FAQs?
Just tried it too. works like a charm and boosted quadrant up to 1300. Yeah I imagine that you(we) have to remember to disable it to flash another ROM.
So flashing the browser fix just involves copying the zip to the sd, renaming it update.zip, and use recovery to apply the update?
You don't need to rename the browser fix zip, or any for that matter. Just reboot into recovery and flash the fix by selecting it just as you do for a rom.
trekie86 said:
Went through these steps and it appears to be working just fine. Thanks. So if I need to disable lag fix, I have to go back into recovery and not create the disable-lagfix folder like on the www.phoenix-hq.com FAQs?
Click to expand...
Click to collapse
It looks like Adam and Xtreem haven't updated the website's FAQ section in a while. The first versions of Phoenix-Rising used DG's Firebird kernel, which used voodoo lagfix. Creating a file/folder named "disable-lagifx" to disable your lagfix only applies to voodoo lagfix. The lagfix on hardcore's kernel (which is the stock kernel used on both of Adam's roms) uses the ultimate lagfix configuration, which is controlled entirely through the recovery menu. Voodoo and ULF are similar to one another, but the user configuration processes are different.
If you need to reflash something, disable the lagfix first by booting into recovery, and follow the same steps you used to enable the lagfix and just select disable instead. However it is best to flash back to stock first before flashing a new rom, so yea, I would recommend starting over when you're ready to install 4.5
Changing the dialer is not all that complicated. Head over to the Phoenix/Firefly themes thread, you can find a bunch of different flashable dialers over there. http://forum.xda-developers.com/showthread.php?t=896339 Zelendel just finished a few new ones that have the stock button configurations in place. You'll have to look for that post, its somewhere near the last 1/3 of the thread.
quick question ( I would search but its broke, and i cant post in the phoenix thread until i have 10 posts)
Presuming its cool to flash this over 4.1, my brother did it with no problems, i just need to know if i should check backup rom or clear and wipe data in rom manager when i flash from sd card
New to the android stuff, but the first rom i tried to flash it locked up while installing it, he then told me just to flash straight from rom manager, worked great, so im going to try that
Thanks, i asked him but hes sleeping lol
I have the pheonix 4.1 rom. I noticed that using the power button it allows you to choose download mode. If I open odin one click and go into download mode this way will I be able to flash back stock or will I get stuck in file analyzing? I'm a little afraid to try because I don't know if I can leave download mode w/o bricking it. It's a miracle that I got it unbricked when I flashed the first time.
Sent from my SGH-I897 using XDA App
Ebro365 said:
I have the pheonix 4.1 rom. I noticed that using the power button it allows you to choose download mode. If I open odin one click and go into download mode this way will I be able to flash back stock or will I get stuck in file analyzing? I'm a little afraid to try because I don't know if I can leave download mode w/o bricking it. It's a miracle that I got it unbricked when I flashed the first time.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes, push and hold the power button gives you the extended power menu. Flight mode, Power off, Reboot, Recovery and Download. I've written some detailed instructions on how to flash back to stock JF6 and Master clear. Which I recommend doing when changing ROM's
Flash to Stock JF6:
1. Download Odin One Click from: http://www.mediafire.com/?0w2y31maz8mdom4
2. Download your Windows Drivers from:
Windows 64bit: http://www.mediafire.com/?3dh4d6up72me9re
Windows 32bit: http://www.mediafire.com/?0b45zo7o75rc5d5
3. Make sure your USB cable is connected directly to the back of your computer, not a USB hub or to a front connection and all of your drivers have been properly installed
4. Do not connect your USB cable yet.
5. On your phone, go to ; Settings/Applications/Development/and check “USB Debugging”
6. Turn your phone off
7. Remove your SIM card and Micro SD if you have one
8. Open Odin One Click
9. On your phone, press and hold the Volume up and the Volume down buttons. Do not touch the power button. If you have a ROM that supports a extended power menu, just press and hold the power button until the extended power menu comes up
10. While holding them, or after you select DOWNLOAD mode, insert your USB cable, wait for a couple of seconds and a yellow triangle with the Android figure will show up
11. You’ll see in Odin, that your phone has been discovered
12. Press “Start”
13. ***VERY IMPORTANT*** Do Not mess with your phone at all. If you lose your USB connection, you could brick your device, and will possibly have to make a jig
14. When it is done, your phone will reboot and Odin will display “Removed”
15. Unplug your USB cable from your phone
16. If you are proceeding to Master clear, you must close Odin BEFORE Master Clear
Master Clear:
1. Ensure you have backed up all of your information onto your Micro SD or your desktop BEFORE doing this. IT WILL ERASE EVERYTHING ON YOUR INTERNAL SD!!
2. Make sure to remove your SIM and Micro SD if you have one
3. With your USB cable disconnected from your phone, open Odin One Click
4. On your phone, go to ; Settings/Applications/Development/and check “USB Debugging”
5. Connect your USB cable to your phone
6. You’ll see in Odin, that your phone has been discovered
7. Click “Master Clear”
8. When the Master Clear has completed, your phone will reboot
9. The phone is now as it was when it came from the factory
gokartracer5 said:
So flashing the browser fix just involves copying the zip to the sd, renaming it update.zip, and use recovery to apply the update?
Click to expand...
Click to collapse
do not rename the file to update.zip, that name is used by recovery. just use the name as it is.
Thanks, I thought I could use the power button. Thanks again for the help.
Sent from my SGH-I897 using XDA App
Introduction
I've put together a video on how to flash a rom. It includes Rooting, Backing up data, Flashing a kernel, Flashing a rom, and troublehooting bad flashes.
Warning
Before you go and flash a ROM for the ultra-fast speeds, kick-butt graphics and awesome sound upgrades... Realize that the risks are real, it is possible for you to black-screen-brick (hard brick) your phone. Here is a real-world example:phone won't turn on. At this point, only JTAG recovery will be effective. I will be posting a video on JTAG soon enough.
You may feel more comfortable stopping after rooting and titanium backup, and not installing a ROM at all, that's OK.
How-To
If you are installing a ROM, then select the ClockWork Mod flashable zip you want and copy it to your phone's internal memory before you watch the video. I did not cover this in the video as there are many options. Team Komin recommends Andromeda3, but you may select any Captivate ROM.
Here is the video which I have prepared on flashing a custom ROM.
Flashing Toolbox
Windows Drivers - select the proper driver for your setup
32 bit: http://www.mediafire.com/?0b45zo7o75rc5d5
64 bit: http://www.mediafire.com/?3dh4d6up72me9re
Files
*SuperOneClickV1.7 - http://files.teamkomin.com/Andromeda/Tools/SuperOneClickv1.7-ShortFuse.zip or http://www.mediafire.com/?kr649t97dd116cd
*Odin3 1.7- http://files.teamkomin.com/Andromeda/Tools/Odin3 v1.7.exe or http://www.mediafire.com/?dy2ix2icags19qr
*Ursa Minor - http://files.teamkomin.com/Andromeda/Tools/UrsaMinor.tar or http://www.mediafire.com/?a1i0boby6em54eo
*Andromeda3 - http://files.teamkomin.com/Andromeda/Andromeda3-Final.zip or http://www.mediafire.com/?vpu22j478j4542a
Recovery Software
*Odin3 one-click 1.0- use only in case of emergency, this can damage your phone -http://www.multiupload.com/XAZUYNXSC1
Tips, Tricks, Good to know
If you have a standard computer setup and you see your phone connected to a port higher then COM6, reboot your phone and your computer before flashing anything.
Phone--!--PC is just a download mode. If the computer does not recognize the phone, reinstall drivers, reboot and pull the battery out, then try again.
Odin is only used for initial and/or recovery modification. After using odin to flash a new kernel sucessfully, you will only need ClockWorkMod (CWM) to flash most kernels and ROMs. CWM is accessed by pressing and holding the 3 button combo.
If your phone displays Phone--!--PC and does not register a COM port on your computer follow the directions below
1. remove the usb cable, battery, sdcard, SIM.
2. wait 10 seconds, then insert the USB cable.
3. press and hold the 3 button combo while you insert the battery
4. continue to hold until phone's screen goes black twice and release power button.
5. timing is critical, it may not work the first time. Keep going until you see the COM port is connected properly.
Disclaimer: All materials presented are for informational purposes. This video is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.
Thanks for the guide adam, I'll be using this tonight. Could you possibly update this with a section on how to go back to a stock kb1 build? That would be great.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
AdamOutler said:
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
Click to expand...
Click to collapse
Thats JF6, not KB1.....
Stock 2.2 you get from the update using kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dead Links
Hey could you repost the download links because none of them work anymore? Thanks
Sorry, Team Komin's server is down right now, there are other sources on the internet. I will mirror on mediafire as soon as I can
In a boot loop - Moved from Andromeda thread
Hi Adam, Just to get up everyone where we are. I had a flashing issue with Andromeda which resulted in the phone continuously rebooting; i.e. white screen Ursa Minor screen disembodied voice which I now think says missing operation, it definitely doesn't say backup operation, I've listened to it soooooooo many times. . .anyway I put the phone in download mode as you said - BTW this phone with phone off vol+vol then plug in USB and download appears. Holding the power button takes you -when the phone isn't loopiing of course- into recovery mode. I had already restarted the computer, - not a VM - restarted Odin 3 and tried to reflash. Pass! Reset and unfortunately I'm still in that loop can't get to recovery mode.
I removed the battery and USB. Held down all three buttons and with the USB cable connected put the battery back. I held through 2 screen goes black circuits. Second time up the screen shows a gray battery then goes black then I get the ATT screen followed by Ursa Minor and my now less than favorite voice. Doing the same without the USB cable I don;t get the battery but I do get the ATT splash screen between the two black screen and then that darling voice again. So that's where I am. Ideas please
Personally I would One-Click back to Stock. ROOT. Install CWM using Rom Manager. And then install Andromeda via CWM. (I usually skip re-rooting and just install from CWM via the update.zip from ROM Manager) See if that doesn't work... If it does, finish up by installing Ursa Minor #2 (or is it just Ursa Minor now?)
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
^^ It can be tricky to get it into download mode, but there are several ways to do it on all phone. The important thing is that you get a sane COM port like COM8 or less on Odin3 1.7, and that you have download mode activated on the phone. Good to see that everything is working properly.
BWolf56 said:
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Click to expand...
Click to collapse
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
fireboss said:
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
Click to expand...
Click to collapse
OK well I've confirmed that Odin One Click won't restore on this phone unless it is open on the Windows machine when I connect the USB port tot throw the phone into download.
I restored then went through the flashing process again. This time when when it rebooted it didn't loop but it wouldn't go into recovery. I used droid explorer to flip it to recovery mode. Inoted then that there was no adndromeda.zip package on the sd card. I assumed Ursa was supposed to pull that over because in the video it says to find it and install. In any case I drug it from the computer to Droid Explorer and then was able to find it and install the Rom. The unpack looked normal enough the system rebooted. I unplugged USB,gave it the three button fix roputine, and was back in the loop. No matter what I did it looped. The loop was slower this time and the voice clearly said Restore Operation. Not knowing enough to wander farther and unable to get into recovery now because Droid Explorer couldn't see the phone anymore I let Odin restore it. That's where I am now.
Suggestions?
AdamOutler said:
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
Click to expand...
Click to collapse
Thanks! I'll try that out once I get home from work. The only thing I can say is that I wish that would've been up when I got my 1st cappy - would've saved me the trouble of having to Odin3 1 click
Once again, Great work!!
EDIT: This should be Stickied!
fireboss: redownload all links above, it is possible that something went wrong with the download process and a bit is missing somewhere.
-copy the rom of your choice to your SDCard (Team Komin recommends Andromeda3, but any will work)
-put the phone into download mode and flash ursa minor tar file using Odin3 1.7
-let it run though it's operation until it boots normally.
-remove the usb cord, press and hold 3 buttons to reboot into recovery
-select zip from SDCard- Andromeda3.zip
i dont see a link, or file attachment or any mention of 3e recovery in OP
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Might already be in Ursa Minor? (correct me if I'm wrong Adam)
fireboss said:
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after.
Thanks
Click to expand...
Click to collapse
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Right Bwolf
No need to mess with 3e recovery. UrsaMinor.tar overwrites 3e recovery and gives you CWM so you can begin flashing immediately.
mxracer101 said:
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Click to expand...
Click to collapse
That works. The biggest thing is that you are in download mode and you have a sane COM port like COM5 or 6, not COM14. As shown in the video, COM14 lead to Phone--!--PC..
I may do this video again with heimdall. it worked well.
mxracer101, any chance you can generate a pit file? I'd like to make Andromeda3 into a full heimdall flash where you simply put the phone into download mode, select the files, hit start, and let the stock phone boot into Andromeda3.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For the Galaxy Tab 10.1 WiFi Edition
Warning: I am not responsibile for any damage you may do! Use at your own risk!
Warning 2: Backup to your PC all files you want to keep unless you know what you're doing!
What you will need:
Update.zip Method:
Clockwork Recovery (See here or here)
Update.zip (Thanks pershoot! ) Mirror
Instructions:
Clockwork Recovery Method:
Code:
[LIST=1]
[*]Copy pershot's update .zip to your sdcard
[*]Power off your device
[*]Turn on your device by holding the power button and the volume down key at the same time
[*]Select the recovery option by using Volume Down to switch option and Volume Up to select
[*]Do a full wipe
[*]Choose a zip to flash from sdcard
[*]Once installed reboot system
[*]Wait 5 - 10 minutes for it to boot (be patient)
[*]Done! :D
[/LIST]
Change Log:
Code:
[B]14th July:[/B]
New WiFi base (No more sim card issues)
Removed Odin method
[B]Initial Release:[/B]
3G Rom for WiFi Tab (Issues with sim card)
To Get Root:
Download and install this .zip in Clockwork mod
Current Issues:
... None so far!
TouchWiz Video:
http://youtu.be/hlLP3RXkmUQ
Screenshots:
Where did you get it???
Sent from my GT-I9100 using XDA App
It's been posted in the general section.
http://forum.xda-developers.com/showpost.php?p=15510585&postcount=18
I want this bad!!
Lovellkid
Cant wait...
Doesn't anybody know how to convert this image file into an update.zip that we could flash via ClockWorkMod? Doesn't any dev want to be the unforgattable hero posting the first instructions for TouchWiz on our beloved Galaxy Tab 10.1?
you can restore the img file from backup/restore > advanced option of clockwork recovery! but first copy the img into clockworkmod >backup folder in sd card.
No, it says "MD5 mismatch"...
OK, had a spare I/O tab lying around that I use for development and writing apps, so thought I'd try it....This is with Odin3 v1.3...obviously I have a tab that is not full of personal stuff so I just blasted it....If you want to do it on your one and only then for Pete's sake make sure you back up all data and apps before if you feel it's neccessary
Unzipped the file from the download link.
Select the downloaded .tar in PDA in Odin, connect tab and click start...don't hold your breath, you'll probably be dead before it's finished
When the Odin upload has finished the tab boots straight into recovery mode...I had a few warnings regarding efs and sd extension etc. but as this is a wifi only tab and does not have a removable sd card think that is probably normal.
In recovery the installation program automatically formatted the cache...
As I was strting from scratch I did a factory reset just for good measure.
After many years of mac, pc, prologue and now trying app development work I am a firm believer in "If a job's worth doing, it's worth doing properly"....loading upgrade upon upgrade on existing systems eventualy brings said system to it's knees, so better to start afresh.
Hit reboot from recovery and the usual fresh install scenario started with the pulsating Samsung logo as the dalvik was I suppose re-written
Then went to normal initial setup screen which for some reason started in Italian - I know I eat a lot of pasta and pizza and drink chianti from time to time but that's just ridiculous!!
Initial reaction to visual interface was "Wow!" Now I am a bit of a purist and Vanilla lover but I am not blinkered (never joined any of the blind rhetoric "mac is best", "pc is best" blah blah clubs being a scientist by origin) and I have to say in my opinion the visual interface is far better than vanilla honeycomb
Will run some standard tests and put up screenshots in an hour or so...gotta eat some pasta and drink a couple of bottles of chianti first...
stinky73,
Same result on a Retail Tab 10.1 with a LOCKED bootloader, seeing that it works for me, it should be safe for everyone who wants to try without worrying about a brick.
NOTE: You have to do a factory reset, I got a bootloop but the problem was fixed by the reset
stinky73 said:
OK, had a spare I/O tab lying around that I use for development and writing apps, so thought I'd try it....This is with Odin3 v1.3...obviously I have a tab that is not full of personal stuff so I just blasted it....If you want to do it on your one and only then for Pete's sake make sure you back up all data and apps before if you feel it's neccessary
Unzipped the file from the download link.
Select the downloaded .tar in PDA in Odin, connect tab and click start...don't hold your breath, you'll probably be dead before it's finished
When the Odin upload has finished the tab boots straight into recovery mode...I had a few warnings regarding efs and sd extension etc. but as this is a wifi only tab and does not have a removable sd card think that is probably normal.
In recovery the installation program automatically formatted the cache...
As I was strting from scratch I did a factory reset just for good measure.
After many years of mac, pc, prologue and now trying app development work I am a firm believer in "If a job's worth doing, it's worth doing properly"....loading upgrade upon upgrade on existing systems eventualy brings said system to it's knees, so better to start afresh.
Hit reboot from recovery and the usual fresh install scenario started with the pulsating Samsung logo as the dalvik was I suppose re-written
Then went to normal initial setup screen which for some reason started in Italian - I know I eat a lot of pasta and pizza and drink chianti from time to time but that's just ridiculous!!
Initial reaction to visual interface was "Wow!" Now I am a bit of a purist and Vanilla lover but I am not blinkered (never joined any of the blind rhetoric "mac is best", "pc is best" blah blah clubs being a scientist by origin) and I have to say in my opinion the visual interface is far better than vanilla honeycomb
Will run some standard tests and put up screenshots in an hour or so...gotta eat some pasta and drink a couple of bottles of chianti first...
Click to expand...
Click to collapse
Awesome, can you try and flash the pershoot / bonsai overclock-able kernels and see if they work? Thanks for the info!
Touchwiz UX
I have an unrooted device and followed stinky73's instructions and was able to install touchwiz UX on my device
The only issue i have seen so far is that the samsung app store says it needs a sim card to be able to run.
I'm gonna try rooting it now.
Update:
Can't get into Recovery Mode
lordwinkevin said:
I have an unrooted device and followed stinky73's instructions and was able to install touchwiz UX on my device
Click to expand...
Click to collapse
So you went straight from a stock tab, flashed this with Odin and now have tochwiz working properly?
I have a Droid Charge, so I'm familiar with Odin, but how do you enter download mode on the tab?
Thanks
apascual89 said:
So you went straight from a stock tab, flashed this with Odin and now have tochwiz working properly?
I have a Droid Charge, so I'm familiar with Odin, but how do you enter download mode on the tab?
Thanks
Click to expand...
Click to collapse
Hold down power + Vol Up until you see the 2 options for 'Recover' and 'Download'.
Use 'Vol Up' to select an option
Use 'Vol Down' to enable it
This no longer is available after I flashed the Touchwiz Tar file via ODIN though so if anyone has found a button combo for recovery for it, please let me know.
Thanks.
phonepersonality said:
Hold down power + Vol Up until you see the 2 options for 'Recover' and 'Download'.
Use 'Vol Up' to select an option
Use 'Vol Down' to enable it
This no longer is available after I flashed the Touchwiz Tar file via ODIN though so if anyone has found a button combo for recovery for it, please let me know.
Thanks.
Click to expand...
Click to collapse
It still works, but the problem is that you have like half a second to release the buttons before the tab reboots again. I am able to get successfully into recovery if i act quick.
In other news! The root from recovery was successful, This version is rootable by simply flashing the root zip file from the stock recovery.
I have retail version with unlocked bootloader from BB and installed customized recovery (clockworkmod) then connected to my pc with odin3 running. You have to have the custom recovery and i had it when i rooted and unrooted my device.
PS
This version is i think for the 3g model because it has extra settings that is unusable like tethering. The overall experience is very nice and has some very nice functionalities. The UI is very intuitive and has some very poweful apps preinstalled. I am looking forward to the official touchwiz ui and one of the added functionalities i love is the ablity to change the display modes or screen color calibration rendering more natural colors for my photography portfolio. The picture editor is very robust and hopefully the stylus in the works will work like the htc flyer stylus for use their own memo pad.
Sent from my GT-P7500 using XDA Premium App
You just have to install the customized recovery by following the instructions of how to root the device. Just follow until you are able to install the custom recovery then use odin to get touchwiz ux
Sent from my GT-P7500 using XDA Premium App
I just tried pershoots kernal, and please note that it does not work, and flashing the tool pack does not fix it. The only way i could find to fix it was to install the tar file from odin again.
hello i've been trying 2 get a new rom for my brother's SGS+
but almost every rom i try (mostly jelly bean and ics roms but also some gb ones) give me n error
when i try 2 install them through recovery mode,
i get error status 7, installation aborted
now i looked for this problem on the internet and it appears there r some solutions found on this link:
http://www.knowtechbetter.com/how-t...ry-cwm-while-installing-flashing-custom-roms/
however i did not understand any of this
i m not new in installing roms and such but i m not very femilier with all these "more complicated" things
i noticed at the comments that the first solution helped someone
and it looks easy, if any1 could explain me shortly how do i do this this would be very helpful.
thanks~
Install newer CWM.. you have to ask this in the special thread made for it
broodplank1337 said:
Install newer CWM.. you have to ask this in the special thread made for it
Click to expand...
Click to collapse
i have faemod v1.2 based on cwm 5.0.2.7 ..
and honestly i dont know which threat you are reffering to
Cyanogenmod 10.. There is a link to CWM..
On the wiki page (see the index i made) you can also find CWM and an installation guide.
mrjraider said:
Cyanogenmod 10.. There is a link to CWM..
On the wiki page (see the index i made) you can also find CWM and an installation guide.
Click to expand...
Click to collapse
if u could help me just a little more, i cant find it.
Wiki link http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001
mrjraider said:
Wiki link http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001
Click to expand...
Click to collapse
thanks i managed 2 install cwm 6
but i encountered a new problem.
i installed the non-touch verision and now i cant do the "select" option
it is supposed 2 be the power button but it doesnt work
so now i cant do anything..
also i tried rom manager but it just opens recovery mode for me
any way i can return to an old verision of recovery w/o using the reovery mode so i can go back and install the touch verision this time?
There are more buttons to use. If i can remember you need to use the menu button
mrjraider said:
There are more buttons to use. If i can remember you need to use the menu button
Click to expand...
Click to collapse
tried them all.. i am really stuck here
appearntly alot of ppl have this problem.
is there any way to install it through odin or some other app?
Via odin install CWM 5.5.0.4.. See the wikilink i provided.. This one is stable and the homebutton is the choose button.
mrjraider said:
Via odin install CWM 5.5.0.4.. See the wikilink i provided.. This one is stable and the homebutton is the choose button.
Click to expand...
Click to collapse
maybe im doing it wrong but odin doesnt even recognise the file.. and there is no guide there
i did try a odin flashable cwm V6 but its stuck on "setup connection" each time i try..
Le tips:
- Patientce
- Remove and replug device
- Reboot device
- Use another USB port or cable
- Turn kies of (ctrl+alt+del > Taskmanager > Procesess > Terminate anything with KIES in its name)
- Turn AW/FW off
Just flash TWRP and you're good to go
Sent from my GT-I9001 using xda app-developers app
mrjraider said:
Le tips:
- Patientce
- Remove and replug device
- Reboot device
- Use another USB port or cable
- Turn kies of (ctrl+alt+del > Taskmanager > Procesess > Terminate anything with KIES in its name)
- Turn AW/FW off
Click to expand...
Click to collapse
dude im fricking out..
i accidently soft bricked it and now im trying 2 flash it back 2 stock with odin through your guide
but odin recognises my pc recognises the ops file as a text file so odin doesnt even see it...
u gotta help me ;_;
hey man relax... in wiki page you'll find cwm5.5.0.4 flashable zip and you can install it from recovery ( even from stock recovery if i remember corectly)... if you can't acces your phone you can copy it from pc to phone using recovery ( mounts and storage )... if you are stuck in recovery( you're phone boot in recovery only ) you'll need to flash the bootloader using odin.. also you can find the steps and necessary files in wiki and in cm10 by ivendor in firrst post ..Good Luck !!!
1: How did you softbrick it? What did you do, because I thought Odin got stuck??
2: You do see an Phone an ! and a PC?
3: You do have the latest ROM by Samsung and the correct AriesVE.ops?
If yes then we can get started. Follow my guide, when odin gets stuck at System (for a long long time > You know this because the green balk with time gets stuck) unplug device, reboot download again, reboot computer, and try again with BroodROM RC5 (see index)... (BroodROM RC5 is a last resort for our device since it has fixed many softbricked one including mine)
mrjraider said:
1: How did you softbrick it? What did you do, because I thought Odin got stuck??
2: You do see an Phone an ! and a PC?
3: You do have the latest ROM by Samsung and the correct AriesVE.ops?
If yes then we can get started. Follow my guide, when odin gets stuck at System (for a long long time > You know this because the green balk with time gets stuck) unplug device, reboot download again, reboot computer, and try again with BroodROM RC5 (see index)... (BroodROM RC5 is a last resort for our device since it has fixed many softbricked one including mine)
Click to expand...
Click to collapse
see the problem?
http://i39.tinypic.com/amp1ch.png
the thing is even tho i read your guide it seem like im doing something wrong..
for instance when i add the files both ops and "one package" file it doesnt see them so i have to write their location
shahaf321 said:
dude im fricking out..
i accidently soft bricked it and now im trying 2 flash it back 2 stock with odin through your guide
but odin recognises my pc recognises the ops file as a text file so odin doesnt even see it...
u gotta help me ;_;
Click to expand...
Click to collapse
aaaand that's what happens when you start flashing random stuff to your phone without knowing what you actually do...
Ok, I wont tease you or anything, here is what to do:
READ THIS
THIS (all stuff from there, doesn't matter if you don't consider it necessary, you surely will in the future)
After you read all those and understand everything, flash back to stock using @mrjraider tutorial, it's a clear step by step one so follow every step.
Now, the thing is that you'll need CWM Recovery, not FeaMod which is only able to flash GB ROM's.
The most stable CWM recovery is CWM 5.5.0.4 you can find it at the bottom of the OT from this thread
HERE is how to flash CWM with Odin.
Please, pay attention and don't rush things up. And next time you have a problem post in an appropriate thread don't open a new one and especially not in the dev section, see this
Also, no user "gotta help you" you've chose to flash tings to your phone, if you mess it up, it's your own failure and nobody 'MUST' help you... (see this)
educk said:
aaaand that's what happens when you start flashing random stuff to your phone without knowing what you actually do...
Ok, I wont tease you or anything, here is what to do:
READ THIS
THIS (all stuff from there, doesn't matter if you don't consider it necessary, you surely will in the future)
After you read all those and understand everything, flash back to stock using @mrjraider tutorial, it's a clear step by step one so follow every step.
Now, the thing is that you'll need CWM Recovery, not FeaMod which is only able to flash GB ROM's.
The most stable CWM recovery is CWM 5.5.0.4 you can find it at the bottom of the OT from this thread
HERE is how to flash CWM with Odin.
Please, pay attention and don't rush things up. And next time you have a problem post in an appropriate thread don't open a new one and especially not in the dev section, see this
Also, no user "gotta help you" you've chose to flash tings to your phone, if you mess it up, it's your own failure and nobody 'MUST' help you... (see this)
Click to expand...
Click to collapse
i did try using his guide and i folowed it step by step
my only problem is that odin gives me that message i showed in my last post..
also untill i fix this soft brick i cant move on to recovery mode so
i need 2 fix that first..
the guide doesnt show anything related to what im doing wrong..
Someone with brains would have removed odin, and the ops file and redownloaded it again. Also save those on your desktop