Database Develop

Galaxy Tab bricked.. like really bricked

Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks

Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App

Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d

Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...

Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks

You need to make sure samsung kies are not running for sure unistall it and try it again

use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day

Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App

Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse

I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...

Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.

Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.

Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer

HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.

One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2

...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?

[Q] Failing to flash on the actual phone, not odin.

Hey guys, first post. And well, as the video said, I'm a noob!
So I've tried two different guides, but am currently trying to implement this one in different ways.
Now, I do all the steps in order to get the phone connected, which it finds and is successful. I was trying to install the firmware as a single package. Which on the program(odin) side. All goes well.
Now the issue is, which I can't find on the forums or with google. Once the phone boots itself up during the process and the firmware is sent to it. On the screen for a moment I see some debug looking text scroll. It shows 2 folders system/ something. But I can't quite make out the rest as it does this very quick. Regardless, I think it has something to do with access is not allowed? So it quickly skips that and the phone boots up normally. So nothing is installed, and the normal firmware with all the bloatware is just loaded back up.
Odin then just waits a few more minutes and passes it. But obviously nothing happens.
I tried rooting the phone, which was successful. But it didn't help me in attempting the above method again.
I've attempted with odin as well doing what the above guide states as well here "If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY". But in doing so, adding the file to the PDA section, odin reports it's an invalid image type. Then seems all good, but I'm worried in doing it this way, in case I end up bricking the phone.
I been trying to install the firmware "S5830XWKT7_S5830OPPKS6_S5830XWKT3_HOME.tar.md5" Which is the 2.3.6 Australian one.
Any help would be appreciated as to why it's failing on the phone end of things. As the program does seem to issue to use, as it does successfully transfer everything in the first place.
Thanks guys,
Myth.

[Q] Forgot USB-debugging downgrading

Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh

emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?

arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:

emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]

th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..

SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:

emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!

SM-N9208 Duos China Phone (Cloned) Need help!

Hello! I am currently new here and a newbie when comes to this stuff. Anyway, to get to my point, my cousin gave me an SM-N9208 Duos but it was a China phone and he said that it was a cloned phone. I still accepted it though but when I was attempting to use it, I noticed that it had a lot of issues and pop-up messages which annoyed me. When I asked him what he had done to the phone before handing it to me, he said that the phone had a lot of viruses and malwares. I attempt to hard reset it through recovery mode and through the phone system itself but it was no use, it still goes through the same window "Unfortunately, CPS has stopped" on both hard reset attempts. It also keep installing apps that has korean or chinese women on the icons. It keeps spamming any app installations when I connect it with my WIFI connection.
Also, any other issues was that when I attempt to flash the stock rom of it using ODIN3_v3.10.7, it doesn't recognize the device, I also attempt it to connect the device as USB storage and I can still read the device using adb devices from CMD and but still no go with ODIN3. I even attempted having the device go through recovery mode but still no go too. I attempt to install Malwarebytes app but it doesn't ready any viruses or malware on the device.
Just to let you guys know also that when I attempt to do the download mode, it just shows 3 options, recovery, fast boot and normal boot.
This is kind of sucks to my end and I really need help with it. I will really appreciate it if anyone can help me on this.

Expanded FIX for Touch / Calibration Screen Issues

My Touch Screen DiED!!! (A Sad Story that Ends Happily)
I have flashed many a rom on my N910T Note 4. But yesterday I thought I'd update my TWRP install, and elected to use the new TWRP app to do so. Right TWRP file (double-checked). Fired up the app... and apparent success. On reboot, however, what looked to be
*DISASTER*
I touched my screen but nothing happened. Then I moved my finger and something elsewhere than under it opened up. In short, the sensors had become non-calibrated - they no longer properly detected where on the screen I was touching. The fact they did at all was better than nothing... but not much.
First, then, I did at least have some ability to still do things.
Second, better, I found that the s-pen's sensors worked just fine! Boy, was that helpful when it came to trying to type in my pin number / password.
Third, initial looks on the ol' google revealed people saying I'd have to buy a new sensor for the touch screen. Arrrgh!!
BUT THEN THE GOOD NEWS... I HOPED!
I discovered a number of folks suggesting what sounded almost James Bond-ish... a code, input into the phone touchpad, that when "called" could result in a calibration reset. Over and over again, there it was:
=================================
"dial *#2663# and update the touch FW by pressing TSP FW update (General)"
=================================
Okay, said I. Tried it from my new TWIZd rom. But no love. I got an error message. But then it occurred to me to read the many posts on this code more carefully... and sure enough, they did suggest that using the OFFICIAL rom provided by Samsung/my provider was necessary. Sigh... that meant navigating TWRP -- which by the way was also affected by the bad calibration. It was doable... just... by figuring out where my touches were actually activating the screen (it was less severely affected at the top but very severe near the bottom). Eventually got the phone wiped (Thank God I had just backed up my sweet TWIZd install to the ext sd card!). Luckily, I had a generic old copy of my phone's original rom on the ext sd, though it was one that had been debloated and rooted. I hoped it would work....
The flash hung. Forever. heading for 20 minutes. Finally I pulled the battery, not hopeful, and restarted the phone. *WHEW* it came up with the rom installed. Skipping both google and samsung installs, I went right to the Home screen and used my s-pen to type in the code then hit the call key.
Up came a screen of buttons, including a greyish TSP FW update (General) button. (See pics; neither is a Note 4 but both give accurate idea of what the screen looks like when the code given above is dialed in and works correctly.)
I tapped it with the s-pen.... and my screen was fixed!!
I made sure to use TWRP to backup that generic rom to my 128g external sd card - that way if this happens again I can "restore" it via TWRP and repair the phone quickly.
One thing is for certain... I sure appreciate this community of folks, which is where I found much of the info. And I will not be using that TWRP app (created by commercial interests anyway) again. Back to installing TWRP the old way, via either a *.tar TWRP file and ODIN via a PC or via flashing an *.img file w/ TWRP itself.
That's my story and I'm sticking to it.
Hit thanks if you found this amusing / helpful / or just plain odd.

Hi,
SO...I am pretty much in the same boat you were... but I have not been able to get the dialer thing to work...
when I type it in, it just flashes something to fast to see.. and then says "MMI complete" .
So far the ONLY thing I have done with this phone is root it (using Odin and chainfire) ... and install the wrong TWRP ... and then install the correct TWRP.
As far as I know, I still have the original ROM on it! I had not gotten to the point putting a rom on!!
Any suggestions?
Thank you for any help...

Thanks Shonkin, this worked for me on my SGN4, after flashing the bootrom with a Vodafone stock image.
Much appreciated