Hello to all. First, thank to the devs for all the fantastic work done, and to all the people willing to check and answer these threads. So down to my problem.
When I first got my S5 (SM-G900F) I immediately rooted with cf-autoroot. Tripped knox but worked well. From there I went on to install Twrp and then CM 11. The bugs drove me off, so I wanted a tw based rom. At the time I chose XtrStoLite (spelling?) And that worked a treat.
So after a while I found alliance rom and thought wow, this is great. So I installed it as per the instructions in the OP. Now we get to problem one: I got stuck at the Samsung boot screen. No boot logo, nothing, no matter what I did, even formatted /system, still nothing. I tried a few suggestions from the extremely helpful dev, @Goldie, none of which worked, such as flashing another rom first, so I tried with cm and slimkat. Didn't work. Tried updating supersu, didn't work. Tried different TWRP version, nothing. Tried Philz. Tried different Kernel with and without SELinux set to permissive and still it would need a battery pull at the Samsung "powered by android" screen.
Okay, last resort, flashed stock for my country (south africa), flashed TWRP, installed towelroot, rooted, flashed newest supersu, installed busybox and retried. This time something changed. Instead of freezing at the first Samsung screen, it now showed "Set Warranty Bit: kernel" in yellow at the top. Then the screen would go black, phone would vibrate twice and then reboot. So now I had a boot loop.
It was suggested to try omega, to see what happens. Well, it works fine. To date I've tried 5 different working roms. Was told to flash via omega, so I did, but same issue. At some point when I was on stock I even did a factory data reset, effectively wiping sdcard. Just in case. Formatted the external sdcard too. Formatted everything from /system to dalvik to /cache and /data, and eventually /data/media, and still that didn't work.
I'm really at a loss here. I'm the only one of all the other users with this issue. The devs have gone way over and beyond to help me, and that makes me happy. I donated because they've done more than others would. But basically I just need ideas of what the problem could be and why this is happening, if anyone has any ideas.
Find a screen shot of my "About" page here.
Related
What I want to do is install a stock non rooted rom, kernel, and recovery. I am not sure how to change recovery to stock either is it like flashing a rom? Please give me some links for these I can't seem to find them, besides the stock kernel I found that.
----------------------------------------------------------------------------------The reason I want the above is bellow, if it matters.-----------------------------------------------------
My phone is about 95% broken.
Before, every rom/kernel combination would randomly restart, it was my phone it self I believe.
I went to a stock rooted rom, but then it restarted, and my lock screen worked, yet my home screen was black all i could do was slide my status bar down.
After that i restarted my self and then it got stock forever on the screen where it says Samsung galaxy s4.
The 5% working part is my recovery, for the most part.
I keep having to do a full wipe, not just system wipe otherwise it says error unable to mount preload or i/o or a few other things, I have to system wipe before every rom attempt.
I tried several popular roms such as sacs and triforce and a few other roms and all the kernels also.
The phone will turn on, work for a little normally, then crash again and go into the infinite loading screen where is simply says galaxy s4.
This phone is only 3 months old, so I want to take it back to sprint being completely stock so they give me a new phone.
I need links to files I need, and if i am forgetting to change anything back to stock please let me know. Thank you.
I replied to you in the newbie thread, but to return to complete stock download the latest firmware from here: http://www.sammobile.com/firmwares/ and install it with odin. Do a factory reset before and after install to make sure you have cleared out what ever is causing your problems. After this process you will be completely stock and unrooted. If you are still having problems after this it is probably hardware related.
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...
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
I'm, sure some of the members here have heard it a hundred times before but I'm struggling to find a solution for it, any help would be appreciated, thanks.
For all intents and purposes, assume I am your grandmother, that's how much of a noob I am at this stuff. That being said I have flashed once or twice before, last time I softbricked it as well and found a solution on here. I was running SlimKat but tried to flash Aryamod using the instructions here ( http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920 ) The instructions said to wipe the internal card and this is where I messed up, I wiped SDCard1 (Which I now realise is the external sd card?) and in doing so clockworkmod crashed, and it just said something along the lines of "failed" over and over. I was forced to remove the battery and reboot. Now it won't boot past the Samsung GN3 logo (but also shows "KERNEL IS NOT SEANDROID ENFORCING; set warranty bit : kernel") I've tried using odin to install the rom I tried last time I softbricked it but to no avail. I'm downloading the official rom from Samsung but it's taking hours so in the meantime just thought I'd pose the question here. It goes into both Download and Recovery Mode but I haven't been able to load a new rom using Odin, Odin passes but it stays in the bootloop. I've tried clearing caches/partitions in Recovery Mode.
I'm sure it's just a noob issue and hopefully an easy fix so I apologise for wasting anyone's time, thanks again.
Put back the arya rom zip into sdcard and flash the rom.
Sent from my SM-N920C
In Odin, uncheck everything except f.reset time. Connect the phone and flash a stock rom. When you see the word reset in the status window, remove USB cable from phone, remove battery, wait 5 seconds, replace battery, boot into recovery, wipe data and cache, reboot.
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: