Hi. My Nexus 7 (wifi) has LRX22G android version. Recently my tablet freezed so I held power button for few seconds to force reboot. After boot i saw decryption failed (picture in attachments in rar file) . After I clicked reset tablet it booted in recovery mode with no command image. I chose wipe data/factory reset. It showed wipe complete but after reboot android stuck on boot loop with no command image (cant show due to prevent spam system on xda and attachments size limit :/ I will send link on private message) . I force shut down and after boot it again shows decryption failed. I suppose that i need to flash rom (I bootloader locked, without root) but i cant enable usb debugging, because i cant get out from this "decrytpion failed window"(I want flash to KTU84P version if possible because LRX22G works slooowly :/). I hope that i showed my problem clearly(I dont speak englisch very well). Thanks for help in advance
Solved .
Tablet came back from service. Mainboard was broken. Topic to close .
Hey hey . I have a quite a lot of problems with my phone and i'm scared I might "fry" it .
I think the internal storage partitions are screwed , i can't flash update.zip from stock in twrp 3.1.0-2 / revolution ( thoes only 2 work ) and i get this error :
32k crc checked failure
E: Unknow comand (errno)
E: Unknow comand (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/update.zip'
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...done"
When I try to flash update_data.zip for my model , its flashing with no error ( result [ ] ) , only failed to mount /vendor , /product at the end.
I managed to flash AOSPA rom , but with results [1.00000] , and its stuck on "your phone is booting now.."
Please any sugesstion or idea how i could fix this it's warmly welcomed .
How to fix: 1. Create in sd card folder: dload
2. Extract update.zip(Use marshmallow ota update zip not Nougat!!!!)
3. Copy UPDATE.app to dload folder
4. When phone is off, hold all 3 buttons: volume +, volume -, and power button
5. After that proccess finishes, power off phone and hold volume + and power button at the same time.
6. Now select factory reset!
7. Done!!!!
bokspro said:
How to fix: 1. Create in sd card folder: dload
2. Extract update.zip(Use marshmallow ota update zip not Nougat!!!!)
3. Copy UPDATE.app to dload folder
4. When phone is off, hold all 3 buttons: volume +, volume -, and power button
5. After that proccess finishes, power off phone and hold volume + and power button at the same time.
6. Now select factory reset!
7. Done!!!!
Click to expand...
Click to collapse
Thank you for this reply . I tried it 5 days ago but no luck .
I sent the phone into service , and they fixed it . They sent it today back with a courier , maybe tommorrow i'm gonna have it back , hopefully .
Thanks again for the reply ,hope it helps some xda users who also bricked they'r phones like me .
Cheers
It sounds like your OEMINFO has a problem or there was a "virus" in the system that corrupted the drive.
Anyway, i'm glad the service fixed your phone
Same thing has happened to my phone deleted OS by mistake
Edit : just sent it off with warranty hopefully back in week or 2
Please i want your help with my phone '' Y5 2017 ''
i Flashed TWRP 3.1.1 by fastboot and then rooted my device , installed magisk after that i uninstalled it to install xposedframework and when i tried to reboot the device it get me '' system isn't responding '' then i factory reset to flash custom rom ' CrDroid_b2 ' now after it finished always turns me into recovery when i reboot and give me ' internal storage 0mg '
please fix it,
Thanks
Hi
I have a Samsung Galaxy Note 3 (SM-N9005) flashed in Cyanogenmod ages ago. I'd like to reflash it with a new more recent ROM*as right now in CyanogenMod phone is more or less in a bootloop (most of time rebooting just few seconds/minutes after having finished the boot).
Unhappy I'm unable to find out which recovery was installed. I tried to keep physical Vol+ or Vol- butoon pushed while booting but it makes nothing. At boot I just get briefly displayed:
HTML:
Kernel is not SEandroid enforcing
Set Warranty bit: kernel
Is it safe to flash it with TWRP considering it as still a fresh device with original rom ? or danger ?
Thanks
You are booting to download mode try recovery mode.
Vol + Home button and power button
Vol- Home button +power button
As it does not have original firmware .
I would flash latest stock rom through Odin then flash required TWRP.
JJEgan said:
You are booting to download mode try recovery mode.
Vol + Home button and power button
Vol- Home button +power button
Click to expand...
Click to collapse
Thanks a lot, was not sure shortcut to use So I could access the recovery mode !
JJEgan said:
As it does not have original firmware .
I would flash latest stock rom through Odin then flash required TWRP.
Click to expand...
Click to collapse
Well it had at first but as Samsung very quickly stopped any updates I had switched it to CyanogenMod. I have succeeded to install on it the latest TWRP: 2.6.3.7 but each time I try to flash a ROM*(tried with two different ROm just to be sure)*I get the same errors in TWRP. For info files to flash on the SD*Card.
Code:
Updating partition details....
E:Unable to mount '/usbstorage'
Installing '/external_sd/lineage-16.0-20181010-
Checking for MD5*file...
Skipping MD5 check: no MD5*file found
Warning: No file_contexts
E3004: This package is for device: hlte, hltespr
E: unknown command [log]
E:Error executing updater binary in zip '/exter
Error flashing zip '/external_sd/lineage-16.0-2
Updating partition details...
E:Unable to mount '/usbstorage'
I double-checked on original sticker for manufacturer on device and it's well labelled as SM-N9005 so it's the HTLE version no ?
Update: I have tested with a ROM with Android 7.1.2 in it and install in twrp is going fine including gapps but at reboot it get stuck on Samsung Galaxy Note 3 and that's it and it's indicated at top of screen in yellow: Set Warranty bit: kernel
Not sure what's the problem there ?
Thanks for help,
Vincèn
and that's it and it's indicated at top of screen in yellow: Set Warranty bit: kernel
Correct unless its all stock kernel rom and recovery .
:Error executing updater binary in zip '/exter
Error flashing zip
Zip faulty or flashing tool wrong version
JJEgan said:
:Error executing updater binary in zip '/exter
Error flashing zip
Zip faulty or flashing tool wrong version
Click to expand...
Click to collapse
Well in fact the problem was the bootloader that needed update first to accept android so recent
Thanks for help
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