Database Users

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.

Bootloader locks itself, can't restore via fastboot

Hi,
recently my friend asked me wether I can look at her P8 Lite which wasn't working after beeing left unused for some time. Basically when she got a new phone this P8 was left in box for a few months and after turning it back on the screen included in attachment appeared. https://imgur.com/a/WcvNByN I'm not new when it comes to unlocking bootloaders and all that stuff as I was doing it many times on another devices so I tought it will be easy job. Well, was I wrong... What I tried so far to recover this phone:
1) I obtained all necesary data to get the bootloader unlock code from Huawei. When I want to unlock the bootloader it works but after I reboot the device it goes back to "Locked" state.
2) It does not boot to recovery with buttons combination.
3) It does boot to fastboot but as I said bootloader locks itself down after reboot.
4) I tried to place UPDATE.APP from various firmweares on SD card and update it that way, it takes extremly long but with this metod it boots to some kind of MIUI recovery in which I have 3 options: wipe cache, wipe data/factory reset, rebboot system. Depending on firmweare it allows me to wpie cache or/and wipe data but reboot system always fails taking me back to this rescue mode screen.
5) Finally I tried to flash stock rom by extracting files from UPDATE.APP via fastboot. It flashes everything except recovery and boot which gives me fastboot error: "FAILED (remote: flash write prim vrl failure)". Interestingly I can flash TWRP recovery without error but when i try to access it whit buttons combination it fails and goes to rescue mode.
Device was stock and unrooted before this. I'm kind of out of ideas, I searched a lot of topics without any conlusion on this, if anyone could help me I wolud really appreciate this. However I think there is no hope for this phone maybe someone here would be able to help.

DoggoGuy said:
Oh no... You should contact Huawei and don't tell them that you tried to unlock the bootloader. Your phone may have a thing named "Huawei eRecovery". Launch it, it will download and flash stock ROM.
Click to expand...
Click to collapse
That option works only in China . I guess

Robx34 said:
Hi,
recently my friend asked me wether I can look at her P8 Lite which wasn't working after beeing left unused for some time. Basically when she got a new phone this P8 was left in box for a few months and after turning it back on the screen included in attachment appeared. https://imgur.com/a/WcvNByN I'm not new when it comes to unlocking bootloaders and all that stuff as I was doing it many times on another devices so I tought it will be easy job. Well, was I wrong... What I tried so far to recover this phone:
1) I obtained all necesary data to get the bootloader unlock code from Huawei. When I want to unlock the bootloader it works but after I reboot the device it goes back to "Locked" state.
2) It does not boot to recovery with buttons combination.
3) It does boot to fastboot but as I said bootloader locks itself down after reboot.
4) I tried to place UPDATE.APP from various firmweares on SD card and update it that way, it takes extremly long but with this metod it boots to some kind of MIUI recovery in which I have 3 options: wipe cache, wipe data/factory reset, rebboot system. Depending on firmweare it allows me to wpie cache or/and wipe data but reboot system always fails taking me back to this rescue mode screen.
5) Finally I tried to flash stock rom by extracting files from UPDATE.APP via fastboot. It flashes everything except recovery and boot which gives me fastboot error: "FAILED (remote: flash write prim vrl failure)". Interestingly I can flash TWRP recovery without error but when i try to access it whit buttons combination it fails and goes to rescue mode.
Device was stock and unrooted before this. I'm kind of out of ideas, I searched a lot of topics without any conlusion on this, if anyone could help me I wolud really appreciate this. However I think there is no hope for this phone maybe someone here would be able to help.
Click to expand...
Click to collapse
I had the same error on my Huawei P8 Lite 2017 but I broke it myself.
The only way I was able to fix it by not taking it to a store was to use DC Phoenix,but it costs 20 euros for a 3 day license.
It was worth it though,since it did first of all lock the bootloader again,and it bootlooped at first but then I went to eRecovery and it installed the latest update and booted up.

[Solved] No way to unbrick my A2017G ?

I have no idea how I managed to get into this situation.
My A2017G was on Oreo 8.1 RR with a treble partition. Since I wasn't happy with that I want to go back to the newest stock rom.
So i followed this Guide [GUIDE] [A2017G] Return to Stock from Custom ROM - Updated.
I flashed the bootstack, then I flashed the stock system and the result was a dfu brick. Meanwhile i have an Axon 7 teared down into pieces, so I'm able to flash with MiFlash.
I tried to flash these roms until now:
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS
A2017G_B09_NOUGAT_FULL_EDL
A2017G_B10_NOUGAT_FULL_EDL
ZTE_A2017GV1.2.0B10_Stock_System_by_raystef66 (+ ZTE_A2017GV1.2.0B10_BootStack_by_raystef66)
(I also tried to flash the "Remove Bootloader Unlock Warning" zip afterwards...)
My only chance to get into the TWERP Recovery is to replace an original recovery.img with the twerp one and flashing with the test point method.
All of them result in a dfu brick or stuck in the Axon7 logo screen after the animation (if i force a shutdown, it will result in a dfu brick too).
I'm out of any ideas since every single try result in a broken device. Does anyone has a suggestion what to do now?

No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.

I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default

tdm said:
No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.
Click to expand...
Click to collapse
keep this in mind, not all G users can do the cable procedure. He's just one more on a pretty big list. It's okay to suggest that unbricking without disassembly is possible but it's nowhere near 100% (or even 50% i'd say) effectivity. Same with FTM mode, people reported that they could get there after draining the battery, well it didn't work for everyone
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
Warcon said:
I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default
Click to expand...
Click to collapse
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done

Choose an username... said:
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done
Click to expand...
Click to collapse
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?

Warcon said:
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?
Click to expand...
Click to collapse
You have no fastboot, because N builds don't have it by default. If you select fastboot it simply boots into system. (in your case it attempts to, so it ends up in the same situation).
Try to install LOS14.1 maybe, since it's just modem, bootstack and ROM. I have zero hope that it'll work but it may as well do the trick. I have no idea why this is happening to you but it's just plain weird, I mean EDL should reflash most partitions

flashed TWRP 3.2.3
made a full edl backup
whiped data, system, cache, dalvik
flashed bootstack_O_b12
flashed oreo modem
flashed lineage-15.1-20180810
flashed pico gapps
it works now

Bricked ZTE Trek 2

While trying to install TWRP via JasmineTool, completely missed the part on first run and now I got the dreaded Your Device is Corrupt error.
I can't go into recovery, it just reboots. I had backups of what I had on the device and I can go back to EDL mode via first DFU Mode, then use ZTE Terminal Software Framework . I can re-flash the backups, it looks successful, but still same issue
I tried to flash b15 or b17 recovery and boot img files, they fail with unknown error.
Any suggestions?

I am making progress... As I found out in another thread, the error is about rebooting and I was not being patient after selecting Recovery (it reboots, then error, then you wait and it boots into TWRP).
So now trying to flash Lineage, we'll see

All good... I am back in business

Note 7 stuck in bootloop after failed flashing attempt. Can't get into fastboot.

ood morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.

I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.