Hi,
A few months ago I installed The Italian Job 1.0 rom on my device. Everything went smooth had no problems. But a few weeks ago I wanted to update my rom. I tried booting into recovery but the following occurred: I received the message if I wanted to continue. I pressed the volume up button to continue. The next screen is the loading screen before the recovery. With the following message 'Downloading... Do not turn off target !!'. But nothing happens. Not even after an hour. I have no idea what's wrong. I can still boot into android and use my device and all the features with it.
I googled the problem but I found nothing to solve the problem. Maybe you guys have an idea?
Greetings
Thulium
You entered to download mod. Recovery mode combo is vol up+ home + power. You probably used col down instead of up
Sent from my GT-I8160
Oh wow, I feel like retard. Thanks for the fast reply!
Related
I upgraded from 2.51.1 to 3.4.2-117, and the phone lags, seems to me that it is because of the google sync. Someone posted the very same problem and said that factory reset solved his problem.
My problem is that the phone does not do factory reset, in Privacy I press the erase button and nothing happens.
I tried to boot into recovery, but I can't get into it. The droid comes up but upon touching the lower right corner nothing happens.
When i try to boot with vol up and down same time, the phone boots into safe mode.
How shall I get into recovery so I could do a wipe? The phone is basically unuseable now because of the lags and freezes
Hey mate! Don't give up. When you see the droid in the center of the lcd just push vol+ and vol- at once. You'll get into recovery mode. )))
thx dude, i figured it out "accidentaly"
Everyone was writing on the net that the recovery boot is up and down the same time instead of the old method of power & volume -.
So, when I got to the droid, started to push every possible button in every possible variation and I got in.
since then I learned that the vol up and down is after power & vol -, not instead.
Hi guys,
As the title says, I've tried flashing in a new/last IceColdSandwich 8.7 AOKP last night. I've been running that mod since... well v4.x or something, never had any problems flashing it.
Procedure: the usual, download the rom, check the checksum, start the Rom Manager and install the ROM from SD, nothing weird.
This time tho I'm stuck at the white HTC screen. Any options? I tried volume-down/power switch boot but it's the same result, nothing happens.
It's worth noting that I had some issues with unresponsive volume button, but I think I'd get it right once in those 20-ish times I tried.
Any ideas?
Thanx in advance...
Try to type "adb reboot recovery" when on white HTC screen if you got adb installed.
Muikkuman said:
Try to type "adb reboot recovery" when on white HTC screen if you got adb installed.
Click to expand...
Click to collapse
Hi, thank for the answer...
I just get error: device not found
It's pretty weird, I used the same machine to perform rooting and all that long time ago so drivers should work. I guess I'll have to refresh those first. While I'm at it, are there any new/important/must have drivers I should use?
If I never get to HBOOT while holding volume-down + power, is that a good sign that my volume button is screwed up or can it be something else/worse?
Ok, it's fixed now...
Extremely weird that it got screwed up, it was a really stable rom. And it looks as stable now when I got it running.
I tried installing new sdk and drivers abd stuff, but just got tired of it and went loco on the volume thingie. Extremely flimsy solution, but after some buttkicking thete was suddenly a contact every now and then. After some 10 - 15 attempts to press volume-down + power button I've got it working.
Installing a rom was a snap after that. Still think it was a weird glitch trat it died on me last night.
Thank You for watching anyway
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Sacrifusion said:
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Click to expand...
Click to collapse
IMHO, it looks like faulty slider flex cable (exact same situation i had, but i was able to enter recovery after 2 minutes of logo on screen)
Try to power on phone with slider open.
If you can enter in recovery mode with "volume -" (if it light blue led or vibrate) and see is d-pad is working.
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Sacrifusion said:
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Click to expand...
Click to collapse
To be able to enter recovery, it is not "holding volume-" while powering on phone or keeping it pressed.
Press power button (and it should vibrate), and release it.
When blue led is on press and release vol- button many times untill you enter recovery (don't keep it pressed all time)
Ah, you are absolutely right. I've never entered recovery like that on another Android before. I loaded up the "near perfect" rom and my game pad seems to be working for now, so it appears I am back in business.
How problematic is it if my slider flex cable is going bad? Will it permanently fail eventually?
My Pixel C is fully changed but the screen is black and won't display anything at all. I know it is on because I can take screenshots with the hardware button and hear the noise. I can also see it on Android Device Manager. I have long pressed with all the different button combinations. It reboots but the screen shows NOTHING (not even the Google boot logo).
Any ideas would be greatly appreciated!
It is stock and not rooted but subscribed to the Beta channel.
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
mightywhites29111971 said:
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
Click to expand...
Click to collapse
I didn't elect to install O. I didn't see the update notification in the last couple weeks before it had this problem.
I can't get to recovery because the screen is off. How did you do it? Or were you able to see the screen after holding the volume down button as well as the power button to get into recovery mode?
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
mightywhites29111971 said:
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
Click to expand...
Click to collapse
Thank you for your reply. Unfortunately, that is not working. I have tried holding for 60 seconds just to be sure. It is so strange!
Not sure what it is in that case. Have you tried the volume up button to get fast boot mode?
I am having this problem aswel, on the android O beta. I can not use it and I can not see the bootloader when holding down power + volume down
edit: resolved the issue by trying button combinations until it booted (took around 2 hours total with time of disappointment in between)
edit2: oh my ****ing god it booted correctly (showed bootloader warning + bootlogo + lockscreen) but it locked and now it's black again!
edit3: was able to get into fastboot after 3 tries so i'm flashing the factory image right now (7.1.2)
edit4: flashed 7.1.2 factory image and was able to fastboot boot into twrp but still no display.
edit5: i am now troubleshooting i checked all the files in /sys/devices/50000000.host1x/54400000.dsi/54400000.dsi.0/backlight/lpm102a188a-backlight/ they all indicate 255 which is 100% anyone have any ideas?
final edit: i fixed it by trying a **** ton of times
Hello,
Can you tell what have you do to repair the pixel? Have the same issues after Oreo update :/
Anyone found a way to fix permanently? Mine started doing it around Christmas 2018, and it takes more and more tries every time (to ctrl-down power) and at some point it works... Then all stays fine until I close the lid or put it to seep.
Did someone reinstalled completly the os and got a success? I am not rooted, this started when It tried (and failed) to install 8.1 (update of oreo).
Hello Everyone,
So Redmi Note 8 was working fine. For the last few days randomly the Volume Icon Appears on the screen and doesn't go away until I press volume down. I think this issue is related to the Volume Up Button. sometimes it doesn't work.
A day ago it got an update so I tried to update it.. after download it restarted and was loading .. got stuck on 4.99% for a while then restarted itself into the recovery menu. no matter how many times I tried to reboot.. it just comes back to it..
after a while when I tried to reboot while holding down the volume down and the power button it rebooted. and was fine but still had the volume issue..
just a few mins ago it restarted and now again its stuck on the recovery menu..
I don't mind about data already backed up when it booted.
i don't really need it to be rooted.
Just want it to work.. also having a custom recovery is fine.
so what do I do for that?? I was looking through guides everything I found required enabling bootloader but my phone won't boot so no way to do that.. at least I don't know of any method.
if anyone can help me with it.. i will really appreciate it..
Thank you ^^
Edit: Its on a Loop now.. Stay on Recovery Menu for a few mins then restarts and goes back into the recovery menu. Been doing it over and over again.
Update:
I figured out the issue.. it was the volume button.. the volume up button was not working as mentioned.. but it seems it was stuck at the volume up position.. That was the reason why I had the Volume notification on screen all the time... and the reason why it kept going back to the recovery menu..
I replaced the Volume Button and now everything is good.
Thanks Everyone ^_^
Mark the thread "[SOLVED]" then?