Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit
willdev13 said:
Hi,
Sorry for any incorrect information in advance, as I am pretty new to this.
I own a Nexus 7 2013 (32gb), I don't know what I am currently running, as my device won't start but, I was running CM11 4.4.4.
Today I decided that I'd try out Android 5.0.1, so I tried to flash my device, this did not work as my device was not found. I used the SDK tools from Google, with the razor image (5.0.1 (LRX22C)). I do have the USB driver add-on from the SDK tools, but that did not fix the problem. As this did not work, I tried this alternative method --> http://forum.xda-developers.com/showthread.php?t=2381582
Whilst carrying out this method I pressed enter through all the steps, even though my tablet did not restart like it was meant to. I then manually put the tablet into fastboot mode and tried again, pressing enter through the whole process. Again my tablet stayed on the same screen (fastboot). I put tried to power on the tablet, which didn't work and put me onto the Google start screen, where nothing happens. The console said that all my data has been deleted, even the os, but then the new image has not been transferred to the tablet.
I then tried the WugFresh N7 toolkit, which again did not succeed in transferring the flash image.
I don't think that I have an os on my device any more, and I cannot put on onto it. I don't know if my USB port is faulty on my device because when I plug it into my laptop, the disconnection sound sounds every so often, maybe that is why I cannot transfer data to it.
If I try to boot my device, it freezes on the Google screen, then nothing happens. If I enter fastboot mode, then go into recovery mode, the picture of the fastboot droid comes up with an x through it.
Any ideas?
Any help appreciated, thanks
P.S sorry for low quality photos, also my tablet is no longer detected in the WugFresh toolkit
Click to expand...
Click to collapse
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped
nightwalker said:
I can suggest u you flash stock firmware using fastboot.
As after reading your query I am sure that the OS has been deleted or corrupted due to several methods used by u.
Go to ur respective forum and u will find everyrhing related to it.
Press thanks if helped
Click to expand...
Click to collapse
I can't flash it with anything, but thanks anyway
willdev13 said:
I can't flash it with anything, but thanks anyway
Click to expand...
Click to collapse
If this is the situation then submit it to S.C
Related
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
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.
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Ok, first step is not to panic and don't do crazy stuff and go over logically. There is no help in starting to flash stuff when your pc doesn't properly connect to your phone.
Does your pc recognize the phone when you insert the USB port after you placed it in the vol+ and power on mode (fastboot)? If yes the device should be seen in the device manager as a android or usb thing.
Check with skipsoft toolkit if you see the device with adb. Do you see any number?
Don't panic here is the solution
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Juan_Cuen said:
Maybe this has been solved before but so far I haven't found a solution to my OPO Hardbrick and I really need of your help. I tried flashing resurrection remix to my OPO and I guess it went wrong, I tried restoring my backup and it didn't work so I decided to factory reset it which deleted the rom. Now, I have used several tool kits and they all seem to have not worked, it only removed my custom recovery (TWRP) and replaced it with the Cyanogen Recovery, now my phone doesn't even turn on, its all black and vibrates, I am able to use the tool kits using the volume up and power button, but no fastboot, any solutions? Thank you so much
Click to expand...
Click to collapse
Like the other people are saying, don't worry, it's probaly not that big of a deal. I had this before. Try booting into fastboot mode and reflash TWRP recovery using the method showcased in this video: https://www.youtube.com/watch?v=KZaajUEybNM (you need to skip through it a little). Make sure you have all the proper drivers installed on your computer.
The phone doesn't go into fastboot, but it is recognized by my computer as QU something with a q, with the qualcomm drivers, I have managed to only let it be recognized via tool kits, It doesn't go into fastboot or anything. I have tried the ColorOS toolkit but apparently its more succesful if I try it on an XP computer. Whenever I hold the power and Volume Up the Phone vibrates and is recognized by the tool kit
Hi all hope someone can help. My oneplus 1 was playing up a bit just lately so I thought I would give is a wipe and fresh install of a Sultan Rom that I had been using. Backed up using Titanium and Twrp to play it safe. Then like a complete novice (not the next stage up which is where I would put myself) I ticked all the check boxes and wiped. I now have no Operating System on the phone :crying: although I have a version of Twrp sitting on there.
So, off to google I trawled to find numerous posts threads and ways to get back up and running using fastboot, ADB sideloading etc. So after a day and a half of trying these methods and various images to download and flash I am no where near having a working phone.
I need help if one kind soul can help and walk me through the process of getting this phone back up and running.
Thanks for any help that comes this way.... Foz
TWRP is present, just copy paste a rom and gapps into the phone. Go into twrp, flash the rom and gapps and reboot.
Did you try this?
hi thanks for replying.
I've not been able to do as you suggest as the phone is not showing up in explorer where I copy/paste Rom/Gapps. The laptop is "seeing" the phone as there is an audible sound when it gets plugged into the USB socket and when using the fastboot command prompt, it throws a serial number at me. this is why I've tried to go down the ADB/Fastboot options of installing a Rom/IMG with no success
Install the drivers of ur phone on ur pc, download the stock rom cm13.1 from xda, and flash it.
---------- Post added at 11:44 PM ---------- Previous post was at 11:42 PM ----------
Or the other option is, get otg drive. Put rom there and flash.
I'm not having any luck with the first suggestion you gave. Every image that i am trying to flash results in some kind of error. I've even tried to put the most up to date version of Twrp on (3.2.1-0-bacon) but I'm not getting any joy with that. Even though I can "talk" to the phone in Fastboot mode I'm getting no joy. I'm thinking of re installing all the ADB set up again just to make sure
Your second suggestion is not an option for me at the minute as i don't have the kit to try it.
Thanks for you input though.
Try using a OTG cable with a thumb drive
adamfoz said:
hi thanks for replying.
I've not been able to do as you suggest as the phone is not showing up in explorer where I copy/paste Rom/Gapps. The laptop is "seeing" the phone as there is an audible sound when it gets plugged into the USB socket and when using the fastboot command prompt, it throws a serial number at me. this is why I've tried to go down the ADB/Fastboot options of installing a Rom/IMG with no success
Click to expand...
Click to collapse
maybe I missed something but you have to connect your phone to the PC when it is in recovery mode (when OPO is turned off press and keep pressed vol down + power button until you see TWRP logo). The pc should see your phone as an external drive, then you can move a ROM and Gapps and flash with TWRP.
-Pepe said:
maybe I missed something but you have to connect your phone to the PC when it is in recovery mode (when OPO is turned off press and keep pressed vol down + power button until you see TWRP logo). The pc should see your phone as an external drive, then you can move a ROM and Gapps and flash with TWRP.
Click to expand...
Click to collapse
You're not missing anything, I don't think. The phone is booted up and the TWRP screen is on. The phone is connected to the laptop and I can hear an audible noise, but there is nothing in the explorer folders that looks like A001 which is what the phone usually looks like when plugged in. If it was I'd like to think it would be straight forward.
se7enlyn said:
Try using a OTG cable with a thumb drive
Click to expand...
Click to collapse
Any recommendations? never used one so I wouldn't want to get the wrong one or one that crap it only lasts 5 minutes. Thanks
EDIT... just ordered this cheap effort https://www.ebay.co.uk/itm/Micro-US...565007?hash=item3af91d86cf:g:y0MAAOSw6VRZ5mtz . Hopefully it will get me back up and running.
should be ok but if not try this https://www.ebay.co.uk/itm/2x-Micro...475501&hash=item25bec575e8:g:z~YAAOSwPkJafy8v its what i buy
afternoon all. right, the postie has turned up with my thumb drive.Could someone advise as to the procedure to get me up and running?
Thanks Foz
ok ... I've now got an OS on the phone...
Thanks to all who have helped.
just as an add on to this thread in case someone has a similar problem.
The phone still wasn't running right and I hadn't installed Gapps so I decided to re flash and start again. Now when I booted into twrp to reflash, it couldn't read the files on the SD card in the thumb drive. I ended up having to re flash a different version of twrp on the phone which miraculously could see the files on the SD card which I installed. The issue I now have is that I don't think there is an area on the phone to store stuff. Whenever I take a pic the camera can't see or access the SD card. When the phone is connected to the laptop, there are no folders within explorer to view so I can't drag n drop files etc to the phone. any ideas/suggestions as to get this sorted?
Thanks in advance... Foz
OK we're sorted. After trying (nearly) every help guide with no luck, I found a similar problem on a YouTube video. In the comments, someone suggested trying to use a Bacon Root Toolkit by WugFresh. after a few minutes setting it up, I've have finally flashed 12.1-YOG4PAS3JL. It has given back my internal SD card. Going to do a back up in a moment and I'm off to flash a more recent ROM
I hope this info helps someone out.
Cheers all
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.