[Q] Blank Screen - Only one Kernel version works - Nexus One Q&A, Help & Troubleshooting

I am having a weird problem with my Nexus One. Everytime I install any custom rom, the installation will happen properly. But then after rebooting the phone will have just a blank screen. It is just the display that does not work. adb works fine and I can view the screen and access it using Android Screencast! When I flash 2.6.35.4_SVS-925mV_CFS_AXI_720p_1113MHz_082710 kernel on top of the custom ROM, it starts working fine! I would like to try better kernels to improve battery and for other stuff. But I am stuck at this point! It happens with every other kernel (I have tried some 10 to 15 other kernels). This is the only one that seems to work. Luckily I found this one..
Yesterday I tried stock 2.3 ROM. It also had the same problem!! Not sure what is going on here. Can someone provide some tips or anything? It is not a problem with flashing as I am very much used to it (have flashed my phone more than 100 times or so!). I am not a very dumb person as well

What recovery are you using? When you went back to stock did you use the passimg method or did you flash via recovery or fastboot?

Only RA 1.8 works for me. I get blank screen with other recoveries. I don't think mine is SLCD. I got it sometime in Jan 2010 itself (when SLCD did not even start).
I flash via recovery.

So even Amon RA 2.2.1 doesn't work that's odd anyway have you tried using temasek system wipe before you flash? I suggest you make a 5X wipe (factory reset) and temasek system wipe 3X then see if you can flash what ever you want.

Dude Random21 said:
So even Amon RA 2.2.1 doesn't work that's odd anyway have you tried using temasek system wipe before you flash? I suggest you make a 5X wipe (factory reset) and temasek system wipe 3X then see if you can flash what ever you want.
Click to expand...
Click to collapse
Ok! I will give it a shot. What has been puzzling is that, when I install the specified kernel (2.6.35.4_SVS-925mV_CFS_AXI_720p_1113MHz_082710), any custom ROM would work!
Anyways... I will try temasek wipe and see if that helps. Will post my findings tomorrow.

Still not working
Hi everyone.. I am still facing the same issue.. I still have only one working kernel version. I have tried almost every other ROM. Kang-o-rama, LeoFroyo, CM7, MIUI, etc.. Everything has this same problem. The default kernel itself does not work.
Any one has any idea?

Seriously when I think about it it might be hardware limitations or issues because it only one kernel works and only one recovery works then I think it might be an issue with the screen, have you ever had it replaced or have you ever had any repairs done on the phone?? If not then maybe call up htc with your problem your warranty is probably out anyway so just tell them that you have root access and only a few custom things work and none of their stuff works. They should be able to fix it some how although it won't be free.

Dude Random21 said:
Seriously when I think about it it might be hardware limitations or issues because it only one kernel works and only one recovery works then I think it might be an issue with the screen, have you ever had it replaced or have you ever had any repairs done on the phone?? If not then maybe call up htc with your problem your warranty is probably out anyway so just tell them that you have root access and only a few custom things work and none of their stuff works. They should be able to fix it some how although it won't be free.
Click to expand...
Click to collapse
Hi.. Can it be something to do with HBOOT or Radio version? When I go into bootloader, following information is displayed.. When I was switching across different ROMs, I had to upgrade HBOOT once as it was a requirement then. I guess it was because of the image size..
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Oct 12 2010, 14:33:16

Well I suppose it is possible but I doubt it because you have the latest hboot and the radio and the radio either works or the phone is bricked most of the time so those should be fine but if you want you could try flashing a new hboot again just to see what happens.
Sorry for the late reply I've been away these last few days.

Dude Random21 said:
Well I suppose it is possible but I doubt it because you have the latest hboot and the radio and the radio either works or the phone is bricked most of the time so those should be fine but if you want you could try flashing a new hboot again just to see what happens.
Sorry for the late reply I've been away these last few days.
Click to expand...
Click to collapse
No problem.. I am starting to have a new problem.. It has been happening over the last few weeks..
http://forum.xda-developers.com/showthread.php?t=1190973
I am thinking of changing the battery!! Any ideas on this one?

Blank screen - logcat attached
Hi.. I am attaching the logcat output when I run into this blank screen issue. The phone itself works perfectly fine. I used Android Screencast and was able to see everything working properly. Still puzzled on the issue!!
This is the logcat after flashing MIUI 1.9.30. Again, I flash wildmonk 2.6.35.4 kernel and everything works perfectly fine.
Can someone look into the logcat and see if anything could be found? Any help would be really appreciated!

ravindran_eee said:
Hi.. I am attaching the logcat output when I run into this blank screen issue. The phone itself works perfectly fine. I used Android Screencast and was able to see everything working properly. Still puzzled on the issue!!
This is the logcat after flashing MIUI 1.9.30. Again, I flash wildmonk 2.6.35.4 kernel and everything works perfectly fine.
Can someone look into the logcat and see if anything could be found? Any help would be really appreciated!
Click to expand...
Click to collapse
Hi.. Can someone help me?

Related

[Q] having trouble installing custom rom

guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??
djbenny1 said:
guys i was able to s-off and root my IS last night with help from alpha rev x.
i then attempted to install custom rom using CWM recovery.
inside recovery i can install the rom fine, it says its installed, aswell as no-sense 1.5 - there are no errors.
but when i go to reboot again, it just sits on the htc boot screen and i have to pull battery to get back into recovery.
please help
is it possible ive bricked my phone??
Click to expand...
Click to collapse
I think it's to do with the radio, someone said that in the alpharevx chat.
did they say how to fix?
is it in the alpharev x thread?
can you link?
how long do you wait for the white htc screen?
I took quite a while for it to load, ill say try reboot and wait for 30 mins
and make sure u have ext4 if the rom require ext4
and i dont think that your phone is bricked
same here...
hi, i am in the same boat as you are. I s-offed through alpharevx, great work btw! I also rooted through superoneclick by means of gingerbreak, also great work! thank these guys so much. Here comes the problem. I downloaded rom manager from the market and installed clockworkmod recovery through that. and i attempted to load a custom rom through the recovery tool. it went fine without any error. however, when i try to reboot, i get the htc logo on white background.... I flashed partition using ext4 formatting tool from here, http://forum.xda-developers.com/showthread.php?t=1088498 , i also flashed the radio specified in this post....but same thing, stuck at "htc"... help...
you have to install 4EXTRecovery_v1.0.6_modded_CWMR_v4.0.0 first. you can find the steps here: http://forum.xda-developers.com/showthread.php?t=1104765. when I tried with just Format_data_partition_EXT4 I got the same results as you
Thank you! I tried the other recovery you mentioned. worked like a charm! Thanks.
once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?
gmarcoux said:
once you've flashed, let me know if you still have earpiece volume with the custom rom. And if you do, did you flash a new radio?
Click to expand...
Click to collapse
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call
kakawong said:
I lost the earpiece volume too, no matter How I change different Radio, still cannot get it back, now I got a phone cannot make a phone call
Click to expand...
Click to collapse
Thats not right ... which rom? If its ARHD ... then did you try the AU radio linked in the first post?
That will surely give you sound on ARHD ...
Sent from my Incredible S using XDA App

[Q] Use of custom kernel over stock ICS rom

is it possible to install Holics Kernel or Feux in my stock ICS rom?
I've read a lot but cant find any instruction or something consistent about custom kernels over stock roms for the Vivid
If its possible, where can I find the stock kernel, or how do I make a kernel backup
You sure can. You just need to unlock your bootloader, flash a custom recovery, and if you want to make your life easier, S-OFF. Check the superguide sticky thread in the dev forum. Everything you need to know to unlock, S-OFF and root are in there. It's pretty darn easy.
Once you're unlocked, if you stay S-ON, you need a kernel in boot.img format, which you will flash using fastboot. If you're S-OFF, you can use an S-ON kernel, or you can simply flash the S-OFF version in recovery. This is much easier, especially when using a kernel like Faux's or Holics, as there are modules which also must be moved into the /system dir along with flashing the boot.img.
Once you have the custom recovery installed, it's very easy to do a back up and restore. Pretty much two clicks. I recommend using the TWRP recovery. It has a touch interface, and supports backups larger than 2GB. I haven't had a single problem with it since I started using it. Ask google about "TWRP Recovery Download" and you can download the recovery image directly from their site and flash it using fastboot.
Just a warning, unlocking your bootloader WILL destroy all your data. It is the same as doing a factory reset, so make sure you back up your contacts and things. Your SD card will not be touched, so you files on the SD are safe and sound.
Thank you Ess.
I've installed your modded Holics Rom, which is great.
But I have a rare issue, the screen goes black, but FM radio still on.
And had 2 random resets
Can you help me?
Sago6 said:
Thank you Ess.
I've installed your modded Holics Rom, which is great.
But I have a rare issue, the screen goes black, but FM radio still on.
And had 2 random resets
Can you help me?
Click to expand...
Click to collapse
Hmm, I haven't really used the radio app, so I can't really speak to that. I haven't heard any issues surrounding it though...
Is that when the resets are occurring? I remember having a random reboot soon after installing Holics, but it only ever happened once, and I believe it was when I went to unlock the phone really fast. I probably hit the sweep to wake twice, then the button a few times. The screen would power up but everything was black, then it rebooted. Since it only ever happened once, I chalked it up to fluke and didn't think about it again.
Can you describe what may have been running, or what actions you were preforming when the resets occurred? I can try to replicate it if you can provide the steps.
ess.boyer said:
Hmm, I haven't really used the radio app, so I can't really speak to that. I haven't heard any issues surrounding it though...
Is that when the resets are occurring? I remember having a random reboot soon after installing Holics, but it only ever happened once, and I believe it was when I went to unlock the phone really fast. I probably hit the sweep to wake twice, then the button a few times. The screen would power up but everything was black, then it rebooted. Since it only ever happened once, I chalked it up to fluke and didn't think about it again.
Can you describe what may have been running, or what actions you were preforming when the resets occurred? I can try to replicate it if you can provide the steps.
Click to expand...
Click to collapse
The first time I was using just whatsapp on 4G connection, but maybe its the "unlock-thingy" u said, doing it too fast =
The screen just turn black and I removed the battery to reboot
The second time i was using facebook app, whatsapp and radio, randomly freezed and rebooted
And thats all, everything its going really good.
In the main post (#1) there is a patch for
PATCH (try to flash on recovery)
Fixed reboot when screen off was used
Click to expand...
Click to collapse
Im sure the "screen off" thing was on
Sago6 said:
The first time I was using just whatsapp on 4G connection, but maybe its the "unlock-thingy" u said, doing it too fast =
The screen just turn black and I removed the battery to reboot
The second time i was using facebook app, whatsapp and radio, randomly freezed and rebooted
And thats all, everything its going really good.
In the main post (#1) there is a patch for
Im sure the "screen off" thing was on
Click to expand...
Click to collapse
I believe that patch was for one of the beta versions, and should be unnecessary for version 1.2 or 1.3,
After almost 3 days, there is no sign of random reboots or failures.
Re-flashed ROM and kernel cause of S-off procedure.
And now im getting like 7-8 hrs of battery in good use.
TY Ess.

[Q] Touchreecn unresponsive after flashing back to stock

I realize this isn't the developer section and that there is a risk in flashing roms.
I had downloaded rom manager and for some reason went on to flashing cwm for the S3.
The camera stayed in a boot loop.
I reflashed a recovery image, twrp, and then went on to clearing cache and doing a data/factory rest (I may have lost the usb debugging in the midst?)
I reflashed a stock rom, all flashing process is fine, the camera boots, hardware keys wok, only problem is the touchscreen is unresponsive.
Any files I can provide to help solve this bad move on my part, or is it toast?
Thanks.
I've managed to hook up a mouse with OTG cable so I can at least do something with it, but I sure hope I can find a fix for this besides having to send it to samsung for repair.
Are there any files I can provide to see if anything looks out of place, build.prop maybe? I really don't know where to start with this.
morbs_gt said:
I've managed to hook up a mouse with OTG cable so I can at least do something with it, but I sure hope I can find a fix for this besides having to send it to samsung for repair.
Are there any files I can provide to see if anything looks out of place, build.prop maybe? I really don't know where to start with this.
Click to expand...
Click to collapse
Have you tried the toolkit here: http://forum.xda-developers.com/showthread.php?t=2099765
You could flash a stock recovery / ROM
I have used this guys toolkit on other devices and they are easy to use and are rock solid.
apprentice said:
Have you tried the toolkit here: http://forum.xda-developers.com/showthread.php?t=2099765
You could flash a stock recovery / ROM
I have used this guys toolkit on other devices and they are easy to use and are rock solid.
Click to expand...
Click to collapse
Yes, I have his toolkit as well. I've used it for my SGS before.
The thing is I may need to flash the original rom, which is from New Zealand. I found the file on sammobile, just the first download I think was corrupt as it would fail md5 checksum and odin wouldn't flash it. I just downloaded another copy of the NZ rom version and am currently trying that out.
Any other version of the original rom i tried, the touchscreen wouldn`t work. The camera is brand new so I`m hoping it`s just software related.
*edit: I just flashed the original rom with odin, touchscreen is still no working. I`ll try the toolit again and see what gives.
u think it might be a kernel issue ? try and reflash the kernel.
pileiba said:
u think it might be a kernel issue ? try and reflash the kernel.
Click to expand...
Click to collapse
I really don`t know what happened, besides the fact that I flashed a recovery that was clearly not meant for the galaxy camera, lesson learned.
I realized my 14 day return was still in effect, so I just returned it to the shop and got a new one. :S
morbs_gt said:
I really don`t know what happened, besides the fact that I flashed a recovery that was clearly not meant for the galaxy camera, lesson learned.
I realized my 14 day return was still in effect, so I just returned it to the shop and got a new one. :S
Click to expand...
Click to collapse
I made the same mistake! I have no 14 day return thing with my device.
PLEASE HELP!
Hi;
I had downloaded CWM rom manager and for some reason went on to flashing cwm for the S3.
Camera restarting and then touchscreen doesnt work. Buttons are working but touchscreen isn't.
Anybody help me?
Please..
I've managed to hook up a mouse with OTG cable too. I hope install new CWM SGC rom. But there is no rom in CWM.
I think we can install touchscreen driver, But where?

Data Connection Issue

Hi
I rooted my phone 2 days back and installed Trickdroid ROM, since then i am facing issues with data connection... This is what happens:
It works for a while and then just stops receiving data.. the sending data arrow blinks (with HSPDA) but the receiving doesn't. If i turn the data off and on again.. it again works for a while.
To troubleshoot: I flashed the ROM again (full wipe, even at first it was full wipe); nothing changed.> I deleted my APN settings and manually added new settings (VODAFONE), still the same... works for a while and stops.
Then i installed Ordroid ROM... same issue.. tried everything.
This was working perfectly when i got my device and was stock.
i can't say that it's 4.2.2 or anything cause my friends did the same and they don't have issues.
Now need some expert advice as to what went wrong.
p.s.: WiFi works perfectly.
You can try updating the radio firmware as this may be the problem but this may or may not 100% fix it as your case seems isolated (not many other complaints). May just be your carrier upgrading stuff also.
You can try full wiping again. It might fix your data problem.
Heres the link for the radios
http://forum.xda-developers.com/showthread.php?t=2183023&page=2317
about halfway down youll find them I just updated to the .24 fw and have seen a slight performance (ATT)
I dont know if you need s-off or not since i am s-off to update these through recovery but even with s-off i couldn't update through adb
mcfool123 said:
You can try updating the radio firmware as this may be the problem but this may or may not 100% fix it as your case seems isolated (not many other complaints). May just be your carrier upgrading stuff also.
Click to expand...
Click to collapse
Will try this.
demongrim said:
You can try full wiping again. It might fix your data problem.
Click to expand...
Click to collapse
I've done my share of full wipes to try to fix this problem... 5 to be exact.. and I am on my 3rd ROM
mcfool123 said:
Heres the link for the radios
http://forum.xda-developers.com/showthread.php?t=2183023&page=2317
about halfway down youll find them I just updated to the .24 fw and have seen a slight performance (ATT)
I dont know if you need s-off or not since i am s-off to update these through recovery but even with s-off i couldn't update through adb
Click to expand...
Click to collapse
Which one should i be choosing?? I am on vodafone india. Also can i just flash through CWM? i am not soff.
I'd try the .24 just since its the newest. I don't know if it will work with S-On since I am s-off. You can give it a try but you can easily set s-off if you need to with revolution. I renamed the zip download to radio.zip and flashed it with twrp so cwm should also work. Just check to make sure theres no problem with putting it on your phone which there should be none and this may fix it since it relates straight to the radio.
mcfool123 said:
I'd try the .24 just since its the newest. I don't know if it will work with S-On since I am s-off. You can give it a try but you can easily set s-off if you need to with revolution. I renamed the zip download to radio.zip and flashed it with twrp so cwm should also work. Just check to make sure theres no problem with putting it on your phone which there should be none and this may fix it since it relates straight to the radio.
Click to expand...
Click to collapse
Flashed the radio. 24. Let's see results now.
I've got the same issues.... I flash the Rom ARHD 10.1 then back to 9.4 be cause i don't like the 4.2.2 sense rom.
I try to change the radio with the 3 .zip avalaible and nothing change. I'll try to full wipe my one today, and do a factory reset..
ps: excuse my english..
Issue persists... what else guys?
vinaymieux said:
Issue persists... what else guys?
Click to expand...
Click to collapse
Sorry its been a while was just wondering have you tried your stock image again to see if the problems goes away when flashed back to that.

TWRP 2.6.3.0 constantly crashing (SOLVED)

I've been using TWRP ever since I have rooted mt ONE. Over the last few days its been crashing while trying to install any zips at all.I can do a nandroid restore but nothing else. When I try to install any file it just goes to a black screen and reboots the phone.
Any ideas of what could be causing this and how to repair it also.
Thanks
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
potsykate said:
I've also just replaced TWRP with clockwork mod touch and that is doing the same thing. I am now at a stage where I cannot install anything via the recovery method.
What is my bet options for starting afresh as my phone is unlocked with HTC dev and rooted also.
I'd like to go back to the beginning and start again.
Thanks
Click to expand...
Click to collapse
This seems to becoming a more and more recurrent event, though I cannot say for what the correct solution is, check these two threads:
http://forum.xda-developers.com/showthread.php?t=2435499
http://forum.xda-developers.com/showthread.php?t=2423817
one of them had to fix a corrupt partition, the other just reflashed and wiped again and again, and it worked.
If something works out for you do share!!
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
potsykate said:
Thanks for that,I'll redownload my favourite Rom and try again without trying to update the Kernel,everything was fine as I remember before I tried the kernel update.
I'll let you know how I get on in a while.
Click to expand...
Click to collapse
Though the reasons are still unclear (at least to me ), it seems that flashing a custom kernel while still in recovery immediately after the ROM does work. Of course, make sure you're flashing a compatible kernel to the ROM; the version numbers of the custom kernels do not correspond to the ROM versions, and I've seen some that flashed an incompatible kernel, just because the version numbers looked similar.
Good luck & keep us posted
PS: If you do solve it, please update the main thread title to include [SOLVED]. thanks
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
potsykate said:
Thanks for the two links,after reading them and doing a fresh install off my rom. Wiping cache,delvick and data I seem to be able to install zips again from recovery without the black screen and reboots.
Yep, so far all the zips that failed earlier are now installing.
A BIG THANK YOU :good::good:
Click to expand...
Click to collapse
Excellent
Edit the main thread title to include [SOLVED] so that others can refer to it :victory:

Categories

Resources