Hello community,
I have actually came across a difficult situation with my Galaxy S3 LTE i9305 (international variant).
In order to give you a high level view of what happened im going to write a few topics of what I have flashed to the phone since I bought it (new) back in March 2012:
1. I'm from Portugal and I bought the phone on an online retailer because I wanted the grey version. So far so good I ordered it on the UK.
2. The phone I received, although being unlocked and sealed/new, had software branding from MDA germany.
3. At the time we were on Android 4.1.2. I went to sammobile and installed the TPH version (Portugal) of 4.1.2 in order to have the full stock experience. Eventually I rooted the device.
4. Later on came the 4.3. At the time I was not aware of the bootloader complications and ended installing the UK or German version (clean) that was on Sammobile. Installation went fine and I immediately rooted the device without issues and disabled Knox in the Rom.
5. Yesterday I had this great idea of flashing 4.4 (still unaware of bootloader issues) and downloaded the spankin new 4.4.4. from the nordic countries from sammobile. This is where it gets interesting.
6. I have tried a zillion combinations and either I get stuck on the samsung logo or I get the error of binary 3 and device 2 (or the other way around). All the flashes via ODIN have been done using the AP/PDA option.
What can I do to unbrick it? I don't remember which ROM I flashed for 4.3 and I have tried to flash the german version of 4.4 (set 2014) and the nordic countries one. Also tried flashing 4.1.2 via CWM recovery directly from SD card but still no go and stuck at bootloop. Have also tried software repair using Kies (manually inserting serial number under the battery) and still no go for my dismay...
Is it recoverable? Is there a way to upgrade it to 4.4? If it helps so far I have been able to fash stuff via ODIN and still have download mode. I dont care about data as I did make a backup before setting off on this "adventure" :laugh:
Thanks in advance.
Eventually solved using Philz recovery. Turns out that during the flash process for some reason the /data partition could not be formatted.
Now recovered and running the clean 4.4.4. of XDA
Related
Ive had the Samsung Galaxy S for about a month now, download the app GST (Galaxy S tweaker) and while doing the changing the lockscreen feaure the phone was hanging at the startup screen and not booting. After much research i evantually figured out i had to reinstall the firmware myself, downloaded all the necessary programs and flashed the fone. The firmware is now debranded and when i connect to it to Samsung Kies and click "Firmware upgrade" it says this firmware cannot be upgraded. Is there anyway i can get the firmware back that came with the phone originally from Orange? Or i would i have to send it back to orange for their branded firmware? The main reason for this is that i want the official release of Froyo when it (evantually) gets released.
I have an unrooted I9305 bought new from eBay in the UK, I believe the handset came from Singapore. I did a factory reset on it once and it restarted in Chinese or something similar!
I have just received an OTA notification that Android 4.3 is available, I haven't installed it yet. I am in the UK on T-mobile. Is it safe or advisable to install this update? From what I understand it will be 4.3 designed for Singapore, I don't want to screw my phone! I contacted Samsung support who came back to me within a couple of hours, confirmed that the handset was from Singapore but didn't seem too sure what would happen if I take the update. They suggested I should take it to a Samsung service centre and have it flashed with the UK stock firmware (which I would prefer) but the nearest one is 40 miles away, they would probably charge me for it, and Samsung said it would invalidate the warranty anyway.
I tried Kies to see if it would give me any more information about exactly what the update is, but Kies seems to be confused. I have version 2.6.1.13105_6 which is the latest according to Help->Check for updates in Kies itself, but when I plug in my phone Kies tells me I have to update Kies itself before updating my firmware. Samsung suggested using Kies3 which I tried but it says my phone is not compatible. I have had slightly better luck with an older version of Kies 2.3.3.xxx which displays my current firmware version and tells me there is an update, but doesn't show the latest firmware version so I still don't know what it will be.
I have just installed a smaller FOTA update and the handset build number now shows JZO54K.I9305ZHBMK1 but this gets no hits in Google so I don't know what it is.
I haven't rooted the phone as the guides usually say only do this if you know what you are doing, and I am clever enough to know how much I don't know!
Is it safe to install the OTA update and will it lose my current settings (like language) if I do? Or is there a better solution?
spencetj said:
I have an unrooted I9305 bought new from eBay in the UK, I believe the handset came from Singapore. I did a factory reset on it once and it restarted in Chinese or something similar!
I have just received an OTA notification that Android 4.3 is available, I haven't installed it yet. I am in the UK on T-mobile. Is it safe or advisable to install this update? From what I understand it will be 4.3 designed for Singapore, I don't want to screw my phone! I contacted Samsung support who came back to me within a couple of hours, confirmed that the handset was from Singapore but didn't seem too sure what would happen if I take the update. They suggested I should take it to a Samsung service centre and have it flashed with the UK stock firmware (which I would prefer) but the nearest one is 40 miles away, they would probably charge me for it, and Samsung said it would invalidate the warranty anyway.
I tried Kies to see if it would give me any more information about exactly what the update is, but Kies seems to be confused. I have version 2.6.1.13105_6 which is the latest according to Help->Check for updates in Kies itself, but when I plug in my phone Kies tells me I have to update Kies itself before updating my firmware. Samsung suggested using Kies3 which I tried but it says my phone is not compatible. I have had slightly better luck with an older version of Kies 2.3.3.xxx which displays my current firmware version and tells me there is an update, but doesn't show the latest firmware version so I still don't know what it will be.
I have just installed a smaller FOTA update and the handset build number now shows JZO54K.I9305ZHBMK1 but this gets no hits in Google so I don't know what it is.
I haven't rooted the phone as the guides usually say only do this if you know what you are doing, and I am clever enough to know how much I don't know!
Is it safe to install the OTA update and will it lose my current settings (like language) if I do? Or is there a better solution?
Click to expand...
Click to collapse
no u won't lose language english is in the blood of every Rom
Download a uk rom a d flash it with odin if ur afraid of any network issues. Since yur going to update via ota it makes no diff. Ur bootloader will be updated to the knox bootloader. And since you are not going to root it... just use odin to flash official i9305 firmwares. You cant go wrong.
Sent from my GT-I9305 using Tapatalk
Thanks.
hayabusa08 said:
just use odin to flash official i9305 firmwares. You cant go wrong.
Click to expand...
Click to collapse
I hope you are right! I presume flashing the firmware will remove all the apps and data I have put on the phone? Alternatively if I just take the OTA update is it likely to cause any issues or you can't be sure what it will do? And will that also wipe all my current apps and data? I have all the standard stuff backed up but since I haven't rooted there is some app data that can't be backed up, as far as I know.
As i have experienced before... unrooted phones data is not possible to be backed up. Heard of helium but yet to use it. So you may actually find out more about Helium app. Another alternative is you can use Kies to back up data.
Secondly check your gsm and lte bands of your phone and the carrier that ur using in uk. If the carrier supports it then it should not be of any issues with connectivity. Sgp phones are unlocked and usable worldwide. I dont see any issues unless your phone is faulty.
Sent from my GT-I9305 using Tapatalk
Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.
HyperEscape said:
Hello All,
Tried searching for a case peculiar as mine, wasnt able to find one so here is the lowdown.
1. Xperia C6603 , originally had 4.2.2 stock ROM which was working fine with my local network. Dont remember the baseband version.
2. Used XperiFirm to download the latest firmware as reported in the list. Dont know what does the suffix RxD (R1D--R8D) means. Anyone please explain. As per the below screenshot downloaded version "C6603_Customized HK_1270-5695_10.5.1.A.0.292_R1D" .
3. Before flashing the downloaded firmware I flashed the dualrecovery from XZDualRecovery. I made a TWRP backup of the 4.2.2 stock ROM on an external SD card, for all partitions including TA,system,boot etc.
4. Used Flashtool to convert the downloaded (step 2) firmware "FILES" format to a flashable FTF file. Flashed the firmware , which went on smoothly.
5. At the first startup I got the following screen , telling me that it is a prototype device/firmware . I went on to see that the network which was working fine with stock ROM 4.2.2 was no longer available.
I tried to go to settings to check and search for networks, which shows available networks, but unable to get itself registered to the SIM providers network. Tried all the settings combinations in menu "*#*#4636*#*#" , nothing makes it work to get the GSM network connectivity back. It is supposedly on the correct setting of LTE/WCDMA/GSM which my current operator supports. Following is the "About" screen for current baseband version.
Tried going in the "Service" menu via "*#*#7378423#*#*" , with the following info, having an unknown modem configuration.
6. Tried reverting back to the old TWRP backup, for which I needed the TWRP recovery loaded on the phone. So ran the XZDualRecovery script again (with the new 4.4 ROM on the phone), however the script hangs around in the end and never reboots the phone with the TWRP recovery. So i am unable to revert and use the stock ROM backups .
7. I dont want to root/unlock the bootloader, however I tried installing TWRP via its "XZrecovery.apk", but it requires busybox (which requires a rooted phone). So i tried the rooting script from [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader], but it also hangs around in the end and never delivers a rooted phone.
8. Tried looking around for assortment of xperia Z baseband files to check and see if flashing it separately can make it work, however to no avail the the condition persists.
Either ways having a prototype version on the phone which transmits all data back to sony is not desirable at all. So need to replace it for sure. Currently I am stuck in the middle without a clue of how to go back and restore the 4.2.2 TWRP backup, or to actually flash a "non-prototype" or retail version of 4.4.x .
Any help/guidance/suggestions to remedy would be appreciated.
Thanks.
=====================UPDATE
Ok followed the instructions at [GUIDE] How to root 10.5.1.A.0.283 / 10.5.1.A.0.292 [Locked Bootloader] , read carefully again to flash the .230 kernel. Flashed the XZDualRecovery and got the TWRP recovery back.
Restored the old 4.2.2 TWRP backup , hoping that everything would go back to normal. However with a successul restore and a reboot, I was amazed to see I still have no network connectivity. The baseband version is "9x15A-ACEFWMAZQ-30110068-44" . Another noticeable thing was that after the restore and first boot, I still got the "prototype device" message again, which was not there when I first booted the device with original stock 4.2.2 ROM before this flashing adventure began.
Any ideas what may have gone bad.
Thanks.
=======================================
Just got to know that my device is a BROWN device, its IMEI number starts from 0044 so it is a prototype. Any ideas is it really good or bad to have one. Also I see that after another restore of the original stock 4.2.2 ROM it is barely getting the signals indoor (1 bar only). The signal reception is very weak and sporadic . Should i keep the device or not and is there any remedy or network signal strength.
Thanks.
Click to expand...
Click to collapse
Firstly I love the detail you have provided which would save you and me a lot of time to pinpoint the exact problem and work it accordingly.
Firstly, I would suggest that if you have a box or any other receipt that shows your exact device name with its basebands. Where did you buy it from and what is your exact location so we can guess your region. This is the time to show it now. Also which basebands work in your location can also help us out.
The problem you have made it flashed basebands of a different variant which has resulted in loss of network. So to fix it we need, and there are three ways about it.
First, download Sony PC companion and try to repair your phone and see if that helps.
Secondly, download flashtool and ftf for your device (make sure you select the right variant this time. Choosing for wrong device can hard brick your phone. so beware) and flash your phone with it.
If all this fails, you go to Sony flashtool called Emma. Download it and try to flash it with that.
You can google how to use every tool on xda and I am sure you would find a lot of guides for that.
Quote me back in case you expect an answer
I have a SM-G900V that was on a custom 4.4.4 ROM. I'm selling the phone and wanted to give a stock but updated phone to the guy.
I downloaded the latest for 6.0.1 for the Verzion G900V and flashed it in Odin. It got a write fail. I tried again and it went further but then got another write fail.
Now when I try to boot the phone it goes to Software update failed error. I can boot again by long holding the power button. The phone is still recognized in Odin.
The bootloader was unlocked
The emmc was 15.
The build number of the custom ROM was: Build: KTU84P- G900VRU1ANI2
I'll keep searching for a solution but the guy I'm selling the phone to is freaking out so any and all help would be much appreciated.
update
I tried flashing the same build as what was on the phone AN12 and it failed with an Auth fail error in Odin. I did some research and saw that could be a CSC problem. I tried using Kies because I read you can find the CSC code that way. I couldn't get Kies to 'talk' to the phone. It saw that a phone was connected but it wouldn't created the connection. I tried firmware recovery but I need the serial number and Samsung in its infinite wisdom doesn't put the serial number on the sticker inside the phone (at least it doesn't on US Verizon).
It's a phone from Verizon (originally bought on contract) in the US and I have been using US Verizon downloads from either updato or sammobile (for the 4.4.4)
I could realy use some help. I'd like not to bork the phone by just trying hail mary solutions.
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
how do I do this?
I can get into the boot menu and have tried all options as in:
Wipe cache partition
Wipe data/factory reset
reboot system now
still stuck in boot loop (1st power on screen)
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
What did you flash in your second attempt?
stonedpsycho said:
What did you flash in your second attempt?
Click to expand...
Click to collapse
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Greeny308 said:
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Click to expand...
Click to collapse
It should boot after flashing that, it could be a hardware problem preventing a successful boot :-( Probably worth trying different filmware though, you could try BTU (UK) or XEU (UK & Ireland)
Bro i will advice you to just get over this stock rom and install some custom rom.
You can install a custom recovery like twrp through odin and then using that recovery install some custom rom made for your device.
All these you might find in your device's xda forum.
Brp i just checked and found that galaxy note 8 has plethora of custom roms available just install the one which you like.
You can see the installation process on youtube.