I tried to flash my verizon firmware to the unlocked one with odin, but it failed and now I'm stuck in with the software update failed, use the verizon software upgrade assistant to repair your device. Any ideas on how to fix?
Here's the procedure I followed:
1. Boot in recover and erase wipe
2. boot into download mode and open odin 3.13.1_3B_Patched
3. Select BL, AP, CP, and non-home CSC file
4. watch for the popup that says "your device will restart to apply new carrier settings", and do it. Make sure your desired SIM is inserted for this step.
It got about 15% through step 3 and said failed on the phone. I haven't been able to get any further.
miketunes said:
I tried to flash my verizon firmware to the unlocked one with odin, but it failed and now I'm stuck in with the software update failed, use the verizon software upgrade assistant to repair your device. Any ideas on how to fix?
Here's the procedure I followed:
1. Boot in recover and erase wipe
2. boot into download mode and open odin 3.13.1_3B_Patched
3. Select BL, AP, CP, and non-home CSC file
4. watch for the popup that says "your device will restart to apply new carrier settings", and do it. Make sure your desired SIM is inserted for this step.
It got about 15% through step 3 and said failed on the phone. I haven't been able to get any further.
Click to expand...
Click to collapse
Try the unpatched odin
chuckboy1129 said:
Try the unpatched odin
Click to expand...
Click to collapse
Unpatched odin gives me an sha256 error. I tried the patched again, it starts to send the files, the gets stuck on write operation failed.
Related
Hi
The device is Samsung Galaxy Tab S2 8.0 SM-T713.
Following is what happened:
1. Installed TWRP and then Installed Lightning ROM v1.0.
2. Restarted the tablet without turning on OEM Unlock.
3. Did not boot by giving error "custom binary blocked by frp lock"
4. Tried installing stock firmware with odin. Firmware installs successfully but when the tablet reboots, it keep showing the glowing samsung logo.
5. Tried multiple different firmwares and eventually tried the latest firmware for the XAR region. Now only that firmware can be installed and all other older firmwares fail in the installation step giving the error "sw rev check fail aboot fused 2 binary 1"
Would really appreciate if anyone could help.
I assume that flashing pit file with the latest XAR region firmware will help boot the tablet but i cannot find the pit file to use.
Please HELP!
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
lewmur said:
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
Click to expand...
Click to collapse
The problem is that the TWRP recovery is long gone. Its not on the tablet anymore. I cannot flash TWRP because of FRP lock. I can access stock recovery but it also does not allow me to wipe data and factory reset due to FRP lock.
Any other suggestions.
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
rafayzq said:
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
Click to expand...
Click to collapse
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
lewmur said:
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
Click to expand...
Click to collapse
All the problems started when i restarted the tablet running a custom rom without enabling the OEM Unlock option in Developer Options in settings.
The lesson i learned the hard way is that you should always keep the OEM Unlock enabled
now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
did you try Kies?
lincolnsxda said:
now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
1st why you ran Verizon bootloader to this phone? this phone has unlocked bootloader it doesnt need to be unlocked
2nd your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repair
3rd when you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root, remember 910t, 910t3 comes with unlocked bootloaders no need to unlock them
Click to expand...
Click to collapse
I have an att note 9 that started boot looping while I was trying to update csa7 to a newer version through stock recovery I clicked something that says lacking boot storage I pressed no to back out of it and it rebooted and now I cannot do anything but go in download mode and recovery ive tried diff update zips and odins and everything has failed does anyone have an odin stock image of csa7 that's working I also have the latest odins 3.13.1 and the patched one both either get stuck on setup connection or failed I have the att 960u its on csa7 thanks in advance
edit 1: odin now fails as cannot open serial port
edit 2: fixed cannot open serial port but cannot get a firmware to write the ones I tried have failed to write
any help would be greatly appreciated I have downloaded almost every att firmware from 960u and 960u1 just need some guidance pls
hi guys, im lost and desperate need help right now
its been 4 days im looking for solution but no avail
please i need help to make my device back to normal again
device : Samsung Note 8 (XSP - Singapore Region) running One UI 1, Android 9. oem unlocked.
so here is the stories,
3 days ago, 22 Dec 2020.
i did factory reset on my device, and reboot
after that, my device lost the network, it detect my sim card but cant connect to network. signal lost.
i tried to reboot like usuall but still, no network available. lost the signal
but i can connect to wifi.
and i reboot it again, suddenly stuck at samsung logo
at first i thought this is easy just need to flash it with stock firmware
and i did, i download the stock firmware from sammobile, XSP - Singapore region.
with BL, CP, CSC, AP file, repartition not ticked. only tick the Auto Reboot and F. Reset time.
i choose the CSC file not HOME_CSC. so everything went well. PASS! green light in odin.
successfully flash my device, but weird, it is still wont detect any network or signal. i tried to automatically find network operator but it says "unable to connect" i tried everything and it says "NO NETWORK"
i did checked my imei , and its safe, its not blocked. but why my device still wont detect my sim card
and the i tried to reflash and flash and flash it again, several time hoping it will detect any network from my sim card after flashing but no avail
and then at the night, flash at 6th time, my device giving me more problem.
suddenly stuck at samsung logo bootloop. i went to recovery state, its says :
"E: FAILED TO MOUNT /EFS (INVALID ARGUMENT)
DM VERITY ERROR" stuff like that
damnn what problem again this time
im frustated already
and i flash it again with Pixel Experience rom hoping the problem will went away, but still , same results. "NO NETWORK"
i look it up in Settings - About - Status - Sim Card Status , its shown "DISCONNECTED"
my imei still there but just wont connect to network.
and then i tried to re-flash it again with stock firmware and again went straight into bootloop. with broken efs etc some****
im so mad and frustated, the problem keeps coming.
and then i found a temporary solution from @bluecub1st thread about the same problem :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
but at my case , the solution still failed,
yes it did success boot back into the system but still my network is still missing.
and he says restore with efs backup but he didnt attach the file to download the efs backup, how can i continue that step?
so i skip that step and just went to reflash it with stock firmware and the problem came again, it stuck in bootloop.
with efs broken ,
anyone here can share your efs backup ?
please i need it
im using samsung note 8 n950f XSP Singapore region
will appreciate your help a lot. thanks a lot
....................
_______________________________________________
Model: SM-G973F [Beyond1LTE]
One UI: v4.1
Android: v12
Baseband: G973FXXSGHWB3
Build: G973FXXSGHWC1
Security Patch: 01 March 2023
Bootloader: Unlocked
(Verified through "Developer Options"
--> 'OEM Unlocked - On' (Greyed out)
_______________________________________________
I am having trouble flashing a Recovery file on this Galaxy S10.
I used Odin v3.13.3 and v3.14.1 ,
and in both times, Odin detects the phone is connected
but when I tried to flash the
• recovery.tar (in "AP")
• vbmeta.tar (in "CP")
Odin does not show that it flashed any of the files,
ie. there is no progress.
I'm waiting for about 1+ minutes, with no activity to show flashing is in progress.
Should it take longer than that?
I have also tried to patch the recovery through Magisk,
ie. after installing Magisk.apk on the phone,
and I directly patch the recovery.img file through Magisk.
Then, tried flashing this patched recovery.tar through Odin,
and there's still no progress in Odin to show me it's flashing.
I've figured out my problem.
I was able to flash the recovery file successfully today.
The solution was that the filename MUST be named exactly:
--> recovery.img (inside recovery.tar )
It must be spelt exactly that way: " recovery . img "
I only renamed my .tar file, as " recovery "
So, everyone ... don't repeat my mistake !
I have a weird issue now, on my S10 [Beyond1LTE].
I installed TWRP recovery and a LineageOS-based ROM,
and it was working fine for a few hours.
Through the ROM, I clicked to reboot to recovery,
and then, now my phone is in some kind of bootloop.
It does not go into recovery either.
I simply cannot get the phone to enter Recovery,
so I need help with this now.
Is it true that if the "USB Debugging"
in 'Developers Options' is switched on,
then I cannot enter the Recovery mode ?
Anyone got any tips or tricks, on how to get the S10 phone,
to enter into "Download" mode ?
Whatever I do, the phone just goes straight to booting ROM
(which itself does not load & hangs),
so I am trying to get into 'Download' mode,
to flash a new recovery, etc... and try again.