Related
I've tried everything that I possibly can, in order to implement ChainFire's kernel via Odin to root my Samsung Galaxy S, but it doesn't matter what I do - Odin gets stuck at Setup Connection for me. (both on Windows 7 [32 bit] and Windows XP)
I've tried asking this question several times in relevant threads, and so far have not received any replies. Hence, I'm forced to make this thread.
I just want to know if there exists an alternate method to root my phone AND replace stock 3e recovery with 2e recovery? While I can root my phone using the SuperOneClick method, I can't seem to install 2e recovery on my phone and therefore no ClockWorkRecovery Mod for me either.
Can anyone in here, please help me with this ordeal?
the answer is simple: just use odin to flash any mod kernal from this forum, like SpeedMode
kursed said:
I've tried everything that I possibly can, in order to implement ChainFire's kernel via Odin to root my Samsung Galaxy S, but it doesn't matter what I do - Odin gets stuck at Setup Connection for me. (both on Windows 7 [32 bit] and Windows XP)
I've tried asking this question several times in relevant threads, and so far have not received any replies. Hence, I'm forced to make this thread.
I just want to know if there exists an alternate method to root my phone AND replace stock 3e recovery with 2e recovery? While I can root my phone using the SuperOneClick method, I can't seem to install 2e recovery on my phone and therefore no ClockWorkRecovery Mod for me either.
Can anyone in here, please help me with this ordeal?
Click to expand...
Click to collapse
Which version of Odin are you using? Have you tried Odin v1.7?
ragin said:
Which version of Odin are you using? Have you tried Odin v1.7?
Click to expand...
Click to collapse
You can also try z4root found in this forum.
I've tried using both 1.3 and 1.7 versions of Odin. And facing the exact same issue; it doesn't go beyond 'Setup Connection' for me, when flashing the kernel.
I've already tried and tested all combinations and permutations of USB cable in / USB cable out / Battery out / SIM out / Odin running with Admin rights / Different USB slots etc etc. Didn't do anything for me.
Let me reiterate myself, rooting alone is the least of my problems. I need to install 2e version of recovery (and hence be able to install ClockWorkMod in order to be able to install 3rd party ROMs). I can't seem to get that done, via ChainFire's method.
I've managed to root my phone via SuperOneClick method, but the issue of 2e recovery remains. So I can't use that method either.
What exactly are you having a problem with? Can you get your phone to connect to Odin but the download won't progress or can't you get your phone to connect to Odin??
My phone shows up in Odin just fine (Com: 14), but once I click 'Start', the entire process stops at:
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
Nothing happens beyond this point. And my phone isn't flashed or affected in any way either.
Are you sure you have all the appropriate drivers?
I had that problem earlier on .. and I believe once I got the Samsung USB drivers from Softpedia it was a wrap.
Odin started working properly.
edit: also check which PIT file you're using. People recommend 512 but the 802 is the one that works for my phone.
KIES identifies the phone just fine. I've already tried removing the drivers and re-installing them automatically via Windows Update - KIES works again, but this issue remains.
I've also removed KIES (even from the status bar area), before starting Odin, so that's not a problem either.
i think you have no problem with odin, but with usb drivers.
without usb connect you have a problem i think. even for redbend_ua u need a usb connect to use adb shell.
http://forum.xda-developers.com/showthread.php?t=773913
dont know if u can use redbend in terminal emulator just local?! we have to ask an expert or just try it
another option is to use a linux box and heimdall. never had any problems with the usb drivers there
kursed said:
KIES identifies the phone just fine. I've already tried removing the drivers and re-installing them automatically via Windows Update - KIES works again, but this issue remains.
I've also removed KIES (even from the status bar area), before starting Odin, so that's not a problem either.
Click to expand...
Click to collapse
ah ok..than try to work with adb and redbend_ua
Use Heimdall, I'm yet to hear of a single instance of Heimdall 1.0.0 failing.
Any link to how can I use Heimdall? Is it possible on a Mac?
Heimdall XDA Thread
Official Heimdall Page
The README includes usage instructions.
Heimdall will run on a Mac as long as you have the updated bootloader provided by Samsung. It was only included in official Froyo releases so you must already be running Froyo for it to work on a Mac. Unfortunately there is no work around if you don't have the bootloader, even a Windows virtual machine running on a OS X will not be able to connect to the phone.
However Heimdall will work fine with any Galaxy S on Linux and Windows (i.e. no updated bootloader required).
If you find Heimdall useful donations are very much appreciated
recovery 2e can be installed on your device fairly easily, as long as it is rooted. Any root method works.
Once rooted, just copy the recovery 2e binary and replace the 3e binary in /system. There are some guides here on this forum on how to do it. I believe simply replacing /system/res/keys with AOSP should be enough for recovery 3e to work properly too...
Finally, I got it working, still using Odin. Thanks for everyone's help. Really really appreciate it.
I have the same problem - could you briefly describe how you got it working with Odin? Thanks!
First of all make sure that you're entering download mode and not recovery mode, before connecting to Odin.
That means pressing (home+power+down-volume key). Secondly, download KIES and and attach your phone with it first in a normal mode and later when in download mode (without turning Odin on).
Thanks a lot, worked!
Benjamin Dobell said:
Heimdall XDA Thread
Official Heimdall Page
The README includes usage instructions.
Heimdall will run on a Mac as long as you have the updated bootloader provided by Samsung. It was only included in official Froyo releases so you must already be running Froyo for it to work on a Mac. Unfortunately there is no work around if you don't have the bootloader, even a Windows virtual machine running on a OS X will not be able to connect to the phone.
However Heimdall will work fine with any Galaxy S on Linux and Windows (i.e. no updated bootloader required).
If you find Heimdall useful donations are very much appreciated
Click to expand...
Click to collapse
Heimdall does not recognize my Epic and I can't get Odin to work. I'm in limbo now as phone will only go to download mode.
There should be a [NOOB] tag for forum posts...
I'm a long time windows mobile user, rather than jump into windows phone I'm making the switch to Android.
I bought my captivate on eBay, it shipped unlocked with a clean gingerbread rom. Not sure which. After reading through a number of threads and articles I was able to:
Setup ADB - Win7 x64
ADB to download mode, Odin 1-click back to stock
Flash CWM, again via ADB to recovery, and then flash the latest MIUI
3br does not seem to be working for me. At first I was able to get to recovery with Vol up + Home + plug into USB. I can no longer get to recovery or download mode at all. MIUI, has the reboot to Download/Recovery mode options, but neither work and just boot back to the OS. When plugged into my computer, the device drivers are not recognized. So it no longer works with ADB. I haven't been able to get the drivers re-installed. When I attempt to ADB, it says "Error: No device connected" (or along that wording). I tried installing the USB drivers straight from Samsung and the galaxy S x64 drivers posted online. Not having any luck.
I can't seem to find my answer searching the threads and web...maybe I'm not using the right terms (I avoided making a new post as long as I could). Everything else works fine otherwise, the phone isn't bricked...but where's the recovery? Any ideas?
I'm assuming if I can get into download mode, then I can Odin-1-click to stock and everything is peachy again? I'm not quite understanding the 3BR fix guides...I thought since I could get to recovery with other methods when I got the phone, that I was fine, but maybe that's my problem.
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
studacris said:
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
Click to expand...
Click to collapse
It must have gotten disabled somehow then...
By Google drivers, you mean the USB package you can select from the Android SDK Manager? I didn't mention this but I think I tried those as well. But I'll remove everything I've installed, restart and try re-installing fresh to double-check.
Thanks for the suggestion, that worked with the drivers from the sdk. So if I end up flashing a touchwiz based rom, will I have to go back to the samsung drivers?
That's correct
Recently i rooted my Samsung Galaxy Tab(SGT) GT-p1000 that was brought from Singapore using the oneclickroot method.
My problem began when i heard about using heimdall to flash custom ROMS on the SGT. So i downloaded the Heimdall files and used heimdall frontend to attempt to root my SGT. Before that i had already used the zadig files to install the samsung composite USB driver. However as i boot my SGT into download mood, i accidentally pressed start to flash into my SGT with only the zimage and a wrongly selected Factoryfs file, These were taken from the BOCA rom I wanted to try to install.
Then i think i went into Boca's bootloader but i couldnt do anything. So i tried to reboot the device but it couldnt boot anymore. Just showed and android with an Exclamation mark. So i saw this thread http://forum.xda-developers.com/showthread.php?t=966015 and i thought that maybe i could use heimdall to flash back the default files. So i reflashed the new FactoryFS Zimage and Param.ifs provided by this new rom.
Now i can boot the phone normally into froyo 2.21, however now everytime i press the lock button the phone retarts. And everytime i try to connect to the internet using WiFi my phone restarts as well. 3g no longer works too. T_T
I can no longer connect to Kies and i tried reinstalling the drivers again but nothing would fix it. I cant use Heimdall or Odin to flash it anymore, Heimdall faced error -12 and Odin just kept trying to secure connection, but it never passes that point.
IM REALLY LOST AS TO WHAT TO DO. SOMEBODY HELP ME!!! PLEASE!
ADB
1-char
dirlan2001 said:
ADB
1-char
Click to expand...
Click to collapse
I don´t think this can help.
I think your problem is that you installed a incorrect rom for your tab model.
Download this:
http://overcome.mimzo.com/p1000/downloads/GB-Stock-Safe-v5.zip
Reinstall samsung drivers.
and flash the file using odin, repartition checked.
rafaeker19 said:
I don´t think this can help.
I think your problem is that you installed a incorrect rom for your tab model.
Download this:
http://overcome.mimzo.com/p1000/downloads/GB-Stock-Safe-v5.zip
Reinstall samsung drivers.
and flash the file using odin, repartition checked.
Click to expand...
Click to collapse
Hmmm... Odin doesn't get connected , so ....
Probably Heimdall will also do the flash for you - Odin is just one Windows-based tool to flash that device. Heimdall should have the same features for differnt platforms (so you can use it also on MAC OSX and Linux)- give Overcome a trial - and don't forget to flash the modem, if you want a fully working device
I've been searching XDA & Google for about 1 month but can't find a solution. I don't know why everywhere in some threads whenever somebody asks the same problem there's no reply to that question. So I decided to post this question here to try my luck...
Problem & History:
I tried to root my Samsung Galaxy Tab GT-P1000R with DoonLord V_4, it couldn't root it but left the tab with touch problem then I tried to root it with famaroot various versions, I then again tried to root it with z4root V_1.3.0, all attempts were useless, I don't know which attempt of them, made my tab unable to connect to pc even in download mode.
When I set my tab to connect to Kies or Media it shows that it's connected but PC doesn't detect it. Please help...
Tab Specification:
Samsung Galaxy Tab GT-P1000 (Rogers)
Firmware Version: GB 2.3.6
Baseband Version: P1000XXJR2
Kernel Version: 2.6.35.7 ([email protected] #2
Build Number: GINGERBREAD.XXJU2
Hi adilpal, go to the first post here http://forum.xda-developers.com/showthread.php?t=1881981
Thanks!
mr.natural said:
Hi adilpal, go to the first post here http://forum.xda-developers.com/showthread.php?t=1881981
Click to expand...
Click to collapse
Thanks for your reply but I have already gone through this post but as I mentioned problem is that PC doesn't detects it even when I put the Tab in DL mode. Is there any method to root it? So that I could use Mobile Odin to restock it.
It is an usb-driver problem and not rooting, I'm 99% sure of it. It's the PC that HAS to find the Tab first.
Hmmmm
mr.natural said:
It is an usb-driver problem and not rooting, I'm 99% sure of it. It's the PC that HAS to find the Tab first.
Click to expand...
Click to collapse
I've tried on another PC and with another USB cable but in vain. Other Smartphones connect it without any problem.
Any smartphone or the P1000 are not the same. I have had on multiple occasions that even Samsung Kies did not recognise it and had to reinstall Kies. Same for the Samsung Mobile phones drivers. And don't forget to reboot your PC after installing drivers.
Keep on trying because it is still going into download mode and logic tells it should be accessible. Does the PC give a notification like driver not found or similar?
NO.
mr.natural said:
Any smartphone or the P1000 are not the same. I have had on multiple occasions that even Samsung Kies did not recognise it and had to reinstall Kies. Same for the Samsung Mobile phones drivers. And don't forget to reboot your PC after installing drivers.
Keep on trying because it is still going into download mode and logic tells it should be accessible. Does the PC give a notification like driver not found or similar?
Click to expand...
Click to collapse
No. There's no activity in PC when I connect it. It neither shows new hardware found nor any other notification like unrecognized device etc.
BTW I have reinstalled Kies, updated it, uninstalled it, installed separate drivers for Samsung USB but no gain...
One last option, let the battery become completely empty (0% charge). Recharge and try again, it rescued my tab once after a bad flash.
That is to my knowledge the last resort.
Alas!
mr.natural said:
One last option, let the battery become completely empty (0% charge). Recharge and try again, it rescued my tab once after a bad flash.
That is to my knowledge the last resort.
Click to expand...
Click to collapse
It didn't help...
adilpal said:
It didn't help...
Click to expand...
Click to collapse
What version of windows are you on? Because windows 8 is a *****, Vista or 7 should work.
(Or GNU-Linux). And have you tried Heimdall already? http://forum.xda-developers.com/showthread.php?t=1323527
Heimdall download https://code.google.com/p/heimdall-one-click/downloads/list
Get a stock ROM and how to use Heimdall (these are old instructions so there could be newer versions available).
-----------Heimdall install instructions ------------------
1. Download Heimdall.
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. Download it here List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
-----------How to use Heimdall-------------------------
1. Put your tab into download mode - Power off Tab, once powered down hold power and the volume down button at the same time. You will see a android digging.
2. Start Heimdall
3. Hook your tab up to your PC or MAC and you will see a progress bar. That must say Ready to get heimdall to work.
4. Find you Firmware and unzip it until you see the following files below.
(NOTE: when you first unzip your firmware it may unzip into a .tar file unzip the .tar file to get the files below.)
a. Zimage
b. FactoryFS.rfs
c. Param.lfs
d. Boot.bin
e. SBL.bin - not always included
f. cacher.rfs
g. dbdata
h. modem.bin - not always included
5. Place each of those files in their correct spot and hit start.
ONE BIG NOTE: if you use a PIT file do NOT select repartition. It might brick your tab as heimdall has a problem when selecting repartition w/ a pit file. It is ok to use the pit file just make sure repartition is unchecked.
(Use ODIN for repartition with pit)
Got it working...
Thanks buddy, I bought a half dozen of USB cables for the tab and got it working with one of them at last... I don't know but I thought it was the last way out to try different cables... And at last, I got it working after long...
Please let me know the correct way of rooting, as DoomLord v. 4 has already failed to root it. Please guide if possible... I have a Ragers (Canada) Tab. GT-P1000R
Okay so i did something dumb and I'm wondering if there is a way out. I just got my second Note 5 because I dropped my first one and the screen went black. It was gonna be cheaper and easier to just buy a new device than actually repairing all the damage.
I installed TWRP through Odin. Stupidly, I did a complete wipe, including internal storage, and now I can't get the device to see the USB/OTG. I have a new cable on the way that's going to get here tomorrow. I can't think of what else it could be? Any ideas would be much appreciated. It doesn't have an OS so I'm thinking I may have wasted 250$.
It's not turbo charging either so could It be the charging port that's causing it to not be picking up the OTG?
Does Odin recognize it at least in download mode?
Have you tried mount on as usb in twrp?
press install>select storage then there will be two option
Internal storage and USB storage. Click on USB and the value will change from 0 to the amount of gb your otg have,then you can flash via otg
CoontDunker23 said:
Okay so i did something dumb and I'm wondering if there is a way out. I just got my second Note 5 because I dropped my first one and the screen went black. It was gonna be cheaper and easier to just buy a new device than actually repairing all the damage.
I installed TWRP through Odin. Stupidly, I did a complete wipe, including internal storage, and now I can't get the device to see the USB/OTG. I have a new cable on the way that's going to get here tomorrow. I can't think of what else it could be? Any ideas would be much appreciated. It doesn't have an OS so I'm thinking I may have wasted 250$.
It's not turbo charging either so could It be the charging port that's causing it to not be picking up the OTG?
Click to expand...
Click to collapse
You need to flash latest stock 6.0.1 firmware on your device using Follow the steps
1)Go to link provided to download latest 6.0.1 firmware for your device model no and country( You can find device model no and country printed on authorised box or below on the back panel of your device like SM-N920C/G/I, Country code you can find on box like INS,SL,UK)
https://www.sammobile.com/firmwares/
2) Download latest odin from google and latest Samsung usb drivers from your device( Copy them on your pc and extract to specific folders, install Samsung usb drivers on pc)
3)Power off your device, now press volume down+home+power button simultaneously, you will now boot into download mode. Press volume up button to continue)
4) Run previously extracted odin.exe on your pc as administrator
5) Connect your phone using original Samsung usb cable, now let pc to install usb drivers for your device..After drivers being successfully installed, you can see your device is added to odin as COM PORT
6)In odin options tab, make sure only auto reset and reboot options selected..Dont select reset partitions from odin..
7)Now add previously extracted firmware in AP tab of odin( In extracted firmware folder, file is named as tar.md5)
8)Give it some time to b ready and now press start button,now flashing is started..Wait untill flashing process being completed..
9) After flashing complete your phone will be reboot automatically..if you stuck at Samsung logo for long time, press volume down+power button..Your phone will be switched off, now immediately press volume up+power+home button simultaneously untill you see Samsung galaxy note 5 logo
10) Now you will boot into stock recovery, from there select wipe data/ factory reset option..After reset reboot your device..Your problem will be solved..
REMEMBER TO DOWNLOAD LATEST STOCK 6.0.1 FOR YOUR DEVICE
Great, I'll try to do that later today. Thanks a lot!
DroidHackeR said:
You need to flash latest stock 6.0.1 firmware on your device using Follow the steps
1)Go to link provided to download latest 6.0.1 firmware for your device model no and country( You can find device model no and country printed on authorised box or below on the back panel of your device like SM-N920C/G/I, Country code you can find on box like INS,SL,UK)
https://www.sammobile.com/firmwares/
2) Download latest odin from google and latest Samsung usb drivers from your device( Copy them on your pc and extract to specific folders, install Samsung usb drivers on pc)
3)Power off your device, now press volume down+home+power button simultaneously, you will now boot into download mode. Press volume up button to continue)
4) Run previously extracted odin.exe on your pc as administrator
5) Connect your phone using original Samsung usb cable, now let pc to install usb drivers for your device..After drivers being successfully installed, you can see your device is added to odin as COM PORT
6)In odin options tab, make sure only auto reset and reboot options selected..Dont select reset partitions from odin..
7)Now add previously extracted firmware in AP tab of odin( In extracted firmware folder, file is named as tar.md5)
8)Give it some time to b ready and now press start button,now flashing is started..Wait untill flashing process being completed..
9) After flashing complete your phone will be reboot automatically..if you stuck at Samsung logo for long time, press volume down+power button..Your phone will be switched off, now immediately press volume up+power+home button simultaneously untill you see Samsung galaxy note 5 logo
10) Now you will boot into stock recovery, from there select wipe data/ factory reset option..After reset reboot your device..Your problem will be solved..
REMEMBER TO DOWNLOAD LATEST STOCK 6.0.1 FOR YOUR DEVICE
Click to expand...
Click to collapse
AndiValon said:
Have you tried mount on as usb in twrp?
press install>select storage then there will be two option
Internal storage and USB storage. Click on USB and the value will change from 0 to the amount of gb your otg have,then you can flash via otg
Click to expand...
Click to collapse
I tried to mount it in TWRP but the box is uncheckable. That is my problem. I go to install and under the select storage I cant select USB OTG and it says (0MB). I'm kinda perplexed. Thanks for the advice though!
DroidHackeR said:
You need to flash latest stock 6.0.1 firmware on your device using Follow the steps
1)Go to link provided to download latest 6.0.1 firmware for your device model no and country( You can find device model no and country printed on authorised box or below on the back panel of your device like SM-N920C/G/I, Country code you can find on box like INS,SL,UK)
2) Download latest odin from google and latest Samsung usb drivers from your device( Copy them on your pc and extract to specific folders, install Samsung usb drivers on pc)
3)Power off your device, now press volume down+home+power button simultaneously, you will now boot into download mode. Press volume up button to continue)
4) Run previously extracted odin.exe on your pc as administrator
5) Connect your phone using original Samsung usb cable, now let pc to install usb drivers for your device..After drivers being successfully installed, you can see your device is added to odin as COM PORT
6)In odin options tab, make sure only auto reset and reboot options selected..Dont select reset partitions from odin..
7)Now add previously extracted firmware in AP tab of odin( In extracted firmware folder, file is named as tar.md5)
8)Give it some time to b ready and now press start button,now flashing is started..Wait untill flashing process being completed..
9) After flashing complete your phone will be reboot automatically..if you stuck at Samsung logo for long time, press volume down+power button..Your phone will be switched off, now immediately press volume up+power+home button simultaneously untill you see Samsung galaxy note 5 logo
10) Now you will boot into stock recovery, from there select wipe data/ factory reset option..After reset reboot your device..Your problem will be solved..
REMEMBER TO DOWNLOAD LATEST STOCK 6.0.1 FOR YOUR DEVICE
Click to expand...
Click to collapse
I'll just do that and start over. Thanks for the advice!
Jdkrosen said:
Does Odin recognize it at least in download mode?
Click to expand...
Click to collapse
I'm not sure. How can I tell?
CoontDunker23 said:
I'm not sure. How can I tell?
Click to expand...
Click to collapse
Step 3 from the other guy's post above you. That's what I was gonna help you with because you wiped the internal storage. Odin will still recognize it but in Download mode and she won't work again unless you flash the stock firmware specifically for your phone from the link above.
Fixed
I reOdined and same problem so I went back and looked at the instructions. I saw that you had to have MM flashed onto the device so I tried that and it worked. I just figured updating the phone would give me enough but it didn't. Thanks for all the help guys!