Related
Hey Guys,
this morning I got offered a new OTA update for my Note 10.1.
Since I've never fiddled around with the device (no root, no custom rom and so on) this never was a big deal for me, so I just installed it as usual.
After the update my device is stuck in a bootloop.
What I tried so far:
Connecting to KIES - failed
Recovery Mode -> Cache Wipe - failed
Recovery Mode -> Factory Reset - partly failed
Recovery Mode -> Factory Reset + Cache Wipe - partly failed
What I mean by partly failed is the following:
The device boots as normal (with factory settings) but as soon as I plug it in to KIES to sync my contacts it crashes and goes to bootloop again.
Now to the weird thing:
When I'm in recovery mode I get an error which (I suppose, at least) shouldn't be there:
Apllied the CSC-code : DBT
did not match sized '/system/csc/common/system/wallpaper/lockscreen_default_wallpaper.jpg' (No data available)
This error points to the lockscreen wallpaper?! And the REAL weird thing: While in bootloop sometimes the device gets through to my wallpaper, which then is the "old" wallpaper I had BEFORE the reset. How can that wallpaper still be there after I did a factory reset? There is no SD card in my device.
Is there any way to get back to a working version? I guess it botched up the OTA-update and now has a broken firmware or something like that...
I have no experience in Android modding/flashing whatsoever, but I'm pursuing my masters degree in Information Systems right now, so I'm not a total noob for what it's worth!
P.S.: I don't care about rescuing any data, there was nothing important which is not already backup'd on the tab... I just don't want to have a 500$ paperweight laying around ^^
Thanks in advance for any help!
You can go to sammobile.com and download manually a firmware that fits your device and flash it through odin. That will wipe the tab and flash a fresh stock firmware.
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Also check this video by zedomax and learn all the steps to flash correctly.
https://www.youtube.com/watch?v=NsDOSvBdALg
Sent from my GT-N8013 using XDA Premium 4 mobile app
kalashenicof said:
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Click to expand...
Click to collapse
Thanks for the fast reply and the information.
Not sure what you need as a "version", this is all I could get before it crashes and goes back to the bootloop:
Model #:
GT-N8000 (it's the one with Wi-Fi + 3G)
Android Version:
4.1.2
Baseband Version:
N8000XXCLL1
Kernel Version:
3.0.31 - 1388206
[email protected] #1
SMP PREEMPT Wed Sep 11 13:39:10 KST 2013
Build#:
JZO54K.N8000XXCMI2
Oh, and I'm from Germany, if that information is relevant!
Thanks in advance!
Your right it's model and not version
Check this out http://www.sammobile.com/firmwares/3/?download=19291
Check if the information matches, then download and flash it via odin.
Make sure you login to samfirmware first.
Hope it helps, if you need something else just ask.
Sent from my GT-N8013 using XDA Premium 4 mobile app
Thanks man! I downloaded the firmware and flashed it according to the video.
My tab boots fine now and the error is gone aswell... It crashed one more time though, but runs stable since. I have to keep an eye on it!
Glad it works now =)
Sent from my GT-N8013 using XDA Premium 4 mobile app
Hi friends, well basically the problem is I got a friends y GT-I9500 and it bootloops over and over with any ROM other than South Africa Rom 4.2.2 and has invalid baseband. It's a cell from a friend of mine I never new which rom was installed on this phone and as soon as I got it I installed the official stock rom from my country which was KIT KAT rom 4.4.2 tried unbranded ARO version first through ODIN, everything went fine, but it got stuck on bootloop.
These were the things I tried.
- stock recovery (I9500UBUGNG1_I9500UUBGNG1_ARO) --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Installed another Stock rom KIT KAT from corresponding Carrier (I9500UBUFNC1_I9500TFGFNC1_UFN) , did :
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
Downloaded previous builds of stock rom going back to 4.2.2 , installed stock version of 4.2.2 ARO unbranded (I9500UBUBMG1_I9500TFGBMG1_UFN)
- stock recovery --> wiping factory data/reset , ---> wiped cache = Same thing bootlooping
I also tried installed some custom roms , having flashed Philz recovery and installed from there onwards, no luck as well.
So I came across some threads which said the only possible way of downgrading if I had installed 4.4.2 kit kat , was using a South African ROM 4.2.2. So I tried it and to my surprise the phone booted fine without any problems. Honestly I don't remember if I did flash it with the PIT file and re-partition. But I did work . The only problem once inside the OS itself it showed invalid baseband. I suppose this was due to the EFS partition being changed intially by KIT KAT.
So I'm hoping someone might help me out as to know what else to try, because honestly I'm out of all ideas.
Thanks !
When you went into download mode, what was the product name the phone reported?
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
mmm I have to check, what do yo uwant me to see what string? I can put it on downlaod mode again.. and get you a screenshot
Screenshot is fine as it will give me what I need to know.
Strephon Alkhalikoi said:
When you went into download mode, what was the product name the phone reported?
Click to expand...
Click to collapse
screenshot attached , please check
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Strephon Alkhalikoi said:
Thanks. I just wanted to be sure you didn't get a Frankenstein phone, as there have been a run of these phones appearing in the last few months. Resellers will take SGH-I337 phones (US AT&T Galaxy S4), slap an I9500 or I9505 IMEI on them, and proceed to add firmware for the I9500/I9505 onto them. When the purchaser gets the device and attempts to update it or customize it, they find they can't, as the AT&T S4 bootloader is locked.
Now that I've gotten the explanation out of the way, you need to do the following. 1) Install Wanam's EFS Backup tool to the S4, run it, and backup the hidden partitions on the device. 2) You're going to again install the latest ROM for your region through Odin, but this time you're also going to add an I9500 PIT file to it. The PIT file should be available for download in the S4 forums here and will tell Odin the correct partition layout of the device. Odin will then install the ROM using that partition layout. With luck, it should correct the issues you've been having.
Should you have an issue with no IMEI or no signal after flashing, flash the modem file, which should also be available on the forums, and don't use the PIT file. If that doesn't work, install EFS Backup again and restore the partitions.
Click to expand...
Click to collapse
Ok , thanks for such a complete explanation. It's always nice when someone with knowledge takes the time to go detail by detail explaining everything. This is the way things have to be done, and explained. Ok so let me get things straight
- Wanams Efs backup , I need to install within a working ROM right? It's not through Philz recovery, What should I backup with EFS backup only EFS?. Something I forgot to tell you was I did change some permissions to see if the invalid baseband got fixed, I changed some owner permissions on the EFS folder, you should know about this.
-Then you want me to install latest ROM should that be KIT KAT right?. Unbranded for my region. Yes I know about the PIT file to repartition, I've already done this and still bootlooped with all the rom variants I tried. The only possible way the phone boots and succeeds is with South African ROM 4.2.2 I've tried all previous roms even choosin the apropiate PIT and still bootlooped.
-The only thing I'm left thinking is all these bootloops have something to do with the modem file, which the South African rom 4.2.2 might have a different modem. Which modem should I install I've read the G versions onwards modified the EFS partition.
- Last, how would EFS backup fix the EFS partition if it's only backing it up, Cause i'm thinking as I've initially when I received the phone installed KIT KAT. IT changed the whole partition scheme of efs.
So now that I've gone through every point, can you clear again the steps sorry if I'm so tedious on reviewing again but I needed to clarify bit by bit.
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Strephon Alkhalikoi said:
I must have misunderstood you regarding the IMEI. If it's invalid EFS Backup won't help. Also, if you've already ran the PIT file and still get bootloops, you may have to take the device in for servicing. A service center should be able to fix this without too much trouble. Unfortunately, I can't fathom why only one ROM installs, unless the carrier locked down the device so much that upgrades are impossible.
Perhaps one of the other advanced users or developers have a clue?
Click to expand...
Click to collapse
Hey so many thanks, honestly I don't know what have been wrong with the device. I'm suspeting this has to do with the modem. Could the modem version on the South africa rom be causing the ROM to install fine. But think of this me first installing KIT KAT and have screwed up the efs and as a consequence the IMEI. My only way would be to install kit kat succesfully as the EFS might have changed. Any advices on this?
The modem isn't likely to cause a bootloop. At worst, it's likely to render the cellular and WiFi services unusable until it's flashed again. Screwing the EFS up is where I believe your problems lie. The EFS partition may well be corrupted, which could cause your bootloop. I really think the only way you'll resolve this is by having someone at Samsung take a look at it. You've repeatedly installed ROMs and have had no luck, so installing a ROM again isn't going to help you here.
I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?
Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.
Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?
I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?
BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.
When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??
BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.
I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.
Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match
Hey,
Need some help here and not sure what's gone wrong, I've managed to root and flash custom ROM's before, but for some reason, my S7 now will not let me flash the BL file when trying to restore a stock ROM.
I can flash AP, CP and CSC with no problems, but trying to flash the BL file it gets half way and then the box at the top just goes red and says FAIL!
I've tried wiping everything from TWRP, installing custom ROM's and so forth to try and then restore from - phone is UK on BT Mobile and usually I use the XEU stock rom to reset.
The problem is, I have no carrier signal or IMEI information (I've tried the SIM in a different phone and it's working fine) so I can only presume it's something to do with the BL flash?
Any help is really appreciated!
Ok, well, hours of playing I found a SM-G930F combination firmware to flash (COMBINATION_FA60_G930FXXU2ARA2_BoxWares) - this has gotten me into FACTORY BINARY and lots of factory test / setting modes - phone now has it's IMEI number back AND I was able to receive a call from my girlfriends phone...
This seems to be running on Marshmallow 6.0.1 but obviously is not usable as an OS - so I need help to uprade firmwares in the correct order as trying to flash to 7 or 8 just fails in Odin and I can't seem to install TWRP recovery either from this.
I'm on BT Mobile (I used XEU before without issue - until recently!) so presume that's still the correct version...
Thanks!
Before I say anything DO you have a backup of your EFS folder do that first
Assuming you can only flash the binary 2 combination file firmware ,Samsung has recently updated their bootloader to not allow downgrades , you can only flash Nougat firmware from this year
Hey, I actually found that from some random spanish forum late last night... so I now have the combination rom with a useless (daily) front end / homescreen running android 6.0.1 but believe the bootloader is locked (from the nice little red error messages on startup) to a more recent version.
Supposedly I should be able to flash a `current` stock firmware then... but cannot seem to flash an AP file over this Combination rom install....
I did manage to download APKInstaller and install Kingroot (TWRP flash does not work - you cannot get into recovery anymore) and some other android apps (phone / sms / messenger) so have limited functionality but better than none for now.
No backups.
Boot into download mode , flash only the Sboot ( unzip the tar and make tar with only sboot) from any recent stock rom .
in AP put TWRP , untick the auto reboot.
when it passes( unplug phone ) hold the volume done , home power button till phone reboots (screen goes off) , quickly press volume up ,home and power button , you should be in TWRP
The combination firmware do not allow recovery modifications , it will just go in bootloop
OK, I'll try that when I get home later... lets say it works, what is my course of action then?
I still think I won't be able to flash a rom from Odin just by installing TWRP, so what actions do I need to take in TWRP? complete format ?
Thanks!
In TWRP make a backup of the EFS and Baseband partitions , copy to memory card .
I learned it the hard way , I ended up buying a second S7 with broken LCD so I can use the board
No box or tool can patch the certificate once you on Nougat as of yet
then you can go back to download mode and flash the AP ,CP ,CSC and phone should boot up , Leave the BL
Managed to get into stock recovery somehow (wasn't working before) and can see options for ADB sideloading etc again so that's something I guess lol
Presumably, if I can flash the boot file then twrp, I can then install a custom rom (i originally went from 7.0 up to 8 with Pixel Experience and Lineage, before things went tits up)
I'm guessing it'll be a case of formating data / wiping cache and installing the custom rom - assuming the BL is running 7.0 - or am i going to need to try and flash everything again via Odin (unsuccessful so far and only rom that will install is Combination)? also what about the CSC file...?
The only reason I'm in this predicament is because one of the custom roms somewhere (or google) screwed my IMEI settings, but Combination has brought those back.
you should be able to install any stock firmware from March 2018 onwards without any problems
Hmm ok so the network things I'm on T-Mobile and not BT Mobile lol (presumably because of the EUR flash) not sure if this will have implications when it comes to billing etc (BT bought out EE/T-Mobile but are different businesses still).
So does anyone have a working link to the XEU firmware? XEU-G930FXXS2DRC3-20180329132652 seems to be the filename... I can only find crap sites with 4kb downloads unless you pay $10-$20 lol
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
As someone said before.. Flash TWRP using ODIN; boot to twrp and make a backup of the EFS partition ONLY. Store the backup in the SD card and then copy it to the pc/dropbox/Drive/whatever. There are no guaranties that you wont loose the IMEI again if you attempt to flash the custom rom again. Then If you want to be on a completely stock rom, reflash the rom using ODIN. If you want to backup the baseband too, do the same procedure again but select only the baseband partition (untick the others)
To download stock roms you can use either the SamFirm tool (google search it.. it is on XDA) or Updato (site). Both of them provide really fast download speeds as there are no caps, and they are free. The files are downloaded straight from Samsung servers.
Sent from my SM-G930F using Tapatalk
Dreamz2k said:
Success - in the absence of an upto date firmware from March for XEU - I found and installed the EUR one - BL everything went straight in and I've booted to setup screen now \o/
In Greek.... OK so hopefully I can just change language and wait for the XEU to surface (or is it OK to use the EUR? I have IMEI everything so looking good so far!)
I will probably flash Pixel Experience again unless someone recommends another over this?
Click to expand...
Click to collapse
i guess i have the same problem like u....cant flash anything...just the combination file like u.....i have the stockrom from march but i cant flash this!! Odin does "Set partition" an do nothing!...
what can i do?