I've rooted my phone a dozen times, flashed TWRP and CWM before via recovery and Odin. Yesterday EVERY aplication started to give me a "Unfortunately, xxxx stopped working" and my phone would enter the system.
I flashed a new rom (5.0 N900XXUEBOA6) and since then, can't root my device.
If i try to use Odin, i have the "Nand write fail" error, if i try the recovery "E: failed to verify whole-file signature" "E: signature verification failed"
I don't think that a factory reset would help my problem, therefore, would you guys have any insight on what seems to be the problem?
HI XDA,
I am using Galaxy Note 4 (SM-N910G)
1st STAGE
Suddenly in my phone's recovery menu says "drk verification failed",
If i install firmware vis Kies or ODIN it says"write flash memory failed"
2nd STAGE
I flash new Firmware and PIT file(get from some web) via ODIN3_v1.85.
But phone was not worked properly.
When i open recovery boot menu it says"Installing System updates"(5 min)
then after select "wiping menu" or "reboot" it takes 10 min.
3rd STAGE
I flash via Smart switch Emergency Recovery mode but it says above errors.(But it working properly compered to above condition but have same errors)
4th stage
I flash official ROM(AP) and Boot Loader(BL) vis ODIN3_v3.11.
Started properly but same screen says"Installing system updates" and all that.
Sometimes says "NO COMMAND" for a bit sec and goes to recovery menu.
Note: Phone is not rooted
What should i do to solve this issue?
I think that may issue again rise from PIT file?(It seems partition line in recovery menu)
is there any way to remove partition made by PIT file?
What should happen if i check "re-partition"(Not given PIT file) or "Nand Erase All" while flashing with ODIN?
I have BL,AP,CP,CSC for that phone.
Thanks in advance.
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
meohmy said:
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
Click to expand...
Click to collapse
Flash this using odin :
https://drive.google.com/uc?id=1tg9hJOCquyfuyROYtgpxyVKNbuidzdL8&export=download
Then, you will be able to flash latest version normaly, and also your will remove frp lock.
Thanks for that, I will flash it when I get home and report back.
Didn't work for me, the combination file gave an 'md5 error! Binary is invalid' message when loading into Odin, while renaming to .tar the flash failed.
firmware update start
Single download
sboot bin
param.bin
FAIL
Thanks for your suggestion though.
I tried installing firmware G928FXXS5CRH1 (VOD) but it failed at hidden system image, I removed that file and created a .tar which flashed successfully but the phone rebooted
to recovery initially but still showed a dm-verity error. I deleted the cache and then factory reset which appeared to also complete successfully but the phone would not boot up.
I then tried flashing the hidden sys image on its own but that failed and the phone went to the Smart Switch error recovery page, Smart Switch will not recognise the phone so will not allow access to the emergency recovery facility.
Still trying though if anyone has any idea's.
Hi there,
Im in the same boat. It had the verity error too.
BUT:
For me it worked to flash the 4-part firmware of the G928FXXS5CRH1 via Odin then.
The device boots again, without the verity error
It had Android 5.1 before, when I could flash the COMBINATION ROM and use it just fine.
(but it was a Android 7 combination ROM) :/
After flashing Android 7 debranded (G928FXXS5CRH1) in 4-parts (BL, AP, CC and CSC file) the FRP lock is still there of course,
but the phone is booting again without the verity error.
COMBINATION ROM will no longer let me flash it, though.
https://forum.xda-developers.com/s6-edge-plus/help/g-928f-verity-0x02-modem-bin-fail-t3886122
The download I did via the tool "samfirm" use chk32 and decrypt on downloading !
"SM-G928F_1_20180828170540_5avji4munw_fac"
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
meohmy said:
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
Click to expand...
Click to collapse
Hell Friend, Not sure If you could get this message, If yes, Kindly help me., I am facing the same issue with my Samsung Galaxy Note 5 (N920G/I) but could not find 4 parts FRP unlock firmware. Do let me know If anyone finds one.
Thanks!
I have a co-worker's G930V that decided it wanted to only boot to the 'no command' recovery thing (not the menu, just blue with no command'), it's devolved to the point where he doesn't care about the data on it, just trying to get it working.
Info:
It's FRP locked (he knows the login, so this isn't important)
It's on binary 10 (can ONLY flash firmware CSF2 as far as I can tell)
Things I've tried and outcomes
Smartswitch: 'unsupported device'
Verizon's tool: 'Unsupport dev_type'
Odin flashing BL/AP/CP/CSC anything other than CSF2: 'SW REV CHECK FAIL'
Odin flashing BL/AP/CP/CSC for CSF2: 'recovery booting' followed by it rebooting and sometimes getting to a screen with a percentage bar that just says 'Error' (attached)
Odin flashing PIT/BL/AP/CP/CSC: same as non put odin
Odin flashing PIT/BL/AP/CP/CSC and NAND ERASE: same thing
I was able to get it to get to the encryption failed screen once by flashing just AP after a NAND ERASE PIT/BL/AP/CP/CSC.
I also got it to show "Custom Binary blocked by SECURE BOOT' by only flashing official firmware...
Update: There are other weird things that happen... I got odin to flash the latest G930U firmware and the same thing happens, I've also seen the grey circle with a lightning bolt screen leading me to believe its a battery issue.
IT WAS A BATTERY ISSUE, Tested with an S6 battery and once I flashed the Verizon firmware it booted right up.
Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?
aenderboy said:
Today i wanted to update my phone from cynaogenmod to a recent lineageos. It followed this guide jfltexx/install, but when i tried to "heimdall flash --RECOVERY ...", the blue progress bar on the phone got to ~99% - then heimdall crashed:
Code:
...
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%libusb: error [udev_hotplug_event] ignoring udev action bind
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Because at that point nothing would change anymore, i unplugged the phone and rebooted. Since then the phone won't boot android anymore and reports "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." when booting to recovery mode. Download mode is still accessible, but worthless:
Flashing the original ROM fails with "Complete(Write) operation failed": imgur
Flashing it with a PIT i found on this forum doesn't work either: imgur
Is my phone completely lost? Is there something i can do?
Click to expand...
Click to collapse
Hello,
Please follow my Guides. I recommend you to follow the guide "clean install from scratch" and also use Odin. Everything you need it's on my thread and in my collection.
Issue Resolved
The solution was to use a shorter USB cable. Thank you so much for making me not loose my faith!