Related
Hello,
I have a nexus one that isn't working anymore. I was trying to install the cyanogenmod, but I guess I didn't do it correctly.
I was following the clockworkmod way from this: h t t p ://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
When flashing the rom something went wrong. After step 6 my phone didnt reboot, it just stayed off. Now it will only give me the nexus sign if i turn on the phone.
I can still acces the recovery menu when holding Power + volume down.
People told that I should go back to the stock rom.
Can anybody please help me?
*don't know if i've posted in the right category
When you get to recovery is it still clockwork or stock? If clockwork then try and flash cm6 again. If not you will have to download a stock rom push it to the sdcard as an update.zip and boot into the boot loader.
Sent from my Galaxy Tab, that makes phone calls
Since you can boot into recovery you have NOT bricked it for sure
As mentioned in the earlier post try to flash the CM ROM again
If you are unable to access the custom recovery (as in, the stock recovery is still in place), you can follow the manual instructions for installing ClockworkMod: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide#Manual_Method
You can then follow the procedure for flashing the appropriate radio image: http://wiki.cyanogenmod.com/index.p...ll_Update_Guide#ClockworkMod_Recovery_process
And you can even install the ROM without using Rom Manager using this process: http://wiki.cyanogenmod.com/index.p...Update_Guide#Second_Method_.28via_Recovery.29
All of this is, as I'm sure you've noticed, posted on the same page that you linked. Hopefully this information will help you, now that you have been assured that your phone is not bricked.
Thanks for quick replies. I've contacted a guy with a lot of knowledge about these kind of thinks and helped me fixing me phone. I dont know exactly what went down but I will give it a try.
My first mistake was thinking that I rooted my phone (using the one click method). Don't know if thats the right way to do it, but in the end it wasn't rooted and I tought it was.
The guy rooted my phone, did the AmonRa recovery install and installed the Ethernom Rom for me. Great to have my phone back to working and great Rom btw.
Performed the Root procedure on my 1.0.1 and it worked fine (for a time being). Then the YouTube app wouldn't load. So I did the 3 button restore and the 8x restore. After the 8x restore, it got stuck in the loop. I tried the power + N reboot as well and it also didn't break it out of the loop.
Followed instructions from nookdevs.com/Flash_back_to_clean_stock_ROM
What do I do to break out of this? This is all new to me.
Considering taking it back to B&N and playing dumb. (sounds about right from what I've got myself into)
First of all, the Youtube thing is a common issue and easily fixed without doing a restore. I suggest you actually read next time instead of wiping clean.
You have to do both a data and system wipe. Do 8 failed boots and then after that wipe finishes do the home plus n button wipe.
Strange thing. Must be your bootctn which is corrupt. Try nookdevs adb command on restore to stock page when in nookie froyo to write to bootctn. Maybe this would end loop.
The command starts with "echo.."
You could also try recovery zip with clockwork recovery i. Xda dev, not sure it will make a difference though..
Sent from my HTC Desire using XDA App
Keep Trying
Take a look at my post if the suggestions and dev tools don't seem to help.
I say keep at it as I did.
http://forum.xda-developers.com/showpost.php?p=10675682&postcount=7
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
PoRco1x said:
Hey guys,
So I've been at this all day on another forum. Here is the link to ONE of the threads : (Edit removed, cant post links yet)
So I was trying to Flash to Android Revolution HD and it got stuck at 30% half way through the installation. This lasted a good 5 hours...
I finally managed to reboot the phone using "adb reboot bootloader"
But now I'm stuck on "HTC Quietly Brilliant" splash screen!
I JUST bought this phone last night off kijjiji and I'm reallly ****ting bricks now (no pun intended)
Any help whatsoever will be really appreciated
Added a screen shot of what it was stuck at a few minutes ago. I JUST managed to reboot it..but it's still stuck.
Click to expand...
Click to collapse
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Hey I got the phone to restart and it goes almost immediately into the HTC screen again. I think "fastboot" setting is on or something. I just can't get it to go to the bootloader
MacHackz said:
Hi, hold it under a bright light and hold down power until it turns off, then reboot into bootloader, select recovery, then reflash the ROM
Click to expand...
Click to collapse
Just tried it under my bright lamp too. No dice
Okay so I used Hansoons AIO toolkit to get it to load into CWM-based Recovery... phew
What's next!?
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
expertzero1 said:
you need to do this when in fastboot
type fastboot erase cache
just to be sure redownload his rom
Click to expand...
Click to collapse
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
PoRco1x said:
Not really sure how to get into fastboot. Will typing that command get me to fastboot and erase cache.
Here are my options now, using the Hasoon2000 AIO
1) Re-flash a recovery - ClockWorkMod, ClockworkMod Touch, TWRP AND THEN Install zip via sd card
2) Do above ^^ but install via sideload
3) Just erase cache with AIO and install zip from sim card
What should I do?
Click to expand...
Click to collapse
It doesn't matter, once you're in cwm recovery, reflash the Rom with a full wipe and you should be good. Calm down dude.
Sent from my HTC One using xda premium
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
What are you holding to try to enter bootloader? I use power and volume down and it works every time. Just hold them until the bootloader screen appears then let go.
Also, like others have said, it's better to use adb and fastboot commands yourself in cmd or terminal, rather than using the toolkit - it's not too hard, there are plenty of guides, you learn quicker and it's more satisfying
Sent from my HTC One using xda premium
ryryzz said:
just like the gentleman above said, you need to calm down first. If your phone can boot, although it hangs midway, it has a big chance not to be bricked in anyway.
And I don't advice you to use the AIO tools, just try to follow every simple guides to flash custom recovery-root-custom rom and you'll get familiar with the process in no time.
So I assume that you can boot into recovery, these are the steps that I think you should follow:
- re-download the custom rom that you wanna flash (make sure that the download is not corrupted)
- boot into recovery (in your case,CWM)
- wipe cache . wipe dalvik (in advance settings)
- install zip --> choose zip --> point to your custom rom
- you'll see the aroma installer, pick your options until it begins to install.
- if the installation went smoothly, don't reboot phone yet, get back to recovery, wipe cache/dalvik then reboot system and let the phone install the OS (first boot usually take long timer)
- if the installation hangs at midway, reboot again into recovery (power + vol down until button blinks and phone boots into bootloader) then start again from first step
once again, I advice you not to use the AIO tools. it's safe but you need to know what you are doing and the process to conquer your phone is not that hard.
Click to expand...
Click to collapse
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
redbull123 said:
So, what's your situation at the moment? You can get into recovery? What are you trying to do?
Click to expand...
Click to collapse
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
PoRco1x said:
I really appreciate your reply man. Yeah, I need to calm down haha.
Alright, the problem is that I can't get into recovery mode unless I use the AIO tool. I've tried everything else. Using the volume down button, under the bright light etc etc. IT just goes straight to the HTC screen. It must be noted that I DID have problems getting into my bootloader before as well. A moderator of another forum made me download an app from the app store that let me either reboot int bootloader or reboot into recovery.
Rebooting in bootloader didn't work through that app either, it just restarted the phone, However,rebooting into recovery worked. Also, AIO tools doesn't seem to allow me to reboot into bootloader either... that command just restarts the phone and gets it stuck on HTC screen.... BUT the "reboot into recovery" works here too
Problem 2 ) The device is being detected by my pc but I can't access the file system in it. It just showing as a drive with no GB in it whatsoever . when I use "adb devices" in cmd it shows my device along with the serial id though.
Click to expand...
Click to collapse
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume and power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
JazLiew said:
It is not bricked, you should hold down your vol down+power a tad bit longer, you should hold it until the screen comes on and not until when it's turned off. If the installation is stucked in recovery you should be able to go to bootloader.
You need to mount usb to your computer first. If you cannot find the option to mount it, you probably need to push files through adb in fastboot mode.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, I tried that too. The phone was INITIALLY just stuck and wouldn't even restart. Nothing I did made it restart until finally... I used adb reboot bootloader to make the phone finally restart into the HTC screen. But no matter what I try to do, it hasn't taken me to the bootloader even ONCE, ever since I got the phone in fact.
Should I push in a new rom using adb? And if so, which one? Android Revolution HD (fresh download) or a different one that you recommend?
Btw, I apologise for the delayed replies, the forum is making me wait between each message since I'm new
PoRco1x said:
Well, I'm not sure what my course of action should be.
I'm in recovery mode right now. Got there using AIO.
The Android Revolution HD rom is STILL in there.
However, I'm wondering if I should put in a new rom using adb push (just watched a youtube video that says I can apparently do that)
Or should I REFLASH with new recovery and then install the rom?
What should be by next step? Because I dont want to be making mistakes
Click to expand...
Click to collapse
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
redbull123 said:
I would just try flashing the ROM again - it sticks at 30% all the time, it's a common problem with Aroma (the installer), nothing to do with anything you've done, nor the ROMs fault. It sometimes takes a few tries to get it properly. I'd recommend using the volume power buttons to navigate around aroma instead of using the touchscreen...
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It's funny you mention that! I had serious issues navigating through the aroma installer, I would have to click the "next" button at least 2-3 times. And when I tried using the volume buttons, it would only go to the button inbetween "back" and "next" which was something like "more info"
Does this point toward any other issue? Or should I go ahead with flashing rom again?
ryryzz said:
While in recovery, on your computer try boot into bootloader with "adb reboot bootloader" and see if your phone can boot into fastboot mode. If it can, I strongly recommend you to COMPLETELY go back to stock by flashing your RUU.exe. After going back to stock, do the whole process of unlock/root again
Click to expand...
Click to collapse
I used adb reboot bootloader to get OUT of the installtion screen, but it didnt take me to the bootloader (as usual) it just restarted. The AIO tools also didn't take me to bootloader when I used one of the commands there. So going to booatloader is really being impossible now!!
I think u need to send it to repair or warranty. Since you can't go to bootloader there's a lot of things you can't do right now.
So now I have two options at hand now...
1) Go ahead with rom installation (this I know how to do)
2) Flash official stock using RUU (this I dont know how to do yet, since I'm not entire sure what carrier this was initially on)
Hi! I do hope someone can help me getting back to installing a new ROM on my Desire 500.
I had an old one lying around and decided to root it. This is not the first time I have done this. I followed the guide in this forum and so far it has been very helpful, thank you! I took all the steps up until installing a custom ROM. Did a full wipe, extracted the ROM to the right folder on the SD card and went into CWM to restore it to my phone. However, CWM linked in the guide does not seem to support restoring from external storage, so I proceeded to flash TWRP onto the phone. Version 2.6.3.0 was recommended in the guide so that is the one I used.
After booting into recovery, I found out that I cannot use the touch screen, thus rendering TWRP useless. Now I would like to install a version of CWM that is compatible with external SD cards, but I cannot get out of TWRP because of the screen not working.
I found a few threads recommending a hard reset, but no matter how long I hold down the volume down and power button (I did this for over 2 minutes straight), the phone does not turn off. I also saw this strange advice to do this under a very bright light, but this also does not seem to work. Removing and re-inserting the battery just immediately puts me back into the locked TWRP screen.
How do I get back into fastboot so I can flash a new recovery image and get rid of TWRP?
Concretely said:
Hi! I do hope someone can help me getting back to installing a new ROM on my Desire 500.
I had an old one lying around and decided to root it. This is not the first time I have done this. I followed the guide in this forum and so far it has been very helpful, thank you! I took all the steps up until installing a custom ROM. Did a full wipe, extracted the ROM to the right folder on the SD card and went into CWM to restore it to my phone. However, CWM linked in the guide does not seem to support restoring from external storage, so I proceeded to flash TWRP onto the phone. Version 2.6.3.0 was recommended in the guide so that is the one I used.
After booting into recovery, I found out that I cannot use the touch screen, thus rendering TWRP useless. Now I would like to install a version of CWM that is compatible with external SD cards, but I cannot get out of TWRP because of the screen not working.
I found a few threads recommending a hard reset, but no matter how long I hold down the volume down and power button (I did this for over 2 minutes straight), the phone does not turn off. I also saw this strange advice to do this under a very bright light, but this also does not seem to work. Removing and re-inserting the battery just immediately puts me back into the locked TWRP screen.
How do I get back into fastboot so I can flash a new recovery image and get rid of TWRP?
Click to expand...
Click to collapse
Remove battery, wait 15 minutes. Press and hold first vol- and after power button. Install this recovery
http://forum.xda-developers.com/desire-500/development/recovery-pilz-touch-recovery-6-59-0-cwm-t3031421
Same problem for me BUT I have an internal battery so would I honestly have to screw open my HTC One M7 to reset this? Waiting for the battery to drain is a waste of a lot of hours having to press vol every minute to leave the screen on