I installed a new 5.1 rom and now when I boot up I only get a black screen. If I press and hold the power button I get a notification asking me if I want to power off my device. So I know the screen works. It works fine in recovery and the boot screen.
Did I not format a partition properly? I have tried 2 different roms and they both do the same thing.
Thank you
It works now. I have no idea what I did. I just installed a rom again and it work.
I almost think it had something to do with the new security thing for android when your phone gets stolen.
Kinda sounds like the ROM did not install correctly, glad you got it working with another flash!
Sent from my Nexus 6
choder said:
I installed a new 5.1 rom and now when I boot up I only get a black screen. If I press and hold the power button I get a notification asking me if I want to power off my device. So I know the screen works. It works fine in recovery and the boot screen.
Did I not format a partition properly? I have tried 2 different roms and they both do the same thing.
Thank you
Click to expand...
Click to collapse
Don't downgrade to 5.0.X or you will be bricked.
Sent from my Nexus 6 using XDA Free mobile app
The same thing is happening to me..
Same here. I even flashed stock LMY47E to make sure the radio and bootloader were installed ok. Any time I wipe a 5.1 rom and install another (or even the same ROM), I get a black screen after it boots. What is weird though is if I flash a 5.02 rom (I flashed Terminus) and then wipe, it loads fine.
#BlackScreenOS
Sent from my Z970 using Tapatalk
Jess813 said:
Don't downgrade to 5.0.X or you will be bricked.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
How can that brick a Nexus? I would think flashing any supported version would run just fine being a Nexus and all?
Related
So I have a bit of an issue. Over the weekend my power button stopped working like it has for many people.
I finally got to a computer last night and was able to turn it on using a method I had read about.
I was using madaco's desire port but I didn't have the option for wake with trackball baked into it. Which I need to have my phone usable. So I had another ROM baked on his site with that option in it but I forgot to tick the option to have the .zip signed. (I'm using an older recovery, had been to lazy to update)
I didn't realized it wasn't signed until I had go into recovery, wiped everything and then attempted to flash at which time it said no because it wasn't signed. So I said F it I'll do it in the morning.
So today I realized I can't boot the phone up because I had wiped everything, including the ext partition. It just sits at the X screen with the unlocked paddle lock on it. Due to this I can't access it with ADB to get to recovery.
If I restart the phone and put it into HBOOT I can't select recovery because you have to press the power button to select the option.
I also tried finding a fastboot command to boot into recovery but didn't locate one.
SOO
Does anyone have a clue how I can get this damn thing into recovery? I'm normally really good with this stuff but I am stumped at this point.
And before anyone says it I can't exchange it because my screen is cracked.
If you can grab a kernel and and recovery image on your PC you can boot them using
fastboot boot <kernel image> <recovery image>
Is that going to get me to a point where I can flash a new rom on it? I was running all of my cache on SD so when I wiped it is messed the rom up.
It already has Amon_RA recovery on it, the release prior to the newest one. So do I really need to flash another one to it?
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
danger-rat said:
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah that's the route I'm thinking about taking. But I think there are option you have to use the power button to confirm.
I'm messing around with different boot.img right now to try and get it to boot. If I could just get the damn thing to boot I'd be all set cause I can use adb from that point. But right now when it stops at the X screen ADB can detected the phone but if you try to access the shell you get "failed to link /system/bin/sh
Thanks for the input man
If your bootloader is unlocked, you can re-image with fastboot.
Also, if you're not unlocked, I'm pretty sure the passimg only selects options with the volume keys...
Sent from my Nexus One using XDA App
I went with the superboot method. When I ran the .bat files it restarted the device and put it into recovery. I flashed a fresh ROM from there.
It's made it to the boot animation so I'll see if it fully boots up in a minute .
Okay, I'm back in action. Thanks for the in put guys.
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
danger-rat said:
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm pretty sure you do. It says you'll probably need to as a foot note in the directions for superboot.
I may be wrong, I haven't kept up on much relating to rooting the Nexus since it first came out.
I think you're probably right... Thanks!
Sent from my Nexus One using XDA App
I was trying to restore my phone to previous state using Rom Manager. Phone restarted in recovery mode, formatted the boot partition and failed to restore. I applied existing of CWM ROM update.zip and snce then my phone restarts in Recovery mode everytime.
I tried one click restore using ODIN, Heimdall nothing worked. recreated the partitions wiped everything, loaded stock ROM but still the phone boots up in recovery mode.
Please suggest some pointers on how to troubleshoot this problem.
peachsun.v said:
I tried one click restore using ODIN, Heimdall nothing worked. recreated the partitions wiped everything, loaded stock ROM but still the phone boots up in recovery mode.
Please suggest some pointers on how to troubleshoot this problem.
Click to expand...
Click to collapse
do you mean the one click for installing stock rom or something else?
I had the same problem a few days ago couldn't figure it Out. searched and searched for the right image
Files for my Nexsus S. I ended up wiping everything and flashed all the image files with TRWP cause CWR wouldn't work
for the stock ICS and and it worked fine. Now I'm running the 4.1.1 jellybean it sweet.Hope this helps.
Sent from my Nexus S using Tapatalk 2
irfarf said:
do you mean the one click for installing stock rom or something else?
Click to expand...
Click to collapse
Yes the one click package for installing Stock ROM. it did repartitioning, wiped all data, loaded everything successfully. but after booting it shows up the recovery screen.
peachsun.v said:
Yes the one click package for installing Stock ROM. it did repartitioning, wiped all data, loaded everything successfully. but after booting it shows up the recovery screen.
Click to expand...
Click to collapse
Hmmm... i've heard of cases where the power button on the captivate refuses to be 'unpressed' which makes it boots up just by plugging in the battery,
Maybe it's like that with your volume buttons?
Does it feels a little bit weird like it doesn't click when you press it?
Sent from my SGH-I897 using xda app-developers app
irfarf said:
Hmmm... i've heard of cases where the power button on the captivate refuses to be 'unpressed' which makes it boots up just by plugging in the battery,
Maybe it's like that with your volume buttons?
Does it feels a little bit weird like it doesn't click when you press it?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Thats a good point...
The buttons seem to be normal. I tried keytest and the results look fine
Volume Up : 115
Volume Down : 114
Power : 116
Menu : 139
Home : 102
Search : 217
Back : 158
Moreover I can access recovery and flash any ROM that I have on SDCard. Funny part whenever I flash a new ROM I see a new recovery
Do you know of anyway use ADB without booting phone and putting it in debugging mode?
Thanks for your inputs.
Update: Issue is resolved
I'm not sure on exactly what worked. Using System Corps Recovery, I changed all the partitions to ext4. Made some random changes to toggles during boot. Restarted in download mode and flashed a one click stock rom from http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
it booted in recovery, then clicked on Flash Bootloader in one click and restarted the phone in download mode and flashed it again with the same ROM.
Thats it. I feel that Bootloader did the trick, but I had it flashed earlier as well.
Thanks irfarf & Sammyazel for your inputs on this.
peachsun.v said:
Update: Issue is resolved
I'm not sure on exactly what worked. Using System Corps Recovery, I changed all the partitions to ext4. Made some random changes to toggles during boot. Restarted in download mode and flashed a one click stock rom from http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
it booted in recovery, then clicked on Flash Bootloader in one click and restarted the phone in download mode and flashed it again with the same ROM.
Thats it. I feel that Bootloader did the trick, but I had it flashed earlier as well.
Thanks irfarf & Sammyazel for your inputs on this.
Click to expand...
Click to collapse
congrats!!
i do also think that it was the boot loader is the problem here
i had a few problem with my friends cappy won't go into download mode and whenever it boots up, it shows a bunch of random colors than a boot image. turns out that the last bootloader flash wasn't done correctly or something.
Confirmed - the problem is with the bootloader. Once I flashed an original firmware from Samsung, I was then able to install CWM and any ROM I wish after that. Not sure what caused the problem, but this was the solution in my case. Thanks to everyone who pointed me in the right direction!!!
Hi,I am new to android world.....i am having the same issue...My zte blade is always booting into recovery mode....
Can anyone help me what to do now????
venkin304 said:
Hi,I am new to android world.....i am having the same issue...My zte blade is always booting into recovery mode....
Can anyone help me what to do now????
Click to expand...
Click to collapse
U may have a stuck or malfunctioning power button.
Sent from my SAMSUNG-SGH-I897 using xda premium
venkin304 said:
Hi,I am new to android world.....i am having the same issue...My zte blade is always booting into recovery mode....
Can anyone help me what to do now????
Click to expand...
Click to collapse
Try running the keytest from recovery mode to ensure all the keys are working fine.
In my case it was corrupt bootloader that caused this issue. you can try flashing stock ROM with bootloaders to fix it.
All the best!
i have same problem. buttons work ok after key test.
how can i reinstall the bootloader?
ps: i hate this stuff.....reminds me of win95/98......awefull times
am06 said:
i have same problem. buttons work ok after key test.
how can i reinstall the bootloader?
ps: i hate this stuff.....reminds me of win95/98......awefull times
Click to expand...
Click to collapse
Whats the model of your phone?
am06 said:
i have same problem. buttons work ok after key test.
how can i reinstall the bootloader?
ps: i hate this stuff.....reminds me of win95/98......awefull times
Click to expand...
Click to collapse
What exactly did you do to get to this point?
You can find Odin KK4 with bootloaders here: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
You will need to flash corn kernel with Odin 1.85 afterwards if you wanna flash a custom ROM.
Hey needing abit of help here
last night i rooted my xperia Z and installed CWM the locked bootloader way
after the cwm finishes installing the phone boots into cwm right away and all works fine...however...
i read on how to boot to recovery myself by turning the phone on and when the LED'S start changing colour to keep pushing the volume up key.
for some reason my when booting my LED goes green and stays green and the phone boots straight away normally so if i want to access cwm i have to keep flashing it to the phone first but i dont get why.
am i missing something here or have you any idea whats went wrong?
please help
thanks
Install the XZRecovery.apk and use the Reboot Recovery option.
XperienceD said:
Install the XZRecovery.apk and use the Reboot Recovery option.
Click to expand...
Click to collapse
thanks i will give that a go
It's known to be a bit iffy on a LB but the app for me has been consistent.
XperienceD said:
It's known to be a bit iffy on a LB but the app for me has been consistent.
Click to expand...
Click to collapse
app works great m8 thanks alot.
although i have a question. what if the phone was to be stuck in a boot loop or suffered from a soft brick and i needed to boot to recovery to fix it what then?. i dont get why everyone elses xperia z's start changing led colour on boot up but mines goes green n doesnt change lol
xEpiKxXperIAx said:
app works great m8 thanks alot.
although i have a question. what if the phone was to be stuck in a boot loop or suffered from a soft brick and i needed to boot to recovery to fix it what then?
Click to expand...
Click to collapse
If you haven't managed to get it installed from the computer then unfortunately you need to reflash and start all over if that happens, or at least to getting rooted and CWM reinstalled then you can just flash your backup.
I ran into a bootloop after flashing a mod my phone didn't like lol. I used the Sony update service to flash the firmware back again although it failed 1st time then I had to get the pc to pick up the phone and thank god it did I started again. So I rooted the phone again and flashed twrp using the app you recommended. But still when the phone boots up the LED doesn't change colour it just stays off or goes green on boot up. But I have the extended boot options to get into recovery mode now so it's all good. But thank you for your help m8
Sent from my C6603 using XDA Premium 4 mobile app
Have a search for Doomlords reboot wrapper. I had to install it when I was in exactly the same situation as you.
Sent from my C6603 using xda app-developers app
Hello
I was looking forward to flashing my S3 Mini with Novafusions CM11.1 but i have problems with after install TWRP recovery that my back and menu buttons (next to the home hardware button) dont work.
I cant get it to work even when i flash to stock recovery and rom:crying:
Does anybody have a solution?
Something to do with the keyboard app or is it a problem outside Android?
Sent from my GT-I8190N using XDA Free mobile app
KoolKid98189 said:
Something to do with the keyboard app or is it a problem outside Android?
Sent from my GT-I8190N using XDA Free mobile app
Click to expand...
Click to collapse
Its in recovery and rom. I can type fine its just that the touch buttons "hardware buttons" doesnt work.
hedgegee said:
Its in recovery and rom. I can type fine its just that the touch buttons "hardware buttons" doesnt work.
Click to expand...
Click to collapse
Could be hardware fault? Since when did this start happening?
By any chance before flashing a custom rom did you turn button backlight off? If so, flash a stock/based rom, turn them on and flash your custom rom.
At least this solved for me 2 days ago which happened for the first time.
KoolKid98189 said:
Could be hardware fault? Since when did this start happening?
Click to expand...
Click to collapse
No its a brand new phone and it works on stock rom fine. It starts happening when i flash to anything other than stock based rom. I will type in the response i gave in the TWRP topic
KoolKid98189 said:
Could be hardware fault? Since when did this start happening?
Click to expand...
Click to collapse
heithered said:
By any chance before flashing a custom rom did you turn button backlight off? If so, flash a stock/based rom, turn them on and flash your custom rom.
At least this solved for me 2 days ago which happened for the first time.
Click to expand...
Click to collapse
Thanks for the tip but no unfourtnately i didnt - i saw a topic after i posted that there are problems on some phones with these rom/recovery. :crying:
I posted this in the TWRP recovery topic:
I was on the CM11 rom and it is the same with any rom based on anything other than stock rom.
They blink a couple of times in the recovery and don't work at all in recovery but there are softkeys. In the rom/system it will take 30 seconds to a minute to work and they will blink until they work randomly.
I got it to work by flashing everything stock again (i had a wrong stock rom i think).
After i flash the TWRP or any other recovery the buttons will act weird and take about 30 seconds to a minute to work in the stock rom or any other stock based rom.
The buttons don't work in any other nonstock based rom on my I8190N.
Is there a fix to this?
Click to expand...
Click to collapse
I will see if there is any fix to this.
so i bought this phone online and it was stuck at Samsung logo so i flashed NC2 via odin and it came back up...... YAY !!
however there's a new set of issues i have to deal with and i cant figure it out because i've tried like 6 roms now and i cant downgrade because of this dumb fuse thing on the N900a
so im stuck with the 4.4.2 roms
however the Problems are:
1. entering camera, it shows black screen then says "warning: camera failed".
2. entering the phone dialler it takes seconds to respond
3. music is freezes
4. unlocking the phone it takes seconds to open
5.wakelock takes seconds also to respond
6. no sound
has anyone any idea whats causing this ?
thanks in advance
Sounds like bad flash. Try to clear everything in stock recovery and flash Odin files again.
Sent from my SAMSUNG-SM-N910A using XDA Premium HD app
norbarb said:
Sounds like bad flash. Try to clear everything in stock recovery and flash Odin files again.
Sent from my SAMSUNG-SM-N910A using XDA Premium HD app
Click to expand...
Click to collapse
thanks for the reply , i did that and flashed all odin files as as well as custom roms , all dont display camera and have same issues ,
still not working , any advice guys