Database Users

[Q] Nexus 7 Bootloop

Hi! I have Nexus 7 and I've used it for 4 months, it's on warranty. It started to lag couple of days and I rebooted it sometimes, but on the one reboot it didn't start Android and stucked on X logo, after another reboot it started a bootloop from X logo to Google logo on and on. After another reboot it stucks only on Google screen. I've tried to wipe data and cache partition, but it also stucks. I also tried Nexus 7 Toolkit, but it gets an error on unlock bootloader. I also tried to do it via Windows' cmd.exe with fastboot oem unlock, the same problem. I can't find any working method. Please, help.

You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
scream4cheese said:
You can use the toolkit to revert back to set stock rom. Download the stock .img from the toolkit and perform the flash. Make sure you boot to the bootloader to do this.
Entering the command fastboot oem unlock on a unlocked device will not do anything if the bootloader is already unlocked.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?

ctychick said:
I'm having the EXACT same problem. Also had my N7 for about 4 mos. I'm going to try the above suggestion also. Please post your results and I'll do the same.
---------- Post added at 10:46 PM ---------- Previous post was at 10:42 PM ----------
If I'm already unlocked (not rooted), what steps should I follow? I'm new to all this and, although I've rooted a phone once before, I barely remember what I did back then. I don't even know what you mean by "perform the flash." Can you provide some more specific directions? I have the toolkit downloaded. Thanks!
---------- Post added at 11:34 PM ---------- Previous post was at 10:46 PM ----------
Ok - figuring this out slowly. Can someone tell me where in my folders I can find my bootloader file?
Click to expand...
Click to collapse
You can't find the bootloader file. It's embedded within the system. Unless you have the flashable zip then you can use that. Why do you need it anyways?

ten char .

Bad block on nand flash
Sent from my ST18i using xda app-developers app

Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *

Lolpoppa said:
Hi mate*
Dunno if you got things sorted but I had the same problem last week. I'd let the unit run flat and stay flat for a coupla days and bootloop is the price I paid. So, I call Asus who inform me that it's under warranty and to send it in for repair. Fair dos to them that's good service but I don't wanna be without my Nexus for 2 weeks so I have another play with it having previously had no joy resetting it using power and vol up/down etc.*
I'd managed to get some charge into it by waiting for the bootloop to turn it on and then manually turning it off. Not sure how quickly yours restarts but I had lockscreen for 10 seconds or so before restarting the cycle. That said it wasn't long enough to reset to factory settings but it was long enough to turn off wifi. Dunno why I tried this, sheer desperation probably but after a restart with wifi off and a full battery I was able to access my stuff and back it up to pc.*
I then was able to perform a factory reset and set the device up again, including wifi and apps. Since then it's been good as gold (but I won't let it drop below 20% charge!) but as there's only 4 months of warranty left Asus are gonna let me send it in to have a new motherboard anyway - might as well as its been wiped anyhow. The last thing I want if for it to [email protected]#k up a week after the warranty's ran out.*
I hope this helps you or other searching for a fix bud, let us know *
Click to expand...
Click to collapse
I tries this but it doesnt seem to work for me, i had the same issue as you and now it seems as though it is bricked :/ i tried doing the steps you mentioned but it didnt work for me. i get to the home screen for about 10 secs till it restarts. i want to save my music/pictures and i dont know what to do (i never enabled developer options either) any ideas?

[Android N Preview 3] Started to Bootloop this morning...

Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
UPDATE (Thanks @NeoAcheron)
While this didn't work for me, this seems to work for some.
NeoAcheron shared the OTA update Google sends out to go from N to Marshmallow. YMMV, so best of luck to you!
If anyone has any other idea's to try, I'd be eternally grateful!
And remember kids, always enable OEM Unlocking like good boys and girls. (Settings -> Developer Options -> OEM Unlocking)

JPT62089 said:
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
Click to expand...
Click to collapse
If you can use fastboot fastboot system that should work out wipe userdata

jaythenut said:
If you can use fastboot fastboot system that should work out wipe userdata
Click to expand...
Click to collapse
Unfortunately, that didn't seem to work
Code:
> fastboot format userdata
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.013s
From the bootloader page on the phone...
Code:
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-mode-charge: ENABLED
Download Mode: DISABLED.

Also worth a note...
Code:
> fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s

format from stock recovery ?

@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
csjneek said:
format from stock recovery ?
Click to expand...
Click to collapse
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.

Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
NeoAcheron said:
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Click to expand...
Click to collapse

JPT62089 said:
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
Click to expand...
Click to collapse
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?

ttminh1997 said:
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
Click to expand...
Click to collapse
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
---------- Post added at 04:18 PM ---------- Previous post was at 04:09 PM ----------
Found this: https://www.reddit.com/r/Nexus6P/comments/4jzp1o/soft_bricked_nexus_6p_with_locked_bootloader_need/
Might be possible to reproduce the special ZIP file to create a "special" downgrade OTA zip file to unbrick it, just to unlock the bootloader (at the very least).
I will have to look into it later, as I am still at work, and need to tend to some other tasks before getting back to this.
Will keep everyone updated...

NeoAcheron said:
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
Click to expand...
Click to collapse
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.

ttminh1997 said:
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
Click to expand...
Click to collapse
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!

NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.

NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Did you just flash every .img file? There does not appear to be any other way.

NeoAcheron said:
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Thanks for posting this NeoAcheron, I sideloaded this yesterday and was actually able to perform an adb sideload this time (found a handy tip... Once the phone is waiting for adb commands, unplug and plug it back into the computer as it may not already see it)
It didn't seem to immediately help, unfortunately. I let it bootloop for a while before giving up and then tried again last night. I had left it on my desk bootlooping for a while and then all of a sudden it was booted and waiting for me to set it up. I quickly did so and immediate went to settings to enable the OEM Flashing setting and just as I did so it went to the red warning screen and then proceeded to bootloop again... I tried to run fastboot flashing unlock again in hopes that my changing the setting took before it bootlooped, but still got the FAILED message. I've since tried every which way of factory resetting, sideloading again, leaving it for hours in bootloop, and still nothing
Anyone have any more ideas?

Maybe a dumb question...but
ttminh1997 said:
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
Click to expand...
Click to collapse
Deleted
---------- Post added at 10:19 PM ---------- Previous post was at 09:59 PM ----------
So you need to get this file: https://android.googleapis.com/packa...cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Can I flash this ( https://android.googleapis.com/packa...cd4f52b800.zip) in TWRP ? I am running N5...I wanted to go back to Marshmallow to be able to flash some roms.
Thanks

NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file:
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance

kristianj79 said:
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
Click to expand...
Click to collapse
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?

DJBhardwaj said:
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
Click to expand...
Click to collapse
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/

kristianj79 said:
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
Click to expand...
Click to collapse
Have you tried on any other Windows or Mac PC? If you can get it to detect, then the problem would be pretty easily solved. To confirm if your device is being recognized, type in the following command in CMD/Terminal:
Code:
fastboot devices

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

Problems with inital setup with used phone

I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.

Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
Click to expand...
Click to collapse
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.

sleepwalking0593 said:
Enter into fastboot mode by pressing volume up + power button together when the device is powered off. Connect your pc to your phone and do fastboot format userdata. For more information you can contact @MrWilsonxD he is an expert for this.
Click to expand...
Click to collapse
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?

Apotrox said:
Aye did this and it failed (Flashing is not allowed in Lock State). So i guess it's because the bootloader is still locked which i can't do since i can't access the settings to enable it (which i have to if i carry out the steps of a basic tutorial). Can i access the settings somehow without finishing the inital setup? Maybe in addition to being able to unlock the bootloader i can also remove the restriction of the old user account?
Click to expand...
Click to collapse
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue

sleepwalking0593 said:
Okay do this now. Wipe system, data, cache, dlavik, vendor. Then go in format and type yes. Flash oos. Reboot to recovery. Flash magisk. Flash no verity. Boot into os. See if it solve your issue.
Next method. Delete these 3 colour files in twrp. Look at photo attached.
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Refer to this thread.
Hope it solves your issue. Goodluck. Happy Friday. Don't forget to leave thanks if I helped.
Me sleep now goodnight. See you tomorrow. I would try to do my best to help you and solve your issue
Click to expand...
Click to collapse
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706

strongst said:
The op has a device with a locked bootloader.
So he cannot have twrp, flash magisk every other things that you suggested...
BTW: if you're sleeping you can grab a BBS idle dump file for sure, you know what I mean
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
If the device has nougat, you can try to type *#812# within the emergency calling screen to get access to the home screen and can factory reset your device.
Otherwise you can try to write the partitions from scratch with the unbrick tool which should also work https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Click to expand...
Click to collapse
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.

sleepwalking0593 said:
But you didn't read my last message i moved to oos now. You don't understand that many people face this issue. Even lightning kernel developer whose kernel was used by Sian in his earlier ROM also had that issue. People don't report on XDA because of things i can't type because i will get warning from mods. Everyone has shifted to telegram and those chats are not moderated and things that happen aren't good. If you are on telegram you will know. Okay i guess i will have to become like others and don't post my own question. Just will reply to others. I will post dump file when i flash ROM again and also developer doesn't support it. + Logs won't show anything. If it was possible atleast a kernel developer would have sent to others. + It's definitely not because of me. Because i didn't install anything apart from magisk, no verity zip, fk kernel app, bbs when i did my last testing. Sorry to bother you.
Click to expand...
Click to collapse
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!

strongst said:
Again: The op of this thread thread as the factory reset protection issue on stock rom with locked bootloader.
You cannot suggest him to boot to twrp or format several partitions, that's simply not possible!
Click to expand...
Click to collapse
I'm sorry, i got messed up with another thread i guess. Okay i will think of another solution now.
---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------
Apotrox said:
I recently bought a used oneplus 5 and i was told/asured it was factory reset and all. Now i'm trying to set it up but im required to enter the gmail account data from the former user, which, of course, i dont have and probably won't get because i mean who's gonna give a stranger his gmail password even if one can change it immediately.
Question is: Is there a way to bypass it (i factory resetted it another 2 times and erased all system settings and all already) and actually use my account for it or is it unusable until i get the account data of the seller
The bootloader is still locked and i factory resetted it myself 2 times.
Click to expand...
Click to collapse
If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.

If you click on i forgot my email id. Than you get an option to enter your phone number. Will that work for you.
Click to expand...
Click to collapse
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.

Apotrox said:
Nope i don't have the phone number used with the google account (apparently the seller used another number than the one he has on ebay). I messaged him but haven't gotten an answer yet.
Click to expand...
Click to collapse
Have you tried my suggestions?

strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
I'm at it, the *#812# didn't work so i'll have to try the unbrick tool method which takes some time to download the files. I'll keep you updated

strongst said:
Have you tried my suggestions?
Click to expand...
Click to collapse
Alright i skipped the thing with the drivers because it showed up correctly and used the msm download tool for OOS 9.0.4.
And it did work!! Thank you so much!

Stuck on twerp read only ...with lock

Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?

back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...

pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk

First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!