Hi,
I tried to downgrade my i9000 and now it's only showing the soft brick sign.
I used to run CM11 with CWM before I decided to downgrade to stock.
I connected the USB cable then used Odin with the same PIT file that I initially used to install CWM. I guess so far so good as it recognizes something on the COM port associated with my USB entry and the background turns yellow.
I have picked the 3 stock files that match my model (GT-I9000M), went in downloading mode and hit Start.
Odin reports that successfully checks the files, then right after "SetupConnection" it ends with Success 0 / Failed 1.
I just do not get farther than that. There is no action in the square above the COM port and there is no other message. The phone remains in Downloading mode and there is no progress bar displayed. at any time.
Anybody can make any suggestion on how to fix it?
When do I know it's totally bricked?
Many thanks.
Until it still goes to downloading mode it is not bricked. This has happened to me once when i tried to go back to stock using odin and odin said it was connected but will say failure after setting up connection my problem was that Virtual box for ubuntu was preventing the phone from being fully connected.
The main problem is that maybe your usb connection in your computer might not be fully recognizing the phone
so try different usb port, open odin in administrator mode, and continue trying it until it works
usually when i use odin i keep the computer as still as possible until flashing has been done completely.
Also are you using the right files because that could be a problem.
Here is the video I originally used to teach me to odin back to stock but its for the samsung vibrant but the procedure is the same
https://www.youtube.com/watch?v=l3K9my9kAvI
Hope i helped
Thank you for your message. You were right, the problem came from USB, specifically from the driver and OS, I guess.
I failed to flash it on Win7 and Win10, as described above, then I told myself I will give it a try on a XP machine (32 bit). It worked like a charm, first attempt.
Regards.
Related
First and foremost, been a long time lurker here (first time poster) on XDA... and the community here is just outstanding.
So I've decided to root my epic, everything was great. I used the one click 2.5CWM root, and realized I wanted to try out another rom that wasn't compatible. Reflashed with the( ReRFS.Format.ROM.EC05 ) (since it kept me stuck on the samsung black screen) then went ahead and flashed the zip for CWM 3.0.0.6 with viperrom,...
Now here's where it gets interesting... I want to be able to revert back to a stock rom, and flash syndicate... but for some reason my CWM wont allow me to flash any .zip files from SD card. It says "failed to mount /sdcard". i formated it on my pc, it reads / writes fine, but anytime i boot into clockwork, it can't mount my sd card. I can still boot into my phone, it's still usable for daily usage, but it just doesn't look like what I like.
Now I've tried running Odin, but when im in the download mode, odin will not recognize my phone being plugged in. I've downloaded the proper drivers, for both my win7 x64 and 32 bit computers, tried every USB port etc... and it still wont work.
any idea on what I can do to get my CWM to work?
Use Odin with a non-stock cable.
I've tried it with 4 different data cables, 2 Samsung OEM, and 2 generics...
Have you tried a different PC, or Heimdall?
Make sure you're using Odin 1.61, the correct PIT, and the EC05 TAR.
http://k0nane.info/rom/odin-pit.zip
http://k0nane.info/rom/SPH-D700-EC05-8gb-REL.tar
Also there is a small amount of phones that did not want to Odin correctly unless the battery was out. You can try that too.
So I've tried to run Heimdall, and i'm still experiencing the same issue that I was having with Odin.
Every time I plug in my device via USB (samsung OEM data cable, only cable i have that will prompt that a device is connected) windows will pop up with a message, device not recognized (unknown device in device manager when in download mode) it seems to be fine and it'll recognize it correctly when I have the phone running (booted up into the rom)
I ran the zadig.exe for the drivers, and nothing seems to work.
Instead of Odin, try the SWUpdate for EB13, it is much less fickle
Place your phone in download mode (keyboard #1 and the power button) and see if it will connect/install
If It works, you can then move on to either upgrade to EC05 using the stock update zip, or install CWM and flash your FAV ROM
My comp doesn't seem to want to recognize the phone anymore... everything is "unknown device" now
Yeah get your hands on a blackberry cable. My guess it will help your cause. Make sure the drivers are installed on your pc as well.
im just going to reformat my netbook and do a fresh install on the drivers, too tires of the "guess work" i'll keep you guys posted on how that goes
SUCESS!
my epic is back to full stock via Heimdall. (took a little playing around to get)
@qbking77 - Thanks for the tip, I ended up using a 7" black berry data cable, and heimdall recognized it.
The only thing now though, all of the wires i have now, don't seem to let me use One Click Root CWM 3.0.2.5 I'll try it with my OEM samsung cable (that worked before) when i get home, I'll keep you guys posted.
Thanks again!
I am currently on a stock unrooted 4.1.2, SPH-L710. I have been attempting to root my Galaxy S3 using Odin3 v3.07 on Windows 7 using a variety of methods. I get the basic gist where you put the phone into download mode and then flash a *.tar or *.tar.md5 in the PDA field. It gets as far as "Firmware Update Start" and then "<some file name>" (like recovery.img--varies with the solution), but it never progresses past this point. Looking at some guides, it appears that there should be a "NAND write start!!" message which never appears, as well as a progress bar, which I never see. This leaves me stuck in download mode, but thankfully if I just unplug the USB cord Odin detects it as a failure. Following that, I am always able to boot back into Android, so it seems Odin is unable to touch anything at all.
I tried to use this toolkit (http://forum.xda-developers.com/showthread.php?t=1703488), but despite installing drivers, I could never get it to recognize my phone as being in USB debugging mode. This is after all drivers had installed correctly. I have also heard that there can be problems using usb cords other than the original, but I have made sure to use the OEM cord. Any ideas on what might be the problem?
doublering said:
I am currently on a stock unrooted 4.1.2, SPH-L710. I have been attempting to root my Galaxy S3 using Odin3 v3.07 on Windows 7 using a variety of methods. I get the basic gist where you put the phone into download mode and then flash a *.tar or *.tar.md5 in the PDA field. It gets as far as "Firmware Update Start" and then "<some file name>" (like recovery.img--varies with the solution), but it never progresses past this point. Looking at some guides, it appears that there should be a "NAND write start!!" message which never appears, as well as a progress bar, which I never see. This leaves me stuck in download mode, but thankfully if I just unplug the USB cord Odin detects it as a failure. Following that, I am always able to boot back into Android, so it seems Odin is unable to touch anything at all.
I tried to use this toolkit (http://forum.xda-developers.com/showthread.php?t=1703488), but despite installing drivers, I could never get it to recognize my phone as being in USB debugging mode. This is after all drivers had installed correctly. I have also heard that there can be problems using usb cords other than the original, but I have made sure to use the OEM cord. Any ideas on what might be the problem?
Click to expand...
Click to collapse
You could try using a different USB cable. The OEM ones have been known to cause problems with Odin.
As far as USB debugging goes, I've had some Windows 7 computers that will see the phone with USB debugging disabled, and some won't unless I uncheck USB debugging.
QBking 77 has a nice video on rooting the S3 at: http://www.qbking77.com/how-to-root/root-samsung-galaxy-s-iii.html
Good luck!
Install drivers again. Plug your phone let it be recognized. Unplug the phone. Put it in download mode, plug it. Let the computer recognized it. Unplug. Open Odin and try again.
There's a method by Chainfire in Original Development, which works great.
Sent from my SPH-L710
Hi, I recently tried using a stock image with odin for my galaxy tab pro 8.4. Odin started flashing but failed when sending system.img.
I tried this process twice and got the same result even using a different USB port in may computer and a different cable but, after the second try (and as the first one I disconnected the computer and restarted into download mode), the tablet usb stopped working.
When I connected it in my first two tries, I got the typical windows sound when you connect anything in the usb, now I dont get anything and not even in the device manager. I tried with another computer and got the same problem, no usb connected sound and nothing in device manager.
My device is now stuck in odin mode. If I try to reboot normally I get into download mode but with the message "Firmware upgrade encounterd an issue. Please select recovery mode in Kies & try again".
I have tried deleteing de drivers and installing kies but still nothing.
Can you help me please?
Nevermind
MarcoZM1978 said:
Hi, I recently tried using a stock image with odin for my galaxy tab pro 8.4. Odin started flashing but failed when sending system.img.
I tried this process twice and got the same result even using a different USB port in may computer and a different cable but, after the second try (and as the first one I disconnected the computer and restarted into download mode), the tablet usb stopped working.
When I connected it in my first two tries, I got the typical windows sound when you connect anything in the usb, now I dont get anything and not even in the device manager. I tried with another computer and got the same problem, no usb connected sound and nothing in device manager.
My device is now stuck in odin mode. If I try to reboot normally I get into download mode but with the message "Firmware upgrade encounterd an issue. Please select recovery mode in Kies & try again".
I have tried deleteing de drivers and installing kies but still nothing.
Can you help me please?
Click to expand...
Click to collapse
For anyone facing this, you have to wait for the tablet to run out of battery and then connect it again to the computer. It will be detected as before.
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD
Went into twrp v2.8.7.0 to check something then a reboot when red text appeared int hte upper left corner where stock recovery does saying "Recovery is not seandroid enforcing" and eventually went into "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again" the damn thing will not connect to kies in any way, shape or form I have 2 usb 3.0 ports and 2 usb 2.0 ports. I've tried multiple cables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- uninstalled kies and reinstalled not checking unified drivers but it will not connect to kies. It isn't recognized by the Samsung drivers yet my the usb drivers see my note 4 is, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If anyone has any suggestion, please let me knoiw thanks
I ended up on that screen recently after a failed firmware flash in Odin. I was attempting to flash the latest 5.1.1 firmware I found on Sammobile. My note (P600) has a finicky micro-USB port, so that could have been the problem.
On second try, it worked just fine. Even though Windows explorer wasn't recognizing my tablet, Odin saw it just fine (you can see where it says "added" after plugging it in). I'd recommend giving that a try.
Thats what got me ant the kies thing besides everything pointing kies being the only way out- odin didnt recognize it's existence- plug, unplug nothing on the odin window… I was actually on 5.1.1 and was fine I just don't know who the hell went wrong
Sorry if this is too obvious, but are you able to get it into download mode before trying ODIN?
Hi no it goes right to "Please select recovery mode in kies and try again" nothing else when I was able to get to download mode before it was not showing up in odin at all.
QUOTE=jerrys0828;71275901]Sorry if this is too obvious, but are you able to get it into download mode before trying ODIN?[/QUOTE]