Database Users

Please help! ZTE Axon 7 won't boot after deleting Lineage and TRWP

Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways

If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition

Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.

tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it

Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks

tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding

Lenovo K6 without OS

Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
TWRP: https://dl.twrp.me/karate/twrp-3.1.1-1-karate.img
Gapps: http://opengapps.org/ (ARM64)

J.D.M said:
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
Click to expand...
Click to collapse
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.

Crolys said:
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Click to expand...
Click to collapse
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem. Remembering that in the site https://dl.twrp.me/karate/ has two versions of TWRP, the version twrp-3.1.1-0-karate.img is 32bits and the version twrp-3.1.1-1-karate. img is 64bit.

J.D.M said:
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem.
Click to expand...
Click to collapse
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now

Crolys said:
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Click to expand...
Click to collapse
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.

Crolys said:
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Click to expand...
Click to collapse
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.

got same 255 error,just now i reflashed stock rom and issue resolved

vasu009 said:
got same 255 error,just now i reflashed stock rom and issue resolved
Click to expand...
Click to collapse
how did you reflashed the stock rom, please reply cause im stuck with the twrp and unable to do it. my phone doesn't have an os now

what s the password of the trwp

J.D.M said:
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
Click to expand...
Click to collapse
Can install this ROM on any Lenovo K6 Power device ??

dushd95 said:
Can install this ROM on any Lenovo K6 Power device ??
Click to expand...
Click to collapse
Yeah

J.D.M said:
Yeah
Click to expand...
Click to collapse
It says device not supported why??

Dont forget to reboot again into twrp - after flashing 64bit twrp . This is a step that is very important if you will not reboot your phone into twrp after flashing 64 bit twrp then , it will keep showin you the error 255.
So check that .

wacccim said:
what s the password of the trwp
Click to expand...
Click to collapse
Go for 3.2.1.0 it is better then 3.1.1.1 in 64 bits it ain't ask password i use it to flash all roms

Tere 3.1.1-1 asking for password to encrypt data
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:

Erase the data
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
Use erase the data from wipe option then you will be able to install rom and g-apps.
Every time you will need password, I don't know why but after erasing data you install all files otherwise you need to erase data again and again

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
I Faced same problem. It's ok that your phone is in weird state for time now. And also possible to recover.
Hopefully you have adb-tool, custom-rom & gapp, twrp.img on your PC.
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
fastboot oem reboot-recovery
3)Wait for mobile to boot in to recovery mode with TWRP
Now need to flash custom-rom followed by gapps installion.
I) You can use pendrive with otg to flash custom-rom followed by gapps
OR
II)You can use phone storage/SD card to flash the custom-rom followed by gapps
OR
III)adb sideload command as fallow
a)In TWRP recovery on mobile, goto Adavanced->ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify custom rom path inside ""
adb sideload "C:\adb\images\MyCustomROM.zip"
Have a patience to complete the operation.
Click back for Adavanced Menu again.
b) Select ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify Gapp path inside ""
adb sideload "C:\adb\images\open_gapps-arm-7.1-pico-20180611.zip"
c)Have a patience to complete the operation.
Once complete go to TWRP Screen.
d)Now go back TWRP main menu & select wipe->format Data.
Go to Reboot->system.
How to install TWRP if no OS there
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
a) To check the device is connected to PC or not
fastboot oem device-info
b) To flash the recovery. Give twrp path inside the ""
fastboot flash recovery "C:\adb\images\twrp.img"
c) To boot into recovery mode
fastboot oem reboot-recovery
---------- Post added at 10:03 PM ---------- Previous post was at 09:57 PM ----------
[/COLOR]
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
In my case, It worked with PIN.

A6000 Plus stuck on Bootloader

I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.

If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!

kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?

kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM

StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.

jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.

kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?

StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5

kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)

StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.

Axon 7 not bricked but almost.....pls help

Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck

Following this post, you device should be rescued.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
If your phone can not automatically boot into edl mode, then try follow method.
1) Power off your phone,
2) connect your phone to PC with a USB cable while holding hold vol up and vol down at same time.
here2for said:
Background....wanted to upgrade from 6 to 8 so went through the process using miflash and one of TurkDevs packages (A2017V3.0.0B01-2_FULL_EDL_PACKAGE_BY_TURKDEVS).
Everything installed ok but the package was kind of 1/2 Chinese so I removed it. Have been trying to install another package but with no luck so far.
When I tried other pkgs I was getting a message that the device state was locked....used AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS to unlock device ....worked fine
Current state - When device powers up it goes directly into bootloader and has the following info : fastboot mode
Product name: AILSA_II
Variant - MTP eMMC
Bootloader version - blank
Serial number - 8fb6f15
Secure Boot - Enabled
Device - Unlocked
Device will toggle between bootloader and recovery mode.
In my Device Manager it recognizes the phone as "Android bootloader interface" but has dropped the Qualicomm 9008 usb driver.
Would be grateful for any direction on this.......simple as possible please, I am not a super wiz with this stuff. I would like to put something better than android 6 on the phone as long as it is a stable release
Best Regards, Chuck
Click to expand...
Click to collapse

Thanks for reply but link is 404...pls resend tks
:::::::::::::::::::::

https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

further....
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??

Run command： fastboot devices
If you device show up, then you can flash twrp by command
fastboot flash recovery "path"/"twrp file name".img
here2for said:
hi, followed link and d/l the EDL tool. When I run it it looks for the phone but cannot find. In my device manager it shows Android phone>Android Bootloader Interface but no QC 9008 port. If I run ADB it cannot find device either. When I power my phone it goes right into boot loader...I can toggle to recovery and try to run a package from SD card but it will run but generates error "footer is wrong".....thoughts ??
Click to expand...
Click to collapse

mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!

....tried to install a couple different roms (placed them on the SD card) twrp....begins to install but then generates the error - "zip signature verification failed" ?? have tried resurrection remix and aokp nougat for axon 7.... get same error. Thoughts please

you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
here2for said:
mmm...progress, got twrp to load. I see that the oreo 8.1 upgrade is available , will try to load it on. Let you know if any hiccups. tx for the help so far !!!
Click to expand...
Click to collapse

llaalways said:
you are welcome.
Once your twrp is loaded, you device is definitely rescued.
first, install latest twrp3.2.1.7 img from twrp, if it is not the latest.
then format data, and wipe everything, then copy modded latest stock rom zip file and corresponding bootstack, magisk16.4, to sd card if it can be mounted, or to internal storage otherwise.
Install bootstack, latest modded stock rom, magisk 16.4, factory reset, and restart.
Click to expand...
Click to collapse
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck

which model is your phone? A2017U, A2017G, or A2017?
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Tx Chuck
Click to expand...
Click to collapse

I suggest stock rom, you can follow this post to flash it.
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
llaalways said:
which model is your phone? A2017U, A2017G, or A2017?
Click to expand...
Click to collapse

axon 7 almost bricked....
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse

Do not forget install Magisk16.4 after install ROM.
And try factory reset and then reboot disemmcwp.
If there is still problem, try format data again.
here2for said:
here2for said:
llaalways... thank you for the help with this, much appreciated. In your last reply are you referring to 3 files ( rom, bootstack and magisk16.4 ) ? if so which rom and bootstack would you suggest....
Update - was able to install DrakenFX bootloader and stock system with TWRP. Did the install with no errors and both showed successful.
Now when I reboot or power on the phone it boots directly into fastboot. From there I can load recovery which goes to TWRP. How can I get it to boot properly into the OS?
Thank you, Chuck
Click to expand...
Click to collapse
Click to expand...
Click to collapse

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