I read many topics in the forum, tried several ways but without success.
My phone froze, so I had to take the battery out. When I turn the phone on, it shows samsung logo but gets stuck on the slimbeam screen.
So the current situation is:
- Recovery mode doesn't work.
- Download mode works.
- My computer and Odin don't recognize it.
-I tried 2 PC's (win 10) with samsung drivers installed.
-Various usb cables.
-I tried to use odin in win7 compatibility mode ...
I don't know what to do anymore, please help me. I really like my cell phone.
Sorry my english.
Related
Hi,
I give up, I have tried so many things to solve the problem but I need your help please.
My GT N7100 can only be "seen" by usb only when it's in download mode. But when I boot the phone, it only charges...
I've tried to uninstall all samsung drivers, kies and cleaned the registry. I ve tried to reinstall only the samsung drivers... No
In download mode, the phone is recognized as a gadget serial then the driver is found (samsung modem), I can even hear the windows sound of usb...
I thought about a problem with the usb electronic part, but I can t figure out why it would be recognized in download mode in this case...
Please help and sorry for my bad english
Regards
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Have you tryed using a different usb port? How about using a different pc? Does it even connect when you tab s is on? My pc can detect my tab s fine but had some issues with windows 8.1 and odin crashing. My guess would be trying on a pc that can detect other devices in download mode just fine. Did you also enable usb debugging?
I'm stumped given what you have tried. I'm assuming you are using CF-autoroot. On Windows 7, Odin wouldn't see download mode until I installed the Samsung drivers downloaded from Samsung. Then everything went fine (after which I rolled Windows back to the previous restore point because the Sammy drivers messed up my Nexus 5 connection. Also, if it matters, I used Odin 3.0.9 but with Chainfire's Odin.ini file.
Are you waiting to plug the tablet in until after you have entered download mode? I don't know why, but the instructions for CF-autoroot were very explicit about that.
coolguycarlos said:
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Click to expand...
Click to collapse
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
pdolton2000 said:
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
Click to expand...
Click to collapse
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Yes I already tried different USB ports. Different USB cables. Different computers. USB Debugging is enabled.
Again Odin does detect the tablet as long as the tablet is booted up to Android. Odin detects is, Windows Detects it, Kies Detects it.
As soon as I reboot the tablet into Download Mode and plug it back into the computer, is as if nothing is plugged in. No driver gets installed. No new hardware is detected and thus Odin wont detect it.
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
coolguycarlos said:
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
Click to expand...
Click to collapse
Nice one pal glad it all worked, thought you might not of been in dwnload mode coz thw only reason odin wouldnt detect it is that reason....strange how vol down was taking you into recovery though, usually thats vol up...mad
---------- Post added at 07:35 AM ---------- Previous post was at 07:32 AM ----------
DUHAsianSKILLZ said:
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Click to expand...
Click to collapse
Adb drivers are active regardless when usb debugging is enabled ....some times though you have to install them manually....but as hehad installed samsung software the drivers got installed.
Hey there guys!
Recently I wanted to get some custom ROM on my brother's Gio. It had stock Samsung software on it, did a factory wipe in recovery, worked perfectly, then I installed CWM in the orignal recovery from the SD card - didn't root before. Since then I can't boot into Recovery, however Android booted up. I tried to use some apps in software to get rid of this problem, but ROM Manager said the device is not supported, then I tried another one called Rashr, which had a question relating to recovery I guess instantly on the app's startup, I hit "Reboot" since then the phone is bricked. If I turn it on with just the power button, it shows the Samsung logo, stuck in a bootloop. I can't access recovery, only dumpram, and Download Modes. I tried fixing this with reinstalling the stock stuff through Odin, but the software doesn't detect the phone. Tried installing Kies, standalone USB drivers, multiple Odin versions, different cables, ports, different computer, nothing worked. When I connect the phone to my PC it plays the "device connected sound" but I got a message, that it's an unidentified device. Went into Device manager, where it recognizes it as a Samsung USB device, with the yellow triangle. Tried updating the driver manually from the manufacturer's list, uninstalling then reinstalling the drivers with no luck. Also I tried cleaning the USB port of the phone, still nothing.
The computers I've tried are running Windows 8.1.
Please help me, I think I've tried everything still the device is bricked.
I have same problem.
did you fix it ?
weLL ,sad to say it but ,its neither worth the effort,time or my typing these letters up here to remind you ,that it's neither the end of days or expensive to buy something this side of the stone aGe ! have fun but not with that one ;(
https://forum.xda-developers.com/galaxy-gio/orig-development
search here, download mode should be enough
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
Title tells everything. And i'm also tried everything. Can't use download mode on my Galaxy W I8150.
I tried; different cable, different port, direct usb ports, drivers, searched internet...
Just didn't try another pc. I don't think it's about pc. I'm running Win10x64 latest. I'm also tried from virtual machine (win7). I can normally use mtp to transfer. P.S : Upload mode also not working, it shows android logo and a package logo, waiting for recovery settings but it restarts phone after 5-6 seconds.
Any idea to fix it?
i have same problem.
I'm stuck...
I had to use windows xp