My SGS does not boot and does not enter recovery mode. I can enter download mode though. I suspect it happened after I removed some files from SD card.
Can I access SD card in download mode?
How can I use download mode to restore firmware and the recovery?
Thanks in advance.
u have to reflash your firmware. if u get only downloadmode working u can only reflash your device.
try a custom kernel first. if this wont work, then flash new firmware
Strange.from download mode you can only flash firmware.I think u can use adb and connect your phone to computer.try little search on topics don't rush first read carefully.
[email protected]
@malcho
adb wont work in download mode. only in cwm and after successful boot
So I understand I need to connect to PC in download mode and then use some software like ODIN to flash a ROM? Correct?
thats right.
may u can flash via kies, if u want a stock rom from samsung
I didn't know that info about adb.Thanks for info
[email protected]
Well, it's strange but looks better. Even before I did anything with ODIN the phone booted into the new ROM but I still cannot get into recovery. Seems like ROM installation procedure deleted something essential to run the recovery.
So now I have the download mode and Android working.
I am trying not to make any sudden moves so that I won't lose to ability to boot the ROM. What would be the best way to restore ClockworkMod recovery?
What ROM are you running now?
From a running stock-ROM the easiest way is to flash some custom kernel that includes CWM.
Here's a list http://forum.xda-developers.com/showthread.php?t=966646
For 2.2.1-based ROM I prefer Speedmod.
For 2.3.3-based, choose your own
edit: There are some ROMs/kernels that can only enter recovery when USB-debugging is on.
profalbert said:
What ROM are you running now?
Click to expand...
Click to collapse
I've just switched from Darky's 9.2 to PilotX with 2.6.35.7-I9000X[email protected]#Beta4.2_1 kernel.
From what you are saying I understand CWM recovery needs Linux kernel to run. I thought it's a stand alone boot-loader independent from the OS and kernel.
I installed CF-Root-XW_NEE_JVH-v3.2-CWM3RFS which comes with CWM recovery via ODIN with no effect. I still cannot reach recovery mode.
My phone came with 3e recovery which I downgraded to 2e (I don't remember how I did it then). Is it possible it has something to do with the problem?
You should always flash to stock when you have an issue.
You can also use Darky's resurrection (at least, part A: Pit with re-partition)
Then flash the original firmware (from samfirmware.com)
Thanks to everyone.
The problem was solved using http://www.v00d00.co.il/GBFINAL.pdf guide. Note, this guide is only relevant for Hebrew PilotX ROM.
Related
Hi
Maybe I didn't search very well but I have a question that seems very stupid...
With Odin, is it possible to flash a custom rom?
I mean the rom that i use normally flash with voodoo on the recovery mode can't bee found by odin...
Thing is that i've got the corrupted memory problem and acted to fast and flashed the stock 2.2 firmware from bell....now i'm stuck with 3e recovery...
If I could flash to a pre-rooted rom with CWM or Voodoo it would be better i thing if i want to try some manipulation with adb
Teranox said:
Hi
Maybe I didn't search very well but I have a question that seems very stupid...
With Odin, is it possible to flash a custom rom?
I mean the rom that i use normally flash with voodoo on the recovery mode can't bee found by odin...
Thing is that i've got the corrupted memory problem and acted to fast and flashed the stock 2.2 firmware from bell....now i'm stuck with 3e recovery...
If I could flash to a pre-rooted rom with CWM or Voodoo it would be better i thing if i want to try some manipulation with adb
Click to expand...
Click to collapse
I haven't confirmed this or searched but I think it's because you have voodoo enabled, this format is ext4 which is a linux format and can't be seen on windows unless you ahve some 3rd party software installed. Just boot into recovery and disable the voodoo, this will put your phone back to the normal format and odin should recognize it.....i'm totally guess here since i haven't tried it but I think this would be the cause
Darky's ROM is meant to be flashed via Clockwork recovery and can not be flashed by odin, darky's comes in a zip file and odin only uses .tar extensions
Hi guys,
i just got a Galaxy S (international, germany) and wanted to flash Clockwork Mod so i can flash a custom rom (miui). I got it with version 2.2 so i rooted it with z4root 1.3 and then tried RomManager to get CWM on it. But it did always reboot into Samsung stock recovery mode. So i tried this Odin3 1.7 and flashed a Kernel and got into a bootloop (First this one, then i used the one promoted in this video (YouTube Video, description XDA Thread with promoted Kernel. Phone now stuck at booting (isn`t even bootlooping, just stuck at the GALAXY S GT etc. logo. I still can reach the Download Mode.
Can anyone please help how to get at least the phone working again I`m really desperatly.
Greetings from Germany & Merry Christmas
Alch
Install a new Rom with odin will make your phone boot again.
2.2 is probably too old now.
Upgrade to Gingerbread Stock using Odin. Turn on Repartition and follow the instructions to flash.
Download a Custom Kernel for the Gingerbread firmware that you flashed. Every Kernel except the stock comes with CWM Recovery.
Copy the MIUI zip file to sdcard and flash it with recovery. It should boot right up.
If you are still having bootloops, try doing a factory reset and then boot MIUI.
Don't try things that you aren't experienced with.
Anyway, download odin 1.85, flash stock Froyo, launch Kies, update to official Gingerbread, launch Odin, flash Semaphore Kernel and GG.
Merry Christmas!
How can i flash Stock Froyo/Gingerbread trough Odin? Can`t find anything usefull @ google
btw i can reach Recovery Mode (CWM / Speedmonk something)
(Kinda experienced by flashing around with my N1 for around 2 years now, but never heard about this Odin Program)
thanks for help anyway
AlchemistEDW said:
How can i flash Stock Froyo trough Odin? Can`t find anything usefull @ google
(Kinda experienced by flashing around with my N1 for around 2 years now, but never heard about this Odin Program)
Click to expand...
Click to collapse
I am not going to help you with this one. You need to get comfortable with the forum and its contents first. Read all the guides and stickies before proceeding with Firmware flashing. There are many different types of firmwares with Bootloaders which are often dangerous to flash and few without bootloaders. Hence, first go through the guides and go with the flashing only when you are confident that you are doing everything in right order.
http://forum.xda-developers.com/showthread.php?t=1379853
Just do what dhiru1602 says. after you flashed it with the latest Gingerbread ,
flash the cf-root kernel with odin . than download the latest galaxian/semaphore kernel, copy it to your internal sd-card and flash it with the app SGS Kernel Flasher . you can find that app on the market. good luck mate !
Thanks guys, u really saved christmas for me Just booted up the latest Miui Rom!
Happy Holidays
Alch
Hi everyone,
I've a problem with my SGS.
I was trying to install my first custom rom on the stock android 2.3.6 - CM10 following the WIKI.
After I've installed as suggested Heimdall, I've tried to install hardcore's ClockworkMod Recovery but once I've typed the command "heimdall flash --kernel zImage" in the terminal window the phone starts booting up again and again in an infinite loop.
How can i fix the problem?
Thanks for helping
benjollo
benjollo said:
Hi everyone,
I've a problem with my SGS.
I was trying to install my first custom rom on the stock android 2.3.6 - CM10 following the WIKI.
After I've installed as suggested Heimdall, I've tried to install hardcore's ClockworkMod Recovery but once I've typed the command "heimdall flash --kernel zImage" in the terminal window the phone starts booting up again and again in an infinite loop.
How can i fix the problem?
Thanks for helping
benjollo
Click to expand...
Click to collapse
Do you use sgs or sgs+ ?
because i know more things about the sgs+
maybe solution: turn out the battery and then if you can get into recovery mode, flash a cwm recovery zip and an ICS or JB rom
if it doesn't help report back
Greets
It is a SGS.
I've noticed that I can get into ClockworkMod recovery with the 3-buttons combo and i can navigate in the menu or wipe cache and so on.
Is it possible that my problem is due to an wrong firmware? Maybe i should use the multiCSC version?
Where can I find the cwm recovery zip?
benjollo said:
It is a SGS.
I've noticed that I can get into ClockworkMod recovery with the 3-buttons combo and i can navigate in the menu or wipe cache and so on.
Is it possible that my problem is due to an wrong firmware? Maybe i should use the multiCSC version?
Where can I find the cwm recovery zip?
Click to expand...
Click to collapse
when you can get into clockworkmod recovery heimdall finished his job and you can flash cm10 but dont forget wipes
Sent from my GT-I9001 using xda premium
checkout
http://hdtechvideo.com/community/index.php?posts/1412/
Thanks everyone for help and hints!
I managed installing CM10 by reverting to stock firmware with Odin, then reflashing again CF with Odin and at the end installing latest CM10.1 successfully
The only thing I was missing in the first attempt was I haven't installed KIES on the pc (it is new) where i plugged the SGS (I thought that with heimdall i wasn't supposed to install kies) but in order to get Odin working i must install kies.
After kies installation, Odin successfully revert to stock firmware, than CF e than CM10.1
benjollo
First, I have a Captivate with 2.1 update1 stock Eclair and has 2e recovery. After trying countless times ( 2 buttons and diff combinations ), I am not able to get in download mode (the phone just reboot into OS) , so Odin and Heimdall methods cant be used; yet I can get into 2e recovery easily. So, I use the old method to flash CWM thru 2e recovery :
1) Do I have to upgrade to GB 2.3.5 rom and bootloader ? or just keep 2.1 and
2) From the temp CWM ,can I flash a permanent CWM over 2e recovery by using modded Corn kernel or so ? or can I just flash any custom ICS/JB ROM and its kernel has CWM recovery ?
abced123 said:
First, I have a Captivate with 2.1 update1 stock Eclair and has 2e recovery. After trying countless times ( 2 buttons and diff combinations ), I am not able to get in download mode (the phone just reboot into OS) , so Odin and Heimdall methods cant be used; yet I can get into 2e recovery easily. So, I use the old method to flash CWM thru 2e recovery :
1) Do I have to upgrade to GB 2.3.5 rom and bootloader ? or just keep 2.1 and
2) From the temp CWM ,can I flash a permanent CWM over 2e recovery by using modded Corn kernel or so ? or can I just flash any custom ICS/JB ROM and its kernel has CWM recovery ?
Click to expand...
Click to collapse
Here's a good start: http://forum.xda-developers.com/showthread.php?t=1350266
Now, as for your questions. 1- Yes, you will have to flash Odin KK4 with bootloaders. Those bootloaders are required to run GB and up.
2- You will have to flash Corn Kernel to get the recovery (cwm) to flash custom ROMs after flashing KK4.
As for your download mode problem, you can try a few different ways; usually it's vol down + power (phone has to be turned off) and don't release until it boots into download. Another option is to buy/make a jig, which will force your device into download mode.
That being said, know that you can get in download mode no matter what ROM/kernel and whatnot you run, recovery and download aren't affected by those.
now I have a new problem, I was able to get into download mode and used the 1click Odin uckk4 to flash. Yet, it failed twice. So, now the phone reboots into the white ATT screen then straight into the new 3e recovery with a lot of error " ccant find E partition , etc. " Help ! :laugh:
PS: I wanna add for whoever got the same mistake, do not use the one click Odin file ( with bootloader, partition, ROM, etc. ) Instead, just flash the BL alone, then the kernel as in the 2nd OP post ; then you ll have the permanent CWM recovery to flash other ROM . I downloaded SlimBean onto external SD card, how can I flash it ? the CWM does not let you pick the ROM from external SD card.
abced123 said:
now I have a new problem, I was able to get into download mode and used the 1click Odin uckk4 to flash. Yet, it failed twice. So, now the phone reboots into the white ATT screen then straight into the new 3e recovery with a lot of error " ccant find E partition , etc. " Help ! :laugh:
PS: I wanna add for whoever got the same mistake, do not use the one click Odin file ( with bootloader, partition, ROM, etc. ) Instead, just flash the BL alone, then the kernel as in the 2nd OP post ; then you ll have the permanent CWM recovery to flash other ROM . I downloaded SlimBean onto external SD card, how can I flash it ? the CWM does not let you pick the ROM from external SD card.
Click to expand...
Click to collapse
You should have a external sd folder when you hit ''install from sd''. See if it's there. Otherwise, mount your phone under recovery and move SlimBean in your internal.
i was on the Liquidsmooth rom, i wanted to go to FireKat.
i tried to go back to stock using Odin, using this tutorial http://forum.xda-developers.com/note-4-tmobile/development/guide-odin-to-stock-unrooted-firmware-t2957156 and in the middle of Odin doing its thing it failed.
now im stuck at "Firmware upgrade encountered an Issue. Please select recovery mode in Kies and try again."
so i downloaded Kies, and my phone isnt recognized.
what can i do so that i can at least get the phone working again?
Several options - first why did you not flash over recovery?
Second boot into recovery and reset.
Third if you can't get into recovery flash a custom recovery such as twrp and flash a new rom.
Hope this helps
johntuck77 said:
Several options - first why did you not flash over recovery?
Second boot into recovery and reset.
Third if you can't get into recovery flash a custom recovery such as twrp and flash a new rom.
Hope this helps
Click to expand...
Click to collapse
the instructions on the first page of the FireKat rom say to "1. Odin Flash Stock ANK4" so flashing via recovery is not a option.
i no longer have a recovery, during the Odin flash back to stock it failed and deleted my recovery. only thing i could boot into is DL mode.
i ended up having the wrong verison of Kies, had to use a older version. the phone was recognized and i "unbricked" the phone.
Meaning install a custom recovery and a different rom and you should be fine
ubber said:
the instructions on the first page of the FireKat rom say to "1. Odin Flash Stock ANK4" so flashing via recovery is not a option.
i no longer have a recovery, during the Odin flash back to stock it failed and deleted my recovery. only thing i could boot into is DL mode.
i ended up having the wrong verison of Kies, had to use a older version. the phone was recognized and i "unbricked" the phone.
Click to expand...
Click to collapse
The first step is just to make sure u r on the most current bootloader.
Can you boot the phone into download mode? If so you can flash recovery and a new ROM.
Sent from my SM-N910T using XDA Free mobile app
ubber said:
the instructions on the first page of the FireKat rom say to "1. Odin Flash Stock ANK4" so flashing via recovery is not a option.
i no longer have a recovery, during the Odin flash back to stock it failed and deleted my recovery. only thing i could boot into is DL mode.
i ended up having the wrong verison of Kies, had to use a older version. the phone was recognized and i "unbricked" the phone.
Click to expand...
Click to collapse
You should be using keis 3 anything else will fail. If you have download mode Odin back to stock with factory firmware. Tekhd has a step by step on how to root. Download firmware from sammobile and ur back to business. Pick your ROM careful.
BAD ASS NOTE 4 & GEAR S
Happened to me once, seems dumb enough, but change USB cable when flashing stock with odin. If you have access to download mode, you have not perma-bricked your device. Might help. Might not