[Cross-posting this thread here, because it probably belong in the Q&AHT-subforum]
I wish to root my soft-bricked S5mini.
But have realised that I cannot use djibe89's tutorial without enabling USB debugging in settings (which are currently unavailable).
I've tried to install Kies to reinstall firmware, but get endless connection error, and troubleshooting connection error (i.e. reinstalling Samsung USB driver) doesn't fix it.
It seems like Odin is able to connect to the phone (at least I get ID:COM blue).
Question 1: Does this mean that I can flash fresh firmware/ROM to the phone with Odin?
Like described in this guide by jackeagle (and then enable USB debugging)?
Question 2: How and where do I find the right firmware/ROM?
I have a Danish language SM-G800F phone, but it doesn't seem like Samsung is providing firmware anymore. When I check sites like sammobile.com, there are 3 different version 6.0.1 in mutiple languages (including multiple UK versions) but not Danish one.
Can I use any firmware version (including ROM Unofficial Lineage OS 16 provided in djibe89's Galaxy S5 mini G800F pack)?
Or is there a specific UK/US version that would work with my phone?
I hope someone can help, because my backup phone stopped working a couple of days ago
Related
I F****** up..
i played with rooting and flashing before i found these forums with guides and stuff.
and now my samsung galaxy have no mobile network, no imei number and freezes when i activate bluetooth..
it was also bricked (logo loop) but i fixed that.
i have flashed stock firmware in it and it works fine beside the 3 problems above.
i've tried
http://forum.xda-developers.com/show....php?t=1801997
http://forum.xda-developers.com/show....php?t=1804123
neither did work since i cant usb connect i've tryed every option to get my pc to usb detect my mobile.
including kies and latest samsung drivers, reinstalling and with or with out kies.
someone please be my hero and give me some answers
you guys ****ing rock and i know we can fixx this!
Unfortunately the only simple way to fix things ...
Unfortunately the only simple way to fix things is to find a backup of your EFS partition - look after something called:
efs.img
efs.tar.gz
efsbackup.tar.gz
efsdev-mmcblk0p3.img.gz
(the img versions are probably the best, but either one should work to some extent).
EDIT:
OOPS, just now I noticed that you are speaking about a i9305 - you should look here:
http://forum.xda-developers.com/showthread.php?t=1946915
Hi,
I've already been through the thread
[30.03.2012][CF-Root 4.4] J-P/S/Q-*,JV-1KBHIOPQRSTAUV,JVU,JW4 - su+bb+2e/CWM-rfs+ext4
which has links to all the ROM files to be used with CWM in recovery mode (and explanations about their names).
I don't have a standard production phone. Mine has a build name of: FROYO.eng.eunju81.hong.201000831.205407 therefore I can't go by the names of the ROM files which are based on build names like FROYO.xxJP (P obviously referring to "Production"). Does the date of that build have any significance to you experts (Aug 31, 2010)? Does this narrow down what ROM file I can download?
Also, my phone is a pretty standard 512MB, ARM processor phone for that era (I'm guessing, since it was given to a journalist for review who gave it to me when she was done reviewing it).Will I have to use ODIN to flash it? I WAS able to root it (the Chinese made Eroot succeeded where all else failed) and install ROM Manager AND CWM but I then downloaded all three ROM types for my phone (the phone part isn't active I only use the WIFI so I tried the Galaxy Tab ATT, T-Mobile and Verizon but they all gave errors when I tried installing them). I read that it's imperative to have the right file, but with my funky build number, that doesn't seem possible. Am I going to be able to do with this without "doorstopping" my phone? (sorry. I like "doorstop" better than "brick" .
Wrong forum, this is S2/I9100 Q&A, not Tab Q&A which is here (we have device specific fora).
I've asked mods to move your thread, sit tight until they do.
One other thing;
I forgot to mention: Kies updated the firmware to the latest version if that helps you "axe spurts" figure this puzzle out. Thanks in advance!!! :fingers-crossed:
>>my phone is a pretty standard 512MB, ARM processor phone for that era (I'm guessing, since it was given to a journalist for review who gave it >>to me when she was done reviewing it).Will I have to use ODIN to flash it? I WAS able to root it (the Chinese made Eroot succeeded where all >>else failed) and install ROM Manager AND CWM but I then downloaded all three ROM types for my phone (the phone part isn't active I only use >>the WIFI so I tried the Galaxy Tab ATT, T-Mobile and Verizon but they all gave errors when I tried installing them). I read that it's imperative to >>have the right file, but with my funky build number, that doesn't seem possible. Am I going to be able to do with this without "doorstopping" my >>phone? (sorry. I like "doorstop" better than "brick" .[/QUOTE]
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
Try to flash this firmware : http://www.sammobile.com/firmwares/3/?download=18114 via odin3 it's a i8190XXAMG4 (DBT) firmware it also include modemfs (modem) then try to upgrade your baseband to XXAMG4.
bohlero said:
Hello,
I am new to mess around with mobile phones and Android and (therefore) also managed to bring my girlfriend's GT-I8190 phone to a non-working state. Although there are lots of information in this forum I am more confused than sure what to do. I hope to get here some help / information / explanation.
Past
The phone was bought in Germany and had probably a German firmware. But I do not know, since no connections to Kies or whatsoever and no backups where done earlier. After a error of Android (e:\ failed to mount or something similar) which blocked the phone on the startup logo of the non-modyfied S3 mini, my guess for a quick solution was to flash the firmware with Odin to a new(er) German version. I downloaded (from a German forum) and flashed successfully several versions (supposedly OXA). But with all version the network connection hasn't practically worked. Only very weak and only at a few locations. Once I used in desperation also a so called stock-recovery from somewhere.
Present
I visited a shop where the uber-friendly Samsung service overwrote the firmware first with the general and later with the LaFleur version (PDA: XXAMG4, CSC: QXXA MH1). Kies tells me the CSC is somehow a VE1 version (what country is that code for - moon?). But the problem hasn't changed.
I still have the original IMEI, but I'm missing the baseband and, what worries me more: no product code. I managed to read it out only with "CheckFus" which says only: Not Active1
Future ?
Since I probably haven't used the right firmware at least once, I am hesitating to do more. My ideas are as following: modem, firmware, baseband.
What is the best way to proceed? Is there still a easy solution? I don't mind to change to another version - no stock firmware is required. Am I close to have a 4" tablet?
Any answer is appreciated - thanks!
Click to expand...
Click to collapse
I8190XXAMG4 / QXXAMH1 is a German La Fleur firmware. I have no idea why your CSC seems to be messed up. It should probably be DBT.
What does it say if you dial *#1234# in dialer?
Thanks for the infos so far.
I did not intend to link to the LaFleur version in the first post.
Do I need the root recovery for the baseband update?
With the 1234 code I get:
AP: I8190 XXAMG4
CP: XXXX
CSC: I8190 QXXAMH1
I think this is the same as mentioned before. I checked the origin of the files I used before on this mobile and it is possible that I used this a recovery file which may be for a 8190N (I cannot post the outside link yet). I did not read careful enough the thread linking to this file.
Can this be the origin for the messed CSC version and the missing product code?
Looks like you're without baseband.
Take a look at this thread and flash a modem for i8190.
http://forum.xda-developers.com/showthread.php?t=2526831
Sent through time and space from my s3mini/CM11
Happy end
Hello again,
firstly: Problem is solved - phone works properly. Thanks for the replies and to tys0n for the work with the files and the support - acutally doing the job of Samsung and google.
For the sake of completeness, I will tell what I did, if any unexperienced user (as I still am) will ever come across this thread:
I tried first just the standard firmware AMG4 from Sammobile (which is linked above) and afterwards the baseband files - but both did not help as expected.
I installed CWM and used the file from here and miraculously it was working (The phone is used only in 2G). Later I wiped the data and flashed again with the AMG4 firmware to have a clean version now.
AP, CP, CSC say all XXAMG4 now, Kies recognizes it as DBT (as supposed to). But the product code, which came back and was read out with CheckFus, says I8490 RWA XSE. This should be Indonesia, correct? Is there still an inconsistency somewhere?
Thanks again for the help
Robert
Hello Folks,
the last days I have read so much, but all tutorials I read are pretty old or lead me in a dead end road.
Could somebody give me some infos what to do and how I get to a good result for my dad's Samsung GT-I9000
Unfortunately I have no windows computer here, which gives my headache with tutorials based on a windows connect. what I have:
- Mac OSX 10.10.4
- Heimdall 1.4, Kies, SmartSwitch installed
- Samsung Galaxy S i9000 (branded from 3 Austria - Hutchinson)
this phone was unlocked from a shop before, but my dad got no "unlock number". it has worked unlocked for some years. I wanted to try out if I can get into recovery by pressing "Vol.Up - ON" (no home button) and it just restarted. since then I get the popup for using "unlock PIN". even a working 3 SIM card from a friend does not work anymore. Android Eclair just shows a SIM symbol in the upper right corner with a red exclamation mark.
If possible, I want to update to a pretty new Android. I have read the post here that Coderom with Android 5.1. even runs on this model fine.
If I would like to jump from this pretty old firmware to such a new one, do I need to root, unlock it first and flash step by step newer Android version? or is it possible to flash the Coderom immediately (after root, unlock and probably a recovery installation)?
If a custom ROM is flashed, is the phone still SIM locked?
Modell GT-I9000
Firmware Version 2.1-update1
Basebandversion I9000NEJG1
Kernel Version 2.6.29 [email protected] #2
Buildnumber ECLAIR.NEJG3
IMEI is shown
IMEI is shown
WLAN-MAC-Adress is shown
Bluetooth-MAC is shown
*#1234# shows:
PDA: I9000NEJG3
Phone: I9000NEJG1
CSC: I9000DREJH2
*#7465625# results in:
Netzsperre {on} /// netlock
Teilweise Netzsperre {off} ///partly netlock
SP-Sperre {off} /// SP-lock
CP-Sperre {off} /// CP-lock
-------------
First I have tried to backup the important data from the phone (only contacts and photos).
Until now I could not backup the efs folder/partition. (probably I need root first, right?)
I could hardly connect Kies with the phone, but I have not got any data with it. And I got an initialise error if I wanted to update (so 2.2 or 2.3 was not possible). An info box showed to use Smartswitch.
So I have used Smartswitch on the Mac and could connect via USB to the I9000. I have seen public folders and made a backup of the contacts and pictures. An upgrade was not possible too. Thus, the 3 branded Android Eclair is still on the phone.
With "Vol.Up - ON - Menu" boots the recovery.
With "Vol.down - ON - Menu" boots the yellow construction figure state for Odin. (download)
No play-store on the phone. Only google market (where I have not found anything useful). I have searched on apkmirror and could not really find apps for Android 2.1.
---------
what would you suggest to do and in which sequence? (without windows)
- root
- unlock
- backup efs folder
- install clockwork mod
- format somehow f2fs ?
- flash coderom
(do I have to care about german language too? or are most distributions CM etc. multi language?)
thanks for any help!
Michael
It is strange, I have problems now to get into that recovery with the three button combination. Downloading modus works fine.
=>>> Now I got it....I must hold all 3 buttons the same time and wait 2 times for the Samsung logo. After that, I need to leave the power button but not the other 2. That starts the Samsung Recovery.
Something that should have taken me 5 minutes to do, I have now spent 6 hours straight and I still have not been able to successfully flash the firmware. I'm losing my mind.
I have a Note 9, running the latest version of Pie, on Tmobile. I have tried with 3 different versions of Odin (3.13.1, 3.13.1 Patched and 3.12.3) as well as 3 different firmware files (one for CHA unknown, one for TMB specifically and the one that Frija found which surely must be healthy and a perfect fit). I have verified it is for the correct Build, PDA and CSC. I have enabled USB debugging on my device (but could not get the OEM unlock option to appear, so not sure if that's what's causing this headache or not). I have tried running only the AP file in Odin, I tried adding all the files, I have tried running the extracted .pit file, I have tried quickly cycling through the download mode when I get a failure in Odin, but it never passes. I've had all of the various failures in Odin - it gets stuck on setup connection, stuck on initializing, it comes back with a write failure error and succeed 0/fail 1. I've used different ports, different USB cables, and installed the Samsung drivers multiple times. I have searched so many threads and at least one of these things seems to fix the issue for someone, but I can't find anything that works for me. What am I doing wrong?
KnowinglyUnknown said:
Something that should have taken me 5 minutes to do, I have now spent 6 hours straight and I still have not been able to successfully flash the firmware. I'm losing my mind.
I have a Note 9, running the latest version of Pie, on Tmobile. I have tried with 3 different versions of Odin (3.13.1, 3.13.1 Patched and 3.12.3) as well as 3 different firmware files (one for CHA unknown, one for TMB specifically and the one that Frija found which surely must be healthy and a perfect fit). I have verified it is for the correct Build, PDA and CSC. I have enabled USB debugging on my device (but could not get the OEM unlock option to appear, so not sure if that's what's causing this headache or not). I have tried running only the AP file in Odin, I tried adding all the files, I have tried running the extracted .pit file, I have tried quickly cycling through the download mode when I get a failure in Odin, but it never passes. I've had all of the various failures in Odin - it gets stuck on setup connection, stuck on initializing, it comes back with a write failure error and succeed 0/fail 1. I've used different ports, different USB cables, and installed the Samsung drivers multiple times. I have searched so many threads and at least one of these things seems to fix the issue for someone, but I can't find anything that works for me. What am I doing wrong?
Click to expand...
Click to collapse
u and u1 device will never show oem unlock. bootloader isint unlockable.
search and read up more on the subject on xda or Google.
if you do have an F or N or 9600 model, then read up on what firmware you can flash and also get the proper samsung android driver for your PC in order for Odin to recognize the phones COM port.
but I have a feeling your issue is not knowing what device model you have and that that implies.
bober10113 said:
u and u1 device will never show oem unlock. bootloader isint unlockable.
search and read up more on the subject on xda or Google.
if you do have an F or N or 9600 model, then read up on what firmware you can flash and also get the proper samsung android driver for your PC in order for Odin to recognize the phones COM port.
but I have a feeling your issue is not knowing what device model you have and that that implies.
Click to expand...
Click to collapse
I failed to mention and that was my bad, but I am aware of which model I have. I am running the N960U.
i had this problem before, i solved it by using a different pc with windows 7, i think it's all about the usb connection, if you have a modern motherboard with usb 3 you will suffer using odin.
alsartawi said:
i had this problem before, i solved it by using a different pc with windows 7, i think it's all about the usb connection, if you have a modern motherboard with usb 3 you will suffer using odin.
Click to expand...
Click to collapse
That is not true. I have an Acer Swift 3 2019 version with a USB3 connection and I was able to installed the Samsung Stock OS onto my Note 8 N950N without any issues using Odin
iceepyon said:
That is not true. I have an Acer Swift 3 2019 version with a USB3 connection and I was able to installed the Samsung Stock OS onto my Note 8 N950N without any issues using Odin
Click to expand...
Click to collapse
maybe