Develop Bugs

[Q] S4 Mini I9190 3g firmware, help?

Hi there, I have a s4 galaxy mini GT-I9190 says baseband version: I9190ZSUAMG1. Build number: JDQ39.i9190ZSUAMG1. I believe it is a Hong Kong version? Sorry I'm a noob. I am looking for the United Kingdom firmware. Could anyone send me a link so I can download it? As I am not sure what I need.
Also is it fairly easy to do the update?
Regards,
Alan

A14n said:
Hi there, I have a s4 galaxy mini GT-I9190 says baseband version: I9190ZSUAMG1. Build number: JDQ39.i9190ZSUAMG1. I believe it is a Hong Kong version? Sorry I'm a noob. I am looking for the United Kingdom firmware. Could anyone send me a link so I can download it? As I am not sure what I need.
Also is it fairly easy to do the update?
Regards,
Alan
Click to expand...
Click to collapse
Yes you currently have either the Hong Kong (TGY) firmware or Taiwans (BRI) region.
It seems that your model doesn't have the U.K Stock firmware as of yet.
Check out: http://samsung-updates.com/device/?id=GT-I9190
I'm not sure if any other regions will work.
To note on if it's easy to update firmwares;
Some info on every step for rooting>recovery>flashing firmwares or custom roms steps
Updating/Restoring your firmware is relatively easy.
Go to the following thread to get started with rooting your device and flashing a custom recovery which is needed for flashing Firmwares and Roms: http://forum.xda-developers.com/showthread.php?t=2398143
Kies: http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Sent from my GT-I9195 using xda app-developers app

Will there ever be any UK firmware for the I9190 non LTE? If the (i9195) has the uk version already. I'm not even sure you can buy the i9190 in the UK? As i bought this one from Ecell off ebay, Hong Kong version.
Would the i9195 rom work on the i9190? probably a stupid question... Or is there any europeon roms out there that would be better than the HK version.
I'm encountering problems, on the google play store. There's a game called asphalt 7/8. When I go to it in the store it comes up. " your device isn't compatible with this version". Is it region locked or something? It thinks im in HK so I can't get it? It's really annoying. Is there anything I can do?
Alan

The i9195 ROM will NOT work on the i9190.
You could email the developers for info regarding asphalt. If it were region locked, it wouldn't show up on your play store at all.

Frustrating...i9190 in UK
Thats the thing it does not show up in my play store. Only way I see it is by clicking a link to the game on google. Then it says" your device isn't compatible with this version".
What can I do, this is so frustrating. I am in the UK and it thinks I'm in HK. Anyway around this?... Any other firmware out there with a region that can access everything on google play without restrictions?
I don't mind rooting my phone, have done it before on an older android.

A14n said:
Thats the thing it does not show up in my play store. Only way I see it is by clicking a link to the game on google. Then it says" your device isn't compatible with this version".
What can I do, this is so frustrating. I am in the UK and it thinks I'm in HK. Anyway around this?... Any other firmware out there with a region that can access everything on google play without restrictions?
I don't mind rooting my phone, have done it before on an older android.
Click to expand...
Click to collapse
Like i said before i'm not sure if other regions will work for your device.
GT-I9195 files will most definately not work since it uses another kernel iirc.
You could ask Arco regarding suitable regions for your device other than HK for European customers or you could install CWM on your device and try some E.U firmwares out yourself.
If none of them work or you get bootloops you can always hop back to the Hong Kong firmware.
Last but not least, if none of this works and you're still eager to play asphalt you should google for the APK & SD files (.obb) which ofcourse is illigal and i cannot link you to it (sorry have to stick to xda rules).
Sent from my GT-I9195 using xda app-developers app

Thanks for your help, who is Acro do you have their contact details? I have successfully rooted the phone now. Got CWM installed.
I've tried the Market Enabler app to get asphalt 8. But that does not seem to work. Damn why didn't I get the S4 mini LTE.

A14n said:
Thanks for your help, who is Acro do you have their contact details? I have successfully rooted the phone now. Got CWM installed.
I've tried the Market Enabler app to get asphalt 8. But that does not seem to work. Damn why didn't I get the S4 mini LTE.
Click to expand...
Click to collapse
Arco68 is a developer/user here at xda , he works on CyanogenMod 10.1-Nightlies for the GT-I9195. Just check out the general S4 Mini section.
Sent from my GT-I9195 (CM10.1-Nightlies) using xda premium app-developers app

Bricked? Help
Ok I tried flashing the phone using Odin, and it failed right at the end. Now phone is stuck saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Well I tried that and Kies is not detecting anything :'(. Looks like I've broken it completely now.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_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> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

A14n said:
Ok I tried flashing the phone using Odin, and it failed right at the end. Now phone is stuck saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Well I tried that and Kies is not detecting anything :'(. Looks like I've broken it completely now.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_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> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Is that the Hong Kong firmware? Did you made a backup before you did anything? You should know that its a must if your inexperienced with this kind of stuff.
Have you tried renaming the zip file to update.zip and load it from cwm or if you have it, the backup file? maybe that will work.

Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.

A14n said:
Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.
Click to expand...
Click to collapse
Good that everything worked out eventueel.
Just Google the asphalt 8 apk and sd data files and save yourself the trouble (and money lolz). It worked for me with most games incl. Asphalt 7 & 8.
Sent from my GT-I9195 (CM10.1-Nightlies) using xda premium app-developers app

A14n said:
Ok I managed to get the phone up and running again I reinstalled CWM. Then flashed a different firmware I9190UBUAMH1 and it passed this time. Seems way better a lot less bloatware more UK friendly.
Asphalt 8 still shows as incompatible, mystery as to why? I have seen videos on YouTube of it running on the S4 Mini. I have e-mailed gameloft, but no reply yet.
Click to expand...
Click to collapse
Please Help Me
My Phone is I9190 .
it was running i9190xxuamf7 , then i install I9190ZSUBML3 and among installing it failed with this message " Odin : Invalid system.img.ext4 "
after that i reinstall i9190xxuamf7 then installed successfully but after boot there was No Radio such as Antena ,Bluethooth , wifi
then i install i9190xxuamf7 with a i9192 pit & Odin Failed with This Message :
" Set Waranty Bit : System
Set Waranty Bit : Cache
Set Waranty Bit : Hidden "
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9190XXUAMF7_I9190OJVAMG2_I9190XXUAMF7_HOME.tar.md 5 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> SingleDownload.
<ID:0/004> tz.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
PLEASE !!! SOMEONE HELP ME... I AM SO SAD & TIRED
WHAT SHOULD I DO ?

SOLVED !
bahmax said:
please help me
my phone is i9190 .
It was running i9190xxuamf7 , then i install i9190zsubml3 and among installing it failed with this message " odin : Invalid system.img.ext4 "
after that i reinstall i9190xxuamf7 then installed successfully but after boot there was no radio such as antena ,bluethooth , wifi
then i install i9190xxuamf7 with a i9192 pit & odin failed with this message :
" set waranty bit : System
set waranty bit : Cache
set waranty bit : Hidden "
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> i9190xxuamf7_i9190ojvamg2_i9190xxuamf7_home.tar.md 5 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> singledownload.
<id:0/004> tz.mbn
<id:0/004> nand write start!!
<id:0/004> boot.img
<id:0/004> recovery.img
<id:0/004> system.img.ext4
<id:0/004> persist.img.ext4
<id:0/004> non-hlos.bin
<id:0/004> cache.img.ext4
<id:0/004> hidden.img.ext4
<id:0/004> fail! (size)
<id:0/004>
<id:0/004> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1
please !!! Someone help me... I am so sad & tired
what should i do ?
Click to expand...
Click to collapse
i solved my problem !
I found out if your last good worked rom is "z" you should instal 'z' based rom & if it was 'x' you should install 'X' based rom.
For example mine was i9190xxuamf7 & i install i9190zsubml3 then my phone crashed even when i reinstalled i9190xxuamf7 because phone did not let me downgrade so i should upgrade it to a 'x' based rom so i install i9190xxubmj7 then my phone worked correctly and my problem solved
good luck
bahman mahmoudzadeh
25-day-1392

same problem i cant flash orginal fw
I9190XXUCOC1_I9190SERCOC1_I9190XXUCOC1_HOME.tar can flash
I9190XXUCOD2_I9190OJVCOD2_I9190XXUCOD2_HOME.tar cant flash

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<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> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

[Q] Black Screen of Death after flashing Stock-Rom with Odin

Hi everybody,
i have same problems with the Stock-Rom of Lolipop with VD2-Branding.
ODIN has faild with:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now i have a "Black Screen of Death".
The ROM: VD2-T805XXU1BOCC-20150403134302.zip
Odin: 3.10.6
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2 Germany
Flashing with TWRP also failed. Is it possible, that i use the wrong image?
Edit: Now it works, but the way was very terrible. Odin flashing till error. Following this i have flash the Recovery TWRP. Now the Tablet has booted, but i disbelieve it works fine.
Can someone help me to install the offiicial Rom correctly?
Thanks a lot and have a nice day!
best regards masterkifke

Masterkifke said:
T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_HOME.tar.md5
Click to expand...
Click to collapse
Masterkifke said:
VD2-T805XXU1BOCC-20150403134302.zip
Click to expand...
Click to collapse
Masterkifke said:
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2
Click to expand...
Click to collapse
Does your SM-T805 have a letter after the model? Like C, M, W or Y?
If not, then when I search www.sammobile.com for your firmware, this is the download file name I find that you should be using. I am not sure what the file name will be after extracting the zip though. Would take five hours of downloading for me to find out.
But if you compare this name to the file you originally downloaded and it is the same, then I think you are flashing the correct firmware.
T805XXU1BOCC_T805VFG1BOC4_VD2.zip

Ignore the error then boot into recovery and wipe cache.
Job done.

Thanks for help.
The device comes without an extension like C , M, W or Y and the ROM is from sammobile. So i think the ROM is correct.
But the problem is after flashing and getting the error, i don't have any access to recovery and for wipe the cache -> POWER + VOLUME UP + HOME goes directly into "Back Screen of Death".
So i must install TWRP before.
But my target is to the device bringing back into factory state.
At the moment it works fine.
Thank you for help.
best regards from germany
masterkifke

It won't boot if you don't have a valid recovery installed. Flashing stock firmware always installs stock recovery.
So either reflash stock firmware, flash stock recovery or flash twrp.
However I can quite clearly see from your first post that recovery has flashed fine, so it seems the problem is you are not using the right timing and button combo to enter recovery mode.
Many people have encountered the hidden.img fail when flashing a different region firmware as its csc specific.
All you need do to solve it is enter recovery mode and wipe cache.

I think my phone is bricked

Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out

gfp11289 said:
Hey all I'm not sure what happened but I reflashed to stock KitKat and while I did that I installed all the newest updates to receive Lolipop and after I finished that I downloaded CF-AutoRoot. I rooted it and got stuck with a bootloop so I went into the stock recovery and erased everything. So I repeated step one by reflashing KitKat and now Odin is giving me an error and it isn't working.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1ANIE_N910PSPT1ANIE_N910PVPU1ANIE_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I'm about to pull my hair out
Click to expand...
Click to collapse
You have a dev edition or retail?

Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point

gfp11289 said:
Retail I believe
Could I just go into TWRP, go to my computer, put on a ROM, transfer it to my phone, and then install something from there?
I don't really care about stock at this point
Click to expand...
Click to collapse
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.

jcip17 said:
If you're able to get in TWRP you do not have retail version. Do you have any ROMs or TWRP backups on an SD card? The CF-autoroot part is confusing me I don't remember ever having to use that.
Click to expand...
Click to collapse
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo

gfp11289 said:
Nope none. I tried downloading about 4 different stock roms and they all give me the same error in Odin.
I'm able to get into TWRP and Custom OS but that's it. The phone just keeps restarting after the Note 4 logo
Click to expand...
Click to collapse
You can't flash stock roms (.zip files)in ODIN. They need to be .tar files
First check under your battery it should say developer device. If not you have a retail version. If you do have developer edition try to go through these steps and hopefully you will be okay. .
http://forum.xda-developers.com/note-4-verizon/development/how-to-custom-recovery-root-t2923340
If you have a retail version try this.
http://forum.xda-developers.com/not...nt/verizon-note-4-firmware-odin-file-t2926827
You said you accepted the lollipop update when you were on Kit Kat?

I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P

gfp11289 said:
I need the Sprint firmware but it doesn't say anything about Developer or Retail under the battery
Model: SM-N910P
Click to expand...
Click to collapse
Woh don't do anything I said. You're in the wrong forum
Try to seek help here
http://forum.xda-developers.com/note-4-sprint​

Oh shoot I didn't even realize I was in the Verizon forum. Sorry

gfp11289 said:
Oh shoot I didn't even realize I was in the Verizon forum. Sorry
Click to expand...
Click to collapse
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !

jcip17 said:
Hey on the bright side you're a senior member now :highfive:
Hope you get your phone working !
Click to expand...
Click to collapse
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?

gfp11289 said:
Me too
Do you have any ideas possibly? If I'm able to get into TWRP and I put a ROM on a micro sd card, couldn't I just install it from there?
Click to expand...
Click to collapse
Yes definitely just do an advance wipe and wipe data, system, cache, and dalvik cache before. But don't confuse TWRP with the stock recovery. TWRP is a custom recovery.

Samsung Galaxy A3 Custom Binary blocked by FRP lock

Hello,
when I start my device then the error "Custom Binary blocked by FRP lock" comes.
I knew the error (OEM-unlock) not activated after root.
So, now I want to flash the new firmware with odin.
My handy model: SM-A310F
I downloaded the right firmware (I think) on sammobile (version: A310FXXU3CQL2) but when i want to flash it with Odin, it stops by hidden.img (~90%) with an error. (checkout log)
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 3048 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So, what can I do now?

FabianGER said:
Hello,
when I start my device then the error "Custom Binary blocked by FRP lock" comes.
So, what can I do now?
Click to expand...
Click to collapse
try a different version of ODIN and see if is working

broky said:
try a different version of ODIN and see if is working
Click to expand...
Click to collapse
Dont work

FabianGER said:
Dont work
Click to expand...
Click to collapse
tried this one?
Odin3_v3.10.7

broky said:
tried this one?
Odin3_v3.10.7
Click to expand...
Click to collapse
Yes, but dont work too
same error
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

i have same problem

no one to help us !!!!!

go to the recovery and wipe data/factory reset then try to flash the new firmware with odin it should work that fixed it for me ... besides that the firmware u posted A310FXXU3CQL2 is for a3 2016 so you either are flashing the wrong firmware or you are on the wrong forum this is for A series 2017

Enable oem unlock in developer options

my phone galaxy a310f 2016 when i switch it on say's custom binary is blocked by fap,i have tried odin solution but it does not get dectected,i have tried trouble shooting for gadget serial it says drive software can not be found what i can do please help.

1st , its not home for a310.