Can't return back to stock ROM - Galaxy S 4 Mini Q&A, Help & Troubleshooting

Hello, could please someone help me with this terrible problem? I have Galaxy S4 mini (i9195 LTE version). I flashed clockwork recovery, make a root and install CyanogenMod 11 (everything works fine). But I need to complaint this device back to the shop, because it has problems with random restarts (and I was thinking than maybe a flashing of custom ROM can help, but no). But when I connect device to the PC with Odin (3.09, but I tried 3.07 and others), select original ROM (which I downloaded from sammobile) and click Start, process fails after few seconds (I tried all of USB ports on my laptop and I tried same steps on my second PC), but with no success
Here is the log from ODIN:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195TMZBML1_I9195XXUBML4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the screen of my phone I see this:
ODIN MODE
Model: gt-i9195
Current binary: custom
System status: official
Knox kernel lock: 0x0
Know warranty void: 0x1
CSB-config-LSB: 0x30
Bootloader ap swrev: 2
Write protection: enable
SW REV CHECK FAIL: Fused 2 > Binary 1
And I am trying to flash this ROM:
Model: GT-I9195
Model name: GALAXY S4 mini LTE
Country: Germany (T-Mobile)
Version: Android 4.2.2
Changelist: 2340422
Build date: Fri, 20 Dec 2013 16:46:00 +0000
Product Code: TMZ
PDA: I9195XXUBML4
CSC: I9195TMZBML1
MODEM: I9195XXUBML4
Can someone tell me why I can't return back to stock ROM?

jerrry said:
[SNIP]
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/CODE]
[SNIP]
Click to expand...
Click to collapse
See that "Auth" there? Have you allowed access to your phone via USB? First thing that comes to mind for me.

Because you have latest knox bootloader. Do you see that line ""bootloader ap swrev : 2"" in your download mode.....that indicates it.
So this means you cannot downgrade to jellybean roms. Do not try to downgrade because repeated failures of odin might brick your device.
The mbn files odin flashes are all related to bootloader and corrupted bootloader = hard brick.
If you are desperate for jellybean flash the brazil ububne2 for I9195. Only that JB works. Good luck.

ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?

jerrry said:
ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?
Click to expand...
Click to collapse
You cannot go back any further. Jellybean ububne2 is the latest jb rom and only that works. Ofcourse you can flash any stock kitkat firmware if you wish. Good luck.

Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.

jerrry said:
Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.
Click to expand...
Click to collapse
Try the knox free kk rom. worked fine for me. knox tripped and running cm11.

kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).

jerrry said:
kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).
Click to expand...
Click to collapse
It is the stock rom , knox bootloader removed so people can update without knox. Thanks to SilviuMik
Click Here

oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).

jerrry said:
oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).
Click to expand...
Click to collapse
oops. I think i read somewhere he got a request for 9195 too, maybe he has prepared it. Just do a search and see.
See this

Related

[Q] Bricked Device - How to clean install Original 4.3 Jelly Bean ?

Hello,
Device : Samsung Galaxy Note 2 (GT-N7100)
I am a new Android user and I tried installing a Custom ROM (KitKat 4.4) on my device which worked well.
I used TWRP to boot from in order to install it. Later I tried another ROM which seems to have bricked the device.
Now when I start my device, it doesn't progress pass the Boot Logo.
Is there a way to restore the device ? Any method using Odin ?
I don't have to worry about losing data because there's nothing to back up.
I would appreciate it if someone could point me a method to install a reliable (Stock) Jelly Bean 4.3 firmware.
I do not use it for making calls - only as a WiFi device. Would it be possible to use the recently released original 4.3 firmware
available for India, Hong Kong, China ?
You can get your stock rom from sammobile and flash with odin. You can also try booting to recovery factory resetting/flashing a different custom rom. I've had my share off boot loops
Sent from my GT-N7105 using XDA Premium 4 mobile app
Not Successful with Odin
Hello,
I tried flashing a Stock firmware from SamMobile and I get errors on Odin.
<OSM> Please wait..
<OSM> N7100ZCUEMK3_N7100CHNEMK3_N7100ZCUEMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
What could I have done wrong ?
andy_central said:
Hello,
Device : Samsung Galaxy Note 2 (GT-N7100)
I am a new Android user and I tried installing a Custom ROM (KitKat 4.4) on my device which worked well.
I used TWRP to boot from in order to install it. Later I tried another ROM which seems to have bricked the device.
Now when I start my device, it doesn't progress pass the Boot Logo.
Is there a way to restore the device ? Any method using Odin ?
I don't have to worry about losing data because there's nothing to back up.
I would appreciate it if someone could point me a method to install a reliable (Stock) Jelly Bean 4.3 firmware.
I do not use it for making calls - only as a WiFi device. Would it be possible to use the recently released original 4.3 firmware
available for India, Hong Kong, China ?
Click to expand...
Click to collapse
Which rom?
Once I saw there is a FACTORY rom for N7100. Give it a try.
Here it is http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
DOWNLOAD_N7100XXDLJ2_OXA_FACTORY
These firmware is made for emergency recovery device to factory condition
Firmware consists of four parts, plus pit
Attention! All user data will be deleted during flash the firmware, including internal sdcard
After flash you will have clean device (factory condition) CSC - XEF default
Can flash with PIT - Included in the firmware (The optional - required if damaged partition PIT)
Click to expand...
Click to collapse
Thanks a lot for the above information.
I'll try it out and update results.
[email protected] said:
Which rom?
Once I saw there is a FACTORY rom for N7100. Give it a try.
Here it is http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
Click to expand...
Click to collapse
Thanks ! I've got it working now.

[Q] Help Flashing Note 2 N7100 through Odin3

Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
Click to expand...
Click to collapse
I believe that if it is official 4.3 you cannot downgrade.
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
thedadio said:
Is it a clone?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
New Droid said:
If it is a clone is very well disguised, and it have the same SoC (CPU, RAM, Internal Memory, etc)
And it is impossoble to downgrade from 4.3?
Click to expand...
Click to collapse
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
tonylee000 said:
You can downgrade from 4.3 but you cannot downgrade the bootloader, that will be stuck
Click to expand...
Click to collapse
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
New Droid said:
Can you guide me to a post to try please.
I've tried a lot of post but it always fails.
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Update on first topic
Click to expand...
Click to collapse
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
....
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
tonylee000 said:
Ah the official stock images will have a bootloader bundled in it. So that maybe where its going wrong. If you install a custom recovery and put a custom rom (arhd19 or wanamlite3.9 are both android 412) that might be the easiest but I would only guess that yhey would work with the mk3 bootloader but it would probably burn the efuse voiding warranty.
Click to expand...
Click to collapse
I've installed the latest version of CWM Recovery Touch v6.0.4.1 and try to flash the CyanogenMod 10.1.3 to see if it woks.
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Right now I'm on my mobile. Can you send me the link to one post with that please. Thanks
Enviado do meu U9200 através de Tapatalk
The_Flashaholic said:
flash dr ketans knox free bootloader from one of his threads its a downgradable 4.3 bootloader
Click to expand...
Click to collapse
Can the mk3 bootloader be downgraded? I wss under the impression that once upgraded to a mk bootloader you were stuck with it as theyre not downgradable
New Droid said:
Hi everyone. I'm having some troubles with a galaxy note 2. I have one but is with the firmware of China with the JB 4.3.
I've being trying to flash with the firmware of europe, JB 4.1 with odin3 but i can't. It always give an error on sboot.bin.
I've downloaded the stock firmware from sammobile.com.
Tried in different computers and differents USB cables.
Also tried to install two differents USB drivers from differents sources.
Weird thing, i cant root my device by flashing by odin.
Can anyone give me an help?
This is my device:
Android Version 4.3
Baseband Version N7100ZCUEMK3
Build Number JSS15J.N7100ZCUEMK3
This is the error on Odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDME6_N7100TPHDMF1_N7100XXDME4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
sora9009 said:
if this is true then it is a great news..we can downgrade to 4.1.2 even with 4.3 bootloader installed...am i right ?
Click to expand...
Click to collapse
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
exceptionalkhan said:
That MSR version's size is greater than a 1000MBs which means that it has all the required files, which are needed to downgrade from 4.3 to 4.1.2.
So definitely check it out and share the result with us:highfive:
Click to expand...
Click to collapse
im pretty sure bootloader cannot be downgrade.
sora9009 said:
im pretty sure bootloader cannot be downgrade.
Click to expand...
Click to collapse
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
exceptionalkhan said:
Not sure but it worked for me. I had the N7100 made in korea version which is an international version. I upgraded to 4.3 chinese version. Then I wanted to downgrade to 4.1.2, I tried the chinese 4.1.2 version and two others. Which encountered some errors in flashing. Then I tried the MSR version which worked just fine.
Everytime I was flashing the 4.1.2 versions other than the MSR it incremented the binary counter by 2.
Click to expand...
Click to collapse
this is really a great news.Thanks
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
Sorry man, for me didn't work :S It keeps giving the same error :S
Hi everyone. Finally i could flash the note 2 :victory: but i still dont get it why i cant flash through odin
This is how i do it.
1. Flash the ClockworkMod Recovery through.
2. Flash the TWRP 2.6 Recovery.zip through CWM Recovery. (Don't know i i cant flash this recovery directly on odin
3. Flash a CyanogenMod Nightly ROM
4. Install Odin Mobile.
5. Flash the lastest official rom by Samsung for Europe.
6.Yeh I have a official rom on my mobile :victory:
Now I have one problem, when i try to make a call i cant hear the people on the other side and vice versa. I know the mic and speaker are working, if o try to make a call through skype it works perfectly!
Obs.On every ROM i have this problem, on Stock ROMs by Samsung, Europe and Chinese Version and also on CyanogenMod.
When i try to flash the European ROM on Odin it fails when try to write the modem.bin.
I can flash the Chinese ROM without any problems on Odin.
I'm using the lastest ROM JB 4.3 from Samsung
What is the problem now?
The MSR firmware zip link no longer exists?
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
exceptionalkhan said:
Ok Bro. All you need is to install a Firmware supported by your phone.
I had an N7100 with exact downgrade problem and was fixed by checking different Firmwares. you can install another if you like, european firmware maybe not compatible with your phone. DOWNLOAD Firmware which has size more than 1000 MBs.
Head Over to this Link and Download the Firmware with starting words "MSR",
http://forum.xda-developers.com/showthread.php?t=2571281
It will surely work.
I have tried all of these 4.1s but the MSR-N7100XXDMC3-201304291545.zip worked.
a "THANKS" will make my Day
Click to expand...
Click to collapse
MadR4sta said:
I have Chines SN N7100 and screwed with no Google accout
The MSR firmware zip link no longer exists??
Click to expand...
Click to collapse
Ma Bad...
Bro! the thread is closed, will update that later.
An updated link is Here:https://my.pcloud.com/#page=publink&code=XZgADZWDMzsYh1Xa8uTeOaSPsb2VAn5tb7

[Q] [SOLVED] GT-I9195 soft-brick after downgrade to stock rom

Hi guys,
i'm an idiot. I tried to flash trough Odin a stock firmware. However i made a mistake choosing the firmware version and the phone enter in soft-brick mode.
Now i am in this situation:
ODIN MODE
Product name: gt-i9195
current binary: custom
system status: custom
knox kernel: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
bootloader rp swrev: 2
write protection: enable
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
Before making this issue i had Cyanogenmod 11 Snapshot 12-2014
1. I don't know the version of my firmware (I know, i am a stupid guy...)
2. If i try to flash something trough odin everything fail... (CMW recovery, stock recovery, pit file found on internet...)
3. i red many thread and i tried many things but nothing happen....
Do you have any suggestion?
Thanks a lot, really...
atlantis87 said:
Hi guys,
i'm an idiot. I tried to flash trough Odin a stock firmware. However i made a mistake choosing the firmware version and the phone enter in soft-brick mode.
Now i am in this situation:
ODIN MODE
Product name: gt-i9195
current binary: custom
system status: custom
knox kernel: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
bootloader rp swrev: 2
write protection: enable
"Firmware upgrade encountered an issue. Please select recoviery mode in Kies & try again".
Before making this issue i had Cyanogenmod 11 Snapshot 12-2014
1. I don't know the version of my firmware (I know, i am a stupid guy...)
2. If i try to flash something trough odin everything fail... (CMW recovery, stock recovery, pit file found on internet...)
3. i red many thread and i tried many things but nothing happen....
Do you have any suggestion?
Thanks a lot, really...
Click to expand...
Click to collapse
It happend to me few monts ago to, i mean the same msg appear
after my cable plugt ot of my lap top while it was instaling with odin.
So i just did it over agwin and no problem.
You need to find out which model you have, 90 or 95 or 92.
Then you go to Sammobile and download stock firmware
fir your model an flash it throo odin agin.
where can i find the model?
thanks
atlantis87 said:
where can i find the model?
thanks
Click to expand...
Click to collapse
I would think that you should know which phone you bought?
Anyway it says under your phone battery is it Gt-I9195 or I9190 or I9192.
After you find out go to sammobile and enter your firmware and country.
Try to download the one wich is carrier branded, i mean if
your phone is bought in vodaphone or tmobile...ect.
Mine was bought in vodaphone(vip) so i use those ones.
But if your phone is ulocked, i think you should be able to
install firmware from any carrier.
kubura2999 said:
I would think that you should know which phone you bought?
Click to expand...
Click to collapse
Yes, sure, GT-I9195
kubura2999 said:
After you find out go to sammobile and enter your firmware and country.
Try to download the one wich is carrier branded, i mean if
your phone is bought in vodaphone or tmobile...ect.
Click to expand...
Click to collapse
I don't know exactly the country. I live in Italy but i bought this phone on Amazon. On the datasheet was written "Germany" but i never check if this was the truth....
kubura2999 said:
But if your phone is ulocked, i think you should be able to
install firmware from any carrier.
Click to expand...
Click to collapse
All my problem happened because (i think...) i tried to flash a wrong version of firmware. I flash many firmware getting from the site "samsung-updates.com" for gt-i9195 but nothing works... I tried Italian version (1° step when the phone worked) and 3 version of the german firmware.
atlantis87 said:
Yes, sure, GT-I9195
I don't know exactly the country. I live in Italy but i bought this phone on Amazon. On the datasheet was written "Germany" but i never check if this was the truth....
All my problem happened because (i think...) i tried to flash a wrong version of firmware. I flash many firmware getting from the site "samsung-updates.com" for gt-i9195 but nothing works... I tried Italian version (1° step when the phone worked) and 3 version of the german firmware.
Click to expand...
Click to collapse
Hmm..s.h.i.t man, i dunno. I mean that what happend to yo
happend to me twice (the kies message appearing)
Once like i said when my cable was pluged out while it was instaling through odin,
and second time also long time ago when i downloaded the same firmware buth another
carrier. Buth every time i solved with the firmware from my carrier.
Sorry man, maybe someone with more experties can help you more
This is the message on odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCNK4_I9195OXXCNK4_I9195XXUCNK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[SOLVED]
i found Philz touch recovery. I flash this recovery in odin (the last recovery that i've tried didnt' work...) and it works! After this flash i made a factory reset, i've flashed another rom and the phone is ressurect...
However now the cellular network doesn't work and also wifi and bluetooth connection....

need to reprogram as the phone stuck at Samsung Galaxy S III

My phone got crashed which can't bootup. The phone always stayed with Official release, never rooted. I am not sure which version has been upgraded to, now it stuck with Galaxy S 3 screen, only thing I know it has the SecureLinux enabled, so it must be either 4.3 or 4.4. I wanted to reprogram to the official firmware, but not sure if I reprogram to the wrong version, would that causes any problem?
Please help.
additional infomation:
at download mode:
PRODUCT nAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOM SECUREBOOT: ENABLE
Does this download menu look like 4.2?
Or it is 4.3 , I dont see warrenty flag.
Thanks.
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
audit13 said:
No mention of arrange bit or Knox is the screen so the phone must be running a 4.2.2 or older rom.
Click to expand...
Click to collapse
The phone is T999 for T-mobile, but seems there is one time only that it had official release of 4.2.1 or 4.2.2 available. I am not sure if I should flash the 4.1.2 or 4.2.1 back. But I seem can't find the 4.2.1 or 4.2.2 firmware on line anymore.
Question is that if I try to flash 4.1.2 to the phone, would it cause any problem if it was in 4.2.1?
Thanks all, I know this probably an old issue.
Flashing 4.1.1 or 4.1.2 should be fine.
audit13 said:
Flashing 4.1.1 or 4.1.2 should be fine.
Click to expand...
Click to collapse
###Right now I can't go to recovery mode, so I am trying to program the stock recovery, but failed. When I tried to odin the stock 4.1.2 it failed too. Here is the error during flashing stock recovery.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
audit13 said:
Tried different USB cables? Different USB ports? The rom cam from sammobile.com?
Click to expand...
Click to collapse
Here is the error msg:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
audit13 said:
It's stops when trying to flash the bootloader. Either you're using the wrong file or the phone does have a 4.3 bootloader. The download screen info provided in your post mentions nothing about warranty bit or Knox.
Click to expand...
Click to collapse
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3?
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
thanks for your response, yes the bootloader seems is 4.1.2, right now I am getting impatient about this, So I also tried to repartition it, reload the 4.1.2 bootloader. I can reload the 4.1.2 bootloader, that is only flash got success, flashed the 4.1.2 bootloader.
I have a second identical phone, So I can risk everything in the phone. Is there anyway I can just program it to 4.3? All I want is just get the phone back. I tried to load 4.3 bootloader, but it failed.
audit13 said:
You can flash a newer stock rom via Odin if you want to. If the bootloader is 4.1.2 and you have the correct stock rom, Odin should be able to flash the aboot.mbn file it Odin can't which tells me the file is wrong for the phone or the phone does have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
There is possibility that the pit is wrong, I tried to load the downloaded T999-16Gb pit from download site, maybe that file is not right? Since I can flash the stock boot.img by using Odin for version 4.1.2, the bootloader must be right???, Don't know what aboot.mbn would be affected by anything else.
I am wondering if someone can provide the T999 regular 16GB pit file, the early version of T999, Thanks.
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
audit13 said:
A pit file only needed if Odin cannot read the partition info from the phone and, based on the logs, a pit should not be necessary.
Click to expand...
Click to collapse
is it possible that the phone is upgrading from 4.1.2 to 4.3 and got crashed. but the bootloader is still showing 4.1.2?
what other possible reason that I can't flash aboot.mbn?
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
audit13 said:
Boot into download mode again and let me know what it says. It the bootloader was corrupt, that would be a problem.
Just to confirm: you're using firmware from sammobile.com and you are using the original Samsung USB cable to flash the phone.
Click to expand...
Click to collapse
Reboot to download mode, it is saying the same.
I am trying to flash stock recovery, modem, bootloader, all stock version 4.1.2 Only it can flash 4.1.2 bootloader, the recovery and modem always fails. Also the stock rom got failed.
With the same setting I can flash my other S3 recovery without problem, so the Odin, USB cable should not be an issue.
Thanks.
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
audit13 said:
Yes, this is weird. You have 2 identical phones? You can pull the pit file from the working phone and use it to flash the problematic phone.
Click to expand...
Click to collapse
the only problem is that my other working phone is running 4.3. I don't know what is the procedure to program it to 4.3 if my crashed one is in 4.1.2

[HELP] how to fix SGN8.0 always failed while flashing

ODIN MODE
PRODUCT NAME: GT-N5110
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
RP SWREV: A1
can any body know how to remove these line?
KNOX WARRANTY VOID: 1
RP SWREV: A1
i google it and i see that any off that two line are the cause why i can flash my official firmware..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i try all of andoid version of GT-n5110 its always fail..
BTW the samsung galaxy NOTE 8.0 have a gyroscope sensor for pokemon go?
can any body fix diss?
Elesio badiable said:
KNOX WARRANTY VOID: 1
RP SWREV: A1
can any body know how to remove these line?
Click to expand...
Click to collapse
Once you tripped the KNOX counter, you can't reset it. But, it will not block you from flashing via ODIN.
Elesio badiable said:
BTW the samsung galaxy NOTE 8.0 have a gyroscope sensor for pokemon go?
Click to expand...
Click to collapse
It does have a gyroscope (read under the "Sensors" here), but have no idea about "pokemon go" compatibility. :silly:
Stillness said:
Once you tripped the KNOX counter, you can't reset it. But, it will not block you from flashing via ODIN.
It does have a gyroscope (read under the "Sensors" here), but have no idea about "pokemon go" compatibility. :silly:
Click to expand...
Click to collapse
But how to fixx that can you pls help me ? i want to flash stock firmware Pls?
Elesio badiable said:
But how to fixx that can you pls help me ? i want to flash stock firmware Pls?
Click to expand...
Click to collapse
Why not try flashing the correct firmware for your device?
Your device is the wi-fi version (GT-N5110), but you are flashing a ROM for the 3G version (GT-N5100). Details from your OP proves that:
Elesio badiable said:
PRODUCT NAME: GT-N5110
...
<OSM> N5100XXDNG2_N5100OXEDNG1_N5100XXDNE2_HOME.tar.md5 is valid.
Click to expand...
Click to collapse
Stillness said:
Why not try flashing the correct firmware for your device?
Your device is the wi-fi version (GT-N5110), but you are flashing a ROM for the 3G version (GT-N5100). Details from your OP proves that:
Click to expand...
Click to collapse
sorry i try it but it failed so i try GT-N5100 because i want to try if it gonna success but it failed so pls!! helpp
BTW you have a back up or stock rom of GT-N5110 not custom rom!! that i can flash it by TWRP i want to try the stock rom of thiss phone so pls? thks 4 help by the way ...
seems like your phucked it up dude! You can try COI3 firmware, as it flashes the latest bootloader over what 4.4.2 had installed originally. If it fails, you probably flashed a custom Note 2 Verizon firmware that ruined your bootloader info. Once you flash a higher revision bootloader, you cannot downgrade, unless someone developes a fix like Dr Ketan did for the Note 2 guys.

Categories

Resources