Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.
By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol
shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.
Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Related
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
Lets make a long story short, i just got my OPO, as an advanced android user i desided to put
ParanoidAndroid 4.6, but before I installed custom bootloader (TWRP) and rooted it. Since i am installing new ROM i did a backup and then i needed to wipe my device, by accident i wiped everything from my phone, including backup and new ROM. I was left with TWRP (It is my 1st android phone without sdcard so i started to panick), then i started it in fastboot mode, to check if I can copy ROM again from my pc, but it didnt work. Then i went to restart options in TWRP and choose restart in recovery mode, then my phone turned off. Apperently it did restart but now my screen is just black and I cant do anything with it. I was holding power button, then with volume up, then with volume down, no result. When i connect it to my PC i hear sound that phone is connected but still nothing is happening. Please help me what should I do. My guess is when i pressed to restart in recovery mode, it wasn't meant to be the custom one, so it tried to open one that dosen't exist. My phone was charged 40% when i was doing that.
Note1: Unknown USB Device (Device Descriptor Request Failed), this is what i get when I check Device Manager.
Many suggestions were made so far none of them help. Hope someone will help me here!
First, TWRP isn't a custom bootloader, it's a custom recovery. The phone can't 'open a recovery that doesn't exist', it opens whatever recovery you have installed at the time. Make sure the phone is powered off (hold power for about 10-15 seconds), then try booting into recovery again (hold power + volume down).
Transmitted via Bacon
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
There is another problem
bigballa said:
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
Click to expand...
Click to collapse
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Only 1 thing
I just need to fix how to find device in adb and then it will be very easy.
Mod Edit: quoted post removed.
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]
Gapkobob said:
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Click to expand...
Click to collapse
Gapkobob said:
I just need to fix how to find device in adb and then it will be very easy.
Click to expand...
Click to collapse
My friend you're in a bit more trouble than I think you realise you're in. Your device is showing up as QHSUSB_BULK in Windows, which means it's technically bricked. I believed you can save it though, have a look in this thread, you're gonna need to read through it all to find the solution you need. Let me know how you go.
Transmitted via Bacon
Simple driver issue.
The following steps will solve your problem: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
Solved !!!
Solved thx to everybody. http://forum.xda-developers.com/one...een-fastboot-adb-t2835696/page16#post55129486 this helped
Great news.
Transmitted via Bacon
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.
My VZW rooted 4.4.4 GS5 decided to shut off, and reboot into recovery. Had TWRP with SS installed about 3 weeks ago, and all was working EXCELLENT, without any problems. I've been using this thing rooted and debloated for about 2 or more years. I have never tried to install any other custom ROMs. All I did was debloat the VZW crap off of it. I tried SS in the past, but it did not seem to do anything, so I uninstalled it, so I thought.
It appears as though through recovery, that it has been wiped.
The ROM installed was the 4.4.4, which all I wanted to do was debloat a couple years ago, which I did. Now the phone seems to have taken a crap, and I can't seem to get it to do anything. There is probably about 70% battery to play with. I can get it booted to recovery, but nothing else. I attempted to sideload the 4.4.4 firmware, but was unsuccessful. Maybe I don't know what I am doing. When I originally rooted, I used Odin to downgrade to 4.4.4, per instructions I found. But now, I don't know what to do.
Can someone please hold my hand here, and PM or email me so I can get this phone up and running again? This is both my personal and business phone. Please PM me, or email to [email protected]
Thank you.
Can you get into Download mode? If so, from there you should be able to Odin flash firmware located at sammobile's site.
Beeko said:
Can you get into Download mode? If so, from there you should be able to Odin flash firmware located at sammobile's site.
Click to expand...
Click to collapse
It will boot to Recovery mode, and give me the options to install via ADB, from external, etc. Not sure if I know exactly what you are meaning by d/l mode.
It obviously does not boot normally.
When it boots to recovery, my options are reboot system, apply update from 1. ADB, 2. External, 3. Cache, or the two wipe options.
That is as far as it will go now.
Just put batt back in, connected USB cord from PC and tried to boot. Up top, in red Secure Fail: Recovery. Then a msg on the screen. System software not authorized by VZW has been found on your phone. Please turn off and go to a VZW store for help.
When it does turn on, it goes to the Samsung screen and says Custom, with the unlocked padlock. It has displayed that since the day I rooted, back about two years ago, but has always booted through.
Now it is going back to Recovery, and gives me those 5 previous options for installing / recovery. But that's where I am stuck, and need a little (a lot) of expertise and guidance.
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
I don't think it boots to d/l mode. It boots to Recovery, then gives me the options that I previously listed; ABD, External, or cache. I don't believe that ADB is d/l mode, is it?
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
It only boots to recovery.
You tried to boot to download mode with battery pulled - volume down, power, home button?
johnnycooper said:
Pull battery, put battery back in , then hold power, volume down and home at same time. If it boots to download mode then use Odin
Click to expand...
Click to collapse
johnnycooper said:
You tried to boot to download mode with battery pulled - volume down, power, home button?
Click to expand...
Click to collapse
Okay, now it seems like I 'might' be getting somewhere. Yes, now the battery is OUT, and it did boot to ODIN, and I think it might be doing something. See?, need the hand holding. Will update, in a bit to see if this works. Thank you!
The phone says it's d/l, but there doesn't seem to be much happening on the ODIN screen.
You have to have usb hooked to pc , open Odin on pc. Then press up on phone then load factory tar to Odin
---------- Post added at 10:36 PM ---------- Previous post was at 10:33 PM ----------
Go here and read the part that days prepare your phone after #9
http://forum.xda-developers.com/showthread.php?t=3290370
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Okay, it went through what appeared to be an install, then it showed that it was upgrading, through 145, did a reboot, but now all it is doing is turning on and off, showing the GS5 screen with the Custom padlock logo.
Pull battery , boot to recovery, wipe cache. If that dont work, start over
boblpn said:
Okay, it went through what appeared to be an install, then it showed that it was upgrading, through 145, did a reboot, but now all it is doing is turning on and off, showing the GS5 screen with the Custom padlock logo.
Click to expand...
Click to collapse
It prepared the phone, rebooted, showed the red VZW screen, and now seems to be stuck in a boot loop. I have done a battery pull, and rebooted, but still stuck in a loop.
Should I try installing a different ROM? If yes, which one? Can you provide a link?
boblpn said:
Should I try installing a different ROM? If yes, which one? Can you provide a link?
Click to expand...
Click to collapse
Already did, it's in the link
question..What if he ONLY wants to go back to his KK 4.4...all he has to do is ODIN the NCG, towelroot, install SuperSU and then flash the 4.4 and he'll be back...what is being offered may not be what he wants and then may not go back to KK if he so desires...you got to give and explain to users what will happen if done...
If you can get to DL mode, Run Odin as admin on your PC and then load up whatever stock firmware you want from HERE.
He can use this thread here which could be helpful as well. http://forum.xda-developers.com/showthread.php?p=53447942#post53447942
boblpn said:
The phone says it's d/l, but there doesn't seem to be much happening on the ODIN screen.
Click to expand...
Click to collapse
It won't download anything unless you push it using Odin. Boot into recovery and give me the build number at the top. Then we can find the factory firmware to push with Odin in download mode.
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
try charging the phone for a few hours
se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.
sounds like u need a new battery
ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.
@bmark240
help please
se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.
kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os
THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.
i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.