Develop Bugs

[Solved] [Q] SGH-T999 Rooted bad, phone stuck on start screen

Hello xda,
I tried rooting my SGH-T999 and it took a while so I unplugged the USB and restarted the phone. Phone keeps saying it has encountered a problem with the current firmware, connect to KIES and select recovery. Kies does not connect to the device. I read on xda to reflash using ODIN. I have ODIN v1.85 from trying to root, is this the right version to use because I also found the ODIN3_v3.07? As far as USB driver, is there separate drivers for ODIN or are people referring to the Samsung Kies drivers (I just installed KIES). I read to do it on this screen and I also read to try to go into the recovery mode (holding vol down, home, power) and then reflashing; which should I do?
Also, I found this link on xda for the T-mobile firmware ( http://forum.xda-developers.com/showthread.php?t=1949687 ). No idea which one to choose, why are there so many, I am currently downloading the latest one
"UVDLJA
PDA: T999UVDLJA
CSC: T999TMBDLJA
Version: 4.1.1 JB
Date: Nov. 14, 2012
Sammobile Link
Samsung-Updates Link"
If I want to use the pre rooted file do I need to fix my problem first and try flashing with stock firmware or can I try to fix the issue directly with the pre rooted firmware?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.

Aerowinder said:
Use the Odin from my signature.
You can probably just flash mrRobinson's stock rooted rom to fix it. And Kies is garbage. Uninstall it.
I would like to see the root guide you used as well.
Click to expand...
Click to collapse
I used this guide to root.
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Before I try to flash with mrRobinson's stock rooted rom which I just finished downloading, I will uninstall Kies and install the USB drivers first?
Thanks for your response Aerowinder.
I got USB drivers earlier today that was a newer version but I will be using the files from your sig since it works :good:
Another question I had was, does the phone need to be in download mode or can I do it in the screen where it says "encountered problem with current firmware. Connect to KIES and select recovery" screen when I flash with Odin? I know normally I would have to be in the download mode but I'm wondering if it is the same when I am getting this error.

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.

Aerowinder said:
Phone must be in download mode to use Odin.
The drivers in my signature are not the newest, you are correct. They are the last version I found that work without any issues. The newer ones pretty much suck. Constant disconnects mainly.
Click to expand...
Click to collapse
Awesome thanks!
So I am watching the root video on your sig, so in my case I would choose the rom I want for the PDA instead of the cwm-touch-6.0.2.3-d2tmo right? Should I extract the rooted firmware or just load the zipped file onto ODIN PDA?

Re: [Q] SGH-T999 Rooted bad, phone stuck on start screen
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.

Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.

Aerowinder said:
Root66 does not contain a recovery so you still need to flash one of those but don't use my link. Get ROM Manager once you're up and running.
If you don't care about the flash counter you can flash the tar in my signature.
Click to expand...
Click to collapse
Okay I don't care about the counter, I just want my phone to work and I'll be happy.
But now I'm getting a little confused about the cwm recovery.
So just to be clear, you are saying I need to flash a recovery (cwm-touch-6.0.2.3-d2tmo in my case since I don't care about the counter), BUT do I flash the recovery before or after I flash with Root66 firmware? That part I am confused about. And do I flash one right after another or do I need to restart my phone or ODIN first?
Thank you so much for helping me out. I was freaking out this morning and I am very grateful for your help and knowledge. I hope I am not being too much of a pain or hassle with these questions. Sorry that I am quite new to this

Woody said:
Sorry to interject here but you can get an Odin flashable recovery from here.
You can flash one of these and then flash Root66 right after and you'll have stock Rooted ROM with stock or custom recovery (your choice).
Not to be a buzzkill or anything but you are probably the 5th or 6th person in the past 2 weeks that have encountered the "encountered problem with current firmware. Connect to KIES and select recovery" error. Only a few of them have been able to pull out of it. The ones that have, have had to flash Root66 (or their device respective FW) multiple times.
I hope that you can get out of it and please post here if you do. Aerowinder knows what he is doing. Follow his lead.
Click to expand...
Click to collapse
Woody, I went to the link you posted. What are the 4 files for?

Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.

buzzking00 said:
Woody, I went to the link you posted. What are the 4 files for?
Click to expand...
Click to collapse
Top one is TWRP version 2.3.0.0
Second is 6.0.1.2 CWR touch version
Third is TWRP version 2.3.1.0
Fourth is Stock recovery.
Do not flash all of them. Are you a TWRP or CWR kind of person? Instead of re-typing it out, go here and I come in on post #20 on the 2nd page. Read that to the end and let us know if you understand it. Pretty easy to follow but I understand your Panic Mode, so take your time.
Aerowinder said:
If still having problems, only thing left to do is flash a full stock image, link also in my signature.
Click to expand...
Click to collapse
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
Awesome. Thanks Aerowinder!
I will try this when I get home (assuming I can go into download mode...) and post what happened

Woody said:
^^ This is what I see in his future.
Like I said above, I haven't seen too many people get out of that "Encountered..." error without some real technical expertise.
Click to expand...
Click to collapse
I will take a look at the link Woody.
I am really hoping this will work on the first try!
Okay so from reading your post Woody I can use EITHER the TWRP and CWR, but I want to use the one that is easiest to use. Which one do you guys think is easier to use?
Also, SU3.3 or SU1.04 which one should I use? Aerowinder, your sig shows both now but earlier I didn't notice the SU1.04. I just realized I only need the SU file IF the prerooted file doesn't work but just in case it doesn't I guess it is better to know.

Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.

Aerowinder said:
Draw straws. I use CWM/Superuser. I use Superuser because CM comes with it. AOKP comes with SuperSU... both work fine. Just make sure you use the ones from my signature, as they are newer versions. You won't need su if you get a prerooted rom, only for stock.
Click to expand...
Click to collapse
I am going to try it in an hour.
Wish me luck!
1. Download mode
2. Flash CWM
3. Flash Root66
4. Hopefully no problems

:good:

Aerowinder said:
Don't use those - they are older versions.
If you don't care about the counter, then flash the CWM in my signature using Odin (can provide TWRP tar link if that's your thing), then flash root66 using Odin. You can reboot in between... but no real reason to do so.
If you are still having issues after you flash these, drop into recovery (vol up + home) and reset factory defaults. If still having problems, only thing left to do is flash a full stock image, link also in my signature. The page you linked to does not contain the newest version because DocHolliday hasn't been around here much lately.
Click to expand...
Click to collapse
OMFG OMFG OMFG
OMFG OMFG OMFG
OOOOOOH MYYYYYY FOOOOOOOOKIN GOOOOOOOOOOOOSH
AEROWINDER AND WOODY
I LOVE YOU SO MUCH
IT WORKED AND NOTHING GOT ERASED. I THOUGHT PUTTING THE NEW FIRMWARE WOULD'VE ERASED EVERYTHING WITH THE NEW ROM BUT NOPE.
Uninstalled KIES and USB drivers.
Installed USB drivers from Aerowinders sig
So the Odin 3.07 didn't work either so I ended up using ODIN 1.85
Turned off auto reboot and left f reset on (no idea what f reset does lol)
Flashed CWM
Flashed root66 rom
Restarted phone and it was back to normal with all the data saved, but no SU (wasn't unlocked)
So reflashed CWM
Then restarted in clockwork recovery and ran super user and now the phone is rooted
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
:good::good::good: 3 thumbs up to the knowledge members above Aerowinder and Woody!
THANK YOU!
Panic mode TRANSFORMMMMM! *Panic mode has now transformed into excitement mode*

buzzking00 said:
Thanks for your helpful knowledge and now I am going to learn everything about android so I too can help another new android user in the (hopefully near) future.
Click to expand...
Click to collapse
So, ahh, are you excited? Haha. Great. Glad you got it up and running.
I hope that you do learn more about Android and share it with someone who needs help someday. When I first came, that is what someone did for me and I have tried to do it ever since. We are all still learning, including Aero and myself, so there will never be an end but rather more.
Good job and now you should make a Nandroid backup just in case you ever get in a bind again.

Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums

buzzking00 said:
Well now I gotta learn how to make back-ups and what a Nandroid backup is lol.
Time to search the forums
Click to expand...
Click to collapse
That's the attitude, with Android you have to be a sponge and try to learn as much as you can. A single Google search will give you the answers you seek and making a backup is pretty much universal no matter what Rom, phone you have. Good luck
Sent from my SGH-T999 using xda app-developers app

Need Stock Firmware/ROM for Glaxy S4 SGH-M919V (Videotron)

Hi I installed SwapSD on my sgh-m919v Galaxy S4 from Videotron but it totally screwed up my phone.. Now I get ''mtp has stopped'' ''settings has stopped'' and ''android.process.media has stopped'' each time I start the phone. I've been looking for the stock rom for my specific model (SGH-M919V) for hours but can't find it anywhere. I tried using SGH-M919 stock rom but it won't work even if I strictly follow the guide, ODIN tells me FAIL!! (Auth).. Could someone upload the stock rom for that specific model somewhere and give me the link please ?
I attached a screen capture from odin to show you what problem i get
Thank you

elektronick2010 said:
Hi I installed SwapSD on my sgh-m919v Galaxy S4 from Videotron but it totally screwed up my phone.. Now I get ''mtp has stopped'' ''settings has stopped'' and ''android.process.media has stopped'' each time I start the phone. I've been looking for the stock rom for my specific model (SGH-M919V) for hours but can't find it anywhere. I tried using SGH-M919 stock rom but it won't work even if I strictly follow the guide, ODIN tells me FAIL!! (Auth).. Could someone upload the stock rom for that specific model somewhere and give me the link please ?
I attached a screen capture from odin to show you what problem i get
Thank you
Click to expand...
Click to collapse
I have this stock roms i just need to post it and it nearly 2Gb.
---------- Post added at 08:20 PM ---------- Previous post was at 08:13 PM ----------
do you have TWRP installed because the thing i have is a backup i did from that software. i dont know if it that you need.

elektronick2010 said:
Hi I installed SwapSD on my sgh-m919v Galaxy S4 from Videotron but it totally screwed up my phone.. Now I get ''mtp has stopped'' ''settings has stopped'' and ''android.process.media has stopped'' each time I start the phone. I've been looking for the stock rom for my specific model (SGH-M919V) for hours but can't find it anywhere. I tried using SGH-M919 stock rom but it won't work even if I strictly follow the guide, ODIN tells me FAIL!! (Auth).. Could someone upload the stock rom for that specific model somewhere and give me the link please ?
I attached a screen capture from odin to show you what problem i get
Thank you
Click to expand...
Click to collapse
Not sure if you got what you needed but you can take the phone back to stock using Samsung Kies, just plug the phone in download mode select "tools" then "Firmware upgrade and initialization", input your phones info and off you go..
if you could also grab the rom downloaded by Kies and uploaded for us that'd be cool.

gillesguinet said:
Not sure if you got what you needed but you can take the phone back to stock using Samsung Kies, just plug the phone in download mode select "tools" then "Firmware upgrade and initialization", input your phones info and off you go..
if you could also grab the rom downloaded by Kies and uploaded for us that'd be cool.
Click to expand...
Click to collapse
Unfortunately reverting back to stock with Kies has not worked for me either with that method.
Hopefully the stock firmware for this carrier will drop soon!

Bump

I too would like the stock firmware for this device before I start tinkering with it.
I am surprised however that odin fails while flashing the sgh-m919 firmware. I thought these devices were essentially the same.
Have you fixed your phone yet, and how so?

+1
I've soft bricked my phone and would really appreciate a stock m919V firmware. I've installed a bad kernel and/or rom and even the partitions are all screwed up. Nothing to do without a m919v odin flashable image.
Anybody?
dj_aj said:
I too would like the stock firmware for this device before I start tinkering with it.
I am surprised however that odin fails while flashing the sgh-m919 firmware. I thought these devices were essentially the same.
Have you fixed your phone yet, and how so?
Click to expand...
Click to collapse

sorinmtl said:
+1
I've soft bricked my phone and would really appreciate a stock m919V firmware. I've installed a bad kernel and/or rom and even the partitions are all screwed up. Nothing to do without a m919v odin flashable image.
Anybody?
Click to expand...
Click to collapse
Sent in a request to samfirmware.com & samsung-updates.com to post the firmware. Hoping that they consider the request.
Maybe you could do the same? I'm not asking to spam them, but I suppose it'll have an impact if there's more than 1 person requesting the firmware.

sorinmtl said:
+1
I've soft bricked my phone and would really appreciate a stock m919V firmware. I've installed a bad kernel and/or rom and even the partitions are all screwed up. Nothing to do without a m919v odin flashable image.
Anybody?
Click to expand...
Click to collapse
So, in my last post, I had mentioned that I had contacted samfirmware.com to post the stock firmware. They've responded to my request and already uploaded the firmware!
Posted the link here:
http://forum.xda-developers.com/showthread.php?p=42001570#post42001570
Good luck flashing it back to stock and reviving your S4.

Awesome. I'm downloading right not, but since I'm not a paid member on hotfile I'll only know in an hour if it works. I'll keep everybody posted, hopefully I'll be able to flash it with odin.
I'm also wondering what the no-name firmware on sammobile is. They posted the videotron, wind, and mobilcity firmwares. Is the no-name one unbranded? We'll have to wait and see.

So I downloaded the videotron firmware and it worked. Everything is back.
I'll try the unbranded version to see what it does.

Did you install the stock firmware using the stock recovery?

sorinmtl said:
So I downloaded the videotron firmware and it worked. Everything is back.
I'll try the unbranded version to see what it does.
Click to expand...
Click to collapse
Glad to hear it, keep us posted if you flash that unbranded firmware. Hoping it frees up some internal storage.
---------- Post added at 03:12 PM ---------- Previous post was at 03:11 PM ----------
speed4134 said:
Did you install the stock firmware using the stock recovery?
Click to expand...
Click to collapse
I believe he would have flashed the stock firmware using Odin for Windows. At least that's how it is normally done.

I just downloaded the videotron firmware from the website, I didn't flash the recovery. It's .md5 format, so I've flashed it with Odin. The phone was on CWM recovery, but it doesn't really matter as the firmware flashes the stock recovery too.
So I just flashed the videotron image in odin, phone rebooted and everything is fine, I'm back to stock, including no root and stock recovery. The only thing that's still there is the fact that phone is unlocked. (I've used the method described in the forum to unlock it).
As for the other firmware, it has _ESK in the name. I'm 99.9999% sure it's Eastlink firmware, another mobile carrier in Canada. The other ones had _VTR and so on in their name.

thanks for the info

Hotfile is down
I'm looking for a factory image of any of the MDJ builds.... Hotfile is down so I can't get it... does anybody have a copy that they would be willing to upload for me.... I need it so I can reset and sell this phone ASAP to get christmas money. Thanks

[Q] bricked -i747.

i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this

ghjsdf9 said:
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
Click to expand...
Click to collapse
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?

Larry2999 said:
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Click to expand...
Click to collapse
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions

ghjsdf9 said:
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
Click to expand...
Click to collapse
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.

Larry2999 said:
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Click to expand...
Click to collapse
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]

ghjsdf9 said:
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
Click to expand...
Click to collapse
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.

Larry2999 said:
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Click to expand...
Click to collapse
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......

ghjsdf9 said:
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
Click to expand...
Click to collapse
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.

Larry2999 said:
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Click to expand...
Click to collapse
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????

ghjsdf9 said:
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
Click to expand...
Click to collapse
I've seen this particular problem reported several times and it's always been a problem with the pit file. Flashing a complete stock system should fix all partition problems though. If the stock file you are using is an Odin flashable file, you may try using Odin 3.09. Otherwise, I'd suggest you find a recovery flashable image and flash via (custom) recovery.

HUGE Problem with s4 mini GT-9195

I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmware i had was 4.4.2

Silvershot said:
I recently rooted my I9195 successfully. i then flashed a custom kernel i found here on the forum (kernel v1 or sth like that) then my phone wouldn go past the boot white logo screen. i then tried flashing other kernels but they were apparently wrong as some features of my phone didnt work. i finally found the right firmware for my phone and tried to flash it with odin but it failed and now my phone only shows this message where it says that the firmware update failed and i have to use kies in recovery mode.
so i use kies and try the install firmware thing that asks you to put in your model and serial number. i do that and it says the device doesnt support initialisation. tried on another computer and it said that serial number was invalid.. i was very careful when typing it etc.
help.. what do i do?
btw last firmwar i had was 4.4.2
Click to expand...
Click to collapse
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.

S3miniFin said:
I think you should put original back and start over and read forum more howto.
You use ODIN to flash custom rom, why? ODIN is for original rom. With custom rom need use TWRP or other recovery boot.
Click to expand...
Click to collapse
I used ODIN for past phones to flash custom kernels and it worked fine. i said i flashed someone that isnt supposed to be supported. i have no idea. i am not an expert and i thought someone can provide with a fast fix since there will surely be someone to have experienced this issue.
anyone else?

bump! please help.. i dont have another phone and I need to get this fixed asap!

You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420

S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1

Silvershot said:
check my attached image.. i cant flash anything with odin. it gives me error fused 2 > binary 1
Click to expand...
Click to collapse
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...

S3miniFin said:
How about download-mode? Never seen ODIN-mode myself, so cannot understand what is going on there....
With download- mode i do all things with ODIN if need...
Click to expand...
Click to collapse
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.

S3miniFin said:
You don't need root phone before new kernel or custom rom. And i believe you use wrong files for that and now phone wont boot.
Start over with original ROM. With that you can test is your phone ok. Then use ODIN for recovery kernel and custom rom. Also check this:http://forum.xda-developers.com/showthread.php?t=2678420
Click to expand...
Click to collapse
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.

Your phone has official 4.4.2 Rom and you are currently using it. If you have Wi-Fi issues, your can try to flash custom kernel (Silviu, alexax)
Sent from my GT-I9190 using Tapatalk

Silvershot said:
that works, and it says downloading like normally when you try to flash something with odin, but it fails and gives me this error again: sw rev check fail: fused 2 > binarz 1
the rom im trying to flash is the DBT one in germany.
I am choosing AP btw, and not the other flash options.
Click to expand...
Click to collapse
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
Silvershot said:
i flashed one of those roms and i got my phone to boot. i have no wifi. i guess it was the last rom i flashed which was the wrong one.
i now tried the one which is supposed to be the correct rom but i land on the same error again. can someone help me find the correct stock rom?
here are the current device info. it seems that there is no official 4.4.2 rom for my phone. so i ****ed up lol.
Click to expand...
Click to collapse
For Wifi problem could help if boot phone again after first setup.

ok now it wont go past the flashing SAMSUNG logo. i went and bought a huawei g play mini today. no more time trying to revive the s4 mini.
if someone wants to give it a try let me know and i'll ship it to you.

I will try it!
Plz sent me a PN (i'm german)
Sent from my GT-I9195 using XDA Free mobile app

S3miniFin said:
But why you use F.Reset Time -option? Clear that and try again.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
For Wifi problem could help if boot phone again after first setup.
Click to expand...
Click to collapse
i tried rebooting the phone but it still is as slow as before. it peaks on 27mbit when i start the speedtest but then drops down to 19 or sth..
actually the download speed seems to be the problem. not the upload. now i forgot the network and connected again and its even slower

I need your all help. dead s9 / bricked

So i have a samsung s9 SM-G960F/DS version. i had have run TWRP on it and magisk + exposed and it worked fine. i had to uninstall exposed to log into some apps and then i would reinstall it agian. but when i ran the exposed unintaller the phone would not boot. i tryed diffrent things and it would not boot unless it had the exposed intalled on it. i did a complete wipe of the phone with TWRP and now i can´t install stock rom. i downloaded the latest stock ROM for my model and the latest odin that can handle the lz4 compression. bur when i but in BL AP CP CSC it just get stuck on system.img all the time. i there is simply nothing i have not tryed. and nothing works for me. The only think working is if i flash the TWRP then i can boot into recovery TWRP. thats it. i am at a point where i will pay anyone who can help me figure this out cause i almost lost all hope for this to work agian. So i really really hope someone here have an ide to what could work for me. every tip and trick i will test and if someone offer help via discord or somthing i would also be glad to hear from you.

Hi
Extract and flash bootload.img or hidden.img file from the main stock rom.
I'll check the actual file name for you when I get home later. Did experience that problem sometime back on my s6 edge.

Usually there is a small error message on the screen of the s9 if odin fails or stalls. It's small blue text, I have a feeling it's either 'magic string error' or 'SYSTEM not [Sec]' or close to it. I find this happens when flashing the wrong firmware for that model. Example, flashing G960N firmware for a G960F.
I just did a reflash and here are my exact steps for my G960F.
1. Download Odin 3.13.1
2. Make sure Samsung Drivers are installed
3. Grab the latest firmware for your device, my device is a G960F so I just picked the latest BRJ3 firmware with November patch from Updato. Just get the firmware for your exact model.
4. Extract the files from the ZIP file
5. Add all the correct BL, AP, CP and CSC files to odin.
6. Select nand erase
7. Boot S9 into download mode
8. Flash to phone.
Don't try to flash TWRP before installing the full firmwares and until the phone is setup.
If all fails, and because you seem to be able to install TWRP, then you can download TGP Kernel ROM and flash that. It is based on stock G960F firmware, has a nice aroma installer for selecting various things and tweaks. It also provides a clean install of Magisk if that's something you like.
Also be sure to flash no-DM Verify.

Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find

*Detection* said:
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
Click to expand...
Click to collapse
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.

zalik20 said:
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
Click to expand...
Click to collapse
Why not ot share those items to help others in the forum.

nsnobel2 said:
Why not ot share those items to help others in the forum.
Click to expand...
Click to collapse
You should look for samfirm or frija tool . Those would help you get latest firmware for your phone. Download it , flash it with odin and everything should be fine. Just remember that its possible that as you would be on latest firmware, you might not be able to downgrade in future.