Recover Bricked AT&T Tab SGH-I987 - Whew - Galaxy Tab General

UPDATE: As rangercaptain notes, there's a simple fix (which I failed to find the first round) for the white line black screen brick (or whatever you want to call it.) For anyone else, this may still hold value for how to convert your AT&T Tab to a P1000 Euro version with phone functionality or if you need to otherwise recover/restore a rooted AT&T Tab that's not booting.
I bricked my SGH-I987 (don't ask how). It was an already rooted and unlocked Galaxy Tab I bought crippled (of course) from AT&T sans contract. It was bricked. I couldn't get to the bootloader but I could hear the Samsung startup sound and then I got a blank screen with a faint line through it.
Anyhow, here's what I did to recover it.
Install USB drivers (if not already installed, else skip. The files I eventually found were called usb_drivers_GalaxyS_x64.zip but work perfectly on my Win 7 Ult x64 system.)
Turn off Tab
Hold the [Volume Down] + [Power On] buttons until the Digging Android screen appears
Connect your Tab
Run Odin (as an Administrator if you're on Vista/7). If the phone is connected, you'll see
COM with a value and color highlight (not blank and white). (I used Odin3 v1.7.exe)
In Odin, load the following files (which I downloaded from samfirmware.com - the download will be password protected with the password "samfirmware.com"):
PIT => P1000XWJJ4\P1_add_hidden.pit
PDA => P1000XWJJ4\P1000XWJJ4-REV03-ALL-CL639474.tar.md5
PHONE => P1000XWJJ4\MODEM_P1000XXJID.tar.md5
CSC => P1000XWJJ4\GT-P1000-CSC-SERJJ2.tar.md5
Make sure "Re-Partition" is checked
If all's set, click Start and Odin will do it's thing. The Tab will reboot a few times and I was done and "unbricked".
Of course, I can't use the AT&T sim for phone functions because the sim's voice calling is blocked by AT&T. But, I put in another GSM sim and the phone works. Will you find me holding my Tab to my face? Um, no. But it will be handy in a pinch.
I hope this helps. Don't contact me asking for files. I'm not sure of their distribution/licenses so Google and download them like a big boy (or girl).

I hope nobody follows all these steps! A few threads down in the general section is a thread about at&t black screen with thin white line during boot. All you do is flash one file with odin. The link for the file is there. Too bad people can't do a little research before posting.
Bricking means totally dead, with no chance to fix it. Obviously you weren't bricked.
And at&t does not stop the tab from making voice calls. The stock rom doesn't have a dialer so you have to flash a rom with a dialer.

You're right about the black screen white line, for some reason I didn't find it when I first researched it. That would have saved me some time.
As for being officially "bricked" or not, 6 or half dozen.... If I can't boot the device I just flashed and I can't fix it no matter what - it's bricked to me.
Anyhow, yes sir, voice/phone features on AT&T sim cards issued with Tabs purchased from AT&T is blocked. Only data and messaging are enabled.
The AT&T SIM issued by AT&T with my Tab failed on both the Overcom and MoDaCo ROMs with dialer apps; but my T-Mobile and a foreign card worked fine. (Data worked on all, I'm just referring to voice dialing.) I also took my AT&T/Tab SIM and put it in a few other unlocked locked devices and again, nada. Every time dialer functions fail with this AT&T/Tab SIM it does so with the AT&T operator message "this service is not enabled..."
So yes, SIMs issued with Tabs purchased from AT&T do have voice/phone functionality disabled (it's not just a dialer issue). "Too bad people can't do a little research before posting."

Those features aren't disabled, they are not offered by at&t or included or intended for the tab. When we enable them by flashing another rom, it is with a sim card and data plan that is not a tab plan. At&t thinks I am using a captivate.
When you held in the power and volume down did you see the digging android? That's download mode, what to be in to flash. If not there still is a way to flash, but you have to use adb.exe, from the android sdk. Have you used adb yet?
How did you get the borked tab? What did you pay? I'm glad you got that tab working!

Thanks dude... you saved me... but i didn't get my 3G back... didi you get it?
defconjuan said:
UPDATE: As rangercaptain notes, there's a simple fix (which I failed to find the first round) for the white line black screen brick (or whatever you want to call it.) For anyone else, this may still hold value for how to convert your AT&T Tab to a P1000 Euro version with phone functionality or if you need to otherwise recover/restore a rooted AT&T Tab that's not booting.
I bricked my SGH-I987 (don't ask how). It was an already rooted and unlocked Galaxy Tab I bought crippled (of course) from AT&T sans contract. It was bricked. I couldn't get to the bootloader but I could hear the Samsung startup sound and then I got a blank screen with a faint line through it.
Anyhow, here's what I did to recover it.
Install USB drivers (if not already installed, else skip. The files I eventually found were called usb_drivers_GalaxyS_x64.zip but work perfectly on my Win 7 Ult x64 system.)
Turn off Tab
Hold the [Volume Down] + [Power On] buttons until the Digging Android screen appears
Connect your Tab
Run Odin (as an Administrator if you're on Vista/7). If the phone is connected, you'll see
COM with a value and color highlight (not blank and white). (I used Odin3 v1.7.exe)
In Odin, load the following files (which I downloaded from samfirmware.com - the download will be password protected with the password "samfirmware.com"):
PIT => P1000XWJJ4\P1_add_hidden.pit
PDA => P1000XWJJ4\P1000XWJJ4-REV03-ALL-CL639474.tar.md5
PHONE => P1000XWJJ4\MODEM_P1000XXJID.tar.md5
CSC => P1000XWJJ4\GT-P1000-CSC-SERJJ2.tar.md5
Make sure "Re-Partition" is checked
If all's set, click Start and Odin will do it's thing. The Tab will reboot a few times and I was done and "unbricked".
Of course, I can't use the AT&T sim for phone functions because the sim's voice calling is blocked by AT&T. But, I put in another GSM sim and the phone works. Will you find me holding my Tab to my face? Um, no. But it will be handy in a pinch.
I hope this helps. Don't contact me asking for files. I'm not sure of their distribution/licenses so Google and download them like a big boy (or girl).
Click to expand...
Click to collapse

Bricked sgh-i987
I believe I have truely bricked my tablet. Rooted no Problem. flashed euro version pit and rebooted. Had at&t logo on screen. Tried to reboot into dl and now all i get is a black screen. After I leave it plugged in for a while the screen will turn on but only to a white screen with faint horrizontal lines across it. Computer will not detect device and netiher will oden. HELP!!!!!!!
Thannks in advance
Phone LG G2X rooted
CyanogenMod-Trigger2x_build_12
kernel: 2.6.32.40-cyanogenmod-morphic
oc 1552MHz
graveyard:
LG LW690 -sold
SGH-915-wife
i9000-slow

Definitely bricked sgh-i987 samsung tablet at&t
aaronclouse said:
I believe I have truely bricked my tablet. Rooted no Problem. flashed euro version pit and rebooted. Had at&t logo on screen. Tried to reboot into dl and now all i get is a black screen. After I leave it plugged in for a while the screen will turn on but only to a white screen with faint horrizontal lines across it. Computer will not detect device and netiher will oden. HELP!!!!!!!
Thannks in advance
Phone LG G2X rooted
CyanogenMod-Trigger2x_build_12
kernel: 2.6.32.40-cyanogenmod-morphic
oc 1552MHz
graveyard:
LG LW690 -sold
SGH-915-wife
i9000-slow
Click to expand...
Click to collapse
UPDATED :
Phone LG G2X rooted
CyanogenMod-Trigger2x_build_12
kernel: 2.6.32.40-cyanogenmod-morphic
oc 1552MHz
GRAVEYARD:
LG LW690 -sold
SGH-915-wife
i9000-slow
SAMSUNG ATT SGH-I987 TABLET

Related

Totally bricked my Samsung Galaxy Tab P-i9000

Hello - I urgently need help with my Samsung Galaxy Tab.
I flashed a wrong PIT/PDA & what happened is:
- my Galaxy Tab does not reboot at all
- the flashlight in the back suddenly switched ON automatically
No matter how long I press the Power Button, the device switches off just for one second, and then the flashlight switches ON again - but no reboot.
I cannot get into download mode / when I try to use commands with Odin, it only says: error: device not found.
Odin does show my device ([COM:4]), it appears as: Added // only the download mode does not work!
When I tried to start SuperOneClick, trying to Unroot, it is stuck with: "Waiting for device"
Weirdly, though, my netbook does install the drivers automatically when I plug it in. Which means, my netbook can "read" the device.
Does anyone here know how I could make the extreme Hard Reset, without having to reboot?
--------------------------
If you think this post should rather go to the Developers section, please feel free to move it // I am thankful for any help
Have you tried connecting to it with ADB to see if you can reach it at this level (apart from with SuperOneClick)? Try installing the Droid Explorer application on your Windows PC and see if it will recognise your Tab. If it will you should be able to initiate a reset from the Droid Explorer UI. If it won't I would suggest that you are hard bricked and it will have to visit Samsung. Good luck!
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
QueenAmy said:
Hello,
thank you for your advice.
adb does not detect my device ..
and, unfortunately, neither does Droid Explorer
Just find it so strange that ODIN does ..
but like you said -
I am also afraid, that this is a "hard brick" & I will go see the retailer tomorrow.
Thank you, though, for offering help.
Click to expand...
Click to collapse
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
rotohammer said:
If Odin sees it, its not bricked. What image is on the LCD when Odin sees it, or is it blank?
Click to expand...
Click to collapse
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
bdl1969 said:
I guess the problem here is that even if Odin sees the USB device connected, if the Tab won't go into download mode then it's as good as bricked. With the SGS you can construct a USB jig with a 301k resistor between pins 4 and 5 of the micro USB to push the device into download mode if it won't respond any other way. I wonder if a similar thing would work for the Tab... Sounds like a challenge for someone who has two Tabs and doesn't mind experimenting a bit with one of them.
Click to expand...
Click to collapse
lol, I'll get my cheap Chinese Tab cables this week and hack one up to test.
My guess is that Odin will only see the Tab when it is in download mode. Id try flashing it in that state and find out for sure. It sure cant hurt.
You went to your retailer?I have exactly the same problem!!
First of all - THANK YOU for having started this discussion.
Yes, I went to the retailer. My Galaxy Tab is with Samsung Technical Support now; will keep you posted.
To answer some earlier questions, yes ODIN did recognize my Tab; but the screen on the Tab remained totally black. Only this strange "flash" light on the back kept glowing.
rotohammer, if you really get to test what you mentioned before, I'd be interested to hear what happened - but, personally I would not recommend it, unless you are sure you want to risk completely ruining your dear Tab.
studio54 said:
You went to your retailer?I have exactly the same problem!!
Click to expand...
Click to collapse
I did ... and less than 2 weeks later ..
Update:
13-Jan-2011
Today noon I got a call from my retailer my Galaxy Tab was ready to be picked up & I was really lucky: my retailer said the repair would normally cost EUR 650.-
.. as I had damaged the whole mainboard ..
but as the Tab was less than 1 month old, they were so kind to do it w/in my warranty - so I did not have to pay for it.
I'm very relieved, as you can imagine.
Got my Galaxy Tab back with a brand-new mainboard, everything is working well &
I sure learned my lesson.
I will not flash the Galaxy Tab again.
Only because Galaxy Tab and Galaxy i9000 are both on Froyo, it does NOT mean that you can flash the same software!
I wanted to apply the 3 button combo fix on my Galaxy Tab but apparently it does not work!
Bricked mine as well, but mine is a weird case
I bring up the weirdest case of bricking so far, i was on an official Arabic (P1000JPJK2)Firmware, and i noticed a new Arabic release on SamsungFirmware.com (P1000JPJM3) i downloaded it and downloaded the .pit file, Started Odin v1.7 and unchecked repartition, selected the PDA and the pit and started the processes, odin finished and Reseted the device and give me the green light with the word PASS, however, the my p1000 decided to reboot into download mode automatically, so i rebooted the device manually and got stock in the Samsung Logo and keeps looping. so i decided to go back to my previous Rom but it will always fail and i would have to reboot my tab and it will show the good ol' Phon-PC logos, however, odin would see it and would flash anything i want. i tried flashing various versions of rom's but they would all fail... i tried repartition checked and unchecked and nothing worked, so lastly i decided to flash the .pit file alone and that worked and got me back to where i was stuck in the Samsung logo loop and no ROM would be flashed through Odin BUT the (P1000JPJM3) but it still will not boot! and funny enough i took it to sammy's repair shop and they told me to come pick it up in a few hours but they told me that they failed to repair it and they would need to keep it till tomorrow, but they guy was not that optimistic about getting it repaired and to make things worse i couldn't get unrooted so there is a good chance that there will be no warranty... does this mean that i bricked it for good? please help me.

[Q] Is my Tab done for? Is it fixable? Help!

I'm having the following problems with my TAB and would like to know it's fixable. I treid almost everything to fix it without success. I'm hoping someone can help me. Anyone have these problems before?
1. Doesn't charge normally. It would charge but charge really slow like it's connected via us. It shows an x next to the lightening icon when I charge it using the original charger and cable.
2. I cannot go into recovery mode. I get the black screen with the white line. There's also no boot animation when it boots up.
3. The camera doesn't work. I get a fail message when I open it.
4. My computer doesn't detect it in download mode, kies or mass storage. My computer detect my samsung galaxy s i9000 without any problems so I know it's not the computer. I cannot change the firmware because my computer doesnt detect it.
5. I dont have the receipt to do a warranty repair. What are my other option?
AT&T SGH-i987
Firmware 2.2
Baseband P1000XXJHA
Kernel 2.6.32.9 [email protected] #19
Build XXJMA
Any help is much appreciated! Thanks!
Did you register your Tab with Samsung?
If so, they have a record of your purchase and will be able to provide support.
If not, then try this which I got from their online chat: Hope it helps.
"Kyle: To recover the device via the hardware keys, do the following:
Kyle: 1. Power off the handset.
Kyle: 2. Hold the Vol Down Key + Vol Up Key + Power Key for 15 seconds then release.
Kyle: 3.When the recovery screen comes up, use the volume up key and volume down key to navigate through the selections and the power key to select item.
Kyle: 4. Select Delete all user data to recover the device. To confirm, scroll down and select Yes – delete all user data. The phone reboots and again displays the recovery screen.
Kyle: 5. Select Reboot system to restart the handset again. "
Thanks but I cannot get to that recovery screen like I said above. All I get is a black screen with a white line when I try to go into recovery mode. I also purchase this used with no receipt.
U just need to flash a working rom. Try roto jm... in the dev forum
Your tab was modified. I wont blame Samsung if they wont fix it for u
Sent from my SGH-I987 using XDA App
How do i flash to a different rom if a computer wont detect it?
Do you have the latest kies installed? Is USB Debug on? If it still doesn't detect, have you tried android-sdk or heimdall. Each comes with usb driver. I find it hard to believe your PC doesn't detect the tab. I never heard such thing before unless you're the real first victim then...yeah, try to call Samsung and pay a fee.
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
starbuck123 said:
Yes, I tried to use android-sdk and heimdall but they don't detect my TAB for me to do anything. I also installed the newest KIES software. I also don't understand why it doesn't detect it in download mode. This is the first time I encounter this problem. I flashed my Galaxy S I9000 phones many times without a problem. Is the combination of the firmware and kernal I have that is causing my computer not to detect the TAB?
Is there a way to root my TAB via an APK? I tried Z4Root but it's not working. It tries to acquirer shell and closes after a few vibrate. yes, debugging mode is on.
Click to expand...
Click to collapse
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Benjamin Dobell said:
You've followed Heimdall's README and installed the included driver? Make sure you follow the instructions exactly.
If you have done that and your device still isn't recognised consider trying a another cable, USB port or entirely different PC.
Click to expand...
Click to collapse
Thanks for your advice but I already tried above. I didn't have any problems/trouble connecting my Verizon Tab and Galaxy S phone to the computers to change the roms. There is most likely something wrong with the Tab. I gave up and contacted Samsung yesterday. I sent the Tab to them yesterday and hopefully they won't charge me to fix it.

[Q] SGS Problem That Nobody Can Fix?

The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.
frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?
R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.
peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.
@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App
peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.
Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App
Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.
The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.
I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.

[CLOSED]Yoga Tab 2 (830, 1050, 1380) - get back to KitKat

@MikeChannon removed OP. please close
what? lol
Yeeha! You are the magic man....
workdowg said:
Yeeha! You are the magic man....
Click to expand...
Click to collapse
He truly IS the man. Helped me out BIG style.
ionioni said:
READ CAREFULLY AND BE WARNED BEFORE ANYTHING:
THIS CAN HARD-BRICK YOUR DEVICE AND I TAKE NO RESPONSIBILITY FOR THAT!
use it only if you must or not at all
you can read this for some details about what bricks are so you understand what you can get into
this is for all Yoga Tab 2 models 830, 1050, 1380 (regardless of the submodel F,L,LC)
it restores(downgrades) your bios firmware from whatever Lollipop version to the original/genuine one from the latest KitKat stock rom released by Lenovo (and all the latest KitKat stock rom's have 150422 in the rom filename, ie April 15, 2015 and nothing not even minor OTA's were released after this date for KitKat, next ones upgraded KitKat to Lollipop)
useful to:
1. those who want to return back to the KitKat stock rom from Lollipop (if you simply flash back the KitKat stock rom files and you are still on Lollipop bios firmware you will softbrick as the Lollipop bios is a x64 version while the KitKat loader/kernel are ia32 so you will get stuck at efi shells, bios screen etc)
2. those who took the Lollipop OTA, succeded, but had in time problems (bricked their device) and cannot flash a Lollipop stock rom as they don't have one (not being released by Lenovo/available yet and at least some 830 and 1380 models are in this situation), so they must flash back KitKat stock rom and after take the OTA to Lollipop (and the KitKat flashing part put's them in the same situation as those from p1.)
3. those who tried to take the Lollipop OTA and had problems and they tried to flash KitKat stock rom and yet they are failing (this could be due to problems in the updating while OTA was applied, yet could be that their bios firmware was updated to Lollipop version)
4. those who want to test stuff (going down/up between versions) ... you name it...
how to use it:
1. first download and extract the corresponding tool for your device (830 and 1050 models share the same bios firmware so they have a common tool), while at this you can watch the little attached recording i made with the tool restoring the bios for my 1380F tab so you know what to expect when you run it. USE THE TOOL THAT MATCHES/CORRESPONDS TO YOUR MODEL, you can hard-brick if for eg you use the 1380 one on a 1050 model (didn't even tried but nothing good can happen)
2. place your tab in the DnX mode: power off (by force if you have to), press and hold both VolUp and VolDown butons, keep them pressed, now press Pwr to start and release Pwr when it turns on/buzz (but keep holding pressed Vol buttons), in a few seconds your screen will display "Fastboot starting..." and it will hold on that, now you can release the Vols (you are in DnX mode). you must get that message, try again the whole sequence until you succed, don't move on until you have that "Fastboot starting..." on your screen.
3. run the tool (you must have the intel drivers installed, if you flashed to your tab at some point you should have them already), follow the messages i think it's quite easy and straightforward, in a few minutes you will be done and having a brand new kKitKat bios firmware on your tab
(3) if while running it hangs on the "Preparing to push files..." message, and your tab starts to the whatever error message you had before it means that you already have a KitKat bios (the tool works only with the Lollipop bios firmware) so you don't need to restore the bios, you can flash stock KitKat rom directly (in this scenario the tool doesn't modify anything on your tab)
4. when it finishes the tool will automatically reboot your tablet, leave it for a few seconds to start (it will most likely go ninto some efi shell, or bios screen whatever your old files were) afterwards turn it off (long press Pwr) and that's it
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
i must warn you again, while i tested this tool (i think i moved from KitKat to Lollipop and back at least 20 times and never had any issue with it) you are the only responsible if something bad could happen, this is playing with bios (and any mistake will hard-brick your tab so you will have to send it to a service for fixing). make sure you have enough battery (while i used the tool even when i was with 5% on my battery i would not recommend, i say at least a 30-40%, the process runs only for 2-3 minutes so that should not be an issue). and of course once it started the flashing DO NOT EVEN THINK OF INTERRUPTING! (you could close other software on your PC that maybe can hang your computer while flashing.. you got the point)
Good Luck!
edit: i already have messages about successful bios restoring (as expected no? ) but failing on completing the OTA to Lollipop update after flashing anew the KitKat stock rom. to them and to all of you people who are going to Lollipop from your newly flashed stock KitKat: SET YOUR COUNTRY CODE!!! after you flash back stock kitkaton the first boot input ####6020# in your contacts and a dialog will pop from which you MUST choose a country (no matter which one, preferably yours or a close one), then after the tab reboots for updating the region and comes back to Android check that you have a country code set by entering #### 59930# and it should show the code you chosed. if you take the OTA without a country set you will FAIL! if you failed on your OTA to Lollipop flash anew the stock KitKat rom and set the country code
also do not take an OTA if your device is rooted, always UNROOT first then take the update, and you can root back after or just don't root until you finished the whole Android installing and OTA updates
Click to expand...
Click to collapse
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Works perfect! Thanks!
daWyrd1 said:
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Click to expand...
Click to collapse
yeah... the guys at Lenovo deserve a break, they have such a beautiful daadeedaadoo sound on the boot animation (that one cannot even disable it )
bisti2004 said:
Works perfect! Thanks!
Click to expand...
Click to collapse
Pentru putin
Mersi Dorin!
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
aerofisher said:
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
Click to expand...
Click to collapse
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
ionioni said:
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Click to expand...
Click to collapse
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
http://bfy.tw/2gNc (just having fun) it is the one that says phone support.
ionioni said:
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
Click to expand...
Click to collapse
Yes, once i talked to them (about 5 minutes) they emailed me all i needed and i just had to find a local fedex dropoff center. They boxed it and i got it back in 6 days.... this seems to be a common thing for them....
Sent from my YOGA Tablet 2-1050F using Tapatalk
Yoga Tab 2 (830, 1050, 1380) - get back to KitKat
You are my lifesaver and I just can not thank you enough @ionioni
how can you make a file like restore-kitkat-bios-1380.zip ??!! you are such a genius !! :good:
We will never be able to flash it back to KitKat Bios without this zip file !! :crying:
But why don't we need to flash it back to Kitkat Bios on my Samsung Note 3, S5, Note 10.1 (2014 version) and Nexus 9 ?!!
thank you very much for your hard work again and keep up the good work pls
this was on my inbox and it should continue publicly maybe others can benefit
KainXSS said:
I'm wondering what your flashing to the tablet with your tool, I have a Lenovo S8-50F and lollipop is pretty abysmal on it, so I'm wondering what your flashing to downgrade the bios so I can try it on the S8, since its very very similar to the 830.
Click to expand...
Click to collapse
you should NOT use the tool unless it is made exactly for your model, or you most likely will hard-brick. moreover Lenovo uses an in-cpu module for digitally checking the authenticity of the firmware you have on your board at pwr on time and even if you have a bios that would work on your model if it is signed with another key it will cause a hard-brick (the measured boot module will refuse to load the IBB in the new bios).
for eg if one writes the 1051 windows variant of bios on the 1050 android one (they are identical in hardware) it hard-bricks (tested).
send me a link to the latest KK stock rom for your device and i will check on it.
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
bombolota1 said:
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
Click to expand...
Click to collapse
not so much you can do, the hardware is fine, it just got the wrong firmware in it... somehow you must rewrite the bios but you cannot do that from the outside (ie by software means) without being able to boot at least in DnX mode. you can check quickly ... if after you PwrOn (well.. after you long press Pwr button as at this moment Powered On of Off are werid concepts ) you don't get NOTHING on your display (ye not even the Lenovo -> Powered by Android white/black logo) than that's it (try maybe to see if somehow DnX didn't got hooked by entering a fastboot devices and see if by some miraccle you don't see your device there)
your device must be opened by a repairing service tech (especially if he is on warranty), you could do it yourself (i did) but you need the appropiate tools and know/how otherwise from a hard-bricked yet recoverable (the hardware is ok) you will transform it into just a paper holder
updated kitkat bios restore tool to version 2 (foolproof version). read the main thread post at the beginning.
Good morning.
Please let me introduce my situation. I use Lenovo Yoga tablet 2 Pro. On 9-th of november I updated Android to 5.0.1. Unfortunately, one of my commercial aps now can not make a connection with external device (no appropriate information about USB connection is appeared).
I am affraid the problem lies on the Android 5.0.1 system. Before that everything had worked perfect.
That is way I decided to downgrade to the Androix 4.x.
I found above treads, but have some doubts.
Is above tool downgrade my system to Android 4.x or do I need to do some additional operations, to get back to the Android 4.x?
In the section - how to use it (point 5) we can read:
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
Click to expand...
Click to collapse
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
pawlikp100 said:
In the section - how to use it (point 5) we can read:
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
Click to expand...
Click to collapse
you must:
1. Downgrade the bios using the restoring tool (you mention "Yoga Tab 2 Pro" so you must use the 1380 version), and you must do that so you can flash KitKat stock rom on your tablet (if you try to flash directly, without the bios downgrade it will fail and you will soft-brick your tablet)
2. After restoring the bios, download from here your stock KitKat rom and extract
3. Flash using Intel Phone Flash Tool (open with it the "flash.xml" from the target_bin directory of the extracted archive). the Intel Tool can be found in the tools directory of the same extracted archive.
4. After you finished sotck KitKat flashing, remember to set your contry code (####6020# in Contacts), also it's not necessary to make your settings wifi etc before you set your country code as they will anyway going to be deleted (a factory reset is performed on country code setting operation). if you don't set a country code you will fail when upgrading to Lollipop.
5. Update using the Lollipop OTA or stay on KitKat
Thank you for explanation.
I download system, installed Phone Flash Tool, open it and chose flash.xml, but after connecting my YT2Pro I can not see device specific with "Start to flash" button in the Device list area of the program.
see below screen. Is this screen looks as it should? (ups, unfortunately I can not post images, because I am new user).
One more thing, tablet should be turned off during flashing?
Right now my tablet is connected to the laptop by USB. It is not switched off and charging is in progress (laptop does not see my tablet as an additional disc/device).
Is above status correct?

Samsung Galaxy S5 doesn't start because MODEM ERROR

Hello,
I use Samsung Galaxy S5 a year and less. Friend of mine brought it from the US. It’s unlocked with a code. The device is TMobile. A few days ago I used it as Hotspot router, to share internet to my laptop. I restarted the phone, but not turned off the Hotspot. When the phone is switched on, displaying the following error: "Secure Fail: Modem ...“in red letters, top left and in the middle - exclamation point in a yellow triangle, and below it the inscription in white letters: "Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost". I tried to flash with Odin with different ROMs for model G900T. It gave me PASS all times, but the error still comes and the phone does not start. I gave it to a friend who has GSM service. He said he made 6 service flash and nothing. He tried flash with stock ROM and 4 fiels+pit, but nothing. I tried different tutorials from here, but I am not quite good and not sure I do things properly. I dis flash with this CF-Auto-Root-kltetmo-kltetmo-smg900t. Again same error but I had a different boot menu. There did a few cash and full resets. After that the phone started and stopped on Samsung android advertise. I flash with stock ROM after and again same modem error. I am from Bulgaria. I called to local Samsung service. They refused me to see the phone because they are not authorized. Have to repair just in USA, but this is complicated. Any idea what to do? Please, give a few tutorials to repair this!
Thanks in advance!
Please, you could give me threads which contains thing I have to do to repair my phone. No problem if I have to do few things. Important is to try everything possible again and in wright order.
Here's what I did...I used an older phone to download my modem to since my laptop was down at the time...I then booted into TWRP recovery after I've inserted the extSD card and from there I used TWRP to get modem back..hopefully I understood ur question and this would help you..sorry if it doesn't!
Sent from my SM-G900W8 using XDA-Developers mobile app

Categories

Resources