[Q] Boot problem. Cannot access recovery. milestone - Motorola Droid and Milestone Q&A, Help & Troublesh

Well, short summary : Cyanogenmod 6.3.6 for milestone(milaq)
​Androidiani Milestone Openrecovery (based on the Openrecovery by Skrilax_CZ by 89luca89 and Azhad)
Everything was smooth and good. But sometimes I would run into some low memory situations. The recovery menu had some memhack
options. I tried them. This is when trouble started.
Current symptoms :
Phone switches on and does not go past the Motorola M logo. It just stays there. Only way to switch off is to pull battery
Cannot load into recovery. I see a yellow exclamation mark with a small phone icon. And it just stays there. Not the box with an arrow pouring into a phone.
Can load into bootloader. Gets recognized in RSD lite. Can reflash vulnerable recovery upto the point that it needs a restart. It cant restart so it asks me to manually restart which i cannot do.
What should be done? . I've gone through all threads thatt seemed relavent. It always calls to reflash the vulnerable recovery, which I can do but cannot reboot
Thank you in advance.

I hope I'm wrong, but I guess your phone is hardbricked.
Maybe someone with greater knowledge could help you.
(Try to ask around on the #milestone-modding IRC channel)

Erovia said:
I hope I'm wrong, but I guess your phone is hardbricked.
Maybe someone with greater knowledge could help you.
(Try to ask around on the #milestone-modding IRC channel)
Click to expand...
Click to collapse
Thank you for your reply. I really hope it isn't hardbricked, I only tried some settings from the recovery menu.
How does the IRC channel work?
I just describe my problem in the common are or do i ask someone specific?

I see in the irc-log you already found it. I hope your problem will be solved.

if nothing will help flash a full sbf firmware with rsd lite....
all data and settings gone, but i think your device will boot again

Erovia said:
I see in the irc-log you already found it. I hope your problem will be solved.
Click to expand...
Click to collapse
Thank you very much. You directed me in the right direction. My phone is ficed and running fine now. I'd like to post the problem and the solution here.
Problem : Phone will not boot past M logo. Phone will load into bootloader. Attempts to get to recovery will result in phone stuck at yellow exclamation mark with phone icon, not the typical arrow pouring out of box into phone icon. Phone will not charge.
Solution : In a general scenario, to get to recovery hold 'x' and power up, keeping it pressed until yellow exclamation mark with phone icon comes up. Then press volume up and then press camera key. This will get you to standard android recovery. I use androidiani-openrecovery so I apply the relevent update and load openrecovery. Then you wipe date, wipe cache, wipe dalvik. Then apply cyanogenmod update. And reboot. Softbrick solved.
Now, I was unable to get past the yellow exclamation and phone icon. Pressing volume up and camera button did nothing. I wouldn't budge. Turns out, when I replaced the digitizer on my phone, I placed the camera button upside down. So the camera button would click but would not half click(for focussing). Apparently recovery is loaded when volume up is held down and the camera button is half pressed. Turned the camera button over and voila! recovery. What followed is in the previous paragraph.​
So that's how to deal with a softbrick. A bazillion thanks and much respect to nadlabak.

-FuFu- said:
if nothing will help flash a full sbf firmware with rsd lite....
all data and settings gone, but i think your device will boot again
Click to expand...
Click to collapse
That makes sense. That would work I guess
I haven't tried that though as the problem was fixed, described in my last post.
I presume the procedure to flashing a full sbf firmware is the same as the vulnerable_recovery.
PS: Thank you for your great work on the OR minimod :good:

i try my best to add some nice features to OR
and i rescue some devices by flashing a full sbf, if something going wrong when i test something and if it dont pass the M Logo i just reflash 2.2.1 and try again

Related

[Help]Milestone keeps repeating android boot!

So right now, my phone keeps on getting stuck at the 'android' word bootscreen. It keeps repeating and seems to go on forever! Someone please help me! I heard its due to rooting! Can anyone confirm this?
What did you do? I tried once to install aps 2 card and the phone stood in android screen about 20 min
Anyway if it doesn't start. Flash new android: nand restore or sbf
.
Sent from my Milestone using Tapatalk
Finally somebody replied back. Its been going on for days, I've removed the battery, placed it back, same thing.
Also, sorry but I have no idea how to flash something. How do I do it? And it doesn't even go past it.
I should spend on time in this sub-forum.
If you have flash a custom ROM then just reflash it or try another ROM.
It's highly, highly unlikely that your phone it breaked so don't worry about.
I have never flashed a custom rom. I don't even know how to flash in the first place.
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
under18 said:
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
Click to expand...
Click to collapse
Yep, I can go into it. But I checked, and can't find how to install a vulnerable recovery. Any help?
My site is down atm, but this may help;
http://forum.xda-developers.com/showthread.php?t=932196
shut down phone ->hold down hard keyboard x key and power button->when M logo appears release power button but keep pressing x key until recovery mode shows up
there is an option for clearing data/factory reset
you'll loose everything but it propably fix the problem
Including my contacts?
ray243 said:
Including my contacts?
Click to expand...
Click to collapse
your contacts if you have chosen it will be at your Gmail account and they will be restored.

[Q] No functional recovery image... now what.

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.

[Q] N1 caught on the screen fastboot

Hello
I can't boot on my n1.
Every time I turn on my phone it gets stuck on the screen fastboot.
The worst is that no button works, nor volume, nor power, nor the trackball.
I searched the forum and found no solution.
I appreciate the help
This is the screen
imageshack.us /photo/my-images/843/imag0652g.jpg/
One of the buttons (trackball? volume?) is stuck.
That's what all the forum searches should have told you.
Nothing to do but physically repair it.
If it is getting stuck in Fastboot mode, it would be your trackball button that is stuck.
res
It was really a physical problem at first, the trackball was stuck and now I can move the volume and power buttons.
However when I select the bootloader i go to another screen and selecting fastboot back to the previous screen and the system does not load.
When I select reboot or reboot bootloader, go to the same screen and the system will not boot.
When I select recovery appears a triangle with an exclamation and not leave it, I have to take the battery out.
I've made clear storage and nothing changed.
That is, still can not get the phone working.
Any suggestions?
Thank you very much
If you are looking at keeping the phone stock, I would recommend looking into the PASSIMG method (method can be found in the Nexus One Wiki link in Jack_R1's signature under Unroot/Restore). This will put your phone back to the way it was when it first came out of the box.
If you are wanting to load a 3rd-party firmware, the easiest way is to unlock the bootloader using fastboot and then load a custom recovery like ClockworkMod or Amon_RA. This will allow you to install a custom ROM.
I made a video, hope it helps.
youtube
watch?v=GBvtiB2n3zM&feature=youtu.be
You have a link explaining how to do this method?
Thanks
For which method? Either way, I am sure both are well documented in the wiki in Jack_R1's signature.
Hello everybody
Unfortunately I could not solve my problem.
I tried the method passimg but not worked. The phone does not leave the bootloader screen.
My sd card is formatted, the file passmig put it, the file is installed, but then back to the same screen and the system will not boot.
Can anyone help?
I lost my phone?
Hey I'm having the same issue, I'm still with the phone like if the trackball is stuck, but I feel button ok, I press it normal. I think it could be the flex, what do you think guys?

[Q] HTC One won't turn on. Can't go into recovery or fastboot. Bricked?

I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
Click to expand...
Click to collapse
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
kuboa said:
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
Click to expand...
Click to collapse
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
hold it under a bright light and try again
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
if you can get still have adb access use Hasoon's AIO Toolkit to reboot to bootloader/recovery and go from there. otherwise hold power and volume down button with the screen facing a very bright light.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
kuboa said:
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
Click to expand...
Click to collapse
just reflash superuser, i think it was left out by mistake
Aldo101t said:
just reflash superuser, i think it was left out by mistake
Click to expand...
Click to collapse
I tried that but didn't work. Anyways, that's a far less scary problem than a bricked phone, I'll figure it out. Thanks again.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
hi there.. im having the same problems. i cant access recovery and my computer wont let me access the files on my phone neither. when i boot on the phone it goes right into the bootloader and won't go anywhere else. please help! many many thanks
Bricked after attempted TrickDroid update
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Deano1889 said:
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
Click to expand...
Click to collapse
go to fastboot, use HTC all in one kit by hasoon to flash TWRP, go in twrp, Wipe everything including data, system, cache, dalvik cache, again go on HTC kit and put command of adb sideload, go on TWRP advanced menu and sideload roam. once sideload gets transferred, it will start installing and try different rom like ARHD 10.1
I can't belive it, but the bright light thing actually worked for me!
Thanks!
I was in the same situation with an HTC logo and flashing back and home keys. When I tried volume down + power under a bright light, it came back to life in bootloader. Not sure what the bright light has to do with it but glad it worked.
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
ayan15 said:
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The bright light trick is not a bug, and it has nothing to do with TWRP. It happens because HTC built in a "pocket protection" so that the phone will not reboot on its own in your pocket. The proximity sensor needs light shining on it for a hard reboot to work. (Sometime they're not sensitive enough and it takes a brighter light than you would expect)
Sent from my HTC One using XDA Premium 4 mobile app

[Q] HELP! Phone won't turn on after installing Aroma

Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Nelayme said:
Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Click to expand...
Click to collapse
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
AllAboutTheCore said:
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
Click to expand...
Click to collapse
Tried this many times but still nothing happens. I think it's totally bricked
Put it under a light, a very strong light and longpress the power button, try this
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
AllAboutTheCore said:
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
Click to expand...
Click to collapse
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Nelayme said:
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Click to expand...
Click to collapse
if your phone is booting to recovery you can still fix it without replacing mainboard just download cyanogenmod once and try flashing it after wiping everything and see if phone boots up. if it does you can use another custom sense 5rom and if it doesnt htc is the way to go
You're not bricked at all, calm down. Aroma crashes all the time and you just didn't finish the rom installation. Go back into recovery, wipe everything and flash it again. To turn the phone off, plug it into your PC and type 'adb reboot' and then hold down power and volume down as it is rebooting.

Categories

Resources