Database Users

Black Screen Vibrant

Okay, I know there is many post about this, but none seem to answer my question or help me. I have a Vibrant and I've been searching this site along with google to help fix my phone.
I brought it off a friend so warranty won't happen since T-Mobile is being asses. My phone is suck on the black screen after it passes the big S logo. It stays black, and I get 4 lights bright on the buttons. I've reflashed my phone with Odin and it has not worked. I think it correctly as well. Com3 was on, ran the stock Vibrant with Pitt and Tar with PDA one. That had only got my phone off the complete brick that my phone had gone through, when It wouldn't even turn on.
I got the brick off and now I'm stuck with this program. I did have a one click root fix and I was trying to mess around with clock work. To help answer some questions. No, I can not boot into recovery mode. Yes I have cleaned and wipe out cache. Yes I can go into Download mode, but its pointless since odin doesn't do much for me. No I can not go into the phone since the black screen is there and no I can not flash a update file for some reason.
Saying that, I would be grateful for some help and before hand I thank anyone who comes across this even if they don't help, just for taking time to read this and maybe referring someone else to help me or even pointing me in the right direction. Thanks and once again PLZZZZZZZ HELPPPPPPPPPPPPPPPP.

No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?

zephiK said:
No, odin is not "useless." I'm pretty positive that you applied Odin wrong.
- Check the MD5 on the files you downloaded; verify they are indeed identical.
- Search for development forum for "drivers"... theres a thread posted by TGA_Gunner. Find that thread and download the version respective to your OS (x86 or x64). This one is proven to work.
What exactly happened in Odin?
Click to expand...
Click to collapse
Okay. One thing I notice when I try to put my phone into the Android system recovery it says this "
-- Movi_check start .. !!
checksum confirmation need _checksum [1301305579]
MBR _Chksum in header :4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MBR Checksum Error
Movinand Checksun Confirmaton Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti - CSC ...
Installing Muti - CSC "
Another thing, I hit reinstall packages and It says "
-- install from sdcard...
finding update package ...
opening update package ...
E: cant open /sdcard/update.zip
(no such file or directory)
installation aborted.
the drivers I use are the samsung Vibrant drivers for windows 7 64. I know it works because the phone before didn't come up when I didn't use the driver. It always failed and when I install it, than it read my phone. When I connect the phone to the computer, the phone does read it and on odin, it says com 3 in yellow. I than Install pitt and install tar.
The tread you sent me too, I actually went through there before. Both of those drivers didn't work but I found one for windows 7 and it started working for my computer. I could tell it works because the computer actually reads the phone and so does odin. Like I use odin right because it goes through the phone and than says pass at the end. so like WTF lol. I'm pretty sure I'm doing it right tho
Another thing. I used odin a few seconds ago, got the phone to run and it went through the green bar and a blue screen now saying reset came up. My phone than went into androids recovery mode but it started to wipe out data. When doing so, the data said wipe fail. It booted up and now back to the start. Black screen, 4 panels on the bottom lit up and nothing to do.
I'm starting to think it has to do with clockwork I did a partition in it and every since than my phone has been doing this blackscreen with 4 lights.

ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work

same thing here, know idea, odin says everything passed but still the black screen and four buttons. i also noticed that the sound and tmo splash screen are not in sync. no idea ???? help would be great!!!!!!!!!!! same errors though. also from the partion feature in clockworkmod.

i assume your on windows i don't keep up if there is a working version for mac. Anyway, make sure your update.zip is just named update DO NOT add .zip yourself or the phone for what ever reason sees .zip.zip. I would also go ahead re download your odiin files just to make sure non of them are corrupted for what ever reason.

files all check out good, i can't gain access to the phones sd, i have flashed this thing with every checked build i could find, all with the same result. the master boot record is not adding up.? still have know idea.

have you tried using this.. http://forum.xda-developers.com/showthread.php?t=740558
this work for me and was able to flash to stock..

somebody please help I'm experiencing the same problem as the OP? can somebody point me in the right direction I've been looking for hours

Instead of making us read the entire thread perhaps you could summarize your specific problem.
My initial impression goes like this.
1. Get into download
2. ODIN back to STOCK 2.1
Run odin in admin mode
Use rage against the cage
After getting back to stock Recovery 2e go ahead reroot and flash away
Sent from my SGH-T959 using XDA App

Don't know if this is still an issue, but here's how I fixed it.
http://forum.androidspin.com/showth...yo-That-does-not-Brick!-Downgrading-Is-Fine-)
Downloaded this file knowing it wouldn't work, Had ODIN flash it and got into this weird recovery screen. Just pulled the battery and then flashed back to stock using ODIN.
Helped me out.

Use 512 .pit and True Stock 2.1 from this post
http://forum.xda-developers.com/showthread.php?t=747335
And quit messing with your phone! lol

This is how i fixed mine too, my phone would go through a seemingly normal start up, but the UI would never load and it would stay on a blank screen.
Flash Eugenes373s froyo that doesnt brick. once it brings you to the recovery screen, pull the battery and once again use odin to flash back to stock. the phone should boot up now.

mnm0071980 said:
ANY body ?
help would def be appreciated and even donates if possible. I just need my phone to work
Click to expand...
Click to collapse
Hey i just encountered the same exact problem four days ago except i flash with odin it says pass but im still stuck on a black screen after the s logo my problemwas encountered by tryig flash a kernal. Please tell me that u found a solution

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??

I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line

UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:

Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:​
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

How is that going to take away the udc start?

I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.

Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.

FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade

So I am guessing there is no way to downgrade the boot-loader without unlocking it?

FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.

Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:

Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.

summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.

[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...

Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.

ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.

FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...

ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.

re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!

summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.

Samsung Galaxy A8 (A-800I) Stuck on Logo Screen with red Custom Binary blocked by FRP

Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.

rissered said:
Hello all!
First of all i want to thank this site (and the people behind it) that makes everything android possible.
I feel privileged to be a member of this forum specially on rough times like what i am facing right now.
I rooted my Galaxy A8-A800i the other day and everything went great. I followed the instructions that i found here. Unfortunately, yesterday i turned off the OEM Unlock on my phone. Now, as the thread title says it. it is stuck on the Logo Screen with the annoying " Custom Binary blocked by FRP Lock ". i read a guide that ashyx made and i felt stupid. I didn't know that turning the OEM Unlock will do that to my Phone.
Right now, I am digging deep on this forums to try and revive my phone that is currently in Brick state.
i am downloading a firmware from sammobile for my phone, the problem i have is... i don't know how to use it. I don't know much about my phone but I do want to learn a lot and i know that this is the right place. I would like to ask assistance on how to use the firmware that I am downloading right now, and also, can i make the Knox Counter go "0" again?
Thanks for everything guys. I highly appreciate everything i've learned here so far.
Click to expand...
Click to collapse
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0

nepalbiraj said:
you can try flashing the official firmware I hope it fixes your phone.
and knox cannot be reset to 0
Click to expand...
Click to collapse
Thank you!... i downloaded the stock firmware from sammobile. but whenever i extract it there's a rar message saying it is corrupted so i DLed a new one, it has the same result. I haven't tried using it to fix my phone but i will try right now. Ill give an update on how it goes.

Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip

rissered said:
Tried flashing the new firmware but Odin can't detect my phone. i have the latest Driver for SAMSUNG and i have the latest Odin. I tried restarting my phone and my computer several times but it still fails. i am really frustrated and our of options right now. Even if Odin detects my phone there's no guarantee that the stock firmware will be installed properly since it always shows corrupt when i extract it from zip
Click to expand...
Click to collapse
Install the Samsung drivers first, reboot your pc.
Start odin in Admin mode then put your device in download mode, plug in the usb cable. Your device should be detected.
Don't try flashing a corrupt firmware, it will be rejected anyway as it will fail the md5 check.
I suggest you use a different browser to download.

@ashyx hey! thanks for all your help. my internet went offline while i was trying to respond to the other thread. my phone is now fixed with your help. Thank you so much! only took 3 mins for the while Odin flashing to complete

This issue is now FIXED

rissered said:
This issue is now FIXED
Click to expand...
Click to collapse
but how? I have installed official firmware and flashed via odin and it shows"success", but then it gets stuck in the samsung logo. please help

Unable to download new ROM to Note3 N900W8

Hello and I apologise in advance for the size of the post. I'll try to be as succinct as possible but there's a lot to say. First off, I had a Wind Note 3. Then sick of the reception I swapped to Mobilicity. I rooted the phone 8 mos. ago and it went well, but a month later when I tried to install a new rom with Odin I did something wrong. To the best of my abilities, i made sure that what I was installing was for my type of phone. My Note ended up caught in an unending rebooting process with the message 'Recovery Booting...Recovery is not Seandroid Enforcing Set Warranty Bit: recovery'. So I reconnected it to Odin and let it do its thing and I had a mediocre working phone. The menu and back keys were useless. I lived like that until I saw this post. So I downloaded the first item from this site. For Gapps I got the first choice of this list . However when I went to put my mobile in recovery mode it did the same 'Recovery Booting' message as it did the last time. Then I ran Odin again with this and while the phone was still not working properly when I tried to boot on recovery mode it allowed me to. I then uploaded the new rom but I got this message: (please follow this link for pictures.
So I need some guidance in what to do even if it is to tell me to use it as a paperweight. However, I think there's still hope for it. Any input will be much appreciated it.

I suggest you start over by flashing a stock rom from sammobile.com.

Update
audit13 said:
I suggest you start over by flashing a stock rom from sammobile.com.
Click to expand...
Click to collapse
I did found the rom as u advised. The problem still persist, Odin shows no button called PDA as a mention but AP instead. Any ideas?
Sorry for pestering you, I dont mean to spam you. Thank you kindly,
PW

AP=PDA
Sent from my SM-G925F

PDA appears in Odin 3.07. AP appears in newer versions.

I tried updating my J5 to Android 6

I tried to update my J500FN to Android 6.0 according to some guide from a website called "rootupdate" which showed up when I googled "update samsung galaxy j5 to 6.0"
This was a mistake because it was too vague, and I ended up trying to install the rom using some TWRP Manager app by Jmz Software.
Now when I try to boot it up, the Samsung screen shows up as normal, but at the top left it says "set warranty bit: recovery". Also I can only get to the Samsung screen once, afterwards I have to remove my battery and reinsert it to see it again.
Since then, I've tried to unbrick it according to several different guides which all follow the same beat: download the firmware you need, and use Odin to flash it or whatever it does. Problem is that I can't find a firmware with my model number anywhere (J500FNGSMH) and whenever I try to flash anything with Odin it takes its sweet time until kindly informing me that the operation has failed by yelling "FAIL!" at me. I've used Odin 3.09 and 3.10 and they both provide the same result. Now I'm at a loss, so I figured I'd create this thread to ask for help. Just remember that I suck at this type of thing so you'll probably have to explain it like I'm 5 years old.
PS: I just copied most of this from another forum post I made in sammobile, which somehow got me banned immediately so now that website is on my list of things to get revenge on, so if it doesn't make any sense that's probably why.

ihatedust said:
I tried to update my J500FN to Android 6.0 according to some guide from a website called "rootupdate" which showed up when I googled "update samsung galaxy j5 to 6.0"
This was a mistake because it was too vague, and I ended up trying to install the rom using some TWRP Manager app by Jmz Software.
Now when I try to boot it up, the Samsung screen shows up as normal, but at the top left it says "set warranty bit: recovery". Also I can only get to the Samsung screen once, afterwards I have to remove my battery and reinsert it to see it again.
Since then, I've tried to unbrick it according to several different guides which all follow the same beat: download the firmware you need, and use Odin to flash it or whatever it does. Problem is that I can't find a firmware with my model number anywhere (J500FNGSMH) and whenever I try to flash anything with Odin it takes its sweet time until kindly informing me that the operation has failed by yelling "FAIL!" at me. I've used Odin 3.09 and 3.10 and they both provide the same result. Now I'm at a loss, so I figured I'd create this thread to ask for help. Just remember that I suck at this type of thing so you'll probably have to explain it like I'm 5 years old.
PS: I just copied most of this from another forum post I made in sammobile, which somehow got me banned immediately so now that website is on my list of things to get revenge on, so if it doesn't make any sense that's probably why.
Click to expand...
Click to collapse
As it seems you still have recovery there. You can use it to flash any custom rom try odin 3.11 and try different firmware from updato.com

You can get Firmware from sammobile

I don't even remember how, but i flashed some rom and Odin told me it failed, but my phone started working normally anyway. Technology am i right lads