Database Users

[Q] Unusual s4 brick help

Forgive my noobishness. I've actually lurked xda boards for years and used the EXCELLENT user made guides for all my phones. However, I'm at a complete loss and nothing I've searched, read, or tried has worked and it's consumed my entire day and left me with no phone at all. I cannot believe this phone can be dead unless there's some physical problem so I'm really hoping someone can walk me back to normal.
I bought a new S4 from T-Mobile on Labor Day (obviously I'm in the US). 2 days ago I rooted it successfully using Jimmy Mcgee's video and the various links including mattlgroff's and k0nane's threads. No problems whatsoever. After I did that I used Ti Backup and backed up the apps just in case, then I ran the moderate version of the Truly Clean script and did a factory reset. Everything was perfect. Then...
My wireless data stopped connecting. But that's not my current problem.
I decided to unroot and go back to factory to a) see if something I did was causing the data issue or b) take it back for an exchange at the store. I started with the K0nane and the Samersh72 guides, but frankly tried so many things and failed I don't know were I went wrong. First I tried M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Then I tried Samsung-Updates.com-KERNEL-SGH-M919-TMB-M919UVUAMDL-1366964131.tar
Then I tried the one I did to root it OUDHS-Recovery-jfltetmo-1.0.3.3.tar
Mostly I have gotten a NAND writing fail in Odin with everything I tried (yes I tried making sure Kies is off, the original usb cable, and another PC) which then locks me out of the recovery boot screen and gives me some yellow triangle between a phone and a pc with an error about the stock firmware and tells me to connect to Kies. I can fix that by flashing this PIT file CSB_signed_Fusion3_EUR_0325_V2.pit which allows me to go back to the OUDhs recovery screen.
Also Kies will no longer connect to this device and it says driver install failure when I connect it to the PC (except it stell charges, using the stock cable still).
Dear god someone help me, and I will buy you a beverage. I'm doing instant email notifications of replies. PLEASE.

I'm not sunk yet. I'm rereading the FAQs and guides and I'm going to start over to where I was able to get the rooted version to work. I know the CWM recovery is working so we'll see.

Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2

diodaq said:
Pull out battery for a while, then go to download mode (vol down+home+power) and flash stock fw in odin.
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Ok I will try that. Also I am now trying to flash Samsung-Updates.com-SGH-M919-TMB-M919UVUAMDL-1366964131\M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
I am getting a little farther in the Odin process but it still says fail right after
aboot.mbn

Also I originally followed Jonny's video and only flashed the cwm custom recovery though odin. I flashed the rooted zip file from my phone's internal sd card like in the video. Now I can't get to the internal memory so I tried saving the zip file (the one I used to root it) on the ext sd card. I'm unable to flash that rooted zip from the ext sd card because the phone wants to reboot as soon as it starts doing so.
Is there a way to flash that rooted zip file (or a stock one) from an external sd card?
Is there a way to flash that rooted zip file through odin?

All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.

norml said:
All you have to do is get into download mode and flash stock mdl tar with odin. After it's finished, it'll go into recovery by itself and wipe some small cache partition by itself, after it does that, hold onto the volume up button and get into recovery again and do a factory reset. This is so you don't go into a bootloop. Now get CF auto root and flash it so ur rooted. Next flash a custom recovery and ur all set. It's really easy to do.
Click to expand...
Click to collapse
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.

mattwood440 said:
So far I have been totally unable to get odin to flash a stock tar or any tar since I did the first one 2 days ago. Always, fail.
Click to expand...
Click to collapse
Are you loading the stock tar by clicking PDA?

norml said:
Are you loading the stock tar by clicking PDA?
Click to expand...
Click to collapse
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).

mattwood440 said:
Yes. Also when it fails, it locks me out of the recovery mode. Can you tell me what happens when you flash a new PIT file? Doing that alone does not get a FAIL message and it brings back the recovery screen. However, when I select the pit file it automatically selects the re-partition option which the k0nane says is a no-no (at least for flashing the pda, not sure about the pit which is why I'm asking).
Click to expand...
Click to collapse
Pit file basically means repartitining the storage chip of your device. Yes odin will automatically check repartition when flashing pit files. Flashing pit file is serious business. I recommend following the unbrick/ unroot thtead in the general section. Its pretty precise and I think since you are getting repeated fails in odin you will have to flash pit file.
You will be fine if you follow the instructions there precisely.
Sent from my GT-I9500 using xda app-developers app

OMG it worked. K0nane's procedure worked on a different pc. Dowloaded a fresh Kies but didn't install any of the extra stuff with it. Downloaded, extracted, and ran odin as admin. Hooked it up. Downloaded and extracted the UVUAMDL tar. Put that in the pda box and hit start. Mine would immediately FAIL but this one kept working, and working, and working and reboote. Why why why? I've been at this for about 16 hours. That makes no sense. Thanks anyway. I'll try the other root method when I'm feeling brave again.

[Q] Updated to KNOX, can't restore with KIES or ODIN, soft brick??

Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....

orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
P.S: I was getting the similar problem you have. another usb port helped me

Bordo_Bereli51 said:
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
Click to expand...
Click to collapse
Thanks Yeah I've tried that, I've tried front, back, on a laptop, but Odin still red fails at the writing 'System' (the largest 'chunk' of the tar.md5 file) no matter which 4.3 rom I try
I so upset :crying:

orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
*************
For me I do:
1 - Flash with Odin Pit
2 - Flash with ODIN last recovery philz_touch_5.15.8-i9505.zip
3 - Wip full recovery for new rom
4 - Flash the I9505XXUAMDF_I9505PHNAMD8_PHN
And then this happened.

Alan-B said:
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
Click to expand...
Click to collapse
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar (rename it from .tar.md5 to .tar if your file ending at .tar.md5) and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again

Bordo_Bereli51 said:
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again
Click to expand...
Click to collapse
Hey Bordo
Thankyou so much for your suggestion - I will try the individual component flasher later tonight and then write back on what happens
I will also remember to kill Kies with task manager beforehand, before using ODIN or any other flasher :good:
Thankyou so much for your time and effort in trying to help!!!! Much appreciated

[Q] Killed my Tab 4 (SM-T230NU)

I was looking to factory reset my Tab 4 7.0 to sell, but since I've rooted it and installed TWRP, the process wasn't as simple as I'd have liked. I tried the standard Factory Reset function of TWRP, but it didn't do anything. I tried Wipe Data, still nothing. Then I did an Advanced Wipe and checked off everything, not realizing one of the options was to wipe /system. Now my Tab 4 keeps rebooting to TWRP, and the recovery also states "No OS is installed".
I'm currently downloading the new NH1 firmware from SamMobile and considering flashing it through Odin 3.09. Would this be the most effective method, considering I had no prior backup made to the tablet? Will this likely remove my root access and custom recovery? Is there a chance of tripping something like a Knox counter and bricking my device (happened once when I tried an old method to root my Note 3, Knox blocked part of the flash and left the system halfway between two OS images)

Sounds like you're on the right track with downloading the firmware off of SamMobile. I had a similar issue with my Galaxy Tab 2 and that got my tablet out of its funk.
Sent from my SM-T330NU using Tapatalk

At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
hi i have a tab 3 7.0. why dont you try using odin 3.07 if that fails try emergency firmware recovery in kies. odin flashing of official firmware does not increase binary counter as stated by sammy tech support. but you flashing twrp does increase binary count. hope i helped.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to comCellular allsh. Odin says it was fully successful, but when the taalso tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
I have successfully flashed ND9 and N2E firmwares with Odin 3.07. The NH1 firmware is corrupt when I download it. These are the Cellular South versions which I assume are the US firmwares. I did also flash the Canada versions and I couldn't tell them apart. Currently on ND9 firmware so I could get it rooted. I only have the WiFi 230NU.

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
this question may sound silly but have you tried to wipe data/cache after full odin firmware install?
I believe i was able to keep all my apps and data after full firmware upgrade using odin, so it isnt doing full wipe after all.
.

I rooted and installed TWRP on this device and decided I wanted to get the SM-T330NU instead. I returned the T230 and the clerk tried to factory reset the device and it booted up into TWRP - the clerk made the comment "What in the world" but did not say anything. I had tried to factory reset it before returning and it would not work either.

rsktkr1 said:
I rooted and installed TWRP on this device and decided I wanted to get the SM-T330NU instead. I returned the T230 and the clerk tried to factory reset the device and it booted up into TWRP - the clerk made the comment "What in the world" but did not say anything. I had tried to factory reset it before returning and it would not work either.
Click to expand...
Click to collapse
If you power off the device and then boot up into download mode, connect the usb to your pc and run odin you can flash the factory stock image to the device using odin and that will reset the device to stock. Replacing TWRP with the factory recovery image and everything else. You can download the stock files for the device either by searching these forums or going to sammobile. Try starting with the oldest version available and update from there. I rooted and unrooted the SM-T230NU several times using this method and had no issues. Be patient. Allow the device 5 minutes to boot up after flashing the stock. Make sure the device has 80% charge or better before starting. Leave the device connected to the PC with odin open until you see a message in odin that reads, "passed".

chuman72486 said:
I was looking to factory reset my Tab 4 7.0 to sell, but since I've rooted it and installed TWRP, the process wasn't as simple as I'd have liked. I tried the standard Factory Reset function of TWRP, but it didn't do anything. I tried Wipe Data, still nothing. Then I did an Advanced Wipe and checked off everything, not realizing one of the options was to wipe /system. Now my Tab 4 keeps rebooting to TWRP, and the recovery also states "No OS is installed".
I'm currently downloading the new NH1 firmware from SamMobile and considering flashing it through Odin 3.09. Would this be the most effective method, considering I had no prior backup made to the tablet? Will this likely remove my root access and custom recovery? Is there a chance of tripping something like a Knox counter and bricking my device (happened once when I tried an old method to root my Note 3, Knox blocked part of the flash and left the system halfway between two OS images)
Click to expand...
Click to collapse
Just install deodexed rom from twrp

I don't think sm-t230's have Knox do they? You didn't kill your tablet just flash a stock ROM from sammobile. And you'll be a-OK
Sent from my SM-T230 using XDA Free mobile app

Can't install recovery on SM-T330NU

I tried installing almost all recoveries under T330 and T330NU but Odin keeps reporting as fail. I have tried Odin 3.09 and further without any hope. I even tried using another PC, installing drivers, and ,any versions of Odin but report fail. When I try to boot up the device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Kies and Kies 3 don't recognize my device. Oh and Stock ROM from sammobile and the one provided here in the general forum also report FAIL right after aboot. Am I hard bricked?

Rusell said:
I tried installing almost all recoveries under T330 and T330NU but Odin keeps reporting as fail. I have tried Odin 3.09 and further without any hope. I even tried using another PC, installing drivers, and ,any versions of Odin but report fail. When I try to boot up the device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Kies and Kies 3 don't recognize my device. Oh and Stock ROM from sammobile and the one provided here in the general forum also report FAIL right after aboot. Am I hard bricked?
Click to expand...
Click to collapse
Russ, no you're not bricked, you have a flash that failed in odin, and if i understand it correctly you now have an instruction alive in your cache that executes at reboot resulting in kicking you back to that particular message/state in odin. Succeeding in a recovery or boot.img flash should break it out of that "loop". what changes have you made to your device that odin flashes are now failing? Also , are you using the factory provided cable?
m

moonbutt74 said:
Russ, no you're not bricked, you have a flash that failed in odin, and if i understand it correctly you now have an instruction alive in your cache that executes at reboot resulting in kicking you back to that particular message/state in odin. Succeeding in a recovery or boot.img flash should break it out of that "loop". what changes have you made to your device that odin flashes are now failing? Also , are you using the factory provided cable?
m
Click to expand...
Click to collapse
I am using factory cable and have use other USB cables that are verified working. What I did was flash TWRP from sub77 and then tried to flash stock rom because it was being buggy. That is when the problem started and I cant go past the message. Although I can now access Download mode but when I try to boot up normally or to recovery I receive that message.

Rusell said:
I am using factory cable and have use other USB cables that are verified working. What I did was flash TWRP from sub77 and then tried to flash stock rom because it was being buggy. That is when the problem started and I cant go past the message. Although I can now access Download mode but when I try to boot up normally or to recovery I receive that message.
Click to expand...
Click to collapse
Okay download mode is good, flash the last known working recovery that you were using. Remember to DESELECT the auto restart option in odin.
when the flash is done [res-ok] etc. , force reboot to recovery and attempt a restore of your associated backup. Meaning if your existing backup was made with an older known working version of TWRP you must use that version. If Philz, then Philz.
Odin's later newer version is required to flash the LP 5.1.1 update for the sm-t330nu. see @thisisapoorusernamechoice 's thread for instruction.

S7 Edge no cellular network

Hi there, I have been using S7 Edge SM-G935F happily and a couple of days back installed the BlackDiamond NFE and was not able to connect to the cellular network or make any calls or use mobile data
Again I tried the OneUI and Pixel Experience and all seem to end up with the same problem.
Inserted the SIM into another mobile and there is no problem with the network or the SIM.
Please help me fix the problem, tell me what do I need to flash/install/update.

I guess you need to reflash the stock rom with Odin.

Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers

Thanks for the reply @ariondoneda I will flash the stock rom and will let you know how it went. Cheers

So, after downloading various firmware from SamMobile and all versions of Odin, I was able to flash the latest BTU firmware and with Odin v3.14.
The problem is still persistent, the same Three SIM when inserted into another mobile and in the same location gives a signal strength of -63db which is very strong.
But, when inserted back into the freshly flashed S7 Edge hardly gets any signal -113db, which is very weak
I ran out of options and looking forward for some help in getting back those signal bars back in my mobile.
Hoping someone in here knows how to solve this weird issue

Just came across such issue with another guy yesterday.. your efs got corrupted/damaged. You have to fix it either using hardware box (a local repairer shop can do)
Or
Try following this thread to word.. should give you signals back (tested by me) ..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Note : flashing firmwares again after fixing by above method would negate the fix. Above fix needs to be done after every firmware flash to get signals..

Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only

Siddu_j143 said:
Thanks, @shan22 for pointing me in the direction of a possible solution link
I followed the guide word to word and got a success message from the box and it did reboot like mentioned in the 13th point of the guide
The final result is a no change and still, the same signal strength which is very weak of -113db and most of the times it is emergency calls only
Click to expand...
Click to collapse
Did you flashed csc or home_csc?
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
Sent from my hero2lte using XDA Labs

Did you flashed csc or home_csc?
A) Always a CSC and not HOME_CSC.
Try flashing dbt firmware (with the same bootloader number as your current firmware and using CSC file (NOT Home_CSC) and then doing a format data in recovery)
A) Installing the firmware as I write this.
Then reflash btu firmware (with CSC file, NOT Home CSC) and do a format. Then retry the fix I mentioned in previous post to word..
A) Will do and update you
Also tell me whats your current bootloader number.. if its less then 7 we can try fixing it via combination rom..
A) Will do
Sent from my hero2lte using XDA Labs

Hi @shan22, thanks for all your replies and time to help me out. Here is what happened. I flashed the DBT firmware which was a success and after the flashing, it started into its default recovery where it said "No command" with a dead droid symbol and died and went into the loop I forcefully started the phone into download mode, installed the TWRP, restarted into TWRP, formatted the data and started the phone into download mode, flashed the BTU firmware which also succeded and went into the same loop of "No Command". This happened a couple of times and none of the DBT or BTU firmware did actually start the system. I had no choice and finally had to install the "PixelExperience_Plus_hero2lte" custom ROM zip from TWRP which worked previously and is working now. All of this effort and it's still down to the same problem, no signal at any time
Sadly, the bootloader version is 8

Yeah version 8 .. no dice. Weird, does your phone gives any error when it gives dead android ?
Looks like you get a dm-verity error upon flashing stock firmware..
Trying flashing no verity zips in twrp after flashing stock rom..
So, your efs is indeed corrupted.
Retry all the procedure..
>flash dbt in odin using csc (not home csc)
>flash twrp in odin and boot into twrp directly without booting into phone
>flash no verity zip, then flash latest magisk zip in twp
>boot into phone
>go in download mode again and flash btu in odin using csc (not home_csc)
>flash twrp in odin and boot into twrp directly without booting phone
>flash no verity and magisk in twrp
>boot into phone and see signals..
If no signals, then from this point refer to my above posts where i gave a link of box like software to fix signals. Follow that thread to word and you should get better signals.
That's the thread : https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my hero2lte using XDA Labs

A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.

Siddu_j143 said:
A bit of progress now. As soon as I flash, I need to disconnect the cable from the phone to boot into anything and I am carefully using the auto-reboot option in Odin.
I flashed DBT using CSC, the flashed TWRP and went into it without booting, flashed no verity, then Magisk and boot into the phone. (No errors this time)
Went into download now, flashed BTU, then TWRP and went into it directly without booting. Here when I try to flash the no-verity or the Magisk, I am seeing the error "Failed to mount /data (Invalid Argument)" followed by "Unable to mount storage" error.
Same with Magisk and if I try to wipe the Dalvik Cache or Cache.
The phone is now stuck at the flashing Samsung logo when I start it normally.
Click to expand...
Click to collapse
Oof lol
You need to format data under wipe options and type yes after booting first time into twrp and then flash no verity zip and then magisk ..
This is a standard root procedure for root on android oreo, I hoped you would know that ..
Do this and re-follow all the steps I mentioned above ..
And please read forums thoroughly before messing with your phones.
Sent from my hero2lte using XDA Labs

Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:

Siddu_j143 said:
Hi @shan22, did the steps you mentioned and passed the /data unable to mount error, followed the instructions of installing the DBT first and then BTU, somehow got the signal but, not strong as the other mobile on the same network shows. I am now doing the steps you provided the link to and will update you. Thanks again for all your help, much appreciated. :good:
Click to expand...
Click to collapse
You won't get fully normal signals but will get atleast better or almost good signals. Since your factory efs is corrupted, it can only be restored via efs backup and combination rom with matching binary version. Since you don't have efs backup and latest combination roms aren't available, so there isn't a permanent solution for this.
Sent from my hero2lte using XDA Labs

Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:

Siddu_j143 said:
Agreed @shan22 did go through the whole process and there is no betterment in the signal, it's just the same but a bit better than the earlier. I guess I need to look for a combination rom with the same binary:crying:
Click to expand...
Click to collapse
Sad to hear that, that's why I don't use fully ported/custom roms because they always have a tendency to f*** up your efs, specially if you mess with wrong options or don't know what you're doing.
Even with an efs backup(from when your phone was working correctly), you still need combination rom
And not even paid websites have version 7 and 8 binary combination roms .. the only thing I came across on a lesser known website was that name of version 7 combination rom was : G935FXXU7ATB1 . Maybe it will be of some help to anyone here
Sent from my hero2lte using XDA Labs