DOWNGRADE BEFORE I COULD UPGRADE
I had to jump through a lot of hoops to help a friend upgrade their Samsung Continuum (on Verizon) to the new Froyo 2.2.2 (EC09). I had previously rooted the phone, which was still on DL17, and that was now crashing the official upgrade. So I thought I'd document what finally worked, for anyone else who's struggling with the same. Not guaranteeing my procedure will work, of course.
Mostly, I've summarized and rewritten the other instructions I found buried in and amongst the other discussion threads. After successfully restoring 'stock' the official Froyo upgrade finally worked.
PRE-REQUISITES
- locate the thread, [DEV] Continuum DataBase [EC09][DL17][EC03][EC07]
- download the following files:
Samsung i400 USB driver
"DL17 Factory stock rom+radio+kernel (odex) all in one odin flash"
(the resulting unzipped file is 'Continuum-Stock-DL17.tar.md5')
ODIN flash-tool
- download the updated "EC07" PIT file (the "DL17" PIT didn't work for me!)
Samsung_I500_VZW_PIT.PIT
PROCEDURE
Install the Samsung i400 USB drivers
Remove battery from phone (not sure if this is necessary but some threads advised it, and after several failed attempts I was desperately trying everything. In any case, it didn't interfere with a successful imaging!)
Connect the phone on USB
Hold VOL-DOWN plus PWR buttons until the built-in 'Flashing' screen appears (should be immediate)
Confirm that the computer detected the phone over USB
If not, re-run the Samsung USB Driver install and select 'Repair')
run ODIN
Confirm that there is a yellow 'COM' status showing in the top-left.
If not, ODIN isn't connected to the phone!
Click on 'PIT' button and select the 'Samsung_I500_VZW_PIT.PIT'
UNCHECK the checkbox option for 'Re-partition'
Click on 'PDA' button and select the 'Continuum-Stock-DL17.tar.md5' file
Click START
You should see a steady stream of status updates in the bottom-left window as well as a progress bar in the top-left (labeled "factoryfs")
The update should take about 10 minutes, then the phone will reboot. The reboot takes about 2 minutes and there is nothing shown on the phone!
NOTES
I originally tried using the (DL17) 'SCH-i4000-VZW-Continuum.pit' but it didn't work.
I also tried it both with and without the re-partition option; neither worked
At one point the phone stopped being recognized on USB. I simply re-ran the Samsung USB Driver install and selected 'Repair'. Then the phone was recognized again.
There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"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, sorted in a "where are you now" setup:
Note: You will need to use Vol+ to select download mode after you reach the mode selection screen.
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol-, Home button, and Power.
- Press and hold Vol-/Home/Power, Insert Battery.
- Use a USB jig (can be manufactured jig or homemade chain of resistors)
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", hold Vol-/Home, 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 mode.
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+, Home button, and Power.
- Press and hold Vol+/Home/Power, Insert Battery.
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 recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery.
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
- Download the app "Rom Manager", select "Reboot to Clockwordmod Recovery"
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin up, the phone's in download mode, it's connected to the computer, but Odin is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you with that smug green face.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices (phone and PC) - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up Odin. Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the Android guy with the 4-5 lines of text in the upper left corner.
7. Connect your cable to the phone. Let it sit until Odin recognizes it (which should only take a couple of seconds).
If, for some reason, Odin doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
--------------------------------------
Additional Note:
If you're moving from an AOSP-based rom (MIUI, CM10, etc) to a Touchwiz-based / Samsung Stock-based rom, remember to wipe data / factory reset prior to flashing a stock rom. You will hang on the "Samsung" logo if you don't.
Please note very carefully, though, to do the wipe in CWM recovery - not 3e recovery. If you do it in 3e recovery, you'll format the internal storage, meaning you lose all your pictures, music, etc.. (I learned this the hard way.)
--------------------------------------------
If anyone has any additional items / corrections, please reply and I'll update the OP accordingly. Thanks.
Reserved
Great guide!
I'd like to add my experiences, while using CWM 6.0.1.2 booting into Recovery is a bit tricky. It appears the default recovery boots instead of CWM. The only work around I know of is to Flash ClockworkMod Recovery first from ROM Manager v5.0.2.0 and then select Reboot into Recovery. Any other method I try seems to fail.
I'm running Stock At&t ROM, rooted.
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
OP thanks for exelent post..I had one more problem with USB connection. Sticks in usb port did not connect correctly. Just jently squize USB male connector on samsung data cable so top of male connector will bend just enough to get good connection when you push back to PC port.
@djtiko - I answer on other post to your problem..
djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
Do a factory reset again, should fix you up. If not, consider using Odin to flash a stock ROM package.
Thanks got it all fixed, just had to do a data wipe in the stock recovery and then I was golden
ondin
Hey guys when i run the bootloader file should i open it up in the pda tab on ondin or in the Bootloader tab?
Should be in the pda tab I believe.
Edit. Which bootloader file are you referring to? To know for sure, you could just flash the entire stock rooted jelly bean Rom.
If using Odin with Chainfire to auto root just to root I found that the file that you are using to root you HAVE to have in the SAME folder I made the mistake of downloading the Odin then Odin with chainfire from http://forum.xda-developers.com/showthread.php?t=1963790 then was opening the odin first downloaded then it would stall for not able to start the installation then rechecking the unzipped folder for the .tar.md5 file noticed that Odin was there too, loaded it and PRESTO rooted in less than 30 seconds... So for other that are just looking to root give chainfire a check, yes you would need to use the triangle away if you are worried about that however you don't loose anything when doing it this way so all a matter of what you are looking to do. THANK YOU so much for the help with the drivers issues!
So I have liquid smooth 4.2.2 installed with along of Clockworkmod recovery. However this morning i recieved a notification saying that i had a gapps update. so i I went ahead and downloaded the zip file. When attempted to install, it asked if i have a recovery system or something like that. Me very ignorantly selected no and my phone guided me to download a different recovery. so i went ahead and installed it and after it booted i rkept on recieving a message that said unfortanely gapps has stopped. Then I thought that if i did a factory reset it would reset my whole phone and hopefully clear this error. I went ahead and pressed home, power and volume up and bam thats when i realized i overwrote my clockworkmod recovery with another recovery. It had to options to factory reset so i went ahead and tried it anyways. when the phone booted i still recieved the error message but this time it also had the message "setup wizard has stopped." im stuck with the screen you get when you intiially set up your phone and i can't do anything about it. I try pressing home, volume up, and the power button but it doesnt bring me to the recovery screen. Instead it just loads back to the initial setup screen after a while. When i try plugging it in the computer it doesnt not read. I cant do anything. Please help me! I just got the phone about a couple months ago and am to poor to buy another one.
Did you try going to download mode by holding volume down + home + power buttons?
Sent from my SGH-T999 using xda app-developers app
Your phone isn't bricked use Odin guide that is stickied in dev section
T-Mobile SGS III
calbertc12 said:
So I have liquid smooth 4.2.2 installed with along of Clockworkmod recovery. However this morning i recieved a notification saying that i had a gapps update. so i I went ahead and downloaded the zip file. When attempted to install, it asked if i have a recovery system or something like that. Me very ignorantly selected no and my phone guided me to download a different recovery. so i went ahead and installed it and after it booted i rkept on recieving a message that said unfortanely gapps has stopped. Then I thought that if i did a factory reset it would reset my whole phone and hopefully clear this error. I went ahead and pressed home, power and volume up and bam thats when i realized i overwrote my clockworkmod recovery with another recovery. It had to options to factory reset so i went ahead and tried it anyways. when the phone booted i still recieved the error message but this time it also had the message "setup wizard has stopped." im stuck with the screen you get when you intiially set up your phone and i can't do anything about it. I try pressing home, volume up, and the power button but it doesnt bring me to the recovery screen. Instead it just loads back to the initial setup screen after a while. When i try plugging it in the computer it doesnt not read. I cant do anything. Please help me! I just got the phone about a couple months ago and am to poor to buy another one.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly. Doing anything else will just prolong your problem.
Easy and sure way fix your problem - Here is s step by step guide:
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the file using Winzip or 7zip so the .TAR file
is in the new folder you just made. Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: Odin_Flash
• Download ODIN which is required for flashing the stock rooted firmware (a windows app)
• Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
• Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
• Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up,
then release and press Volume Up to enter Download Mode)
• Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
• You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
• Click on the PDA button in the middle-right area of Odin.
• Browse to and select the rom you just downloaded (TAR file).
• Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
• TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
• If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
• Click Start to begin the flash. This will take a while, so be patient!
• Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
• You may unplug the phone and close Odin if you wish.
• Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
• (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
I am completely new to the whole rooting thing, but I decided to try rooting my T-Mobile Galaxy SIII (which is running Android 4.3) because I wanted to put CyanogenMod on it. I followed this guide:
Step 1: Extract CF-Auto-Root and Odin 3.07 files using winrar/7zip/winzip or any other extracting tool.
Step 2: Switch off the Galaxy S3. Then boot the device into Download Mode by pressing and holding Volume Down, Home and Power buttons together until a construction Android robot icon with a warning triangle appears on screen. Now press the Volume Up button to enter Download Mode.
Step 3: Launch Odin on the computer as an Administrator.
Step 4: Connect the Galaxy S3 to the computer using USB cable while it is in the Download Mode. Wait until Odin detects the device. When the device is connected successfully, the ID: COM box will turn to light blue with the COM port number. Additionally, the successful connected will be indicated by a message saying Added.
Step 5: In Odin, click the PDA button and select the CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 file.
Step 6: Verify that Auto Reboot and F. Reset Time checkboxes are selected in Odin. Also, ensure the Re-Partition option is NOT selected.
Step 7: Double-check and click Start button in Odin. The installation process will now begin.
Step 8: Once the installation process is completed, your phone will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect your device from the computer.
There is only one thing I did differently than what the guide said was to install SuperSU before I did the root. The root completed successfully; however, SuperSU crashes whenever I try to launch it and KNOX puts a warning in my notifications tray. I never installed or launched KNOX prior to performing the root and I cannot update or remove SuperSU. I also cannot install or remove KNOX. I've been browsing forums and looking for answers but I can't understand half of the things people are saying. Does anyone have a noob-friendly solution? (By the looks of it, there are many people with similar issues due to KNOX.)
Thanks in advance.
I had been trying to figure out this same problem for days. Finally got it last night.
Just like you, I had been trying to use the CF autoroot method on my tmo s3 (4.3). Ran into the same "Unfortunately SuperSU has stopped." It seems as though CF autoroot and Knox don't play nicely. You might try using TWRP recovery instead of CF. I ended using the TWRP 2.5.0.0 to root via Odin. Success! Also, I was having troubles with my pc, so you might try to switching machines if you're still having trouble.
Here's a great guide on how to do this by @cLogic, who took @upndwn4par's method and refined it for T-Mobile. http://forum.xda-developers.com/showthread.php?t=2563955
Hope it helps!
I bought this device recently. Unfortunately it seems now that it's hard bricked. I've got the Hyperdrive rom installed and it used to work perfect. The problem started when the battery ran out while I were streaming live TV. Since then it wouldn't boot properly. It was stuck in bootloop, however I were still able to get it into recovery and download mode. I tried to recover from a backup through TWRP but did not succeed properly (the screen just froze after a couple of minutes). Afterwards it was really hard to make it do anything. It started to boot into something called "SDCARD MODE", with options to press the volume up key for normal reboot, and volume down for "download mode". But neither option worked.
I managed to get it into download mode and tried to reflash the original firmware for my device (P600ZHUCNH1) with Odin but it failed. When I rebooted the device the display showed the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I tried to flash the same firmware again with Odin but it failed again.
And since then I haven't managed to turn on the device. Holding Home button + Volume Up + Power or Volume Down + Power doesn't work. Battery is fully charged. Tried to reinstall battery. Tried a USB Jig. But no luck.
Any suggestions on what to do?
Thanks in advance!
@MikkelJakobsen
You have a solution to resolve that problem off yours.
Those 3rd screen image, tell that you need to use the Kies Software to restore your tablet to his own factory firmware.
Just follow this steps:
1. turn off your tablet, and go into "Download Mode"
2. start Kies3 Software in Windows, and go to the menu Tools -> Firmware Upgrade and Initialisation
3. Write the Model number off your tablet -> SM-P600
4. Then write the Serial Number (that on the backcover off the tablet).
5. Confirm all ok.
Then it starts to download the original firware files from the Samsung Servers. And it will flash the firmware.
And that's it. You should have after the tablet running smooth and 100% again!!!!
Best regards!
Flygye said:
@MikkelJakobsen
You have a solution to resolve that problem off yours.
Those 3rd screen image, tell that you need to use the Kies Software to restore your tablet to his own factory firmware.
Just follow this steps:
1. turn off your tablet, and go into "Download Mode"
2. start Kies3 Software in Windows, and go to the menu Tools -> Firmware Upgrade and Initialisation
3. Write the Model number off your tablet -> SM-P600
4. Then write the Serial Number (that on the backcover off the tablet).
5. Confirm all ok.
Then it starts to download the original firware files from the Samsung Servers. And it will flash the firmware.
And that's it. You should have after the tablet running smooth and 100% again!!!!
Best regards!
Click to expand...
Click to collapse
Thanks for your help! However, the problem is that I can't even turn on the tablet anymore. The screen just stays black no matter what I do. So I don't see the "Firmware upgrade encountered an issue" anymore and theremore Kies doesn't recognize any connected device.
Try do take off the back cover from the tablet, disconnect all the flex cables.
Remove the 13 screws from the batery holder, and then disconnect the battery cable's power.
Wait a few seconds, and then place all the parts on the tablet again.
And try to turn on the table again.
See if this helps.