SM-T550 Reboot problem, E: signature verification failure, unknown volume /sbfs - Android Q&A, Help & Troubleshooting

Hi!
I am working with a brand new Samsung Tab A 9.7" SM-T550. The first thing I did was root the device using Ashyx's instructions and files.
(http://forum.xda-developers.com/android/development/root-samsung-galaxy-tab-9-7-sm-t550-t3126827)
This seemed to go fine and root was verified, however while running the verification program the device spontaneously rebooted. As I put the device into service, I noted this happened several more times - perhaps once per hour of use or more.
A search of XDA and the internet in general suggested that I do a factory reset and / or wipe the cache. I booted into recovery and performed a factory reset. I do not recall if there were any errors at this time. Putting the device back into service it seemed as though the problem was fixed, however this lasted less than 1 day and the spontaneous reboots returned.
At this point, I attempted another factory reset and noted this error and this output:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sbfs...
E: unknown volume for path [/sbfs]
E: unknown volume "/sbfs"
-- Set Factory Reset done...
-- Copying media files...
-- preload checkin...
Data wipe complete.
I attempted the factory reset again with the same result.
In an attempt to restore whatever is missing and causing this error, and perhaps causing my reboot problem (a stretch, but admittedly I'm in over my head and just guessing at this point), I decided to flash the Stock recovery.
I booted into download mode and, using Odin with the stock recovery which was provided in Ashyx's original post in the AP field, I flashed.
I again attempted the factory reset to see if it eliminated the error (unknown volume "/sbfs"). It did not. I then attempted to wipe the cache and found the following errors and output:
E: Table length: 170
E: Verify signature...
E: signature verification is successful.
dm-verity verification failed...
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
So questions:
Having flashed the stock recovery, I have lost root, right?
Any thoughts on what these errors mean, if they should be of concern or how to remedy them?
Any thoughts on if the autoreboot problem is related to the errors, and / or how I might fix the original problem of rebooting?
Thanks in advance!
Reid

Related

[Q] Stock recovery wipe data vs. CWM recovery wipe data

Hi guys,
A quick question.. I had some issues after installing Batista 0.5 ICS, meaning that in CWM Recovery, when I tried to wipe data/factory reset i got "Error mounting /sdcard/.android_secure". So I flashed stock LPQ, and went back in Recovery, and tried agan the wipe data/factory reset, and it only displayed "Formatting Complete".
Now my question is, does CWM wipe data does something more than stock recovery wipe data?
If not, can you guys help me to stop receiving that error message in CWM?
Thanks alot for your help!
Cheers
Talbred said:
Hi guys,
A quick question.. I had some issues after installing Batista 0.5 ICS, meaning that in CWM Recovery, when I tried to wipe data/factory reset i got "Error mounting /sdcard/.android_secure". So I flashed stock LPQ, and went back in Recovery, and tried agan the wipe data/factory reset, and it only displayed "Formatting Complete".
Now my question is, does CWM wipe data does something more than stock recovery wipe data?
If not, can you guys help me to stop receiving that error message in CWM?
Thanks alot for your help!
Cheers
Click to expand...
Click to collapse
NO its the same .
CWM gives additional wipe and format options .
Error message could be wrong /faulty firmware flash or likewise wrong CWM .
Flash rom again .
Basics of CWM are of course in the stickies .
jje
JJEgan said:
NO its the same .
CWM gives additional wipe and format options .
Error message could be wrong /faulty firmware flash or likewise wrong CWM .
Flash rom again .
Basics of CWM are of course in the stickies .
jje
Click to expand...
Click to collapse
Thanks JJE! I've tried all manner of CWM installs. Even went back to 2.3.6 KL1, so that i could install its respective CF Root kernel (along with an older version of CWM). But still the same issue appears. However, i found a "recovery kernel", that i think could help with my issue, but i'm not sure if i should flash it, since LPQ is 4.0.3 and that kernel says it's 4.0.2 (gt-i9100_clockworkmod-recovery_4.0.0.2.tar).
Is that safe to flash over 4.0.3 LPQ?
Thanks again!
Anyone? Am I alone in my little thread?
Echo, echo, echo...
You should be able to flash a 4.0.2 kernel over 4.0.3 no problems. Obviously backup first (Nandroid backup, Titanium backup, etc, etc). If something weird like the phone not booting happens, you could try flashing the original kernel again & see if you get CWM back & then restore your backup. Or at worst you might need to flash a stock rom in Odin, CFRoot again then restore your backup.
Obviously if you're having problems like that, as JJE suggested it might be a somehow incomplete flash of the rom in the first instance. It might even be worth trying a clean reinstall of the rom. Have you asked in the thread devoted to the rom if other users have had the same problem ?
Talbred said:
Thanks JJE! I've tried all manner of CWM installs. Even went back to 2.3.6 KL1, so that i could install its respective CF Root kernel (along with an older version of CWM). But still the same issue appears. However, i found a "recovery kernel", that i think could help with my issue, but i'm not sure if i should flash it, since LPQ is 4.0.3 and that kernel says it's 4.0.2 (gt-i9100_clockworkmod-recovery_4.0.0.2.tar).
Is that safe to flash over 4.0.3 LPQ?
Thanks again!
Click to expand...
Click to collapse
On which Firmaware are you now?
as you told in your first post "So I flashed stock LPQ, and went back in Recovery, and tried agan the wipe data/factory reset, and it only displayed "Formatting Complete".
that is what actually required to happen " "Formatting Complete". because it will not take more time since it is fresh rom there is nothing to format any user data..
when is your error reappearing?
Thanks Mistah,
I did try Odin installing the stock LPQ and then CF Root > error message. Then I tried Odin installing 2.3.6 KL1 and then CF Root > error message. However, in stock recovery, i didn't get any error message. It says the formatting is complete, so that must mean that it was able to format succesfully. In CWM recovery, however, if i try to wipe data, i get the "Error mounting /sdcard/.android_secure" message. "Skipping format" and so on..
What do you mean by a clean install?
Thanks Zaheed,
The error comes after i flash CF Root (on either LPQ ICS, or KL1 GB), and from CWM recovery i select wipe data/factory reset.
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
skipping format...
Data wipe complete.
In Show Log (from CWM Recovery) it says the following:
Formatting /sd-ext
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
W:Failed to mount /dev/block/mmcblk1p1 (No such file or directory)
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Now I'm on stock LPQ downloaded from sammobile, the Open Europe version.
Any thoughts?
Thanks again for your time, guys!
By 'clean' install I mean format cache, data, system, & sd card then do an Odin install.
Talbred said:
Thanks Mistah,
I did try Odin installing the stock LPQ and then CF Root > error message. Then I tried Odin installing 2.3.6 KL1 and then CF Root > error message. However, in stock recovery, i didn't get any error message. It says the formatting is complete, so that must mean that it was able to format succesfully. In CWM recovery, however, if i try to wipe data, i get the "Error mounting /sdcard/.android_secure" message. "Skipping format" and so on..
What do you mean by a clean install?
Thanks Zaheed,
The error comes after i flash CF Root (on either LPQ ICS, or KL1 GB), and from CWM recovery i select wipe data/factory reset.
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
skipping format...
Data wipe complete.
In Show Log (from CWM Recovery) it says the following:
Formatting /sd-ext
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
W:Failed to mount /dev/block/mmcblk1p1 (No such file or directory)
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Now I'm on stock LPQ downloaded from sammobile, the Open Europe version.
Any thoughts?
Thanks again for your time, guys!
Click to expand...
Click to collapse
I think you dont want to worry about this error, after this wipe are you able to boot into the ROM? were your all apps and user data wiped? then no need to worry...
once again make sure are you selecting the correct matching CF-root for your ROM..
another option : I tried before when I got an error in my CWM was, I downloaded ROM manager (i did not concern to donate the silly bucks to Koush) and flashed the latest touch recovery (note: this will work only with ROM manager, not with CWM Manager)
and selected reboot into CWM from Rom Manager, then it will temporerly flash the touch recovery on your recovery partition, all options in that was working like a charm,
But when you select reboot into from anywhere else, or with Vol-up+Home+power you will be booted into your current custom recovery which was flashed along with the kernel.
regards
When i wipe data/factory reset from stock recovery, the image of Android comes up and that blue interrupted line at the bottom, and yes, the apps and settings are reset. However, in CWM recovery, when i wipe data/factory reset, that image of Android is somehow corrupted, with 3 blue interrupted lines showing up, but no animation. Even so, the apps and settings are reset.
So i'm thinking it has to do with recovery partition.
Anyway, I'll try your suggestion later on, as i'm at work now.
Thanks again, Zaheed! Guys..
Much appreciated!

[Q] Stuck booting, several partition table IO errors

Let me start by saying that I'm fairly certain this isn't due to a bad flash, since I haven't flashed anything or updated anything on my phone for MONTHS. The last flashable zip I've got on my SD card is for NC5D, so I'm 95% positive that is where I stopped...
I had a meeting this morning, and, when it was over, I checked my phone to see if I had any missed texts, emails, etc. When I looked, it was in the process of rebooting. I didn't really think much of it, other than to note it was odd. I let it do its thing, and checked again in a couple minutes. It was still booting. Getting slightly concerned, I placed the phone on my desk and watched it. It seemed to be perpetually stuck booting. (I let it sit for about fifteen minutes, just to see, and it stayed on the boot animation.)
My first attempt was to hold in the power button, and force it to start booting from scratch. This resulted in no change, just hung during boot.
Next, I tried pulling the battery. Upon re-inserting it, and powering on, the phone was, once again, stuck booting.
I booted into recovery (TWRP 2.7.0.1), and thought I would do a wipe to fix it. Since I didn't really have anything I needed to keep, I did a standard wipe (Dalvik, Cache, and Data).
It gave me the following error text:
Code:
Updating partition details...
E:error opening '/data/system/procstats'
E:error: I/O error
E:error opening '/data/system/usagestats'
E:error: I/O error
E:error opening '/data/system/ifw'
E:error: I/O error
E:error opening '/data/system/users'
E:error: Not a directory
E:Unable to mount '/usbstorage'
Full SELinux support is present.
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Wiping data without wiping /data/media ...
E:Error opening '/data/system/procstats'
Done.
Formatting Cache using make_ext4fs function.
Updating partition details...
E:error opening '/data/system/procstats'
E:error: I/O error
E:error opening '/data/system/usagestats'
E:error: I/O error
E:error opening '/data/system/ifw'
E:error: I/O error
E:error opening '/data/system/users'
E:error: Not a directory
E:Unable to mount '/usbstorage'
Hoping it wasn't totally hosed, I did a reboot.
It played the startup sound (I hadn't noticed this on any of the other boot attempts, but that may have been due to the case being on the phone), and started the boot animation.
I let it sit.
And sit.
And sit.
No change in status ever happened, the phone just kept the boot animation going.
I can successfully get into both download mode and recovery, so I'm thinking I'm not completely screwed, but I have no idea where to proceed next...
Can I just flash my phone through the successive iterations of release, up to current? (If so, would there happen to be a list of stock ROMs somewhere that I can use as a starting point?)
Or are the I/O errors a sign of an absolutely dead phone?
I posted this in the Sprint section, since that's the phone I have, but if I am more likely to get a solution over in the general Note 3 area, I am willing to move / repost...
Thanks for reading, and any suggestions are welcome!
hey jus a thought can you try 2 flash the twrp recovery or wateva recovery and when it finish pull battery
and then put it back and then boot to recoevery if you can do that you should get a memory card and load it from there?
you shuld be able to flash a rom on top of that and then start over. :fingers-crossed:
That reply, while not the exact solution, pointed me in the correct track...
I already had TWRP, and tried re-flashing my current ROM, but had no success there.
I was able, however, to ODIN a newer ROM, and a newer TWRP, and that seems to have fixed it.
Thanks!

Samsung GALAXY Ace GT-S5830M Bootloop

Good afternoon, guys.
I'm writing here because I'm completely desperate. Yesterday I tried to update a Galaxy Ace GT-S5830M using a custom ROM. Sadly, I forgot to install the CWM first, and of course, the installation was aborted in the process. After that, each time I entered to the STOCK recovery, it said "E: failed to mount /system (invalid argument)".
I tried to install the CWM, apparently in a successful way but it didn't stay there, I mean, when I reboot the phone I end in the STOCK recovery. The thing is, after "installing" the CWM, I tried to wipe it all, but I got some issues:
1) When doing the dalvik cache wipe I got this: E: unknown volume for path [/sd-ext]
2) Trying format/system I got "Error while mounting /system!" "Skipping format" or something like that.
If I try to reset factory from the STOCK recovery I get "E:format_volume: rfs format failed on /dev/stl11"
I also tried to install a STOCK ROM through ODIN (I used 1.85, 1.87 a 3.07 without any luck) but sometimes I get stuck in "SetupConnection", in other cases the process ends failing while writing the BcmBoot.img (Complete(Write) operation failed), and the likes.
And adb doesn't recognize the cell phone at all.
Do you have any idea or suggestion? I tried it all but I just can't make the cell phone go ahead. By the way, KIES don't recognize the cell phone, don't know if that can change it all.
PS: I can "install" a ROM while playing around in the CWM. It apparently installs correctly but then, after rebooting, I get stuck in the "SAMSUNG GALAXY Ace ..." screen.
Please, help.

TWRP Wiped Everything :(

EDIT
I woke up and did exact the same thing as I was doing yesterday. It worked. I don't know how or why, but it worked.
Now I'm stuck on "Android initializing apps" screen. Maybe soon I'll get it to work xD
---------------------------------------------------------------
EDIT 2
All was needed to do, was boot the phone without charge cable pluged-in.
It's aaaaaallll fine now รต/
---------------------------------------------------------------
So... As the title says. By mistake, I wiped everything: Dalvik Cache, System, Data, Internal Storage, Cache, Micro SD.
Yea, everything. Total newbie.
My device is an Moto E XT1025
I'm trying to fix it for couple of hours now. But simply can't.
I have an .zip with ROM in the SD, tried to install/flash and give me this errors (in sequence):
- no MD5 file found;
- could not detect filesystem~;
- failed to mount~;
- patching system image unconditional;
- failed to update system image;
- error executing updater binary in zip;
Then I tried to adb sideload, so I have this error:
- no MD5 file found.
And it stops here.
The ROM I tried was: https://forum.xda-developers.com/devdb/project/dl/?id=14329
Now all my phone can do is: stuck at bootloader screen and enter in recovery/twrp mode.
I don't know what I can do now
Brother
Everything is possible in fastboot...
https://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
U can this just use xt1025 firmware replace with xt1022

Stock rom loaded and getting E: Failed to /misc partition Please help

Hi all,
I have Samsung A5 2016 and I tried to update my phone through latest Naugat official firmware using by Odin however it turned out something wrong. My first problem is when I enter the boot screen, ''installing update'' screen pops up and then ''no comment screen'' afterward. Second problem is that boot screen shows an error says E: failed to find /misc partition. I've read tons of post however I couldn't figure this out.
I would greatly appreciate it if you could help me.
Thank you & Best!
Hi
My message has been moved here
https://forum.xda-developers.com/samsung-a-series/help/sm-a510f-rom-stock-entering-mode-t3653121
Thanks
Anybody know how to deal with the E: failed to find /misc partition? I saw this come up on my SM-J700T after I tried to flash TWRP. The flash passed but TWRP was not successfully installed. Probably because I did not prevent reboot and reboot in a proper way . But now I have been all around the barn trying to recover and eventually get twrp and root. I flashed several stock roms with lots of errors and finally got the phone running with Nougat 7.1.1 but the E: failed to find /misc partition error remained on the phone all the while. I was unable to use Odin to re-partition due to errors and have been trying to figure out how to use adb, also with errors (yesterday I launch "abd devices" and get a listing for my device (I think- it is not properly identified) and it lists the device properly, today it lists the same device as unauthorized. So what I really would like to do is completely wipe the phone and start fresh but I only have access to the stock bootloader which allows cache wipe and data wipe- factory reset, which does not wipe the Missing partition. So 1)completely wipe phone 2)install twrp 3)root

Categories

Resources