Help get back to a custom - ZTE Axon 7 Questions & Answers

So I was running Lineageos awhile back but then went back to stock. I am looking for advice to get back to a custom ROM again. My current situation, stock B35 everything with unlocked bootloader. No access to fastboot (understood access removed). The only way I seem to be able to access via adb is when phone is booted into OS. Otherwise adb never reports the device as available. I don't use Windows so maybe someone who is fluent to this type of procedure using Linux would be most helpful. I've tried booting into EDL but adb doesn't list phone as available device. Thank for your help.
A2017U
Mike

jonnjonzzn said:
So I was running Lineageos awhile back but then went back to stock. I am looking for advice to get back to a custom ROM again. My current situation, stock B35 everything with unlocked bootloader. No access to fastboot (understood access removed). The only way I seem to be able to access via adb is when phone is booted into OS. Otherwise adb never reports the device as available. I don't use Windows so maybe someone who is fluent to this type of procedure using Linux would be most helpful. I've tried booting into EDL but adb doesn't list phone as available device. Thank for your help.
A2017U
Mike
Click to expand...
Click to collapse
Your phone is surely already unlocked so you don't need Fastboot. ADB cannot flash anything on the phone on its own. and EDL has nothing to do with ADB or Fastboot.
First of all you need to get TWRP. You can either do so via Fastboot if you have it (coincidentally you need TWRP to get Fastboot so it's not possible) or via EDL. To install TWRP via EDL you need to use one of the tools available, but i don't know if any of those runs on Linux (EDL Tool is a .bat, axon7tool and miflash are .exe). Maybe axon7tool, but I'm not sure.

Related

adb doesn´t see N4 in recovery

Hi, these days I adb sideloaded android 4.3 on my Nexus 4. adb worked like a charm at this time. Now I wanted to root my phone (til now the phone was on stock recovery), but since 4.3 the device is not recognized by adb anymore when in stock recovery mode. So something changed during the update and i can´t communicate with my device anymore in recovery. I know that there is a similar thread on this topic, but my computer runs Archlinux 64-bit, therefore I started this new topic.
I would be happy if you could help me rooting my device.
You need to flash a new recovery in fastboot mode first, then flash the SU package
EddyOS said:
You need to flash a new recovery in fastboot mode first, then flash the SU package
Click to expand...
Click to collapse
Thank you for your answer. The problem is that the bootloader is still locked, so I wanted to open it with adb first.
If you unlock it and flash a custom recovery straight away before rebooting you shouldn't lose any data
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
p53se said:
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
Click to expand...
Click to collapse
That's what I said in the first place, you can only unlock using fastboot
I've found a driver that works fine for me on another XDA thread...
download.clockworkmod.com/test/UniversalAdbDriverSetup6 .msi
I'm on win8 and i was having the same trouble with ADB in recovery, after installing these, no problem!
Thank you for your answer. I´m sorry for the misunderstanding, but everything works like a charm now.

ADB drivers for bricked devices

*update*
So now I can't access recovery nor fastboot. Any ideas how to fix that?
*original post*
So, I was dicking around with this zenfone 5 aaaaand I managed to get it stuck in bootloop. Being the epitome of calmness I panicked and screwed up more. Anyway, here's the brass tacks.
The phone is bricked, I can still access droidboot but that's it. I can flash fastboot.img and recovery.img, but can't find device when trying to adb sideload the rom, because I didn't install the adb drivers earlier. The way I see it, I can't flash new roms till I somehow magically able to install adb drivers without being able to boot into the phone and turn on usb debugging.
So, I need help. Is there some way I can still somehow shove adb drivers into this?
Click to expand...
Click to collapse
After a bit of googling, I found out that TWRP has mount feature and I flashed that through fastboot. And then I mounted the phone and managed to install adb driver that way. Then to install the rom I got from asus site, I flashed the fastboot and recovery image that corresponds to the rom, aaaaaaaaaand now I lost droidboot for some reason. Every attempt to boot goes to recovery, so I can't adb sideload anything now. But I got recovery, so yay?
I forgot the question. How do I proceed from this? (My current condition= Nothing is working except recovery)
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
yasin0005 said:
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
Click to expand...
Click to collapse
Yeah I did that. It's just that, now it's stuck at "Asus, in search of incredible". No droidboot, no recovery.
install intel driver !!

LG Stylo 2 unable to be recognized in recovery

New to XDA so sorry if i posted this in the wrong place
But recently i received a new phone, an LG Stylo 2 Boost Mobile. It recognized fine while it was on through adb, but when i turned it off and booted into recovery, it wouldn't be recognized by adb, nor fastboot, and when i tried to "reboot into bootloader" it only restarted the whole phone into its normal boot. Adb sideload worked but i had no idea what files to try due to a locked bootloader and no stock ROMs found anywhere. I tried kingroot and it didn't have any ways to get an instant root. Im running Ubuntu and the phone is on 6.0.1 Marshmallow. Any ideas out there? I'd be sure to give them a try
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
es0tericcha0s said:
The phone would only be accessible in recovery via the adb sideload option with stock recovery.
What exactly are you trying to accomplish?
Click to expand...
Click to collapse
I'm trying to unlock the bootloader so i can flash a new recovery then root won't be hard to achieve, but when i try to access the phone in recovery mode, it doesn't recognize whatsoever. I thought there would be something i could do with sideload to somewhat downgrade the system and gain some type of bootloader, but that didn't work. Is there someway i can flash a custom recovery?
Don't believe there are any options for unlocking the bootloader or a custom recovery for that phone. According to what I could find in a quick search, there is root available but only on the software update ending in ZV3.
https://forum.xda-developers.com/lg-g-stylo/help/boost-mobile-lg-stylo-2-lgls775-t3388675
Alright, thanks for the info, wasn't sure if there was a way around it or not

Help with loss of root/twrp

I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers

what am I missing? adb sideload twrp fails

I am following this guide here to root oneplus 6t (european variant), 9.0.5 Android:
https://www.xda-developers.com/onepl...otloader-root/
bootloader is unlocked and I can see there is a positive connection between phone and PC by checking the output on adb devices and fastboot devices. both work as intended.
the problem is that when I try to adb sideload, it says that I need version 1.0.32. so this means I cannot flash the custom recovery.
any tips? been looking online for quite some time now and cannot figure out what to do anymore. where can I find this 1.0.32 adb version?
I am a long time user on nexus 5 and just bought this phone, want to root it aswell. (note: this does not mean I have high level of knowledge on these types of hacks, just wanted to have this clear.)
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
nikexv2 said:
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
Click to expand...
Click to collapse
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
cesar.maranhao said:
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
Click to expand...
Click to collapse
You need to flash the zip from within the recovery that you booted using adb, not sideload it.
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
cesar.maranhao said:
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
Click to expand...
Click to collapse
wrong twrp used. you correct twrp and it will work. like this twrp https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752 or https://forum.xda-developers.com/devdb/project/?id=27466#downloads the choice is yours alone to make.
you are asking for help with 6t in the 6 form. whats wrong with this? you should be at this link https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482

Categories

Resources