Wifi not working, so I flash it Odin official APJ1, now when boot: "SECURE CHECK FAIL: MODEM"
Can restore from Verizon Repair Assistant, but wifi still not working and OTA write "can't authentication your device" (from sim Internet).
Knox 0x0
Variants?
Related
Dear All,
Originally I have a N9200 which i accidentally deleted 3000+ photos of a 1 years old baby.
Here is what i did...and the problems i faced...
1. Used the software Dr. Fone for Android to try root the device
Result: failed
Problems : the application keep looping and reboot the device, and after 2 hours it tells me failed to root and hence failed to recover photos
What i Did : staff of DrFone tell me my phone is in 6.0.1 mashmallow and hence not supported...
2. OK... if Dr Fone failed to root, then i use CF Auto Root. I got the CF Auto Root , but ...
Result: failed
Problems : when update using Odin , the phone showed that "Custom Binary blocked by FRP"
shxx... i further check in google that i need to check "Allow OEM unlock", but the phone seems still can boot up normally... at this moment i notice now the phone will be rebooted automatically after 2mins...
What i Did : i used the 2mins to check back "Allow OEM unlock" and try again
3. Check Allow OEM unlock and flash CF Auto Root again
Result: failed
Problems: i noticed the CROM lock is still on...
What I Did : i installed CROM Service app, but when it opend it failed to unlock....and i checked that the phone's baseband is "Unknown" now....the phone will still be rebooted automatically after 2mins
4. Use Samsung Kies 3 Emergency Initialization
Result: the update look fine, but when it goes to recovery mode, it showed "Installing Update" , and a yellow triangle appeared with a dead android appear...
After restarted, everything is clean now...However, the phone is still rebooted automatically after 2mins..........
What I want to do is to recover deleted baby photos only:crying::crying::crying:
The deadlock now is... the phone cannot be rooted due to CROM Lock, but CROM app failed to launch due to baseband unknown!!
Anyone have similar situation and hopefully can share together.
Thanks again...
try app disk digger .. but works fine when the phone is rooted
Hello all
I tried flashing the device using Odin and everything downloads successfully. The phone will reboot and during the system update process, it fails at 32% each time. The phone then freezes on "Erasing". I can redo the Odin process and each time it just fails at 32% during the update process. I am unable to boot the phone into recovery mode. Smart Switch also does not recognize the device that was why I attempted the Odin process in the first place. The only thing I am able to do to this point is put the phone into Odin mode. I have been flashing G920AUCS7ERC1_ATT7ERC1 using Odin 3.13.1 Patched.
In Odin mode the device shows
PRODUCT NAME: SM-G920A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0X0000)
RP SWREV: B:5 K:3 S:3
A little backstory... This phone belongs to my mother. She thinks she downloaded some applications and this sent the phone into a bootloop. A soft reset leads to a screen showing "No command". I am unable to do anything further with the device. I am really just looking to get the phone to boot so I can image the device and pull whatever data from it that I can.
Thank you for any help you can provide.
Probably phone can't access DRK.
System Status: Custom on a locked bootloader means someone tried to repair the DRK using a combination firmware, but didn't finish the job. You will need a factory binary on Nougat, which will boot the phone, then will need to repair the DRK. Or if you don't, flash an efs backup through Odin in download mode.
I flashed in G920AUCU5DQB3_FIX_DRK_dm-verity that I located through these forums and now the phone will freeze on the "Samsung" screen just as the device is detected through USB but then the phone restarts and loops again. This is the furthest I have made it so far lol
Look up combo firmware G920AUCU6AQC1, that appears to be a 2017 release so it probably has the same bit increment as nougat
Teracotta said:
Look up combo firmware G920AUCU6AQC1, that appears to be a 2017 release so it probably has the same bit increment as nougat
Click to expand...
Click to collapse
When I attempt to flash this firmware, the process fails and "SW REV. CHECK FAIL. DEVICE: 5, BINARY: 4" is displayed on the phone. I tried using different cables and multiple attempts with the same results each time.
Kromah02 said:
When I attempt to flash this firmware, the process fails and "SW REV. CHECK FAIL. DEVICE: 5, BINARY: 4" is displayed on the phone. I tried using different cables and multiple attempts with the same results each time.
Click to expand...
Click to collapse
That is the knox bitlock which means that you are on a newer bootloader than the combo firmware. However, G920AUCU6AQC1 should be a newer firmware, and shouldn't interpret that as binary: 4. I am guessing it's a wrong display.
You may need a box to boot it out. See this topic which hits on your exact firmware:
http://forum.gsmhosting.com/vbb/f684/sm-g920aucs7-dm-verity-error-question-solved-2367622/
On dm-verity error I think fix efs function gets the phone to boot.
dave357 said:
Actually you can downgrade to 6.0.1 and any Revision aka BIT 5 firmware. The reason for this is that the Rev 7 or 7.0 Firmware has the same bootloader firmware as 6.0.1 as long as its BIT 5 aka Rev 5 Firmware you are flashin. Also use Odin 3.13.3 SHAE 256 Fix_ATT_Verizon. PrinceComsy Odin may work as well. But I have done several of these downgrades on G920A with no issues-
Click to expand...
Click to collapse
This is worth a shot, try to back to the most recent Marshmallow firmware, then flash the Marshmallow combo rom.
I have a Galaxy note9 N9600 and when i try to flash any room i get the Error in the Note 9 display
Mdm mode can´t download
also in odin it says
error fail (auth)
I can restore it(donde it already) so it is not locked in "demo mode"
anyone knows what could be hapenning?
thank you in advance!
i have also same model N9600 Mdm Can't download mode also stock on recovery mode any solution help please
Hi. I have my note 8 in boot loop with a red string "custom Binary Blocked by FRP Lock".
My device was absolutely not rooted.
I can only enter the Download Mode.
There I found the binary count is greater than zero (0xa... it should be equal to 10) and also thatmy current binary is custom.
But it also give warranty void: 0x0000 (mmeaning the device is not rooted)
How is this possible?
Should I use Odin to re-install the OS?
Thank
Hi! I've tried following dr.ketan's post on rooting a Note 9 with the first method ("(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only").
After that I've flashed RomAur via TWRP, booted up and while setting up my account the screen became black with the message "only official released binaries are allowed" . I've then tried to flash the stock firmware via Odin but on the screen of my phone I get a "SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1" error.
Odin seemed stuck so I unplugged my phone and then got a screen saying "An error has occured updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
My phone's a N960F/DS
After further research I've come to the conclusion that:
1) SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1 means the firmware I was trying to flash was too old and Samsung decided that downgrading isn't an option anymore.
2) I'm unable to flash anything else besides Samsung official firmware for a 7 or more days because of a Knox Guard (RMM/KG state prenormal). So reinstalling any custom recovery to then flash a new Rom can't be done since there's no way to bypass this time period on Pie.
I did end up flashing stock but I can't mod my phone until the kg state goes back to normal or checking
I've tried waiting for 168 hours twice since the last post. KG State won't change from prenormal. I should mention that my OEM unlock option is available but I can't flash anything besides Samsung binaries. Last week I've flashed TWRP despite the KG State not changing and I got the same "only official released binaries are allowed" error followed by a red fail box in ODIN. At this point I have no idea how to fix it. Does anyone have any suggestion?
I've downloaded the latest stock (N960FXXU4DSLB) and installed it. After that it looks like the prenormal state went away. Immediately I've toggled the OEM Unlock option, waited for the factory reset to be done and checked to see if the toggle was still there. The OEM unlock option works just like before BUT I've successfully installed geiti94's latest TWRP (3.2.3 ATM). Flashing RMM-State_Bypass_Mesa_v2.zip no-verity-opt-encrypt-6.0.zip and Magisk 20.2 seem to be able to get root working but there are some weird bugs:
- can't set up any security measure such as a pin, patter or biometrics
- if I try to log into my Samsung account I get a "processing failed" pop up
- restarting my phone causes it to bootloop