Related
***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk
Hey everyone, I'm currently on B29, non-rooted and locked bootloader.
I would like to root and make my up to stock 7.1.1. The issue I'm having, is that there is an absolute ton of conflicting info and ways to do things that I'm just not sure at all how to proceed.
What I've tried so far was starting with this guide: https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234. But the tool from step three wouldn't download and the hosting site threw a ton of popups and redirects at me (yes, I have uBlock).
Then continuing through that same thread I found this tool https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 that is apparently safer, but I have no idea how to use it.
Then I started hearing about this EDL mode stuff https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 which I attempted to do when I tried the Axon7Toolkit yesterday, but my phone just wouldn't go into EDL mode (or I just had no idea how to tell if it was or not) and the MiFlash thing didn't do anything.
So my real questions are:
1: Which version of TWRP and SuperSU do I need?
2: How do I unlock the bootloader?
3: What steps should I take so that I eventually end up rooted on stock 7.1.1 (currently still on B29)?
Thanks!
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Choose an username... said:
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Click to expand...
Click to collapse
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
CookedBooks said:
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
Click to expand...
Click to collapse
No access with adb or fastboot in edl mode. It' strictly for use with low level tools like miflash. Your environment will make the difference. I couldn't get miflash on my main pc (win8/x64) to see the device. Likely an issue of drivers even through the proper driver is installed, and phone is showing up properly in device mgr. I used a spare pc with a relatively fresh win10/x64 install. Miflash saw the phone right away.
Also, for edl mode, my u model will just flash the led once then go blank.
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
gpz1100 said:
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
Click to expand...
Click to collapse
Okay thanks, I'll give it a go again. Would you be able to clarify which version of TWRP I should use? I'm thinking 3.0.2-0 but I've seen other guides mention different versions and other people say the wrong version is going to be a massive headache.
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
gpz1100 said:
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
Click to expand...
Click to collapse
Okay thanks. As for the rest, am I correct in my understanding that I need to:
First: Use Axon7tool to flash TWRP https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Second: Unlock bootloader
Third: flash the official 7.1.1
Hmm you could use a7tool to flash TWRP, then install the twrp app and upgrade to 3.1 or whatever, and then get to nougat after some backups. I'm not sure but I think tenfar's twrp FUBAR'd some partitions when you tried to backup
Okay thanks. I think I'll give it a rest for today, I've been scouring threads since yesterday trying to get a clear picture of what to do. I think I'll spend the week researching further and give it a go next weekend.
I just miss having AdAway and CF Lumen installed on my phone. And I really want to give Substratum a try.
Thanks for all the tips and info!
Hang in there. You are on the right track. The edl thing can take a few attempts to get recognized.
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
lafester said:
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
Click to expand...
Click to collapse
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
If you have to use axon7tool then you might find this useful
https://forum.xda-developers.com/showpost.php?p=71206394
But I think that the US version has a different way to root and stuff, so i wouldn't be able to help...
bkores said:
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
Click to expand...
Click to collapse
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
CookedBooks said:
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
Click to expand...
Click to collapse
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
bkores said:
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
Click to expand...
Click to collapse
Okay, I just walked into work though. When I get home and settled this evening I'll give it a whirl and let you know what happens.
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
bkores said:
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
Click to expand...
Click to collapse
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
lafester said:
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
Click to expand...
Click to collapse
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
bkores said:
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
Click to expand...
Click to collapse
I used the toolkit to flash b15 full with miflash and it worked fine, however I already had miflash installed.
Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.
bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.
I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro
Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff
Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )
Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out
Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!
Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:
angelmika91 said:
Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:
Click to expand...
Click to collapse
that is not very understandable to be honest. Just know that any misstep can put you into a hard brick.
If your phone is an A2017G then you have to install A2017G stuff, NO MATTER WHAT. The name will change to A2017U after installing a ROM, but that's normal since most ROMs are based in U firmware. Your phone is still a G.
You cannot install an official SD card update from zte if you are on TWRP, it will fail. Those can only be installed through the stock recovery
To unbrick your phone, first enter EDL mode (vol+ vol- and insert the cable). Tell me what driver appears on the Device manager (QUSB_BULK, Qualcomm HS-USB, ZTE diagnostics)
If it is Qualcomm HS-USB QDLoader 9008, you'll need a stock EDL file (download one FOR THE A2017G, from the EDL Tool thread). Then install it using EDL Tool
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.
Choose an username... said:
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.
Click to expand...
Click to collapse
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.
Syberclone said:
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.
Click to expand...
Click to collapse
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.
Choose an username... said:
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.
Click to expand...
Click to collapse
I do know the difference between "signed" and "unsigned" software.
I'll let you help this guy out if you think my info is misleading, good luck
Hello,
We can close the subject, I managed to do it again my phone thanks to the update file (the last update ZTE) I still had in the micro SD card.
The latter by putting it in my samsung tablet I saw that my content was not finally erased. So I put the sd in my tel and suddenly the content was finally visible in the part apply update from sdcard. I could make a flash with the update and everything is fine it works! ouffff
Anyway all my apologies I had misread the tutorial.
I did not see that it was compatible only with Marshmallow and not Nougat. I was in 7.1.1 ... I focused too much on the models (A2017x) and the updates of ZTE (B4 / B5 / B6 ...). Then my english is bad. I had to use google translation but no apology is my fault. I should have been careful. I am a bit rusty since Nexus 4 (or it was super easy and there was a huge community) and even the LG G3. I find the ZTE Axon 7 more boring to root, to unlock ...
In short again thank you and sorry for this post !!!
Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
Glad you got your phone running again
angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
what kind of driver problem? EDL or mtp?
Honestly MTP works when it wants to work, so I can't help you if your PC doesn't recognize it. EDL is another matter though, pretty easy.
Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.
Can someone please help me? I don't know what more to do. Please.
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.
I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.
Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!