Related
Well, I've bricked my three week old Verizon galaxy tab trying to flash the stock firmware back to the device to try and get the recent Verizon update working, which has been failing consistently. I've thoroughly read through every thread on the forum I could about the black screen of death, so I understand there's a good chance I'm pretty screwed here. I have a couple more questions on the subject, but I understand that I might not be able to get answers for them past the information that's already available.
I'll start by describing my setup and how the flashing process went wrong. I was using the stock Verizon ROM with Boushh's Voodoo Plus kernel v3, converted to ext4 of course. After the recent Verizon update failed to install on my Tab I followed through all the suggestions on the CDMA VZW Tab update thread, downloaded the update zip, put it on the sdcard, ran from rescue manager, unrooted, reflashed stock, wiped data and cache, re-ran from rescue manager at first boot... nothing worked. Things went really wrong when I tried flashing the entire ROTO backup of the Verizon stock ROM. I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
* I've seen it suggested that the tab be left to drain for days or weeks, but not many reports that this worked out in the end. My battery was at about 45% percent when this whole thing went down. Should I even bother waiting? My only alternative at this point is to send the thing to Samsung for repairs which breaks my heart. Verizon won't replace it as I've had it for over two weeks.
* Could a homemade USB jig help me in this situation? I have some soldering experience but I heard that it won't help if the screen won't turn on. Ideally I'd buy it online, but I couldn't find one for the Galaxy Tab on ebay.
That's it I guess, but any information you can offer pertaining to this problem would be appreciated. Thanks!
to be honest, i do not know why people think they can brick the tab.......the only way is to throw it from a building.
Just go to overcome forum and follow this (i 'bricked' my tab a 1000 times):
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
you also get the link for the p1 file you need.......easy
This sounds like very useful information, thank you. I'll definitely do this if I can get the Tab to respond to anything I do, which I can't so far. It won't turn on regardless of what volume button I press or not press. I'm pretty sure I had it connected to the PC while trying to put it in download mode just to see if it would be recognized as USB device despite the screen not turning on, but I'll try again to make sure when I get home.
Edit: Yeah, no luck. Not recognized as a USB device, which makes sense seeing as the screen doesn't even turn on.
I am having the same issue... My daughter put my computer to sleep while I was flashing back to stock using heimdall. Any luck getting your Tab to power on?
nirslsk said:
I had the bright idea of setting up Heimdall to flash every file of the backup it had a slot for, including the pit file, zImage in kernel and recovery, factoryfs, param.lfs, cache.rfs, dbdata.rfs, modem.bin, boot.bin in primary bootloader slot and sbl.bin in secondary bootloader slot. When I pressed the start button it grayed out and nothing was happening. I waited a few minutes and finally turned the tab off. When I turned it back on again and tried to put it in download mode, the phone -x- computer logo showed up which freaked me out as I've never seen it before. Still, the computer did recognize the tab as composite USB device and so, unwittingly, I tried flashing with heimdall again. The flash went along perfectly well, but when it was finished both heimdall and the tab just hung there. I waited a few more minutes and turned off the tab again. After that it never turned on again. My questions, based on what I've read about the black screen of death so far are these:
Click to expand...
Click to collapse
same problem
If your tab is showing any sign of life then you are not bricked and just need to keep at it until you find a solution. When you have exhausted all other resources you can send it off to get it fixed. I ended up bricking my tab when a flash was interrupted to the point that there was no sign of life at all. I found someone here who could fix it for $50 and had it back within the week working as it should. I highly recommend his service as a last resort.
His screen name is connexion2005 and here is a link to his profile.
http://forum.xda-developers.com/member.php?u=1602851
Hi people,
I have just got a Galaxy Tab just for kicks. It's a P1000L brazilian one.
I want to unbrand it (it's Claro branded, the operator took out Gmail and Gtalk, also assigned search to Yahoo instead of Google), so I have talked to a friend which also has a Galaxy Tab, same model, but unbranded, all Google apps inside.
My FW is (or was ) P1000LVJJJ4, and his FW is P1000LVJJM9, so I went to this thread at TheGalaxyTabForum, downloaded the P1000LVJJM9 FW, PIT file and ODIN 1.3.
http://www.thegalaxytabforum.com/index.php?/topic/112-samsung-galaxy-tab-firmware-list/
I have read about the process and started doing it. Here's what happened.
I haven't checked the partition option, just put the PIT file and the FW file in the correct fields, put my Tab in download mode, clicked start... and after some time, almost at the end, ODIN failed. My Tab got stuck in download mode, yellow triangle. I got it disconnected from the USB cable, than put it again. Restarted the process, but ODIN got stuck in setup connection.
I took my Tab off the usb cable again, it was still stuck in download mode, yellow triangle. Pressed the power button for a while, it has turned off completely. Now it's bricked, maybe dead. No life signal, nothing happens when I press any button or button combination, nothing is shown when connected to the charger or USB, not recognized in KIES and ODIN, nothing at all.
Is there any hope for me? What can I do to solve this?
same problem here any help plz ?
Generally its a brick when it can't be recognized in Odin or Heimdall... This is because you can't flash anymore.... Best bet is to try a warranty repair....
Good luck...
so... anyone help me please?
Hello everyone I am sure that there is a lot of this thread going.
But I think mine is even worse.
the problem:
I rooted the device, everything worked fine ( did it with card reader - because my pc can not recognize the device had the problem a long time ago, somehow it worked then, but does not now, giving me the code 10 and 43
I think my USB port on the SAMSUNG might be damaged, because it does recharge but wont connect at all, tried kies, tried all the debugging modes, drivers, turning off the computer, rebooting all that stuff..)
The main problem is I flashed the cwm, rebooted, worked fine, then I clicked the do Backup thing and from then I can only go to yellow "downloading" or samsung logo, cannot even use that "Odin" because my USB is apparently damaged.. Any Ideas at all other than taking the phone and throwing it into the dumpster?
it is gt-s5830
my system is Win7-64bit
any help will be deeply appreciated ...
sincerely Fariel2012
Samsung logo freeze, cant recovery, can download mode (cant join to pc)
try with different usb cable
daniga74
Fariel2012 said:
Hello everyone I am sure that there is a lot of this thread going.
But I think mine is even worse.
the problem:
I rooted the device, everything worked fine ( did it with card reader - because my pc can not recognize the device had the problem a long time ago, somehow it worked then, but does not now, giving me the code 10 and 43
I think my USB port on the SAMSUNG might be damaged, because it does recharge but wont connect at all, tried kies, tried all the debugging modes, drivers, turning off the computer, rebooting all that stuff..)
The main problem is I flashed the cwm, rebooted, worked fine, then I clicked the do Backup thing and from then I can only go to yellow "downloading" or samsung logo, cannot even use that "Odin" because my USB is apparently damaged.. Any Ideas at all other than taking the phone and throwing it into the dumpster?
it is gt-s5830
my system is Win7-64bit
any help will be deeply appreciated ...
sincerely Fariel2012
Click to expand...
Click to collapse
Hi there
you will need to give a usb jigg service to your device and then flsah it back to stock using odin
SGA s5830 stuck @ boot logo
I follwed these steps before it stuck @ boot logo
1 rooted phone through root_S5830.zip file
2 then used 6.0.4.6-cooper_fix.zip cwm recovery
3 decided to flash Touchwiz-Resurrected_ROM_V1.0.zip rom
4 followed all steps to flash thrrough CWM recovery
phone reebots samsung.com logo>> samsung boot animation shows up>>samsung name appears again keeps glowing and phone restarts!!!
after it I tried 6-7 different roms then i tried to flash through odin but wasnt able to do so but failed the device showed up in odin but wasnt able to flash stock rom
then i decided to go for Phil touch recovery I installed Philtouch recovery and tried to flash a custom rom now I'm stuck again at boot name GALAXY ACE s5830 nothing goes further!!!
I searched over XDA and some guy quoted this problem is solvable by using odin and putting phone in downloading mode (vol- button+home button + Power on ) I am able to put my phone in downloading mode, but when i conncet it to PC it says USB device not recognized WTF!!!!!???? 10 mins ago i connected my Phone using same cable same port same odin now this ***** appears ???
I swapped PC's, Cables, ports everything nothings working , phone wont start stuck @ boot logo pls help ASAP :crying:
That's it.. You have hard bricked your phone that's dead recovery and dead download mode. Give your phone the usb jigg service which will force it to go to either the download mode or the recovery mode whatever you want.
Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi
It is exactly this: just another bricked Note thread.
ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi
Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?
If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?
AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.
Part of the "hardware" is your battery...
Hello
I have a mini S3 and went to install CyanogenMod on it but the ODIN stopped in the middle of the installation, causing the Android stay corrupted and whenever I called this message appeared: "firmware upgrade encountered an issue. Please select recovery mode in kies and try again "
So I downloaded the original S3 mini according to my country and everything and I install ROM, well, the installation took place correctly but leave it stuck in boot start screen showing the phone model, then I install the ROM again but the ODIN stopped again and there came the problem ...
it does not turn on the power switch and the only way to 'make it light up the screen' is connecting the USB, but when I plug the cable it gets on and off the screen repeatedly at the "firmware upgrade encountered an issue. Please select recovery mode in kies and try again " until I remove the cable and the phone turns off completely.
I hope you guys understand my problem and can help me please.
Already grateful : )! (sorry my english)
Try another computer or another cable. If it is stuck at boot screen, do a wipe/factory reset in recovery menu
Can't power on and enter on recovery menu
JanniekM00 said:
Try another computer or another cable. If it is stuck at boot screen, do a wipe/factory reset in recovery menu
Click to expand...
Click to collapse
I can't do wipe/factory reset in the recovery menu because i can't power on at all. It keeps only blinks (on and off) all the time when its plugged on PC or charger.
Thanks very much for your support!
Did you see the s3 mini logo if you turn on the phone. If you see this works download mode then? if not then your phone is bricked....
When you try and turn the phone on does it display the phone name? Or does nothing happen? If you get nothing then I'm afraid it's bricked. I'd try a different computer, different lead and possibly a different windows os. Then try and flash a stock rom using odin and be 100% sure it's for the model of the phone you have as there's loads of variants of the s3. Other than that, I can't help you any further
Hi everyone,
At first sorry for my english. I`m Dawid from Poland
OK, so i have gt-i8190N and when i trying to turn it on i see only white screen. Screen is ok because i can run phone in download mode.
Of course everyone says " so try to flash rom by odin" but i can`t because in odin i have error "FAIL Get PIT for mapping There is no PIT partition". I was try to flash rom with PIT file (to i8190N and i8190) but without succes.
Are anyone have the same problem?
I was try OneClick also.
Thanks for any answer.