[Q] S4 Mini I9190 3g firmware, help? - Galaxy S 4 Mini Q&A, Help & Troubleshooting

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

Related

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/
Q&A for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i did all this to my s4 but now when i boot it, says Kernel Is Not Seandroid Enforcing, Set Warranty Bit
also when i booted the phone the wifi does not work. could you help with this problem?
Samsung Galaxy S4
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Ayaz Gill said:
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Click to expand...
Click to collapse
Yes
UPDATE: I fixed the issue while posting this, the solution is included. I am hoping by posting this it may help someone having the same problem, because I spent hours and days trying to solve the issue. Sorry the post is so long.
This is my first post.. I am in desperate need of help!
I have searched everywhere, and cannot find any answers really.
I rooted my M919 at one point, and I could not receive OTA updates.
I do not know if it was rooted when I tried to update it with Odin though.
I was in a hurry (I know BIG mistake) and I never wiped my phone or anything before trying to flash the phone.
I think the phone may not be working because I may have not used triangle away before, but I am not sure if I ever used it. I did the root a long time ago.
I have tried changing USB cords, computers, drivers, md5 files, different Odin versions, flashing PIT file, you name it, I have probably tried it
When I boot the phone the currupt recovery screen shows up. Kies will not recognize the phone.
In the left corner it says:
ODIN MODE
...SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I can still access "downloading" mode, and it says the same as above.
Odin gives me different errors depending on the file I am attempting to flash
The reason I tried flashing the PIT file is because it would sometimes say
I am not completely sure what update I was using before this all happened, but I think it may have been this one, unrooted?:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5
Error codes are as follows:
While flashing 4.4.4 (Odin 3.10)
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
JFLTE_USA_TMO_16G.pit
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
One time I tried using this and it passed!!!
This ONLY works on 3.07 to my knowledge though. It fails on every other Odin
Recovery File I found (Odin 3.07)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/005> Added!!
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The screen is now frozen on the "Samsung Galaxy S4" screen and just shuts off if trying to boot into recovery mode.
If plugged into USB while trying to boot into recovery it launches the recovery file I just flashed!
I went back into download mode, and plugged the phone back in.
I opened Odin 3.07 again, since I had success with the recovery file.
I tried flashing 4.4.4 again M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
and it failed while only having Auto Reboot checked. I tried launching it with Auto Reboot AND F Reset Time, and it worked!! Hope this helps someone!!
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
shaqto said:
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
Click to expand...
Click to collapse
Replied to your email. Not sure if I still have it but I may be able to find it if you say it's not there.
alright i did a no no... I tried flashing back to stock odin when my phone was encrypted .. now its softbricked.
everytime i try to flash the stock odin, it always fails at system.img ext4. Need some help guys, its been softbricked for a week. I flashed philz touch twrp on it so I do recovery on it. any ideas?
doesnt work
Bricked my s4/but i had twrp installed to fix it
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
asmth00 said:
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version Bootloader/Modems do you have now on the phone? If the version you have now has Knox, then you can't downgrade to MDL.
If you are not sure, you can use this free app: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
If the version is MK2 or newer, you can't downgrade to MDL.
You can find newer firmwares either on the SamMobile.com site, or on this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
In odin, it says 0:[COM4] on the top left
You have 0:[COM3] in your screenshot
Is there a problem or something?Or is it fine?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
AziNoapte said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
Click to expand...
Click to collapse
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: http://www.sammobile.com/firmwares/
Rob
rlichtefeld said:
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: ------------To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links--------------
Rob
Click to expand...
Click to collapse
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
AziNoapte said:
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
Click to expand...
Click to collapse
Since this forum is for the T-Mobile variant of the S4, and I'm not familiar with the GT-I9505, I would suggest you try the forum for that model:
http://forum.xda-developers.com/galaxy-s4
If you flashed a T-Mobile tar to your I9505, it is probably because of the radio/modem which was designed for the T-Mo model. There should be links in that forum about no WiFi, etc.
Rob
Hello gang. Got a new circuit board installed two weeks ago. Got the phone back, started setting it up, and after about an hour the touchscreen quit working. >8\
I emailed the shop and they said "could be because you're rooted."
Smelled like bull**** to me, but giving them the benefit of the doubt I figured I'd try to flash back to stock. (Which I WAS actually stock, I had the 4.4.4 OTA update, and then rooted and de-bloated.)
Anyway, I downloaded the "Stock firmware" (SGH-M919-UVUAMDB-k0nane.tar.md5) from post 1 in the title thread and flashed it with Odin.
SEEMS to be working, but oddly enough I have a M919UVUFNH7 baseband and bootloader, but Android 4.4.2, which based on my reading, should be impossible?
Also, like several other posters, I have no wifi.
In any event, I am currently downloading the NH7 firmware from sammobile. Says 2 hours to go.
Will try to flash that with Odin and we'll see what happens. Anyone have suggestions in the meantime?
OK - follow-up. I downloaded M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar and flashed it with Odin. Even though Odin said "Boot" and "Modem" in the flashing process, I still seem to have NH7 bootloaders and baseband.
Help?
Well, never mind. I don't care anymore. Tried to replace my glass and cracked the digitizer. Dunno if I'm down to drop another $120 on this thing now.
$300 purchase price
$100 circuit board replacement
$12 glass
Now $120 for a display? I might just call knock it off with this thing.

Pls Help by upgrade from 4.4.2 to 5.1 on SM-T805

Hello,
I'm new here and I heared that Android 5.1 is still alive for SM-T805 but it seems that's not available in germany - very bad I found .
Now I wnat to know if it's possible to get a "How To" for an upgrade from 4.4.2 to 5.1 for my SM-T805. I know that there are some recent threads but in the topic
my modelnumber ins't listed and I also don't accept downloads (PIT and ROMs) which want to do a specieal task (e. g. "try out this app" or "try to win an iPhone 6"
and so on).
The download for PIT/ROM should be easily done over share-biz or any other file hoster.
I think that I'll need Odin to upgrade manually but I hope too that I don't need to root my device.
At last I want to know if 5.1 is good enough an comes with german language support or is there a better custom rom with german language support which
supports my SM-T805 and most/all Playstore-Apps and comes with better performence and longer battery duration and so on.
Sincerly,
Chaos234
Hi!
Hi! Samsung has not yet released the Android 5.1 for our decide, for now only the 5.0.2. What you can do is download the ROM (Stock ROM 5.0.2 Lollipop by Sammy) and flash it with a program called Odin. It's very simple to do, but one should be careful not to do anything other than prescribed. Simple: Download the ROM to your device, SM-T805, and download and install on your PC Odin, open it and then click in PDA and select the downloaded ROM. You can find the firmware on sammobile.com siteFinally, in its S Tab, select your language and enjoy. :fingers-crossed:
Everything you need to know is posted in the thread below.
One one of the rules of XDA is to search before asking repeated questions. XDA is not a spoon feeding forum.
I suggest you read the WHOLE thread before posting any questions.
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
Thanks for the link.
I'll update this night and then I response to this threat if all worked fine .
In addition, I searched for a link like yours in the developers section but I founded only a threat for SM-T800 and other Devices bot not my Device.
It's also better to pin the thread in the comlpeat section so that it's shown on each subboard in this category e. g. as an anouncement.
Edit 1: First try to get 5.0.2 failed! I'll now use recovery mode and try it again.
Q: Is CyanogenMod better as Android 5? What are the differences between them?
It seems that the ROM for my file is definitly defect!
Code:
<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/005> Added!!
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It fails every time on the "hidden.img" ... any ideas?
chaos234 said:
it seems that the rom for my file is definitly defect!
Code:
enter cs for md5..
check md5.. Do not unplug the cable..
please wait..
t805xxu1bocc_t805vfg1boc4_t805xxu1boc1_home.tar.md5 is valid.
checking md5 finished sucessfully..
leave cs..
added!!
odin v.3 engine (id:5)..
file analysis..
setupconnection..
initialzation..
get pit for mapping..
firmware update start..
singledownload.
sboot.bin
nand write start!!
boot.img
recovery.img
system.img
modem.bin
cache.img
hidden.img
fail!
complete(write) operation failed.
all threads completed. (succeed 0 / failed 1)
it fails every time on the "hidden.img" ... Any ideas?
Click to expand...
Click to collapse
You didnt read the whole thread like i said!
ashyx said:
You didnt read the whole thread like i said!
Click to expand...
Click to collapse
Well, used twrp now (ok ... now knox is set to 1 but it's ok for me ) and actually it's in the boot state.
I'll wait until it has botted finaly but it seems that it works now.
EDIT: Works now! *big smile*

Galaxy Note 8 GT-N5110- Stuck In Bootloop After Factory Reset

Boot loop after factory reset on GT-N5110
I tried to reset the device using Settings>Back up and reset>Factory data reset>Delete all.
Rebooted into a black screen with an Android with a hatch open and a blue spinning thing. It's been stuck in a endless loop of the startup screen with the name and model, which then goes to the Android with open hatch.
I pried the rear cover off and discovered that I don't have any screwdrivers small enough to remove the battery. So I'm wondering if there is any software based fix that I can try.
Holding down Power+Volume Down interrupts the loop and brings up this screen - blogyourearth.com/wp-content/uploads/2012/02/Samsung-Galaxy-S2-Warning-Custom-rom-installation.jpg
I've had the tablet for 2 years, so the warranty is long gone. I'd be open to flashing a Custom Rom/Kernel, as long as I'm able to go back to the default TouchWiz 4.1.2.
Bump/Update
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
emc_2 said:
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
Click to expand...
Click to collapse
Are you able to enter download mode without issues?
pvsgh said:
Are you able to enter download mode without issues?
Click to expand...
Click to collapse
Yes, no issues at all.
emc_2 said:
Yes, no issues at all.
Click to expand...
Click to collapse
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
pvsgh said:
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
Click to expand...
Click to collapse
Have no idea on how to do any of the above, but I'm googling now. Are there any guides/articles on how to do this, that You could point me in the direction of? Since I'm soft-bricked, is there any point in trying to back-up my presumably borked ROM? I've already downloaded my country specific, stock 4.1.2. ROM.
Many thanks for taking the time to help me and I apologize for the noob questions. I know my way around Windows, but when it comes to Android - I'm hopeless
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
emc_2 said:
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
Click to expand...
Click to collapse
OK so now you have a working TWRP recoveryand you also know what was causing ODIN to fail.
Next step would be to install a custom ROM, check the development section.
if you prefer stock then you ODIN your stock tar file which you downloaded.
Using TWRP, I backed up; EFS, Boot, Cache, System and Data. After the backup completed I followed the prompt to reboot and it booted into Android *happy dance*.
looks like all the user preferences are gone. No more password or background pictures and all apps have been removed from their folders. Basically looks like all the apps that I installed are there and any data associated. But all my preferences and set options are gone.
Going through the apps, I remembered that I had rooted using Framaroot. Do you think that may have been the cause for the soft-brick? Should I un-root and then try the factory reset again or just flash the stock ROM that I downloaded?
EDIT: didn't see your reply when I started typing this out. Since TWRP is flashed. Does that mean it has replaced whatever recovery Samsung had in place? If so; does having it installed/flashed increase the chance of a fairly stress free recovery in case of future problems?
So, it turns out pvsgh is pretty awesome!
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
i.imgur.com/j9neU0B.png
emc_2 said:
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Added!!
Removed!!
i.imgur.com/j9neU0B.png
Click to expand...
Click to collapse
You can take a backup that you can use to restore your tablet if you ever get issues again.
Or just follow the same procedure again.
Taking backup is completely a user choice whether he want it or not.

[2015] ODIN failed flashes reflashing STOCK 4.4.2 - Please HELP :'(

Hi there!
I recently bought a N3N (N7505) :good: for mobile drawing. Since I bought it used, I found KNOX at 0x1 and the 4.4.2 it came with was already annoyingly buggy (lags everywhere, packed RAM & phone app FCs). I did manage to root it through CF-Autoroot (I think?) and even put a custom recovery (TWRP touch v2.8.7.0)
The problem is, everytime I download a ROM from Sammobile (md5 checks confirm undamaged downloads), it fails to flash via ODIN (flashes ALL THE WAY till the end and says FAILED - phone reboots perfectly to previous OS like nothing happened) and I'm wondering if I downloaded the wrong ODIN files, or is there something I'm missing?
So, i'm currently on N7505XXUCNL1 and wondering how I can reflash it (or a similar one) to refresh the phone anew :angel:
ROMz, Y U NO FLASH???
Any advice on what ROM would best suit me to refresh my N3N with???
:victory::victory::victory:Thanks in advance!!:victory::victory::victory:
UPDATE:
When i'm in Download mode, this is the information displayed
ODIN MODE
PRODUCT NAME: SM-N7505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
AP SWREV: (2)
The ODIN log for when I try to flash N7505XXUCNL1_N7505OXXCNL1_TPH is here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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)
The ODIN log for N7505XXUCOE1_N7505SWCCOF1_SWC is here:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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'm stuck on the Firmware update encountered an issue. Please select recovery mode in Kies and try again
can you provide us the log?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
The ODIN failed flash log??
Where do I find that?
damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
Greetings damadikaz,
I have posted my ODIN logs as an UPDATE on the main post for two separate flashes that both failed.
Any help is greatly appreciated:highfive::highfive::highfive:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
audit13 said:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
Click to expand...
Click to collapse
Oh WOW!!! It could be!
Thank you very much:laugh:
Going to download tonight and flash :good::good::good:
Will return with feedback!
Thanks again good sir! :highfive::highfive::highfive:

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.

Categories

Resources