[Q] Help needed- Bootlooping - G2 and Desire Z Q&A, Help & Troubleshooting

HI,
I am facing a peculiar kind of a problem. I recently rooted my Desire Z following the cyanogen wiki to the letter. I have tried many ROMS but whichever ROM I install, I am facing this problem. For the first few days of Install, my phone works perfectly. But after a few days if I reboot, my phone gets stuck is a bootloop( i dont know if thts the right word, coz it boots and it starts the android but before the launcher is started it restarts again.
First I was using Flinny's CM10.1 test builds, and then I changed it cause I thought that was the problem. Now I am using Andromadus' Mimicry 1.5 which is also giving me same problem.
Everytime this happens I have to use the PCIMG10 file to restore it and then root it again and then install the ROM..
Is there any way to solve this problem.. I'll provide logs if u require... I am desperate..

yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)

demkantor said:
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
Click to expand...
Click to collapse
I have a logcat from when I was running Flinny's CM10.1 test builds.. I faced this many times with that ROM and so I took a log last time it happened.
BootLoopLog_CM10.1
The latest time since I was in a hurry to get my phone back to working condition couldnt get a log. But soon after, it happened again. I installed only "Explorer" and "What'sapp" when this happened again. I have captured the logs and here it is.
BootLoopLog_Mimicry1.5
And ya I did try and restore a previous backup, and I also tried wiping and installing the ROM, but in both the cases the Phone will hang at the boot animation screen or restart again. Here attached is a log of the phone restarting after a clean wipe and fresh install of the ROM.
BootLoopLog_Mimicry1.5-after reinstall
Code:
Bootloader screen info
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:30
Please help me out... this is kind of frustrating.
P.S- I did see that thread.. but since my phone was not bricked, I didnt post it over there..

are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens

demkantor said:
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
Click to expand...
Click to collapse
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..

manujosephv said:
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
Click to expand...
Click to collapse
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..

manujosephv said:
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
Click to expand...
Click to collapse
Guess what... That worked... My phones been running without bootloop till now.. :good:
Everytime I reboot, my heartbeat increases.. but it comes through smoothly at the end.. thanks a lot..
P.S - Completely off the topic.. Mimicry ROM is giving me insane battery life.. Running the phone more than 1 day without charging.. :laugh:

Related

[Q] Does your phone require multiple battery pulls to boot up?

Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.

[Q]Desire Z keeps rebooting after few seconds on home screen

Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium

CyanogenMod 9 Alpha 1

HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.

[Q] Having weird issues, could it be my setup?

Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
What version of TWRP are you using? I heard 2.6 may have some issues?? Also, did you do proper wiping procedures, such as factory reset, cache wipe, dalvik cache wipe, etc before modding a new ROM? Which new ROM are you flashing, and did you flash a new radio with it?
danny_dv8 said:
Let me start off by saying that I bought this phone already rooted so I didn't have a chance to learn with it. Every time I flash any rom that people say should work well, it doesn't work great for me. I flashed the latest version of TWRP myself. Now, in order to get a good flash, what should my mounts be set to? Currently they are preload, ext sd, and internal. I don't know what I'm doing wrong but even on something as stable as cm 10, I still have issues. (Slowness, no gps even after fix, and some other small stuff). Help please and again, I am a total noob so I apologize for that.
This also causes problems when I install a kernel. It will never load the system. Even if I wait one hour, do a hard reboot and wait another hour, it still won't load. I'm sure I'm doing something wrong, but what?
Click to expand...
Click to collapse
First, what is it flashing procedure? I should be downloading rom to ur external/internal SD card, then boot to recovery and make a backup of data, boot, and system partitions, then wipe dalvik cache, system, data, and cache 3x each, then go back to main menu and choose install, find the rom and flash it, if aosp also flash gapps, then reboot, shouldn't be having any issues if u follow that procedure, and upon first reboot let the phone sit for around ten min or so to let everything settle, the first few days or so things will still be settling in so give it 3 full battery cycles before u start guaging performance, I'm on twrp 2.6 and never had an issue yet an I'm a flash addict, u could also try reverting to stock with Odin and then starting over, Odin give a more complete system wipe so u may have some corrupt files somewhere, but like I said if u follow that procedure u should be ok
Sent from my SGH-T989 using xda premium

[Q] Can't Last One Day with a Custom ROM

Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!

Categories

Resources