The phone (VZ Galaxy S8+) is not rooted and on stock ROM.
The phone is having issues during calls this past week, so I decided to take a look if it has anything to do with the install failure of the July 2018 (that was pulled) update.
I did an OTA update in July 2018, it downloaded... but the install failed.
In going to recovery, I cleared cache > turned off phone > return to recovery > it started to install the update. Then, the screen turned blue and said, "no command".
The recovery message states as follows:
#fail to open recovery_cause(NO such file or directory)
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
Supported API: 3
#MANUAL MODE v.1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory}
E:[libfs_mgr]Error fetching verity device number: No such device or address
E:[libfs_mgr]Couldn't get verity device number!
lE:[libfs_mgr]Error removing device mapping: No such device or address
Successfully verified dmverity hash tree
Click to expand...
Click to collapse
What does this all mean?
Did you get a answer
sunNsnow said:
The phone (VZ Galaxy S8+) is not rooted and on stock ROM.
The phone is having issues during calls this past week, so I decided to take a look if it has anything to do with the install failure of the July 2018 (that was pulled) update.
I did an OTA update in July 2018, it downloaded... but the install failed.
In going to recovery, I cleared cache > turned off phone > return to recovery > it started to install the update. Then, the screen turned blue and said, "no command".
The recovery message states as follows:
What does this all mean?
Click to expand...
Click to collapse
Did you ever get this figured out asking because mines says the same
I got rid of the phone and replaced it with the Google version of the Pixel 2 XL.
The S8+ got too temperamental and unreliable for work.
Related
One time, when I tried an update an error occured, the phone reboot and said: "the device has been reported to the initial configuration". Now there is no notification to update. I have to do it manually.
What is the problem ?
i did a factory reset but it doesn't prompt me again if i want to update.
I did this tuto: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=14962 to receive OTA
but nothing changes and i'm now onto 2.20.40.97 but each time i have to update manually.
And now when i go into recovery it show me: "installing system update..." and few seconds later it show me error (with the android logo)..
Can you help me ?
up please help me.
I succeed to (re) update to .97 with recovery: i put the firmware onto sd and internal root storage named mofd_sdupdate.zip and it update BUT I don't know if i can receive updtaes notifications...
That error logo is not a problem as long as the device wasn't updating. Also, I never received any notifications for OTA except once.
Hi,
I had previously rooted my device: Android 1 - Micromax Canvas A1. I also had installed CWM on my device. For some reason, I have removed recovery mode and unrooted my device. My device had Marshmallow with February patch.
But whenever I try to get OTA it doesn't get succesfull. Whenever I try to go into recovery mode it shows my dead android with warning sign saying "No command!". When I try to press "Power Key + Volume UP" I get error message saying "Error in @/cache/recovery/block.map (status 7)".
Reading few posts, I understood that some system files got corrupted and I won't get OTA updates. So downloaded one Zip files and I flashed all the *.img files (recovery, system, boot, etc). Now my system had Android 5.1. But I'm getting same error while going into recovery mode.
I also tried to use "Smart Phone Flash Tool " but whenever I click "Download button" it stucks in the same state showing no progress.
I have read many posts and tried many things but I'm stuck at this stage. Can anybody help me out of this problem?
Update: Though I wasn't able to get into recovery mode directly. I (major) updated my device from KitKat to Marshmallow. Then, minor updates also went fine. Now, I'm on latest April 2016 update. Still, when I try to get into recovery mode, I still see "No Command". But after pressing Volume Up + Power button I get the recovery option. Is this default behavior.
ghsatpute said:
Hi,
I had previously rooted my device: Android 1 - Micromax Canvas A1. I also had installed CWM on my device. For some reason, I have removed recovery mode and unrooted my device. My device had Marshmallow with February patch.
But whenever I try to get OTA it doesn't get succesfull. Whenever I try to go into recovery mode it shows my dead android with warning sign saying "No command!". When I try to press "Power Key + Volume UP" I get error message saying "Error in @/cache/recovery/block.map (status 7)".
Reading few posts, I understood that some system files got corrupted and I won't get OTA updates. So downloaded one Zip files and I flashed all the *.img files (recovery, system, boot, etc). Now my system had Android 5.1. But I'm getting same error while going into recovery mode.
I also tried to use "Smart Phone Flash Tool " but whenever I click "Download button" it stucks in the same state showing no progress.
I have read many posts and tried many things but I'm stuck at this stage. Can anybody help me out of this problem?
Update: Though I wasn't able to get into recovery mode directly. I (major) updated my device from KitKat to Marshmallow. Then, minor updates also went fine. Now, I'm on latest April 2016 update. Still, when I try to get into recovery mode, I still see "No Command". But after pressing Volume Up + Power button I get the recovery option. Is this default behavior.
Click to expand...
Click to collapse
What is your current build Number??
Sent from my Micromax AQ4501 using XDA-Developers mobile app
Too long to read full story
Hello everybody,
I kind of lost here.
For some reason my rooted 3XL is still stuck on the January patch level. Whenever I check for an update Android tells me that my system is already up to date.
Also after a "checkin" (*#*#2432546#*#*)
No difference wheter I'm checking on Wifi or on cellular (Vodafone).
I can't sideload either, since I'm experiencing this strange "can't read file" bug within adb.
For this I already tried all know solutions (manually patching adb.exe to be "LARGEADDRESSAWARE", using the patch tool, using a x64 version of adb)
"Install update from SDcard" also does not work in recovery, since it tells me that it couldn't mount the storage.
Any other ideas? I mean the whole problem starts with the fact that I'm not offered any updates from within Android. That would be the preferred solution.
Flash full March factory image?
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
z3dulik said:
Hello,
I have a pixel 2 xl, with android 10 february 2020 patch. Device was rooted with magisk than removed it but somehow I lost the option to OTA update from settings and some apps still saying root detected.
Now I tried to add android 11 and all stuck.
I have secure boot yes and device state unlocked.
When I go to recovery on top shows R/RPP4.200409.015/6455311
Wehn I try to apply update from adb with "adb sideload taimen-rpp4.200409.015-factory-dca8dad0.zip" nothing happens, it's stuck to verifying update package...
If I remove cable usb-c to usb-c shows signature verification failed.
tried with:
taimen-rpp4.200409.015-factory-dca8dad0.zip
taimen-ota-qq1a.200205.002-1c132203.zip
Any help please?
Click to expand...
Click to collapse
Just nuke it with flash-all.bat May factory image. You can boot TWRP and flash the R OTA as well.
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
When I turn it on i have an alert "your device is corrupt."
z3dulik said:
I did with flash-all.bat too, goes to the end with some missing files in the log, but still not working.
TWRP when I try to flash .img - returns no such partition
Click to expand...
Click to collapse
I would extract the factory image, fastboot erase user data then update bootloader, radio and vendor on both slots(reboot bootloader after each flash) then flash-all or fastboot update with the Taimen file that contains the vendor image
It's a bit longer of a process but it works.
Tried too, same thing. Looks like it's something related to recovery. Can't write to
z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
Swap slots and flash to both
Sent from my Pixel 4 XL using Tapatalk
Managed to flash twrp on boot_a
z3dulik said:
Tried too, same thing. Looks like it's something related to recovery. Can't write to
Click to expand...
Click to collapse
I've got out of this before
Boot TWRP
Format data
Pop in an otg with stock OTA hit mount go back and hit mount then it'll appear as auto-1 in TWRP and flash the OTA
It works if you need to go back to previous month or Android version. Just make sure both slots are the same after you boot
OTG not recognised
/vendor error
also the factory images are missing from here? https://developers.google.com/android/images
I can see only OTA
fixed with factory android 10 april. thanks all for help
Hi!
So it appears I have soft-bricked my phone. At least I hope this is a soft one, but looks harder and harder with every minute.
What I did:
- I have an A5 2017 initially running Android 8.0.0 build A520FXXUGCTKA.
My plan was to install Lineage for MicroG on it. I followed the instructions on the Lineage website, encountered immediately an absence of OEM unlock button, solved it with flashing latest stock ROM with CSE which also reset the device and doing the date/time trick (+- 8 days), after which OEM unlock appeared and I had both it and USB debugging on.
So I proceeded to install TWRP and was able to successfully boot into it, after which I followed the next fatal steps:
Now tap Wipe. <<did this
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage. <<did this, and it suddenly gave me a bunch of errors about being "unable to mount /data"
I disliked this and decided that I have to solve this before proceeding to step 3 of the guide. So I found somewhere a solution to go to Advanced Wipe, select the Data partition and repair it, which I did, but after this step I think it recommended to reboot the phone, which I unfortunately did... and I was stuck in Samsung boot with only the logo loading. I panicked and immediately tried to go back to recovery, which stopped the loop and game me the red message Only officially released binaries are allowed to be flashed.
So the status of the phone right now is:
- I cannot go into recovery mode anymore. It gives the red message about official binaries.
- Phone doesn't load into system either. It again gives the red message.
- I can go into Download mode and see the following status:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-A520F
CURRENT BINARY: CUSTOM
( I did not actually go to step 3 of the guide and try to upload the custom ROM. But I suspect this is because it now sees the ROM as changed/damaged)
SYSTEM STATUS: Official
RMM STATE: Prenormal
(This line was absent when I managed to turn on the OEM unlock finally. Now it's back)
FRP LOCK: OFF
Secure Download: Enabled
- I cannot upload ROMs via Odin anymore. The device isn't seen by it with Download mode like before. The drivers were installed by me previously and I was able to upload via Odin. I tried to reinstall them with zadig, but instead of 2 entried named Gadget Serial like before, zadig now only sees one Gadget serial and one Unknown device #1.
I tried to flash ROM in parts to the partitions directly (binaries, img) via Heimdall (using phone.pit mapping I downloaded a bit earlier via Heimdall). Heimdall said that it was a success on each download part, but also wrote 0% near the progress and it seems that it did nothing.
To me, phone looks now as if it sees its ROM as damaged, but ignores any attempts to get anything on it anymore. Which is logical because it seems to have either locked itself in a new state or restored to the state where the USB debugging and OEM unlock are not turned on. And I can't obviously get the system to load to turn them on.
Maybe somebody encountered a similar situation and knows how to get it out of this state or what this might be?