is there any combination file that will work on Nougat 7 g935f ?
i also need one all the ones i get give me boot loader exception error
---------- Post added at 07:37 AM ---------- Previous post was at 07:21 AM ----------
the only solution is to downgrade to android 6
everything works fine there
Anyone found a working combonation rom for 7.0 ?? I have the G930FXXU2ARA2 file which gives me a bootloader exeption also
Bootloader exeption
{ RST_STAT = 0x10000 } = FAIL
EVT 2.0. = PASS
ASV TBL VER = 10, GRADE = C = PASS
ASV TBL VER2 = 0. = PASS
ECT : PARA005q. = FAIL
LOT_ID = N673A. = PASS
CHIP_ID = 078F8c6cd2c4. = PASS
CHIP_ID2 = 00000000. = PASS
MNGS : 46'C APOLLO : 47'C G3D : 47'C ISP : 46'C. = pass
Exeption: do_handler_sync: DABT_EL1 (esr : 0x96000010)
=FAIL
Ive deconstructed the combination file to try and pinpoint the issue the failure for the bootloader exeption comes from the Sboot.bin file as i said i deconstucted the combination file and peice by peice made bootable MD5 files for odin the system to test the bootloader exeption only comes into play when Sboot.bin is flashed the boot,nad_fw, system, modem,and everything else work fine but Sboot will not i have possibly also put it down to that the factory nad will not boot onto a knox tripped device however i cannot be sure this is just an educated guess possibly parts of the nad_FW require information from knox and hence wont boot what makes me think of this is the bootloader exeption RST_STAT = 0X10000 and knox trio in download mode appears as 0x100 i could be mistaken but Sboot.bin is the culprit for the exeption hands down if anyone finds a working Sboot for this or knows of one please let me know asap im trying to recover my imei number as it is 000000000000000 FRP LOCK is off OEM lock is OFF flashing my stock rom has not worked and i do not have access to my twrp EFS backup my firmware is G930FXXU2 which is using the new V2 bootloader.
Also i cannot access part of the system.img on the combination firmware it is password protected has anyone ever seen that before also or has the user whom uploaded the combination rom possibly locked the system file down its all the files that would appear in the system folder such as build.prop ect ect ect i wanna know why its password locked and but why its password locked whats so secret SAMSUNG i want to know and i will find out mwahaha
If anyone can help it would be much appreciated.
Thanks
Matthew
Matty1993 said:
Anyone found a working combonation rom for 7.0 ?? I have the G930FXXU2ARA2 file which gives me a bootloader exeption also
Bootloader exeption
{ RST_STAT = 0x10000 } = FAIL
EVT 2.0. = PASS
ASV TBL VER = 10, GRADE = C = PASS
ASV TBL VER2 = 0. = PASS
ECT : PARA005q. = FAIL
LOT_ID = N673A. = PASS
CHIP_ID = 078F8c6cd2c4. = PASS
CHIP_ID2 = 00000000. = PASS
MNGS : 46'C APOLLO : 47'C G3D : 47'C ISP : 46'C. = pass
Exeption: do_handler_sync: DABT_EL1 (esr : 0x96000010)
=FAIL
Ive deconstructed the combination file to try and pinpoint the issue the failure for the bootloader exeption comes from the Sboot.bin file as i said i deconstucted the combination file and peice by peice made bootable MD5 files for odin the system to test the bootloader exeption only comes into play when Sboot.bin is flashed the boot,nad_fw, system, modem,and everything else work fine but Sboot will not i have possibly also put it down to that the factory nad will not boot onto a knox tripped device however i cannot be sure this is just an educated guess possibly parts of the nad_FW require information from knox and hence wont boot what makes me think of this is the bootloader exeption RST_STAT = 0X10000 and knox trio in download mode appears as 0x100 i could be mistaken but Sboot.bin is the culprit for the exeption hands down if anyone finds a working Sboot for this or knows of one please let me know asap im trying to recover my imei number as it is 000000000000000 FRP LOCK is off OEM lock is OFF flashing my stock rom has not worked and i do not have access to my twrp EFS backup my firmware is G930FXXU2 which is using the new V2 bootloader.
Also i cannot access part of the system.img on the combination firmware it is password protected has anyone ever seen that before also or has the user whom uploaded the combination rom possibly locked the system file down its all the files that would appear in the system folder such as build.prop ect ect ect i wanna know why its password locked and but why its password locked whats so secret SAMSUNG i want to know and i will find out mwahaha
If anyone can help it would be much appreciated.
Thanks
Matthew
Click to expand...
Click to collapse
For me bootloader exception occurs when I flash any other firmware part like CSC etc after flashing G935FXXU2ARA1 factory binary, BTW my phone is S7 edge and yours is S7 flat and your help forum is here : https://forum.xda-developers.com/galaxy-s7/help
for me when flashing G935FXXU2ARA1 from AP tab only, I could boot in factory binary without any problems. don't know if there is some other combination firmware with V2 bootloader
edit : here is the V2 combination binary for S7 edge https://shell.boxwares.com/Download.aspx?L=4720
Btw, downgrade to marshmallow not possible anymore after updating the bootloader to V2, I checked by flashing only AP and csc and it remained stucked on the powered by android screen.
Related
What should I do to really have a " completely rooted N9005" ???
I need some suggestion of the "experts" about the fact that my SM-N9005 , that " seems to be rooted " ( and this is confirmed launching the app " root checker" and obtaining the result " This device has root access" ...) ...but , despite this apparent status , it provides me the following issues :
a) I cannot use CWM mode to flash any new ROM nor any other patch using .zip file ; when I try to do a flash , using the option " apply update from external storage" as in this options list :
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
it seems to start to flash but after few seconds I obtain a RED message in the bottom oif the page , like :
" E:signature verification failed"
and in yellow
--Appling Multi-CSC ...
Applied the CSC-code : XTC
Successfully applied multi-CSC
install from sdcard complete
But in reality anything happen , the sistuation is exactly the same as before ...
b) I cannot do any back up ( EFS nor other kind of back up ) ; so , every time I try to flash even using MOP ( it works, but even MOP seems to have some problem..) I get a new ROM installed but with problems... sometime the phone is blocked with the " samsung logo and the Blue led" and I need to restert it with ODIN .....and I need to reinstall all in manual mode
in order to provide to the experts additional info , here are other details
AP : N9005XXUDMJ7
CP: N9005XXUDMJ7
CSC : N9005XXDMJ4
kernel 3.4.0-201940
[email protected]#1
Wed Oct 30 16:51 ....
Build version
JSS15J.N9005XXUDMJ7
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
I would invite everybody able to provide any suggestion to propose some verification or even ask me any additional info to find the way to use a rooted phone as was used to do with other phones before = flash roms without this problem
Thanks in advance for any contribution
tower5 said:
What should I do to really have a " completely rooted N9005" ???
I need some suggestion of the "experts" about the fact that my SM-N9005 , that " seems to be rooted " ( and this is confirmed launching the app " root checker" and obtaining the result " This device has root access" ...) ...but , despite this apparent status , it provides me the following issues :
a) I cannot use CWM mode to flash any new ROM nor any other patch using .zip file ; when I try to do a flash , using the option " apply update from external storage" as in this options list :
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
it seems to start to flash but after few seconds I obtain a RED message in the bottom oif the page , like :
" E:signature verification failed"
and in yellow
--Appling Multi-CSC ...
Applied the CSC-code : XTC
Successfully applied multi-CSC
install from sdcard complete
But in reality anything happen , the sistuation is exactly the same as before ...
b) I cannot do any back up ( EFS nor other kind of back up ) ; so , every time I try to flash even using MOP ( it works, but even MOP seems to have some problem..) I get a new ROM installed but with problems... sometime the phone is blocked with the " samsung logo and the Blue led" and I need to restert it with ODIN .....and I need to reinstall all in manual mode
in order to provide to the experts additional info , here are other details
AP : N9005XXUDMJ7
CP: N9005XXUDMJ7
CSC : N9005XXDMJ4
kernel 3.4.0-201940
[email protected]#1
Wed Oct 30 16:51 ....
Build version
JSS15J.N9005XXUDMJ7
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
I would invite everybody able to provide any suggestion to propose some verification or even ask me any additional info to find the way to use a rooted phone as was used to do with other phones before = flash roms without this problem
Thanks in advance for any contribution
Click to expand...
Click to collapse
try this flash with odin http://forum.xda-developers.com/showthread.php?t=2567283
I does not work.....
jaythenut said:
try this flash with odin http://forum.xda-developers.com/showthread.php?t=2567283
Click to expand...
Click to collapse
first of all , thanks for your support
but I tried , without success , to flash this with odin ; ( I used odin 3.04 ) ; it remains " waiting" for a very long time ( 15 minutes..) without any action , any flash....
I did the test twice, same result....
Any other suggestion?
what could I do to do a deep cleaning of some wrong setting ?
tower5 said:
first of all , thanks for your support
but I tried , without success , to flash this with odin ; ( I used odin 3.04 ) ; it remains " waiting" for a very long time ( 15 minutes..) without any action , any flash....
I did the test twice, same result....
Any other suggestion?
what could I do to do a deep cleaning of some wrong setting ?
Click to expand...
Click to collapse
Strange that your phone shows "Qualcomm Secureboot: None"
In other phones it should be "Qualcomm Secureboot: Enable (CSB)"
tower5 said:
...
in download mode:
ODIN MODE (in red)
Product name : SM-9005
Current Binary : Samsung Official
System Status : Custom
Reacxtivation lock : OFF
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x1
Qualcom secureboot : NONE
AP SWREV : S2,T2,R2,A2,P8
Write protection : Enable
...
Click to expand...
Click to collapse
Your phone seems to have a peculiar setting on secureboot + SWREV configuration, and also seems to be on the (original ?) XTC (Philippines) CSC.
One of the things that I would try (given that your knox is already 0x1) would be to change CSC and write BTU MI7 firmware (and eventually check if CSC actually changed from XTC to BTU). After that you should try again writing Philz recovery.
Another thing to check would be your current bootloader version (and also the bootloader after you write BTU MI7 firmware), the command in adb is:
adb shell getprop ro.boot.bootloader
(or just "getprop ro.boot.bootloader" in a terminal prompt directly on the phone).
I found the solutions !!!!
xclub_101 said:
Your phone seems to have a peculiar setting on secureboot + SWREV configuration, and also seems to be on the (original ?) XTC (Philippines) CSC.
One of the things that I would try (given that your knox is already 0x1) would be to change CSC and write BTU MI7 firmware (and eventually check if CSC actually changed from XTC to BTU). After that you should try again writing Philz recovery.
Another thing to check would be your current bootloader version (and also the bootloader after you write BTU MI7 firmware), the command in adb is:
adb shell getprop ro.boot.bootloader
(or just "getprop ro.boot.bootloader" in a terminal prompt directly on the phone).
Click to expand...
Click to collapse
the solution was :: " apply " what is indicated in this post
http://forum.xda-developers.com/showthread.php?t=2567133
tower5 said:
the solution was :: " apply " what is indicated in this post
http://forum.xda-developers.com/showthread.php?t=2567133
Click to expand...
Click to collapse
Interesting, what firmware do you have now? And how are the switches listed in download mode? And what CSC do you have now? Do you have your IMEI back and is the phone registered on the network (and you can make/receive calls)? Is WiFi also working OK?
Dear Readers,
I recently bought my Samsung Galaxy A5 2016 and its an excellent phone, although, I rooted it quite soon after purchase.
Used CF-Autoroot and everything worked just fine,
Now today I wanted to get Xposed up and running on my phone, and I wanted to back up everything first.
I installed Flashify and downloaded a TWRP img, I flashed it and rebooted my phone.
Heres some info now:
Normal boot: Kernel is not seandroid enforcing
What comes next: Bootloaded exception
[RST_STAT = 0x10000]
ASV TBL VER = 32768
LOT_ID = N469X
-Some useless CPU heat info etc-
Exception: do_handler_sync: UNKNOWN
pc : 0x40205000 l r : 0x43e07c68 sp:"0x43f07f40
Now after that I shut down with vol down+main menu+power button
And I boot again with vol up+main menu+power button
First comes up:
Installing system update...
Then:
On the bottom of the screen: dm-verity verification failed. . .
And ofcourse in the middle the basic options
On the top
Android System Recovery <e3>
PLEASE help me out cause I really dont know what to do now..
Greetings from The Netherlands
Edit: I get different text on the first normal boot every time it seems, some weird letters and numbers etc.
Example: B f $ AFA G $ AFB p G @F H1 G pl
Edit2: I cannot acces download mode and factory reset doesnt work.
You try to run the manufacturer's software with Samsung's Kies3 then follow the ROOT and install TWRP back through Odin Dowload mode Mode.
I have this S7 Edge Verizon which a few days ago gave me a problem. I was using the phone just for a few days.While using it, social media normal stuff it self restarted ( notice that it was pretty hot, but it's a usual thing at this point ) and it got stuck in logo.
P.S: I am really familiar with this kinda stuff because I work at a phone service.
So I tried the usual stuff, wiping cache and data but it didn't solve any thing. So I decided to flash official rom. I downloaded the oreo rom from sammobile and when I tried to flash it, it just skipped all files. I thought this would be due the verizon model, because it's bootloader was locked and oem unlock wasn't enabled. I tried to flash the firmware without the bootloader and with pit but no result. Than I decided to enable oem unlock throught combination file.
When I downloaded combination file, at the website it said G935V but it actually was G935A, and somehow it flashed successfully without any problems. But after reset the phone was stuck at the very first Samsung Logo with some cpu and voltage information at the top left corner with a warning saying RPMB provisioned.
At this point I thought I might as well flash the stock firmware again but this time I got bootloader error and trying to flash it without a bootloader it would skip all files saying something like " skipping all binary files " as before. Bare in mind that during all this testing the phone got really heated. So I let it cool for a while and still nothing happened. Than I decided to flash this boot_root file I found and it actually booted up the Combination Rom. I enabled usb debugging in the settings but there was no Oem Unlock option, not even grayed out ( maybe because the rom G935A does not have the option ).
Even the USB debug enabled it still couldn't flash stock rom because of bootloader error and some binary error also and again if i didn't include bootloader it would skip all files.
I was thinking of installing a custom rom but I found out that there is not twrp avaible for s7 edge verizon because of it's locked bootloader. And if I try to install supersu through adb it just doesn't work.
Now my download section looks like this
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON (don't worrie about it, i got all the gmail info)
WARRANTY VOID: 0x0 (the warranty has expired anyways)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B5(2, 1, 1, 1, 1 ) K1 S4
SECURE BOOT: ENABLE
IDOQ : G(42), S(12) mA
CPU SERIAL NUM : 0x1408501f
Fused open loop voltage: 970mV
RPMB PROVISIONED
The Samsung first boot up screen still has the RPMB PROVISIONED with the cpu information and also the custom flagg and I am able to boot up the combination rom.
I also tried to flash the official rom with z3x but it didn't solve anything. If you need any additional information just tell me. Any help would be greatly appreciated.
You need to download official firmware from another source. I recommend updato.com.
https://updato.com/firmware-archive-select-model?record=4F3A1B13706611E89F15FA163EE8F90B
You need to flash the latest Oreo firmware for the Verizon SM-G935V because it sounds like your phone has issues with your current bootloader. Go back to the Verizon firmware first and see if the phone works normally. Also, flash the regular CSC file not CSC_HOME.
Help
I too have the same exact problem. Has anyone figured out how to fix this?
Hi recently I believe I soft-bricked my Galaxy S8 SM-G950U I was having trouble getting service on it, It would only work on like major roads so I knew something was wrong with it so I tried to get the device fully updated and everything by going in the setting menu in Android and doing it from there It still was doing the same issues. So I went about restoring it with OEM firmware with Odin, everything worked when I restarted it, it was running more smoothly and everything. So since I achieved doing that I was like might as well root it so I installed firmware in Odin then everything messed up I couldn't get into my boot-loader anymore. So I reflashed the stock files that originally worked at first and I was having the same issue. In the bootloader it's on a blue screen I see no command for a second and then it goes to installing updates and the screen keeps on flashing. I believe it's because I reflashed a firmware that had a loader bootloader I believe it was the v2 bootloader. I need the v3 bootloader for ATT galaxy I can't find it on any site preferably all the Odin files needed. Please any expert let me know if you experience this thanks!
DOWNLOAD MODE
CARRIER : ATT
RPMB fuse blown
RPMB PROVISIONED
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS : OFFICIAL
FRP LOCK : ON
WARRANTY VOID : 0x0
QUALCOMM SECUREBOOT : ENABLED
RP SWREV : B5(2,1,1,1,1) K4 S5
SECURE DONLOAD : ENABLED
DID : 205EA46632FD
installed firmware:
https://ibb.co/ggCYYkN
recovery:
https://ibb.co/bzd8dxs
i try to install :
G950FXXU4CRJ5_G950FOXM4CRJ3_ARO
Prince Comsy Odin v3.12
first time i tryed to burn the rom i got in odin write failed (or similar i didn't write it down).
second time and later i get PIT error
https://ibb.co/cxYd0YP
please your help to understand whats going on with this device \ firmware
do-d said:
installed firmware:
https://ibb.co/ggCYYkN
recovery:
https://ibb.co/bzd8dxs
i try to install :
G950FXXU4CRJ5_G950FOXM4CRJ3_ARO
Prince Comsy Odin v3.12
first time i tryed to burn the rom i got in odin write failed (or similar i didn't write it down).
second time and later i get PIT error
https://ibb.co/cxYd0YP
please your help to understand whats going on with this device \ firmware
Click to expand...
Click to collapse
Looks like judging from your screen shots
1. You are trying to flash F firmware onto a U device. Exynos to snapdragon. Will cause you issues.
2. You will need Odin ( or patched Odin ) 3.13.1 or higher
3. You will need a binary ( bootloader ) version 5 or higher.
Just download latest firmware from sammobile
spawnlives said:
Looks like judging from your screen shots
1. You are trying to flash F firmware onto a U device. Exynos to snapdragon. Will cause you issues.
2. You will need Odin ( or patched Odin ) 3.13.1 or higher
3. You will need a binary ( bootloader ) version 5 or higher.
Click to expand...
Click to collapse
thank you!
phone was sold as F model , it has all stickers saying its F model
here it looks like an F firmware installed https://ibb.co/ggCYYkN
but its a U model ?
so for next time what is the right way to get the real device model ?
do-d said:
thank you!
phone was sold as F model , it has all stickers saying its F model
here it looks like an F firmware installed https://ibb.co/ggCYYkN
but its a U model ?
so for next time what is the right way to get the real device model ?
Click to expand...
Click to collapse
There are many guides on the internet regarding to phone authentication and about refurbished phones.
On your S8, since it doesn't have a removable battery, on the back, down the bottom, should show model no. etc. engraved on it ( not stickers ).
On the back it will also show iIMEI + serial number. Compare it to what it say's on the phone ( about phone + *#06# ) to the back engraving.
There are websites that can check your IMEI number to give you various information about the phone.
Buying a phone from the internet ( eg: eBay etc.) using the IMEI can be used as a way to check the phone.
i just got one more device from a local store , it's not official retailer of samsung , its from a paralel imports
and its the same ****
firmware box and stickers say SM-G950F
recovery say SM-G950U, i didn't tried to flush because i cant get the OEM unlock.
BTW is it possible to downgrade this device to android 8 ?
image uploader
so if i understood right i should be able to flush this firmware on this phone
G950USQU5CRL2
?
do-d said:
so if i understood right i should be able to flush this firmware on this phone
G950USQU5CRL2
?
Click to expand...
Click to collapse
In download mode it will have a line with PR SWREV
The number after the B is your binary ( bootloader ) number.You will need to flash this number or higher. You can not downgrade binary numbers.
Depending on what firmware you flash U or U1 you may need patched Odin.
spawnlives said:
In download mode it will have a line with PR SWREV
The number after the B is your binary ( bootloader ) number.You will need to flash this number or higher. You can not downgrade binary numbers.
Depending on what firmware you flash U or U1 you may need patched Odin.
Click to expand...
Click to collapse
so from Download Mode picture i can say binary 7 it is
in this firmware G950USQU5CRL2 U5 is it the binary or is it the security patch ?
do-d said:
so from Download Mode picture i can say binary 7 it is
in this firmware G950USQU5CRL2 U5 is it the binary or is it the security patch ?
Click to expand...
Click to collapse
Binary ( bootloader ) is the 5th number from the right of the firmware ( in the above post it's 7 )
e.g.:G950USQU5CRL2 - 5 is the binary number.
The letters/numbers after the binary number will tell you version ( security patch ) issue information but is easier to check the date of the firmware from the website you are downloading from.
thank you @spawnlives i really appreciate this
spawnlives said:
Binary ( bootloader ) is the 5th number from the right of the firmware ( in the above post it's 7 )
e.g.:G950USQU5CRL2 - 5 is the binary number.
The letters/numbers after the binary number will tell you version ( security patch ) issue information but is easier to check the date of the firmware from the website you are downloading from.
Click to expand...
Click to collapse
Sir, my binary matched with the ROM, but I get the error again as "secure check failIT", "sw rev check fail device 2 binary 1" and "secure check fail bootloader"
can u share the link to download the appropriate bootloader for J5 Prime(G570F)