Database Users

[Q] [i9505] Possibly bricked or TWRP messed it up [SOLVED!]

I've had problems with my phone for a while now, no stable roms or mods, phone doesn't wake up from deep sleep, lagg....
So I got in to recovery mode (latest TWRP) a few hours ago and I got asked for a password? :S didn't know that TWRP had a protection function.. I pressed BACK and that was that, I got in to the menu and pressed INSTALL but the SDCARD was empty?
Using the filemanager in TWRP the internal SDCARD was still empty, but the microsd worked fine.
After rebooting the phone I got stuck on the sgs4 screen, so the rom didn't boot.
I went back to recovery and wiped everything possible and formatted the sdcard, afterward I installed a rom and rebooted.
Still the same problem, got stuck on the sgs4 screen.
In TWRP the sdcard was still empty. So I downloaded a odin flashable rom and flashed the phone through odin but got stuck at the same place.
I now have the stock recovery and when selecting "apply update from external storage", I get the error message:
"E:failed to mount /sdcard (No such file or directory)"
Is there any function in a TWRP/CWM or modded recovery that can fix the internal sdcard?
Or perhaps repartition everything?
Just to let everyone know, the flashing in odin and TWRP worked as usual, so the system/data etc partition as fine.
Guess it's the sdcard partition that's corrupted OR if TWRP somehow locked the sdcard because I didn't enter a password?
I could be wrong but then I'm completely clueless.
Appreciate some help, thanks!
EDIT: [SOLUTION]
Since there is no way to use adb in recoverymode or downloadmode (I wasn't able to), you need to use odin.
1. Enter download mode and flash a clean rom through odin.
2. Enter download mode again and flash TWRP through odin.
3. Wipe DATA through TWRP and reboot.
4. Factory Reset through TWRP and reboot.
5. Done.

Seems like this is the wrong place to ask, but I think I found the problem.
It was TWRP with their "password protection" that cause the problem.
Downgrading to other versions wont help as it did for others with the transformer pad.
I did a search for "TWRP PASSWORD" and it looks like TWRP has a bug.
This is what I get in TWRP:
E:Mount: Unable to find partition for path '/sdcard'
EUnMount: Unable to find partition for path '/sdcard'
This is definitely the last time I'll use TWRP.
When flashing CWM, I'm unable to boot into recovery, only works with TWRP..

I'll keep posting here until I solve this if anyone get the same problem.
http://forum.xda-developers.com/showpost.php?p=44007919&postcount=1
In the link above, someone manage to fix their phone with the same problem I have, even though it's the nexus7.
So what I've learned is that I shouldn't let TWRP root my phone.
I need a system.img file, could it be just the system parititon? Don't know how to get that file, so could use some help.
EDIT:
I'm going to unpack a odin package, found a system.img.ext4 in there, guess that wont help so have to find one with stock filesystem.

Help needed - i9505g soft-brick/recovery boot-loop

This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!

Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks

I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?

same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J

Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.

It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje

umount of /system failed; so such volume

Hello,
I'm trying to install a custom rom on my note 4.
I rooted successfully, and installed TWRP through flashify.
First issue I ran into is that the phone got stuck in a bootloop after installing TWRP. All fine I said, it's cool since I want to flash a ROM anyway.
I downloaded the ROM for my device, and after I clicked factory reset and tried installing the ROM, I got the error
Code:
unmount of /system failed; so such volume
I looked around online, some posts said that it's fine, the ROM will install anyways, but that's not the case. The ROM didn't install (the process is finishing way too quickly), and I'm still stuck at bootloops.
I'm running TWRP 3.0.2.0 (newest version), android 5.1.1, on my note 4 N910H.
I have access to TWRP and to download mode, and I can move files between the PC and my phone using an external memory card.
PLEASE HELP ME :crying:

Rom.zip not installing on any twrp version

So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.

ap29600 said:
So i was swapping roms: i booted into twrp, cleared cache and data and flashed my rom ( ResurrectionRemix-M-v5.6.0-20151213-wt88047.zip ) and Gapps.
i noticed flashing RR took just a minute and returned this message:
"unmount of /system failed; no such volume
script succeeded: result was [0.200000]"
after that the Gapps package flashed with no problem, but my phone does not boot properly.
Edit: i also tried different twrp versions, but i got the same result with each of them
It does still boot to fastboot, but i wasn't able to get into android.
i read something about cf.lumen drivers causing this kind of error while swapping roms, but i don't know if they were there in the first place or how to uninstall them.
Click to expand...
Click to collapse
Good night, try to flash miui. Then install twrp 3-1 and ROM. But first go to the Lineageos tag and download the modem and flash. Then try ROM again.

I had MIUI installed before the Rom flash, and i was using fastboot ti boot into twrp without actually flashing it.
I eventually solved my issue by flashing a different rom, so i think the one i was using was corrupted or Just bugged.
Thanks for the support.