Okay from the top, have OPO that had paranoid 4.6 Beta 2 working just fine. Was playing with settings(dumb idea) and changed the runtime to ART like i have on multiple other phones just to try it out. Phone rebooted and upgraded all the apps like it should, but about 5 seconds after it booted, screen froze for a second and then it rebooted. Once it rebooted it was up for 5 seconds again and then rebooted again. thus started a continues reboot loop.
Using the five seconds i had i was able to race through settings and switch the runtime back to dalvik. this caused the normal reboot and fixing of apps however once it finished the boot process it began the reboot loop again and there was nothing i could do to stop it.
I booted to recovery and attempted to reflash the last update, that failed.
attempted to wipe cache and dalvik cache and that failed.
attempted factory data reset, that failed
NOW is when i made a mistake, on TWRP i checked system wipe as well as data and cache. Wiped everything.
So, phone was then entirely devoid of OS which is a slight problem. I was able to get into fastboot however and flash cm11s which i figured would fix it, false. Now when it boots the system ui crashes over and over continuously and it wont become stable. Went back to recovery but my twrp was gone and i just had cyanogenmod simple recovery. attempted to get to fastboot mode but its apparently nonexistent, i tried every combination of commands possible to get there but cant. so now im stuck with an unusable OS and a useless recovery and no way to get to fastboot mode that im at least aware of... if there are any other details that could help feel free to help, ill post pictures once i figure out a way to do that.
please, for the love of God, help me.
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
tiny4579 said:
If you gold the power button for about 15 seconds then it should turn off. Then hold volume up and then press and hold power while still holding volume up for a few seconds and it should boot fastboot mode. Try erasing userdata from there to see if you can recover from the crashing.
Click to expand...
Click to collapse
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
grenademasta said:
I wiped out everything on my Oneplus two months ago by mistake. Then my phone wont boot up because it had nothing in it except the TWRP. I tried EVERYTHING, to load a Rom into the phone, but it didn't work. It goes through the motion of loading a Rom into your phone and when you are about to hit the 100% level, it says FAILED. It wants you to check the debugging which you can't because your phone wont boot up. Anyways, I purchased a micro usb flash drive and loaded up the Rom into flash drive from my comp's usb. Then I connected it to my phone from TWRP via the micro usb port. After it loaded up the Rom from the flash drive, it booted up. Hope that works.
Click to expand...
Click to collapse
hey i hadnt thought of that, thanks ill try that as soon as i can get my hands on a micro usb flash drive, will the device find it using cyanogenmod simple recovery? twrp is gone for some reason.
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
grenademasta said:
Don't know if it will work without TWRP. I only see "Apply Update" then "Apply from ADB" and "Choose from internal storage". Hopefully the phone might recognize additional storage from the micro usb flash drive. Good luck.
Click to expand...
Click to collapse
thanks for your help! ill update as soon as i get one
The latest twrp supports mtp and you can use adb push to push the file to sdcard. Its really worth learning.
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
You should let go of the power button after the device turns off. Then vol up+power when the phone is off. This is different than what I read for the device but it works for getting me in fastboot.
Try flashing it by adb?
Overdose1986 said:
Try flashing it by adb?
Click to expand...
Click to collapse
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
as for the holding of the volume up button, ive tried every combination of holding and releasing i could think of, it just wont work :/
ugly_duckling said:
tried using adb to push files but got error: closed, tried adb kill-server etc to try and get it to work but it wouldnt go, trust me i have tried a lot of things
Click to expand...
Click to collapse
He meant using adb sideload
Sent from my Oneplus One
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Makrilli said:
He meant using adb sideload
Click to expand...
Click to collapse
ya i tried, it wouldnt connect to the phone, tried multiple tweaks from pc side and device side and couldnt get it to work, im probably messing it up somewhere but i tried to follow various "tutorials" to the letter
markbencze said:
have you had a look at my thread here? sure sounds like one of the issues listed. Take a peak and decide if it's something you'd like to try
Click to expand...
Click to collapse
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
ugly_duckling said:
Hey thats exactly how it started when i first reflashed cm11, but i managed to get through and force disable audiofx, from there though it just kept crashing system ui, i will definitely try this when i get outta class.
is there something different ill need to do based on having already disabled audiofx?
Click to expand...
Click to collapse
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
ugly_duckling said:
I tried that a hundred times, the problem is once the screen turns off, if you keep holding vol up it never comes back on, its something i have never seen before and its exxtremely frustrating. Its like fastboot doesnt exist.
Click to expand...
Click to collapse
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
markbencze said:
Disabling it will not fix your issue. My thread tells you what needs to happen. Generally when people decide to try new ideas without proper knowledge is when they get into trouble
Click to expand...
Click to collapse
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
ugly_duckling said:
ya i gotcha, i was just wondering if i needed to re-enable audiofx for stuff to work, my other problem with this method is, and correct me if im wrong, but i believe i need to be in fastboot mode? which for some reason is unattainable at the moment..
Click to expand...
Click to collapse
Yes and then follow the directions in my thread
luka1002 said:
Just a tip, if u can go in fastboot mode, try to disconnect usb from phone first , and then try
Click to expand...
Click to collapse
idk why, but i read this post and said "what the hell, ill try it again" out loud to myself. unplugged my phone, held down the volume up key and turned it on, IT WENT STRAIGHT TO FASTBOOT. fml thanks guys, i think i can fix everything from here...i dont know how i managed to never do it correctly even though before this happened i booted into fastboot regularly to flash different ROMS...thank you guys very much for the help
Related
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Drdandy said:
I'm a noob and I wiped my phone before trying recovery! DERP. Not sure what to do next.
So... I need a little help. I've been looking around and havent been able to find a situation like mine. I've got a completely wiped/factory reset HTC Inspire 4g. SD card is good and reformatted to fat32. Heres the basics. When I press the power button I get 3 vibrate and orange light, when I press volume down and power I get 5 vibrates and green light. When I plug phone in with usb (to computer or charger) I get clockworkmod recovery v5.0.2.7. I am able to toggle through options, all works fine.
This is where I need help and I get easily confused. What do I do to get this phone back to stock settings? I've tried putting the stock pd98img.zip file onto the sd card, then installing via clockwork recovery. When I do this, I get failed installation EVERY time. I've also tried connecting through ace hack kit on my lap top and running the stock settings flash. Whenever it resets the phone it does the 3 vibrates/orange light and stops.
I would really appreciate someone with a little more experience to walk me through what I need to do to recover.
Update: When I try to download the zip from the sd card via clockworkmod I get the error E:Signature Verification Failed. I'm not sure what this means.
If someone can solve my problem I'll buy them lunch or coffee! Some kind of gift card to your favorite place? I'd really like my android back!
Click to expand...
Click to collapse
You only flash pd98 files from fast boot not from CWM recovery. Boot in bootloader and it will find it
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Drdandy said:
I am going to come off as the biggest noob here, but its got to be done. How do you boot in bootloader?
EDIT: Alright. So Bootloader is Volume down and power. My phone won't boot into bootloader. Phone vibrate 5 times and green led comes on. Screen stays black the whole time.
Click to expand...
Click to collapse
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
zelendel said:
Ok i dont use CWM but there maybe an option in there to reboot into bootloader. Try holding volume up and power. Could be confusing devices on that though
Click to expand...
Click to collapse
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Since you can boot into recovery, adb should still work. Enter recovery then plug in your phone to PC and run adb reboot bootloader
Have you tried reflashing a rom in recovery aswell?
Drdandy said:
Nah, no other combo's work for getting into bootloader or rebooting it. From what I've read on other forums, if I can't get into bootloader, I'm bricked. Do you think since the phone is wiped back to factory settings that HTC would replace it under the warranty?
Click to expand...
Click to collapse
If you are booting into CWM your not back to factory. As stated above you can use adb to boot into bootloader
Just making sure I'm doing this right as its the first time I've ever use adb commands to me phone. Do I need to downloand Android SDK to write commands to the phone?
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Drdandy said:
Okay. I've learned how to use the adb commands. That was cool. haha. So I popped the battery out, then back in to get to CWM. With phone connected to computer I tried adb reboot bootloader. My phone rebooted itself, but it did the 3 vibrates with a flashing orange LED. Adb reboot recovery does the same thing.
For being in recovery. Are you guys talking about the volume down power combination, when I do this and connect the phone to the pc, the pc doesn't detect the phone. So there is no abd commands/flashing roms to it in recovery.
Click to expand...
Click to collapse
OK looks like your bootloader is messed up. Go to the ace hack kit thread. There you will find a link foe the IRC chat room. Go there and tell them what you did. They maybe able to help you.
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Macrophage001 said:
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Click to expand...
Click to collapse
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
tivofool said:
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
Click to expand...
Click to collapse
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Macrophage001 said:
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Click to expand...
Click to collapse
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
tivofool said:
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
Click to expand...
Click to collapse
Yeah I meant it's actually physically broken. I was hoping that wouldn't be the case but it seems like I'm going to have to find out how to take my phone apart.
Thanks for the help.
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.
Wow, been buying new phones every year (sometimes more frequently) since the Galaxy Skyrocket and ROM'd every single one.
This is my first ever hard brick!!!!
Not getting any display at all.
Charge was ~30% at the time if I remember correct.
Can't get to fastboot or any display output at all.
Just a dead black screen. ugh
This isn't a questions thread, since there is no recovering from hard-brick like you can from soft-brick.
So I'm not here to ask for help, because there is no help.
This thread is just to let you see what I did wrong that caused a hard brick.
TWRP Booted to slot B.
Wiped cache/dalvik & system & data.
Flashed Bootleggers ROM zip (unofficial, not available to public, I kinda wasn't supposed to flash it but hey, it's not at fault here, so don't think that).
Rebooted to recovery.
But it rebooted to stock recovery, so TWRP got lost.
Booted up to Bootleggers.
Let it settle.
Looked around and it's neat.
Rebooted to Bootloader.
Fastboot booted TWRP.
Installed TWRP zip.
Noted that I'm on slot A again.
Rebooted to slot B to verify nothing was installed there.
It never actually booted, of course. Just got a black screen.
Held power button/volume-up buttons down forever and got nothing.
Waited 5 seconds and tried holding power button down forever and got nothing.
Waited five minutes.
Tried holding power button for a long while. Nada.
Let it charge for 10 minutes (never got charging symbol).
Held down power button 60 seconds. Nada
I wish there was something I could offer - I have thought I was hard bricked on other devices I have owned but thru the help of others was able to eventually get to a point where I could flash a stock image. I don't know if you are really past that point or not but I wish you luck and hope you find a solution.
Might be worth contacting GOOGLE for a warranty repair - worst case, they will charge you something to bring the phone back from the dead .....
Good luck my friend, hope you figure something out.
Google Fi "support"
lol
Google Support
You are number 97 in the queue.
Click to expand...
Click to collapse
Yeah, I'm usually the guy helping others recover from soft brick.
This one is just dead-dead.
Even tried checking if my PC recognized it for ADB or fastboot after various key press combos.
CZ Eddie said:
Google Fi "support"
lol
Yeah, I'm usually the guy helping others recover from soft brick.
This one is just dead-dead.
Even tried checking if my PC recognized it for ADB or fastboot after various key press combos.
Click to expand...
Click to collapse
Don't feel too bad. I did pretty much the same thing. You don't want to try and boot to the inactive partition with twrp. It's like there is no system there and voila, your hard bricked. I did rma the device.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Don't feel too bad. I did pretty much the same thing. You don't want to try and boot to the inactive partition with twrp. It's like there is no system there and voila, you're hard bricked. I did rma the device.
Click to expand...
Click to collapse
You know, I suspected this was the issue.
Me booting to an unused, inactive partition.
We didn't have this issue on Pixel 1 though.
At least not when I was still flashing my P1.
I never had a Pixel gen 2.
I just did some Googling and see there are warnings out there not to do what I did because it could cause a non-recoverable brick.
So I edited my thread title for any other fools like me. :good:
This might sound strange, but I once thought I hard bricked my original Pixel. Tried for 2 days to get it to boot. Then finally I got it to boot by holding down the Power Button & Volume Down Button, then plugging in the charger cable while still holding the buttons down. It booted up bootloader screen and I was able to fastboot twrp and bring the phone back to life. Not sure if you tried that or not.
wtyler2505 said:
This might sound strange, but I once thought I hard bricked my original Pixel. Tried for 2 days to get it to boot. Then finally I got it to boot by holding down the Power Button & Volume Down Button, then plugging in the charger cable while still holding the buttons down. It booted up bootloader screen and I was able to fastboot twrp and bring the phone back to life. Not sure if you tried that or not.
Click to expand...
Click to collapse
Yep, I tried that but thanks.
Let it charge a while.
Let it sit a while.
Then pressed vol+ & power and plugged in charger.
Also did vol- & power and plugged in charger.
And power and plugged in charger.
And vol- and plugged in charger.
And vol+ and plugged in charger.
Also did this by pressing the buttons and waiting a second before plugging in charger.
lol I did it all.
****ty!
I wonder if there's is a way for twrp to warn that that partition is empty and not to boot. Or something twrp can do to prevent booting in that?
Anyone able to talk to the twrp team about this?
I noticed that when you wipe system it goes to black screen. It happen to me twice. I was able to get back to bootloader by pressing volume down and power button at the same time.
Sent from my SM-G955U using Tapatalk
---------- Post added at 07:55 PM ---------- Previous post was at 07:51 PM ----------
c_86 said:
****ty!
I wonder if there's is a way for twrp to warn that that partition is empty and not to boot. Or something twrp can do to prevent booting in that?
Anyone able to talk to the twrp team about this?
Click to expand...
Click to collapse
When I wiped system and flashed a rom system image which flashed ok, I press reboot. TWRP said there is no system OS to boot.
Sent from my SM-G955U using Tapatalk
rimgarciag said:
[/COLOR]When I wiped system and flashed a rom system image which flashed ok, I press reboot. TWRP said there is no system OS to boot.
Click to expand...
Click to collapse
Yep, it does this!
I should have known better but as an Android tinkerer, I always do things I shouldn't do.
Anyhow, I'm sort of back up and running.
I kept trying and trying and trying to get to bootloader.
And finally got it!!
At first, it started by an occasional white line that would briefly show up on the screen for 1/4 of a second.
A kept trying and trying, and eventually I would get fastboot briefly flash on the screen for one second and then go away.
After four or five times of getting fastboot to flash up on the screen like that, on the sixth try (?) it finally stuck!!
So I ran flash-all.bat and the OS booted up just fine. :good:
I then encountered nothing but issues with trying to get TWRP installed again.
It was failing to decrypt anything even after installing it three times.
And before that, my PC kept refusing to recognize the phone after booting TWRP, so I had a heck of a time just trying to transfer the TWRP.zip to the phone to install.
I gave up on all that.
And I did the following:
fastboot erase partition (A & B individual partitions for everything below)
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
Now I'm gonna flash-all.bat again and hope things go better this time around. :good:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
CZ Eddie said:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
Click to expand...
Click to collapse
Great that you're up and running. Maybe I should have kept trying on my device. But after a number of attempts and it not charging at all I gave up. You just kept trying to boot into the bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Timing is the key here to get into bootloader, you've got release the key combo super quick. It's a really stupid behavior, but I had the same situation and that's what happens.
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Paradoxxx said:
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Timing is the key here to get into bootloader, you've got release the key combo super quick. It's a really stupid behavior, but I had the same situation and that's what happens.
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Click to expand...
Click to collapse
I'm not sure I understand the timing to do a hard reset. When I boot into the bootloader I typically press and hold power and volume down until it boots into the bootloader. I do notice the first time I do that it doesn't seem to do anything but if I do it again it boots. If I do a quick press and release of the keys it didn't seem to do anything.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure I understand the timing to do a hard reset. When I boot into the bootloader I typically press and hold power and volume down until it boots into the bootloader. I do notice the first time I do that it doesn't seem to do anything but if I do it again it boots. If I do a quick press and release of the keys it didn't seem to do anything.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It's simple really.
If you hold the key combo too long, you'll end up hard resetting instead of going into fastboot. You have like half a second to react to release the keys and not hard reset and stay into bootloader.
Press both buttons->Hold till bootloader screen appears->Release immediately->If not released HardReboot.
Paradoxxx said:
You never got hard bricked, it's just that holding power button plus volume down to boot is also the hard reset key combination, and while trying to boot into bootloader, you get the almost exact timing as the hard reset.
Click to expand...
Click to collapse
Yep, I'm familiar with this behavior.
But I don't think it's what was happening for me.
Well, maybe it was, but the timing was off.
Because I've done this hard reset before.
As well as booted to Bootloader thousands of times.
I'm pretty good with the timing when they're working properly.
Paradoxxx said:
Maybe having flash all already started with fastboot in waiting for device could help in getting the timing right, as as soon the device would be in bootloader, fastboot would start flashing the stuff ?
Click to expand...
Click to collapse
I actually did try this!
And nope, it didn't work for me but maybe it would for others.
Because when I finally got bootloader to stick, it wasn't recognized by my PC.
I had to reboot my PC.
All in all, I'm happy it wasn't a hard brick after all.
Just a unusually bad soft-brick. :good:
Continue to hold volume down key when you release the power button.
CZ Eddie said:
Yep, I'm back up and running again.
Got Bootlegger's ROM installed.
Click to expand...
Click to collapse
WOW, so glad you got it back. Gave me severe indigestion before seeing that you're OK.
HI Guys, just curious, as I've not worked on A/B partitions before (my P3xl will be the first time), but how does one boot TWRP to an inactive partition? My guess is inactive means there is nothing in there since an erase was done on system, and perhaps a fastboot set_active_<the inactive partition> was issued?
Just a thought so that I know what not to do. Thanks in advance everyone!
CZ Eddie said:
Yep, it does this!
I should have known better but as an Android tinkerer, I always do things I shouldn't do.
Anyhow, I'm sort of back up and running.
I kept trying and trying and trying to get to bootloader.
And finally got it!!
At first, it started by an occasional white line that would briefly show up on the screen for 1/4 of a second.
A kept trying and trying, and eventually I would get fastboot briefly flash on the screen for one second and then go away.
After four or five times of getting fastboot to flash up on the screen like that, on the sixth try (?) it finally stuck!!
So I ran flash-all.bat and the OS booted up just fine. :good:
I then encountered nothing but issues with trying to get TWRP installed again.
It was failing to decrypt anything even after installing it three times.
And before that, my PC kept refusing to recognize the phone after booting TWRP, so I had a heck of a time just trying to transfer the TWRP.zip to the phone to install.
I gave up on all that.
And I did the following:
fastboot erase partition (A & B individual partitions for everything below)
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
Now I'm gonna flash-all.bat again and hope things go better this time around. :good:
Click to expand...
Click to collapse
I think i may be fully bricked
https://forum.xda-developers.com/pi...reen-fastboot-one-catch-t3875953#post78351724