Database Info

[Q] Wierd message after using Triangle Away 1.95

Hi
Could someone help me please?
I could not post this question in the Original Android Development forums as my post count is less than 10 hence I am asking here.
I'm an M1 User and I have 12 GB of data and I'm an IPhone 4 user hence my Sim Card is a MicroSim one and I wanted to try out the Phone Features of the Note 10.1
I had to use Triangle Away v 1.95 after one of the sim pins broke on my Note 10.1 after I took my microSim Card in its Microsim Adapter out from the Tablet.
I used it and it cleared the root flashed firmware times download to zero and official firmware said Samsung Official Firmware.
I only used the HighonAndroid Odin hack and the Clockworkmod Recovery to root my phone and backed up after I did that.
I did not flash a full custom firmware.
However it said that the device was modified under the in Tablet Settings even after after i removed SuperSU.
When it downloading mode it said System Status : Official.
I did not get my set from either Starhub/M1 or Singtel which are the three official Telcom companies in my country.
So I download the firmware files from Sam Mobile for my non telco set from here.
sammobile.com/firmware/?page=3&model=GT-N8000&pcode=XSP&os=1&type=3#firmware
After flashing the System Status in Downloading Mode said Custom and the in Tablet Settings Status said Device Modified.
I'm not sure if Triangle Away worked for me or not.
Did it work?
I could not follow the same instructions for Triangle Away as the Samsung Galaxy S3 or any other phone because the battery for the Note 10.1 is built in.
On a side note : I managed to send the tablet in for repair within warranty also as Sim Card Pins being broken by MicroSIMs in MicroSIM Adapters seem to be covered under warranty here.

While I can't answer your question I can tell you Q&A is the right section.

http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/
TA worked, but Samsung has additional checks now.
The key is that some things (such as flash counter) were persistent after a return-to-stock. The extra system checks will go away if the device is returned to stock. TA resets the persistent stuff.

Er I don't understand. I was on stock except I flashed HighonAndroid clockworkmod recovery. After I flashed back to StockRecovery then flash back the XSP stock firmware it still said System Status custom in the settings app. So how do I clear that?

leonaheidern said:
Er I don't understand. I was on stock except I flashed HighonAndroid clockworkmod recovery. After I flashed back to StockRecovery then flash back the XSP stock firmware it still said System Status custom in the settings app. So how do I clear that?
Click to expand...
Click to collapse
I think there's a specific order in which you need to clear stuff... Might want to do some searching in the I9300 forums, that's the first device to have this new system check stuff.

From what I read in some thread, u must flash back to stock recovery. Then u can flash ur stock Rom again.
Sent from N8000, from the corner of this rounded earth.

antique_sonic said:
From what I read in some thread, u must flash back to stock recovery. Then u can flash ur stock Rom again.
Sent from N8000, from the corner of this rounded earth.
Click to expand...
Click to collapse
Oh well guess I'll have to wait till I get the set back from the service centre to see if it's been re-flashed to stock firmware with the device status in Settings said as Official.
Basically 16gb is too little and the move to external sd card option is not avaliable unlike S3 and S2.
I had a 32gb Samsung Class10 card from Qoo10.com.sg and since its bigger I thought it would be better to move apps for reading manga like Mango to the SD card instead cause the download is kinda big like 2-3gb worth of manga and pictures.

Other threads say, that after flashing the stock firmware, the device requires a complete wipe from stock recovery. Then also the "modified" setting in is gone.

GTI9500 bootlooping any ROM other than South Africa 4.2.2 , invalid baseband

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.

Restart loop

Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?

Well not having the phone in front of me, I don't really quite understand the issue myself - however, I would suggest using RSD Lite and one of the FXZ files to flash everything (including recovery) back to stock.
If you still have issues, there is a bigger problem (likely hardware failure).

Hello
sorry if my explanation was not clear.
I added a photo which shows the two steps in the operation of my phone.
Step 1: Start the phone .
Step 2 : boot ROM CM12
The Step 2 lasts 23 seconds then return to Step 1 and Step 2 and Step 1, Step 2 infinitely .
I hope this is understandable .
I read on the forum that used some RSD Lite but as I had not used for the ROM installation, I did not understand why use .
I'm a new user, i can't post picture, I send link by PM, thanks.

I thought my last post made it clear what purpose RSD Lite and the FXZ files are - they restore the phone to stock completely - ROM, recovery, everything will be reset to when it was stock from the factory (granted it may be a newer image than what shipped on the phone, but you get the point).
Again, as I stated previously, if you still have issues after flashing everything stock your issue is likely not software, but hardware.

I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.

Nicolas.636 said:
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Click to expand...
Click to collapse
The hardware issue is likely not related to the SIM modification. As to what exactly has failed, I'm not sure... perhaps the NAND or something else memory related.

Aouch aouch...
Thank you for your help.
I think it remains for me to search for a motherboard for photon Q.
Long life in the forum!

Use "borrowed" TWRP recovery image.
Nicolas.636 said:
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Click to expand...
Click to collapse
I had a similar incident a few days ago. I have a hard time stopping myself from pushing the limits. Usually I stop when it's broken. I tried RSD Lite, SDB sideload/ flash, zip install from recovery, fastboot(mine's dead), all with no luck.
Any how, If you have CWM, temporarily change to TWRP. If you already have TWRP it's easier.
XDA has a TWRP recovery image in the forum. Put that in your sdcard (I had to paste it from my computer because my xt897 was soft bricked). Flash from TWRP.
Worked fom me. got my phone back after 1 week of flashing everything and then some.
Good luck.
http://forum.xda-developers.com/showthread.php?t=2295643
http://forum.xda-developers.com/showthread.php?t=2295643&page=2

Hello
thank you for this new information.
I tried it and it worked with the ROM [PQ_ICS-Stock] but only with that one!
I tried the ROM [PQ_JB-421] , several Cyanogen ROM but still the same looping boot problem.
I tried several version of TRWP without success .
I do not understand why my Photon Q only works with this ROM [PQ_ICS-Stock] .
Is still a motherboard problem ?

Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?

Nicolas.636 said:
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Click to expand...
Click to collapse
If you can't RSD Lite, something is up. Either you are not doing the process correctly, or there is something wrong with the device (still).
Perhaps you were always on ICS and never made the official jump to JB? You say you can RSD Lite to an ICS version, just not a JB version? So 4.0.x works but 4.1.x does not?
Again I'm talking stock. If stock doesn't work, I wouldn't even attempt CM. Start with the basics, then work your way towards the aftermarket.

I agree that if the stock rom does not work after the installation with RSD Lite is that it remains something (software) .
The first motherboard I used 12.1 CM for several months it is that the phone supports android 5.1
I agree that it must abort running a stock ROM before flashing a ROM CM. But the ICS ROM STOCK works!
It is possible that I did not do the process correctly .
What surprises me is that the second board had the same problem with the ROM SPRINT !
I will do other tests.

Nicolas.636 said:
What surprises me is that the second board had the same problem with the ROM SPRINT !
Click to expand...
Click to collapse
This is the part that makes me think you are perhaps missing some step in the process somewhere.
Can you RSD Lite to ICS? Not flash it with TWRP. If that is successful, try to RSD Lite to the latest JB again.

I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.

Nicolas.636 said:
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Click to expand...
Click to collapse
Bad ESN shouldn't prevent booting... it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...

arrrghhh said:
it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
Click to expand...
Click to collapse
yes
I used RSD Lite 6.1.6 for flashing the ROM [ 2014-03-09 - TSv2 ] but the process has blocked after the flash.
Here is what I did :
1- run RSD Lite
2- Start the phone in FASTBOOT mode.
3- usb phone connection to PC
4- opening of the ROM [ 2014-03-09 - TSv2 ] and "uncompress and start flashing"
5- flash goes well
6- the phone reboots => Logo M red => telephone reboot => Logo M red => again ....
7- RSD Lite waits for the restart ... [ it waits again, LOL ]
8- I turned off the phone and I unplugged.
9- I turned on the phone who start properly, I arrived at the language selection screen .
The ROM is an android version 4.0.4 , I think you know this ROM .
Why the process with RSD Lite has blocked the phone to reboot ?
That's what I did wrong in the process?

I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.

Nicolas.636 said:
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Click to expand...
Click to collapse
Without having the device in my hands, it's hard to say for sure. The only difference I can see you are doing differently from me is using a newer version of RSD. I doubt that would be an issue, but may want to try other RSD versions.
In the end, I suppose if 4.0.4 works, use that...

Thank you for you help.
I'll buy a other PHOTON Q on EBAY.
I do other test with the new PHOTON Q.

Hello
I received my new q photon.
It is version 4.1.2
I unlocked the bootloader .
I made a backup with TWRP and OPEN_RECOVERY_209 .
I tried an installation of 3 different ROM but I have an error message !
I do not understand where does the problem ?!
Is this a bad version of TWRP or ROM ?

S6 SM-G920f stuck on samsung logo after trying to install xposed framework

hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?

so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x

vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F

Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx

When u install xposed did u ude the special wanam version of the framework

Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install

Samsung Galaxy S7 cannot flash BL

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?