Database Develop

Impossible to flash?

Hi, I need help with a (possibly) soft bricked phone. It boots, yet it reboot itself once it tries to read the multimedia files in the internal storage. The owner is a co-worker so I really don't know how or what could possibly trigger this behavior (a virus perhaps?). The device is not rooted, even if I set usb debugging it just keep rebooting and losing all configuration. Uninstalled apps respawn again once it reboots. I tried to flash it with many Odin versions to a proper stock rom, but when the device reboots all the files remain the same, as if nothing were ever done. I tried wiping everything from recovery mode, didn't work either. Whenever I enter recovery mode it updates some files and says it can't gain access to CSC. I'm not an expert on repairing phones so I'm already out of options, any suggestion would be appreciated.
Edit: Android version is 2.3

Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.

Cassiusss said:
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Click to expand...
Click to collapse
Didn't work either. All files are still there after rebooting. CSC still fails to load in recovery.

I saw some people with this issue in other android devices, it seems the problem is a corrupted internal memory (nothing can be erased or written). I may just give up

Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.

Cassiusss said:
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Click to expand...
Click to collapse
I can't install custom recoveries, it doesn't recognize external storage and not even Odin can rewrite the recovery.

If you're sure that you can't install TWRP with Odin then I don't know how you could solve your problem, sorry. :/

@Cassiusss Hey Bro,
I have been using epirex cm13 builds
but later these days, i didnt used it much as i was flashing around on my 1+3.
Now, i cant boot in recovery and bootloader, whenever i reboot to recovery or bootloader it boots back to rom.
i try adb commands and flashing recoveries through app but didnt work.
Also I tried odin flash it but as it cant boot in bootloader, how can i revert back.
I am using 12 june build Cm13.
Please help.

Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?

Cassiusss said:
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Click to expand...
Click to collapse
I tried ur mentioned app but it again takes 1-2 secs and boots to system.
I also extracted out boot.img from cm13 and flashed it through rashr but after flashing it again booted to system.
Also tried to factory reset from phone but surprisingly it again didnt show anything and booted to system.
Can You tell me any method to HARD RESET or format its system partition so i can odin it ezily.

I think that formatting system will not bring back recovery or download mode.
What's important is to gain access to download mode (because without it you can't use Odin).
Are you sure that booting your phone while pressing "Volume down" + "Home" + "Power ON" keys is ineffective?
Maybe you'll need an USB JIG to force the download mode...

I guess your device memory is broken. Because my friend's ace3 had the same problem with you, and the service center said that the emmc had been broken. So no hope at all

Odin flash twrp boot loop

I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.

jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?

fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.

jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.

jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.

jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.

the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20

Software update failed with odin (firmware flashing issue)?

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.

SAMSUNG NOTE 8 N950F (XSP - Singapore Region) WONT BOOT INTO SYSTEM!! HELP!!

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

....................

Having 'Trouble' Flashing Recovery -- SM-G973F [ Beyond1LTE ]

_______________________________________________
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.