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'
Related
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 ??
I was wondering if there was a way to unlock the bootloader on the v410 running 4.4.2. I have tried FreeGee and my device freezes and then restarts. I am rooted (TowelRoot) and have SuperSU and Busybox installed. I would like to be able to install TWRP recovery.
newbreedsoftware said:
I was wondering if there was a way to unlock the bootloader on the v410 running 4.4.2. I have tried FreeGee and my device freezes and then restarts. I am rooted (TowelRoot) and have SuperSU and Busybox installed. I would like to be able to install TWRP recovery.
Click to expand...
Click to collapse
I installed TWRP using flashify with no issues.. You might want to try that.
shilofax said:
I installed TWRP using flashify with no issues.. You might want to try that.
Click to expand...
Click to collapse
Which version TWRP are you using? Are you on kitkat? Trying to root and install TWRP
I am a newbie here. But I unlocked my device thru the carrier. What have you been able to use to unlocked boot loader? I have Lollipop 5.02 running on my device.
unlocking v410 bootloader
Repins55 said:
I am a newbie here. But I unlocked my device thru the carrier. What have you been able to use to unlocked boot loader? I have Lollipop 5.02 running on my device.
Click to expand...
Click to collapse
I have been fighting this for a couple of days. It seems that users are downgrading to a previous version 4 of Android in order to unlock the bootloader. I have been unable to make this work personally. Kingroot rooted 5.0.2, but the TWRP recovery ROM will not load. I think it's because the bootloader is still locked.
Yeah I'm having the same issue. If I flash the e9wifi .IMG recovery then boot recovery I get this fastboot screen which I've never seen on this vk410. I can't really use fast boot commands it seems not to respond well I know something is off I'm curious if its my headspace and timing or the tablets.
{
"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"
}
Click to expand...
Click to collapse
lg gpad v410 boatloader
i was able to root with 360
mine has boatloader removed
att has download mode where you might wipe
recovery with linux tools
and use fastboot, on my other phone commands wouldnt work, and it was non-writable
recently while trying to flash the kernel with anykernel2 it opted to fastboot mode, i havent tried any commands my pc is down
i extracted the boot.img after root
put the zlmage in a zip to flash the kernel i borrowed and it booted to fastboot mode
the zip file name is in the other post
id like to know if it works
thanks
No Command @ bootloader
Ive got the LG Uk 410 i flashed the firmware years ago. Im trying to get into the bootloader to cleanwipe so i can upgrade to a more recent CM but bootloader says no command. Ive tried power button, pwr vol up, pwr vol dwn, vol dn & up but i cant get past it can anyone please help? Need to get to clean wipe
one I had boatloader non-functional
but had twrp and rooting/no kernel flashing
Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.
TheWoerbler said:
Guys, I think I messed up big league. I set a pin on startup and I'm guessing that encrypted my "system" partition. After trying and failing to decrypt that with the PIN I had set to use on startup I tried wiping "dalvik", "cache", "system", and "data". Then I flashed DrakenFX's B15 stock ROM, but it's still asking for PIN on startup. When I rebooted, I was faced with the stock recovery. ADB won't install on my computer, so I don't know how to flash recovery back onto the device. (Do I need the device powered on and in an OS for ADB to recognize the device and install the correct drivers?) TWRP says there is no OS installed. So, I guess my question is this: How do I decrypt my device and get back into an OS.
Thanks a million for your help in advance.
Click to expand...
Click to collapse
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer
J0nhy said:
The only way to really decrypt your phone is by formating it, as for twrp try fastboot instead of adb is going to be easier and then download the OS of your choice if u need further help pm me ill help u through teamviewer
Click to expand...
Click to collapse
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?
TheWoerbler said:
*EDIT* So the ADB installer ver. 1.4.3 wasn't playing nice with Windows 10. I installed the 1.3.0 installer and it worked right away.
Thanks! I'm back into DrakenFX's B15 ROM, now I need to figure out how to get ADB and fastboot drivers to install correctly. Every time I run the ADB+Fastboot installer, I go through the process and it says "0 Files Copied." Any help there?
Click to expand...
Click to collapse
This is the adb and fastboot i use:
https://mega.nz/#!FdARiCIJ!QM_sfJ_JNBNv5HvjyNycVVZCSN6fUP5gVZdXKpUOAbo
To use it simply unzip the files then shift and left click and then click "open command window here" if you want to use adb type abd then whatever same thing with fastboot
{
"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 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 all,
I need help with my Axon 7 (A2017G)
I upgraded my phone to Oreo 8.1 (AospExtended), played with it a bit, but decided to downgrade to 7.1.1 (stock) again.
After I did so, I noticed something different. Firstly when it boots up, this screen appears
{
"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"
}
It goes away after 5 seconds and boots or if I click the vol up or down button, it takes me to this screen
If I choose anything other than Recovery, the phone just boots up
If I choose Recovery, it takes me here
I cannot boot into recovery mode at all. I can't find out how to install TWRP recovery on here at all.
Also If i boot using power+vol down, this appears
Please advise how to install TWRP and lock the bootloader
Have you tried the Axon 7 tool by Djkuz?
It should be able to get you out of this, I'll find the link for you.
Khepralife said:
Hello all,
I need help with my Axon 7 (A2017G)
I upgraded my phone to Oreo 8.1 (AospExtended), played with it a bit, but decided to downgrade to 7.1.1 (stock) again.
After I did so, I noticed something different. Firstly when it boots up, this screen appears It goes away after 5 seconds and boots or if I click the vol up or down button, it takes me to this screen
If I choose anything other than Recovery, the phone just boots up
If I choose Recovery, it takes me here
I cannot boot into recovery mode at all. I can't find out how to install TWRP recovery on here at all.
Also If i boot using power+vol down, this appears
Please advise how to install TWRP and lock the bootloader
Click to expand...
Click to collapse
that is, like, 100% normal. you have stock recovery and that FTM mode just gives you adb. If you can't enter fastboot then you would have to install it via EDL.
But before doing that, why the heck would you want to lock the bootloader? Lol you can just hide the 5 sec screen and sell it (or return to zte, they never check), there's no difference at all
If you're gonna lock anyways, you have to install TWRP via EDL (use EDL Tool by djkuz) then install the "remove inscription" by raystef66 or follow the steps on his guide. Then you will get fastboot. After you do that, just reboot the phone. TWRP should be replaced with stock recovery again. Check if it was (power + vol+) and if you enter stock recovery then go to Fastboot (via "adb reboot bootloader") and do the command to lock
Of course you have to be FULLY stock (no magisk or whatever) or you'll brick your device
Axon 7 tool
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
There is an Axon 7 tool kit as well via another post here.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Syberclone said:
Have you tried the Axon 7 tool by Djkuz?
It should be able to get you out of this, I'll find the link for you.
Click to expand...
Click to collapse
Thank you
Choose an username... said:
that is, like, 100% normal. you have stock recovery and that FTM mode just gives you adb. If you can't enter fastboot then you would have to install it via EDL.
But before doing that, why the heck would you want to lock the bootloader? Lol you can just hide the 5 sec screen and sell it (or return to zte, they never check), there's no difference at all
If you're gonna lock anyways, you have to install TWRP via EDL (use EDL Tool by djkuz) then install the "remove inscription" by raystef66 or follow the steps on his guide. Then you will get fastboot. After you do that, just reboot the phone. TWRP should be replaced with stock recovery again. Check if it was (power + vol+) and if you enter stock recovery then go to Fastboot (via "adb reboot bootloader") and do the command to lock
Of course you have to be FULLY stock (no magisk or whatever) or you'll brick your device
Click to expand...
Click to collapse
Thank you