Database Users

Bricked System - Need Image for fastboot or ideas

Hello,
somehow I had a problem that many apps force closed after doing something, so I tried flashing opengapps - worst idea. I started the phone and nothing worked because I always get force close on Setup Assistent.
I were on Cydras Rom (https://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742). So now I tried overflashing it again but somehow it says successfully installed and also "cant unmount system: volume not found". The system image is now about 900mb big, the zip 1.3gb - can't be possible. It doesn't but and stuck on the first Leeco screen. Now I tried sideload: failed - invalid command..
Well, I tried getting another rom and put it on phone by MTP in TWRP.. Same problem - TARS causes boot into Recovery and CM13 by Superluminal doesn't even flash: stuck on "patching system image unconditonally".
Has someone a solution or more like is there any system image I can flash through fastboot?
Or could someone make one? PLEASE!
I think somehow the system can't be mounted...

Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?

Somehow I tried this twrp backup: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
Now I can't mount storage, because it's encrypted... -.-
I have x720 and I don't really know what caused the FCs, the last I remember was uninstalling Android WebView.
Now I have to try to get access to storage again..
## bootloader is unlocked

dark_prince said:
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Click to expand...
Click to collapse
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?

Grossoshop ROM is fastboot installable.

Presterin said:
Grossoshop ROM is fastboot installable.
Click to expand...
Click to collapse
Link?

idragonx said:
Link?
Click to expand...
Click to collapse
Sure, here you go: http://blog.grossoshop.net/leeco-x720-grossoshop-rom-italiano-ota/

idragonx said:
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Click to expand...
Click to collapse
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...

dark_prince said:
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
Click to expand...
Click to collapse
How to reformat? I tried wiping all & make it ext4 in TWRP.
Sideload doesn't work: * failed to read command: Invalid argument

Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)

dark_prince said:
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
Click to expand...
Click to collapse
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"

idragonx said:
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?

Presterin said:
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Click to expand...
Click to collapse
I used this from the post: https://mega.nz/#!tUkUQJwZ!h3tniWVWlSiYJICadW7MuEdYLDFKfNmNcEOBQ-eL1JM

dark_prince said:
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
Click to expand...
Click to collapse
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot
#####
I GOT IT.
Finally - https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
It could do it using fastboot - oh god thanks. Now I try to flash my custom rom.

idragonx said:
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot.
Click to expand...
Click to collapse
mD5 verified?
Alright try this. Get latest CM13 build from teamsuperluminal website and also get the x720 patch from there too. Then in TWRP (while connected to USB) go to advanced wipe > cache + system + dalvik + data.
Open downloaded CM13 zip in 7-zip file manager, go to META-INF > Android folder and extract only the updater_script file. (Should be in that or in a subwoofer). Keep the 7-zip opened and dont close it.
Open the updater_script file in notepad++ and remove first line which starts with "assert". Save
Then drag drop it back into 7-zip( in the same folder structure.) Close 7-zip after
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.

dark_prince said:
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
Click to expand...
Click to collapse
Thank you very much for your help, but finally I found the 18s from grossoshop with the BATCH - it could fastboot load the system.img partially and now it boots <3

Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...

dark_prince said:
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
Click to expand...
Click to collapse
Well, but I can't flash back my cydras ROM

Imho it should work now to go back to stock. Download official Chinese firmware zip file (not OTA) and rename it to update.zip
Put it in internal storage (not into any folder)
Go to fastboot and flash stock recovery.
Then boot into stock recovery and apply update.zip
Result should be profiting.
idragonx said:
Well, but I can't flash back my cydras ROM
Click to expand...
Click to collapse

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!

magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.

worked for me perfectly

pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.

Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.

pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.

Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

[GUIDE] 2 Minutes Magisk installation, Best Method +OTA

Hey hey hey !!! I'm back for a new method, for flash Magisk without patched_boot.img or select current-slot etc, just by do 2 things. And it works for all phone version, Sable, Beta.... ( We use TWRP temporarily, so after the process, TWRP is gone)
Credits :
Me for the idea.
@Frustrated Indian the tester.
@TingyiChen for this nice TWRP.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about features
included in this GUIDE before using it! YOU are choosing to
make these modifications.
Of course first you must have the drivers installed on your pc. And an unlocked bootloader + unlock critical partition, if it is not, follow this procedure :
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
- And follow phone on screen steps to validate unlock bootloader...
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
Downloads :
- TWRP here
- Magisk Latest Beta / Stable (if you prefer) zip
- Magisk Uninstaller zip
Steps :
- Download TWRP
- Copy it to your pc adb folder
- Rename it to twrp.img
- Download Magisk Installer
- Download Magisk Uninstall
- Place these 2 folders on your phone storage
- Reboot phone to fastboot
- Open fastboot command prompt on your pc
- Type "fastboot boot twrp.img" without quotes
- Your phone will boot twrp
- Decrypt data with your pin if needed
- Click install and select the Magisk Installer zip, swipe to confirm
- Wait for the process
- Reboot
That's it !! You now have root on your phone, and TWRP is gone.
If you have issues you can uninstall Magisk with the Uninstaller zip.
For OTA just uninstall Magisk using Magisk Manager, by flash the stock boot.img to your current-slot, or using the zip and flash it like the Magisk Installer.
Check my other thread, Part 3 : OTA for more informations.

-reserved-

I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?

After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773

Magisk link not work.

kishd said:
After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773
Click to expand...
Click to collapse
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.

SpectraFun said:
Magisk link not work.
Click to expand...
Click to collapse
Fixed. sorry it was an issue when we click links using XDA phone app. Have a nice day.
Matteo

Adairo said:
I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?
Click to expand...
Click to collapse
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).

Atlas/ML said:
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.
Click to expand...
Click to collapse
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.

kishd said:
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.
Click to expand...
Click to collapse
flash stock kernel has no sense. that's why it doesn't work. if you have issue you should just flash boot.img or flash magisk uninstaller in twrp like magisk zip. sometime hex kernel cause some issues . for me with all version tested, with help of the maintainer @draco I'm not able to boot fine. I have a green glitchy screen etc, and after some boot my device screen stuck on black screen.

works fine, thank you!

bavmouse said:
works fine, thank you!
Click to expand...
Click to collapse
I'm glad to hear it, enjoy

Atlas/ML said:
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).
Click to expand...
Click to collapse
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2

Adairo said:
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2
Click to expand...
Click to collapse
I recommend you to use magisk and install systemless xposed.

Atlas/ML said:
I recommend you to use magisk and install systemless xposed.
Click to expand...
Click to collapse
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition

Adairo said:
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition
Click to expand...
Click to collapse
okay, give me results if it works. good luck

Atlas/ML said:
okay, give me results if it works. good luck
Click to expand...
Click to collapse
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device

Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
hum, interesting

I'm on September update and want to update to the October one, I've tried doing everything in Part 3 but no success. Any solution that let me keep my data?

Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
Xposed will not work untill we get a deodexed stock rom or custom rom

Deprecated

Obsolete, move to the new thread here below.
(EASY ROOT) Z982 via QFIL or TWRP B20_Modified SYSRW 4/8/19

xxMoon said:
!!!!!WARNING!!!!!!
This will wipe your phone.
Prep
Enable USB Debugging and OEM Unlocking on your phone
Install ADB Driver
Install EDL Drivers
Restart Computer
Files
ZTE_BLADE_Z_MAX_edl.7z
Guide
1. Extract the folder inside ZTE_BLADE_Z_MAX_edl.7z to your desktop.
2. Connect your phone to your computer.
3. Open the folder "ZTE_BLADE_Z_MAX_edl" that you just extracted.
4. Right click on ZTE_BLADE_Z_MAX_edl.bat
5. click run as administrator
6. Press Y
7. Press 1
8. Press 2
9. Press Y
10. Press N
11. Press 1
12. Press 3
13. Press Y
14. Press N
15. Press Q
16. Disconnect your phone from the computer.
17. Press and hold "Power and Vol+" untill the ZTE Logo Appears then release the power button while continuing to hold vol+
18. Once booted into TWRP Recovery, swipe to allow modifications.
19. Tap Wipe
20. Tap Format Data
21. Type yes
22. Tap Blue checkmark
23. Back out to the main screen.
24. Tap Reboot
25. Tap System
"Initial Boot will take some time, and may even reboot"
"If more than 5 mins elapses, press and hold power button to restart device"
26. Setup Android
27. Locate Magisk and open it.
28. Install magisk manager "May have to anable unknown sources first"
!!!!DO NOT UPDATE MAGISK!!!! Only update the magisk manager.
Profit!!!!
Click to expand...
Click to collapse
nvm fixed my issue

So upto magisk v18.0 works fine. However, 18.01 causes the phone to go into dfu mode.
It is important that you only update magisk manager, not magisk itself.

xxMoon said:
So upto magisk v18.0 works fine. However, 18.01 causes the phone to go into dfu mode.
It is important that you only update magisk manager, not magisk itself.
Click to expand...
Click to collapse
Even though it says I have 18.0 installed, whenever I download a module it says that I need version 17.0+ which sucks because I really want to change the fonts. Whenever I try booting into twrp to manually flash, it never shows my files, no matter where I put them, I tried using Es file explorer to move them to/system/bin but it says operation failed every time so I do not know what to do at this point. I cant flash files via twrp or magisk and I really would like some help on this.
---------- Post added at 06:40 PM ---------- Previous post was at 06:32 PM ----------
If so can you give me a detailed explanation on how to flash modules through ADB, seems that it is my only option until Magisk lets me download what I want. All I want to do right now is change my fonts so I can get rid of these blob emojis. If it helps, the file I'm trying to obtain offf magisk is called IOS 12.1 Emoji but like I said, it says I need v17.0 to install and gives me installation failed everytime

Good ****!!!!

Since a lot of people are having problem with magisk all just rebuild my boot.img so you won't have to add the su file. Then hopefully people would use it because it currently up to date without any issues I can find

Jasonls221 said:
Since a lot of people are having problem with magisk all just rebuild my boot.img so you won't have to add the su file. Then hopefully people would use it because it currently up to date without any issues I can find
Click to expand...
Click to collapse
I did a whole reflash using yours and magisk wasnt there so I had to go back to the original one posted from moon. Can you explain what you did to flash yours and get it to work? Can you also re-upload the file on here? Thank you

evtoofly said:
I did a whole reflash using yours and magisk wasnt there so I had to go back to the original one posted from moon. Can you explain what you did to flash yours and get it to work? Can you also re-upload the file on here? Thank you
Click to expand...
Click to collapse
The only problem with mine was you had to transfer the su file I supplied to /system/bin

Jasonls221 said:
The only problem with mine was you had to transfer the su file I supplied to /system/bin
Click to expand...
Click to collapse
so without fully reflashing , all i have to do is use a file explorer to transfer su, and then use twrp to flash the boot image only? I really dont wanna have to wipe my device again and set up my phone again
---------- Post added at 05:35 AM ---------- Previous post was at 05:33 AM ----------
Thats another problem I face as well, no file explorer has let me move a file to the bin folder so how did u do it?

evtoofly said:
so without fully reflashing , all i have to do is use a file explorer to transfer su, and then use twrp to flash the boot image only? I really dont wanna have to wipe my device again and set up my phone again
---------- Post added at 05:35 AM ---------- Previous post was at 05:33 AM ----------
Thats another problem I face as well, no file explorer has let me move a file to the bin folder so how did u do it?
Click to expand...
Click to collapse
I used twrp and adb. adb push su /system/bin

Jasonls221 said:
I used twrp and adb. adb push su /system/bin
Click to expand...
Click to collapse
where did u place the boot file on your device for twrp because twrp never sees files for me
also with the su file, can I put that anyweher on my device and run that adb command for it to transfer? sorry im confused
edit: I managed to get everything working and now I can install modules and also have the latest version of Magisk, thank you!

evtoofly said:
where did u place the boot file on your device for twrp because twrp never sees files for me
also with the su file, can I put that anyweher on my device and run that adb command for it to transfer? sorry im confused
edit: I managed to get everything working and now I can install modules and also have the latest version of Magisk, thank you!
Click to expand...
Click to collapse
Cool, I'll try to make this automated but I'm not good with windows

I cant wait for roms to come out for this device! Also gotta learn how to turn s secure on for this device , now that its rooted.

evtoofly said:
I cant wait for roms to come out for this device! Also gotta learn how to turn s secure on for this device , now that its rooted.
Click to expand...
Click to collapse
I could make a custom ROM once there's a TWRP recovery able to flash zips successfully

good job...

Legit works like a charm.. Very impressive!! All hail the ZTE PIMP!!
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
Question i have a zte z970 that has had the firmware deleted. Anyone know of a fix for this?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
I can boot into normal recovery but i cant flash any of the stock firmware i can find....

For z970 , that is a easy fix, get your twrp firmware backup and restore it ...Don't tell me you don't have the backup...I have backup but it interludes my person things together

Would I be able to install systemless xposed via magisk or no?

evtoofly said:
Would I be able to install systemless xposed via magisk or no?
Click to expand...
Click to collapse
I've tried, but I dont think it worked.

xxMoon said:
I've tried, but I dont think it worked.
Click to expand...
Click to collapse
It actually does work. With the latest magisk, all you do is download the xposed sdk 25(Android 7.1) module on magisk and then download xposed 3.15 apk installer and xposed will work. I have been using it all day and already have some xposed modules installed:good:

Update to OxygenOS 9.0.0

Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
Code:
Updating partition details...
...done
Full SELinux support is present.
Data successfully decrypted
Updating parition details...
...done
MTP Enabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
[COLOR="Red"]E:String resource 'zip_compatible_err' not found.
Using default value.
Zup Treble compatibility error!
Invalid zip file format!
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip[/COLOR]
Updating partition details...
...done
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks

Mouchoir said:
Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks
Click to expand...
Click to collapse
Hello, I can't recommend any guide on outside of xda cause they're not consistent...
Just follow this guide in the first post https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 would help you.
You can't flash twrp 3.3.1 cause you need newer firmware, pie firmware.
Please answer all the questions:
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?

Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo and use a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using an Oreo TWRP if you're on Oreo Firmware/ROM or Pie TWRP if you're on Pie Firmware/ROM) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Click to expand...
Click to collapse
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks

Mouchoir said:
Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks
Click to expand...
Click to collapse
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).

strongst said:
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).
Click to expand...
Click to collapse
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP

Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
Clean flash wipes system and data, so no os, data and settings.

PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?

Mouchoir said:
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?
Click to expand...
Click to collapse
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8

strongst said:
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8
Click to expand...
Click to collapse
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Code:
Data successfully decrypted
Updating parition details...
...done
Successfully decrypted with a default password.
Updating parition details...
...done
Full SELinus support is present.
MTP ENabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
Patching system image unconditionally...
E1001 Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR:7
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip[/COLOR]
Updating partition details...
...done

Mouchoir said:
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Click to expand...
Click to collapse
Error 7 is corrupt file, you'll find about it here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003/page591

Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7

Mouchoir said:
Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7
Click to expand...
Click to collapse
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions

strongst said:
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions
Click to expand...
Click to collapse
As stated here, I used 7zip
PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.

Yes because to use fastboot you have to be in fastboot mode...

PierreVicquery02 said:
Yes because to use fastboot you have to be in fastboot mode...
Click to expand...
Click to collapse
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?

Mouchoir said:
As stated here, I used 7zip
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.
Click to expand...
Click to collapse
Mouchoir said:
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?
Click to expand...
Click to collapse
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device

PierreVicquery02 said:
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device
Click to expand...
Click to collapse
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out

Mouchoir said:
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out
Click to expand...
Click to collapse
That's such a strange bug. If you are in fastboot, it's impossible for your PC to recognize it in ADB mode. Try with another computer or use unbrick tool to clean your phone (it installs Oxy 9.0.8)

Well I managed to see the fastboot thanks to the EOM cable but I think I bricked my phone