Edited in 2022 to make it look a bit better!
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it OR YOU CAN LEAVE Privo data and factory app, you have a backup anyways. *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma. You may try to skip this step. There have been comments saying that this guide also works without this step.
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while for the signal to appear. If your signal is returned then go to phone app and dial *#06# and look or the IMEI matches the IMEI of the box of your phone (make sure you have the original box if you don't have this then open the back of your phone (if you can), there is a sticker label with your s/n and IMEI. If you cannot open the back of your phone, then you will have to trust that the IMEI is right. If everything is functional then you're done with this guide. The next steps are more ''checking'' if everything is alright.
Step 7) If your s/n is ok skip to step 8 if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and IMEI and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Congratulations on getting past step 8. I hope this guide has helped you and that it worked for you. If not then I'm sorry for not being able to assist you. This guide is just me sharing what I did to solve this issue. Good luck on solving your problem if this guide did not work.
If the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) When you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version. You can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) If it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) If you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy flashing and please confirm in the comments below if it worked for your device or not
Guys please comment or it works on your device or not!
It works for me. But I have to manually change CSC on my phone after original rom flash to fix Network. TGP rom have that option.
I followed your guide and my model name changed from G930F to G930FD and my IMEI is just bunch of zeroes wtv
SOLVED AT LAST - MISSING IMEI and EFS DAMAGED SOLUTION
Hi Guys,
First off, please take GOOD note - I am NOT a techy, just an old boring flashaholic who works in an office and likes pyjamas more than partying. This is my account of me fecking up my phone and finally reaching a solution after three days and most of two nights to a missing IMEI, messed up EFS and non-working phone - hoping that it might help anyone as desperate as I was. You do what you do with your phone and that's your business and I'm not responsible if you mess it up, but my hope is that you have have a brain (that's all I have) and you get some helpful piece of info here as I did from a whole ton of posts I read that finally led me to this.
Next - I am not sure what landed me in this mess. I've seen Superman Rom mentioned a couple of times..I didn't use that but I did use Batman Rom which is by the same Dev. It was great to use, too, so I'm not faulting the Dev by any means. What did happen, though, is that when I flashed other ROMS, maybe 3 or 4 of them following, the Batman splash screen was always there before the new ROM's boot sequence, so there were clearly some residual things of it in there ...so perhaps the same coding is in there and could have had something to do with it, I don't know. The breaking point came when I flashed Sac23 Rom hoping to get Pie on my phone. It was cool but I decided to revert to Resurrection Remix - always my favourite overall - and all of a sudden I get errors.
What should have been a routine "Restore" of my backed up RR ROM via TWRP gave "Error mounting EFS". Reboot, wipe, retry. No joy, same again. A couple of tries to restore the EFS from the backup in TWRP didn't work either.
Next go to is flash "original firmware" (more on this wording later). I had that on my PC (not a phone backup, just the firmware so it's clean copy with no data).
Get Odin out, download mode, correct files in correct boxes, all that standard stuff you can find guides on most places - no joy.
Error showing was "Fail at pm.bin" or something like that. Install aborted.
Try again. This time "Fail at cm.bin" Install aborted. Reboot from recovery also fails. Oh sh1t.
Several more attempts made. I have five different Odin vers. I have seven different firmware vers. I have two USB ports and about 8 Samsung cables. Not a single combination I tried worked.
The XDA heroes will know what to do, I thought. I read and read. And read. And CubZ (who is a hero even if he IS from Lancashire ), says MAKE SURE YOUR PHONE IS RUNNING ORIGINAL SOFTWARE. Well...I kinda did that mostly already...but maybe I need to go RIGHT back to the rubbishy 6.0.1 version that came actually ON my phone when I got it....almost 2 years ago? Who remembers that stuff?? I'm about 18 ROMS down the line now. I was desperate. I'm telling you...I even got out my bank statements to trace when my first payment to my current provider was...I read about firmware numbers and country codes, and I chose one from Sammobile with a build date, country code, unbranded code (which my phone always was) and correct phone model (of course!) as I needed. And it WAS .."the ORIGINAL" firmware.
This time I swear Odin failed me a second BEFORE I pressed the start button! No joy.
Have a flask of coffee and a few valium sandwiches and off I go back to XDA again. I read a loooong series of "Missing IMEI" stuff and there's CubZ again with an IMEI/EFS fix guide guide...brilliant! And it WAS brilliant, and clearly he helped tons of people (kudos, man). But I had messed up MY phone in the time-honoured "right royal" way - worse than his guide could help me. My IMEI was Unknown, my EFS was empty, My SIM wasn't being recognised, no network info or signal...nothing. But genius that he is, he CubZ DID post a Combination file that gave me a base to keep trying on when firmware after firmware had failed almost immediately with errors either of pm.bin/abort or cm.bin/abort.
I almost wore the print out on CubZ guide, I read it so much and tried so many times. Then...I see people saying things about U1, U2 and U3 firmwares. Turns out you shouldn't mix the two. I got that snippet from CubZ too. More research and the little coffee-fuelled connections in my brain are like.....ok....
My ORIGINAL firmware has in its name "U1" and there are similar ones with "U2". Might that be it? My phone has been screaming "DEVICE 2 FIRMWARE 1" (or something like that) at every aborted 'original firmware' installation via Odin and download mode that I've tried, including the EXACT firmware that was on my phone the day it was unwrapped and I danced happily round the room with it.
So if DEVICE 2....FIRMWARE should be 2 maybe? Back to Sammobile. There are firmwares with the same model number, country code, branding info as mine..but with a "U2" where mine said "U1". But...they were Oreo and Nougat where mine was "originally" Marshmallow.
It's now day three in the Big Mother House. My valium and coffee and running out and my communication with the outside world has ceased. I've had about five hours sleep, my food is running low and I cannot call for takeaway cos I ficked my phone up good and proper. I even....get this....start looking up PAID services to fix this. I KNOW, right!!??
I pick up a Nougat firmware from Sammobile...careful to match model, country, branding AND U2 - wondering if I can match it up with CubZ's Combi file as a base to appease Odin......and then maybe revert to my 'original' stock from that to start another attempt at the IMEI/EFS thing.
It loaded. Odin was pleased with my sacrifice. And lo and behold, it had restored the whole lot WITHOUT me having to go any further with stock ROM reversions. It frickin' worked. I got my signal back. My SIM card was detected. My phone number was showing. My IMEI was showing. My E-Frickin-S was mended. I feel like Judd Nelson at the end of Breakfast Club.
So here's the semantic bit that I hadn't known and that is unclear in many many posts. My phone is now working 100% on stock firmware....but is is NOT REALLY the ORIGINAL software - it's the MODEL......COUNTRY......BRANDING.....LANGUAGE - specific firmware but it is Nougat where my original was Marshmallow, and it is a U2 firmware where my original FW was U1. THAT was the killer difference, it seems. Thanks to all of you who posted anything - many many of you - who helped me get this. It's a compatibility issue detail I've never seen or had issues with before.
I now have G930FXXS2DRDI_G930FXEU2DRB5_XEU
Where G930F is the model number, XEU is the country code for UK and Ireland (even though UK is a nation and not a country - just sayin' ) and the U2 sits there hiding in the middle of the second section of the name.
Which gives unzipped files as follows: NOTE - THESE ARE NOT LINKS.
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar.md5
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar.md5
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar.md5
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
It's Nougat, but that's okay for now; I got my IMEI, EFS, SIM, BIN, probably ENT, RAC, SUV and BMX too, everything
And now, with my working phone, I am gonna phone the local Chinese Takeaway for food, answer all my emails that popped and binged and tinkled at me when it became resurrected, and leave CubZ with huge thanks and all of you guys with the hope that this helps somebody out there.
And maybe look at backing this sucker up and reverting to my Oreo RR ROM I love so much..... I HATE Touchwiz!!!!
Good luck!
:good::good::good:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
shabbir143 said:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
Click to expand...
Click to collapse
You deleted all files and folders from EFS Mounted partition? how is it possible working?
You are awesome man!
I just deleted the files in EFS, restarted without installing custom rom and my IMEI was fixed.
I'm definitely donating. How to donate to you?
Thanks for your great work!
cisekpro23 said:
You deleted all files and folders from EFS Mounted partition? how is it possible working?
Click to expand...
Click to collapse
I think samsung phones are capable of regnerating their efs. But its not working for me on samsung galaxy s6. Guess I am screwed.
Hey everyone, I'm sorry for not responding to anyone in this thread. I've been inactive for a long time. I want to thank everyone for trusting the guide and I hope it has worked for you if you tried following the steps. If you have any questions feel free to ask me.
Also I have edited my guide to improve the reading experience because I see my English was absolutely horrible at the time when I wrote the guide.
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
vigilante said:
Edited in 2022 to make it look a bit better!
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it, you have a backup anyway *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while if your signal is returned then go to dialer and dial *#06# and look or the imei matches the imei of the box (make sure you have the origional box if you dont have this then open the back of your phone, there is a sticker label with your s/n and imei if imei is not good then skip to step 9
Step 7) now if your s/n is ok skip to step... if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and imei and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Step 9) now for if the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) when you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version you can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) if it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please donate and like this thread if you found this helpful, I have experienced this problem my self and it costed me €60! I said NO its too expansive so then I found this solution and now I am sharing it to the world, I could have let this guide cost €61 but my guides and solutions are free a support would be great for finding this out
Happy flashing and please confirm in the comments below if it worked for your device or not
Click to expand...
Click to collapse
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
bamcarpio123 said:
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
Click to expand...
Click to collapse
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Click to expand...
Click to collapse
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
vigilante said:
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
Click to expand...
Click to collapse
I'm sorry for being so stupid because I continued without performing a backup in TWRP, I forgot to back up the EFS, and when I panicked because I was already screwed up, I deleted the efs folder—which is incorrect. I deleted the efs partition before I saw this thread. And now it always says, "failed to mount /efs (invalid argument)" and I've done everything, and it seems like everything is done, I have no idea what to do. I haven't slept for four days and there is still no hope. but my phone is still okay with the stock firmware, but it always restarts. I did almost everything but still nothing
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
If I lose my IMEI, it won't matter. But the thing is my phone is always restarting every minute.
(can someone know how to disable auto-reboot so i can still use my phone even the EFS is damaged?)
ALSO THANKYOU FOR YOUR REPLY! I APPRECIATE IT!
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER? HMM. BUT I WON'T GIVE UP
bamcarpio123 said:
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
Click to expand...
Click to collapse
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER?
Click to expand...
Click to collapse
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
.
.
vigilante said:
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
Click to expand...
Click to collapse
My phone is Samsung Galaxy J8. Before i start to flash custom rom, I took a snapshot of the device's hardware information and discovered that the csc is really XTC. I have completed all the necessary steps. I did everything right, but nothing actually changed. I'm so exhausted that I might just give up. I appreciate your assistance.
If I can't retrieve the imei, it's fine, but unfortunately my phone is always restarting
EDIT: MY PHONE IS NOW FIXED. THE SIMS ARE NOW WORKING, THE SIGNAL IS BACK AND I FEEL SO HAPPY. HOW DO I FIX? WELL I USED THIS METHOD, I DELETE ALL THE FILES FROM EFS FOLDER (NOT THE PARTITION JUST THE FILE INSIDE OF IT) THEN I FLASH THE LATEST STOCK ROM WHICH IS ANDROID 10 BUT THE CSC FILE IS FROM ANDROID 9 AND AFTER THAT I USED TFT SAMSUNG MODULE WHICH IS VERY HELPFUL AND LEGIT TOOL AND ITS 100% FREE!. THEN I FIX THE IMEI AND BASEBAND USING THAT TOOL AND YES THAT SOFTWARE IS A BEAST. AND NOW ITS WORKING PROPERLY. IT TOOK ME 2 WEEKS TO SOLVE THE PROBLEM BUT IN REALITY ITS VERY SIMPLE HAHAHA! IT SAVES ME FROM SPENDING MONEY JUST TO SAVE MY PHONE BUT I DO NOT KNOW THAT I AM THE ONE WHO WILL FIX MY PHONE HAHA HOW COOL IS THAT. JUST DON'T GIVE UP NO MATTER WHAT HAPPENS!
#FVCKTHATZ3XBOX
THANKS TO THIS METHOD AND TO SIR VIGILANTE.
EVERYTHING IS POSSIBLE JUST DONT GIVE UP EVEN YOU'RE TIRED.
Related
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414
I don't know...but I'll try to find
Thanks!
I tried the firmware of galaxy 3, but didn't work
I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support
Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?
Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....
@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).
arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*
@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.
@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!
News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry
Hi guys
recently bought a s6 from ebay which was frozen on S6 logo. Basically managed to clear cache and factory reset from recovery but that didn't work, anyway I DL the O2 firmware and odin and put it into download mode I get a fail on odin when trying to install the rom
The phone has knox 1 and also has red writing SW Rev. Check Fail. Device: 3 Binary: 1.
I'm unsure what to do and if theres any chance for me to recover.
Many thanks
Mav
it failed because you flashed an incompatible Firmware.
where did it stopped flashing in odin? In sboot.bin?
If thats the case, you need to download proper firmware/country for your device.
Let me know what country is ur fone made of.
Hi thanks for your reply.
I managed to get it working by installing root and unikernel, it boots into O2 the firmwarw is 5.1.1
Only problem now is imei is 3500000000006
And it wont make calls dont know if imei is corrupt ir they sold me a stolen or lost phone?
I may install tw recovery and custom rom and see if that works.
Any suggestions?
Hi
Ive managed to sort out and get it to work infact typing on it now. Its currently rooted custom rom and twrp. I e managed also to restore original imei number so overall im quite pleased with myslef lol.
Anyway one last problem i have is ive tried all sims but none work i know ita picking up signal as the bar shows top right. Also chexk my settings.
Ive tried automatically and manually going to register networks but it says unable to connect try again later. I know uts not my area as my wifes s6 works perfectly. Sim also def works. The phone also picks up when a new sim has been inserted so i dont think its sim slot.
Any ideas guys
OK new update if anyone can help I'd really appreciate.
Installed new vador rom Imei reverted back and serial number is all zeros
Is this something to do with baseband if so how can I fix read somewhere about ariza patch but that was s3 4 etc.
Thanks
Mav
1. Your EFS is corrupted. The IMEI you see is a generic one, phone will be useless for network provider only wifi will work.
2. The one thing that caused this is by flashing an old bootloader to your phone. Thats why youve encountered Check Fail error on Download mode.
Happened to me also but got it fixed in the end.
OK thanks for the info how do I fix? I do have my wife's s6 but that's not rooted and don't want to root can I restore the efs
Many thanks
Mav
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
maverick7777 said:
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
Click to expand...
Click to collapse
I think I know one thread that has a firmware downloader with ultra fast download speed you may try searching it.
I dont know if it will help, but you may be able to successfully flash the firmware but many of those who have problems were unable to boot the phone due to corrupted efs data.
Here's my way of fixing it (if you still have intact efs). http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
But if its already wiped, there's no way you can retrieve it unless bringing it to samsung or any repair shop.
Anyways, mine was fixed (IMEI) using Octopus box repair tool. Since I cant do anything to recover my generic imei.
batuzai04123 said:
I think I know one thread that has a firmware downloader with ultra fast download speed you may try searching it.
I dont know if it will help, but you may be able to successfully flash the firmware but many of those who have problems were unable to boot the phone due to corrupted efs data.
Here's my way of fixing it (if you still have intact efs). http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
But if its already wiped, there's no way you can retrieve it unless bringing it to samsung or any repair shop.
Anyways, mine was fixed (IMEI) using Octopus box repair tool. Since I cant do anything to recover my generic imei.
Click to expand...
Click to collapse
Thanks silly question but how do I know if my efs is ok or corrupted?
at the moment the phone works perfect it is rooted, twrp recovery and vador rom but it just wont connect to networks. I know its not stolen or lost.
maverick7777 said:
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
Click to expand...
Click to collapse
As far as i know if your EFS partition is corrupt and you do not have a back up of the EFS partition to restore which you probably dont as you bought this as broken then sim capability is dead, im not sure of any other way to fix this unless you have the intact efs partition
Hi
How can I tell if the efs is corrupt it shows a baseband it now shows the correct ime I
It just won't connect to network it says try again.
I can post a screen print of efs folder on es Explorer if anyone knows what it should look like
Here are screen prints but I think I'm speaking to myself lol
Hi there i spent months on fixing issues like this (i now have a tool that takes care of all this) , best thing you can do is flash to a rom where the original imei came back do a backup of the efs, flash to a orginal rom ( latest rom) make sure its the right one for your device, connect to kies, install the rom again root and restore the efs failing that the imei is blocked use checkmend.com the uk version if your from the uk, message me if you need help
maverick7777 said:
Thanks silly question but how do I know if my efs is ok or corrupted?
at the moment the phone works perfect it is rooted, twrp recovery and vador rom but it just wont connect to networks. I know its not stolen or lost.
Click to expand...
Click to collapse
Your rom, recovery and kernel doesnt have to do with corrupted efs.
Only way is to bring it to repair service using box tools to re enter/validate your imei so that you can connect to your network provider. There is no other way around other than retrieving your efs and installing it or thru repair service.
You may now relax yourself at finding ways to connect, I assure it wont help trying to flash and flash and flash stuff to your phone.
---------- Post added at 08:46 AM ---------- Previous post was at 08:37 AM ----------
Uhm can you send sms or make calls? It seems you have a valid Imei
Ok ive tried all stock roms including o2 and a uk btu one but no luck they all do the same thing get frozen on Samsung logo then I flash unikernel and it boots.
When checking my efs folder I can see no modem file I'm now wondering could that be the fault? so I downloaded modem and BL for 5.02 and 5.11 both will not flash via odin I get a fail message and on device check fail device: 3 binary: 1 messgage in red?????.
So I'm a little lost, I was wondering if I managed to root my wifes s6 which is virtually new could I back up her efs folder then copy it into mine and just amend the imei to my original would that work? also is there a way of rooting my wifes phone without triggering knox?
Any other suggestions guys I really don't know what bootloader was on it to start with or rom is there any way for me to find this out?, also another weird thing when the o2 uk roms install they install german apps?
Thanks guys
Ive repaired EFS Partitions with scripts downloaded from links at xda.
For example i trashed my EFS partition on my note 3 so it caused hard reboots after android booted up and it couldnt be fixed with anything else than the EFS partition repair scripts.
Edit: friend repaired his Note 4 also.
Thanks but where can I find these scripts as I've looked everywhere and if I did find how do I go about doing it. At the moment when I try to flash modem and bootloader it fails.
EFS brick
maverick7777 said:
Thanks but where can I find these scripts as I've looked everywhere and if I did find how do I go about doing it. At the moment when I try to flash modem and bootloader it fails.
Click to expand...
Click to collapse
hi my friend,
i have exactly the same issue as u, i'm really hopeless, did you get any solution so far??????????????????????????
i hate being using my s6 as an ipad mini, holding two phones in my pockets
ketman5001 said:
hi my friend,
i have exactly the same issue as u, i'm really hopeless, did you get any solution so far??????????????????????????
i hate being using my s6 as an ipad mini, holding two phones in my pockets
Click to expand...
Click to collapse
Same with me also need help
I tried to root my SM-G930F with current firmware G930FXXU1DQB3_G930FDBT1DQA8_DBT with this CF Autoroot file: https://download.chainfire.eu/929/CF-Root/CF-Auto-Root/CF-Auto-Root-herolte-heroltexx-smg930f.zip The latest one is based on NRD90M.G930FXXU1DQD7 and I am not sure if this is a problem.
During flashing the phone rebooted once showing "Kernel is not seandroid enforcing", then after some seconds another reboot. I waited nearly one hour with the phone beeing stuck in the samsung logo. When I shutdown and boot up the same happens. When in Recovery mode it shows first some failed "update" but I can get in the menu, download mode also working.
Now I am pretty lost about what I can do next. Of course my data is prio1 so I was searching for a way how to recover the phone and keep my data. Prio 2 is I still want root.
I have searched the whole day and I found the following options:
1. Flashing the whole Stock Rom: As I have read this should fix the bootloop problem, but since it's a 5-part ROM it will most likely also wipe my data - I really absolutely want to avoid this if possible!
I also read in some cases you don't have to check "Re-partition" if you don't use another CSC (this would be the case). So I was wondering if I could flash stock without re-partition and erasing user data.
2. Flashing only boot.img and/or recovery.img: Chainfire writes "If it still doesn't do anything after 5 minutes, something has gone wrong, and you should probably reflash your stock boot.img and recovery.img." Funnily he doesn't provide any guide -.- I don't know if this is trivial (I have only some basic knowledge on the whole Android flashing) but I was searching like crazy for any tutorial how to do this. My idea was that in this way only the recovery and boot are restored and user data is untouched- correct? So the only guides I found going in this direction are those mentioned here: https://forum.xda-developers.com/showpost.php?p=67648452&postcount=2
Now as these are rather old I am even not sure if they still count for Android 7.0 as I don't want make even more damage. Therefore my question - is this a possibility to convert the IMG to TAR and flash them ? Are both needed or just one, is the order important etc.. ? Maybe someone has a more specific guide.
3. Flashing TRWP: I have not read much about this yet because I wanted to stick to the simple Autoroot method and also don't make things more complicated. But I was wondering if in this way the bootloop could also be fixed and my original goal of rooting also could be achieved?
4. Trying CF Autoroot with earlier version: I searched for any archive of the CF Autoroot images. Maybe I could get the phone back to work with an image based on my version. Problem is it seems Chainfire does not keep the older versions and I didn't find any in other places. Anyone got such version for the DQB3? It would be worth an easy try..
5..... any other possiblity ?
General question for the future: Does anyone know why the rooting went wrong? What was my mistake? I striclty followed the guide, have activated OEM and USB Debugging, started Odin as Admin etc. Is it a version mismatch issue ?
I am really thankful for any advise! In the past I flashed my SGS2 and SGS5 and never had any issues as I always followed the guides and was very careful. Can't understand why there is no warning for this particular case ..
Michael
Flash stock again using ODIN (do not change any settings) and use HOME_CSC instead of CSC and you will not lose any data
HOME_CSC = No Wipe
CSC = Wipe
Then follow the TWRP / SuperSU thread to get root
I flashed as you proposed and the phone is back to normal without any data lost
Thank You so much *detection*, You saved me a lot of trouble!
For anyone else having the same problem I used this guide (it's for the S7 edge but process is the same).
I will report back if I managed to root with TWRP and how to do it.
BR
Michael
:good:
I've got the same problem (stuck at logo after Auto-root). Do you know any working solution to root S7 Edge without loosing the data?
wojtas44 said:
I've got the same problem (stuck at logo after Auto-root). Do you know any working solution to root S7 Edge without loosing the date?
Click to expand...
Click to collapse
Ask in the Edge forums
https://forum.xda-developers.com/s7-edge
Hi guys,
Not started a thread on XDA for years but I really am stumped.
I have claimed my girlfriends s6 (SM-G920F) after she upgraded and intended to root it and maybe try a few Oreo ROMs etc. After investigation I saw that (I think this is right) I don't need to OEM unlock this version of the device and rooting via Odin is the best way to do it. BTW if I do need to OEM unlock then that might be the solution to my issue, so if some one could clarify that'd be great.
So a week ago I downloaded Odin and also my old favourite CF-AutoRoot after putting in the device details. The package was generated, I unzipped and put it in a folder in my desktop
After putting the device in download mode I run Odin as administrator and plug it in. The device is recognised and I get the blue box to show this.
I then click the AP box and select the image file and click start, everything runs as expected to this point and I get PASS displayed in the info bar. On the phone the progress bar looks like it has not completed and I can see a small portion still to run. On the first try I left phone like this waiting for it reboot for over an hour. I was expecting 5he device to reboot and get the android with the red exclamation point. At this point I restarted manually and saw during the boot process an error message saying Recovery not SE Enforcing in red.
I have read a few posts saying this can be caused by the wrong image being used, so I downloaded the Auto root package again and made sure that it was all correct, but the same thing occurred.
I have been looking and reading for the last week to find a solution, but I'm still in the same position. Can anyone help or point me in the right direction?
If you need any more info let me know.
Thanks in advance
Jon
im in exacltly the same boat pal. was running nanorom on my rooted s6, but had no vr capability and just got some galaxy gear goggles. tried to reflash arter97 kernal and lost my whole setup. ive been in and out of hard brick for last 24hrs and am back now to where you are, i can access download and recoveries via three button combo, but any packages i flash with odin just fail out right.
ive been here before though and usually get out once i find the right stock rom and csc's for my version. iof i find anything ill come back and share it with you pal.
Cheers mate, it's really frustrating. I'll keep looking too and post back if I have any success.
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
copernicus666 said:
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
Click to expand...
Click to collapse
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
what a f**k about!!!!
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
shiko2007 said:
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
Click to expand...
Click to collapse
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
copernicus666 said:
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
Click to expand...
Click to collapse
if your not root yet just download latest your carrier/country firmware
from sammobile
and flash it by odin
but you are probably trip knox so you must root
so the steps you should do :
1-download your carrier/country firmware from sammobile
2-flash it by odin
3-flash cf-auto root to pass bootloop
or
download twrp recovery of g920f and flash it by odin to replace stock recovery then after flash it ,wipe delvik cash then flash su binary
DagsyMc said:
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
Click to expand...
Click to collapse
Legendary post! Cheers mate you just made my morning. I knew the XDA guys would pull through.
I'm on my way to work, but I'll give it a crack later.
Cheers bud - Kudos
I've looked through the forums to identify a similar problem to mine in hopes I can resolve this issue but I've not found one. So here's my problem.
I have a UK Galaxy S7 running on the 6.0 firmware that came with the phone when it first released (Yes I know it's very old and should have updated along the way but I had plans to root and install customs at some point which obviously didn't happen). The phone is unrooted and the stock rom is the XEU version with Multi-CSC (according to recovery)
The phone was running fine until a few days ago when all of a sudden it shut off and wouldn't power on via the power button. So I pressed and held Home + Volume Down + Power. The green screen appeared and selected Volume Down to restart the device (as you do in odd situations like this).
PHONE IS NOW STUCK IN BOOTLOOP!!!
I have tried various means (not including flashing) to get the phone to boot to the home screen with no success. I have not performed a factory reset from recovery because I have various data, including pictures, music and other software on the internal storage which I wish to keep and not lose. The phone is still under warranty so I can take it to a Samsung repair outlet to get them to fix it for me but due to data privacy or whatever, they have to format it clean to then install the most recent firmware.
I've been scouring the forums for help on flashing OTA updates which retain data on phone whilst possibly allowing my phone to boot into the home screen so I can access my data. Is such a thing possible?
Any help would be greatly appreciated.
You can flash the latest firmware without losing data (as long as the hardware is not faulty) by downloading it from either sammobile, updato.com or using the samfirm tool here on XDA (Fastest option)
Then extract the firmware and add all 4 parts to ODIN 3.12.7 (Do not use ODIN 3.13.1 unless you want to flash BTU Oreo 8.0)
AP << (Takes quite a long time to add, be patient as ODIN will look frozen)
BL
CP
HOME_CSC
If you use CSC instead of HOME_CSC it will wipe the device after the flash, HOME_CSC will not wipe it
Put the phone into download mode (Home & Power & Volume Down)
Connect to PC USB and hit start on ODIN
Wait for the flash to complete (It can take quite a while) and the phone should hopefully boot back into Android
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Cassie` said:
Thank you for the quick response.
It's imperative I get this right and ensure I've understood your reply correctly.
I have downloaded the following:
SM-G930F_1_20180417125627_cz5yqc22v0_fac - from SamFirm as it was much quicker like you said.
Odin3+v3.12.7 - This particular version was quite difficult to get a hold of. Various sites redirecting me to various pages without a direct link to download but I hope that is the correct one.
The firmware zip contains the following files:
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar -------1
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar -------2
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar -------3
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar -------4
I have labelled the files 1-4 in the order of flashing/installation (I presume?)
I will also follow your instruction of flashing HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar as this will NOT wipe any existing data on the phone?
Will following the above steps act as an upgrade to the phone and not wipe apps/pictures etc in the internal storage?
Have I missed out any other steps?
Click to expand...
Click to collapse
Almost, you must flash all 4 files at the same time, load them all into ODIN before hitting start, doesn't matter which order you load them in as long as they are all loaded before flashing
And you are correct with the rest, HOME_CSC will not wipe anything, and yes it will act as an upgrade although it is a full ROM you are flashing, to you the user, it will appear exactly the same as an upgrade as long as you use HOME_CSC
No other steps needed
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Cassie` said:
I have loaded all 4 files as seen in the screenshot however, after clicking on Start, about 5 or so minutes later, it says FAIL in the first box above where it initially said RECOVERY. It's stopped and not done anything else.
I'm not sure what to do here.
I've also added a shot of the top left of odin screen
Click to expand...
Click to collapse
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
*Detection* said:
Yea it's failed, you can close ODIN and disconnect now
You can try doing it again, but that should have worked, you could try downloading the latest 6.0.1 ROM and flashing that the same way first, it looks like your bootloader is version 1 where this ROM is version 2 as shown by the S2 number in the middle of the firmware version
Click to expand...
Click to collapse
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Cassie` said:
I've gone to https://updato.com/firmware-archive-select-model?record=0DB04AD4C34211E69215FA163EE8F90B
From there I've selected the most recent 6.0.1 ROM which is dated 4th December 2016. Problem is that the download is EXTREMELY slow and I have no idea how to use SamFirm to download that particular ROM.
I guess all I can do now is play the waiting game and repeat the steps with the 6.0.1 ROM once it's downloaded.
Thank you for your responses and I will post back here once the download has finished.
Click to expand...
Click to collapse
Yea unfortunately all alternatives other than samfirm tool are slow, and samfirm only downloads the latest ROM
Judging by the bootloader version and the ROM version you have chosen, if this also fails, then I would assume a hardware failure
The only other thing I could suggest if this doesn't work, is to pick an older version of ODIN to flash the older firmware, ODIN 3.11.1 was used for MM 6.0.1 ROMs if I'm remembering correctly
https://forum.xda-developers.com/showthread.php?t=2711451
or
https://odindownloader.com/download/odin3-v3-11-1
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Cassie` said:
I've restarted the device and it said An error has occurred while updating the device software use the emergency recovery function.
I attempted to reboot the phone a couple of times to get into recovery and I was successful. I now see the the Bootloader version is now 2 as opposed to 1. After seeing this I attempted to flash version 7 as initially suggested yet it did not work.
I'm not sure how Bootloader changed from 1 to 2 and is still failing to flash in odin. I am still waiting for the 6.0.1 ROM to download, fluctuating between 16-19 hours as of writing this response. Once it's ready I'll try and load up odin 3.11.1 as a second solution and try 6.0.1, even though Bootloader says 2.
Click to expand...
Click to collapse
Your ODIN screenshot looks like it managed to flash the bootloader before it failed, so it's possible you are going to need to use a version 2 ROM from now on, I have the same phone, XEU G930F and it is running Bootloader version 2 (Running the BTU Oreo 8.0 stock ROM)
But if the 7.0 Nougat ROM failed again it's looking more like a hardware issue, seems to be failing when it should be starting to flash SYSTEM (AP)
You can try flashing the 7.0 ROM section AP on it's own with ODIN 3.12.7, see if that fails immediately, if it does that's likely where the problem lies, it's not unheard of for these S7's to fail like this out of the blue, I see it maybe a couple of times a month on XDA
Only solution is to get the mainboard replaced
But yea, give 6.0.1 a shot anyway, worth a try saying as everything else has failed up to now
(Looking for mirrors for that 6.0.1 ROM, I've got it on my main machine but it is offline right now with no graphics card so I can't access any files, stuck with a laptop, I always download and save every new firmware release for this reason)
There is Samsung SmartSwitch software for Windows for the emergency firmware recovery, but it WILL wipe your phone back to factory and delete all your data (Last resort if nothing else works, although if ODIN doesn't work, I'd say hardware failure)
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Cassie` said:
Right so I've managed to download the most up to date 6.0.1 ROM and attempted to flash it with ODIN V3.11.1 and it idles at the recovery.img part and fails like the previous efforts.
I'm not sure if attempting to get OREO running with the latest ODIN might work? If not then I may have to give up and do a factory reset through Samsung SmartSwitch.
It probably is a hardware failure as I had noticed the lightning bolt appearing when the phone is off whilst plugged in the charge, it take about a minute or so for the percentage bar to appear, usually it was about 2 seconds before this disaster occurred.
Click to expand...
Click to collapse
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
*Detection* said:
Worth a try flashing Oreo, BTU on samfirm tool will give you it for the G930F
If you're seeing problems with the charging now, you might get lucky and find the USB port is the only thing needing replacing, but if you send it off for repair it's unlikely even if that is the case that they won't just charge you for a new mainboard, you can likely get USB ports from eBay but opening the S7 isn't as straight forward as the back is glued on for IP68 water resistance and needs a heatgun to remove, not sure if anything else like the screen needs removing for USB, I've not opened mine
You've tried a new USB cable and a different PC too ?
Click to expand...
Click to collapse
The charging issue occurred immediately when the phone shut off by itself and wouldn't power on conventionally. The phone is still under warranty so if the Samsung SmartSwitch software is unable to recover the phone then I will take it to the repair center and have them fix/replace it. If it's a case of undoing the glue and whatnot then I'd rather they give me a replacement.
I did change the USB cable to a different one, and I've attempted to flash the 2 different ODINS with the 2 different ROMS on a laptop as opposed to the desktop I was using. Still fails at the recovery.img part of ODIN.
I'm going to try Samsung SmartSwitch now and see if this will give it some life. If THAT doesn't work then it's 100% hardware issue and my data was lost to begin with.
Considering both versions of ODIN didn't work with either ROM, I don't think I'll be looking for the BTU version of OREO to attempt to install with. If there's a direct download that's quick I might but I think I'll attempt to Emergency Recover through the Samsung tool.
I want to thank you plenty for your help and knowledge on this. It certainly has been helpful and given me better understanding of the problem I'm facing and potential solutions. I have a feeling that the SmartSwitch recovery won't work either and still be posting back here hahaha.
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Cassie` said:
OK I've got bigger problems on my hands now.
SmartSwitch and Kies both say "SM-G930F" does not support initializing. Please contact our service center.
I've already inputted my serial number and it gives me the same message on both programs. When I called up customer support they said my warranty is till the end of May this year.
Would the service center be able to solve this problem?
Click to expand...
Click to collapse
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
*Detection* said:
Yea I'd get it repaired under warranty asap then if it runs out soon, they will most likely replace the mainboard I'd say, which means 100% data loss as the storage is on a chip on that board, or might even send you a new S7
Really does sound like hardware failure if all of these recovery options have failed, just keep quiet about what you've done to try and fix it, just act dumb and say it won't turn on or they could claim you nulled your warranty messing with ODIN
And no probs, that's what XDA is all about Let us know how the repair goes and buy a MicroSD card to save your important files to this time so you don't lose anything if it happens again
Click to expand...
Click to collapse
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Cassie` said:
I had an SD card inside with all my pictures I took whilst in Japan (Thank GOD!). I took it out when this issue arose to avoid potential data loss there.
As far as ODIN is concerned, warranty still appears intact but yes I'll keep hush hush when I'm there. I believe they said they'd give me a refurbished S7 if they couldn't reflash it there.
Click to expand...
Click to collapse
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
*Detection* said:
Yes, ODIN will not void warranty if you only flash stock, but telling them you used ODIN might, it's not a tool meant for us, it's Samsung's internal flashing tool not meant to be leaked online, sometimes they'll use any reason to blame you and not have to pay out / replace it so yea best not say anything other than official recovery methods suggested by Samsung themselves, if anything at all, I'd just say I didn't do anything, an OTA update came through and it never rebooted or something
Good job with the pics, I don't save any media to the phone itself, I create folders on the SDCard and move it over if I can't have it save there automatically, that way wiping the phone is nothing but a pain to set back up again, nothing actually lost
Click to expand...
Click to collapse
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Cassie` said:
I'm going to give flashing one last try.
I am currently downloading Android 8.0.0 for United Kingdom (BTU, NOT XEU). I have to head to work in a few minutes. When I get back I'll attempt to flash that without BootLoader as that will change it to version 3 and you can't downgrade from that from what I've read here and there. If that fails then it's off to the repair center. If it's some sort of hardware failure then it won't flash regardless what stock rom/ODIN version I'm using.
Not sure if BTU update with home CSC will retain my data (assuming it works)
Click to expand...
Click to collapse
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
*Detection* said:
Your CSC will remain XEU as it is Multi-CSC containing BTU, and BTU contains XEU, I'm running it now with BTU firmware & XEU CSC
Bootloader for this Oreo 8.0 BTU firmware is still 2, with it being a new Android version you'll need to flash the BL too anyway
Click to expand...
Click to collapse
I've had no luck flashing it with Oreo. It's definitely going to the repair centre. Such a shame.
I'm very grateful for your time and help with this. I will report back this weekend with the results of what the repair centre will do regarding the device. Don't like to leave a thread without an end result.
Many thanks again!