Database Users

SOFT BRICK need help

okay so i just got my nexus and coming from htc one s i fariley decent at flashing and rooting and all that cool stuff.
but im right now im stuck in a bootloop at the google screen with pad unlock i tried relocking the bootloader and then unlokcing it again and flahsing cwm and factory reseting but still stuck at bootloop. ( if anything i had already updated to 4.2.2 ) so i need help thanks

Download wugresh root toolkit for nexus devices, and then use the Flash stock+unroot and select current status as soft/bricked/bootloop

this is a known issue with some units after unlocking the bootloader.
boot into fastboot again and flash custom recovery .img file with terminal
run recovery and clear cache, dalvik cache, and fix permissions then reboot.
your phone should boot in under a minute.
(this took me about an hour of watching the boot animation to figure out...I wanted to pull my hair out lol)

thanks man im trying this now and it looks like it's working ill get back to you on the status and thanks to the other guy who had suggestion

Boot loop after flashing latest Android 7 image

While on a developer preview of Android N with my unlocked rooted phone and TWRP 3.0.2-1, I accidentally ran the September OTA. The OTA failed, but left a mess behind with the phone rebooting 4-5 times a day.
Today, I decided to fix the problem, so I flashed the latest official image (NRD90U). Complete wipe, but since I have backups, I considered it to be no big deal. Turns out it was
The phone is now a boot loop (corrupt warning -> google logo -> corrupt warning -> google logo...). Reflashing changes nothing. Trying to boot (fastboot boot) TWRP (any version) does not work (it just goes into the boot loop). Tried to downgrade back to 6, same problem. Nothing seems to work.
Somehow, something is still ****ed up on the phone, but I have no idea what. This seems to be very similar to this thread (http://forum.xda-developers.com/nexus-6p/help/help-help-help-hard-bricked-6p-t3428225/page3), but there does not seem to be a solution.
Is it definitely bricked or is there anything I can do from fastboot to try and fix this? I am unlocked. I just need a stupid TWRP so I can restore my backup and hopefully get back to a working state from there.
PS: I'm sure I downloaded the right image and flashed it properly.

OP2 soft bricked, can't access recovery, not recognized by laptop

Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.

If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac

CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.

AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.

justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.

Zte axon 7 reboot loop using axon7toolkit

Hello Experts. I am currently having an issue with my Zte axon 7 or ZTEA2017U as the back says. I was using the AXON7TOOL and I used the unlock boot loader feature and it unlocked to boot loader then I choose root and it rooted it but now it does not boot up! It says "Your device software can't be checked for corruption. Please lock the bootloader." "If no key pressed your device will boot in 5 seconds" and it never boots up it shuts down and does it all over again. SOME PLEASE HELP IM PANICANING. IF U NEED ANY MORE INFO TO HELP PLEASE COMMENT! its running Android 7.1.1 Nougat I also tried Factory Reset and Wipe Partiton and that did nothing.

sonic1337 said:
Hello Experts. I am currently having an issue with my Zte axon 7 or ZTEA2017U as the back says. I was using the AXON7TOOL and I used the unlock boot loader feature and it unlocked to boot loader then I choose root and it rooted it but now it does not boot up! It says "Your device software can't be checked for corruption. Please lock the bootloader." "If no key pressed your device will boot in 5 seconds" and it never boots up it shuts down and does it all over again. SOME PLEASE HELP IM PANICANING. IF U NEED ANY MORE INFO TO HELP PLEASE COMMENT! its running Android 7.1.1 Nougat I also tried Factory Reset and Wipe Partiton and that did nothing.
Click to expand...
Click to collapse
Oh god don't panic. Do NOT lock the bootloader though!
When that screen shows up, hit the volume down button and select 'recovery', then hit power. It should boot up on the recovery. Three things might happen:
a) you will boot into TWRP, in which case the fastest way would be to install Lineage or a Lineage based rom. If this happens download a LOS-based ROM, and also the Universal Bootstack and A2017U modem, then put them on the phone, wipe system, data and cache, and install all 3
b) you will boot into the stock recovery. if this happens you'll need an SD card (4gb or more), you simply put an official A2017U update.zip there (tell me if this is your case and I'll see if i can find a link)
c) your phone will simply reboot, in which case you might need to use MiFlash

When I goto Apply Update from SD card it says "Sorry,you can't sdcard upgrade" im not sure if that normal
I GOT Option B btw and I do have a 4gb sdcard in currently

sonic1337 said:
Hello Experts. I am currently having an issue with my Zte axon 7 or ZTEA2017U as the back says. I was using the AXON7TOOL and I used the unlock boot loader feature and it unlocked to boot loader then I choose root and it rooted it but now it does not boot up! It says "Your device software can't be checked for corruption. Please lock the bootloader." "If no key pressed your device will boot in 5 seconds" and it never boots up it shuts down and does it all over again. SOME PLEASE HELP IM PANICANING. IF U NEED ANY MORE INFO TO HELP PLEASE COMMENT! its running Android 7.1.1 Nougat I also tried Factory Reset and Wipe Partiton and that did nothing.
Click to expand...
Click to collapse
This is not good. It can't be dm-verity because the toolkit disables it when rooting. It has to be a problem with the new version of SuperSU. I'll downgrade it when I get the chance. Thank you for bringing this to my attention.

bkores said:
This is not good. It can't be dm-verity because the toolkit disables it when rooting. It has to be a problem with the new version of SuperSU. I'll downgrade it when I get the chance. Thank you for bringing this to my attention.
Click to expand...
Click to collapse
2.79 always works, though it'd be best if you just added magisk 14

Ok I was lucky enough it get TWRP on it so what do I do now? I was able to flash it with miflash. I also cleared the entire phone so now it says no os are you sure you want to reboot? So how can i install the Operating system. Sorry for all the hassle this is my 2nd android device i'm used to apple and the easy jailbreaks and restores. Can I have the download links to the things I need to get cause I don't have a clue what to look for. I really shouldn't have done this for being such a noob. XD

@sonic1337 I downgraded the SuperSU version. The root option should work now without issues.

Thanks for downgrading it but my phone no long has an os on it so I cannot us the root anymore I need to know how to reinstall it. If you can help me with that I can try it again.

sonic1337 said:
Thanks for downgrading it but my phone no long has an os on it so I cannot us the root anymore I need to know how to reinstall it. If you can help me with that I can try it again.
Click to expand...
Click to collapse
i don't get why you wiped the entire system clean but okay lol
get DrakenFX's TWRP-flashable stock system zips for the A2017U (be SURE they are for the A2017U).

[Help] Bootloop after updating, usb debugging not enabled.

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.

Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.

Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com