Database Users

Help me please (Bootloop/Bricked)(Samsung Galaxy J5, SM-500FN)

So I was going about doing my business, I rooted and flashed a custom XPosed framework build and after that my device got stuck in a TRWP bootloop, it will not go boot into anything but that.
(When rebooting from TRWP it says "No OS installed, are you sure you want to reboot?"
And when I try to flash a custom/stock ROM it gives me the error "E: Error executing updater binary in zip '/external_sd/ROMNAME.zip' "
Details:
Samsung Galaxy J5, SM-500FN, TWRP v2.8.7.0, Odin cannot recognize the phone while in TRWP which is the only possible state and the PC cannot access it's files, I need to use SD cards to get files on it.
Thanks a LOT to anyone helping me.

What do you mean TWRP is the only possible state? To use odin you need to boot to the USB Download Mode. To do this you need to take off the battery, put it in again, and then do Vol down + Home + Power.

You can flash stock firmware via odin, http://www.sammobile.com/firmwares/
Or flash Nick Verse's TWRP
http://forum.xda-developers.com/android/development/recovery-samsung-galaxy-j5-t3338869
And CM 12.1
http://forum.xda-developers.com/android/development/rom-cyanogenmod-samsung-galaxy-j5-t3404569

Downgrade to Marshmallow

Hello Friends, I just upgraded my Zenfone 3 ze520kl to Nougat, but i prefer Marshmallow i try from recovery mode to flash Marshmallow, it shows error and the installation aborted. Can any one help . Thanks.

What error does it show?

Error with some numbers follows by 'install aborted'. I unable remember the error numbers. I did three times all the time with same remark.Thanks.

That's not very helpful. Can you try it again and tell us exactly what it says?

Hi,
I downgraded a few days ago, here's an overview of the steps.
WARNING, this requires a factory reset so you will lose the data on the phone, so make sure you have backups before you proceed. You do this at your own risk and I am not responsible for any damages.
I assume you have adb / drivers all configured and know to how use them.
1) download firmware file http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip and save to SD card / insert card in phone.
2) download recovery and boot img files for Z017D_WW_13.20.10.152
- https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
- under the folder Z017D_WW_13.20.10.152
3) Go to fastboot mode (power + vol up)
- flash recovery.img (command: fastboot flash recovery recovery.img)
- flash boot.img (command: fastboot flash boot boot.img)
4) reboot to recovery (power + vol down)
5) install update form micro sd card.
set the file UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip that you saved earlier
6) wipe cache
7) factory reset
If you don't do a factory reset and reboot, Android pretty much crashes on multiple processes on start up, it is unusable.
Regards,
TK

Credit goes to https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524 for laying the foundation.

Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.

Same thing happened to me as well. I just went ahead to flash the RAW file (http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html) and updated the software to the latest marshmallow update, followed by a factory reset.

If we Downgrade
Then we get update in future yes or no??
Sorry for bad English??

Yes.

Hi, thanks for the help. Please answer this:
Do I need to use Recovery and Boot.img the same version of ROM? Why?
Why do I need to install Boot.img?

580 stuck at Downloading...

Hello!
So my 580 (rooted, stock) is stuck in Download mode. This followed a Magisk update and reboot, and it seems like I can't even power the device off - even through TWRP, choosing Power Off reboots it and I'm stuck with Downloading...
Any ideas what to try? Should I reflash the ROM through Odin (which parts?), and if so, what will I lose?
Thanks for listening
PS tried flashing a known good Magisk zip, aborted with:
ERROR: 1 because: "Unable to unpack boot image". Any help greatly appreciated...
PS2: Tried flashing Magisk Uninstaller, interesting: it failed with "Magisk is not installed!".

krakout said:
Hello!
So my 580 (rooted, stock) is stuck in Download mode. This followed a Magisk update and reboot, and it seems like I can't even power the device off - even through TWRP, choosing Power Off reboots it and I'm stuck with Downloading...
Any ideas what to try? Should I reflash the ROM through Odin (which parts?), and if so, what will I lose?
Thanks for listening
PS tried flashing a known good Magisk zip, aborted with:
ERROR: 1 because: "Unable to unpack boot image". Any help greatly appreciated...
PS2: Tried flashing Magisk Uninstaller, interesting: it failed with "Magisk is not installed!".
Click to expand...
Click to collapse
Seems like you've actually wiped the device.
Flash stock firmware with odin and start again.

Not sure how I could've wiped it - I did nothing of the sort that leads to it, like going into settings, recovery or Odin
But in any case, I did have to reflash from start and set up my device again... what a PITA!

Maybe this will help you to fix E: Can't mount EFS(invalid argument) g935f

Hi! my G935F can't boot after a corrupted EFS file was flashed it just said in the recovery e: unable to mount EFS (Invalid argument) I was tired and I have searched on every site but nothing... until the crazyness came to me!
I managed to fix it flashing twrp on odin, then booting on twrp and using the option reboot, then click on reboot on download directly from twrp it will boot on download but there is no text on the download screen, flash EFS with odin http://efs.firmware.ir/sm-g935f/ and wait(use the odin on the page to flash the EFS File), it will fail try again then it will show all the treaths completed (0 succeded/0 Failed) but that doesn't matter then reflash the stock rom using odin, let it reboot and you'll get the "Device does not have DRK" blue screen let it stay a minute then it will boot straight to recovery saying that it updated some files...
after that go to download again and use odin to flash twrp recovery and then reboot on recovery to make it reboot straight to download again, once there flash CF auto root from here https://desktop.firmware.mobi/ and there you go... let it boot it will say "the device is not seandroid enforcing" then it will automatically reboot and it will surpass the samsung logo... my phone is still on 00000000 IMEI but at least it boots...
Hope it works for you, give it a try but I have to tell you am not responsible for any damage to your device.
Tell me in the comments if it worked

Galaxy S8 Stuck on "Powered by Android" Screen After Android 9 Update.

Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.

Try Flash Same Firmware Reigon You have own in prev Version

MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.

hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory

I think you Flash worng Firmware send download mode photo

MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks

same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot

hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard

hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?

Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?

Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
How can I fix this?

Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.

I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.

Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp

techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4

nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts

hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
e: unknown volume for path [/ odm]
e: unknown volume for path [/ vendor]
dm-verity verification failed ...
E: [libfs_mgr] is_dt_compatible (): firmware info was not valid : '/ proc / device-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you