Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......
Restore a nandroid.
RUU start over.
I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.
You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.
No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..
Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.
I managed to break the screen on my TMO Galaxy S2 last night. It doesn't display anything or register touch. Kies detects the phone but it won't access it because of the lock screen...which I can't unlock.
I've tried going into Recovery Mode, but I'm having trouble finding blind navigation guides for it. The one I found on the forum (for a different S2 model) instructs:
-> Get into recovery mode
-5x down
-enter
-2x up
-enter
Doesn't seem to work. It's for CWM, which I don't believe is installed any more (I was rooted at one point but something glitched and my phone started rebooting constantly, so I unrooted and flashed back to stock). I updated to ICS via Kies about a week ago.
The phone appears as an Unspecified device named SGH-T989 in Windows' device list when I'm in Recovery Mode. In normal mode, it appears with two drive letters, but I can't access either (presumably because I can't get it into USB mode).
Is there a way to bypass the lock screen and access my phone in Kies, or can someone else with a stock phone walk me through the recovery mode menu to mount the internal SD card?
Edited--Nevermind. A friend pointed me to ADB, and after reading a bit, I was able to use 'adb pull /sdcard/ backup' and get all my data while it's connected to USB, right through the lockscreen that stops kies.
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!
Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt
[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.
Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.
As the subject line says, I'm worried I bricked my Tab S. Awhile back I flashed my tablet to IronRom. I hadn't used it in awhile and this morning I attempted to update via OTA Updater. I was able to download the update and reboot into TWRP for the install, but the tablet froze while I was wiping the cache and I had to restart. I was able to reboot into TWRP and installed the ROM (without erasing cache or data) but now I can only boot as far as the "Galaxy Tab S" screen. I can no longer boot into TWRP, though I can boot into Download Mode, but my computer won't recognize the tablet. Is there anything I can do or am I screwed?
Edit -- My computer recognizes the tablet when I open Kies, but it tries connecting for a few minutes then times out.
CarQuery8989 said:
As the subject line says, I'm worried I bricked my Tab S. Awhile back I flashed my tablet to IronRom. I hadn't used it in awhile and this morning I attempted to update via OTA Updater. I was able to download the update and reboot into TWRP for the install, but the tablet froze while I was wiping the cache and I had to restart. I was able to reboot into TWRP and installed the ROM (without erasing cache or data) but now I can only boot as far as the "Galaxy Tab S" screen. I can no longer boot into TWRP, though I can boot into Download Mode, but my computer won't recognize the tablet. Is there anything I can do or am I screwed?
Edit -- My computer recognizes the tablet when I open Kies, but it tries connecting for a few minutes then times out.
Click to expand...
Click to collapse
Reflash tarp through Odin and then try to reboot recovery. I have my Tab S 10.5 LATE on that same room, no problems.
If your computer can't recognize your tablet in the Odin program, try using another USB cord.