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!
Related
I unlocked the boot loader using the easy unlocker (version 4.2) And everything went smoothly. I then pushed Clockworkmod onto it as well. Booted fine, no problems.
I put the .zip for Neutrino onto the internal storage of the phone, then installed via zip. The install went smoothly, but when I went to exit and reboot I get the following error:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I powered the phone off, and when I try to turn it on, the phone gets stuck at the Motorola screen. All it displays is "Unlocked" and hangs there until I pull the battery. I can access recovery, fastboot, etc. But, the phone won't load past there.
Any help would be greatly appreciated.
I started with a newly fixed Atrix, with 2.3.6. Unlocked fine, no problems. Also, sorry for posting here, and not the development thread, but I don't yet have permissions.
Have a great day.
EDIT: Tried doing a factory reset, wiping the cache, and reinstalling. Still getting the errors that I posted above, and it still won't boot.
EDIT 2: I'm allowed to post in the developers forum now. If I get a fix over there I'll update over here for anyone who may run into my problem in the future!
pink401k said:
I unlocked the boot loader using the easy unlocker (version 4.2) And everything went smoothly. I then pushed Clockworkmod onto it as well. Booted fine, no problems.
I put the .zip for Neutrino onto the internal storage of the phone, then installed via zip. The install went smoothly, but when I went to exit and reboot I get the following error:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I powered the phone off, and when I try to turn it on, the phone gets stuck at the Motorola screen. All it displays is "Unlocked" and hangs there until I pull the battery. I can access recovery, fastboot, etc. But, the phone won't load past there.
Any help would be greatly appreciated.
I started with a newly fixed Atrix, with 2.3.6. Unlocked fine, no problems. Also, sorry for posting here, and not the development thread, but I don't yet have permissions.
Have a great day.
EDIT: Tried doing a factory reset, wiping the cache, and reinstalling. Still getting the errors that I posted above, and it still won't boot.
EDIT 2: I'm allowed to post in the developers forum now. If I get a fix over there I'll update over here for anyone who may run into my problem in the future!
Click to expand...
Click to collapse
Do not post on the Development thread, this is the right place. Development is for Development of ROMs, Kernels and Modifications that is why is named so, not for asking questions. try rebooting into recovery, mounts and storage, format cache, format data, format system, wipe data/factory reset, then install/flash the ROM.
So, once my Rezound started prompting me for the OTA update, I decided I would unfreeze the apps I had so it could update no problem. Attempting to do so with Gemini App Manager was a failure as at first it couldn't get root and then after I updated it I can no longer un-freeze apps without 'donating'. So I just decided to let my phone do it's thing and see what would happen. It downloads, when the phone resets it comes up to System Recovery. Down at the bottom is displays the following :
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
wrong taskid 221384E:Error in /cache/fumo/OTAPkg.zip
(Status 1)
Installation aborted.
If I reboot the system the phone works fine until it starts trying to force me to do the update again, then it's the same thing again. How can I resolve this and just install the damn update?
ebrammer252 said:
So, once my Rezound started prompting me for the OTA update, I decided I would unfreeze the apps I had so it could update no problem. Attempting to do so with Gemini App Manager was a failure as at first it couldn't get root and then after I updated it I can no longer un-freeze apps without 'donating'. So I just decided to let my phone do it's thing and see what would happen. It downloads, when the phone resets it comes up to System Recovery. Down at the bottom is displays the following :
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
wrong taskid 221384E:Error in /cache/fumo/OTAPkg.zip
(Status 1)
Installation aborted.
If I reboot the system the phone works fine until it starts trying to force me to do the update again, then it's the same thing again. How can I resolve this and just install the damn update?
Click to expand...
Click to collapse
Well, I factory reset the phone, re-rooted it. I have root again, all apps are intact, but the update still will not take. Same issue, same error message.
The OTA will not flash unless your are completely stock. You have a custom recovery, so it isn't going to work unless you flash the stock recovery and are COMPLETELY stock.
I also had a similar issue. I had an issue with update 8 working for it had some random restarts and WiFi didn't work but update 6 was fine. Regardless what you do for this, and you're in recovery, simply go to flash a zip file and navigate to the ota-update folder and then downloads and you can select your zip file there. Just confirm it with the power button and away the install goes. Hopefully this helps and its your issue.
Sent from my ADR6425LVW using xda app-developers app
kpritchard said:
I also had a similar issue. I had an issue with update 8 working for it had some random restarts and WiFi didn't work but update 6 was fine. Regardless what you do for this, and you're in recovery, simply go to flash a zip file and navigate to the ota-update folder and then downloads and you can select your zip file there. Just confirm it with the power button and away the install goes. Hopefully this helps and its your issue.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Well, I think I bricked it. I had a firmware.zip and I installed it and now it's dead.
Booting up normally it just hangs at the 4G LTE screen and never goes anywhere.
Booting into recovery everything seems normal until I try to do anything.
For instance :
Wipe -> Wipe ALL data/factory reset =
Formatting DATA...
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid Argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE...
Skipping format of /sd-ext.
Userdata wipe complete!
Many of the other "wipe commands" yield the same result.
I downloaded PH98IMG_ICS_3.14.605.12.zip from shipped-roms.com and tried to install it,
I get :
Install.....
Finding......
Opening.......
E:Can't open /sdcard/PH98IMG.zip
(bad)
Installation aborted.
What the hell did I do wrong and how do I fix it?
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
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.
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