Database Info

[Q] Bootloop, Rom Manager, no restore possible

Can be closed!
Oh man, I read the warning too late.
I had a few issues installing Rayman's 4.2 on my TF101 with clockworkrecovery v5.x (Error was not able to open /cache/recovery/** or so. Shouldn' t matter anymore).
Call it stupidness, I thought using the actual cwm version would solve my problem.
As you can see, it did not.
I flashed v.8, the addons and the gapps. No errormessage (did not get any with the older version either).
But it is stuck in a bootloop.
Not too stupid, I did a backup before - sad but true I can't use it. (E:unknown volume for path[/sdcard/]\\E:Can`t mount /sdcard)
Of course I am not able to flash any other rom from internal sdcard. (not even think about external sd!)
I can push a rom to sdcard via adb push, but can`t use it (>choose zip from sdcard \\ E:unknown volume for path[/sdcard/]\\E: Can`t mount /sdcard/) and after reboot the rom dissapears.
Pushing to /data/media is not possible, as media does not exist.
Fastboot seems not to be a possibility, as I can`t boot in bootloader mode... (but tell me, if I am wrong!)
So if anybody knows a solution - I would be so happy!
Update 1:
I followed these instructions:
www tabletroms.com /forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
I installed Nvflash on my linux pc.
APX mode works, I just had to do what people told me to. (Press Vol UP(!) and Power Button)
Connect via USB.
Then run sudo ./download.sh
Everything looks fine, but then again: An error occurs:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Update 2:
I tried another version. For some reason, my TF is not WW, as I thought than US...
Everything is fine, I am happy again. Maybe it helps anybody? And if not - I had my xda rubberduck.

[Q] Galaxy S3 Soft Bricked? & no access to E: or Internal or extSD cards

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.

coolpad f1 not opening

Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :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 tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .

peej2014 said:
Hello guys . After a restart of my coolpad f1 8297w my phone was in bootloop . I entered in recovery mode and this message appeared :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 tried to use Sp flashtools and even that it was successful the phone does not open at all anymore .. Any ideas ? Thank you .
Click to expand...
Click to collapse
I have that phone and had the same problem. Re-format the cache partition to fix the recovery. And then reflash a stable rom.
---------- Post added at 12:42 ---------- Previous post was at 11:44 ----------
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

How can you un brick if it wont powrr on? I'm letting mine charge, it was gave by a friend. Id like to get it running..

Samsung Galaxy S8 reboot loop

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

PC won't recognize phone/TWRP stopped working

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.