I have the SGH-i987 AT&T Galaxy Tab and while flashing it I recently got the black line in the middle problem. Considering the searches turned up a fix for that I followed the steps I could find (and using Odin) and was able to get it booting into the setup, after which I couldn't go any further because any attempt to get keyboard input caused it to crash and reboot. I've searched high and low for a way to get this thing back to stock and can't find a single source here or anywhere else on the web that is helpful. I'm hoping that someone here can help get me pointed in the right direction, because right now I have a useless device that does nothing but show me the battery is charged.
So you know: I've searched XDA and found nothing that applies to the AT&T model of the Galaxy Tab. The Verizon fix doesn't work and the T-Mo thread contains a dead link to the file I'd need. I've tried searching SamFirmware and it's been a completely useless experience-- whether that's due to poor layout and navigation or my being unfamiliar with how they keep any actual ROMs is beyond me, because the site just takes me in circles. Searching here hasn't gotten me anywhere either, since most point me to the Verizon thread (though one person has tried suggesting the T-Mo fix, but again dead links). I'm getting really let down, since I love how incredibly helpful and informative XDA usually is and this is one of those cases where I'm just spinning in circles trying to find an answer because I know the discouragement toward just showing up and screaming "Help!"
But I got nothin. I've done the searches. I've read plenty. I've searched the web (including this). I've been to the site that lots have claimed would have the file I was looking for. Nada.
Found this by searching in XDA under your device model, hope it helps
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".
I've already tried that. I've tried using instructions that used Odin. I've tried instructions that used Heimdall. I've even downloaded and used this jar executable called soft unbrick or something like that.
This is driving me crazy. Nothing seems to work. In fact, the last thing I tried (which were instructions similar to yours) got rid of the white line but have left me with a plain black screen with the buttons lit on the bottom and nothing else. The only thing I can still do is get it into download mode.
sorry to hear that if i come across anything will post,
basia314, thanks for the attempt to help, but as soon as I did a google search on it I found the XDA thread in question, and it's one I've already found before. If you read the rest of the thread in question (here) you'll see that it doesn't work.
Currently XDA contains no thread with info on how to fix my problem. I've searched. Google has provided no links either. The closest I came to finding a solution is the suggestion that I let some guys fix it for $50.
GreNME said:
I've already tried that. I've tried using instructions that used Odin. I've tried instructions that used Heimdall. I've even downloaded and used this jar executable called soft unbrick or something like that.
This is driving me crazy. Nothing seems to work. In fact, the last thing I tried (which were instructions similar to yours) got rid of the white line but have left me with a plain black screen with the buttons lit on the bottom and nothing else. The only thing I can still do is get it into download mode.
Click to expand...
Click to collapse
You say you have tried that but your first post states that you did not find anything .... which one is it?
There is a stock AT&T rom here on XDA, where did you get the one you tried?
Can you get into Recovery? In the thread listed above one of the posts states that there is no boot image and a black Recovery screen that is functional. Maybe what you flashed is giving you these same results, have you tried waiting a bit longer after a flash to see if it will actually do anything, the first boot after a flash takes a little longer. Are you checking the re-partition box during the flash, the file linked in the other thread should be flashed with the re-partition box UN-checked.
Just trying to brain storm here, hoping you fix it.
Well, it's a moot point now.
After following the instructions here to fix a "soft brick" I've now gone to hard brick. Can't power it up at all and can't get it to download mode.
When I said I couldn't find anything here I mean I couldn't find anything that helped. I can find tons of threads, usually pointing to either dead links or saying "go to samfirmware" (which I do, and still find no helpful info). I've tried close to a dozen different things to try to get my Tab back, all things either found here on XDA or linked to in threads here at XDA. Not a single one worked. And now I have a Tab that is as bricked as can be.
Of course, I've found threads here that claim a Tab can't be totally bricked as well. Maybe their Tab can't be, or maybe they're keen on tearing the thing apart to fix whatever breaks, but I don't have the tools here to do that. For me, my Tab is as useful as a brick right now, and has been for a month of trying to get it back to normal.
For reference:
[x] I am following instructions as completely as they're given
[x] I read as much as I could find reference to for things I wasn't sure of ahead of time.
[x] I googled.
[x] In Odin I checked the repartition box when instructed to do so, and made sure it was unchecked when instructed so.
[x] I made sure every time that the device was recognized in Odin in Heimdal
But...
[x] Yes I was foolish to have not made a backup.
This is killing me, and I don't have the $50 USD to get someone to fix my Tab for me as claimed in this thread. So I'm stuck with a Tab that's bricked.
Still nothing
Interestingly, I could get Odin to see my device, but trying that stock ROM still failed. I have no way of knowing if I had it successfully in download mode because the screen is doing nothing. Completely black, no lights.
Any thoughts?
GreNME said:
Interestingly, I could get Odin to see my device, but trying that stock ROM still failed. I have no way of knowing if I had it successfully in download mode because the screen is doing nothing. Completely black, no lights.
Any thoughts?
Click to expand...
Click to collapse
So it's not completely bricked?
Just a question, but from the thread started by k0sh about unbricking, did you try and just leave your tab plugged into a WALL charger for a few hours.
I would attempt at restocking with the OVERCOME stock safe, following their instructions to the tit.
---------- Post added at 04:50 PM ---------- Previous post was at 04:46 PM ----------
It does sound like you are experiencing the same black screen that I mentioned from the other post.
If you haven't done so yet, do try the re-stock instructions from the OVERCOME thread using their stock safe.
It spends most of its time connected to a wall charger.
I'm guessing it's not completely bricked, but it's non-functional to me since I can get zero screen feedback. This means I can't tell when it's in download mode or not.
What's "the OVERCOME stock safe", for reference? I ask because I've followed the instructions on several threads already, and the problem has gotten progressively worse. Also, I've followed instructions 'to the tit' as much as I'm capable so far, so it's not like I'd be doing any different with some new set of instructions. I don't like trying to take shortcuts, though I have to admit that I've had to try to research the meanings of other references made before (i.e. - I have no clue what "OVERCOME stock safe" is, though I assume it's a ROM that I'll have to follow three somewhat-related links to in order to get to the megaupload site to get it).
Addendum to above...
I didn't mean to come off as flippant, though I am a bit on the frustrated side considering every set of instructions I've been able to find to fix my Tab has resulted in it being worse than before the fix.
I'm trying to search for the instructions you reference, but not finding any detailed instructions anywhere. All I find is "flash OVERCOME using Odin" or something similar. As I said I have a completely black screen, so I have no indicator of whether I've got the thing in Download mode. Yes, I found out that it's not completely dead by using Odin to detect a COM connection, but that's not necessarily a guarantee that I have it in Download mode, is it?
GreNME said:
I didn't mean to come off as flippant, though I am a bit on the frustrated side considering every set of instructions I've been able to find to fix my Tab has resulted in it being worse than before the fix.
I'm trying to search for the instructions you reference, but not finding any detailed instructions anywhere. All I find is "flash OVERCOME using Odin" or something similar. As I said I have a completely black screen, so I have no indicator of whether I've got the thing in Download mode. Yes, I found out that it's not completely dead by using Odin to detect a COM connection, but that's not necessarily a guarantee that I have it in Download mode, is it?
Click to expand...
Click to collapse
alterbridge86 has a very well known thread in the Development section (Don't follow the links just yet) that has been around for a while, the OVERCOME team has provided us with many very stable and fast ROMS. To do a nice fresh install of their ROM they recommend doing a flash of a stock firmware to clear all the bits and bytes. If you follow the thread you will notice a detailed (and I mean detailed) instruction setup which is linked below.
Now, I'm not saying that you are not a smart person or anything so don't take any of the following as an insult, I just want to help so don't mind the simple instructions.
If I were you, after downloading all the files that you need for the stock safe stuff, to make sure you are properly in download mode when necessary do the following;
1) start the ODIN software on your computer.
2) connect your tab to the computer, check to see if odin connects
3) If odin connects than your tab is obviously ON, with the tab still connected to the computer press and hold the power button until the tab shuts off, at that point ODIN will disconnect.
4) press and hold the volume down button, then press the power button for a sec or two (the standard way to get into DL mode) and very shortly after you should get ODIN showing that it is connected again.
This will probably indicate that your tab has some functionality that you might be able to work with, but it wont be easy. After flashing anything you should wait a while as everything you flash will require a long first boot. Especially when you can't see any prompts. After flashing the kernel the install guide says you should hear a "sexy robot" voice (STEP 9). The flash will be quick but when the device reboots if you are not hearing the voice DON'T TOUCH ANYTHING, alot is happening in the background give it a good 5 minutes for it to finish (even 10 for safety), it should boot into the stock OS. If you don't see anything reboot your tab by holding the power button for 5-10 seconds to shut it off then turn it back on. BUT WHATEVER YOU DO, WAIT AT LEAST THOSE 5 MINUTES after flashing the kernel because it converts your system from RFS to ext4.
The OVERCOME rom thread is located here
The INSTALL GUIDE is located here
Good luck.
I'm about halfway through the process, and I've already got the screen working again.
I took the initiative to search around on the search string you gave me ("Overcome Stock Stable") and came across the same page you link to above. I was actually just about to post it here for future reference if anyone ever found themselves in my position again.
I'm trying to consider whether to leave it at stock or to flash the Overcome ROM on it. Your thoughts?
(and many, many, many thanks!)
GreNME said:
I'm about halfway through the process, and I've already got the screen working again.
I took the initiative to search around on the search string you gave me ("Overcome Stock Stable") and came across the same page you link to above. I was actually just about to post it here for future reference if anyone ever found themselves in my position again.
I'm trying to consider whether to leave it at stock or to flash the Overcome ROM on it. Your thoughts?
(and many, many, many thanks!)
Click to expand...
Click to collapse
I'm very glad to hear that you got it working, I've got two tabs and half bricked both of them at one point or another. And I find it's actually not that easy to completely screw these things up, they just get frustrating trying to fix.
Anyway, you should definitely try the OVERCOME series of ROMs, they are really good. Lot's of small things that make it worth while as well as big improvements over stock (speed, battery etc.. etc..) I'm running BOCA on mine, had the Honeycomb RC1 on it for a few weeks and now am waiting for these wonderful devs to cook up a usable ICS ROM>
Enjoy
Go to: teamovercome.net and read. Their install instructions are some of the best I've read. These guys are really good.
Sorry I didn't see the second page, that you had gotten the answer already
Related
So here is what I have. One of my friend's girl friend attempted to flash here T849 T-Mobile tablet. I do not have any info on if she attempted with Heimdal or Odin but the result was that it would not turn off. They brought it to me and I ran down the battery and recharched it, I was able to get it into download mode and have attempted several firmwares via Odin. All have passed and installed fine. When I turn on the tablet after the flashes it still has the black/blank screen. I hear the boot sound and the soft buttons at the bottom light up as normal. Its like the screen is dead. I do not believe it is though. Any suggestions?
I have attempted the power+touching screen trick to reset. It resets fine but still no response from the screen.
Like the other ten people posting about a black screen, you have a protected bootloader.
I have been part of this community for about 5 years, I read alot on here dont post alot. I have read all the threads pertaining to that problem but have not found a solution that worked to fix it, or else I would have not posted. So rather than post a smart ass response trying to expose me as a lazy xda newb asking a dumb question how about suggesting something that I have not tried.
As stated in the first post I have done complete stock rom reinstalls and can not see an image on the screen so I can not turn the apk to unlock the bootload. So still no love. Do you have a suggestion?
Also, I have nothing on the screen at all. most of the protected boot loader stuff I have read at least has the phone exclamation triangle computer graphic up. I have nothing.
I gave him the answer and he complains about it.
rangercaptain said:
Like the other ten people posting about a black screen, you have a protected bootloader.
Click to expand...
Click to collapse
Ok, you stated that other people have had a similar problem. The ways to avoid it are in several places in the galaxy tab forums. The ways to fix it I have yet to find. If you are as helpful as you are suggesting would you be as so kind as to give a tip on how it could be recovered? This is not even my tab. I would not have had this problem in the first place.
Hi. I've messed up and seriously need help.
My phone is stuck on the startup-screen showing "GALAXY S GT-i9000".
3 key combination VolUp-Power-Home just swiches that screen on and off.
3 key combination VolDown-Power-Home brings up the Download screen, but can that help me?
It don't seems to be contact between the phone and my Windows 7 PC.
I've found some fixes involving special hardware, soldering and/or resistors. I don't have those things or any experience in soldering.
Is there any way I can save my phone without doing hardware work?
If you have download mode it's not bricked, just flash a rom using odin corresponding to version you already had installed. If you had 2.2 flash 2.2 if you had 2.3 flash 2.3. search youtube for tutorial on how to flash using odin.
mortenarcher said:
Hi. I've messed up and seriously need help.
My phone is stuck on the startup-screen showing "GALAXY S GT-i9000".
3 key combination VolUp-Power-Home just swiches that screen on and off.
3 key combination VolDown-Power-Home brings up the Download screen, but can that help me?
It don't seems to be contact between the phone and my Windows 7 PC.
I've found some fixes involving special hardware, soldering and/or resistors. I don't have those things or any experience in soldering.
Is there any way I can save my phone without doing hardware work?
Click to expand...
Click to collapse
make sure samsung drivers are running
mortenarcher said:
Hi. I've messed up and seriously need help.
My phone is stuck on the startup-screen showing "GALAXY S GT-i9000".
3 key combination VolUp-Power-Home just swiches that screen on and off.
3 key combination VolDown-Power-Home brings up the Download screen, but can that help me?
It don't seems to be contact between the phone and my Windows 7 PC.
I've found some fixes involving special hardware, soldering and/or resistors. I don't have those things or any experience in soldering.
Is there any way I can save my phone without doing hardware work?
Click to expand...
Click to collapse
remove the battery for 2 minutes. put back the battery and go to download mode..
If it was bricked fyi, you'd get no response from any combination
This happens sometimes when you restore a CWM backup, it means ther kernel did not retsore correctly. Just go into download mode and only flash the kernel you where using in your rom, or even one of the kernels like semaphore. Your phone is fine, not bricked.
mortenarcher said:
Hi. I've messed up and seriously need help.
My phone is stuck on the startup-screen showing "GALAXY S GT-i9000".
3 key combination VolUp-Power-Home just swiches that screen on and off.
3 key combination VolDown-Power-Home brings up the Download screen, but can that help me?
It don't seems to be contact between the phone and my Windows 7 PC.
I've found some fixes involving special hardware, soldering and/or resistors. I don't have those things or any experience in soldering.
Is there any way I can save my phone without doing hardware work?
Click to expand...
Click to collapse
I used to be in your situation. I tried re-installing and installing every possible drivers and the computer still wouldn't recognize my SGS. I guess there are ROMs that you can't restore backup from the Recovery Mod. Odin would not recognize your device no matter what. I sent it to a couple of SGS local experts and they said they couldn't do more because they said the damage I did was too major and they have no guarantees that my phone wouldn't get worst after they tried fixing. So they recommended me to Samsung Service Centre.
And this is what they tell me. Your SGS is actually not going to operate anymore unless it is revived. So Samsung will have no idea what happened to it. Blame it on Kies and if your SGS still has warranty, you will get your SGS fixed for free. Cheers
Thanks
Thanks all of you guys for your replies.
I was way down when I wrote the question. I'm new to this sort of problems.
BUT after a lot of hazel I managed to save my phone. I also experienced a bootloop, but flashed a new ROM and came past it.
For a newbe like me its a lot of information out there. To much really, to be able to find what your looking for...
My humble requests to all of you making tutorials:
- Don't expect that everyone knows where to find the files and programmes you refer to. I spent a lot of time trying to find the the ROM I needed.
- zoom in so we can see the file names you are using.
Besides that: Thanks to all !
mortenarcher said:
Thanks all of you guys for your replies.
I was way down when I wrote the question. I'm new to this sort of problems.
BUT after a lot of hazel I managed to save my phone. I also experienced a bootloop, but flashed a new ROM and came past it.
For a newbe like me its a lot of information out there. To much really, to be able to find what your looking for...
My humble requests to all of you making tutorials:
- Don't expect that everyone knows where to find the files and programmes you refer to. I spent a lot of time trying to find the the ROM I needed.
- zoom in so we can see the file names you are using.
Besides that: Thanks to all !
Click to expand...
Click to collapse
As a beginner, you're right: it's a ton of information to absorb, and sorting through the endless tutorials filled with vague terminology you can't even begin to piece together is a frightful journey—especially when you're doing it while your phone sits beside you semi-bricked. But I'm glad you sorted it out! It's an adventure alright. Just make sure you learn more than you lose.
Well guys I’ve been reading this forum front to back for over a week and was scared as hell to mess with my phone, but I really wanted ICS and some of the other nice software I’ve seen here.
Firmware: 2.3.3
Baseband: I9000DXJV9
Kernel Version: 2.6.35.7-I9000DXJV9-CL216763
[email protected] #2
Build Number: GINGERBREAD.DXJV9
I wanted to start simple with a CF root. I’ve read the flashing instruction so many times I thought I could do it in my sleep. So I backed everything up, turned the phone off and back on in DOWNLOAD, started Odin 1.82, loaded the CF root for JVQ (which is as close as I could find worked with my phone), then I attached the USB cable. The first time it started to flash, but it immediately hung while trying to start a connection. I unplugged and the phone was still fine. Started over and this time I saw the drivers install and thought now it should be OK.
Loaded the CF root JVQ in PDA, left everything as default (re-partition unchecked) and the other two checked. It flashed quickly and just as quickly it came up FAILED! Disconnected my phone and now I can’t even get DOWNLOAD. All I get is the silly icon of a phone with a caution triangle in the middle of a dashed line to an icon of a computer and even that won’t go away now. I remember seeing this symbol one time somewhere on this board, but don't remember where.
Looks like my worst fears have come true…a bricked phone on my first try. I never envisioned a situation where I could not get to DOWNLOAD mode and I do know where to buy a JIG, but I think it wouldn't help even in this case. Any help will certainly be appreciated.
khrfx4 said:
Well guys I’ve been reading this forum front to back for over a week and was scared as hell to mess with my phone, but I really wanted ICS and some of the other nice software I’ve seen here.
Firmware: 2.3.3
Baseband: I9000DXJV9
Kernel Version: 2.6.35.7-I9000DXJV9-CL216763
[email protected] #2
Build Number: GINGERBREAD.DXJV9
I wanted to start simple with a CF root. I’ve read the flashing instruction so many times I thought I could do it in my sleep. So I backed everything up, turned the phone off and back on in DOWNLOAD, started Odin 1.82, loaded the CF root for JVQ (which is as close as I could find worked with my phone), then I attached the USB cable. The first time it started to flash, but it immediately hung while trying to start a connection. I unplugged and the phone was still fine. Started over and this time I saw the drivers install and thought now it should be OK.
Loaded the CF root JVQ in PDA, left everything as default (re-partition unchecked) and the other two checked. It flashed quickly and just as quickly it came up FAILED! Disconnected my phone and now I can’t even get DOWNLOAD. All I get is the silly icon of a phone with a caution triangle in the middle of a dashed line to an icon of a computer and even that won’t go away now. I remember seeing this symbol one time somewhere on this board, but don't remember where.
Looks like my worst fears have come true…a bricked phone on my first try. I never envisioned a situation where I could not get to DOWNLOAD mode and I do know where to buy a JIG, but I think it wouldn't help even in this case. Any help will certainly be appreciated.
Click to expand...
Click to collapse
JIG will most likely save your day, because you can have hardbricked phone only by messing with bootloaders AFAIK. And as CF-ROOT doesn't touch bootloaders, you'll be fine..just get jig and continue flashing
ps. I assume that you have tried taking battery off, inserting it while pressing 3-button combo etc. methods which you'll find around the forum..dunno even if they actually work..
Last time i got exactly the same situation when flashing CF root for 2.3.5 XXJVS..
Try connecting the phone to the comp with the phone, triangle, and comp icon on your phone screen, see if Odin detected your phone...
If yes, you can try flashing the whole stock firmware again, it should work...
i got into that situation twice and those steps always worked for me luckily.. (it works for me, saved my bricked phone)
wish you luck
asdsadas2010 said:
Last time i got exactly the same situation when flashing CF root for 2.3.5 XXJVS..
Try connecting the phone to the comp with the phone, triangle, and comp icon on your phone screen, see if Odin detected your phone...
If yes, you can try flashing the whole stock firmware again, it should work...
i got into that situation twice and those steps always worked for me luckily.. (it works for me, saved my bricked phone)
wish you luck
Click to expand...
Click to collapse
Now your solution may be exactly what happened. I tried to connect using Kies, but my computer never even saw a device being plugged in so I never even thought to try Odin.
So I must apologize. I didn’t have the patience or perseverance to wait for an answer. I happen to live in a large city in a country that has a lot of clever tech people and phones are huge here in Thailand.
I was either going to buy a cheap phone so I could stay in basic contact until I worked through the problem with the help of this board or buy a new Galaxy S, instead I decided to see if someone here could actually get me back up and running in short order. Fortunately I found one shop that did. I watched him load up Odin, pick the PDA, PHONE, CSC and PIT files and re-partition, but I don’t know how he got a connection to Odin, because that’s where I was stuck.
I certainly could no longer get a connection via Kies or the drivers I had which were working just a short time ago. So the question I still have is how the heck did he get a connection to the phone?
Of course it would be too much to ask for him to load the original software so now Kies will not work with my phone, but that doesn’t bother me so much because I really don’t use it. He installed 2.3.2, Baseband XXJVE, Build Number XWJV1, which is a step backwards, but it works, although I’ve gotten one screen with tiny red letters in the top-left corner that said “panic kernel”, but after a reboot everything has been fine. BTW, the repair cost just under $15 USD.
Here's another question while I'm at it. What causes this to happen? I thought for sure I did everything I've read a 100 times on this board in the proper order.
Buy a Jig at eBay
Well, yes JIG will most likely save your day.
BUT
Try those meanwhile you wait for JIG:
1. take battery out and leave it few hours maybe and than try to boot download mode (increase times-hour, 2 hours, 4 hours,....)
2. press buttons for download mode (that phone and pc connected with dots and triangle will most likely appear), plug your phone to PC and try different USB ports and see if odin finds your phone, it happened to me once, however odin did
find my phone on that pic and i flashed (dunno why, maybe just luck)
3. take battery out, press buttons for download mode, and put battery back in, it can trigger download mode (found this by googleing sometime ago)
Or try google for more solutions, allthough I reccomend JIG
I know about the JIG and where to get one, but it ain't gonna happen soon and I'm sure this guy yesterday did not use one and he was confident he could restore the software and he did, so there is a way without the JIG.
gaspernemec said:
Well, yes JIG will most likely save your day.
BUT
Try those meanwhile you wait for JIG:
1. take battery out and leave it few hours maybe and than try to boot download mode (increase times-hour, 2 hours, 4 hours,....)
2. press buttons for download mode (that phone and pc connected with dots and triangle will most likely appear), plug your phone to PC and try different USB ports and see if odin finds your phone, it happened to me once, however odin did
find my phone on that pic and i flashed (dunno why, maybe just luck)
3. take battery out, press buttons for download mode, and put battery back in, it can trigger download mode (found this by googleing sometime ago)
Or try google for more solutions, allthough I reccomend JIG
Click to expand...
Click to collapse
This was a very useful reply and I thank you for it. Mail here is unreliable so I won't have a JIG until April when a friend brings one over, though Hong Kong sells most of them on eBay and some of them do deliver here free. I might try to get one from there.
Anyway, if this does happen again I have a couple of other things to try thanks to you.
I thought about Google (of course), I'm just not sure how to word the search with the phone+triangle+computer icon, but I'll give that a go also.
Kurre and asdsadas2010 also gave useful replies...Thanks.
I didn't think it would be that easy to find, but the first result in my search that popped up was this thread here: http://forum.xda-developers.com/showthread.php?t=751210 and here http://forum.xda-developers.com/wiki/How_to_get_into_download_mode
Lots of variations on similar solutions. Really no need to add to this thread anymore.
Thanks
Like the title says, I will paypal $15 (or more if you give me extra help) to whoever can help me root and upgrade my Galaxy Tab SCH-i800. I need it rooted and an upgrade to 4.0 or higher would be nice. I've tried one click roots and none worked. I've tried following youtube videos and they never turn out to work. Seems like cyanogenmod would be the best route, but I just can't seem to get it right.
Now, I've done my fair share of computing: I'm familiar with torrents, keygens, cracks, I've also accomplished several circuit board repairs for my car stereo, car window switches, and my macbook. But when it comes to software I'm more of an apple person, windows and android frustrate me.
I should also mention I made another attempt to root my tab last night. I was following a youtube video on how to use heimdall and I got pretty far and everything seemed to be working, but after the part where heimdall automatically reboots the tab it booted up like normal, but the touchscreen doesn't work. it senses my finger but the directions are off, like up is right, and down is left, and vice versa. Now I need to figure out how to fix this.
I'm exhausted after spending hour after hour googling all these problems and trying to understand all this android and root lingo. I figure I should just have an expert completely walk me through it so I can stop wasting my time sitting in front of my computer and so I don't mess up anymore.
Thanks!
You can try
http://forum.xda-developers.com/showthread.php?t=1585619
it is for Sprint tab, but will work on Verizon tab.
priyana said:
You can try
http://forum.xda-developers.com/showthread.php?t=1585619
it is for Sprint tab, but will work on Verizon tab.
Click to expand...
Click to collapse
I'm sure this is helpful, but the problem is I don't understand what all of this means, I've tried figuring it out but I screw up everytime.
Firstly, do you have access to a windows or Linux machine ... Aka not a mac
jim80b said:
Firstly, do you have access to a windows or Linux machine ... Aka not a mac
Click to expand...
Click to collapse
Yeah I have a pc with windows 7. I've tried several attempts with heimdall and I finally got it to work after watching a few youtube videos, and it rebooted my tab and I thought I finally got it, but when it turned on things were very messed up. the screen digitizer is Waaayy off, up is right, left is down, and vice versa. I don't think its communicating with the battery correctly since it says it been 100% for 3 days straight. also a big problem is it won't turn off.
I must have loaded the wrong file for something in the process and got something screwed up. Should I download all the stock firmware or software and reload it on my tablet?
Also back to rooting, I was talking to someone and they suggested I use odin instead of heimdall, they think I will have better success.
Also since I have your attention, I want to upgrade to 4.0 or higher. Do I root before I upgrade or after?
Thanks!
There are many resources on these websites... Www.xda-developers.com and www.rootzwiki.com. check out the forums for the galaxy tab. Both have step by step instructions on doing this. When looking for Roms, make sure you download the p1c ROM. Cyanogenmod and other roms use that designation. That is for the CDMA tab (Verizon and sprint). I've used heimdall and Odin. IMO they are both equally as useful and user friendly.
If your tab doesn't shut down, hold the power button down for about 8 seconds. It will shut down.
Which ROM did you flash when you started seeing the touchscreen problems?
Hang in there. I remember when I started tinkering with rooting and flashing Roms. It takes some time to understand and get it right. Hang in there.
Sent from my SCH-I545 using Tapatalk
Carson-TL said:
Yeah I have a pc with windows 7. I've tried several attempts with heimdall and I finally got it to work after watching a few youtube videos, and it rebooted my tab and I thought I finally got it, but when it turned on things were very messed up. the screen digitizer is Waaayy off, up is right, left is down, and vice versa. I don't think its communicating with the battery correctly since it says it been 100% for 3 days straight. also a big problem is it won't turn off.
I must have loaded the wrong file for something in the process and got something screwed up. Should I download all the stock firmware or software and reload it on my tablet?
Also back to rooting, I was talking to someone and they suggested I use odin instead of heimdall, they think I will have better success.
Also since I have your attention, I want to upgrade to 4.0 or higher. Do I root before I upgrade or after?
Thanks!
Click to expand...
Click to collapse
Can you boot into recovery by pressing power-on and volume-up keys together?
If you can and you have installed a correct CDMA kernel via Heimdahl everything can be worked out and you can get to 4.0, not latest 4.4.2 though at this point.
However, the behavior of your screen suggests you installed a wrong kernel...
Hm
I've recently rooted/flashed my newly acquired sch-i800 to all kinds of roms. if you want me to zip up the heimdall files i've used, let me know.
alternatively, this is the guide i used:
well due to being a new member it wont let me link, pm me for a link to the guide i used.
the first rom i successfully flashed was the p1c download cm9.1 and corresponding gapps
Soooooo, I installed a new layer and the phone borked, hooked it up to the unbrick restore tool kit, it flashed the whole rom and failed after 100%, Now when I connect it it gives me this. Any help?
Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Can you get into recovery and reformat?
Maybe as of now, try to follow this post.
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I assume you have tried the restore method posted by tomsgt. And on that thread there are a few other posts same error as you
Hello, the recent bricks appear to have something to do with a guide posted by a user recently. If you have bricked your phone, please join the hangout below where we will cooperate with you to investigate the cause of your brick and attempt to find a fix.
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs
Various from errors
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?
Persuasion89 said:
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?
Click to expand...
Click to collapse
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op
mrmazak said:
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op
Click to expand...
Click to collapse
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.
Persuasion89 said:
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.
Click to expand...
Click to collapse
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.
mrmazak said:
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.
Click to expand...
Click to collapse
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.
Persuasion89 said:
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.
Click to expand...
Click to collapse
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.
Yeah exactly what I'm dealing with, well first I was getting a flashy home screen after boot. Re flash didn't work so I took the bad advice of format+DL. The thing I don't get though is if it's not the preloader then why won't ANYTHING flash.
Have you tried a read back? Because every option on my end is just a brick wall right after initialization. I figured if preloader is intact then it would at least attempt to read the memory blocks, or let me attempt a format, or anything. My phone's picked up properly by two PCs, and really the red bar is the da handshaking the preloader to lock the phone in that state during the flash right? Or Chinese to English translation is more difficult to understand than I expected.
Regardless I'm just a noob with too much free time. I'm Trying to make a bootable drive for my laptop so I can put in work, but latest Ill be at it here in a couple hours once I'm free. I'm convinced this is fixable so I'm going to pull everything I can from the working phone and see what I can figure out. Ill be back to consult the thread before I do anything big though. Hopefully I can contribute some to this. I have a vision of how this is going to work, but I couldn't explain it for the life of me.
Gytole said:
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.
Click to expand...
Click to collapse
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
mrmazak said:
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.
Click to expand...
Click to collapse
How difficult is it to remove? I'm assuming there's some soldering involved?
Persuasion89 said:
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
How difficult is it to remove? I'm assuming there's some soldering involved?
Click to expand...
Click to collapse
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.
Gytole said:
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.
Click to expand...
Click to collapse
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.
Persuasion89 said:
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.
Click to expand...
Click to collapse
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though
just see something about vcom drivers. and the op screenshot shows usb driver(lower right corner of photo). it should be a vcom driver(lower right corner of photo)
mrmazak said:
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though
Click to expand...
Click to collapse
so i have a full rom backup. or at least it should be. I also have a full TWRP backup i cant use on my SD card. MT Droid tools doesnt support this chipset though, so I dont know how else to get this readback i did chopped into partitions.
Just wondering, how many phones are bricked? Of these bricked phones how many were caused from flashing witha VM? And how many used the format function to try and recover?