Database Users

ROM Install Issue

My original issue got resolved thanks to s15274n. This mans ROOT walkthrough is amazing!!!!!
NOW I have a problem getting my ROM to load.
Im trying to Install the Malice ROM. and nothing is going quite as smoothely as I think it should.
This is attempt 2, the first time I waited an hour to try and install this rom, straight from SD, and I think the furthest it got was "installing ROM"
nothing. pull the batery out (I assume thats a total noob move, and at beast ill-advisable.) rebooted, went about my day. well, im trying again, and now the furthest ive gotten is "Installing update" the status bar is never filling or scrolling though.
Whats the problem? (going on about 15 minutes with no change btw)

You must use Odin to either
-Flash back to stock so you can reinstall packages
or
-Flash a voodoo integrated kernel so you can flash roms w/ CWM/Voodoo Recovery

Download a voodoo kernel and flash it using odin.

ok, I have the kernal and I have ODIN. once again I have never used ODIN< I definately used a one click root.
does anybody have a link to a thread with *detailed*, hold my hand, walk me through it and pat me on the butt at the end Instructions on this? It's a learning process and damn if im not learning something by the time this is all said and done lol.

last time it sat still for me when it said installing update, it was a bad download. I redid my download of the rom and it went through fast and smoothly. Thats how i fixed my prob maybe it will fix it for u.

I really need some help i want to cry
I got the samsung galaxy s(vibrant) and it doesnt go pass the welcome screen im trying to install a rom but i dont know how have looked over thing i installed odin3 and everything else but when i plug it to the usb it doesnt show on my computer idk why and nothing shows on the id com for odin someone plz tell me this can be fixed please can someone plz plz help me i begg you from the bottom of my heart

i always odin to stock whenever i flashed a new rom, works like a champ all the time.

elmoslonely said:
I got the samsung galaxy s(vibrant) and it doesnt go pass the welcome screen im trying to install a rom but i dont know how have looked over thing i installed odin3 and everything else but when i plug it to the usb it doesnt show on my computer idk why and nothing shows on the id com for odin someone plz tell me this can be fixed please can someone plz plz help me i begg you from the bottom of my heart
Click to expand...
Click to collapse
do you have the .pit and .tar files? Also, are you turning your phone off? There is an awesome guide by s15274n called the noob guide. It goes over very specifically how to root, it also has a small tutorial on rooting using ODIN3. Search the q&a forum, i believe thats where the guide is.
Also just to clarify, im not saying ur a noob or inept, im just saying its a super awesome guide. My phones neen rooted for three days now, ive flashef a bunch of roms and i always flash nack to stock...REALLY helpful tutorial. Good Luck!

Can't use Odin to flash firmware, no recovery, no OS, HELP

Well, I broke my phone.
My earpiece boost stopped working and I could barely hear on the phone, the new Facebook app was crashing Facebook constantly and I was getting random reboots yesterday so I figured I would go for something new.
Because this was my first rom on my S4, I figured I should go back to stock first, bad idea. I loaded Odin up, went to flash the stock firmware to install the newest version of Sacs rom, and it failed right at NAND write start!!
I even went online and downloaded a newer firmware (February) and that failed also. I can't do the emergency fix in Kies and I can't use the other option in Kies because it says my serial is incorrect
I don't know what to do at this point, but I desperately need my phone ASAP in case my boss calls me.
Any help appreciated.
April

Well you REALLY don't give much info.
What version of Android were you on when you got your phone?
Do you have the T version of the phone or just the standard.
What ROM are you talking about 'bening your first'?
How did you install it?
What file did you try and Odin?
It is recommended you read, read some more, search and then read some more to keep just such things from happening.
Just a wild guess but you tried to Odin a .tar to a version 'previous' to the version you started with.
OR you tried to Odin a .tar for the wrong model - tried a non T .tar on a T model or vice-versa
Search for the FULL NAE .tar if you are on the 'standard' model and Odin that one.
Or, if on the T variant, hit up those threads, find the lates .tar and Odin that.

@aprilx
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.

Sorry, I worked 16 hours yesterday, so checking the forums was the last thing on my mind considering I got up at 5am and got home at 9:30pm.
I figured out what it was, after trying a million different things. I found a MJA stock firmware and I was able to flash that, and now I finally have Kitkat on my device.

[Q] I would like some help.

Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?

nneely said:
Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?
Click to expand...
Click to collapse
You would be better off asking in your relevant forum, this is for the i9505

nneely said:
Hi, I'm a noob with phone software and I've seemed to get myself in a TERRIBLE spot. I tried a root earlier today and succeeded. (I don't have the link to the guide. It was a "noob guide" for sch-i545 phones with kitkat 4.4.2)
I decided I would uninstall the root and something went wrong. Now my phone goes into the "firmware upgrade encountered an issue" screen. I can also get into the download mode.
I've tried all sorts of different drivers and different versions to set back to and a few versions of odin as well as kies. nothing has been working.
I'd really like some help. I don't have very much money and wouldn't be able to afford a new phone for quite some time. Should i not just tell Verizon I lost this phone and have my warranty replace it?
Click to expand...
Click to collapse
Just came across the below guide after searching a bit, have you tried this process yet? Or firstly have you tried downloading your full firmware from samsung-updates. com and manually flashed it through Odin?
http://androidcentral.us/2013/09/how-to-fix-firmware-upgrade-encountered-an-issue-on-kies/

DSA said:
You would be better off asking in your relevant forum, this is for the i9505
Click to expand...
Click to collapse
sorry. i wasn't paying attention. I've moved a my thread to a different area

gsmyth said:
Just came across the below guide after searching a bit, have you tried this process yet? Or firstly have you tried downloading your full firmware from samsung-updates. com and manually flashed it through Odin?
i do realize im in the wrong forum area, but yes i tried the guide with kies and kies says that it can't update anything on my device
i've also tried full firmware updates and manually flashed through Odin and they fail every time.
Click to expand...
Click to collapse

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

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