So I got this Oneplus one from my friend and it's come to me to revive it as there is something wrong with it.. The current state of the phone is that when it's plugged on the computer it can go into fastboot mode or when I try to boot it I will see the oneplus one logo and then it will bootloop. No recovery mode. For some reason without plugging in the phone when I try to start it the phone just vibrates and then goes off and the screen is black all the time. Have charged the phone for an hour to make sure it's not out of juice.
This phone has unlocked bootloader and was on Lineage OS if I am not wrong but I am sure this friend has done something wrong in flashing the wrong file. I know there are loads of solutions which I have tried. Trust me I've tried all and then I am making this new thread or else I won't replicate content.
Things that I tried :
1. Tried flashing cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB via fastboot mode. Everything writes properly but still the same bootlooping and no recovery.
2. Tried flashing Color OS via MSM8974DownloadTool. Everything again goes fine and it's green but again got the Red oneplus one logo this time (maybe that's the color OS boot image) and then bootlooping. Also no fastboot in this mode.
3. Tried Oneplus One Patch released by them officially on their forum to revert the phone to complete stock. Again same issue.
Is there anything else I need to try to make this phone work or is this going to the bin
Any leads would be appreciated from you guys.
Thanks.
have you tried swapping out the micro usb cable because that might be your problem
Replace the batteries with a new one....
Try using fastboot image of cm11s, the very first factory rom for bacon.
I once had to go this far back when flashing sail rom or something
OK let me try with a new cable and let me try flashing cm11. Will update. Thanks.
Update : Trying since morning to get the CM11 fastboot file but unable to get it. It's there on android host server but I am getting constant speed of 10KB/s. Kept it to download for 6 hours and it failed to download.
Anyone has a google drive link to the file? It would be a great help.
If fastboot works there shouldn't be problems at all. First of all wipe everything including internal(search commands online)...also try "fastboot oem unlock" command again. Then just simply flash the latest TWRP via fastboot and from TWRP flash Official LOS15.1(works beautifully) and gapps.
i had somthing simular happened and what i did was i flashed color os then flashed twrp then cm and then booted it (it worked) then flash linage os 15.1 and thats that (i did this cuz i bricked mine while trying to make a boot logo)and btw make sure you have not got the color os boot logo set as the boot logo while installing other roms due to the fact color os boot logo stops or roms from loading make sure you have got the original boot logo!
choosymoron said:
OK let me try with a new cable and let me try flashing cm11. Will update. Thanks.
Update : Trying since morning to get the CM11 fastboot file but unable to get it. It's there on android host server but I am getting constant speed of 10KB/s. Kept it to download for 6 hours and it failed to download.
Anyone has a google drive link to the file? It would be a great help.
Click to expand...
Click to collapse
who are you downloading it from aka which developer
I am inside the OS so the issue was to do with the cable. So stupid but I guess flashing Color OS did help. Thanks a lot guys. We can close this thread. Also the battery seems to be broken, will have to change that.
because i had the same issue a few months back i totally bricked my opo and i thought my phone was gone and not coming back
Related
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Shinobi_warrior said:
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Shinobi_warrior said:
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Click to expand...
Click to collapse
Are you able to boot into twrp? If yes,then flash this firmware.It should solve any firmware corrupt issues,i.e. you should be able to boot into fastboot again.
Thank you, YES this is exactly what I needed/looking for.
.
You have fixed/saved the Day confirmed now.
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.
So, i`m pretty sure my phone is hard bricked.
I was running with it for several months with no issues, so today i decided to flash EK 1.15 and then rebooted my phone, but instead of booting it went to CrashDump Mode and i can`t get it to boot or enter fastboot.
I`ve tried to use MSMtool but to software does not recognize my phone and on the device manager it shows as `Qualcomm HS-USB Diagnostics 900E`, on the CrashDump it shows `Could Not Decompress Initial ramdisk image.rd_load_disk`.
I`m opening a ticket with OnePlus, but as i live in Brazil and this phone was imported i think i`m fu****
Does anybody had this problem or knows if it is indeed a hardbrick?
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
I'm so glad you got it up and running again! There's nothing worse than thinking there's no way out!
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
Glad to see you got it. I had the same issue few days ago and, indeed, it was quite hard to run fastboot mode.
Sent from my GM1913 using XDA Labs
Good recovery! Cheers
I had a OnePlus 6t around the time they first came out and I ended up in crash dump mode probably 12-15 times, sometimes just randomly without doing anything to my phone..I would look at it and it was in crash dump. I recall the devs saying something about a fix for it back then... I have a OnePlus 7 pro 1917 global model now and I bought it used and only had it about one week now. Same exact cinereous. I looked down at my device on day one of me having it and there it was, crash dump mode. Since then on my Guac I've seen crash dumb four times. I've only flashed dotOS and DerpFest but the first crash dump I experienced on this phone was before I flashed anything. I was stock with TWRP installed.. I'm back at my home base now so if and when it happens again ill grab logs and share them. I have always been lucky enough to be able to get control of my device back by holding down power+ volume until I boot to bootloader and then tap power at the "start" screen and ive always booted back up. Have you all experienced crash dump mode often on 7 pro? Hopefully this will be fixed we some point.
Hi all, I've been on Lineageos 16 for a while and finally decided to update to 17. I went ahead and acquired the latest twrp from mauronofrio. I flashed on both AB slots stock OS and then proceeded to flash the latest lineageos with of course gapps, magisk and twrp. However, once finished I booted to system and got stuck in the lineageos loading screen.
Thinking I might've done it wrong, I reded my steps and still the same. This took me almost the whole day, but nothing worked. So I decided to go back to 16 and then everything got worse. Suddenly I got an error that slot A was denied and now I somehow cannot even access twrp anymore. I've tried all different twrps, from the official one to blu_spark one and mauronofrio. Nothing worked, I would either get the Fastboot mode logo or just a black screen with the led light on. Now my phone is stuck with these outcomes.
I can access fastboot so I decided to use the flash-all bat but that didn't work either. I can't even boot to system as I get a black screen again with the led light on. I seem to be stuck at this and now I regret having even attempted to update my lineageos. I didn't even get the chance to backup my data. So idk if there's a unbrick tool that doesn't erase all your data as I cannot afford to lose my data.
Any help is appreciated. My phone is currently in fastboot mode and I'm completely worned out. I spent the whole day trying to fix it, checked so many forums and I feel like it only got worse. If more information is needed let me know. (And yeah the bootloader is unlocked.)
Mangob0y said:
Hi all, I've been on Lineageos 16 for a while and finally decided to update to 17. I went ahead and acquired the latest twrp from mauronofrio. I flashed on both AB slots stock OS and then proceeded to flash the latest lineageos with of course gapps, magisk and twrp. However, once finished I booted to system and got stuck in the lineageos loading screen.
Thinking I might've done it wrong, I reded my steps and still the same. This took me almost the whole day, but nothing worked. So I decided to go back to 16 and then everything got worse. Suddenly I got an error that slot A was denied and now I somehow cannot even access twrp anymore. I've tried all different twrps, from the official one to blu_spark one and mauronofrio. Nothing worked, I would either get the Fastboot mode logo or just a black screen with the led light on. Now my phone is stuck with these outcomes.
I can access fastboot so I decided to use the flash-all bat but that didn't work either. I can't even boot to system as I get a black screen again with the led light on. I seem to be stuck at this and now I regret having even attempted to update my lineageos. I didn't even get the chance to backup my data. So idk if there's a unbrick tool that doesn't erase all your data as I cannot afford to lose my data.
Any help is appreciated. My phone is currently in fastboot mode and I'm completely worned out. I spent the whole day trying to fix it, checked so many forums and I feel like it only got worse. If more information is needed let me know. (And yeah the bootloader is unlocked.)
Click to expand...
Click to collapse
tipically when phone starts on fastboot and Is recognized from PC there Is always a chance to make It working again
I am used to use the *fastboot.zip when i run on throubles... there Is also the "All-In-One" tool, but before... dis you run the "flash all.zip" file running with admin priviledges?
basically type "cmd" tight click on "command prompt" then "run as administrator"
once in dos prompt type 'cd "full path of unzipped folder"'
then "flash all"
(you can also use powershell, it's the same, important Is the "run as administrator" start option")
I was able to finally get into twrp and backup important files. Did a clean install with msmdownloadtool to bring it back to stock. I think my rooting days are on hiatus for now. What a stress this was.
This thread can be closed. Thank you!