Hi Team,
After waiting for t he OTA for quite some time. I decided to manually flash 5.1.1 on my G925F S6 Edge. I downloaded the following firmware at home. And tried to flash at my work. Now it flashed just fine , but i am stuck at a nasty boot loop. I have access to download mode , but no recovery. How do i turn the phone off now ? Since i cannot download any bigger files at work.
Also please recommend a 5.1.1 firmware to flash on my phone . I believe my phone`s origin is from Thailan
Update : 1
Tried 2 different Images (UK/ Thailand). Everything flashes just fine. No Odin Errors etc . But the phone gets stuck at Powered by Android
Update 2:
Tried BTU image (UK based) did`nt work too
Update 3 :
here are some screen shots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really need to turn this thing off !! Unable to find anything in search as well
have you tried flashing the same firmware again? Make sure you have stared Odin as an Administrator
leekslk said:
have you tried flashing the same firmware again? Make sure you have stared Odin as an Administrator
Click to expand...
Click to collapse
yes , did that thrice but to no avail. Each time ran odin as admin
It happened the same to update via OTA, I took him for service of Samsung and up within 15 days will not tell me what's wrong, but I was told that possibly was a problem with the motherboard!
i download and flashed "G925FXXU2BOGB_G925FOXA2BOGB_XEU" , it flashed fine using ODIN but stuck at Powered by Android. I flashed it atleast 3 times but no use.
Then i downloaded and flashed "G925FXXU2POGU_G925FTHL2POGU_THL" . thailand based firmware but its doing the same thing. My phone`s origin was Thailand thats why i downloaded it.
Its been 6-7 hours since the phone is stuck , i cant even shut it off. I can only go to the Download Mode. I could really use some help now. Can someone please help me out here.
I am downloading the BTU 5.1.1 UK version now. I have tried atleast 6 times now. But its not going past the powered by Android logo.
I also cannot access the recovery as well. I am getting out of Ideas now . I can only access the download mode.
Lowresolution said:
i download and flashed "G925FXXU2BOGB_G925FOXA2BOGB_XEU" , it flashed fine using ODIN but stuck at Powered by Android. I flashed it atleast 3 times but no use.
Then i downloaded and flashed "G925FXXU2POGU_G925FTHL2POGU_THL" . thailand based firmware but its doing the same thing. My phone`s origin was Thailand thats why i downloaded it.
Its been 6-7 hours since the phone is stuck , i cant even shut it off. I can only go to the Download Mode. I could really use some help now. Can someone please help me out here.
I am downloading the BTU 5.1.1 UK version now. I have tried atleast 6 times now. But its not going past the powered by Android logo.
I also cannot access the recovery as well. I am getting out of Ideas now . I can only access the download mode.
Click to expand...
Click to collapse
no error message on ODIN? Sorry, trying to understand so I could try to help.
Would be great to take a screenshot of ODIN when it's "done" and a photo of the phone, before disconnecting or restarting.
Also I assume you're using a G925F
Flashing the 5.1.1 BTU did`nt work as well. I am out of options now . Have tried a total of 3 , 5.1.1 Images but none of them worked. Everything gets stuck at Power by Android logo for hours. I cant access recovery as well. Just the ODIN mode.
Giving into warranty is not an option since i bought it used. Any idea if this could be a hardware based issue ? keeping in mind it was working flawlessly uptil this morning on 5.0.2 !
What would i do with a 600$ brick :'(
leekslk said:
no error message on ODIN? Sorry, trying to understand so I could try to help.
Would be great to take a screenshot of ODIN when it's "done" and a photo of the phone, before disconnecting or restarting.
Also I assume you're using a G925F
Click to expand...
Click to collapse
Finally someone see`s my thread. I am all posting screen shots in a minute .
Screen shots updated in Post # 1
Any one ?
erikpr10 said:
It happened the same to update via OTA, I took him for service of Samsung and up within 15 days will not tell me what's wrong, but I was told that possibly was a problem with the motherboard!
Click to expand...
Click to collapse
I have read that a HARD brick is a problem with the motherboard.
Yes, from the looks of it I think this is a motherboard problem...I'd suggest you take this to a Samsung repair shop and tell them that the phone has been like this since "morning". Since you haven't rooted the phone, they will repair it free of cost most likely. Should they ask you for proof of purchase, tell them you got it as a gift from an uncle who's in Bahamas with to cell connection at the moment and cannot be contacted...worst case, act dumb and ask them to define what proof of purchase means...
But seriously, I would take this to the Samsung store. It so happened to me that I had a hairline crack in a Samsung A5 and although I got the device for free from the telecom provider (who said that it would cost me $100 to repair) the Samsung repair shop replaced the screen at no extra cost...It all depends on how you ask to the people there..try to be in your best behaviour and act as naive as you can...Trust me they will repair it for you...All the best...
Worst case scenario and if they do ask you to shell out $500...I'd suggest buying another phone which is not a Samsung...
Lowresolution said:
Any one ?
Click to expand...
Click to collapse
Alright, bringing it to the service centre is your worst case scenario (of which you already know about).
Here's what I see and agree, ODIN flashed fine, stuck at "powered by android" boot screen.
But let's back track slightly.
1) Can you remember which firmware you were on before you flash the 3 different firmwares.
2) what else have you flashed, did you try to root or something?
3) have you tried to use smartswitch to "fix" the phone (sorry, I know this isn't very helpful, but thought I pointed it out. Also it may take about 30 minutes for smartswitch to fix your phone if it really is fix-able to use the emergency restore firmware or something along this line)
4) I have a hypothesis that you came from 5.0.2 and 5.1.1 is leaving you in a "booting" screen forever so I am thinking the recovery difference is the culprit. It's likely that you can unbrick your phone by flashing the firmware that you were on before flashing these 3 new firmwares (back to point 1). Hence, best way to help yourself now is try to recall which EXACT firmware you were on before. Perhaps more helpful would be a) which region was the phone on b) was it 5.0.2?
5) alternate trouble shoot to find out more information, are you able to boot into recovery. Would like to see what "recovery" version you might be on
let's see if we can try to save your paperweight
This is a longshot and will trip knox but flashing twrp and seeing where that takes you?
Here is the solution from Vietnam and i can sure it's work !
Download this:
G925F: http://www.fshare.vn/file/KYYMWF42LLXM
G920F: http://www.fshare.vn/file/G2MN8UDXFX6P
G925T: http://www.fshare.vn/file/MSQ2TPTRZGYA #Mega
Just flash AP and BL in Odin and it will boot
smartmobee said:
Here is the solution from Vietnam and i can sure it's work !
Download this:
G925F: http://www.fshare.vn/file/KYYMWF42LLXM
G920F: http://www.fshare.vn/file/G2MN8UDXFX6P
G925T: http://www.fshare.vn/file/MSQ2TPTRZGYA #Mega
Just flash AP and BL in Odin and it will boot
Click to expand...
Click to collapse
I opened them up using VPN. Its a firmware actually
G925FXXU2BOFJ_G925FOXA2BOFJ_XEU(4File)_ChoiMobile.VN.zip
Can someone tell me if its safe to flash it up ? Also can you upload this over to mega ? downloading through VPN is v v slow, like 5 kb/sec
leekslk said:
Alright, bringing it to the service centre is your worst case scenario (of which you already know about).
Here's what I see and agree, ODIN flashed fine, stuck at "powered by android" boot screen.
But let's back track slightly.
1) Can you remember which firmware you were on before you flash the 3 different firmwares.
2) what else have you flashed, did you try to root or something?
3) have you tried to use smartswitch to "fix" the phone (sorry, I know this isn't very helpful, but thought I pointed it out. Also it may take about 30 minutes for smartswitch to fix your phone if it really is fix-able to use the emergency restore firmware or something along this line)
4) I have a hypothesis that you came from 5.0.2 and 5.1.1 is leaving you in a "booting" screen forever so I am thinking the recovery difference is the culprit. It's likely that you can unbrick your phone by flashing the firmware that you were on before flashing these 3 new firmwares (back to point 1). Hence, best way to help yourself now is try to recall which EXACT firmware you were on before. Perhaps more helpful would be a) which region was the phone on b) was it 5.0.2?
5) alternate trouble shoot to find out more information, are you able to boot into recovery. Would like to see what "recovery" version you might be on
let's see if we can try to save your paperweight
Click to expand...
Click to collapse
Thanks so much for a detailed reply my friend
1-)I dont remember exactly which firmware i was one , but i remember checking the " Samsung Phone Info App" and seeing that it was from Thailand and was on 5.0.2
2-)Besides the 3 firmwares , i did not flash anything else
3-)I tried smart switch as well, it was downloading something. But after that it said that the mode in which the phone is on is not supported by smart switch and i`ll have to put it in recovery mode
4-)Again i only remember that the firmware i was on was from Thailand and was 5.0.2 , besides that i dont remember :'(
5-)I have tried numerous time , but it does not boot into recovery mode
I will so thankfull if you guys can save me from having such an expensive paper weight
Duncan1982 said:
This is a longshot and will trip knox but flashing twrp and seeing where that takes you?
Click to expand...
Click to collapse
I have`nt done that Yet. I have no issues in Tripping Knox , since i already have no warranty on this and i know for sure that the service center here wont take the phone in warranty since i bought it used
Lowresolution said:
I opened them up using VPN. Its a firmware actually
G925FXXU2BOFJ_G925FOXA2BOFJ_XEU(4File)_ChoiMobile.VN.zip
Can someone tell me if its safe to flash it up ? Also can you upload this over to mega ? downloading through VPN is v v slow, like 5 kb/sec
Click to expand...
Click to collapse
believe me, or you can use this method: (will trip Knox)
Flash TWRP recovery using Odin from this topic
Use an OTG cable (in case your phone cannot be turned on) to transfer this ROM
Flash that ROM using TWRP
100% work
Related
First of all, thanks for reading, and i hope this problem/my hesitation could be resolve.
This is not my phone, a friend of mine gave this to me in its current condition.
His story:
The phone slipped off from his pocket while hes riding a bike. it met hard road screen down, bounce two or three times and then got hit by a car.
it then just scattered on he road into four pieces, the phone, battery cover, battery and soft tpu case. surprisingly when my friend picked it up, reassemble it and try to turn it on, it did turn on. and no, the screen haven't crack, not even a scratch on the screen. just some dent on the plastic around the screen and some scratches on the battery cover. damn this thing is rock solid.
then came the problem. out of nowhere the phone suddenly ask for somekind of unlock code. no, its not simcard lock code, my friend haven't setup this phone to ask for simcard lock code when boot, even so when he try his simcard lock code, the phone still showed wrong password.
he dont now what in the world code it asked, neither do i. it asked the password with and without any simcard inserted.
so he gave this phone to me knowing that i know this kinda thing. but frankly i've never own an s2 before, so i came here today as a noob
i did own a samsung phone before, a galaxy ace, and currently owning a sony live walkman, so i'm not really and android noob literally.
from my understanding this phone is full stock gingerbread, never flashed, never rooted before.
so i try to enter recovery mode to try to do factory reset, i can successfully enter the recovery, and can choose to do factory reset, but then after confirming to do factory reset it ask for password again.
so i cant even do factory reset from stock recovery. my last choice now is reflashing (i can still access download mode).
btw picture worth than a thousand words eh?
when booting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the password request screen after booting:
the stock recovery:
the password request screen after confirming to do factory reset from the recovery:
So my question is:
1- from the booting picture above, this is the "original" s2 with exynos cpu right?
2- any other way to overcome this problem without reflashing? adb access or something?
3- if i choose to reflash, can i do it with heimdall from linux? i'm a linux user.
4- is I9100XWLPO_I9100NEELP4_I9100XXLQ6_NEE.zip the correct stock rom to flash? its not the infamous leak stock ics that caused hardbrick when wiping from recovery, right?
5- if i can successfully reflash with stock rom (if i do, i planned to reflash with stock ics), then the damn unlock screen still appear what can i do next?
an0nym0us_ said:
First of all, thanks for reading, and i hope this problem/my hesitation could be resolve.
This is not my phone, a friend of mine gave this to me in its current condition.
His story:
The phone slipped off from his pocket while hes riding a bike. it met hard road screen down, bounce two or three times and then got hit by a car.
it then just scattered on he road into four pieces, the phone, battery cover, battery and soft tpu case. surprisingly when my friend picked it up, reassemble it and try to turn it on, it did turn on. and no, the screen haven't crack, not even a scratch on the screen. just some dent on the plastic around the screen and some scratches on the battery cover. damn this thing is rock solid.
then came the problem. out of nowhere the phone suddenly ask for somekind of unlock code. no, its not simcard lock code, my friend haven't setup this phone to ask for simcard lock code when boot, even so when he try his simcard lock code, the phone still showed wrong password.
he dont now what in the world code it asked, neither do i. it asked the password with and without any simcard inserted.
so he gave this phone to me knowing that i know this kinda thing. but frankly i've never own an s2 before, so i came here today as a noob
i did own a samsung phone before, a galaxy ace, and currently owning a sony live walkman, so i'm not really and android noob literally.
from my understanding this phone is full stock gingerbread, never flashed, never rooted before.
so i try to enter recovery mode to try to do factory reset, i can successfully enter the recovery, and can choose to do factory reset, but then after confirming to do factory reset it ask for password again.
so i cant even do factory reset from stock recovery. my last choice now is reflashing (i can still access download mode).
btw picture worth than a thousand words eh?
when booting:
the password request screen after booting:
the stock recovery:
the password request screen after confirming to do factory reset from the recovery:
So my question is:
1- from the booting picture above, this is the "original" s2 with exynos cpu right?
2- any other way to overcome this problem without reflashing? adb access or something?
3- if i choose to reflash, can i do it with heimdall from linux? i'm a linux user.
4- is I9100XWLPO_I9100NEELP4_I9100XXLQ6_NEE.zip the correct stock rom to flash? its not the infamous leak stock ics that caused hardbrick when wiping from recovery, right?
5- if i can successfully reflash with stock rom (if i do, i planned to reflash with stock ics), then the damn unlock screen still appear what can i do next?
Click to expand...
Click to collapse
well i would suggest u to flash either LP7 or LPS one since they r official ones, thro odin and check for the issue
not the solid answer i'm looking for, but thanks anyway
anyone else?
...
MistahBungle said:
That's the most solid answer you're going to get. If it were really really easy to bypass the only form of security the phone has it would defeat the purpose.
Sun's right; nothing stopping you rebooting into download mod & flashing a stock rom.
Click to expand...
Click to collapse
did u guys even read?
i'm not just asking about if i can just flash with stock rom, and i know i can, the only thing stopping me is the 5 question in bottom of op (did u even read it?), and to add more its not my phone, its my friend's, if i can avoid flashing and preserve his data i'd go that path to not flash and preserve his data.
I read it all
The advice you've just got is sound, if indeed the story is true. I'm tempted to doubt it, as I've never heard of a phone putting a password lock on itself.
scayre32 said:
The advice you've just got is sound, if indeed the story is true. I'm tempted to doubt it, as I've never heard of a phone putting a password lock on itself.
Click to expand...
Click to collapse
thats what i've been wondering. and the accident of slipping from hand on running bike is true, i was there.
and the phone currently with me, asking for security code when booting and when trying to wipe from stock recovery, with or without simcard.
an0nym0us_ said:
thats what i've been wondering. and the accident of slipping from hand on running bike is true, i was there.
and the phone currently with me, asking for security code when booting and when trying to wipe from stock recovery, with or without simcard.
Click to expand...
Click to collapse
well let me be honset with u my friend, just a slip and the phone been dropped to ground doesnt bring about itself the issue what ur friend phone is having right now. may be something else which ur friend might have done silly and not telling u the same(truth).
the only way to resolve is flashing a stock rom, else ur friend will have an expensive piece of Paper weight
Sun90 said:
well let me be honset with u my friend, just a slip and the phone been dropped to ground doesnt bring about itself the issue what ur friend phone is having right now. may be something else which ur friend might have done silly and not telling u the same(truth).
the only way to resolve is flashing a stock rom, else ur friend will have an expensive piece of Paper weight
Click to expand...
Click to collapse
i know, but even how dodgy it is, flashing with stock rom via odin would erase all evidence in case my friend not being honest and this is stolen phone or anything.
an0nym0us_ said:
i know, but even how dodgy it is, flashing with stock rom via odin would erase all evidence in case my friend not being honest and this is stolen phone or anything.
Click to expand...
Click to collapse
I'm guessing the phone is stolen.... I'm guessing the lockscreen is because after realizing the phone was stolen they remotely locked it via an app... if I were you id get that phone out of my posession until you can confirm it is not indeed a stolen phone..... and fyi the data on the phone isn't the only way to identify your phone... as a matter of fact, as easily as data is wiped on these phones, its not even a good way....
an0nym0us_ said:
i know, but even how dodgy it is, flashing with stock rom via odin would erase all evidence in case my friend not being honest and this is stolen phone or anything.
Click to expand...
Click to collapse
:laugh::laugh: well now i think ur in a confused state for sure right.
and what do u mean by 'Stolen phone or anything'
1)is it not ur friends Phone in the first place?
2)hasn't he got any proof (purchase bill)from any merchant from whom he has purchased the same?
...
Sun90 said:
:laugh::laugh: well now i think ur in a confused state for sure right.
and what do u mean by 'Stolen phone or anything'
1)is it not ur friends Phone in the first place?
2)hasn't he got any proof (purchase bill)from any merchant from whom he has purchased the same?
Click to expand...
Click to collapse
thing is, i saw he use this phone from weeks ago, without this damn annoying lock screen. i was there when the accident with the bike happen last week, and since that this lock screen appear on every boot, and on attempt to wipe data from recovery, with or without any simcard.
and to answer your question.
1- not mine, its my friend's.
2- he only had a charger, said he buy this phone second hand from his sister's boyfriend two weeks ago.
so me myself not sure if this phone legit, or a stolen phone.
but if its indeed a stolen phone why can he use it without any problem, but the lockscreen only appear after the accident?
if i cant bypass the lockscreen or pull any data from this phone then i'll just flash with odin tonight.
and the request for security code when trying to wipe data from recovery still bugging me tho. hows that possible? i mean a full working gui to input code including a fully working touch keyboard, in stock recovery
The only answer for this is....flash a stock firmware via odin,or else use the phone as an ash tray/plate
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
an0nym0us_ said:
if i cant bypass the lockscreen or pull any data from this phone then i'll just flash with odin tonight.
and the request for security code when trying to wipe data from recovery still bugging me tho. hows that possible? i mean a full working gui to input code including a fully working touch keyboard, in stock recovery
Click to expand...
Click to collapse
The request for a security code in recovery is in case you are trying to sneakily get past the lock by factory resetting.
He could have used the phone, even if it was stolen, as easy as 1 2 3 if people don't put a password on it and instead use picture swype to unlock. I believe you are holding a shady phone and in fact I agree with everyone else here. Password protection screens don't just appear from dropping or crashing the phone.
The other fact is, there is this little detail in your password screen that says "emergency calls only" that only happens when the simcard isnt unlocked for access by the code thats on it.
Out of curiosity, what exactly does one do if they have forgotten or mis-entered a security password on their Stock ICS 4.0.3 device? Just reflash stock firmware back on the device and thats it?
lurker316 said:
Out of curiosity, what exactly does one do if they have forgotten or mis-entered a security password on their Stock ICS 4.0.3 device? Just reflash stock firmware back on the device and thats it?
Click to expand...
Click to collapse
Correct me if I wrong but I think that than it can ask you for your gmail t.Once it happened to me can't remember on what firmware or if I wasn't on my other phone,an HTC desire.
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
bartoloandre98 said:
Correct me if I wrong but I think that than it can ask you for your gmail t.Once it happened to me can't remember on what firmware or if I wasn't on my other phone,an HTC desire.
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
Click to expand...
Click to collapse
Yea it'll ask for your Gmail password then that can reset the screen lock. Damn this is a dodgy thread
Sent from my GT-I9100 using xda premium
You could sell the LCD on eBay for £80,so at least he's not lost all his outlay.
sent by my s2 using xda premium
Hi guys
First of all, I've searched and found out that many others like me had problems finding out what stock firmware they should use by dialing #*1234# (I'm just getting "Connection problem or invalid MMI code") and after having taking my chances I decided to try and flash with the nordic firmware which should be the correct one (opened the .md5 file under PDA in Odin).
I searched the I9100 forums for "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again" but with no luck getting my problems fixed.
I bought my SII about one year ago and I've been using the SuperNexus rom, tried to flash the SuperNexus2 rom when I run into problems with the phone dying on me (when I plug in the charger I still have power left in the battery) so I decided I wanted to try and go back to using the stock rom (hopefully also with OTA updates working).
I've downloaded the I9100XWLSD_I9100OXXLS6_I9100XXLS8_NEE firmware and I have tried flashing it with Odin3 1.3, Odin3 1.85 and Odin3 3.04 which was included with the firmware (Downloaded from Sammobile.com) but with no luck. Sometimes I think it began the flashing process (in older version of Odin, ending up with red FAIL) and sometimes it stalled setting up the connection. From what I understand the firmware includes a new modem and other items (correct me if Im wrong)
I've also wiped cache, factory reset the phone and wipe dalvik in CWM before flashing. I also ran Chainfire's TriangleAway to reset the flash counter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The guides I've been reading said that the ID:COM thing in Odin should be yellow and even thou the color has been correct the flash failed
I have Kies installed (and removed all the KIES software in the task manager before starting Odin), I have tried multiple USB ports on the computer.
Luckily I managed to flash Clockwork Recovery with Odin and managed to restore an old ICS version of Cyanogenmod so I got the phone up and running again but Im not giving up, I want to try Stock (rooter or unrooted doen't matter, Im pretty sure I can root it later). Right now I have SuperNexus2 but the phone still dies on me from time to time (no warning, screen just goes black)
This is what the phone information says right now
Since I cannot use the *#1234# to get information on what stock firmware I should use Im kinda stuck, having read the forum at Swedroid I've found out that the nordic firmware I downloaded should be the correct one.
All help is appreciated
Hi. I don't think dialer codes work on non stock dialers. Also the download may be corrupt have you tried to re-download and check the md5 sums?
Sent from my GT-i9100 using xda premium
Mobile Odin.
Sent from the little guy
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
HANDSY said:
Hi. I don't think dialer codes work on non stock dialers. Also the download may be corrupt have you tried to re-download and check the md5 sums?
Sent from my GT-i9100 using xda premium
Click to expand...
Click to collapse
S III codes work.
Sent from the little guy
gastonw said:
Mobile Odin.
Sent from the little guy
---------- Post added at 08:00 PM ---------- Previous post was at 07:53 PM ----------
S III codes work.
Sent from the little guy
Click to expand...
Click to collapse
On AOSP dialers? I was not aware of that, apologies for incorrect information given.
Sent from my GT-i9100 using xda premium
HANDSY said:
On AOSP dialers? I was not aware of that, apologies for incorrect information given.
Sent from my GT-i9100 using xda premium
Click to expand...
Click to collapse
No need to, I don't know either.
Sent from the little guy
gastonw said:
Mobile Odin.
Sent from the little guy
Click to expand...
Click to collapse
Went with Mobile Odin and it worked fine (I got Triangle Away for free here at XDA so buying Chain fires awsome apply was the least I could do)
Kudos for helping me out you guys
ingels said:
Went with Mobile Odin and it worked fine (I got Triangle Away for free here at XDA so buying Chain fires awsome apply was the least I could do)
Kudos for helping me out you guys
Click to expand...
Click to collapse
Lol 2x1 kinda thing
Sent from the little guy
I had some problems when I returned to Samsung Stock (which looks awful btw, everything is huge and looks like it was designed for people with bad eyes). When the battery drained the phone freezed (still does) and I couldnt reboot the phone (locked on the Galaxy SII I9100 boot logo), a factory reset fixed it thou.
I must praise Chainfire for his Mobile Odin which not only flashes stuff without adding to the flashcounter but also let's you root while you flash (even stockroms)
Samsung stock being....GB?
Sent from the little guy
gastonw said:
Samsung stock being....GB?
Sent from the little guy
Click to expand...
Click to collapse
I9100XWLSD Download (Thanks To SamMobile!)
Base Firmware: I9100XWLSD (4.1.2)
Region: Europe
Country Nordic Countries
Carrier: Unbranded
Build Date: 31 January 2013
Modem: XXLS8
CSC: OXXLS6
That ROM you think is awful?
Sent from the little guy
Sv: [Q] Odin fail going stock (Firmware upgrade encountered an issue). Help pls
gastonw said:
That ROM you think is awful?
Sent from the little guy
Click to expand...
Click to collapse
I don't care much for Samsungs Touchwiz UI or whatever they call it. I prefer a clean system and not forced installed software. Right now I'm more than happy having a stable phone
Skickat från min Nexus 7 via Tapatalk 2
ingels said:
I don't care much for Samsungs Touchwiz UI or whatever they call it. I prefer a clean system and not forced installed software. Right now I'm more than happy having a stable phone
Skickat från min Nexus 7 via Tapatalk 2
Click to expand...
Click to collapse
Supernexus 2 no good?
Sent from the little guy
Sv: [Q] Odin fail going stock (Firmware upgrade encountered an issue). Help pls
gastonw said:
Supernexus 2 no good?
Sent from the little guy
Click to expand...
Click to collapse
I had some problems when I upgraded from SuperNexus to SuperNexus2 (tried build 1 and 2). Phone died from time to time and I had problems rebooting and starting up the phone again and that's when I decided to go back to stock. I tried Odin and the current stock I have installed and failed. Found a CWM backup of Cyanogemod and got that up and running...
I wonder if I might could have fixed the problem with a factory reset but I'm pretty sure I tried that.
The SuperNexus rom was wonderful, a pure Android experience and my number one choice to run. I think I should try to calibrate the battery and see if I can get some more power out of the battery (13 months old). Seems like the phone dies sometimes (the battery percentage was 0% and still running some days ago (did a clear battery status in CWM. I wonder if it might have been a dumb idea)
Skickat från min Nexus 7 via Tapatalk 2
Sv: [Q] Odin fail going stock (Firmware upgrade encountered an issue). Help pls
Got my S2 back after sending it in for a guarantee repair. Seems like the phone was imported from Schweiz (got it from an Swedish online shop) and therefore didnt get it repaired (all S2's from Samsung Sweden comes with a two year warranty) so my problematic phone is still the same.
I tried cleaning the USB connector but that didn't help either.
Got the Swedish Samsung stock installed (not rooted) and any pointers to what I could try will be helpful.
Feels like flashing another stock rom wouldn't help me (not sure what stock rom it came with).
Any ideas?
I've read the whole thread, what's wrong with your device again?
Sv: [Q] Odin fail going stock (Firmware upgrade encountered an issue). Help pls
gastonw said:
I've read the whole thread, what's wrong with your device again?
Click to expand...
Click to collapse
The phone worked flawlessly with some of the earlier versions of JB (SuperNexus) and then all of a sudden (after I upgraded to SuperNexus 2) it started to die on me from time to time (still had power in the battery). I red flashed, and cleared everything (battery stats. dalvik, cache and also did a number of factory resets) without things getting any better (still died on me). Could be browsing the web with the regular browser or Chrome, using the Facebook app or FB messenger.
Phone and battery is about 15 months old and the phone is used every day for Facebook and browsing the web.
Entered Clockwork and found an ICS backup of Cyanogemod which I restored, same problems occurred.
So, I got Mobile Odin and the stock 4.1.2 Samsung rom which I have one the phone now (not rooted) and tried to send it in for a guarantee repair (I called the company I got the phone from whom told me that there was 1 year warranty. I also called Samsung Support whom told me to send it in anyway, asking for their 2 year guarantee which the repair center dismissed).
Also tried cleaning the USB connector (compressed air in a can) but the problem still exists.
Skickat från min Nexus 7 via Tapatalk 2
ingels said:
The phone worked flawlessly with some of the earlier versions of JB (SuperNexus) and then all of a sudden (after I upgraded to SuperNexus 2) it started to die on me from time to time (still had power in the battery). I red flashed, and cleared everything (battery stats. dalvik, cache and also did a number of factory resets) without things getting any better (still died on me). Could be browsing the web with the regular browser or Chrome, using the Facebook app or FB messenger.
Phone and battery is about 15 months old and the phone is used every day for Facebook and browsing the web.
Entered Clockwork and found an ICS backup of Cyanogemod which I restored, same problems occurred.
So, I got Mobile Odin and the stock 4.1.2 Samsung rom which I have one the phone now (not rooted) and tried to send it in for a guarantee repair (I called the company I got the phone from whom told me that there was 1 year warranty. I also called Samsung Support whom told me to send it in anyway, asking for their 2 year guarantee which the repair center dismissed).
Also tried cleaning the USB connector (compressed air in a can) but the problem still exists.
Skickat från min Nexus 7 via Tapatalk 2
Click to expand...
Click to collapse
And you got your phone back, but the same issues.
It sounds like a battery issue to me, borrown an s2 battery and try it out.
You can always contact samsung and claim your 2 year warranty. Customers Right could help in that warranty war.
Sv: [Q] Odin fail going stock (Firmware upgrade encountered an issue). Help pls
C
gastonw said:
And you got your phone back, but the same issues.
It sounds like a battery issue to me, borrown an s2 battery and try it out.
You can always contact samsung and claim your 2 year warranty. Customers Right could help in that warranty war.
Click to expand...
Click to collapse
Yeah, the reason to why there was no service made was that the phone was an imported S2 and not one from Samsung Nordic (or Sweden). The Phone has been up and running for 24h since I got it.
Got the tip to clean the USB connector since dirt and stuff might get the phone to act weird. The Phone beeps sometimes when I try to restart it after it dies and sometimes I have to remove the battery to get it up and running again (usually the battery status is around 40% or less and if I plug in the charger the phone reaches 100% fast (15 mins or so I'd guess).
A new battery is the only thing I have still to try. I guess buying a non original battery can be almost as bad as using the current battery in a short time?
How long could a original battery be useful (for about a days use?)
Forgot to mention that the phone sometimes also locks up. No buttons responding (I think that pressing the power button for 5secs shuts the phone down.. Not 100% sure since this happens much less than the phone dying on me).
Skickat från min Nexus 7 via Tapatalk 2
ingels said:
C
Yeah, the reason to why there was no service made was that the phone was an imported S2 and not one from Samsung Nordic (or Sweden). The Phone has been up and running for 24h since I got it.
Got the tip to clean the USB connector since dirt and stuff might get the phone to act weird. The Phone beeps sometimes when I try to restart it after it dies and sometimes I have to remove the battery to get it up and running again (usually the battery status is around 40% or less and if I plug in the charger the phone reaches 100% fast (15 mins or so I'd guess).
A new battery is the only thing I have still to try. I guess buying a non original battery can be almost as bad as using the current battery in a short time?
How long could a original battery be useful (for about a days use?)
Forgot to mention that the phone sometimes also locks up. No buttons responding (I think that pressing the power button for 5secs shuts the phone down.. Not 100% sure since this happens much less than the phone dying on me).
Skickat från min Nexus 7 via Tapatalk 2
Click to expand...
Click to collapse
Swap batteries for 10 hrs or so.
If he gets issues, your battery is screwed, if you get issues, then we talking hardware.
I bought a I9300 as I was slightly mislead by the seller that the phone could be fixed and would get detected by the PC, which it doesn't.
It's a i9300 and it's blue... and that's all I've got. I'm guessing it's on a stock ROM and stock kernal.
When I attempt to charge the phone or connect to the PC it brings up the screen where the battery is charging but in a crashed state. I turn it on and just get the "Samsung Galaxy S III GT-I9300" screen
Would I be able to send it to a service station still under his warranty and have it returned to me? or is there another way? i'm sure I remember a way of attaching cables to the power board of the phone and restoring it that way but I don't know, maybe I imagined that
I have got another working S3 which is my own, maybe that's of use after reading this:
http://www.xda-developers.com/android/fix-your-soft-bricked-galaxy-s-iii-samsungs-way/
BUT after putting the bootloader on the SD and swapping it to the no power phone how do I copy it over? or this for no powered phones only?
All help is greatly appreciated, thanks guys. Sorry I've got no helpful info about the phone.
UrbanDesigns said:
I bought a I9300 as I was slightly mislead by the seller that the phone could be fixed and would get detected by the PC, which it doesn't.
It's a i9300 and it's blue... and that's all I've got. I'm guessing it's on a stock ROM and stock kernal.
When I attempt to charge the phone or connect to the PC it brings up the screen where the battery is charging but in a crashed state. I turn it on and just get the "Samsung Galaxy S III GT-I9300" screen
Would I be able to send it to a service station still under his warranty and have it returned to me? or is there another way? i'm sure I remember a way of attaching cables to the power board of the phone and restoring it that way but I don't know, maybe I imagined that
I have got another working S3 which is my own, maybe that's of use after reading this:
http://forum.xda-developers.com/showthread.php?t=1916796
All help is greatly appreciated, thanks guys. Sorry I've got no helpful info about the phone.
Click to expand...
Click to collapse
tried factory reset?
Can you get into recovery or download mode?
Sent from my GT-I9300 using xda app-developers app
You need to check with Samsung if they will accept warranty from second user .
You certainly only mess with bootloaders as a last resort.
jje
I've tried holding vol up + power + home but all it does is restart the phone. I'm unsure if that combo is for a rooted device to access CWM or stock.
But i'll press the buttons the phone will turn on and it gets to the GT-i9300 screen and just stops. If I do the buttons again it will just restart and go to the same screen.
I'll see what Samsung recon about the warranty. I'm sure they'll say no
Download mode and post whats on the Odin screen .
jje
JJEgan said:
Download mode and post whats on the Odin screen .
jje
Click to expand...
Click to collapse
Well, it's in download mode.
Currently downloading something, says downloading... do not turn off target!!
It's actually installing drivers on my PC as well
Should say
Odin
Product etc
jje
JJEgan said:
Should say
Odin
Product etc
jje
Click to expand...
Click to collapse
Here it is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got to download the official 4.1.2 firmware before I can try, due to not having a hotfile account it's going to take like 40 minutes just to download 800MB
The details on the phones download screen not Odins .
jje
JJEgan said:
The details on the phones download screen not Odins .
jje
Click to expand...
Click to collapse
oops, haha sorry.
Here's EXACTLY what the screen shows.
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
Downloading...
Do not turn off target!!
Click to expand...
Click to collapse
I am reading that as probable SDS ..
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
A Warranty repair but i am not sure how Samsung handle second users .
jje
JJEgan said:
I am reading that as probable SDS ..
SDS seems to manifest in 2 distinct ways.
1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced
A Warranty repair but i am not sure how Samsung handle second users .
jje
Click to expand...
Click to collapse
So reflashing in Odin is useless?
thanks a lot jje
I'm thinking return to the guy and tell him he can get it fixed with warranty but I would of liked to fix it myself
Can't seem to find these files anywhere:
Check “auto-reboot”, and uncheck all other options.
Click PDA and select the TAR you downloaded.
Tap the Phone button and choose the file named ‘MODEM’. Ignore this step if such file is missing.
Hit the CSC button and choose the file named ‘CSC’. Ignore this step if such file is absent.
Click the PIT button and choose the .pit file.
If there is no such .pit file, please find another firmware which contains a .pit file.
In ODIN, enable Auto Reboot and F. Reset Time options. In case of the Re-Partition option, check it ONLY if you chose a .pit file in the previous step.
Click to expand...
Click to collapse
i downloaded the official fw from sammobile but the .rar didn't include these files
Also, it states custom in the download mode. does this mean it has been flashed?
EDIT: can't find a full flash files for the life of me.
There are 2 ways to flash via Odin. Multiple files or single .tar
Its all irrelevant. You can't flash it. Internal memory has failed and can only be fixed with a motherboard failure.
Custom is a symptom of half SDS which this phone has. Have a look in my [important] sudden death -are you covered? Thread (usually found on page 1 or 2 of general) for more info
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
There are 2 ways to flash via Odin. Multiple files or single .tar
Its all irrelevant. You can't flash it. Internal memory has failed and can only be fixed with a motherboard failure.
Custom is a symptom of half SDS which this phone has. Have a look in my [important] sudden death -are you covered? Thread (usually found on page 1 or 2 of general) for more info
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
The guy I bought it off didn't have a clue what he was doing with the phone, my own phone is covered against the brick bug (not even sure if I have the chip)
Looks like I'm getting a refund OR transferring the warranty and getting it replaced myself.
Thanks a lot guys
one last thing i've just remember to add, can't I use the sd card to act as the eMMC chip? I read somewhere I can, also eMMC replacements can be done with some effort. I'd be interested in giving it a go.
UrbanDesigns said:
The guy I bought it off didn't have a clue what he was doing with the phone, my own phone is covered against the brick bug (not even sure if I have the chip)
Looks like I'm getting a refund OR transferring the warranty and getting it replaced myself.
Thanks a lot guys
one last thing i've just remember to add, can't I use the sd card to act as the eMMC chip? I read somewhere I can, also eMMC replacements can be done with some effort. I'd be interested in giving it a go.
Click to expand...
Click to collapse
I may have seen a guide for that. Search General.
rootSU said:
I may have seen a guide for that. Search General.
Click to expand...
Click to collapse
That's not a guide really, more of an FYI
doesn't say anything about replacing the eMMC chip.
People say to search for the guide but it's not easy to find at all
Hi guys, so yesterday i was trying to re-root my Galaxy S3 after applying the firmware update from Kies (4.2.2 to 4.3), so i opened odin 3.10.6 that i downloaded with the root file, opened it, clicked on AP and gave it "CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5" then hit start, i think it was installing till it got to like 25% and then got stuck, i ket it there and went to see other videos, so i thought probably i installed it on the wrong way, nothing happened yet on odin so i closed it, and this is how everything started, after about 10hours of trying to fix this, i eventually used Kies to apply "Firmware upgrade and initialization", everything went fine, but after the auto-reboot, the phone gave me this error:
E:failed to mount /system (Invalid argument) can't mount '/system '(Invalid argument)
a long list of it, it couldn't mount like anything at all, i tried to boot the phone and nothing happens, eventuually i learned that the only way to get a response from the phone is by plugging it into the computer and going to Download mode (if it's not plugged nothing happens no matter what i do)
I tried rebooting using the download mode and pressing volume down to reboot, and it actually tries to reboot, and shows the samsung s3 logo followed by an android robot like it's applying some updates but shuts down when it reaches like 40% of the process. here's what happens and please note that it only works if the phones is plugged to the computer, if not, i won't get any response from it no matter what buttons i press, and even when it's plugged that's the only way to get a response.
and by the way, i think it can be a battery problem but i have two battries and the samething happened with both of them, and i kept the phone plugged on the charger the whole night hoping it can be charged but nothing happened, (even while plugging it the red right didn't turn on and the phone didn't respond at all)
so, basically, what i "think" i need now is an appropriate list of all Odin files for samsung s3 so i can revive it ( bootloader, PDA, Phone, CSC, and even UMS if necessary) please if anyone can provide me with these files i'd be very grateful. thanks
If you have access to dowload mode, I suggest you to try part 4 of this guide : http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
olimar7184 said:
If you have access to dowload mode, I suggest you to try part 4 of this guide : http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
thanks for the reply, i did already, but i guess i'll go ahead and try it again.
#update: Yup, the same problem, the little Android robot appears to finish the installation and then the phone shuts down again.
chafik94 said:
thanks for the reply, i did already, but i guess i'll go ahead and try it again.
#update: Yup, the same problem, the little Android robot appears to finish the installation and then the phone shuts down again.
Click to expand...
Click to collapse
Then I recommend you to try that instruction http://forum.xda-developers.com/galaxy-s3/help/recovery-twrp-flashing-using-odin-gt-t2680354
If it success you will have access to a custom recovery, this will allow you to flash any rom and unbrick your device
I missed with the bootloader section so probably that's what caused everything, and i couldn't find a proper bootloader for my S3, which is why i thought it'd be better to ask people with better knowledge in this field, i actually found one yesterday which is "ICS_Bootloader_I9300XXALEF.tar" but it failed. so i thought maybe it's not compatible with my firmware or something and in order to get things right i have to reinstall everything as i mentioned earlier, but that's based on mere guessing, I really need people with better knowledge to tell me what to do, i mean as long as odin is getting my phone and writing to it, i believe it can be fixed.
olimar7184 said:
Then I recommend you to try that instruction http://forum.xda-developers.com/galaxy-s3/help/recovery-twrp-flashing-using-odin-gt-t2680354
If it success you will have access to a custom recovery, this will allow you to flash any rom and unbrick your device
Click to expand...
Click to collapse
thanks allot for your help, I tried this and it succeeded but I still can't turn the phone on nor go to recovery mode
If you really can't boot in recovery mode (vol up + home + power) I don't know what to do sorry...
Last possibility that i can think about : Just make sure you are using a I9300 s3, because there are other versions, and the file that you used to root your phone "CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5" (at the beginning of your first post) is for d2att, and I747 not for I9300. + you say latter that you flashed I9300 bootloader "ICS_Bootloader_I9300XXALEF.tar"
The d2att and I747 use qualcomm processor, they are very different from the I9300 with exynos processor.
So check behind the battery witch version do you have.
olimar7184 said:
Just make sure you are using a I9300
Click to expand...
Click to collapse
it is I9300 but i wasn't sure about the auto-root file so that's what brought me here I didn't double check everything before trying the root
here's what the back of the phone says
Model: GT-I9300
FCC ID: A3LGTI9300A
SNN: -I9300GSMH
chafik94 said:
it is I9300 but i wasn't sure about the auto-root file so that's what brought me here I didn't double check everything before trying the root
here's what the back of the phone says
Model: GT-I9300
FCC ID: A3LGTI9300A
SNN: -I9300GSMH
Click to expand...
Click to collapse
to go to recovery :
You tried vol up + home + power ? (when unplugged)
Or just vol up + home when you cancel download mode ? (when plugged)
Because if I understood correctly, when your device is not plugged you can do anything at all ?
And when you plug in your computer it goes in download mode ? Is this also happening when you plug on a wall charger ?
olimar7184 said:
to go to recovery :
You tried vol up + home + power ? (when unplugged)
Or just vol up + home when you cancel download mode ? (when plugged)
Because if I understood correctly, when your device is not plugged you can do anything at all ?
And when you plug in your computer it goes in download mode ? Is this also happening when you plug on a wall charger ?
Click to expand...
Click to collapse
yup, that's exactly what happens, and yes it happen when on the wall charger as well, but the phone doesn't give any sign that it's being charged, and when I unplug it while it's on it turns off immediately. i tried the other method you mentioned about recovery mode, and still nothing happens, the phone shows Samsung galaxy SIII logo and turns off again.
chafik94 said:
yup, that's exactly what happens, and yes it happen when on the wall charger as well, but the phone doesn't give any sign that it's being charged, and when I unplug it while it's on it turns off immediately. i tried the other method you mentioned about recovery mode, and still nothing happens, the phone shows Samsung galaxy SIII logo and turns off again.
Click to expand...
Click to collapse
It's probably an hardware problem, because you said you tried 2 different batteries, and even soft-bricked, the phone should stay on when unplugged
And I have no others ideas how to try to fix it, i am very sorry
olimar7184 said:
It's probably an hardware problem, because you said you tried 2 different batteries, and even soft-bricked, the phone should stay on when unplugged
And I have no others ideas how to try to fix it, i am very sorry
Click to expand...
Click to collapse
Thanks allot for your time, i really appreciate your help, i'll wait if someone else has a solution
olimar7184 said:
It's probably an hardware problem, because you said you tried 2 different batteries, and even soft-bricked, the phone should stay on when unplugged
And I have no others ideas how to try to fix it, i am very sorry
Click to expand...
Click to collapse
I managed to repair my phone today, apparently it was a faulty battery, i used a naked charger to revive it (took off old charger's phone side as shown in the picture, stuck the Black wire to the metal above the positive sign, and the green wire to the one above the negative sign, placed the battery on the phone with the charger in between them and plugged it on the wall for a few seconds, and the phone turned on just fine),
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i re-applied the firmware and this time the android robot where the phone used to shutdown while installing, now completed it's job and the phone rebooted normally, I noticed a yellow text overlaying on the screen, done some more research and found out it is called "Factory mode" (I am a noob you know) so I had to Root the phone to get rid of this problem and this time, thank the Lord, I succeeded in rooting it because I double checked everything lol.
BUT..., Lol when you screw something up, you just have to keep patching it, you fix something here, an other problem appears over there hahaha.
anyways, the problem now is the network, I do have signal and it changes when i put the phone in different places with different signal strengths, and the clock is perfectly updated, but i use the phone as a phone and call people, it gives me this message:
I tried allot of things trying to fix it, nothing seemed to help, and then it came to my mind that probably what I did wrong was download my Service Provider's firmware, maybe the phone Had the international firmware i can't remember and i didn't check it before, the friend i bought it from just told me he brought it brand new but not from a service provider which means it had an international firmware, so now I am downloading a firmware from sammobile that had Unknown in Country, and here's its full title "I9300XXUGNJ2_I9300MSTGNJ1_MST.zip".
My question now, if my theory was wrong and i did somehow apply the right firmware at the first time, will it damage the phone if I applied a different firmware from other Service providers, and i mean this firmware that i am currently downloading?
PS: when the phone turned on the first time the battery had above 70% of charge, i'd like to know what caused the battery to go faulty all of a sudden even while having enough power!
chafik94 said:
I managed to repair my phone today, apparently it was a faulty battery, i used a naked charger to revive it (took off old charger's phone side as shown in the picture, stuck the Black wire to the metal above the positive sign, and the green wire to the one above the negative sign, placed the battery on the phone with the charger in between them and plugged it on the wall for a few seconds, and the phone turned on just fine),
i re-applied the firmware and this time the android robot where the phone used to shutdown while installing, now completed it's job and the phone rebooted normally, I noticed a yellow text overlaying on the screen, done some more research and found out it is called "Factory mode" (I am a noob you know) so I had to Root the phone to get rid of this problem and this time, thank the Lord, I succeeded in rooting it because I double checked everything lol.
BUT..., Lol when you screw something up, you just have to keep patching it, you fix something here, an other problem appears over there hahaha.
anyways, the problem now is the network, I do have signal and it changes when i put the phone in different places with different signal strengths, and the clock is perfectly updated, but i use the phone as a phone and call people, it gives me this message:
I tried allot of things trying to fix it, nothing seemed to help, and then it came to my mind that probably what I did wrong was download my Service Provider's firmware, maybe the phone Had the international firmware i can't remember and i didn't check it before, the friend i bought it from just told me he brought it brand new but not from a service provider which means it had an international firmware, so now I am downloading a firmware from sammobile that had Unknown in Country, and here's its full title "I9300XXUGNJ2_I9300MSTGNJ1_MST.zip".
My question now, if my theory was wrong and i did somehow apply the right firmware at the first time, will it damage the phone if I applied a different firmware from other Service providers, and i mean this firmware that i am currently downloading?
PS: when the phone turned on the first time the battery had above 70% of charge, i'd like to know what caused the battery to go faulty all of a sudden even while having enough power!
Click to expand...
Click to collapse
I don't it will damage your phone, you can try to flash. But instead of taking "unknown" in country, just take your own country.
And check your imei in the setting> about phone > status.
About the battery i really don't know, because i never had this problem with my own s3 before.
olimar7184 said:
I don't it will damage your phone, you can try to flash. But instead of taking "unknown" in country, just take your own country.
And check your imei in the setting> about phone > status.
About the battery i really don't know, because i never had this problem with my own s3 before.
Click to expand...
Click to collapse
I've been trying to fix the IMEI the whole day yesterday, I have the 0049 IMEI i googled it and allot of people had the same problem and the same IMEI, it is not the same as the IMEI behind the battery, one weird thing, when I tried Samsung tool pro to unlock the device, the software said that I had a firmware from Ghana , and I am very sure I was using the Moroccan firmware, now that i installed the unknown firmware it says Belgium, but it shows the same problems, wrong IMEI, wrong Serial Number, and the same error "zTool not found for selected model"
Operation: Unlock
Selected model: GT-I9300
Software version: 24.3
Waiting ADB device... OK
Reading phone info...
Model: GT-I9300
Android version: 4.3
Product code: Not Active
Phone version: I9300BUUGNF1
PDA version: I9300XXUGNJ2
CSC version: I9300MSTGNJ1
CSC country code: Belgium
CSC sales code: MST
HW version: REV__
Phone S/N: 00000000000
Modem board:
RF cal date: none
IMEI: 004999010640000
Checking Super user right... true
Reading nv data... OK
Checking magic... OK
zTool not found for selected model
Done with Samsung Tool PRO v.24.3
i'm really stuck here, been trying everything yet can't find a solution yet
oh, i think that "Ghana" thing happened because i was trying some modem patches like "Modem_I9300_NF1.tar.md5" to unlock the device but they didn't help and i totally forgot about them. lol
chafik94 said:
oh, i think that "Ghana" thing happened because i was trying some modem patches like "Modem_I9300_NF1.tar.md5" to unlock the device but they didn't help and i totally forgot about them. lol
Click to expand...
Click to collapse
Flash the firmware of your country.
And this http://forum.xda-developers.com/galaxy-s3/general/ref-imei-efs-stuff-i9300-including-t2393289 may help you if flashing the firmware of you country don't work
This is not anything new for experienced users, but it will help the newbies.
NOTE: This is, still, the standard process to flash stock ROMs on ANY Samsung running Android, you can use the same drivers, software and key combo for Download mode on other variant or model, what you need to change is the firmware file of course. So feel free to use this guide as reference.
The Stock ROM or Stock Firmware is the software that comes preinstalled in your phone when is brand new, in this case is Samsung's own modification of Android called TouchWiz. If you ran into problems like system apps FCs all the time, bootloops, softbricks,etc... Or if you adventure on the "custom world" (Root, Xposed, aftermarket roms, etc) and things go south, it happens... The stock rom can be flashed to fix those problems and/or get your phone back to a working state again, hence the importance of this procedure.
The tool to flash firmwares on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
Now you need the firmware for your SPECIFIC MODEL, country and carrier are not important, but model IS, deadly. So, don't even try to flash another variant stock rom in you phone, you can and will end up with a hard brick, and good luck fixing that.
Sammobile is the biggest repository for Samsung firmwares, so use that.
J320F and DS - J320F and J320F/DS (Dual SIM) are the same.
J320FN
J320H
J320M
J320FXXU0AQL1 Mirror on MEGA (Netherlands) - I downloaded it from Sammobile and re-uploaded to MEGA. Same .RAR5 stuff and Tecnoriales password.
For any other variant or any Samsung phone for that matter, use the search tool with your model: https://www.sammobile.com/firmwares/
How to flash the Stock ROM using OdinBefore you star please charge your battery to 100%.
1. Install the Samsung Drivers
2. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. Youll see a warning in the screen, accept it pressing Vol+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
4. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
5. Click the AP button and load the *.tar file you downloaded from sammobile. i. e.: J320FXXU0AQL1_J320FDBT0AQK1_J320FXXU0AQI1_HOME.tar.md5 - At this point Odin will hang (stop responding) for some time while it loads the firmware file, that will depend on your PC, from some seconds to a couple of minutes. Be patient.
6. Once Odin un-freezes, go to Options Tab and make sure Re-Partition is unchecked.
7. Press Start to initiate the flashing process, it will take a while. The phone will reboot and when you see a green Pass in Odin it will be safe to unplug your phone..
First boot might take some time depending on the condition of your phone. That's it, your phone should be working again as intended (by Samsung).
Extra: Recovery Mode key combo with phone turned off is Vol+, Home and Power, from here you can perform a Factory Reset.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Sands207 said:
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Click to expand...
Click to collapse
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
mauriciognr said:
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
Click to expand...
Click to collapse
Thank you i appreciate it ?
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
CyberZot said:
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
Click to expand...
Click to collapse
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Scorpionea said:
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Click to expand...
Click to collapse
Thank you very much!
Thank you. Your post hepled me.
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
Click to expand...
Click to collapse
This is the wrong turtorial for you it is to get your phone back to your original software and thats 5.1.1
J320 to Android 7.1
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Click to expand...
Click to collapse
Even though it was mentioned this is the wrong page I don't see why you can't be given some helpful info. The firmware you're looking for to get Android 7.1 is, J320W8VLU2BQK1 J320W8OYA2BQK1 (Its listed for Canada) search for it online.
**Note
If you cant get through the welcome screen. Reset data on recovery
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
CLovecraft said:
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
Click to expand...
Click to collapse
Try to turn on usb debbuging and oem unlock
2gg1 said:
Try to turn on usb debbuging and oem unlock
Click to expand...
Click to collapse
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
so i did this now i wanted to install touchwiz rome on 6,0,1 android but it bootloops i hear i need some baseband but what baseband i need someone can help pls
Looking for J320A
CLovecraft said:
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
Click to expand...
Click to collapse
What did you end up doing to pull this off? I've got the exact same model phone, but cannot seem to find the firmware on Sammobile.