Related
Hopefully this is the right place to post. I apologize if it's not.
Last week I bought the Samsung Galaxy S2 X from Koodo Mobile. The model # is SGH-T989D and runs the newest version of ICS. 4.04 I believe.
I hadn't had any problems until recently. I was trying to root my phone when I ran into some trouble. I forgot to make a backup of my system, so when I ran into problems, I just decided to try out a couple custom roms. At some point something got messed up badly with my phone. Whenever I turn it off now the lights at the bottom of the screen stay on. Unless I hold the power for 30 seconds to a minutes it won't turn back on. The factory reset has also been a problem. I'll go to reset it, and it formats the usb storage, but doesn't restart. When the phone is on, it seems to work fine.
I finally managed to get a telus stock rom to flash and work. So I have two questions I'm hopeful someone can help me with.
1. Are there any Koodo stock roms for ICS? I've looked on tons of different sites, and it seems it's all either for T-mobile or Telus. Is that because Koodos just came out with their phone? I'm just looking for the exact version that would have been on my phone when I got it. I found one online, but it had no baseband version. If I have to return the phone or send it in for repairs, I'd like it back to stock,
2. My other question is, does the light not turning off, and the turn on problems sounds like a hardware issue? I've been trying to fix this for the last 24 hours and it's driving me nuts. Since I'm a noob I have no idea whether I should keep trying or just send it in for repairs. Does it sound like something that can be fixed? Like maybe I'm flashed a wrong kernel or am using a bad rom? I don't know, but advice would be much appreciated.
Thanks to anyone who answers.
you have various roms made for koodo..2) are you talking about the soft keys? depending on what rom you use they can be different (locationwise) ... if I'm not mistaken all --- This is my personal opinion. Jedi on koddo should be more than sufficient as to suit your daily driver needs. Dev is very helpful and keeps a very organized thread. You can also try darkside, if I'm not mistaken he had a koodo version. i own a hercules so i at give more information... for your best info, go into the thread and ask the ppl i n them for their experience. everyone's needs are different so for what might work for me might not for you Infamous is another one. Just click on the t mobile dev section and you just scroll for what you like.. Hope this help
I guess my main question is about the key lights staying on. I'm pretty sure it means its not shutting down correctly because it also won't turn on again unless I hold down the power button for 30 seconds. So could that be caused by anything I did? Like any of the flashing or customers roms I used, or should I just send it back into Koodo?
Okay download this: http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
And then flash a rom (any one, just pick one)
That is a flash able zip (in cwm recovery) that will completely wipe off every piece of system and rom data (does NOT touch anything on your internal memory or external sd). If your hardware lights are malfunctioning due to software, this will fix it. Then, when you flash your rom, if you still have the issue with your hardware lights, it's likely a hardware issue and you should follow a guide to return to stock everything and send it in for warranty repair.
Also, this is a Koodo based rom if you're interested:
http://forum.xda-developers.com/showthread.php?t=1849748
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Just run the cache wipe again. It will fix that.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
robois88 said:
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Click to expand...
Click to collapse
If you're looking to make a backup of your entire device image, your cwm recovery will do that for you under backup. No other way to do it, you have to do it via a recovery mode.
I don't know why factory reset would be causing that problem since I never use that but it does seem odd.
robois88 said:
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
Click to expand...
Click to collapse
To return exactly how you bought it, you need to first flash the stock ics kernel through cwm. Then flash an Odin tar file through Odin (desktop) which will restore stock rom as well as stock recovery. Unfortunately, I've looked around but could not find an Odin tar file for Koodo stock. Maybe you'll have better luck but in any case that is the process.
You seem competent and willing to learn, which doesn't happen as often as you would think. Let me know if I can help further. Good luck.
yoft1,
Many thanks again for your help. I am extremely green to this type of stuff so I feel like I've been thrown into the deep end here.
I've been looking around for the tar file and can't seem to find one either. But with the amount of people on here, there is probably someone who could upload it right? Would there be a thread or better forum for me to make a request? Or is that poor etiquette on this site?
I've just seen so many different roms, kernels, updates, etc...and I'm thinking somebody might be able to get it on here.
Ok you also said the first thing to do is to flash the kernel. Am I just lookng for any stock ics kernel? I just know I've looked through so many website and threads with different kernels, I just want to make sure I flash the correct one. Like is there a specific one per carrier, or model, or brand?
Again thanks for the help.
I would probably start a thread in the general section to see if someone can compile/upload an Odin flashable tar from Koodo stock. If that doesn't work or if no one responds after a bit, I would PM Mr X (a user on these forums). He is a dev that has uploaded stock roms for Telus and tmobile and he's also a really nice guy. He would probably know where to get one.
As for the kernel, I'm not sure if it matters but I would say with 80% certainty that there is no difference between the stock tmobile kernel and the stock Koodo kernel. On top of that, I would say with 99% certainty that it doesn't matter either way because I highly doubt they would look that closely (if there's anything to find at all) if you send it in for warranty purposes (but no promises of course) . If you get your hands on that tar file for Odin, I'm almost positive that the stock tmobile/Telus ics kernel will do it for ya.
Here is one of MrX's threads so you can PM him if the general forum doesn't work out:
http://forum.xda-developers.com/showthread.php?t=1356739
OK, so here is a little more info...My phone is flashed to Cricket carrier. I have spent the last 3 days flashing the **** out of my phone trying different roms,addons, tweaks etc. All the while making sure to wipe Dalvic, and regular caches in between each flash. I am thinking maybe something more than what i am seeing is borked. Could doing a more thourough odin flash help me out? Maybe wiping partitions? A reset pit file? Someone with some insight and more experience with odin may chime in on this one.
Restored my Nandroid backup. Which is CM 10.1 Wild for the night. Now I had everything running buttery smooth on this nandroid except Hdmi mirroring. I have done lots of testing on this rom. The Huge problem now is it restored perfectly with everything running great but, now I know I borked the Gyroscope!!! Has to be that because I have no screen rotation with my nandroid backup now!! WTF???
No matter what rom i flash or how i flash it..., odin, one click, CWM, mobile odin pro, no flash has corrected my auto rotate feature since i flashed the universal Speed Daemon tweak for both touchwiz and AOSP roms!!! Help!!!!
First, this is the Android Development section. You can not post anything other than development in this section. Only ROMs, tweaks, etc go in this section. Questions/problems go in Q&A.
And second, my gyroscope messed up a few months ago as well. It will fix by itself (or at least mine did). Just give it time. If not, then just wipe data and flash a new ROM (or the same one) but make sure to make a backup of your apps before you do it.
Next time, please post in the Q&A section if your phone isn't working properly and need help.
EDIT: And if you are on JB, try using the All-in one Speed Daemon & Gyro/GPS Fix: http://forum.xda-developers.com/showthread.php?t=1975379
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
It's probably been looked at but if not you'll want to double-check that auto-rotate is enabled in settings.
Got me a few times this way...
I've been having this issue ever since CM10.1 nightly 0308. Phone reboots randomly and enters a boot loop until it calms down and boots normal. I never had this problem on any build of CM earlier than 030813 when they moved to 3.4 kernels for the Sprint GS3. I've tried everything, posted on numerous forums, even brought the issue to Cyanogenmod's (Steve Kondik's) attention on G+, but all I get from everyone is upgrade to MD4 radio. I have been on MD4 radio and firmware from the first day it was leaked. So if anyone can help fix this I have a $100 bounty on it. Payable via money order to international winner(s) - no Paypal here, and in local currency on the off-chance that a local dev can help fix it. I have uploaded a video on youtube of the phone in a reboot loop. Video is not top quality, it was taken with an iPhone 4S in a moving vehicle but you can see clearly what is going on.
Here is the link to the video on youtube:
http://youtu.be/kposye98XJI
NB. The phone is flashed to Visafone CDMA network in Nigeria. Voice, SMS and 3g data work flawlessly.
Bounties are not something we like much on XDA.
Try doing a clean flash wipe cache, wipe dalvik and do factory reset. If you don't do a factory reset your laying the new rom on existing rom data.
Also questions go in the Q&A section not in the General section.
Thread moved.
Have a great day!
edfunkycold said:
Bounties are not something we like much on XDA.
Try doing a clean flash wipe cache, wipe dalvik and do factory reset. If you don't do a factory reset your laying the new rom on existing rom data.
Also questions go in the Q&A section not in the General section.
Thread moved.
Have a great day!
Click to expand...
Click to collapse
I've wiped data, wiped cache, formatted sdcard, formatted system, copied my stuff from external sdcard to laptop, formatted external sdcard, done everything humanly possible to get a trouble-free flash. All goes well during flash, no issues.But phone has never gone 24hrs without a reboot loop. On stock TouchWiz all is well, but I don't like TW. Downgraded to CM10.0 and NO REBOOT LOOPS because kernel is 3.0, same as MD4 TW kernel, so this problem never arises. Traced back a bit to CM10.1 nightly of March 17 or 18 and all is still ok because that was the last nightly with 3.0 kernel. Anything after that and the issue comes up again. My baseband is MD4, same as firmware, flashed with the AIO from freeza. To top it all, this is not peculiar to my phone: ALL Sprint Galaxy S3 phones I have flashed for friends all experience this so I just take them back to stock TW. It's frustrating to say the least. Any help?
Your repeating what you said already. In none of what you said have ever said you have done FACTORY RESET...
Then stay with what works
Have a great day!
edfunkycold said:
Your repeating what you said already. In none of what you said have ever said you have done FACTORY RESET...
Then stay with what works
Have a great day!
Click to expand...
Click to collapse
Done that at least 15 times. I've been trying to tackle this issue for months now, still no headway. When I was asking around for solutions some people thought I was a phone hypochondriac. That's the reason I posted the video on youtube.
Stick with what works...
Have a great day!
This thread is not within bounty guidelines. For now I am going to shutdown this "bounty" as it does not have a concise goal that pays out at the completion of the goal as it should be stated on the OP. Arguing points with links to real bounty threads is not what we are here for.
Bounties are strictly pledges. If you want to donate to the developer, donate.
With that said this thread is closed.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Hello to you,
After doing some research without finding answers I allowed myself to create a post on the forum.
I apologize if I put my post in a bad section.
Here is my problem:
When I got home, I noticed that I did not have any sound coming from the speakers of my Xiaomi Redmi Note 4X (mido) with the LineageOs rom, that is to say at the beginning after all worked, it is not not fallen.
For the ringtone and the alarm is ok it's only for all that is music and video, I have not yet test a call in HP.
To try to solve the problem I have to reinstall my phone at 100% while updating the rom but no change is always a problem which is not dramatic the phone is usable but removes some possibility.
Would you have solutions?
Meri in advance for your help and I wish you a good day / evening
Updating is not a reinstallation. It is dirty flashing, where all your settings and modifications survive. Try to go to twrp and wipe system, data and caches. Now flashing gives you a clean installation.