Develop Bugs

problem after updating rom/soft-bricked?

So I was updating six rom and phone went into continuous boot. So went into recovery and wiped all but internal memory and reinstalled. Same boot problem. Went into fast boot and pushed another over as well as a vendor image. Tried installing the new rom, beans gaps, super su and same result. I've left the phone for over 20 mins with no result but the boot screen.

I'm having a similar problem.
My status- Unlocked bootloader, twrp accessible, devices not getting detected in fastboot mode by the pc, rooted, restoring using the backup results in a bootloop, correct drivers installed on the pc, superSU and full backup in the mobile.
i cant transfer files since device not getting detected.
my timeline- i followed every instruction on https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and everything went successful, but when it rebooted to the 'Welcome' page (the page which comes when u open mobile for the first time) i restarted my nexus 5x 32gb to recovery mode and then the every boot procedure doesn't complete for several minutes(doesn't go ahead the ball animation)

Possibly Bricked?

Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED

premedicated said:
Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
Click to expand...
Click to collapse
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB. Hook up your phone to the PC and boot into the bootloader on the phone by powering on while holding in Volume Down + power. In the folder where you have fastboot on your PC, hold down shift and right click the mouse and select open command prompt (or powershell, depending on Windows version). Type fastboot devices to make sure your phone is being seen by your PC. If it is, type fastboot erase system, after that runs type fastboot erase userdata, once that runs type fastboot erase system, and finally fastboot erase boot. Then type fastboot --set-active=b , and run the same commands on that slot. Then type fastboot reboot bootloader, and when it reboots to bootloader type in flash-all.bat . That should wipe everything properly on both slots and install the latest factory image. If that doesn't work then I would say there's definitely a hardware defect. Also if it doesn't work I would try a different port on your PC.

Phalanx7621 said:
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB.
Click to expand...
Click to collapse
Inside of the factory image file, once unzipped there is another zip file contained in there with the same name. Do I need to extract that as well since it has options such as boot.img, keymaster.img and several other .img files in it, or do you just extract the main files containing bootloader-marlin-8996-012001-1808030001.img, flash-all.bat, etc.?
Phalanx7621 said:
Then type fastboot --set-active=b , and run the same commands on that slot.
Click to expand...
Click to collapse
Awesome, thanks for the reply. Question though since i'm not entirely sure about the slots. Since it's already reading it as slot B, will I change the active to slot A at some point or will running those commands in slot B erase slot A, as I understand that it basically works in whatever slot is not active.

It should detect slot A by defualt, but as long as you run those commands for both slots you'll be wiping it clean. Keep in mind we aren't talking about TWRP, we're in fastboot. And no, once you extract the files from the zip you don't need to extract the other file inside of it. The flash-all command will read it and do the proper magic. Just make sure the extracted files are in the folder with fastboot/ADB.

Well, I followed it to a T with your first post and I made it further than before. I got it all the way to where it asked if I wanted to copy files and then it froze. Restarted and it made it to finding my sim before it restarted and then it makes it to a different point before restarting, which is further than I made it before, however it still hasn't made it all the way into the software, so I guess I'm pretty well screwed unless it's something with Slot A. But I'm pretty doubtful at this point.
Update: Now it won't make it past the Google logo anymore again...

Ok, so it still isn't working. I'm going to try flashing the 8.1.0 image in a bit and see if maybe that some how resolves it. Doubtful, but it's my last step before I go spend a thousand dollars buying a new phone..
A couple questions though, when I flash-all I'm getting a lot of "Archive does not contain 'xxxxx.xxx'" errors. Archive does not contain boot.sig, boot_other.img, dtbo.img, dt.img, odm.img, product.img, product-services.img, recovery.img (this one seems important..), super.img, system.sig, vbmeta.sig and vendor.sig are all missing from the archive. This normal?
Also, I can play around in bootloader and I could in TWRP before it was erased for hours with no reboot or anything, but once the OS starts to load or loads, that's when it freezes up and fails. If it was a hardware issue shouldn't it be restarting regardless of what I'm running under?
Just trying to expend all my options before spending more ludicrous amounts of time for a piece of hardware that can just die without reason.

Format failed when doing a full wiping of OnePlus 3

Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx

cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.

tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.

Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s

Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.

cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.

cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse

What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.

@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.

Accidently deleted Android OS on HTC One M8

I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc. I can't send ADB commands to it, it won't show up on windows file explorer, I can't even turn it off. As is said this is an old phone so I am not worried about losing data, which is probably just as well at this stage!
Any advice would be appreciated!

Kieran C said:
I was trying to load Lineage onto an old One M8, I had just cleared the system, cache and data partitions using TWRP. I then clicked reboot, which I now realise was a mistake. I am now stuck on the HTC logo screen, none of the physical buttons are responding, so i cannot get into bootloader etc.
Click to expand...
Click to collapse
The physical buttons will respond, but you need to hold them for a pretty long time in the current "stuck" state. Do this:
1) Hold vol up button and power button, until the phone restarts (may take about a minute in the current stuck state).
2) Once the screen goes dark to reboot (but before the HTC logo screen appears again - I think you have 5 seconds or so), let go of the buttons, and only hold the vol down button. Do not let go of vol down, until you see the bootloader screen.
3) If you fail to get to bootloader, you simply got the timing wrong. Either started pressing vol down too late, or you let go of it too early. Simply repeat steps 1 and 2, until you get to bootloader.
4) Once in bootloader, simply select recovery, which will boot TWRP. And flash Lineage as you originally intended.
A note on wiping system when flashing a ROM: I know some folks will swear by this, and some guides will tell you to do it. But it is not necessary, and as you've seen can cause some complications. Nothing that isn't easily solved, but may give you headache nonetheless (like this case here).
The ROM install script will wipe system before it installs the custom ROM. So doing it yourself is redundant. And in the case of the ROM fails to install (it happens) you are stuck without a working OS. My recommendation is only to wipe cache, Dalvik and data when flashing a custom ROM (the default wipe in TWRP).
Any perceived "benefit" from wiping system is usually a placebo. In the rare event that the custom ROM fails to boot (or some other issue), you can always go back and flash again, wiping system (as a troubleshooting measure, etc.). Of the years of flashing ROMs (dozens and dozens of times) on various Android devices, I can count maybe 2 times where I felt I needed to wipe system when flashing a custom ROM.
Kieran C said:
I can't send ADB commands to it, it won't show up on windows file explorer
Click to expand...
Click to collapse
This can be expected when "stuck" on the logo screen. adb will only work when booted to a working OS, or alternately when booted to TWRP. Same thing with MTP access (File Explorer).

Stuck in install loop - keeps getting wiped on boot?

I'm trying to install LineageOS 17 on a OnePlus 6.
I can boot into twrp and the install process appears to work successfully. I can swap slots and install into either slot.
When I reboot the phone I get to the screen that says "Start" and "Fastboot mode" at the top. If I try to start the phone it comes back to this screen. When I go back into twrp, the contents of /sdcard is empty. I can copy over files using adb push, install the rom and then reboot. However, every time I reboot it seems like it completely wipes the phone including the install it's just done and /sdcard is also wiped.
When I booted into twrp previously, it required my unlock code. It now no longer does that. I wonder if this is part of the problem?
If I install just oxygenos, it takes me to the oxgenos recovery screen but I cant' do anything from there. I'm guessing that won't allow me to boot with an unlocked bootloader?
Can anyone advise how I can get out of this? Installing anything using twrp looks like it works, but it's like it gets wiped every time I reboot.
I can't even seem to get OxygenOS back to working.
Can anyone give me some tips on where to go from here? Nothing I can do from TWRP seems to help. I have tried wiping everything in both slots and reinstalling oxygen, no luck

Still stuck?