Hi
I've been playing around with ROMs. And I might have flashed things that I shouldn't have flashed. Like modem files and stuff.
My phone is working, but I have erratic battery drains. Like 0.6%/h and the next percentage is 25%/h (screen is off), which I hadn't had before.
I bought a new battery because I thought that might be the problem, but the problem is still there.
So I was thinking that I may have flashed some wrong things like modem drivers that might cause the modem to use too much power.
I did flash a stock firmware. But does this include everything I could have messed up? Or can there still be some residue from other ROMs somewhere? (Kernels, modems, ....?)
No flashing stock firmware is enough
Related
Hi all. Have a weird problem with my G1 that my girlfriend is using at the moment. It is rooted and I have tried various ROMs to see if I can fix the problem.
The problem I am having is that once the phone gets plugged into charge, it turns itself off and it seems to loose the ROM that has been flashed so then I have to reboot into recovery and re-flash it. It does this every time I try a different ROM so can't be related to one particular ROM.
Does anyone have any ideas why it would do this?
Hi there,
the proximity sensor on my i9000 isn´t working anymore. Everytime I place a call/get called the screen turns black and freezes. I have to pull the battery and restart it.
Testing the sensor on the LCD-test the screen turned green and the i9000 startet vibrating. Here, too only pulling the battery made it stop.
Here is what I tried so far:
- flashing different stock fw (Android 2.2 / 2.3.x)
- applied handicapped settings
- Using Proximity_Screen_Off App and Sanity-App on stock fw
- blowing air into the USB jack/vacuuming the jack
- opened the device to mechanically clean the sensor
All of the above failed!
The only way I can get it to work is when running android 2.3.7 Joker´s MiUi and run the Proximity_Screen_Off App.
Are there any other suggestions as to what can be tried?
Else I will have to get a new motherboard, because wouldn´t want to be restricted to using only one particular rom.
Any input is greatly appreciated
Thanks Christine
if i recall good (but kill me ive drinked some atm) the greensih issue was showing with voodoo color kernels and all the sensor peoblems came with badly assembled kernel.
so i would advice you to reflash pure 3 file firmware (repartition pit and all that jazz)
and if your sensors still would not work just reflash to your carrier or stock formware for your region and push it to repair center with proper dwscription (do no mentions miui or other crap)
Thanks for answering!
I flashed 3-part firmware, pretty much everything available and a CF-Root kernel.
So it couldn´t have been a bad kernel.
Can´t take it back to service, no warranty left.
I just flashed 2.3.5 and CF-Root and now I am fooling around with it some more.
I just think it´s weird that it would work with that and only that MiUi.
impossible unless youve got some other galaxy variaant than i9000
Hello. As some of you may remember - I have serious problems with wakelocks and it's related to a "SMSDispatcher" service (for those who are interested - http://forum.xda-developers.com/showthread.php?t=2138980).
I had no issues at all on ICS before I upgraded to official JB. Great battery life, huge screen-on time, ~3 days on battery with small usage was something normal for me.
But after upgrading to JB I started to get wakelocks. Loads of wakelocks. I checked battery stats - the Dialer apk showed up. I installed Better Battery Stats and it showed me that "SMSDispatcher" prevents my phone from goind into deep sleep. I thought it was a bug so I flashed back my .195 4.0.4 FW. And guess what. The problem was still there. It... transfered from JB to ICS?! I have this problem for 3 weeks now and even today I still don't know how can I get rid of this.
I tried wiping every partition on the phone including both SD's. Tried deleting contacts on SIM card. Tried deleting all contacts from GMAIL and manually adding them again. Tried flashing stock JB and use my T without restoring ANYTHING. But I haven't tried one thing:
Yesterday I installed unofficial CM10 (from original android development subforum). Almost clear android could have bringed a peace to me finally. It runs great but not perfect. Why? I still have SMSDispatcher issue. LOADS of wake-ups from the Dialer apk (sometimes it shows as com.android.phone, sometimes as RILD).
What I discovered is that on ICS these wakelocks are shorter than on JB. About 1/1,5h of wakelocks for ~22h on battery. On Jelly Bean it was 3h for 8h on battery.
As far as I remember on 4.0.4 .195 FW there was -19 baseband. Both official JB and CM10 use -33 baseband which may be a problem, I don't know.
So my next step in my long path to get rid of this annoying bug is changing to ICS baseband.
And my question is - which files shoud I pull from .195 stock SONY 4.0.4 FW?
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33. So I probably need binaries/files pulled from ICS and I don't know which ones.
Can you help me? Maybe with your help I could finally get rid of this or at least make the problem less annoying...
Can you just flash an ICS firmware and exclude everything except baseband?
Not sure if it wise but it may help you.
romcio47 said:
I tried to flash baseband using flashtool but the baseband didn't change. It's still -33.
Click to expand...
Click to collapse
I already did that. No result.
Another idea - is it possible to repair software on the phone with unlocked BL?
EDIT:
Ok, found Jozinek's thread with .ftf to relock my bootloader. I will try to repair my software and see if this fix my problem.
Problem solved. It was my old SIM card's fault. It was more than 6 years old and I had to manually cut it from mini-SIM to micro-SIM shape. I probably damaged its inside structure or something. I went to my carrier and requested a new SIM card factory cut to a micro-SIM shape and now everything is ok! No strange wakelocks at all!
Hi mate!
I just was wondering after all that u've experienced what do you thing about JB , which is better for performance and battery life management ICS or JB? I'm just thinking is it worth it to upgrade to JB or stay on ICS
Stay on ICS if you don't like charging your phone once a day (in good scenario). Or twice.
ICS has definitely much better working Extended Standby Mode. It gives you amazing battery life sometimes. I'm on JB because of better multitasking and higher RAM available but speaking about the battery - ICS wins. JB just has to be fixed and tweaked by SONY. It's just a first public release. So bugs are something common. We have to wait.
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
It happens randomly when using the phone (it doesn't happen when it's locked). The phone just freezes then restarts randomly.
I tried to find a pattern when this is happening, and found there isn't much of a pattern, but it won't let me add a fingerprint lock (crashes after the 3rd / 4th reading).
I've tried to factory reset and clear cache. I'm running out of options and am preparing to flash a stock ROM via Odin. I'd like to avoid this, since it'll trip knox and this is a new phone so I wanted to avoid flashing anything for now.
Any suggestions, ideas?
I'd say this is a kernel related crash, since it doesn't give any error, just goes out. But I hope I'm wrong.
Baseband: N920CXXU2BPD5
Build Number: MMB29K.N920CXXU2BPD6
Knox untripped.
EDIT: This seems to be a rule: it always crashes when I get to 32% of adding a fingerprint lock.
Here's an update:
Tried flashing other stock ROMs for other regions, still the same problem.
Flashed a custom kernel, still the same problem. -> Not a kernel problem
Flashed TWRP and used it for some time (to test if the phone will do the same). No problem whatsoever. I'm convinced that this is a firmware issue then.
Tried flashing every possible combination of everything. Nothing seems to have any effect. This isn't a software problem.
It's probably a faulty motherboard. The rebooting subsided though.
I'd also like to add that the S Pen holding area (the place where the S Pen is kept inside the phone) has a specific electronic smell (kindda like the soldering smell, but not quite). Really weird.
I voided my warranty by flashing stuff, so I'll probably be looking at a motherboard replacement if anyone's wondering.
Do u have xposed install?
Nah.
I've been running the stock rom for 90% of the time.
RexGrammer said:
Nah.
I've been running the stock rom for 90% of the time.
Click to expand...
Click to collapse
U solved it already? Mine used to have this problem before but its xposed that cause (in my case :highfive
Still haven't.
I'm almost certain it's a faulty motherboard.