my oneplus 5 is bricked and keeps rebooting into recovery continuously. - OnePlus 5 Questions & Answers

hey first, i installed xxx no limits rom in my oneplus5, after that i installed google lens enabler through magisk in my device. then strangely after few hours of installing it, device gone into bootloop. i cleaned the rom and installed oos 4.5.13 and the same bootloop issue persists, then i cleared data in fastboot thinking that build.prop will be set to factory using commands
Code:
fastboot erase cache
fastboot erase userdata
Then after installing any rom, it keeps rebooting into recovery without even appearing of boot animation, just boots to show oneplus logo then recovery and the cycle continues.
please help me to correct my device. i hope it can be reverted to stock rom by flashing system.img and boot.img through fastboot like we do with moto devices. but i dont know how to do and what to do now.

https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169

Related

[Q] Bootloop on any ROM

Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app

Stuck after 5.02 update on android spinning

Turned my Nexus 10 on today and it had an update to 5.02 so I let it download and install it.
Bearing in mind my Nexus 10 is as standard from when I got it completely stock non rooted.
It rebooted and a blank screen was all that appeared. I left it for several minutes and still nothing.
Then i got an android laying on its back with an exclamation mark..
I read about flashing the full image on another thread to resolve this issue
So i went ahead and unlocked my bootloader,
erased everything and flashed everything as below:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
echo Press any key to exit...
Now i rebooted it and got the android opened up cog spinning on his back the data sort of dna web thing spinning too for a short while. however after a few minutes the device rebooted and is now stuck with the Nexus boot animation.
any ideas what i can do?
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
KiraYahiroz said:
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
Click to expand...
Click to collapse
Thanks for this although i reflashed the Nexus 10 through a USB 2.0 port instead of a USB3 and it came up on its own after a minute or so of the boot animation.
So now i can manually keep my Tablet up to date and backed up.

[Q] Stuck at boot animation after flashing 5.1

I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
After you've flashed the factory image boot into the stock recovery and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
IVBela said:
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
Click to expand...
Click to collapse
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
metpage said:
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
Click to expand...
Click to collapse
There was a new radio, but that worked (I accidentally booted normally after flashing it). The rest is the same that I did, except the cache, guess next time I'll try doing it without flashing that one. Do I not have to wipe the cache partition either? (And no custom recovery here, I boot TWRP from my PC via fastboot.)
Edit: Who understands this.... I tried it again tonight, flashed radio, then fastboot update image-occam-lmy47o.zip worked, no error this time, no unpacking, nothing. Just a successful update this time.
Guess that wipe was needed, maybe something was already corrupted before I tried flashing the first time.
Case closed.

Fastboot flash says it works but doesnt

Ok, so this is an odd issue. I've had my N7 Grouper unlocked and have been running custom roms for a long time now, and about 6 months back I tossed on the All-F2FS version of Slimkat. Everything was running fine and has been since then, up until the last few days. Now the device just reboots randomly after it gets into the system. It runs fine in bootloader or recovery so I know it's not a loose battery connector as I've read about. I'm at a loss as to why and I gave up trying to find out.
I've since been trying to simply wipe my tablet and reset back to a clean install of the All-F2FS Slimkat as I've had or even tried a stock restore now. Nothing I do works at all. I've tried everthing from the modified All-F2FS TWRP 2.7.0.0 that I installed as a part of the move to F2F2 but although it reports that it's wiped everything fine, or flashed a new rom fine, it does nothing in truth. After a quick reboot its as if nothing happened at all. I've then tried to run things from adb/fastboot and I'm even after running all the commands in fastboot which all say they run fine (flashing, reformatting partitions, etc.) nothing at all actually happens to the N7.
Anyone else seen this or have any ideas?
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Trafalgar Square said:
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Click to expand...
Click to collapse
I've tried all of those commands multiple times. I'm an old hat at rooting, unlocking, and running custom roms on Android so I've been doing literally everything I can think of. Every command shows that it completes successfully but nothing actually happens. I've tried fastboot erase commands, fastboot format commands, fastboot flash commands, and many many more. I've run six different versions of the factory image, everything from 4.0.0 to 5.1.1. The only errors I've ever seen while working with the tablet is while attempting to erase/format partitions within the recovery there are some errors about not being able to access the cache. I'll update this with the specific errors.
Anyone? I'm at a loss here. I've run everything I can think of and the commands always complete successfully, then don't actually work at all.

Can't flash partitions

Hello all,
I left a similar post in a couple other threads, and thought maybe someone here might have some insight into my problem.
Been running AICP rom (no custom kernel except the one that comes with AICP) with f2fs on /data and /cache for several months on 16GB grouper. About a month or so ago, the wife installed a game that wouldn't run on this hardware (King's Paradise Bay), and I uninstalled it. It left a file in /data/data/....etc that couldn't stat in TWRP, so no nandroid backups since then. I figured I'd just backup user data with TiBkp and wipe with fresh install of latest AICP when time permitted.
The other night I noticed the N7 was boot looping, getting to the stage where the boot animation dims. The boot anim would hang and after several seconds the Google unlock splash screen would come up and the N7 would try to boot again.
I can get into TWRP and bootloader with no problem. However, when TWRP comes up, the log shows the red entries for 2 files that can't stat, which has been this way since that game was uninstalled. I cannot seem to wipe *any* partition, and when I attempt to format or wipe userdata in TWRP, the N7 spontaneously reboots. Manually attempting to wipe/format/etc. via FastBoot doesn't work, with error message showing after trying to flash bootloader. Also, I can't change /data or /cache back to ext4. I am able to successfully read, write, and delete files on the N7 via computer USB MTP connection.
If the N7's flash memory has somehow become corrupted, is there a way to completely erase/format/whatever so that this wonderful device can become usable again? Any help would be greatly appreciated.
Thanks in advance.
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Trafalgar Square said:
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Click to expand...
Click to collapse
Yes, I have attempted all these commands, followed by flashing with either fastboot or TWRP with no success. Fastboot reports success, but partitions are not erased.
I have the same problem. The Nexus Root Toolkit can not flashign. It succeeds only boot TWRP. In TWRP computer sees the files from the tablet.I could not rename and delete. Wipe the TWRP and stock recovery displays the status OK, and the files are deleted. Fastboot shows that uploads, but all files remain unchanged.

Categories

Resources