I have now tried to install Hyperdrive ROM three times. The first time I had found an old thread written well before much of the S4 debauchery got as thick as it is now and it was definitely the wrong version. I`m on NI1 4.4.2 and downloaded the latest HD rom file (21?) as well as the UI. Followed the instructions to a T and wound up with it stuck on the orange HD/Kit Kat animation for eleven minutes. Finally got it to shut off, wouldn`t reboot. Tried a few times hoping to get it to at least get me in a position to restore a backup. Nope. It would get to the setup procedure but every action on the screen resulted in a "Samsung key lock has stopped working" message. Ended up just installing an older Odin stock rom (4.3), rooting and reinstalling Safestrap and finally getting to load my backup. I~m really interested in the HD rom, so can I ask for (a) what I might be doing wrong and (b) how do I do it correctly? I`m on NI1 again, rooted, using safestrap.
Related
Hi all,
I recently installed the newest build of Slimbean. I am having a few issues: I am unable to play any media... Music, videos (youtube). My phone app does not work. I cannot receive nor send any calls. And my phone produces no sounds at all.
I tried installing build 7 to see if it was an issue with the build I was using... didn't help.
Internet and wifi work without any problems.
Galaxy S4 i337m
Baseband: I337MUMUAMDL
Version: Slim-4.2.2.build.7-OFFICIAL
Build #: slim_jfltecan-userdebug 4.2.2 JDQ39E eng.blk_jack.20130706.15730 test-keys
Any ideas?
Thanks in advance
Update: Any ROM I install... Phone and sounds do not work.
Talabis said:
Update: Any ROM I install... Phone and sounds do not work.
Click to expand...
Click to collapse
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
jd1639 said:
I'd Odin back to stock and see if you still have the issue. If you do it's a hardware issue.
Click to expand...
Click to collapse
I did just that... But it's a bit of a story.
I had just fixed another problem I was having yesterday. Was getting stuck at the S4 splash screen right after powering on the phone. The problem was caused by TWRP 2.6 and formatting /data partition. Long story short, I installed CWM and used it to do a full wipe/format of partitions and then was able to install ROMs, restore backups without issue.
So today, since everything was working, I decided to flash a new custom ROM (which I installed) and the MG1 radio. Wasn't having any luck with the radio. Finally, I was able to flash a radio via mobile odin, but then I soft bricked my phone. Got stuck at the S4 splash screen (same issue I had yesterday, but this time, a different cause). So was troubleshooting it all day. Tried to go back to stock, no luck. Tried to restore the stock backup I had, no luck. Only thing I could do was install custom ROMs at this point to get into my phone (i.e. Slimbean, FoxHound, etc...). But, at this point, although I could boot into Android, I had no sound at all and couldn't play video. So after hours of trial and error, I installed CWM again (replacing TWRP 2.5.0.2), did a full wipe/format and tried to install a stock ROM. No luck. Still was hanging at the S4 splash screen. Then I tried to install this ROM again which I had luck with in the past; |ROM| |★VLUAMG1★| |CANADIAN||i337M||STOCK||ROOTED||July.26.13|. But his instructions said to install a wifi fix or fear soft bricking my phone. So I installed the wifi fix, but selected the wrong file (I know, stupid. Done a lot of stupid **** in the past couple days with this phone). Now, after the phone rebooted, I would see the S4 splash screen for a split second, and it would auto load into download (odin) mode. Couldn't get into recovery at all. So then I decided to flash one of the stock ROMs I tried earlier that didn't work, but this time, SUCCESS!!!!! Phone was booting and all sounds worked. I could make/receive phone calls as well... Everything seems to be working fine now. I find it funny that flashing a wifi fix that I shouldn't have seems to have fixed my issue in a sense. Since it allowed me to successfully flash a stock ROM. So I am making a backup of the stock ROM and will decide what I'm going to do from here.
Holy goalie!!! It's been a very vexing couple of days.
Nice that you got it all worked out, I've found out that if your "status" is custom, it will sometimes give you problems when flashing a "stock" rom via odin.
So what I always do when reverting back to the stock rom, I use triangle away to clear the flash count and make my phone back to "Official". If you want the steps to do this, let me know, it's not hard, but there are crucial steps to get this right!
JP
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...
TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
C3PH0 said:
TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
Click to expand...
Click to collapse
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Harleydroid said:
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Click to expand...
Click to collapse
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
C3PH0 said:
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
Click to expand...
Click to collapse
You bet bud
Sent from my Eclipsed Note 3 using XDA Premium
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
FlinderMouse said:
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
Click to expand...
Click to collapse
Try a factory reset and then install stock ROM
i7vSa7vi7y said:
Try a factory reset and then install stock ROM
Click to expand...
Click to collapse
Could you point me in the right direction for that? Everything I have tried so far seems to fail...
Edit: I got back to the NAE stock rom, but I can't downgrade the modem from NG2 back to NAE...
Edit2: I didn't need the correct modem to activate, I guess. Flashing back to GPE, will update this again.
Final Edit: Once I activated on the stock ROM, everything seems to work perfectly on the GPE. Thanks for the suggestion, i7vSa7vi7y!
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