Develop Bugs

[Q] CWM Recovery very slow all of a sudden

Hi Folks,
Was running ZYGOT3 2.0 and Franco #6 for last week or so, with no major issues.
Had a freeze-up after a phone call this morning, figured that maybe I was undervolting too aggressively, and didn't think much of it. Pulled battery, replaced battery, restarted phone, phone hung at Google logo.
Pulled battery again, rebooted to bootloader, entered CWM recovery no problem. Figured I'd reflash the kernel if my phone wasn't booting past the Google logo due to the undervolt settings. When I went to choose zip from SDCARD - the screen went black other than the CWM version and logo, and my folder list never appeared at the top of the screen.
Pulled battery, tried again, same result.
Pulled battery, this time went to advanced menu - wiped dalvik cache no problem.
went back to main screen to try to wipe cache again...and it hung again. Got distracted, came back to phone like 5 minutes later, and CWM had finally responded and was showing me the option to wipe cache.
So I was able to reflash Franco #6 and boot the phone back up. Then I just downloaded Franco #7 kernel - rebooted to CWM Recovery to install - and noticed that the CWM is again very sluggish. It seems that I need to wait anywhere from 30 seconds to over a minute before it responds to even a simple command, such as to show me the list of files & folders.
Any ideas folks?
Thanks!
Justin

Strange issue, need a little help.

I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?

Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk

if you can get into cwm then try fastboot and flash the factory images from the boot screen

_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.

id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it

I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.

Not booting... not sure what happened

So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.

Ryjabo said:
So my phone was sitting here on my desk at work, the display was on (very, very low brightness + super dimmed because of that setting in CM9) and it was downloading (via 3G) a ~300mb file for the Mass Effect game that's on sale in the play store today.
Suddenly I looked over at my phone and it was powered off... charging. The only thing I did notice was that it was VERY warm.
I tried to boot my phone up and it got all the way to the lock screen then it shut off. I let it charge for 20-30 minutes then tried again, would not get past the boot animation. I booted into recovery and wiped cache & dalvik in case something crashed... didn't help. Still won't get past the boot animation.
I'm letting it charge for an hour or so then I'll try to boot it up again. If not I'm going to go into recovery and try a complete wipe/flash.
I was running CM9 + franco (ondemand, no OC or UV)
Has anyone had anything like this happen?
Will report back in an hour or so.
Click to expand...
Click to collapse
try reflashing the rom.

the CPU does have a set limit for how hot it can get. My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Sent From My Sprint Galaxy Nexus

ÜBER™ said:
My guess is downloading that amount over 3G on the charger (my god what were you thinking) made it shut down. Although once cooled down it should have booted right back up.
Click to expand...
Click to collapse
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.

Ryjabo said:
I download lots on 3G. Regularly. 10gb over the last two weeks, in fact. This has never happened to me.
Click to expand...
Click to collapse
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image

simms22 said:
same here, i download lots all the time. my guess is that your phone crashed, and since fsync is off by default in franco kernel, your rom or a partition corrupted. if reflashing your rom doesnt help, youll have to flash the factory system image
Click to expand...
Click to collapse
I just booted into recovery and flashed a completely different ROM (AOKP). Now it's not going past the "Google" logo (with the lock at the bottom).
I'll wipe and reflash CM9 to see if that helps.

I just noticed something I've never noticed before... after flashing the ROM it says this:
Finding update package...
Opening update package...
Installing update...
Fixing fs_size in crypto footer...
Install from sdcard complete.
Click to expand...
Click to collapse
What in the world does that mean?

I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.

Ryjabo said:
I reflashed CM9 again and now it is booted up.
The battery showed at 5% ...maybe I was a little impatient >.<
I figured 20-30 minutes+ on USB charging would be fine... maybe I was wrong.
Click to expand...
Click to collapse
sweet

Happens to me once when my kid are playing where's my water. Phone get to bootloop and first i try to wipe caches but no luck, reflash rom without data wipe -> no luck, luckily i have 1 day old nandroid backup i restored it and it started to work.
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.

jnr21 said:
I quess your phone warms so hot that it needs to reboot and there is some data write at same time so it got some data loss.
Click to expand...
Click to collapse
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.

Ryjabo said:
That's a likely explanation, but this has never happened to me before so I was panicking.
Good times.
Click to expand...
Click to collapse
My phone has booted itself many times also, but only once it got data loss.
I think that disabling fsync in kernel increases risk of data loss...

So CM9 is running just fine. This time I didn't flash Franco, probably won't, don't necessarily need to. And holy dogballs... Titanium Backup is truly, truly amazing. I wish I could give the creator a hug.
Anyway, I have noticed that the bars (signal/3G/wifi) have yet to turn "blue" like they normally are. What does this mean?

help: can't boot, stuck on green htc logo

Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?

landwomble said:
Hi All,
Got a problem with my HOX. Rooted, and was running Franco kernel and PKMN ROM. Had a few issues so flashed back to stock kernel, wiped and reinstalled ROM.
Now I've got a problem; boots up, get a sense lock screen, then when I unlock I just get a white screen with HTC logo on that doesn't go away.
Help!
I've reflashed stock boot.img in fastboot, I've done a fastboot erase cache and still have same issue.
EDIT:
Well, got it to boot. Going thru setup now and it's INCREDIBLY SLOW. It's like it's underclocked to 100mhz or something. It's completely unusable - hitting "Next" in the Android setup menu takes 30 secs to process etc... This is kind of what was starting to happen before I wiped and reflashed - could it be I have corrupt storage or something?
Click to expand...
Click to collapse
Did you remember to install kernel modules AFTER you installed your ROM? Roms come with their own kernels and the kernel modules are already installed under /system/lib. So unless you flash the kernel modules after the ROM, ROMs kernel modules get installed instead.

Yes, I did. Got it working now though - not sure what it was but mounted USB storage and got windows to scan the storage - then re-downloaded the ROM and flashed again. Weird....!

[Q][PRO] Dead phone, it never boots, i woke up to find it like this,

it was normally working at night. I turned off the screen and went to sleep. the battery was about 90%
When i woke up,i found that the screen was lit. it was a little dark blue-ish. The phone did not respond to anything i do !
I made a battery pull and tried to reboot. the same dark blue-ish screen appeared again, the kernel's logo never shows up. i tried to charge it for a while then turning it on. the kernel's Logo appeared. I can now access both CWM and TWRP. but when it's turn for the boot animation. the dark blue screen pops in again
any ideas ??
Specs: Xperia Pro
ROM: Ultimate HD v2.0.3
Kernel: E-kernel (the dual recovery one)
MODS installed:
uHD MOD v2.4
Cybershot
walkman

Recharge it for a while
Try to clead cache and dalvik, fix permissions, try to boot
If it dont work, then change your kernel and try to boot.
If it dont work, revert back to a old backup or flash a stock rom

Thanks for your help.
I fixed it by formatting the system partition and reflashing the rom.
Now it's all good

if at some point the kernel logo doesn't show up, I'd put my two cents on the kernel for an issue... just saying... but as long as you are able to still connect the phone in fastboot mode, you can always try flashing a kernel to recover it.
Just saying. ... good you figured it out.

atmos929 said:
if at some point the kernel logo doesn't show up, I'd put my two cents on the kernel for an issue... just saying... but as long as you are able to still connect the phone in fastboot mode, you can always try flashing a kernel to recover it.
Just saying. ... good you figured it out.
Click to expand...
Click to collapse
I don't think it was a problem with the kernel.
At first the kernel's logo didn't show up because the mobile was low on battery. The screen was lit the whole night. When I charged it a little the kernel booted normally and I accessed recovery without any issues.
I really don't know what the heck happened.
The only thing the mobile should do at night is backing up apps with titanium backup.
I'll try to see if any apps didn't get backed up. Maybe it hangs on a certain app...
Sent from my Sony Xperia Pro using Tapatalk 2