Hello,
Here's what I've been doing. Unlocked my phone and gained root. Then I installed Linage OS 18 using twrp. First startup went fine. Went into settings to confirm I was on Android 11. Then I rebooted my phone just to discover it fails to boot. I get lots of errors on my display. In fact my whole display gets cluttered up by lines of error (see examples below). If I'm doing a normal restart my phone gets stuck in boot loop. I can get it to load up bootloader, but if I choose recovery I just get lots of errors. After several minutes it goes into Linage recovery. I've tried doing a factory reset in Linage recovery, but still these errors show up and it doesn't make a difference. I've tried pretty much everything here without luck. Whatever I do I get these same errors.
Help! By the looks of it I have completely messed up my phone
Example of errors:
E: inotify_add_watch failed: No such file or directory
E: [libfs_mgr] Skipping mounting '/dev/block/bootdevice/by-name/cache'
E: [libfs_mgr] Failed to open '/dev/block/bootdevice/by-name/bache": No such file or directory
E: Failed to mount /cache: No such file or directory
This list goes on and on...
One thing I've learned after over 10 years of HTC phones is they're hardly ever COMPLETELY bricked. Or I'm just that good... I dunno. I've never actually not been able to recover one. So you mentioned it was LOS 18.... Was it a GSI? Because if not, it had to of been a ROM for a different device... And that complicates things. I'm gonna try and help though.
sibbe83 said:
One thing Hello,
Here's what I've been doing. Unlocked my phone and gained root. Then I installed Linage OS 18 using twrp. First startup went fine. Went into settings to confirm I was on Android 11. Then I rebooted my phone just to discover it fails to boot. I get lots of errors on my display. In fact my whole display gets cluttered up by lines of error (see examples below). If I'm doing a normal restart my phone gets stuck in boot loop. I can get it to load up bootloader, but if I choose recovery I just get lots of errors. After several minutes it goes into Linage recovery. I've tried doing a factory reset in Linage recovery, but still these errors show up and it doesn't make a difference. I've tried pretty much everything here without luck. Whatever I do I get these same errors.
Help! By the looks of it I have completely messed up my phone
Example of errors:
E: inotify_add_watch failed: No such file or directory
E: [libfs_mgr] Skipping mounting '/dev/block/bootdevice/by-name/cache'
E: [libfs_mgr] Failed to open '/dev/block/bootdevice/by-name/bache": No such file or directory
E: Failed to mount /cache: No such file or directory
This list goes on and on...
Click to expand...
Click to collapse
Related
Hi guys! I think I need your massive help...
What I did:
S-OFFed my Desire S with alpharevx - no problem
Rooted with Gingerbreak - no problem
Flashed ClockWorkMod Recovery with RomManager - no problem
Flashed Virtuos Unity ROM with ClockWorkMod - no problem
Tried to boot phone after flashing Virtuos Unity ROM - PROBLEM!
Phone stayed at VU bootscreen for about 30 minutes, not responding to anything.
Only thing to do was to remove battery. After that, it hung at HTC Bootlogo (green on white background), nothing happens.
So, I tried to enter CWM to flash my nandroid backup - wouldn´t accept it.
Tried to flash all other ROMs that I found - always error.
Entered CWM to try to wipe partitions.
First screen shows the menu and below that following message:
ClockworkMod Recovery v3.0.2.6
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
I can still use the menu however.
Wipe data/factory reset is no problem
Wipe cache partition is ok, but makes the environment REALLY slow!
Always show errormessage when trying to install ROM, when it is trying to format /system, doesn´t matter if it is custom or my nandroid backup.
Errormessage is: Error formatting /system!
Sometime I had an (Status 1) message when trying to install a custom rom. It says that it is an error in the zip file. However, I tried several with the same result.
So, I thought, "Wrong CWM?". Let´s try 4EXTRecovery instead.
Beginning to flash:
assert failed: write_raw_image(“/tmp/recovery.img, “recovery”)
E:Error in /sdcard/4EXTRecovery_v2.0.2_RC2-saga.zip
(Status 7)
Installation aborted.
There´s no error in the file, I tried to download it from several sources.
I can reach the phone thru ADB and Fastboot. I tried a couple of commands I found on the net to wipe cache but only got an error. Don´t know what to type...
When trying to flash a newer Clockwork Mod Recovery with fastbootcommand, sending the file is OK, but when writing ´recovery´ it hangs, nothing happens for 20 minutes. When unplugging the USB cord I get an error (status read failed (Too many links)).
I also tried to flash my .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img from my nandroidbackup (ex. fastboot flash boot boot.img) with the same results: sending file is ok, when writing the file the phone stops responding until I pull the USB cable, then I get the "Too many links error".
So: Is there anything I can do?
I have all the files .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img on my computer if that is any good.
I can mount and access the sdcard thru ClockworkMod Recovery.
Both HBOOT (Bootloader?), FASTBOOT and CWMrecovery is responding on phone, there is a working link between computer (ADB and FASTBOOT command), however something seems to be broken as it stops responding.
Is there any command I can use? I really don´t know more than the FLASH and WIPE command so maybe i´m missing something?
I appreciate all your input!
Thanks!
kinda looks familiar...
compare your problem to this:
http://forum.xda-developers.com/showthread.php?t=1150917
F**k... Stupid me, I read that post when it was new. However, I didn´t have that problem myself then...
So, is there a command I can execute to see that the eMMC chip is really broken?
As in that thread, point 8, second infoscreen (DS Brick shows). Just to make sure, I think I have a friend that can replace it for me then...
My phone is a Samsung galaxy S3 SCH-S968c, Verizon Networked for Straight Talk. I ran into having my phone stall after the Samsung logos boot up and then the tracfone logo appears and stalls there. The issue started after i tried installing multiple tweeks using a popular app for rooted devices (i cant think of the apps name at the moment). I have a version of CWM on it. After reading threads here in XDA i found that my CWM will not work correctly on this phone. Retired Forum Moderator "edfunkycold" said "It's not really a bug with the recoveries which where modded. It's part of whatever Samsung has done to keep people from rooting and flashing roms." so i downloaded both CWM_mod2.img and TWRP_mod2.img.
So between the soft bricking and the usless cwm i cannot flash anything or access the internal or external sd cards. I tried using ADB and these commands:
adb push .img /sdcard/.img
adb shell
su
dd if=/sdcard/.img of=/dev/block/mmcblk0p18
I just get the Android Debugging Bridge version...............
I also tried other methods found in XDA using ADB.
I tried Samsung Kies, 4 versions of Odin, SkipSoft Android Toolkit and some other java executable program that didnt work.
I can boot into both recovery mode and download mode.
Recovery mode does nothing....
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
E: Can't mount /sdcard
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
.....etc. etc.
In Download mode, Odin recognizes that the phone is connected but when i try loading anything it wont connect. example: trying to load a bootchain file it says:
checking MD5 finished successfully..
Leave CS..
All threads completed. (succeed 0 / fail 0)
Other attempts show the RED FAIL square.
Im having trouble finding the correct Files to Flash. Im guessing the SCH-I535 is the non-straight talk equivalent to my straight talk phone so i have downloaded file: Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip
and Rom: Sons Of Android - cm-10.2-20130928-UNOFFICIAL-jewel.zip
Bottom line is I DONT CARE what version of android (stock or ROM) as long as it's compatible and need the correct flash files necessary. I THINK it originally has jellybean 4.2.2??? PLEASE help. ive been messing with this for 3 weeks now :crying:
Thanks
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
jbaker22 said:
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
Click to expand...
Click to collapse
ADB is not recognizing my phone. Odin still is. I tried to flash recovery with Odin last night. The process completed with success but when i restarted the phone i was not able to gain access back to the recovery. Now I can only get into download mode. Is this why ADB is not working, cuz it has to be in recovery mode?
Also I am confused on how the file structure should be when i put a rom on the sd card. I know they go in the root..... do i just extract them from the ZIP straight over to the SD? Is there a way to convert ZIP files to an Odin flashable file?
FIXED!!!! w/ Straight Talk Stock Firmware SCH-S968C
I FINALLY found a working download link for the correct firmware!!! Thanks to an old post by Kenny1974 who posted the name of the file. I googled it and found only one available!
https://www.dropbox.com/s/j2uc1hkm4...8CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
I Flashed with Odin and Presto!
If this link becomes invalid, p.m. me and i will send you a link or the file.
I have a J7 prime, on7xelte, g610f, oreo 8.1.0, stock firmware, no custom recovery. I wanted to root it and for that wanted to install twrp. I did NOT use Samsung Antiroot Removal Tool, RMM State Bypass zip, No Verify Encrypt zip. I tried to flash it using adb but no matter what it wont detect my phone in recovery/fastboot, only when its on or sideload. On sideload i got an error. So i tried to do it with odin, since odin detects my phone EVEN though windows doesnt. After doing that somehow my system got corrupted. i couldnt mount /data once in twrp and trying to boot it up caused bootloop. i couldnt get it to mount usb either. then i force restarted it into download mode and reinstalled stock firmware, retried the twrp .tar, and failed again. and again. then i saw a video rooting j7 prime with a root file The link to the video:
. the file was for g610fd, i thought the "d" was a typo and flashed it anyway. Now I boot up into the stock recovery with the exact following lines:
Installing system update (loading)
no command (exclamation triangle)
(after a while)
Android recovery
samsung/on7xeltedd/on7xelte
8.10/MIAJQ/G610FDDS1CTE3
user/release-keys
[the regular options here]
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File based OTA
supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
#MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
:/ so apparently at this point, only the volume buttons work. i mean i can only go up and down but not select a thing. its bad. so i tried force rebooting into the download mode. THERE, the VOLUME buttons dont work. means i cant confirm and proceed into the download mode fully. my pc doesnt recognize the device in either states so i cant command in adb. one thing is that even before this error my pc didnt notice my phone in either states. so i might be missing the right drivers. my wire isnt flawed, i have 3 wires. i have hand typed everything here so will be great if you take your precious time to type any advice here for this poor fellow who is scared of losing his only phone.
Hello Guys, Need your help
I have a Samsung Galaxy S8 rebooting after home screen.
When I enter recovery mode, I can see these errors:
# fail to open recover_cause (no such file or directory)
E: uknown volume for path [/odm]
E: uknown volume for path [/vendor]
remove failed dir /system/carrier/ATT/priv-app/AttIqi_ATT (no such file or directory)
cant open directory /system/omc/SUP/etc/sysconfig (no such file or directory)
cant open directory /system/omc/SUP/etc/cid/sysconfig (no such file or directory)
cant open directory /system/omc/SUP/etc/permissions (no such file or directory)
cant open directory /system/omc/SUP/etc/cid/permissions (no such file or directory)
E: [libfs_mgr]is_ft_compatible(): firmware info was not valid
Also, in recovery mode I can see my firmware is G950FXXSBDTJ1 which is related to Germany, as far as I understand
I tried to flash firmware with ODIN, downloaded G950FXXSBDTJ1, used HOME_CSC, but it did not help
Then i Download mode I noticed my Carried ID is XSG which OAE, so I tried OAE firmware, and it did not help either and I can still see G950FXXSBDTJ1 in recovery mode.
What I also noticed is that once ODIN completes my phone starts to update and finishes at 32% and them displays Erasing message
Is there anything I can do with this phone to make it work?
Thank you
From yesterday I'm experiencing this same issue with my s8+ (EU too). For no reason it started to reboot again and again until it "died". When I enter to recovery mode I have exactly the same errors. Now what we have is a pretty looking brick from 4 years ago.
We had the last security patch a few days ago, and I'm starting to connect dots now... It looks bad.
I'm also experiencing the same issue today on my girlfriend's phone. Same errors. This started after a recent update.
It seems Samsung is pushing OS updates that are bricking phones. This is inadmissible!
I am having same problem for 6 months. I think an update did this.
Got the same issue with S8, SM-G950FD
I'm aware of the usual tips for this but nothing seems to be working for me. I currently have three phones (S3 Mini with stock android, OPO and HTC U11 with Lineage). I've just installed the latest Lineage release on my HTC and everything seemed to be working. However, I can no longer boot into recovery. TWRP (from which I've just installed the Lineage update) doesn't show up at all. It just boots into a blackscreen that turns into what seems to be a Lineage recovery with these error messages:
E:inotify_addd_watch failed: No such file or directory
E:[libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/cache'
E:[libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/cache' : No such file or directory
E:[libfs_mgr]Failed to mount /cache: No such file or directory
E:Failed to clear BCB message: failed to open /dev/block/bootdevice&/by-name/misc: No such file or directory
E:inotify_addd_watch failed: No such file or directory
E:[libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/cache'
E:[libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/cache' : No such file or directory
E:[libfs_mgr]Failed to mount /cache: No such file or directory
At this point I'd use ADB to flash TWRP and hope a newer version works but I can't connect my phone to my PC. And I've tried all three phones with different cables with my PC and laptop (both Win10) but not once did a computer even play the "something connected" sound, the USB preferences on every phone are greyed out, and the phones don't show the USB connection notification. I was currently trying to reinstall Magisk but I have to get into the recovery for that (and the Lineage recovery doesn't allow me to flash the .img file edited by the Magisk Manager). I just don't know what I could do to fix this.
Edit: I unfortunately have zero information on why it works now but after rebooting the phone for the 100th time it showed up in adb.