Samsung Galaxy Tab 8.9 LTE unbricking - Galaxy Tab 8.9 General

I have a Galaxy Tab model SGH-I957D (Telus) that I got from a friend who tried to unlock it to work on any SIM card and managed to totally brick it. It will not turn on (or vibrate) at all but the processer section does get warm indicating it is doing something. When I connect it to the computer it shows up as 24! separate drives (which windows cant mount due to them being a Linux format). If I connect it to a Linux computer 5 of the drives will auto mount. Under windows it shows up as a marshall london composite usb device 9006 and I tired following this guide: forums.oneplus.net/threads/updated-29-03-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/page-5 (see post #84) but when I tried installing the drivers under windows 10 it said they were the wrong ones. I did manage to install the Qualcomm USB Composite Device 9006 by downloading this file: yuplaygod.com/files/YUPHORIA/YUPHORIA_drivers-v1.0.zip but that is as far as I got. Since Linux can see the partitions could I somehow recover them manually with the stock firmware image that is meant to be flashed with odin? I can attach a log file I found on one of the partitions if that would help. You can look at all the steps that I have so far taken in this other forum: eevblog.com/forum/repair/samsung-galaxy-tab-8-9-lte-unbricking/

Anyone have a root method for the SGH i957 att lte version running 4.0.4 ICS? I have been looking everywhere for a solution. There are tutorials on the 7300 7310 7320 and 7320t but nothing on the i957. From what I have read this requires a different rooting process than the 7300 series. I believe the 7320 and 7320t are lte versions but the kernels and methods will brick this one. Am I right? Can anyone point me in the right direction? I am new here to XDA. I have leaned a ton in the short time I have been here thanks to forums, threads, and responses from members of the community. What a huge resource of helpful people and information! Thank you!

Related

[Q] Updating Galaxy S Captivate to Froyo 2.2

I'm very sorry for creating a thread like this one, I do not want to be annoying.
This last week, Rogers change my Acer Liquid E for a Samsung Galaxy S Captivate for very bad customer experience.
Since my Acer Liquid E was on Froyo, my Captivate is on Eclair and i'd like to update it.
Samsung Galaxy S Captivate : SGH-i896 (Rogers Canada)
Everything I've found didn't work at all.
I'm Using Kies 1.5.3.10113_29
USB Driver are installed (Samsung)
Proper USB Cable and I follow the instruction step by step on both rogers and samsung website.
Here's go the problem:
(Sorry for my bad english, I'm used to speak french)
When I start Kies, my phone is trying to be detected by Kies but it endless. It said : Connecting the device, please wait. This last step never end (2 hours waiting in front of the computer).
I've been factory reset my phone, reinstalling usb driver and kies and I don't know what to do. I'd like to know if there's someone that could help me ? I've been searching for two days for a miracle, this forum seems to be most competent way to get a result.
I'll be very happy if there's someone that could help me.
Thank you!
Marc
P.S: In my computer Windows, my computer show my mobile name by SGH-i896 and i can acces to by phone like it was mass storage mode.
awake4ever said:
I'm very sorry for creating a thread like this one, I do not want to be annoying.
This last week, Rogers change my Acer Liquid E for a Samsung Galaxy S Captivate for very bad customer experience.
Since my Acer Liquid E was on Froyo, my Captivate is on Eclair and i'd like to update it.
Samsung Galaxy S Captivate : SGH-i896 (Rogers Canada)
Everything I've found didn't work at all.
I'm Using Kies 1.5.3.10113_29
USB Driver are installed (Samsung)
Proper USB Cable and I follow the instruction step by step on both rogers and samsung website.
Here's go the problem:
(Sorry for my bad english, I'm used to speak french)
When I start Kies, my phone is trying to be detected by Kies but it endless. It said : Connecting the device, please wait. This last step never end (2 hours waiting in front of the computer).
I've been factory reset my phone, reinstalling usb driver and kies and I don't know what to do. I'd like to know if there's someone that could help me ? I've been searching for two days for a miracle, this forum seems to be most competent way to get a result.
I'll be very happy if there's someone that could help me.
Thank you!
Marc
P.S: In my computer Windows, my computer show my mobile name by SGH-i896 and i can acces to by phone like it was mass storage mode.
Click to expand...
Click to collapse
Have you checked your USB settings? Go into settings -> applications -> development -> make sure USB debugging is turned off. Then go back to applications -> USB settings -> select Kies (Firmware update). I haven't used Kies at all but in theory this should fix your problem.
Yes I did, is there an other way to update me phone ?
My kies would always do this too. I was able to fix by going into control panel, then device manager and deleting the device named something like "samsung android composite device" (phone has to be connected to see this). Then unplug the phone and reconnect and it would install the drivers again.
I had to do this fairly often, but it always worked. hopefully it might work for you.
Sent from my SAMSUNG-SGH-I896 using XDA App
This my works, but i'de like to know what driver were you using when he asked you to install it the second time ? I'm using the driver for SGH-I897, i didn't find anything for the SGH-I896
i had a lot of problems with kies doing the update to froyo 2.2 too...
first check if your usb settings are going to Kies mode and not mass storage mode. you can check my going to settings > applications > USB settings > Kies (firmware update)
if you are a rogers customer then try to bring it to a Rogers Plus store and ask them to update it for you, might have to try a few stores before you find a someone that can help.
if you want to do the update yourself then you can try this.
i first had to install an older version of kies, the latest one from samsung website would not detect my phone at all. the version i used is Kies_1.5.3.10092_2_1.exe, you can download it here http://dls.scione-music.de/KIES/
another problem i had was that during the update kies was not able to put my phone in download mode so i would get an error and the firmware update would close. what i had to do was manually put it in download mode before i get the error. so before the error pops up you have to power off your phone and disconnect the usb then while the phone is off hold both volume buttons and plug in the usb. This will put you into download mode and then kies will finish the update.
The problem has been solved by switching my windows vista to windows 7! ! I finnaly managed to convince my girlfriend to switch his ****ty pc operating system to 7. Thank you for everything all xda user.
Sent from my SAMSUNG-SGH-I896 using XDA App
I am on rogers froyo 2.2. There are some other ways than kies. You can flash the stock rom here (cwm or odin): http://forum.xda-developers.com/showthread.php?t=905042
or flash any one of these custom roms based on it:
http://forum.xda-developers.com/showthread.php?t=912657
http://forum.xda-developers.com/showthread.php?t=914284
If you are new and don't know how to flash, then read a lot before trying (try stickies in the android dev section and general section).
Edit: didn't see above post. Looks like you got it solved.
awake4ever said:
I finnaly managed to convince my girlfriend to switch his ****ty pc operating system to 7.
Click to expand...
Click to collapse
Freudian slip?

[Q] i896 USB Device Not Recognized

Hi XDA! I would really appreciate some troubleshooting help with my phone.
I have a Samsung Galaxy S i896 Captivate. A while ago I had to restore it to factory settings when I screwed up a rom install. It's therefore no longer rooted, and is on the very ancient 2.1 firmware.
I have been trying to update it to something more usable, but of course Samsung Kies is abhorrent, so I've had no luck there, and I've run into a bigger problem. The phone charges, but no matter which of my usb ports I use (I've tried different computers and cables), the device will not be recognized.
I've tried with debugging on and off, and for reference I'm running Windows 7 on both computers I've tried.
How can I fix this USB port issue, and get it to a newer firmware?
Thanks for any help you can give, I appreciate it.
Try Heimdall. It installs it's own usb driver (libusb) only to the port that you are connected to at the time of the install.
There is a master collection of one clicks that is a stickied thead in the Dev forum with several Stock firmwares to choose from...specifically check out the first four posts. And TRusselo has an updated flashing guide that is a stickied thread in the q &a forum if you want to flash a dev rom.
Sent from my SAMSUNG-SGH-I777 using xda premium

[Q] Moto Razr not recognized as ADB Device

Hey guys,
Total noob here as you can see, but prior to signing up I've gleaned a lot of info and help from xda-dev. Great Forum!
So first off - YES I did search for this, both on xda-dev and google. I've found several suggestions, which I'll go over below, but none have helped and I'm at a dead end.
I have a Droid Razr that I want to root. Phone specs are:
Droid RAZR (XT912)
Android V. 4.0.4
Kernel v 3.0.8
Build num 6.7.2-180_DHD-16_M4-31
PC is Win7 x64
My issue is that the when plugged in (USB Debug enabled, and NOT as mass storage of course) It refuses to show up in device manager as an ADB Connection/Device. It shows up under portable devices. Various Rooting scripts I've tried always fail at step 1, I assume because of this issue.
Here are things I've tried;
Removed ALL drivers and software related to Moto Razr. After my PC was thoroughly convinced that it had never met a Motorola Device before, I plugged in my RAZR and Windows could not find a suitable driver automatically, which I expected. So I tried these things one at a time:
MotoHelper Driver 5.50 - It is the correct driver for the device, but it recognizes my phone as a portable device, not an ADB connection.
Motorola Device Manager - same results
MotoCast (suggested via Google search) - same results.
Android SDK. I downloaded the software, installed the packages I needed, including the Google USB Driver package - same result.
I Googled up a similar issue with a software called "DejaConnect", I downloaded and installed their driver - same results.
Going through each of these, I removed the old drivers and rebooted PC several times, rebooted phone several times, double and triple checked my USB Debug setting, and I just can't get this to show up as an ADB Device.
What am I doing wrong here? I figured if anything could fix my issue it would be the SDK software, but that didn't resolve the issue.
Any help is greatly appreciated, thanks in advance!
Wrong forum wrong device.
Sent from my Galaxy Nexus using Tapatalk 2
It looks like your phone is not in the Mass Storage mode. Switch to that (so that it's not recognized as a Media device, but as a Mass Storage one). That's the way I have it on my Razr I.
And yeah, wrong phone for this forum
mattlgroff said:
Wrong forum wrong device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Sonuva!
Can I get this moved to the correct DROID Razr forum? I don't want to double/cross post.
Thanks patoberli, I will give that a try. From the guides I was reading I was convinced it should NOT be connected as mass storage, but we'll see what happens!
wintermute85 said:
Sonuva!
Can I get this moved to the correct DROID Razr forum? I don't want to double/cross post.
Thanks patoberli, I will give that a try. From the guides I was reading I was convinced it should NOT be connected as mass storage, but we'll see what happens!
Click to expand...
Click to collapse
So just in case this does get moved to the correct Droid RazR forum...
Reading this thread: http://forum.xda-developers.com/showthread.php?t=1764850 I decided to do a factory reset. Before setting up any accounts or syncing, I turned on USB Debugging and BAM, showed up as an ADB Device. After that it was easy peasy.
Used Eternity Project's one-click root tool. Installed Safe Strap for backing up and flashing ROMs, right now I'm using the Black Widow ICS rom.
Successful day.

[Q&A] [GUIDE]How To Unbrick Your Galaxy Tab!

Q&A for [GUIDE]How To Unbrick Your Galaxy Tab!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE]How To Unbrick Your Galaxy Tab!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Galaxy Tab 3 T210R / Bricked?
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Bricked, or not bricked? Samsung Galaxy T210R
gtcreative said:
OK, I know I screwed this up b/c I was tired when I was working on the tablet. It's a Galaxy Tab 3 7.0 T210R (one of several I'm working on). Feel free to say I"m an idiot, I already know it was a stupid mistake.
I reset to factory specs using the operating system after installing the KitKat 4.4.2 firmware update and TWRP. This was that last thing I did before the current status.
Current status is that it won't start, yet Odin registers the tablet as connected, and seemed to be able to reinstall the firmware & TWRP with a positive result.
___________________________________________
UPDATE: I was able to connect kies which also seemed to complete a system update, except that the tablet still has a black screen and seemingly unresponsive buttons. This is so weird.
Sooooo, not sure if it's bricked or not, since Odin registers it being connected. However, Kies can't find it. And none of the buttons appear to work.
I have it plugged into the outlet charging at the moment (not the laptop). It was nearly fully charged when I screwed it up.
I have SD cards, and an a couple exact model tablets that work just fine with the new Firmware (4.4.2) and TWRP (2.8.20). Is it possible to clone one of the working ones onto this one?
The one thing I haven't done is try to install a new ROM.
Help? Bricked? Or... ?
Much appreciate any expertise or suggestions. Thanks.
Click to expand...
Click to collapse
____________________________________________
Update 07/07/2015
I let the tablet's battery run down (as was suggested in one of the threads), and when I plugged it in to the AC power, I got the Samsung Galaxy logo!
I was then able to restart in download mode, and reinstall the md5 file via Odin. Not sure why letting the battery run down works, but at this point, I don't really care. I'm glad that the tablet could be resurrected from the dead, in spite of my mistake.
I hope this is helpful! :victory:
tab not showing up in ODIN
I have my galaxy tab soft bricked, but when I plug it in to ODIN, the pc does not recognise the tablet and therefore I can't reinstall the firmware, although the tablet is connected to the pc, as it gets charging when plugged in.
I've tried reinstalling samsung drivers, killing every samsung keys program running in background, another cable and even three different ODIN versions (v.1.7 // v3.07 // v.3.09), but it is not showing up in any version.
I have been looking for a solution since last year. last year I had windows 8 and it didn't work; then I upgraded to win 8.1. again nothing, and with windows 10 the same story. can anyone help me please?
thank you very much.
internal memory read only my p3100
hi ..
thanks in advance
i dont know what happened to my tab p3100, i am not able place any files in internal memory.
it will get into the main screen and gives bunch of errors like process google play is not working... bla bla bla...
i can uninstal the function but after reboot it will be there in the phone. i am bit tensed what is this is this a bricked one or?
please help me out i tried odin, through odin i installed omia rom 5.1 after that this error i am getting please help me out to solve this.
my phone already rooted..
Once again thanks hooping for the fix.
please mail the fix to [email protected]

S3 LTE i9305 Dead Brick Syndrome aka EMMC Failiure

My S3 4G didn't wake up a couple of years ago. I've been trying since to find a way to revive it and had a glimmer of hope when I saw the youtube presentation of Oranav reviving a standard S3.
Recently, I came across the instructions to revive using a PC running Windows, i9300-EMMC Guide at https://toomoch.github.io/i9300-EMMC-GUIDE/. I have a type 1 brick i.e. totally dead so I followed the type 1 procedure in the hope that it might just work on my phone.
I followed the steps of preparing the environment using the i9300 EMMC toolbox, prepared the SD card, inserted the SD into the phone and tried to turn on as per instructions getting a white screen but no 'funky stuff'. Connected USB cable but was unable to low level format as python kept giving access errors.
I assume the reason I couldn't proceed was because the sbootsdcard.bin, exploit and fw.bin from the i9300 EMMC toolbox aren't compatible with the i9305. That being the case is there anyway of modifying these files or getting the correct ones for the i9305 and following the same procedure?

Categories

Resources