Updated my RiCE to 11.1 from 10.1, managed to get everything done however noticed my wifi calling had gone.
I ended up flashing a CSC file for H3G UK i downloaded from her, which has now got me stuck in the samsung bootloop, the CSC I should have used I didn't.
Tried to flash BL, using the spam start method then flashing TWRP via AP, but still cannot get into TWRP.
Anyone know if I have any other options?
I can not get out of the bootloop, all I can access is download mode.
Thanks
Daf123 said:
Updated my RiCE to 11.1 from 10.1, managed to get everything done however noticed my wifi calling had gone.
I ended up flashing a CSC file for H3G UK i downloaded from her, which has now got me stuck in the samsung bootloop, the CSC I should have used I didn't.
Tried to flash BL, using the spam start method then flashing TWRP via AP, but still cannot get into TWRP.
Anyone know if I have any other options?
I can not get out of the bootloop, all I can access is download mode.
Thanks
Click to expand...
Click to collapse
its better to write your post on their thread.
https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Related
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Stock Firmware for S7 Edge G935T UVU3APG1
Duggi1663 said:
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Click to expand...
Click to collapse
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Duggi1663 said:
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Click to expand...
Click to collapse
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
First of all you wanted to Flash SuperSu.... Did you enable Android Debugging.... Then check OEM Unlock?
If not you messed up there...
Next You need use Odin to flash CF-Root. You are now running a patched Kernel and SuperSU
Use TWRP app to install twrp for your device.
i have the same exact problem, been trying to flash stock firmware but cant get it to work. help please!!!! which firmware? can i get a link please!!!!!!!!!!
qwewqa said:
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
Click to expand...
Click to collapse
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
BobTheTenth said:
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
Click to expand...
Click to collapse
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
qwewqa said:
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
Click to expand...
Click to collapse
Thanks!
Recovery locked
I had a problem with mt tab a SM-P580
After the newest update 7.0 it was crashing, i factory reseted it, and that seemed to work for a while. i deleted most of the apps and it continued. the 3rd factory reset, it got stuck on login/create samsung account with a pop up window of the system ui.
i researched and found the firmware 6.0 on here, i followed the instructions, except that the files was missing the cp. had bl, ap, csc and csc home. still followed instructions without the cp. now tablet its stuck with android and no command on the bottom. At this point, I've tried anything I know off, tried Kies but did not work. tried flashing it with other instructions and firmware 7.0 again. nothing. I even downloaded firmware from samsung, all of them are missing the cp file.
What else can I do.
How to find the CP file?
Thank you all in advance!!
Download Samsung Switch, install and follow instruction for flashing the latest FW
LALAnana said:
I had a problem with mt tab a SM-P580
After the newest update 7.0 it was crashing, i factory reseted it, and that seemed to work for a while. i deleted most of the apps and it continued. the 3rd factory reset, it got stuck on login/create samsung account with a pop up window of the system ui.
i researched and found the firmware 6.0 on here, i followed the instructions, except that the files was missing the cp. had bl, ap, csc and csc home. still followed instructions without the cp. now tablet its stuck with android and no command on the bottom. At this point, I've tried anything I know off, tried Kies but did not work. tried flashing it with other instructions and firmware 7.0 again. nothing. I even downloaded firmware from samsung, all of them are missing the cp file.
What else can I do.
How to find the CP file?
Thank you all in advance!!
Click to expand...
Click to collapse
The proper firmware is here. I believe I flashed the home file in the cp spot.
https://updato.com/firmware-archive-select-model?exact=1&q=SM-P580
Hi guys,
Well it all started when i wanted to root my s8 (SM-g950f) running on android 7.0. It went well until i had to login into my snapchat account, some dumb dude recommanded root-switch, which ended up by deleting my root.
Somehow i had the bright idea of restarting my phone, it didn't start afterwards.
I had to flash the ROM, so I went for the OREO version G950FXXU1CRB7_G950FOXM1CRAP_XEF that i got from sammobile for France (I actually live in Morocco but i've bought my phone from France).
Using Odin PrinceComsy and uncompressing the lz4 files and copressing them again in a .tar extension, i've got a PASS in Odin but the phone entered a bootloop. I went for a little research which ended up by wiping cache and a factory reset solution. First i couldn't access the recovery mode, so i did a flash with twrp-3.2.1-0-dreamlte and a little magic trick (have a fail on purpose to go quickly to recovery mode).
Sadly neither the wipe cache nor the factory reset made an end for the bootloop and my misery
If you got any help for me I would appreciate it.
Thanks,
Resolved Edit :
So I finally got my phone back on. This after i had tryed flashing it with 3 different versions of Android oreo 8.0. And finally, i went back for the nougat easily. I think the source of the problem is the procedure of uncompressing the lz4 files, cause any modifications of the files can end up badly for the flash. Cheers !
xfelt said:
Hi guys,
Well it all started when i wanted to root my s8 (SM-g950f) running on android 7.0. It went well until i had to login into my snapchat account, some dumb dude recommanded root-switch, which ended up by deleting my root.
Somehow i had the bright idea of restarting my phone, it didn't start afterwards.
I had to flash the ROM, so I went for the OREO version G950FXXU1CRB7_G950FOXM1CRAP_XEF that i got from sammobile for France (I actually live in Morocco but i've bought my phone from France).
Using Odin PrinceComsy and uncompressing the lz4 files and copressing them again in a .tar extension, i've got a PASS in Odin but the phone entered a bootloop. I went for a little research which ended up by wiping cache and a factory reset solution. First i couldn't access the recovery mode, so i did a flash with twrp-3.2.1-0-dreamlte and a little magic trick (have a fail on purpose to go quickly to recovery mode).
Sadly neither the wipe cache nor the factory reset made an end for the bootloop and my misery
If you got any help for me I would appreciate it.
Thanks,
Click to expand...
Click to collapse
If it were me I would start from the top and flash:
G950FXXU1AQL5_G950FUWE1AQL5_UNE.zip
with Odin 3.12.3
Then flash twrp-3.2.1-0-dreamlte.img.tar
Then flash Magisk-v15.2.zip
I have the G950F and that is exactly what I have used for Android Nougat (not upgrading to Oreo for now).
cwhiatt said:
If it were me I would start from the top and flash:
G950FXXU1AQL5_G950FUWE1AQL5_UNE.zip
with Odin 3.12.3
Then flash twrp-3.2.1-0-dreamlte.img.tar
Then flash Magisk-v15.2.zip
I have the G950F and that is exactly what I have used for Android Nougat (not upgrading to Oreo for now).
Click to expand...
Click to collapse
So you suggest i give up on the oreo version ?
xfelt said:
So you suggest i give up on the oreo version ?
Click to expand...
Click to collapse
Totally up to you. Sounds like there maybe are some things to get worked out with Oreo maybe. If not then go for it
My device got FRP locked and so I used Odin to flash the official firmware from Sammobile and now I have T mobile menus like personal hotspot in my settings apps even though my device is the Wi-Fi only tab A 2016.
Here's how I got here:
I flashed the correct firmware, and in Odin I flashed the ap file, that's all. It succeeded but when installing updates, it said no command and went to the stock recovery. I factory wiped and rebooted.
How do I get rid of the T mobile menu's?
Any help would be appreciated
FIXED: Reflash in Odin with BL and CSC file
Same
I got the same problem, fixed it by flashing ap and csc
I live in the US and chose the XAR version from Frija
Now my lockscreen doesn't work, how do i fix it?
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