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
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
SebringTech said:
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
Click to expand...
Click to collapse
Have you tried wiping dalvik and cache through recovery? If that doesn't help maybe do a factory reset before restoring the factory image?
Sent from my SM-T330 using Tapatalk
Edit: I think this might be what you need
http://forum.xda-developers.com/showthread.php?t=3176668
I tried to wipe cache and dalvik - still gets stuck at the Samsung logo... Tried to do a factory reset from TWRP and after rebooting from recovery it continues to get stuck. I'll try flashing the kernel but I don't understand why that would have gotten messed with from flashing the recovery and installing the SuperSU part.
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
SebringTech said:
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
Click to expand...
Click to collapse
You're very welcome. Good luck.
Sent from my SM-T330 using Tapatalk
So after exhausting all options, I turn to the experts for help. I have a friend in the UK, who wanted to downgrade his Galaxy s5 g900f 5.0 to 4.4. He's familiar enough with basic odin/recovery use, but only vaguely.
He wanred to downgrade, so I had him flash TWRP 2.8.7.0 via Odin. All went well. I then had him make a full back up, boot, system, data etc. He has no sd card, so after the back up I had him move his entire internal storage (except the back up) to his pc. Then we downloaded OmegaDroid v13 (4.4) for the g900f. Flashing went as expected to start, did full wipe, flashed the zip (aroma installer). The two options for kernel choice with this ROM or stock kernel or Omega kernel. Flashing with stock kernel sends the phone into an infinite bootloop, flashing with the omega kernel never boots at all (black screen with blue led on, I had him leave it like this for an hour to make sure). So I told him to restore his back up until we can find another 4.4 to try. Well restore fails every time.
No problem, I thought, we can mount usb or use adb sideload. So I had him download CM 11. Had him boot to recovery and mount usb while connected to pc. The box wont check, just no response. So I got him to download adb and drivers, had him verify his isntall. The problem here is adb devices lists no device. Odin however can communicate with it.
Am I missing something. Is there a way to turn on USB debugging from twrp or the terminal in twrp? Or is there an odin flashable rooted 4.4 rom available for the g900f that anyone is aware of. My google searches have come up with no answers to these. 4.4 roms in general for this device are few and far between. Ive told him he may have no choice but to go and get a sd card, as this would make life much easier, but it still bothers me that adb cant see the device at all, yet odin can.
Thanks for help in advance.
Let me start by saying I've never modded a phone before so I'm extremely new. I followed a few how-to's on these forums (by rovo89) as well as videos on how to enable xposed installer on my Galaxy s5 G900i. I rooted it successfully, installed TWRP without any problems all using Odin, but then flashed the incorrect arm file, and when I restarted my phone it was stuck on the Samsung bootloop. I didnt download the uninstaller and my phone wasn't able to connect to Odin at that point. I did have a backup file however. I restored to my latest backup however my phone was still unable to boot, even after wiping cache and data files. In a mad rush, i did a complete factory reset and wiped off all of the files including the system, and obviously now when I try and boot i get the warning "No OS installed! are you sure you want to reboot?
Any help would be greatly appreciated, is there any way to remedy this situation or have I screwed up too bad. Apologies for my stupidity.
Edit: I should note that when my phone is in bootloop, it is recognised by Odin (Added!), however while it is in TWRP, it is not recognised (Removed!).
Download official rom for your device and flash it via odin
Hi,
I had a quick battery drainage problem twice on my Tab which got fixed for about a week using the calibration procedure posted on this forum.
Still I factory reset my Tab using TWRP default wipe thinking it will resolve the issue permanently. After reboot, the screen just gets stuck on "Just a sec..." screen.
Now, i found two posts where reflashing with Odin fixed the issue. I did not turn on usb debugging as i was just doing a factory reset. So, i dont know if i can reflash with usb debugging 'off'.
Also, is there any other advanced wipe i can do or anything that will fix this issue without a need to reflash.
Thank you.
Samsung Galaxy Tab 4 10.1" SM-T530NU
Official Android Lollipop 5.0.2
Rooted using Odin and TWRP 3.0.0-0
usb debugging has nothing to do with download mode.... its just while ROM itself is on....
you can odin flash stock firmware as long as you get to download mode
did you flash SU again before reboot? try that