Hi everyone.. first post here.
I just successfully rooted my Nexus S (GT-I9020T, 2.3.4, GRJ22) using adb, recovery clockwork herring and su 2.3.6.1.
ROM Manager is working fine but I do have a couple of issues.
The recovery doesn't always stick and reverts back to the stock one from time to time (I have to flash again then from inside ROM Manager). Which could be a problem due to the next issue..
I've been trying to install some ROMs (Cynogen for instance) but in one version I get a looping boot screen and in an other it keeps going to the recovery screen. Luckily, it's the right one and I can restore a backup. I'm afraid it might revert to the stock recovery at some point and screw me.
Any thoughts on this?
I should have read some more threads first..
I fixed the recovery issue by renaming install-recover.sh using Root Explorer
So I guess I should just experiment to find good ROMs now.
Can anyone suggest a good ROM? I'm looking for improved battery use, slimmed down system, needs email apps (all google apps probably)
Sorted it all out (mount/unmount, delete caches, etc.)
It's working swimmingly now.
Running Cynogenmod 7 and loving it.
I am using Infinity 1.0.0, stable, fast and great battery life, it is a 2.3.4 rom
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App
The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...
SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?
I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.
I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.
Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.
Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..
Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...
I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.
This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.
And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...
I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?
Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.
I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.
Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.
I rooted and upgraded my rom to Eos 1.0.0 several months ago. Ever since then ive been having issues with my bluetooth devices staying connected and working property. Also, lately my browser has been closing randomly and will get worse unless I reboot.
I absolutely love the team Eos build and hope they can help me find a solution. I am wondering if anybody else has had the same issues or know of anything that can help me?
Would upgrading to their new rom build help you think?
Upgrade to EOS 2.0.0
Can you go into recovery and wipe cache, and davlik? and check again.
And, if you decided to upgrade to EOS2.0, don't forget to wipe cache, dalvik and battery stats thru recovery.
Hey guys,
I've got a Wind G2X which I've recently installed the new 2012 baseband on using LG's tool and the local webserver trick (I believe this technically rebrands the phone to T-Mobile). I then installed some not-latest Eaglesblood AOSP and had it for a while -- everything was pretty solid.
Then I decided to upgrade to the latest, since I like to stay up to date. During this upgrade, I've also tried to "Fix Permissions" (in CWM, after a data wipe) to make sure the permissions are correct just in case -- this operation makes no sense if it relies on there being data (I suspect it does, because I was able to successfully Fix Permissions after flashing the ROM). While "fixing permissions", I've had the phone freeze up, so I pulled the battery, tried again, same thing. Ever since, I've tried installing the latest EGB AOSP and kept finding my phone either dead due to emptied battery (way too quickly) or dead WITH battery charge, every day.
Just recently, I flashed HellFire Sandwich (tried 1.7 and now 1.9), both of which greeted me with "Process stopped.. something something.media". Now in 1.9, when I went to the Play Store for the first time, it hung. I had to pull the battery. 2nd run worked fine.
So I have the following questions:
1. What could be wrong? I doubt it's just bad luck with the ROMs -- surely they would notice such significant problems.
2. When I flash a new ROM, I do the "wipe data/factory reset" and "Wipe Dalvik cache" (should I do the 2nd step? if not, can it cause problems?) followed by flashing the ROM and then GApps. When I do this, can there be some remains from the previous ROM (or some system components) causing the stability issues, or is it a perfectly clean installation with the exception of the recovery partition?
3. Is there anything I can do to truly restore/wipe the phone to prepare it for flashing some ROM and guarantee that there isn't some residual software that can cause problems?
I'll see how stable HellFire Sandwich 1.9 will be on this phone, but the .media crash and Play Store hang may be indicators of more to come.
Thanks!
:/
All ICS roms for g2x have issues with the stability , you should wait the new SU660 Kernel source for a super stable and fully working ICS ROMS
always make wipe factory reset, wipe dalvik and go to advanced and select format /system , before flash any roms, there is no bug froms previous software if you follow these steps (sorry for the english lol ) e_e/
I recomend you any cyanogen based rom (GB 2.3.7) with camera port for cyanogen in the lg optimus 2x thread
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
parabol4 said:
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
Click to expand...
Click to collapse
i have this problem as well battery indicator stuck at 1percent.
parabol4 said:
Since I cannot yet post in the development section, I'll hope to have some response here. Upon installing the unofficial CM11 mod in combination with pink kernel, I came across a stubborn bug: the battery indicator is invariably stuck at 1%.
A clean reflash (even /system format) did not help. I flashed back the stock ROM, wiped everything and reflashed the CM11 with no difference so far.
Has anybody got an explanation/bug fix? Thanks in advance..
Click to expand...
Click to collapse
I had this same issue even in stock ROM... just let the battery drain completely til the phone switches off and then charge the phone and boot... it worked for me... :fingers-crossed:
I had this happen to me on stock as well the first day I owned the phone. Left it on the charger all night and on less than ten minutes of use the battery showed 1%. Charged back to full and haven't seen it again. I think server people have experienced this bug.
Sent from my XT1034 using XDA Premium 4 mobile app
find the battery apps in apps setting then try clear the cache. once happen to my old s2's cm11.