[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
Hi,
I've locked my phone yesterday and I've found a problem that doesn't let me unlock the device. I couldn't unlock and reboot the phone, so I took off the battery and placed it on and started up the phone. It freezed again on the unlocking. Tried this a couple of times - same problem. It has no wallpaper, the SD card reacts very slowly, the network also, and the screen doesn't turn off by itself if you don't do it so. Sometimes I can't even answer a call, it shows somthing like "Application not responding. Wait/Force close". I doubt it's the HTC Sense broken down or something similar. Please help me, I need my phone very quickly!
P.S. The phone is NOT rooted
Thanks!
kdervisov said:
Hi,
I've locked my phone yesterday and I've found a problem that doesn't let me unlock the device. I couldn't unlock and reboot the phone, so I took off the battery and placed it on and started up the phone. It freezed again on the unlocking. Tried this a couple of times - same problem. It has no wallpaper, the SD card reacts very slowly, the network also, and the screen doesn't turn off by itself if you don't do it so. Sometimes I can't even answer a call, it shows somthing like "Application not responding. Wait/Force close". I doubt it's the HTC Sense broken down or something similar. Please help me, I need my phone very quickly!
P.S. The phone is NOT rooted
Thanks!
Click to expand...
Click to collapse
You will lose all your data by doing this.
Boot into the bootloader (power off, press and hold volume down, press and hold power).
Wait for some green writing to appear and then disappear (about 7 seconds).
Use the volume down button to navigate to "clear storage", then press power.
Once this is done, reboot the phone and hope for the best.
----------------
If this doesn't work, make a goldcard (google how to) with any other android phone you may have, insert the goldcard in your desire
download the latest WWE RUU (look on resources in my guide)
boot into fastboot mode (hold back & power) and plug it in via USB to your PC
Run RUU.exe and do not touch the phone til it completes.
bortak said:
You will lose all your data by doing this.
Boot into the bootloader (power off, press and hold volume down, press and hold power).
Wait for some green writing to appear and then disappear (about 7 seconds).
Use the volume down button to navigate to "clear storage", then press power.
Once this is done, reboot the phone and hope for the best.
----------------
If this doesn't work, make a goldcard (google how to) with any other android phone you may have, insert the goldcard in your desire
download the latest WWE RUU (look on resources in my guide)
boot into fastboot mode (hold back & power) and plug it in via USB to your PC
Run RUU.exe and do not touch the phone til it completes.
Click to expand...
Click to collapse
Well thanks man for the work, but I'm kinda n00b at all these phone system stuff, is there any other way that has less consequences than this, I mean, no losing all the data stored?
no, not without a properly functioning device.
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Hello, i don't know if my problem is the same but i have the power button don't work too. For restart my phone, i press VOL- when I charged the phone. He boot in recovery and next i reboot system. If a hardware solution is possible, tell me.
maj0r_tom said:
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Click to expand...
Click to collapse
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
tw9 said:
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
Click to expand...
Click to collapse
I have had same problem. I am not expert at all but can suggest you to check out your phone mother board. Problem might be there. Nothing will work if your phone motherboard is out of function. Thanks
Hi to all, yesterday I tried to root my phone following a guide here on XDA Developers (I don't remember which one). I have a Pixel 6 Pro and I tried to flash boot.img when the phone, after being restarted, starts to bootloop and then I try to turn it off. Then, the panic. The phone doesn't seem to be recognizable by ADB nor fastboot and the screen is permanently black. When I try to hold Power button and other combinations (while plugged to my PC) Windows emits some system sounds like "plugged" or "unplugged device" but I can't find my phone like recognizable.
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
xXx yYy said:
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
Click to expand...
Click to collapse
I can't interact with phone, I just see "Pixel ROM Recovery" on devices when I connect to my PC. I don't even know if it's in recovery, if it's on or off
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
simplepinoi177 said:
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
Click to expand...
Click to collapse
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Chexet48 said:
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Click to expand...
Click to collapse
First and foremost is seeing if you can get to Fastboot/Bootloader Mode; When your device is off and not connected to anything (at all, no cord connecting to PC or power plug or anything), hold the Power & Volume+Down buttons simultaneously for up to 2 minutes. If you cannot power on into this mode, you will not be able to flash your device's stock firmware to re-establish any system data that may have been corrupted. It is unlikely, but you may have other options if you can boot into Recovery Mode or somehow into the OS, but if you cannot get into Fastboot Mode, it is too unlikely that you would be able to boot into these. But if you are successful into loading Bootloader/Fastboot Mode...
There's two ways i would suggest you go about it...The first and easiest is to run the official Google Android Flash Tool -- You should be able to load up the latest factory firmware version for your device (Raven), and it should be able to flash the factory image onto your phone to get it working; BE SURE to check the "keep data" (or do not wipe; I can't recall off the top of my head) and to flash to both slots (just to be safe). The second way is to follow THIS GUIDE (as directed by roirraW "edor" ehT's Pixel 6 Pro guide who holds the defacto quintessential central guide in the Pixel 7 Pro forum in which is most up to date, but not catered to "raven") -- specifically you will find what is needed in the "Update and Root Factory Image" section; play close attention to the method using the "flash-all.bat" as that is the simplest and most straightforward way to go about it.. Please read everything and place close attention on being sure to go about it without "wiping" your device (removing the "-w" in the flash-all.bat file), else if you are able to recover your system, your data will not be there when coming back to it and everything would be factory reset.