Database Develop

Soft bricked phone? Can't install recovery and can't install a rom

Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks

Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!

Yeah that sorted it thanks a lot

Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/

@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,

jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!

Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it

@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.

[ROM/GUIDE] How to Restore Stock A2017U B20 Firmware and Re-lock Bootloader

First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit

As tennear has noted, do NOT backup or restore the EFS partition.

Never restore EFS using TWRP. You will lose its contents and probably your IMEI.

@tennear Thanks for the heads up. I'll remove that part from my guide.

Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?

mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?

Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?

mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.

Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk

i can't found same file u can upload again?

Yeah.... most links are dead. Does anyone else have them?

Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.

Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.

Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.

Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?

I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.

@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.

Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.

Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now

[How-To] Install Oreo OTA! [T-Mobile]

*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files

There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.

Screenies
Here you go

Installation went smooth. thanks for the OTA.

now towait for the root and all will be set

wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.

Making a test twrp real quick

Damn...thanks for your work

joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk

Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!

can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff

where's the TWRP, so only use a fastboot flash boot image.zip?

joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!

@jhofseth please write me on hagnouts

please message me on hangouts people who want to help [email protected]

When you brick and have to go to a leaked 8.0 image

Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.

Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?

P10 adb and HWOTA Flashing partition length get error (SOLVED)

I keep getting the same error while trying to flash anything to my p10 and I can't get round it. When I try flashing an update.zip from twrp I get error: 9. I can however flash a system.img for some reason. Ih vae tried force updating (vol+ vol- pwr) with an update.app in dload but that gets to 5% then fails. The device is originally VTR-L09. HWOTA gives the same partition length get error so I can't use that either. At this point I just want the stock firmware.
Any ideas anyone?

HWOTA is not for Oreo - on Oreo the partition scheme is different.
You can search for "HWOTA8", but I don't know if it supports P10.
Otherwise you can use my guide - it works with the same script commands as HWOTA, but modified for Oreo. You just need a sd card and you need to follow "Tutorial 2".

Jannomag said:
HWOTA is not for Oreo - on Oreo the partition scheme is different.
You can search for "HWOTA8", but I don't know if it supports P10.
Otherwise you can use my guide - it works with the same script commands as HWOTA, but modified for Oreo. You just need a sd card and you need to follow "Tutorial 2".
Click to expand...
Click to collapse
So i tried the method 2 and after installing oreoupdate.zip it rebooted into twrp. So i tried rebooting normally and it just went to huawei eRecovery. Should I do forced update? (vol+ vol- pwr)
Or maybe shoud i install the oreo twrp?
edit: I tried installing update.zip again with twrp 3.1.1-0 and it just booted back into twrp, what now?
edit2: I tried unpacking the update.app but got an error saying "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 38059 Got: 180" could it be a problem that it say ramdis instead if ramdisk?

Jyndon said:
So i tried the method 2 and after installing oreoupdate.zip it rebooted into twrp. So i tried rebooting normally and it just went to huawei eRecovery. Should I do forced update? (vol+ vol- pwr)
Or maybe shoud i install the oreo twrp?
edit: I tried installing update.zip again with twrp 3.1.1-0 and it just booted back into twrp, what now?
edit2: I tried unpacking the update.app but got an error saying "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 38059 Got: 180" could it be a problem that it say ramdis instead if ramdisk?
Click to expand...
Click to collapse
If you did everything exactly as I wrote it in my guide, it should boot into TWRP. TWRP shouldn't boot after you installed the oreoupdate.zip because the script should've overwrite it with a custom Huawei recovery.
Try it again and post the TWRP log please.

Jannomag said:
If you did everything exactly as I wrote it in my guide, it should boot into TWRP. TWRP shouldn't boot after you installed the oreoupdate.zip because the script should've overwrite it with a custom Huawei recovery.
Try it again and post the TWRP log please.
Click to expand...
Click to collapse
It is certainly having a problem because I think it might actually be crashing instead of rebooting twrp
I couldnt paste the log so i put it here: https://justpaste.it/1ijaz

The log tells me, that TWRP tries to install the three update zip files and you did not install oreoupgrade.zip - it's not in the log.
Can you please post a screenshot of /sdcard/oreoupdate?
The script should install the modified stock recovery, which is in /sdcard/oreoupdate/, then the script put three install commands in cache for this recovery. After thisthe script reboots into stock recovery.

Jannomag said:
The log tells me, that TWRP tries to install the three update zip files and you did not install oreoupgrade.zip - it's not in the log.
Can you please post a screenshot of /sdcard/oreoupdate?
The script should install the modified stock recovery, which is in /sdcard/oreoupdate/, then the script put three install commands in cache for this recovery. After thisthe script reboots into stock recovery.
Click to expand...
Click to collapse
I definitely isntalled oreoupdate.zip but I feel like twrp is crashing part way as it closes almost instantly then reboot and tries to install the rest. I did it again anyway:
https://imgur.com/gallery/VyoUK
https://justpaste.it/1ijtv
should I maybe try reinstalling twrp and all the files?

Okay. First you need to rename "update_full_VTR-L09_hw_eu.zip" to "update_full_hw.zip"
But this should produce the problem you have.
Somehow the script doesn't install the stock recovery.
Can you please install this TWRP version with following fastboot command:
Code:
fastboot flash recovery_ramdisk TWRP.IMG
Then try it again. If not, can you please test if adb is working with
Code:
adb devices
It should show you your device if it's working. Some P10 are having problem with TWRP and ADB.

Jannomag said:
Okay. First you need to rename "update_full_VTR-L09_hw_eu.zip" to "update_full_hw.zip"
But this should produce the problem you have.
Somehow the script doesn't install the stock recovery.
Can you please install this TWRP version with following fastboot command:
Code:
fastboot flash recovery_ramdisk TWRP.IMG
Then try it again. If not, can you please test if adb is working with
Code:
adb devices
It should show you your device if it's working. Some P10 are having problem with TWRP and ADB.
Click to expand...
Click to collapse
Nothing shows when I do adb devices...
edit: also VTR_RECOVERY_OREO_NoCheck.img was called VTR_RECOVERY_OREO-NoCheck.img with the dash for some reason. made no difference though

Jyndon said:
Nothing shows when I do adb devices...
Click to expand...
Click to collapse
Okay than there's a manual method:
In TWRP open the Terminal and enter following commands:
Code:
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
This commands take a few seconds but the shouldn't give you any output.
If you get an output, post it here, please.
If not continue with following commands:
Code:
echo --update_package=/sdcard/oreoupdate/update.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_full_hw.zip >> /cache/recovery/command
reboot recovery
Again, no output for each command. If there's any output, post it here.
eRecovery should start and install.

Jannomag said:
Okay than there's a manual method:
In TWRP open the Terminal and enter following commands:
Code:
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
dd if=/external_sd/oreoupdate/VTR_RECOVERY_OREO-NoCheck.img of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
This commands take a few seconds but the shouldn't give you any output.
If you get an output, post it here, please.
If not continue with following commands:
Code:
echo --update_package=/sdcard/oreoupdate/update.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/oreoupdate/update_full_hw.zip >> /cache/recovery/command
reboot recovery
Again, no output for each command. If there's any output, post it here.
eRecovery should start and install.
Click to expand...
Click to collapse
I put those last commands in and nothing has happened its still in the terminal. what now?

No output in twrp terminal for each command? Reboot to recovery will start TWRP?

Jannomag said:
No output in twrp terminal for each command? Reboot to recovery will start TWRP?
Click to expand...
Click to collapse
I didnt get any outputs from the first two but the last three didn't show anything after. Did I need to exclude the echo?
and it reboots to twrp when rebooting to recovery
Edit: like the first two show and input thing an output with some stuff being copied after and it shows a time for execution but the last three that start with echo didnt do anything, just started a new line.

Moto G7 plus TWRP installation issues/confusion

Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks

I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.

timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?

timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.

chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse

I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins