OK so im fairly new to the tab, but I have an SGS that ive flashed a million times over. However, I guess on the tab its slightly different. I wanted to get it so that it could work with phone calls, and so I flashed the russian ROM first. Now when I go to boot up it just gets stuck on the Samsung Galaxy Tab screen and nothing happens. I started looking through the forum, and I guess some tabs have the bootloader locked so that only signed roms can go through, and I didnt see that till after i flashed So is there anything I can do now to get it to work again? Anytime i try to flash odin fails at factoryfs.rfs and it goes into the exclamation mark screen.
Hi, I've found many similar/related threads and have spent a lot of time reading and re-reading, but with those attempts I haven't had success so I'm posting this before I get into a worse situation.
On the AT&T Note 3, I rooted with kingo and was following this method http://forum.xda-developers.com/showthread.php?t=2577273 - after which the phone only booted up to the samsung logo with the unlocked padlock icon and the word custom.
I am able to get into recover and download menu's, have followed similar threads for the 900a on various steps to try to get it back using Odin with the MI9 and MJ5 firmwares, it was at MGL when i had the first issue and then starting looking for ways to get back. When i try with MJ5 via odin, the process resets successfully, the device reboots but still just comes back to the samsung logo with the unlocked padlock icon and the word custom. in Odin the status turns green and says Pass.
After this point i am still able to get into recovery menu and download menu, but just can't get by the custom padlock screen.
I have also tried flashing to MI9 in odin but that one fails, with the sbl1 fused 2 > binary 1 message.
Any thoughts on what I should try (or what to not try) next?
Anyone had success in this scenario with either fixing it forward or trying to go back another firmware?
Updated 4/16/2014
Hi just wanted to share how I was able to get back up and running thanks to another forum member @coreygunz23 reaching out to me.
I was able to use this firmware http://forum.xda-developers.com/showthread.php?t=2619941
Here was my experience :
- Flashed it,
- passed in Odin,
- phone auto rebooted came back up to the same custom unlocked logo screen then automatically showed the recovery message,
- then restarted again and came up with the animated samsung logo with sound,
- then came up to att logo and sat there for a good while
- eventually launched the getting started wizard and i've been good so far..
Hey, so i tried rooting my galaxy tab s2 810(first time doing this stuff), i tried flashing a custom kernel, and then used an autoroot. it didn't seem like it was working, and now im afraid that i have gotten myself in more trouble that i thought was possible.. when i try to boot my device it stays on the boot screen saying either '' Kernel is not seandroid enforcing'' or ''recovery is not seandroid enforcing''. i cannot enter the recovery menu by pressing Power+home+vol up.
however i can enter the download section...
i have tried a bunc of different fixes, and i dont know if all i did was make my problem worse... i could really use some help.
Its exactly as title states i was messing with stuff i had no business messing with and have gotten myself stuck in a boot loop where i cant access the recover options it just reads failed to mount like five times then does this process 3 times and resets it does still let me in download mode and ive been trying to flash back to Stock OS but it just keeps failing... Any advice on this matter would be wonderful and very much appreciated..
Also added info i was using Odin when i found myself in this pickle and i have a Tmobile Galaxy Note 8 (SM-N950U)
When i try to flash back to Stock i get (SW REV Check Fail : [ablFused 2> Binary 1)
I feel the need to make this post as I have yet to find anyone else with the exact same issue as me, however here is the details:
I am running a Samsung Galaxy Note 8 SM-N950U from AT&T
Rooted with SamFAIL one month ago without any issues.
Context:
Yesterday when I turned on my phone for no obvious reason it just got stuck into a boot loop (the one where it stays on the Samsung logo forever. Did the obvious steps with no effect.
Afterwards, I tried to follow the SamFAIL root guide from the start to end just to see if it would fix it (I was desperate). Everything went fine, however, when it booted up and whenever it does boot up it starts black then it flashes the recovery mode screen for half a second (I'd post an image, but I am not allowed to, just search up, "recovery mode note 8" and look at the images with the blue background and android mascot), displays some white text on the black screen for perhaps a second, goes black and repeats this. I am able to enter download mode and upload mode, but whenever I try booting into the actual phone this happens.
Strange problem huh? Any hope for me, or do I have a brick now? It's been looping this process for the past 20 minutes now. For now, my plan is to try flashing the stock firmware with Odin. (My internet is slow so it will likely take all day for that file to download.
flash csc in odin. your cache got corrupted
me2151 said:
flash csc in odin. your cache got corrupted
Click to expand...
Click to collapse
Thank you for the response, any suggestion as to where I can get the latest csc for my model?
https://www.androidfilehost.com/?fid=962021903579483124
Okay, that fixed that issue, however now my phone is doing the same thing again but getting stuck on the flashing Samsung logo screen. What now?
EDIT: NEVERMIND, EVERYTHING WORKS NOW. Thank you so much <3
Hi, I am running a Samsung Galaxy Note 8 SM-N950U from Verizon and im currently styck in a boot loop as well. I can still enter download mode and stuff so im trying to flash back to stock firmware to see if thatll help at all. Can someone please help me find the right file to do so, as i dont wanna cause any further issues here lol.
go sammobile / updato - Search there
It has the whole repository of FW for devices