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 ??
Related
Hi friends...
First of all, I'm sorry for my bad English.
So, my phone went to bootloop out of nowhere, no updates caused it, no root method either, just all the suddent... Went to bootloop.
Via recovery mode, I erase all user data & cache = Still BootLoop / Did not work.
Downloaded the firmware from the Asus website (concerning my model of the zenfone), also drivers & tools. So via adb installed it 100% = Still BootLoop / Did no work.
So, if anyone could be facing the same issue and solve it somehow, please let me know the way.
I've seen that this problem is a frequently issue in this phones, but, I haven't seen the solution for this Zenfone Laser 2 ZE500KL specifically.
Thanks in advance.
Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.
Solved!
M Huzaifah said:
Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.
Click to expand...
Click to collapse
Thanks buddy, it worked! did not have a clue that the ZE500KL carry that sd slot. LOL
Did not work for me
M Huzaifah said:
Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.
Click to expand...
Click to collapse
hello
i have done something and finally removed the OS. now it says NO OS FOUND.
i have TWRP. i dont have access to fastboot mode.
when i flash a stock rom it says it is for ww phones. this phone is asus zooe- it is making this error.
do you know why i am unable to access to fastboot mode?
i have made some modifications to the updater script then successfully flashed but when i reboot stuck at the logo.
how to fix his please help me
stuck with no recovery mode
i need some help. my phone asus zenfone 2 laser ze500kl cant get into recovery mode and stuck at the asus logo screen. Cant detect the phone throw ADB in pc
Can someone help me?
Thanks
ricardosanto said:
i need some help. my phone asus zenfone 2 laser ze500kl cant get into recovery mode and stuck at the asus logo screen. Cant detect the phone throw ADB in pc
Can someone help me?
Thanks
Click to expand...
Click to collapse
Have u tried Fastboot mode.
Try
"fastboot devices"
If it does read ur device..Follow these steps
1.flash TWRP recovery
2.flash STOCK ROM
If flash fails open "update script" and remove "aseert" lines
DONE
stuck ze500kl
{
"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"
}
akhil850 said:
Have u tried Fastboot mode.
Try
"fastboot devices"
If it does read ur device..Follow these steps
1.flash TWRP recovery
2.flash STOCK ROM
If flash fails open "update script" and remove "asert" line
DONE
Click to expand...
Click to collapse
It doesn't detect/read my device.
How to make it.i enter fastboot mode on the phone it detects it like kedacom device on the device manager in the pc but in adb nothing.
What to do?
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??
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'
hello..SM-g935df suddenly battery low while updating firmware.now its hang with boot screen.FRP lock also on.I tried many firmware (7.0 and 6.0.1 etc)all firmware fail at flashing "recovery.img" in odin.in recovery mode i can see like below image.
{
"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 reset the device.now its show like this image.please help me
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
JeffDC said:
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
a brilliant method.
I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
Click to expand...
Click to collapse
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here result firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1
geeth said:
thank you for the reply bro.1st I flash g935fd with "G935F_(EXYNOS).tar" but odin was stuck at 99% here result View attachment 4345010
after i remove the USB and plague it again with download mode and flash 2nd file (G935F_(STOCK).tar" )via odin.its also stuck when 99%complete.here resultView attachment 4345011 firmware version is what can i do now bro..please help me.
fw version is SM-G935FXXS1BPJ1View attachment 4345042
Click to expand...
Click to collapse
Head over to the OP's post and ring him up. I think after the first flash, as I get it, you have to somehow run the .bat file in adb, It is the .bat file that deletes the Persistence file/partition, where, as he explains, the FRP (Google enctypted file) is held. Once that is out of the way, FRP should be gone, then flash back your stock BL, or leave it on the U (Universal) BL if you wish?
That's my understanding. I don't think the OP's been around his post for several months. We are hoping he returns to answer and clarify some questions.
Hello. I recently bought a LG G4 through Aliexpress. It is a model h815 10H with Android 5.1 system.
The smartphone came with root installed and I can't access Recovery to install TWRP. Does anyone know a way to install Stock Rom without using Recovery mode?
*access*
brenosoliveira said:
Hello. I recently bought a LG G4 through Aliexpress. It is a model h815 10H with Android 5.1 system.
The smartphone came with root installed and I can't access Recovery to install TWRP. Does anyone know a way to install Stock Rom without using Recovery mode?
*access*
Click to expand...
Click to collapse
Boot your phone into download mode and use LGup to flash
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
Boot your phone into download mode and use LGup to flash
Click to expand...
Click to collapse
I can't boot my phone into Download and Recovery mode. I tried with apps that restart the phone in Recovery or Download mode, but it has the same error.
I tried update with LG bridge, too not..
Updade:
In LGup shows the model of the phone is unknown, I can't select it.
brenosoliveira said:
I can't boot my phone into Download and Recovery mode. I tried with apps that restart the phone in Recovery or Download mode, but it has the same error.
I tried update with LG bridge, too not..
Updade:
In LGup shows the model of the phone is unknown, I can't select it.
Click to expand...
Click to collapse
Lgup and bridge working in download mode only so that they show an error is obvious .
The command to boot into download mode does not work for the g4's. You must use the hardware combo + usb cable connected to a pc.
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
Lgup and bridge working in download mode only so that they show an error is obvious .
The command to boot into download mode does not work for the g4's. You must use the hardware combo + usb cable connected to a pc.
Click to expand...
Click to collapse
Right. I tried again, I managed to activate the download mode this way (thanks). However, LGup continues to recognize the device as unknown, so it does not allow me to continue.
In LG Bridge the phone is recognized as LGF500S, it notifies you that there is an update for the device. In the update information field it shows the LG-H815 model and the new version: F500S30B.
{
"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 try to start, it downloads, but when it installs it gives an error, makes a few more attempts and cancels.
I have the impression that the seller sold me an F500 model, but used the root to mask for H815. Perhaps this explains why the device came with root installed. I need to find out how to reverse this, unfortunately I made the mistake of uninstalling the root using the SuperSu app.