Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Contruk27 said:
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
wrong place, sorry
move to q&a or delete please
Click to expand...
Click to collapse
You might also be able to get it working by flashing the sweetrom like people with the HongKong note 3 had to do to go to KK rom...
Worth a shot if you try everything else and aren't getting anywhere but you will need to be rooted to flash a custom rom...
Related
Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
demLong said:
Hi everyone,
I'm a noob here but I read the guidelines
You're the only who can save me tonight (it's 3 a.m. here and sry for my bad english).
I rooted my Galaxy S4 (international version - Snap 600 - i9505) and I flashed the latest nightly of cyanogenmod. I started my device and, after 4-5 minutes, the rom started. I felt immediately disappointed, it's a pre-alfa version and I installed it just to try it.
So, I decided to install the Pure Google Rom with Android 4.3 (http://forum.xda-developers.com/showthread.php?t=2341026).
I rebooted my device, but for some reasons (I got a small crash, because I failed, removing my battery during the boot animation), my phone is now stucked at the title screen.
I can see just "Samsung Galaxy S4 - GT_i9505" on an infinite black screen. I'm so sad, I wish to solve this problem...
P.S. I tried to reboot in recovery mode: almost the 70% of the times I tried, it failed entering recovery mode. The only time it entered recovery, I wiped everything, but nothing seems to change.
Please help :\
Click to expand...
Click to collapse
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Thx
tingtan said:
Usually the international version is i9500 running on Exynos Octa core. Are you sure you loaded the right firmware?
If you have flashed the custom recovery (CWM, Philz, TWRP), you can try to load different firmware (copy to SD card first). Worst case, you can use Odin to flash. Unless it is hardware problem, it is not easy to brick the phone.
Click to expand...
Click to collapse
Thank you, I flashed the philz touch version for i9505 and it works flawlessly. I installed the Google Stock Rom and it's working. I'll update tomorrow if I got crashes or black screens.
Thank you so much tingtan
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340
So I've been having this strange issue for a year now, where I want to upgrade my SM-T530 (Tab4 10.1 wifi) to the stock Lolipop (5.0.whatever) ROM in order to get the damn kernel updated so I can access all these wonderful custom ROMs (Stuck on CM 12 atm...).
But whenever I flash a stock ROM for my model, it seems to freeze the screen after the boatloader. As in, everything seems to be working, sound and touchscreen, it just doesn't update/refresh the screen. Basically, the same behaviour as described in this post.
So here's the steps I took, in the hope that anyone can point me in the right direction:
Boot tablet in recovery (TWRP 3.0.1, in this case) and wipe Dalvik, /data, /cache, /system, basically everything)
Reboot tablet into bootloader/download mode
Using Odin 3.11.1, flash T530XXU1BOL2_T530PHN1BOE1_HOME.tar.md5 (Found here, which should be the correct ROM for my model (Bought in the Netherlands, but I have no idea where you folks are pulling this T530XX stuff from, it's nowhere to be found on the back))
Reboot tablet
After the 4th step, the tablet will be unresponsive for ~10 minutes (I think it's doing the whole "upgrading apps" thing that follows a new installation). After that, when I hit a certain area of the screen, I can hear the regular Android touchresponse, raising the volume also give the normal beeps and pushing the power button plays the "turning off screen" sound, but the screen stays active, showing the Samsung Galaxy Tab4 boot logo.
Soooo... Anyone care to take a guess what I'm doing wrong?
Personally, I think it might have to do with flashing the incorrect stock ROM, but for the life of me, I can't find out which T530-code I have. I've been flashing different ROMs, but no luck so far...
As for troubleshooting I've already tried:
The above procedure, afterwards flashed TWRP via Odin and flashed a custom ROM via TWRP. Same effect.
Variations of the above procedure, where I keep wiping the tablet after each step
Different custom ROMs
Ugh, nevermind.
Turns out I have an UK tablet (BTU-T530XXU1BOG2). After flashing a dozen or so ROMs, this one did the trick.
Oh well, problem solved :good:
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?