Database Users

[Q] [Wind] I tried flashing FoxHound ROM, and soft-bricked my phone. Any fixes?

Alright... where to begin? Lets start at what happened around yesterday. Prior to the whole weekend, I had CyanogenMod 10.1 installed on my rooted S4. Come Friday, I start to miss some of the stock Samsung features such as Air Gestures, Smart Stay, the stock Samsung camera, and all that. So, I install WanamLite (a custom rom) on my phone. It's good and all but for some reason, the Smart Stay isn't working. To fix this, I go online and start digging; I find people saying "yo, revert back to the original firmware and re-install the Rom, that should fix your LTE problem." I think to myself, "maybe this could help me too." And that's exactly what I do. I go online to SamMobile and download this ROM (http://www.sammobile.com/firmwares/?page=1&model=SGH-M919V&pcode=0#firmware). It installs with Odin and I was able to get back to the Stock Samsung firmware. I then proceed with my plan and install WanamLite; that also worked. So I'm all happy and stuff 'cause Smart Stay finally works but, shortly after fiddling with the re-stocked device, I get bored again. So, I start searching the forums for another rom to replace WanamLite (it was a good rom, but I wanted to try something else before settling down on it).
I find this ROM in the XDA-Developers S4 forum: http://forum.xda-developers.com/showthread.php?t=2303239. I try installing it; it works fine. But then, I notice that half my SD card is used up. So, I go into TWRP and click on Format Data (I'm not too sure about the name, I had CWM prior to the re-installation of Samsung stock firmware). After resetting the Data, I boot back into the phone and notice that the default layout is Easy Mode. (On the bright side, I freed 4 GB from my SD card). Easy Mode's incredibly annoying, so I wrestle with the phone for a while to change the launcher to Nova launcher, but to no avail. In the end, I decide to reflash the FoxHound ROM. I place the rom on my phone and boot into TWRP. That's where the problem comes. I selected: wipe cache, wipe delvic cache, wipe data. Then I wiped the cache and data, flashed the rom and, after that is when the phone started refusing boot up. From then on, it just displayed Samsung Galaxy S4 logo on the screen whenever I tried to start it.
What I tried to fix the issue: Re-installing the stock samsung firmware. (I think I ended up screwing up the phone even more with this. Before, I had TWRP installed but I couldn't boot into it, now I don't have any custom recovery installed and I still can't boot into the phone).
I can access the Download Mode and use Odin. I cannot boot into the recovery. When I hold Volume Up + Power + Home, it just says recovery in blue above the logo, and then, the phone reboots.
So, any ideas on how to fix it?
TL;DR: Tried installing FoxHound Rom. I wiped Delvic Cache, Cache, and Data, and after flashing the rom, the phone refused to boot up; it gets stuck on the Samsung logo. Before flashing, I did Format Data. After being unable to boot into the phone, I tried to flash the Stock Samsung Firmware on my S4. Nothing worked. Any ideas on how I should proceed?

splitinferno said:
So, any ideas on how to fix it?
Click to expand...
Click to collapse
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"

psycovirus said:
Try using Odin mode to install Stock Samsung Firmware...
If it doesn't work,
Install Samsung Kies, put Phone into Odin mode, connect the USB and let KIES reinstall the whole firmware... Go to "Tools" -> "Emergency Firmware Recovery"
Click to expand...
Click to collapse
I've already tried flashing the Stock Samsung Firmware using Odin, it didn't work. Also, I'm having no luck with Kies; it won't connect. Any other suggestions? :/
EDIT 1: Okay, so here's the deal right now: I was able to flash TWRP using ODIN. This granted me access to my recovery, somehow. So right now, I have the FoxHound_GearEngine0.2 ROM installation files on my SD card and I am booted into the recovery. What should I do? Should I try flashing again? For now, I'll just wait for a response.
EDIT 2: Out of curiosity and impatience, I tried flashing FoxHound but got an error:
Updating Partition Details
E: unable to mount data
E: unable to mount internal storage
TWRP v. 2.5.0.3

Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else

maazali said:
Go into the advanced menu in TWRP and try to mount data / internal storage. If you can't, then you're back to odin unless someone can find out something else
Click to expand...
Click to collapse
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.

UNBRICKED
splitinferno said:
I tried to; it didn't work. I also tried clockworkmod recovery. That recovery said it said that the data was already mounted. For some reason, now the phone is stuck in a bootloop. On the bright side, I can freely access my recovery (although I can't do much in it). Should I try flashing other stock roms?
EDIT: Flashing the stock rom brought it back to the state it was in earlier. So now, it just hangs on the Samsung Galaxy S4 screen and no longer reboots continuously. I'm thinking of downloading other stock roms and flashing those.
Click to expand...
Click to collapse
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.

Hahah nice job
Sent from my GT-I9505 using xda premium

splitinferno said:
Alright, after struggling around with the device, I was able to unbrick it. I downloaded the stock ROM from samfirmware and flashed it using odin. After flashing it, it would stay on the Samsung Galaxy S4 logo and that's it and I wasn't able to boot into the recovery either. So, I flashed TWRP using odin and download mode, and found I was able to boot into recovery again. Screwing around with the recovery, I couldn't manage to do much so I decided to re-flash the stock firmware. After re-flashing, I had the same problem. This time, I tried accessing the stock recovery. I got access, which was something I couldn't get before. After getting access, I did Factory Reset/Data (it was something along those lines) and did a wipe cache. After wiping cache, the phone rebooted and, much to my delight, it was unbricked. After going through this, I think I might just like chill for like a month, or a year now with stock... .__.
Click to expand...
Click to collapse
Next time don't wipe data in custom recovery because it will corrupt your data which would most probably end with not booting past the Samsung logo, if you want to wipe in a custom recovery for now you have to manually wipe system, cache and dalvik cache located in mounts in cwm recovery (not sure where to find it in twrp).
You should read a little before messing with things in recovery.

Ahahah that's funny because something similar happened to me. And I was going to suggest doing a factory reset via recovery because that's how I resolved my problem, then I see you did just that! (Y)
Sent from my GT-I9500

[Q] How do I restore device after failed OTA 5.0.1 update on rooted N4?

Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...

May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.

Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?

Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).

AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.

Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?

[Q] [PLZ HELP] Note 4 Won't Reset (Not-Rooted)

hello there, I have a N910F and I have tried resetting it through the settings, as it goes into recovery it says 'installing system update' then just shows up the recovery without actually wiping the phone. when I do wipe the data it completes fine but when I click onto reboot system now an error comes up saying failed to mount data and something in brackets which I cant read because t reboots too quickly. the phone starts up with all my data still in tact.
I have also tried to flash the latest Lollipop version for the device but it as soon as I click start the flash fails. this is confusing me because this phone is not rooted. I even tried to flash TWRP but the stock recovery still seems to show up.
very puzzled would like to know if anyone can help me would appreciate it a lot! :good:

CM 13 - Stuck in Recovery Mode after update

Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?

Do u have a back up to your stock Rom or any other Rom aside from CM?

Flash back to stock and start over with twrp, cm, and gapps.

I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.

My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.

So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?

Flashing Problems

Hi I have a SM-N910F model which is proving extremely difficult to flash. I firstly flashed the latest Marshmallow UK BTU firmware on it which resulted in a boot loop. I cleared cache partition and wiped data/factory reset in the stock recovery (and TWRM recovery) but this did not fix the problem. So I flashed the phone again and this time it was stuck in a boot loop with the text "recovering booting..." at the top left. Tried the same as before and still didnt fix it.
So I then tried a different stock rom - Lollipop UK BTU firmware. This gave me the exact same problems as before. However on a few occasions, I also got an error on the recovery screen saying cache could not be mounted. I cleared the cache partition, tried reformatting cache using TWRM but none of this worked. Eventually I reflashed and it went away but the boot loop doesnt go.
Lastly I tried an even older firmware - Kitkat UK BTU firmware. This again gave me a boot loop problem. It also kept displaying the cannot mount cache error as well. I tried using PIT file to repartition the device and eventually the error went but the device would still be on boot loop. However on two occasions the phone did go past the Samsung logo and show the first setup screen (where you select initial settings like Wifi etc). After like 10-15 seconds it would just switch off and then go back into boot loop. I havent managed to get to the first setup screen again.
I have tried flashing with various different Odin versions but still no luck.
I feel like I have exhausted my options and not sure what to do. Do you think I should try a custom rom? If so, for the sake of getting it to start, which is a good lightweight rom?
Does anyone know what I can do to make these infinite boot loops and/or "cannot mount cache" error go away?

Anyone? I could really do with some help..