Hello. My xperia m2 says that there are no updates and the phone is up to date but it's with android 4.4.2. Theres 1 secound delay in the sound when I play games or use downloaded apps like youtube also the audio doesn't sound very good. To fix that I need to update the android version but I cant. I connected the phone to my computer and updated it with sony PC companion but the version is still 4.4.2. What should I do? I don't want to use flashtools or anything. I think it's the phone's fault for that and I should give it back to the place where I bought it so they can fix that. The phone is brand new and they already changed my camera because it wasn't working. So what should I do?
I suppose it has to do with the Country of your phone and/or if it is branded. IF after using PC Companion it's still with 4.4.2 I'm afraid your best (and only) option is to use Flashtool. Not sure how it works if it is branded though, you may need to to something to be able to de-brand it.
Well, actually try first to check if 4.4.4 is available in this way:
- Dial *#*#7378423#*#* (*#*#service#*#*)
- Check the number in Service Info/SW Info/Customization version. You just need the xxxx-yyyy part
- Downdload and install Flashtool (it's small. You just need it for checking)
- Run Flashtool
- Go to Devices/Check Updates
- Select your phone double clicking on the id xxxx-yyyy you have got before.
- If the version is 18.3.C (like the one for 3 UK) there is no 4.4.4. the latest ROM is 4.4.2. It must be 18.3.1.C for 4.4.4
My is branded from T-mobile, and i flashed CE ftf to debrande, everything is good except i don't have extra apps that T-mobile puts in. As i know your safe flashing ftf cos it's official Sony's software, just using Flashtool instead of PC Companion and you won't lose warranty, as long as you don't unlock bootloader.
Good Luck.
Xperia M2 D2303 on K.K. 4.4.4
Do I install the flashtool on my computer or on my phone?
foxymount said:
Do I install the flashtool on my computer or on my phone?
Click to expand...
Click to collapse
Obviously on the computer. It's needed to flash the phones from it. Just google it, you find it immediately. Then if you decide to flash a generic 4.4.4 FTF just search around. There are dozens of guides in the Internet.
Alright thanks for your support guys
Hi everyone i have a z3v (used) the version of the firmware is 23.0.E.1.11 and i want to update the device to 23.0.E.1.44 plz help me with intructions; the phone keep saying that its updated but with sonybridge (mac) i get the message : there was an issue with the update engine description: UE error 1100.
thnks
mohkam84 said:
Hi everyone i have a z3v (used) the version of the firmware is 23.0.E.1.11 and i want to update the device to 23.0.E.1.44 plz help me with intructions; the phone keep saying that its updated but with sonybridge (mac) i get the message : there was an issue with the update engine description: UE error 1100.
thnks
Click to expand...
Click to collapse
You should just try the Update Phone option that's already in Settings?
GigaSPX said:
You should just try the Update Phone option that's already in Settings?
Click to expand...
Click to collapse
thnks a lot for u're time i will upload screen captures :good:
mohkam84 said:
thnks a lot for u're time i will upload screen captures :good:
Click to expand...
Click to collapse
Then your next solution is grabbing a program called Xperifirm. It's like Flashtool, but this one supports our phones. It will have the update you need from here:
http://forum.xda-developers.com/cro...perifirm-xperia-firmware-downloader-t2834142/
thnks a lot xperifirm is good app and it contains the firmware for the z3v; the problem is that flashtool doesn't have the z3v in devices list for updating or reinstall the firmware
i think i should wait for update (flashtool) and them i flash it with the 23.0.E.1.44
i just want to remove or fix the flashing Red Frame/Border in my device (the Strict Mode method does not solve it)
i found a way but rooted devices only and u knew; no root available for z3v
mohkam84 said:
thnks a lot xperifirm is good app and it contains the firmware for the z3v; the problem is that flashtool doesn't have the z3v in devices list for updating or reinstall the firmware
i think i should wait for update (flashtool) and them i flash it with the 23.0.E.1.44
i just want to remove or fix the flashing Red Frame/Border in my device (the Strict Mode method does not solve it)
i found a way but rooted devices only and u knew; no root available for z3v
Click to expand...
Click to collapse
Just install the Z3, flashtool and fastboot drivers. They will work for the Z3v
Then flash it
ok thnks; do u have tutorial describes how flashing it
Hey Mates!
I've been looking for a solution but cant find any helpful advices.
I have rooted my Motorola G; 2 days ago, no problem. As soon as I rebooted it, it wont boot.
these are the errors that occur when I try to boot it
-hab check failed for boot
-failed to verify hab image boot
-failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
When I try to go to recovery, it says "no command".
It also says that my device is locked.
Meanwhile I've connected it with my PC and I tried to run the desktop version, but no changes so far.
I'd really need your help
Have you tried to reflash the stock kernel?
Sent from my MotoG3 using Tapatalk
ExaHamza said:
Have you tried to reflash the stock kernel?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No I did not. Do you recommend it?
This "how to" is for Samsung Galaxy, I know, but I guess it would be a similiar way to reflash the stock kernel of the Moto G?
Thanks in advance.
Vairo said:
No I did not. Do you recommend it?
This "how to" is for Samsung Galaxy, I know, but I guess it would be a similiar way to reflash the stock kernel of the Moto G?
Thanks in advance.
Click to expand...
Click to collapse
How do you rooted?
Sent from my MotoG3 using Tapatalk
It seems like the link between your pc and phone was lost during data transfer. Ensure to have the link between the mobile and pc secured. Try replacing the drivers and the usb cable with a good quality one. Loose connections can also cause this type of problem. Something similar happened to me too...
After above flash factory firmware to revive your device first. You can root it subsequently.
You can get all the information in the forum under the Factory Firmware thread. Be careful to download the firmware compatible for your mobile model only.
ExaHamza said:
How do you rooted?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I did root it with RootKing.
arunhebbare said:
It seems like the link between your pc and phone was lost during data transfer. Ensure to have the link between the mobile and pc secured. Try replacing the drivers and the usb cable with a good quality one. Loose connections can also cause this type of problem. Something similar happened to me too...
After above flash factory firmware to revive your device first. You can root it subsequently.
You can get all the information in the forum under the Factory Firmware thread. Be careful to download the firmware compatible for your mobile model only.
Click to expand...
Click to collapse
When I rooted my phone I never connected it with my Moto G; after I couldnt boot it, I tried if it would work somehow. I rooted my device with RootKing which was an app on my device.
Vairo said:
When I rooted my phone I never connected it with my Moto G; after I couldnt boot it, I tried if it would work somehow. I rooted my device with RootKing which was an app on my device.
Click to expand...
Click to collapse
It is not clear if your phone's bootloader has been unlocked or not. Rooting apps have been known to create issues with Moto G3. I tried to root my phone (which has its bootloader unlocked) with the Kingroot app. Although I could succeed and boot the device, the signals vanished. Hence I adapted the traditional way of rooting using the fastboot mode.
If you have still issues of not being able to boot your phone, then please flash stock firmware available in Factory Firmware thread of this forum (you can flash even though your bootloader is unlocked) as per details given there in. You can root your phone later. If you have an unlocked bootloader, there are other posts to guide you how to ulock the bootloader first. Please note you cannot modify software if your bootloader is locked.
Hi everyone.
I really need your help. I've been searching for days now and i can't find any solution.
I've bought Z3 (D6603) on Amazon. Before buying, i checked if it was compatible with my country's LTE bands and it was.
The first time i turn it one it was in Chinese ... or something like that.
3g and 4g are not working at all. Already check with my carrier and the settings are fine.
*#*#SERVICE#*#* shows that i DON't Have the band i need. (BC 4)
It seams to be modified by factory...
I also flashed several roms using flash tools. Nothing...
Another strange thing is that i can't unlock the bootloader (following sony's official page).
Also when i try to reset from Xperia Companion i get a message saying that my phone cannot be identified. Same thing using Emma.
PLEASE! any one can help me?
Let's try and identify the phone model etc.
Go to Settings, About phone (at bottom) and give all the info from there / if possible post screen shots.
As much info on the phone as possible would be good. Just don't post the IMEI number or show it here.
Stuff like build number / baseband version and all that technical stuff will be really useful.
The Chinese on start up makes it seem it's either fake or has the Chinese firmware on it and I don't think they use D6603 in China. Not being identified by Sony tools is another red flag.
Can you not send it back for a refund as it is clearly not in functioning order? Amazon should refund you if the seller has "disappeared"....
Response
Dobsgw said:
Let's try and identify the phone model etc.
Go to Settings, About phone (at bottom) and give all the info from there / if possible post screen shots.
As much info on the phone as possible would be good. Just don't post the IMEI number or show it here.
Stuff like build number / baseband version and all that technical stuff will be really useful.
The Chinese on start up makes it seem it's either fake or has the Chinese firmware on it and I don't think they use D6603 in China. Not being identified by Sony tools is another red flag.
Can you not send it back for a refund as it is clearly not in functioning order? Amazon should refund you if the seller has "disappeared"....
Click to expand...
Click to collapse
Thanks for the quick reply.I'm a new user so i can't post images. I'm from argentina and i'm here right now.. so it's almost imposible to get a refund or return it to the seller.
My phone data:
Model Number 6603
Processor info Qualcomm MSM8974PRO-AC
Android Version 4.4.4
Baseband Version 8974-AAAAANAZQ-00005-05
Compilation Number 23.0.A.2.93
From *#*#SERVICE#*#*
Phone Software version 1282-2729_23.0.A.2.93
File System Version: GLOBAL-LTE_23.0.A.2.93
S1 boot version: 1286-7314 S1_Boot_MSM8974AC_LA3.0_52-2
Customization Version 1286-2777_R9B
Active Customization 1286-2777_R9B
type Number PM-0800-BV
Fuel Guage Firmware Version: The phone doesn't support firmware version read
fcostazini said:
Thanks for the quick reply.I'm a new user so i can't post images. I'm from argentina and i'm here right now.. so it's almost imposible to get a refund or return it to the seller.
My phone data:
Model Number 6603
Processor info Qualcomm MSM8974PRO-AC
Android Version 4.4.4
Baseband Version 8974-AAAAANAZQ-00005-05
Compilation Number 23.0.A.2.93
From *#*#SERVICE#*#*
Phone Software version 1282-2729_23.0.A.2.93
File System Version: GLOBAL-LTE_23.0.A.2.93
S1 boot version: 1286-7314 S1_Boot_MSM8974AC_LA3.0_52-2
Customization Version 1286-2777_R9B
Active Customization 1286-2777_R9B
type Number PM-0800-BV
Fuel Guage Firmware Version: The phone doesn't support firmware version read
Click to expand...
Click to collapse
Okay doesn't look too bad. You're on the original firmware, not the updated version which is Android 6.0.1. You are on 4.4.4.
I would say best bet is to download the Argentina (that's your country so I suggest this) or Generic Global firmware and flash it with flashtool.
http://www.flashtool.net/index.php
Install it and then go to it's install location on your PC and find the drivers .exe and install the flashmode, fastboot and Xperia Z3 drivers. It might not install them all. If you get errors installing drivers you need to disable driver signature verification on the PC so Google how to do it if you don't know how. It is very easy. Then you will be able to install the drivers so it can actually flash the firmware.
With that tool there will be an option in the form of a black circle with XF on it. That is XpiriFirm. Use that to find and download the latest FTF (firmware file) for the D6603. It should end with .291
Follow the instructions on flashtool to flash it. Options will show up asking what parts of the ftf you want to include and exclude. All you need to do here is make sure to EXCLUDE anything that ends in .TA
Please do that as it might brick the phone if not excluded (you won't miss it it is very obvious.)
And it might be a good idea to wipe the data so tick the boxes for wipe so you have a completely clean phone.
Flashtool should then ask you to turn off the phone and hold the vol down button to install the firmware in flashmode.
Let it complete and then it will tell you to turn the phone on.
If there are errors then there might be a problem with the phone. If there is then contact Amazon directly and the seller and explain the situation. With some luck they might help you.
Dobsgw said:
Okay doesn't look too bad. You're on the original firmware, not the updated version which is Android 6.0.1. You are on 4.4.4.
I would say best bet is to download the Argentina (that's your country so I suggest this) or Generic Global firmware and flash it with flashtool.
Install it and then go to it's install location on your PC and find the drivers .exe and install the flashmode, fastboot and Xperia Z3 drivers. It might not install them all. If you get errors installing drivers you need to disable driver signature verification on the PC so Google how to do it if you don't know how. It is very easy. Then you will be able to install the drivers so it can actually flash the firmware.
With that tool there will be an option in the form of a black circle with XF on it. That is XpiriFirm. Use that to find and download the latest FTF (firmware file) for the D6603. It should end with .291
Follow the instructions on flashtool to flash it. Options will show up asking what parts of the ftf you want to include and exclude. All you need to do here is make sure to EXCLUDE anything that ends in .TA
Please do that as it might brick the phone if not excluded (you won't miss it it is very obvious.)
And it might be a good idea to wipe the data so tick the boxes for wipe so you have a completely clean phone.
Flashtool should then ask you to turn off the phone and hold the vol down button to install the firmware in flashmode.
Let it complete and then it will tell you to turn the phone on.
If there are errors then there might be a problem with the phone. If there is then contact Amazon directly and the seller and explain the situation. With some luck they might help you.
Click to expand...
Click to collapse
Already done that.... 5 times (5 different firmware). Still the same.. but with android 6.0.1.
I found 1 more thing that may be a clue: When you hard reset the phone or install a new firmware (same thing..i know) when the system show the welcome Sony's screen and the settings wizard, there is a small toast message that shows "Flash restore service starting: please wait for the Power off button" (not the exact message). After several times a black screen with a Power Off button appears and you can't do anything until you press it. After that the phone restart and it's normal again.
When flashing with the flash tool in the MA TA section you can see AUTO_BOOT and OSV-RESTRICTION. When you try to flash any rom, a warning message appears: "AUTO_BOOT and OSV-RESTRICTION not found in the script, continue?" (not the exact message).
Already ask for the refund.. but it cost me something like 150 U$S... also, i don't have the original box ... so it's going to be really difficult to return the product. I'm sure it's a software problem..
Thanks again for your help!!!
fcostazini said:
Already done that.... 5 times (5 different firmware). Still the same.. but with android 6.0.1.
I found 1 more thing that may be a clue: When you hard reset the phone or install a new firmware (same thing..i know) when the system show the welcome Sony's screen and the settings wizard, there is a small toast message that shows "Flash restore service starting: please wait for the Power off button" (not the exact message). After several times a black screen with a Power Off button appears and you can't do anything until you press it. After that the phone restart and it's normal again.
When flashing with the flash tool in the MA TA section you can see AUTO_BOOT and OSV-RESTRICTION. When you try to flash any rom, a warning message appears: "AUTO_BOOT and OSV-RESTRICTION not found in the script, continue?" (not the exact message).
Already ask for the refund.. but it cost me something like 150 U$S... also, i don't have the original box ... so it's going to be really difficult to return the product. I'm sure it's a software problem..
Thanks again for your help!!!
Click to expand...
Click to collapse
Okay good luck. Seems a bit messed up to me :/
Those ta sections are ignored when flashing, you do not need them.
Another solution:
Flash a 575 firmware and root your phone. Then try one of the available custom roms. There also is a solution to enable missing bands, but this is a little bit more difficult.
Sent from my D6603 using XDA-Developers mobile app
punkt said:
Those ta sections are ignored when flashing, you do not need them.
Another solution:
Flash a 575 firmware and root your phone. Then try one of the available custom roms. There also is a solution to enable missing bands, but this is a little bit more difficult.
Sent from my D6603 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks i'll give it a try. Although i tried to root it with no luck.
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.