Database Users

Cannot restore system, stuck on bootloop

Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm kind of new to this.
Greedings
Kynie

Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.

How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?

In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair

Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.

Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk

I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...

Hello do you have find à solution ??

[FIX] Asus Zenfone 2 Laser ZE550KL Marshmallow update problem, failed to mount /asdf

I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.

Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.

Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?

hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:

I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?

How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.

Thank you
Thank you sir, this helped me a lot.

recovery link is asking need access plzz help

My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??

I need Help for reinstall TWRP

Hello,
I had successfully installed TWRP when I was in B03 on my Axon 7 version G but since I have done an update.
Screenshot History
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Currently
I Can not reinstall twrp-3.1.1-0-ailsa_ii.img
What is the right procedure
Can you help me because I do not know what to do
thank you in advance

The manual old fashioned way?
Or with axon7tool and a 64bit windows computer.

marcus.linkenbach said:
The manual old fashioned way?
Or with axon7tool and a 64bit windows computer.
Click to expand...
Click to collapse
Thank you for your reply
With B03 I followed this tutorial
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
But I also tried this tuto since I installed nougat
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
What is the difference of these 2 tutos ?
Which is best to follow
Best regards

Seem to be the same. But it easy to use the manual way.
adb reboot fastboot
fastboot flash recovery twrp.img
Or simply use the axon7 toolkit
https://forum.xda-developers.com/showthread.php?t=3573108

marcus.linkenbach said:
Seem to be the same. But it easy to use the manual way.
adb reboot fastboot
fastboot flash recovery twrp.img
Or simply use the axon7 toolkit
https://forum.xda-developers.com/showthread.php?t=3573108
Click to expand...
Click to collapse
That way only works if you actually have the bootloader mode, and if you updated to B01 you most probably don't even have it. axon7tool works perfectly if you manage to make it detect the phone.

I guess he unlocked the phone on nougat as I did. So he should have fastboot mode available. So the kit should work. Otherwise you are right. axon7tool.exe is the best way.

Crunchiphone said:
Hello,
I had successfully installed TWRP when I was in B03 on my Axon 7 version G but since I have done an update.
Screenshot History

Currently
Currently

I Can not reinstall twrp-3.1.1-0-ailsa_ii.img
What is the right procedure
Can you help me because I do not know what to do
thank you in advance
Click to expand...
Click to collapse
If you have root you can use the official TWRP app to flash it from Android.

marcus.linkenbach said:
I guess he unlocked the phone on nougat as I did. So he should have fastboot mode available. So the kit should work. Otherwise you are right. axon7tool.exe is the best way.
Click to expand...
Click to collapse
I tried your manual method but after rebooting, the phone just boots to normal system. There is no menu or anything that signals fast boot.
Then when I used the flash cmd you said above, I get "waiting for device" for hours.
I never installed TWRP on this phone or unlocked or rooted it. It's B32 update.
Do you know any other way?
Axon toolkit doesn't even show up. I also downloaded axon7tool-1.5 but it's the same, no show.
What am I doing wrong? I just want to install resurrection remix on my phone.

nelmaxima said:
I tried your manual method but after rebooting, the phone just boots to normal system. There is no menu or anything that signals fast boot.
Then when I used the flash cmd you said above, I get "waiting for device" for hours.
I never installed TWRP on this phone or unlocked or rooted it. It's B32 update.
Do you know any other way?
Axon toolkit doesn't even show up. I also downloaded axon7tool-1.5 but it's the same, no show.
What am I doing wrong? I just want to install resurrection remix on my phone.
Click to expand...
Click to collapse
Get your drivers figured out.

nelmaxima said:
I tried your manual method but after rebooting, the phone just boots to normal system. There is no menu or anything that signals fast boot.
Then when I used the flash cmd you said above, I get "waiting for device" for hours.
I never installed TWRP on this phone or unlocked or rooted it. It's B32 update.
Do you know any other way?
Axon toolkit doesn't even show up. I also downloaded axon7tool-1.5 but it's the same, no show.
What am I doing wrong? I just want to install resurrection remix on my phone.
Click to expand...
Click to collapse
Do this:
turn your phone on and enable adb
open cmd (if you have adb working)
'adb reboot fastboot'

Problem with recovey installation

Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

viru78 said:
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.View attachment 5294485View attachment 5294487
Click to expand...
Click to collapse
Before flashing, try: fastboot devices
In Developer options, is OEM unlocking and ADB debugging enabled?
If fastboot devices does not recognize device, try another USB cable or uninstall USB drivers and try again

Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.

Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img

viru78 said:
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Click to expand...
Click to collapse
Seems that something is wrong with your USB driver on the PC - adb devices works but fastboot devices does not (where Bootloader is unlocked and OEM Unlocking enabled)
Try uninstalling the USB driver(s) on the PC or try another PC

yaro666 said:
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
Click to expand...
Click to collapse
Or copy the (twrp) img file right into the ADB folder on the PC, and go with CMD into the ADB folder before running adb/fastboot commands
Then no paths are needed, just like:
fastboot flash recovery twrp.img
But that will not help him as long as fastboot devices fails

I thought about address length, sometimes adb has problem with it, worth a try

fixed, thanks for your answers, the problem was the laptop and drivers, i have had used other pc and install without problems.

help me

i made a mess, i can't install anything, i tried here to do repair installation for sansung a20s software, but it immediately failed, also it doesn't let me exit this screen anymore
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thanks i solved by flashing the original stock firmware again

To root your device, start by flashing TWRP, which you can find here. The TWRP .tar file goes in the AP slot of Odin.
Once you have TWRP installed, you should be able to flash Magisk, which you can find here.

how installa TWRP, i have error
this trying to put... twrp-3.7.0_9-0-a20.img

I didn't notice that OEM LOCK is ON.
You must unlock your bootloader to flash custom images.

ok i haveTWPR done
but after reload sisytem ...

this is very strange, for an old phone, I don't understand, I've never had all these problems ...

i m crazy

Did you flash vbmeta as well as TWRP? This might be the right file

I have to try again ,,,, but I still haven't figured out if anyone has been successful in rooting this device ,, I sansumg told everyone to do it

then, then yesterday I reflexed the original stok, now so I first do a TWPR and THEN this file that you are providing me?

yesss done good
now I need more help, I put TPWR then The file repairs vbmeta ,, ...., but it tells me that I don't have root permissions yet

do i have to give up?

Did you get a working twrp? Try booting into recovery (twrp) and then flash Magisk-v25.2.apk. If that works, reboot into system and install Magisk-v25.2.apk as an app. Then start the app and it will tell you whether you have root. If it doesn’t work, I don’t know what to do next. You may need to have the Magisk apk on a usb drive or microSD card for it to be visible in twrp.

the problem is that I put the TWPR gives me an error
vbmeta ,, then I put your tar file (
vbmeta_disabled.tar
2 KB · Views: 1) the phone starts, but in recovery I don't see TWPR the android menu looks normal

from this menu I tried to install the magic, but the installation fails

When you install twrp from Odin, disable automatic reboot from Odin options. Once you see that the flashing is completed, reboot the phone by holding vol- and power for 7 seconds, then immediately hold vol+ and power to boot into recovery. Otherwise twrp will get overwritten with stock recovery and you have to try again.

I am thinking that by reviewing the file (vbmeta_disabled) it overwrites the TWPR that I first put ,, in the revvr mod it always starts me with the classic menu
[email protected]
but every time I install a TWPR I have to insert after the file (vbmeta_disabled) because otherwise the phone always restarts with vbmeta error in download mod

Use 7-zip and add vbmeta.img from the tar above to the twrp tar and flash that

no work,,stay that way