Database Info

Stuck on Odin??? HELP

Wanted to install 2.3.6 and Cranium RC4.
Have it done like the instruction from fabsau, after that i got the Bootloop.
Now its not possible to flash any rom.
Have tried 3 PCs with all their USB Ports and 2 Cables.
When Iam in the download mode and want to flash via Odin it stuck like that on every firmware(2.3.4,2.3.6,..).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After 5min nothing happens
Who can help
Thank you
olli

try using different usb port..
or enter download mode manually
(volume down+menu+power button instead of rebootdownload.bat)

Unplug USB cable.
Go to download mod again (push Volume down + Home + Power for 10 sec)
Close Odin
start again Odin
and try again.
Don't forget pit file if u cheeked rePartition ;-)
Use Odin 1.7

nothing worked, I allready go manually in DL Mod, nothing else is possible.
Odin 1.70 wont flash, shows failure 1
WTF whats up with my Phone

Dose Odin 1.7 detect phone ?

Masterolli said:
nothing worked, I allready go manually in DL Mod, nothing else is possible.
Odin 1.70 wont flash, shows failure 1
WTF whats up with my Phone
Click to expand...
Click to collapse
ermmm..strange...
its happen to me when i'm using rebootdownload.bat..
but its solve with manual download mode..
anybody has another solution??

Masterolli said:
nothing worked, I allready go manually in DL Mod, nothing else is possible.
Odin 1.70 wont flash, shows failure 1
WTF whats up with my Phone
Click to expand...
Click to collapse
Dont panic as long as you get the tringle yellow sign it can work. do as i mention exactly.
1- remove battery, after 1 min put it back.
2- on your phone and you will see the yellow triangle.
3- open odin 4.43 in your computer and set the files as on pic. you have to flash xxpk4.
4 - connect your phone while it is on with the yellow tringle.
5- odin will map your phone, it will show mapping port in yellow.
6- hit start and wait DONT panic, but wait till it finish.
If you need files you can download from here : http://forum.xda-developers.com/showthread.php?t=1346245

1.ok
2.hav to start manually, when i do nothing it boots to animation and reboot (Bootloop)
2.1 I can enter Download mode like this
Theres no triangle.
I have tried 2.3.6, 2.3.4 rooted like in your pic.
Odin detects my Phone on Comport but still stucks, see first post.

Take out your battery for a while. Rly like 5 min at least. If you have another USB cable, try with that. Also try reinstalling/updating the usb drivers. LINK TO DRIVERSsamsung-mobile-phone-usb-driver-software.updatestar.com/

Masterolli said:
1.ok
2.hav to start manually, when i do nothing it boots to animation and reboot (Bootloop)
2.1 I can enter Download mode like this
Theres no triangle.
I have tried 2.3.6, 2.3.4 rooted like in your pic.
Odin detects my Phone on Comport but still stucks, see first post.
Click to expand...
Click to collapse
good its ok, just flash with xxkp4 like in the pic i show you.

Battery was out for hours, allready have reinstalled usb drivers.
Have tried to flash like on your pic.
Damn it wont flash...
The last two options are build Jig USB Cable (dont know why because i can reach download mode) and when this wont work, I have to bring it back to the shop i have bought :-(

i got some problem howver i manage to overcome tht problem...
1.connect ur USB to your phone & make sure all file being set in Odin for flashing (make sure all file put in destop)
2.put ur phone in manual download mode (press lower volume button+homebutton+on button together)
3.i believe odin can should detect ur phone, then press start.
4.if the odin stuck at same place then off your phone pressing on button (dont remove ur usb cable) & follow step 2 & 3
5.try continue untill it flash.
i've try 4time until i can flashing my phone, hope it can help you too coz ur problem excatly same with mine (cant flash any rom)

hi,
thanks napie fo advice.
Somethimg new happend, when it stucks, i switched it of manually while it was connected, 1 sec before the Phone goes off it starts to flash.
But the problem is, that this happens when the Phone is shuting down, cant stop the procedure.
So it fails.
Its the same with the 2.3.4 firmware!!!
Look at the screenshot...
**** it also shows the same when I unplug while flashing procedure :-((

seem ur usb port got problem...try use another usb port maybe it can be fixed...also please put ur flash file direct in ur destop instead inside other folder name....otherwise use my previous instruction it can be use when ur phone stuck in odin
download file for 2.3.4
http://forum.xda-developers.com/showpost.php?p=17516475&postcount=1
how file to put in odin
http://forum.xda-developers.com/showpost.php?p=17642341&postcount=38

Masterolli said:
hi,
thanks napie fo advice.
Somethimg new happend, when it stucks, i switched it of manually while it was connected, 1 sec before the Phone goes off it starts to flash.
But the problem is, that this happens when the Phone is shuting down, cant stop the procedure.
So it fails.
Its the same with the 2.3.4 firmware!!!
Look at the screenshot...
**** it also shows the same when I unplug while flashing procedure :-((
Click to expand...
Click to collapse
You have to tick one package option then it will work...try it again

mbba67 said:
You have to tick one package option then it will work...try it again
Click to expand...
Click to collapse
But do you explain why XXKP4 didnt install?

@napie I know how to use odin, i have flashed 2.3.4 [email protected] 2.3.6 its not my ability that causes this problems.
I have tried on 3 Computers and 15 different USB ports, its not the USB port.
It makes no difference if the files are direct on the desktop or not, have tried it.
@ mbba67
I know when to select the one pack file, i have flashed several CMW and Kernel.
When its not seleceted it means I will not flash the file. ;-)
I have tried xxxx different combinations.
Maybe i have to accept that its broken :-(

mikeeo019 said:
But do you explain why XXKP4 didnt install?
Click to expand...
Click to collapse
Explaining is not the answer because i think you cant explain why others can flash Cranium RC 4 and others cant since they all doing them same way of flashing
The only way is trying all possiable way untill it comes right....it can be e.g. usb cable, corrupted files, drivers etc......

mbba67 said:
Explaining is not the answer because i think you cant explain why others can flash Cranium RC 4 and others cant since they all doing them same way of flashing
The only way is trying all possiable way untill it comes right....it can be e.g. usb cable, corrupted files, drivers etc......
Click to expand...
Click to collapse
What i meant was that if the problem was that the 'one package' wasn't ticked then it should have worked with xxkp4 as well.

Its now ****ing flashing and it works.
Its the way like napie said with one difference.
(4.if the odin stuck at same place then off your phone pressing on button (dont remove ur usb cable) & follow step 2 & 3)
When it stucks, i switched manually off, then i switched on and the Battery logo appeared.
Now I have pressed the Buttons for download mode there was no Samsung logo.
Strange but works so going on with flashing Cranium RC 4 ^^
Flashed CWM same way, have to go every time this way by flashing wit odin
Thanks to all

[CWM] Clockworkmod Recovery for the Samsung Blaze 4G

Shabbypenguin presents...
Clockworkmod Recovery 6.0.5.0 for Blaze 4G
Sponsored by Shabbypenguin.com. Have you tipped your devs today?
DO NOT CHECK REPARTITION! YOU HAVE BEEN WARNED!​
Why the big red warning? Far too many people have broken their devices by not following these instructions! Search the forums, or drop by IRC - you'll see plenty of examples.
So the T-Mobile CWM worked... well sorta you couldnt see anything, so i fixed it up and made sure it worked fine for yall enjoy
Instructions​
Download Odin 1.85 - see section below.
Download the Clockworkmod recovery TAR - see section below.
Extract the contents of odin-185.zip.
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded.
Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down + Power.
You should now be at Download Mode.
Click Start in Odin.
If you are having issues getting into download mode check out these instructions
That's it! Your device will autoreboot, and your phone should be working properly again.
Downloads​
Download Odin 1.85
CWM Touch 6.0.5.0
​
Credits:​
​
DrTaru: stock device, remote access, lots of testing, screenshots, patience
k0nane: k0nane for being an awesome sauce kind of guy
JFigure/Watcher64: initial testing and pointers/proof of concept
UberPinguin: notes on building kernels for celox, which also apply to this device
SOURCE
If you feel as though my work is worth your money, you can click the link in my signature to donate to me ​

second'dddddd

P-O-S-T :: R-E-S-E-R-V-E-D
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0!​

Okay.
Im having issues.
I have a T-Mobile Samsung Blaze4G
Followed every step to the T.
When I do Vol up+ Vol dwn+ PWR
i come to a recovery screen and at the bottom it says Manual mode.
I dont see anything that says "Download Mode"
From the top down this is what I see
Android Systems recovery <3e>
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
Any ideas?
In Odin I had to download Keis Air because my computer was not installing drivers for the phone. once i downloaded Keis Air and plugged in the phone it recognized it and finished installing the drivers. I did a computer reboot and when I follow the steps I get a YELLOW highlighted box in ODIN under the ID:COM part that says 0:[COM3] in yellow.
I hit start but nothing happens.

Worked awesomely! Just need root now. ;-)
Thanks everyone for all the hard work!

avelasqu said:
Worked awesomely! Just need root now. ;-)
Thanks everyone for all the hard work!
Click to expand...
Click to collapse
I guess you missed this, which was posted at the exact same time.
http://forum.xda-developers.com/showthread.php?t=1591598

k0nane said:
I guess you missed this, which was posted at the exact same time.
http://forum.xda-developers.com/showthread.php?t=1591598
Click to expand...
Click to collapse
Ah shucks. I was able to use the SU files from the t989 and it worked for me.
Is there a difference in what I did and what the root kernel will do?

rooted kernel has a few perks to it that k0nane threw in . hopefully you guys can now attract some devs and start working on roms/cm . we aim to please, just remember us the next time you have a device that isnt getting much love ;P
SCossio from what i understand the key combo gets you into a quasi-downloadmode, need to hit vol up to confirm to enter download mode and then you can plug it in and begin to flash this
perhaps some nice blaze owner can make a how-to video? sorry if our instructions seem off or vague, myself or k0nane have never seen this phone let alone touched one, so we rely on you guys (blaze owners) to help with these kinds of things.

Here is a video on how to successfully enter download mode every time.

shabbypenguin said:
rooted kernel has a few perks to it that k0nane threw in . hopefully you guys can now attract some devs and start working on roms/cm . we aim to please, just remember us the next time you have a device that isnt getting much love ;P
Click to expand...
Click to collapse
This! We're here to help. Feel free to come join us on IRC.

i highly suggest you guys check out https://play.google.com/store/apps/details?id=com.s0up.goomanager to download all your roms etc, just the same as rom manager except you can use any recovery you wnat. same rules still apply... if your devs dont post roms/kernels to goo then they dont show up in teh app

Pre-reqs?
Use odin to install the rooted kernel first, then clockworkmod, correct?
This is my first time rooting. I just wanted to double check that the clockworkmod image didn't contain the rooted kernel already.
Dedridd

It doesn't although for the sake of only incrementing the flash counter once it probably could be consolidated.
However, if you flash CWM its a simple process of flashing the SU binary zip package from the sdcard with CWM, same end result.

I keep getting this message when I try and run odin on my Samsung Galaxy S Blaze 4g I know that I am doing everything right maybe it is my phone
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Someone help me plz

Total n00b here.. with a stupid question. (or twenty).
Let's say, if this "Clockworkmod Recovery for Blaze" was installed via Odin and then Rom Manager app flashed with Clockworkmod Recovery for Galaxy S 2, what happens to the previous files (loaded via Odin)? Do both recoveries co-exist? Or does one replace the other? and if so, can this process be repeated again?
I'm just trying to understand this process.
[Update]: I repeated the process described in this thread, figuring that having recovery for some other phone model would not be a good idea, probably not be a well functioning recovery... everything seemed to have worked great but how can I verify that I have the correct version of recovery now? (I apologize for another stupid question in advance).

SCossio said:
Okay.
Im having issues.
I have a T-Mobile Samsung Blaze4G
Followed every step to the T.
When I do Vol up+ Vol dwn+ PWR
i come to a recovery screen and at the bottom it says Manual mode.
I dont see anything that says "Download Mode"
From the top down this is what I see
Android Systems recovery <3e>
Reboot system now
apply update from sdcard
wipe data/ factory reset
wipe cache partition
Any ideas?
In Odin I had to download Keis Air because my computer was not installing drivers for the phone. once i downloaded Keis Air and plugged in the phone it recognized it and finished installing the drivers. I did a computer reboot and when I follow the steps I get a YELLOW highlighted box in ODIN under the ID:COM part that says 0:[COM3] in yellow.
I hit start but nothing happens.
Click to expand...
Click to collapse
Hey there. The phone must be plugged into the computer before you put the battery in.

You guys can also just turn off your phone hold down the volume up+volume down and plug the usb cable into the phone... Make sure the other end is plugged in to the computer first , Odin 100%
Sent from my SGH-T769 using xda premium

Done...now will wait for ROMs. Thank you to all involved in making this happen.
Sent from my SGH-T769 using XDA

De Odexed / Debloated rom should be coming tomorrow. possibly maybe.

Awesome! Can't wait. Thanks for all of the hard work!

[Q] Is it bricked or hardware?

Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.

One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?

Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.

Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/

So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.

Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.

Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow

Yeah hope so too! Let us know how it ends up going

Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD

Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.

Sweet, glad you got it fixed

[HELP] Verizon S3 won't go to Download Mode.

Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!

You're being unclear. You say you have a Verizon GSIII but also say you have an international GSIII, which is it?
For download mode, pull the battery then try again but hold it for like 15-30 seconds.
Sent from my SCH-I535 using xda app-developers app

Make sure you are not connected to your computer until after you get into D/L mode. I know if I am connected to the PC before I try to enter D/L mode it will not work.

ColdKill3r! said:
Hi, everyone.
I have a Galaxy S3 from Verizon and I cannot root the phone, it simply won't go into download mode.
I have tried formatting it, but still doesn't work.
I have Android 4.1.1 version in it, I have called Verizon and they didn't know how to do it either.
I have done the combo keys Volume Down, Home and Power, but it eventually just starts up normally.
I have tried the same thing on another S3 from Verizon and it didn't go into download mode either.
I did get an international version of the phone, so the problem must be verizon.
Please, help!
Thanks!
Click to expand...
Click to collapse
You have to make sure your USB cable isn't connected while trying to put into download mode. Also hold Power, Volume Down and home button until phone vibrates and then release. Hope this helps

Hey, guys.
Thanks for the replies.
Anyway... I have it disconnected from the USB and I also have already tried the battery thing, but none of those things worked.
I have 3 S3's, one of them is an international model, which I have rooted myself and everything worked (download mode), but the other 2 are the Verizon version (SCH-i535) of the phone isn't working - even though I've tried taking of battery, memory card, sim card, no USB cable connected. I have USB debbuging and everything that I need to have activate, but it won't go into download mode. I wonder if it's blocked (which I doubt, since I've seen people saying they rooted the Verizon S3).

Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Kernelizers; Kernel tweaking at its finest.

It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
luis86dr said:
Its actually a button sequence of the following:
While phone off and unplugged;
Hold Home Button (Just home)
Then hold Volume down while still holding home.
And finally, hold power while holding Home + Volume down
Let me know how that works out for you.
Click to expand...
Click to collapse

help mine doesn't go neither
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help

misstq said:
i did the same key combination but i don't come into download mode.
i enter a screen with an android robot lying on the back, open belly with a warning sign..
can not root ( pls help
Click to expand...
Click to collapse
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)

Download mode
ColdKill3r! said:
It works now. I was just not holding it long enough. I'd let go of it as soon as the phone would vibrate when I should keep holding 'em.
Click to expand...
Click to collapse
Home...Volume Down...Power...vibrate...hold until warning message about using custom ROMs appears. Then press
volume UP and I get the green Android robot and this message "Downloading...Do not turn off target !!" Upper left
corner of screen reads in tiny red text "ODIN MODE"
followed by PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Does the above mean that I am in Download Mode? When I plug in the USB cable there is no response.
What does "Do not turn off target !!" mean?
If I AM in Download Mode at this point I should be able to use heimdall at the command line, but here are my responses
at the command line:
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ heimdall detect
heimdall: command not found
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall detect
Device detected
[email protected] ~/Downloads/Android_ROMs/Galaxy_SIII/Xtras $ ./heimdall print-pit
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
As seen above it seems like there's an attempt to connect to my S3 but the libusb error: -3 sent me off searching about for a solution
and I found something about installing libusbx-1.0.17.
Followed the instructions in the INSTALL file
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
#1 seemed to work, #2 "make" returns the following:
[email protected] ~/Desktop/libusbx-1.0.17 $ make
make: *** No targets specified and no makefile found. Stop.
So, that's where I am stuck. Does #2 mean that I should type "make" and the specify a file as "target"
Anyone know where to go next?
The wiki says "Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary."
I don't object to rooting my phone, but if this heimdall method is the CM recommended method I'd like to get it to work. Suggestions???
Thx,
kb

What are you trying to do? Root? Install cm? I think there are much better ways to do what you're trying to do, but you need to be clearer.
Sent from my SCH-I535 using Tapatalk 2

No download mode.
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.

utter madness said:
I have a sprint SPH-L710 S3, and have previously gotten into download mode with no problems, but now, I get the Samsung logo, and then the Samsung galaxy SIII logo, and then a reboot to recovery, I can't get into download mode any longer to load via odin.
I am completely stuck. I've been working on this all morning trying to recover from my current soft brick state.
I've tried to restore from the backup, but can't be sure it's the correct backup. the filename is 1970-01-01.21.17.36/. I can't help but think that is not correct.
I'm currently running CWM recovery v6.0.3.1, and have been trying to update to 4.4.2 kitkat from stock 4.3 update.
Any assistance is greatly appreciated.
Thanks for any assistance you can provide.
Click to expand...
Click to collapse
I'm going to direct you post your question in the Sprint S3 Q/A section as continuing here will cause confusion since our Verizon S3 has TW 4.3 and we are presently locked down to the point where we are unable to use a custom recovery.
CWM defaults to naming backups in the year 1970 so that looks right at a cursory glance. Last thing, your recovery is very out of date, given how KitKat works with our Verizon S3, you need a newer version of CWM to flash KitKat. Post in the Sprint section and be as specific as you can be as to what you want to accomplish.
Merry Christmas!

SS S3
skywalk3r89 said:
I'm having the same problem as you. Except the difficult thing for me is that I can't see my screen because the lcd is broken. I have tried the buttons and it just wont go into download mode.
The next thing I tried to do was see if I could get it into download mode on a fully functioning SGS3. I tried it out, and even though I was using those buttons, it still wouldn't go. I tried again, but this time I held the three button combo for about 2-3 additional seconds AFTER I felt the vibrate and it worked!! Try that, and hopefully it will solve your problem.
However, I tried my same steps on the broken lcd phone and it didn't seem to work. (at least I can't tell if its in download mode or not)
Click to expand...
Click to collapse
Thank you so much , I followed your way and succcessed

the walkingdead said:
Thank you so much , I followed your way and succcessed
Click to expand...
Click to collapse
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
Not trying to be mean but please do not revive 6 month old thread with a simple "Thanks" post. The moderators hate that. That's what the thanks button is for.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Hey Sandman,
Thanks for the suggestion.
But since there are hundreds of S3s still being sold, and hundreds of buyers looking for support like this, shouldn't we supply this topic if someONE some where might need thsi?
Like I just did on my New bought a NEW a month ago
Huh?

Note 5 bricked

Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.

Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk

Trizen said:
Delete the Samsung drivers and then reinstall them, that may get your computer to recognize your device. As far as the rest idk
Click to expand...
Click to collapse
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?

molodoko said:
I have done that several times so far. The thing is, the system says not reco. but Odin sees it. I can boot into both download and recovery. So is this considered soft or hard bricked?
Click to expand...
Click to collapse
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.

Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums

molodoko said:
I have used Odin 3.09 and 3.10.7. I got my firmware from Sammobile and search by my device model SM-N920T. I have tried this on two different machines, Win8 and Win10. Someone on another thread asked me to try a few different ways to attempt so I will try this:
One "trick" that might work:
Without your phone plugged-in to your PC,
Set up ODIN w/the firmware of choice,boot-up your phone,plug-in to PC,then,boot into download mode while plugged-in.
Try this,or several variations of it.
I had to do this using ODIN on my Note5 to get programs/ROMS to load up.
This isn't common,but,I've seen a few other people have to do this,it's likely a PC-Driver related thing (I have a somewhat uncommon PC,a Gateway,that may explain it)............from Kolio on AndroidForums
Click to expand...
Click to collapse
If it's bootlooping, you must go into stock recovery and wipe data, factory reset!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Brava27 said:
If it's bootlooping, you must go into stock recovery and wipe data, factory reset! View attachment 3569513
Click to expand...
Click to collapse
I have gone into recovery and wiped data however that does nothing. here are the steps I have done:
Power phone on holding the volume up, home and power buttons - it installs system update
-wipe data/factory reset
I get red line: E: failed to mount /preload (No such file or directory)
then using what was suggested in prior post
When trying to flash with Odin it gets to cm.bin and then fails.

Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Sent from my SM-N920T using Tapatalk

Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse

molodoko said:
Brava27 said:
Have you tried re-downloading the firmware from sammobile.com? Try a different build number?
Yes i have. i grabbed the latest and the one before that. Maybe I should go one further.
I also tried using nobleltetmStockRecovery.tar.md5
I have gotten most success from this though it just hangs after NAND Write Start!!
Click to expand...
Click to collapse
That method given to me earlier was the key, it was the order in which i plugged it in, turned it on and boom it worked!!
I am not going to do this again until i am much more well versed in the Android world. Thank you to everyone who helped! :laugh::laugh::laugh::good::good::good:
Click to expand...
Click to collapse

molodoko said:
Good Morning
I have spent all night trying to determine how to unbrick my brand new Note 5. I was able to use Odin to root the device, but then when I rebooted after trying to install TWRP, it is just plain bricked. I cannot get Odin to install any firmware, i can boot into recovery mode, but wiping data and cache does nothing. I get a constant bootloop that says Kernel is not SEAndroid and Custom Binary blocked by FRP.
Every time i plug the phone into the laptop, it says that the USB device is unrecognizable. I have installed Samsung USB drivers. I am just at a loss, Odin fails every time.
I will admit that I am a pathetic noob and should have waiting a longer time to do this. I had just given up my iPhone on Sunday.
Any help would be appreciated.
Click to expand...
Click to collapse
It happened to me too i was scared i thought ihad messed my phone up but I found a solution

You can try different usb port and different cable too. And which tab you use for the installing the stock firmware? FRP lock is here because you didnt open the oem unlock before the installing customized file. You have to install stock with odin. and then factory reset and then you can open the device get the development settings and disable the oem unlock.
SM-N920I cihazımdan Tapatalk kullanılarak gönderildi

Brava27 said:
You can't brick your phone. That terminology is silly.
What Odin are you using? You have to use 10.0.7.1 something like that.
Also make sure you are flashing your device model firmware.
Try another computer if Odin fails on your current computer.
Click to expand...
Click to collapse
Sure you can brick your phone, and the only thing silly about the term brick is the over use of it.