Hello there,
I am trying to install CWM Recovery with Heimdall on my phone (GT-I9300) following the Cyanogenmod tutorial available on wiki.cyanogenmod.org/index.php?title=Install_CM_for_i9300
All went fine during the process to flash the phone with the recovery image, however when I start the phone using volume up, home button and power button simultaneously, it starts on the stock recovery software.
I am using Win 7 with heimdall and I followed exactly the steps described at wiki.cyanogenmod.org/index.php?title=Install_CM_for_i9300
I also did another try with a more recent image of CWM without anymore success. You will find attached the heimdall log in the cmd console.
As suggested in the tutorial I did not root my phone.
Did I miss a step to launch the CWM instead of the stock recovery tool or did I do something wrong ?
Thank you in advance for your help !
You need to boot into Download mode, not recovery. In the guide you linked to it says:
Boot the Galaxy S III into download mode by holding down Home & Volume Down & Power while connecting via USB.
Click to expand...
Click to collapse
Thank you for your response !
In fact I already did that step and I had no problem with it.
Sorry if I was no clear enough.
Here is what I have done exactly :
1) Download koush's ClockworkMod Recovery, and the Heimdall Suite (for windows)
2) Power off the Galaxy S III and connect the USB adapter to the computer but not to the Galaxy S III
3) Boot the Galaxy S III into download mode by holding down Home & Volume Down & Power while connecting via USB
4) Untar koush's ClockworkMod Recovery into the Heimdall directory
5) On the computer, open a terminal and run the following command from the Heimdall directory: heimdall flash --recovery recovery.img
7) A blue transfer bar will appear on the device showing the recovery being transferred. Once completed, the device will reboot automatically.
8) The Galaxy S III now has ClockworkMod Recovery installed. Continue to the next section.
So according to the tutorial ClockworkMod Recovery should be installed. But when I try to boot the phone using CWM, the phone boot in the stock recovery mode. Indeed in the recovery mode, at the top of the screen it is written "Android system recovery <3e>" instead of something like "ClockworkMod Recovery". Moreover in this recovery mode I do not have the option "Install zip from sdcard".
Sorry, I misunderstood you. Don't know the solution, wait for someone more qualified
Use Odin and flash the recovery.
Edit- Check this- http://forum.xda-developers.com/showthread.php?t=1695238
Ok thanks you it works.
I had to uninstall the driver installed by Heimdall for Odin to detect the phone. Except that all was ok.
However, it would have been great to be able to put CWM Recovery on the phone without rooting it !
ajdev said:
Ok thanks you it works.
I had to uninstall the driver installed by Heimdall for Odin to detect the phone. Except that all was ok.
However, it would have been great to be able to put CWM Recovery on the phone without rooting it !
Click to expand...
Click to collapse
You can do that by following this guide
http://forum.xda-developers.com/showthread.php?t=1719744
But why?
I didn't want to root the phone only because I don't need the root access!
Thank you for your link, I'll use it someday when I need to change the android rom of another device!
Related
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
Hi, i think i have a problem with the wrong kernel installed.
I have a SXSwith ICS and since a couple of days i tried to unlock the bootloader, put Doomlords CWM on it an root it, because i like to try another ROM.
I Unrooted it via the official way wich worked out good, the only thing strange was that i restarted and it seemed the whole phone was resetted.
Than i wanted to root and i had to put the phone in recovery mode, and i choose the doomlord CWM and flashed it using this guide
.
Xperia S
1.Download the Doomlord CWM Recovery image (download link here) and the Wi Fi Module for Doom Kernel (download link here) and place the same to the computer.
2.Go and rename the “S-DooMKernel-v01_kernel.elf” file into “kernel.elf”.
3.Copy the file renamed on the same folder with ADB / fastboot.
4.Take your phone and its USB cord and by using both connect it with the computer.
5.Copy-paste the “S-DooMKernel-v01-Modules.zip” file from the PC to the Xperia S SD card.
6.Disconnect the smartphone from the computer.
7.Reboot it by entering in fastboot; press the Volume Up button while connecting the phone with the PC.
8.On the computer open command prompt (Start -> run -> cmd) and enter the command: fastboot flash boot kernel.elf. If this isn’t working try with: fastboot -i 0x0fce flash boot kernel.elf.
9.The handset should reboot.
10.When you see the light turn blue hold the Voluem Up button. The Xperia S will enter in recovery mode.
11.In the recovery menu select “install zip from sd card” and pick the file copied there on step 3.
12.The installation procedure should begin. Don’t press anything as the process might take up to 10 minutes to complete.
13.In the end, from the recovery mode menu select “reboot system now” and you are done.
There you have it; that was the easiest and fastest way in which you can learn how to install Doomlord’s ClockworkMod Recovery on your Xperia S smartphone. Do tell us if there were problems on your way, of if you had issues in understanding one of my directions. Now you can go and update your Xperia S with the lasts ROMs available. Take a look and see if the
Everything seemed to be working but the phone is stuck in Doomlords bootloops.
If i hold the volume up than i can enter CWM but the phone doesn,t start anymore.
The phone was running on a stock ICS ROM (i believe the Swiss one)
I flashed this kernel, 2.6.35.11/Doomkernel.nr1 and SDoomkernel v01 Modules.zip
Who can help me out since i,m stuck here.
doomlord kernel is for GB since youre on ICS try KA Kernel, XSX Kernel, and the Advanced stock ICS. look in the development section. you can flash it in CWM since youve flash doomlord kernel or try to flash via fastboot.
Thanks for your quick response, how can i put the kernel on the internal sd?
the phone doesn't start, so it wont be recognised by windows, i tried to mount in CWM but windows doesn't see it.
If i flash in fastboot mode, do i have to change the name again and wich name if i take the KA kernel for example.
Thanks
koossmatrooz said:
Thanks for your quick response, how can i put the kernel on the internal sd?
the phone doesn't start, so it wont be recognised by windows, i tried to mount in CWM but windows doesn't see it.
If i flash in fastboot mode, do i have to change the name again and wich name if i take the KA kernel for example.
Thanks
Click to expand...
Click to collapse
Just downlaod the advanced stock kernel (the fastboot link) and flash it in fastboot
It will boot :good:
just download any of the 3 but u need the .elf file and then flash via fastboot you dont need to change the name just used the name youve downloaded to flash.
for example : ics14.elf
used fastboot or adb
fastboot flash boot ics14.elf
you can also used the flashtool, flash via fastmode then choose the ics firmware you have then flash only the kernel. uncheck everything except the kernel.
but the easy way to do is flash via fastboot mode.
I just tried using flashtool, everything goes fine exept it doesnt flash.
Downloaded the Stock "Swiss" ROM and tried to flash with flashtool, it recognised the device, because it says device connected, then it askes to unplug en plug in the device, which i've done then the pop up that tells to disconnect/connect the device stays on and nothing happens.
I'm getting a little worried now...
Thanks for your replie
hey you have working fastboot right or adb? flash a kernel like what ive said above using fastboot,
or you can try this, dont connect your phone to pc yet, make sure it is turn off (hold power button +power up wait till it vibrates 3 times.)
1. open flashtool
2. choose your firmware.
3. when it says unplugged your phone,connect your phone to pc then hold power button +volume up wait till it vibrates 3 times, then hold power button + volume down then release it will flash.
Thanks for all the replies, i got it working.
Seems that i turned my phone one in fastboot mode and not the flashmode...oops
Flashed the original Swiss ROM again and it works again, thankgod!
But i dont want the original anymore, can i just flash another available rom on the android dev section or do i need to root? Sorry for beeing such a noob.
yes you can just flash any custom kernel it will give you auto root, then u can start flashing rom via cwm. just follow the instructions in every rom.
I am having the same problem as I am stuck with DoomLord's boot loop. I tried to flash ICS stock rom but cant get to flash it. I tried holding the power button + volume up key(until i get the three vibration) and then hold power button + volume up key and release, I get the same DoomLord's boot loop again. I am using X10 Flashing Tool Version 0.8.0.0 Somebody please help me. The device can fast boot.
download the latest flashtool, then download ICS stock firmware of your choice on the general section, then flash it via flashmode. (power+volume down)
Hi guys, I'm in the process of installing CM 10.0.0 on my at&t galaxy note as per Quincyatt Info on Cyanogenmod wiki. I'm having trouble pushing the cm.zip onto my sdcard via adb. When I try to get into download mode in order to put zip with cyanogenmod on my sdcard I get a screen that says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The play by play is:
1) boot phone by holding Volume Down while plugging in microUSB.
2) Receive "Warning!! A custom OS can cause critical problems in phone and installed applications..."
3) press Volume Up to continue to download mode
4) screen goes to "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The steps I followed on the wiki:
1) Get and setup Heimdall Suite 1.4RC2
2) Flash ClockworkMod Recovery 6.0.3.1-quincyatt onto my phone
3) I powered off
PS when I try to "adb push cm-10.0.0-quincyatt.zip /sdcard/" I get "error: device not found," which I assume is because my phone, while plugged in, is not in download mode.
PPS When I try to go directly into CWM with volume up + volume down + lock/power it takes me to the "Firmware upgrade encountered an issue.."
i had this same issue about a month ago...
-
I booted my phone to this message: Warning!! A custom OS can cause critical problems in phone and installed applications...
Then plugged the usb cable to my phone and ran Odin.and flashed with pda.tar file
Then rebooted the phone and my phone was able to get to download mode.
dubsteps said:
i had this same issue about a month ago...
-
I booted my phone to this message: Warning!! A custom OS can cause critical problems in phone and installed applications...
Then plugged the usb cable to my phone and ran Odin.and flashed with pda.tar file
Then rebooted the phone and my phone was able to get to download mode.
Click to expand...
Click to collapse
Yep. Thanks!
For the record:
I used Odin to flash a stock I717 kernel (provided by da___g) and then proceeded with the cyanogenmod wiki's instructions. In order for my computer to see my phone so it could push files via adb I had to be in ClockWorkMod. My phone was non-functional (could only go into download/recovery mode and CWM) until I flashed CM10 with CWM.
Why push a zip file with adb? Just put it on your sd card by data cable or by mailing it to yourself or by download.
But then you have to be able to get into recovery. . .
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Damn ignore this wrong forum reposted in QandA
GoodKnight_IL said:
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Click to expand...
Click to collapse
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
palmbeach05 said:
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
Click to expand...
Click to collapse
Lol i realized not long ago updated my post in tbe q&a damn if you would have answered sooner would have saved me so much time.
Thanks for the reply though!