[RECOVERY] TWRP 7.1 (unofficial)

Search This thread

mattx1002

Member
Nov 22, 2014
12
11
Not A City, Somewhere
Tried it, but...

I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.

Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys

v1.2.0B09 installed
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
Oh. Yeah. I'll fix that. The problem is that the flash tool wants an image that is an even multiple of the sector size.

In the mean time, you should be able to use dd in adb shell from the old twrp to update.
I flashed the beta to recovery, and this is what I got:
Code:
PS C:\tuliptool> .\tuliptool-win64.exe write recovery
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
log: start 1181696, num 45220
Write 23152640 bytes, 45220 sectors
Failed: Unknown error
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Unknown error
Afterwards, I tried to boot into recovery, and I got some sort of "Factory Test Mode" screen. I'm assuming that means I don't have a recovery or something, because the flashing failed.

Phone Info:
Code:
ZTE/P852A11/tulip
7.1.1/NMF26V/20170519.163520
user/release-keys

v1.2.0B09 installed
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
Yes just flash the recovery. Boot to recovery by holding the volume up button with the power button. I don't think stock updates recovery at boot, but I'm not sure.

Note you will need the custom boot image with verity disabled if you change anything in the system partition. I think SuperSU also disable verity, or at least can.
Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin
 

MrWhite0429

Senior Member
Aug 2, 2016
218
66
NLR
Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.

---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------

I can not get back into EDL or Recovery. ugh....

---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------

UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
I'm confused how you killed android by flashing recovery.

Is it possible you flashed the modified b12 boot image on a b14 system? If that's the case just flash back the backup. I'll create a b14 boot image asap.
Ok. Twrp flashed successfully. Now my device just hangs at the splash screen and will not go any farther.

---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------

I can not get back into EDL or Recovery. ugh....

---------- Post added at 02:32 AM ---------- Previous post was at 02:26 AM ----------

UPDATE: I am able to get back into TWRP if i pull off some very specific button combinations. However thats all im able to do. Android will not boot.
 

MrWhite0429

Senior Member
Aug 2, 2016
218
66
NLR
I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14

---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------

Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold

Power button THEN press and hold volume up.

Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.

---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------

Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
Let me know if you get the device working again. I can help if you can't figure it out.

I am still confused about what could have happened...
I didnt flash any boot image. I flashed the TWRP in this thread with the tulip tool. and did not flash any boot.bin at all. I am on B14

---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------

Also Ive noticed to get back into TWRP if this happens to anyone else. You have to hold

Power button THEN press and hold volume up.

Once the ZTE Screen loads you must tap the power button repeatedly and then for some reason TWRP will boot.

---------- Post added at 02:46 AM ---------- Previous post was at 02:39 AM ----------

Flashed backup and now device will not boot into recovery or android at all, However I am able to still get into EDL.
 

MrWhite0429

Senior Member
Aug 2, 2016
218
66
NLR
Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
Oh.... by any chance did you let twrp mount system read/write? Even once? That destroys the verity integrity.
Ok. I am able to get the device to boot into stock recovery and EDL mode now. However android still will not load. Device has been sitting at ZTE Splash screen for almost 10 mins.
 

MrWhite0429

Senior Member
Aug 2, 2016
218
66
NLR
I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?
 

tdm

Inactive Recognized Developer
Jun 7, 2011
2,139
3,666
Seattle
Let's assume you did allow twrp to mount system RW and your verity integrity is destroyed. Just upload the original b14 boot image and I'll make a modified version with verity disabled. That should get you running again.

Note I'm getting ready to go out with my wife so it will be a few hours until I can do that.
I dont believe I did. Unless I did it without knowing. When TWRP booted it asked me for a password. I selected cancel. Then I selected Read Only. And then I selected reboot to system. and Here I am. With That being said if it may have destroyed the verity then im stuck until I can flash a B14 Non-Verity boot?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Current build
    tulip-twrp-7.1-r1.img
    MD5: bdf289666fc7262b8f3af7f5b579ecaa
    Built: Oct 18, 2017

    Installation instructions
    The easiest way to install is using tuliptool. See the tuliptool thread for details.

    Notes
    r1 should be fully functional. Please report any bugs.
    4
    I figured it all out, thanks for the suggestions, MrWhite0429!

    Alternate methods for getting into EDL
    TWRP method:
    Boot into the TWRP recovery, go into Advanced>Terminal
    Once there, type in "reboot edl"
    You're now in EDL!

    ADB method:
    Either in the OS or in TWRP (I still can't get ADB to work in TWRP, I dunno why), connect with ADB and use the command "adb reboot edl"

    I hope this helps someone else when the volume key combination doesn't work!
    3
    fist of all thanks to @tdm for his works (I just realized that is doing all by himself), as said in another thread after installing TWRP and flashing AOKP and his Lineage 14 I have ghost touch that doen't allow me to write or use the phone.
    Now I'm back to sto, I'm going to test if can I flash magisk patched boot image to root and see if the ghost touch will be back, otherwise, could it be an incompatibility between yout TWRP and the g&arbest EU (eu plug etc.) phone?
    Looks like I'm the only one that have this problem, but as far as I can see mostly peopole that populate the Axon thread has not the EU, mybe the USA or the UK.If I'lll be able to flash the boot.im I will let you know.
    Thank you everyday for your work!
    3
    Well, it depends on exactly how you want to backup.

    I would consider a full backup to be boot, system, and data. (and vendor, but this device doesn't have a separate vendor partition). You can't really go wrong doing these.

    However, it is a waste of time to backup stock boot and system every time because they never change. So you can take a backup of boot and system, and save this off in a safe place. Then you only need to backup data.

    I can't wait until the alpha/beta stage is done, @tdm you sir are epic!

    Also, since this is a new device to me with root and related things and I don't remember how to back up the original rom, how can I back everything up before I start flashing away?
    2
    Yes just flash the recovery. Boot to recovery by holding the volume up button with the power button. I don't think stock updates recovery at boot, but I'm not sure.

    Note you will need the custom boot image with verity disabled if you change anything in the system partition. I think SuperSU also disable verity, or at least can.
    Is the phone able to boot properly if I flash just the recovery without flashing the boot.bin