Unlock bootloader in ur OP8T (For T-Mobile and Verizon variants u need unlock code) (This guide is for non T-Mobile and non Verizon variants):-
1. Enable Developer options by going to settings-About Phone and then keep tapping build number until a dialogue comes saying developer options are enabled/unlocked/on.
2. Go to Developer options by :-
Settings-system-Developer options.
3. Enable OEM Unlocking.
4. Enable USB debugging.
5. Now be on ur PC.
6. Install latest adb and fastboot drivers. (U can install these):-
https://www.androidfilehost.com/?fid=746010030569952951
7. Reboot ur OP8T to bootloader after shutting down ur phone by holding power button+ both the volume buttons.
8. Open command prompt in ur PC and connect ur OP8T to ur PC via a USB cable and enter fastboot.
9. Enter
fastboot devices
Click to expand...
Click to collapse
10.After that Enter
fastboot flashing unlock
Click to expand...
Click to collapse
11. Enjoy! Ur bootloader is unlocked.
Steps to ROOT OP8T (Make sure that ur bootloader is unlocked)(Use USB Cable in the whole process):-
1. Download the Full Stock ROM (not incremental) whose version matches the Oxygen OS version running on ur phone,Download the ROM thru Oxygen Updater (If ur gonna download the ROM thru Oxygen Updater make sure ur on the latest software update) (here is the link):-
https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
-----OR (If Oxygen Updater aint working for u)-----
U can follow this semi-twrp method to extract the boot.img and patch it with magisk later (Skip to Step 11 if u follow twrp method):-
https://forum.xda-developers.com/showpost.php?p=83762929&postcount=17.
2. Transfer the ROM zip file to ur PC.
3. Download and install Python3 in ur PC (here is the link)(This link is for windows only):-
Python Releases for Windows
The official home of the Python Programming Language
www.python.org
TICK THE ADD PYTHON TO PATH OPTION IN PYTHON SETUP.
4. Download and install Payload dumper in ur PC (download from this link if ur running windows) (u can find others for linux and MacOS as well).
https://androidfilehost.com/?fid=818070582850510260
5. Extract the Payload dumper zip.
6. Extract the ROM u transferred to ur PC.
7. Put payload.bin from the folder where u extracted the ROM to "payload_input" folder (payload_input folder will be there where u have extarced payload dumper zip)
8. Run payload_dumper.exe
9. The files which are present in payload.bin will be extracted in payload_output folder.(it will be in payload dumper folder which we extracted earlier).
10. Now, copy boot.img from payload_output and paste it in ur OP8T.
11. Download and install Magisk manager apk from here:-
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
12. Open Magisk manager.
13. Go to settings.
14. Click on update channel.
15. Select canary.
16. Go back and Click on install button.
17. Click on "Select and patch a file" and select boot.img .
18. The magisk_patched.img will be saved in ur internal storage find it and transfer it to ur PC.
19. Now open command prompt in ur PC where u have copied that patched boot.img and reboot ur OP8T to bootloader.
20. Connect ur OP8T to ur PC and enter
fastboot devices
Click to expand...
Click to collapse
21. Enter
Fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Or for safe method without bricking or bootloop
Fastboot boot magisk_patched.img
Click to expand...
Click to collapse
22. The magisk_patched.img will be flashed/booted.
23. Now reboot (if ur in fastboot reboot by fastboot reboot).
24. Now go and open magisk app and see if it says installed then ur rooted if u did the safe method in step 21 then go to magisk and click on direct install and reboot.
25. Done! Ur phone is rooted!
If u have the error that python is not recognised as a internal or external command then follow this video:-
Enjoy!
How do I download the firmware from oxygen updater if im up to date? I have advanced on already, I just am not seeing an option to do so.
rtown195 said:
How do I download the firmware from oxygen updater if im up to date? I have advanced on already, I just am not seeing an option to do so.
Click to expand...
Click to collapse
Hi! Turn on advanced mode and go back to the main page of Oxygen Updater, there should be a download update bar at the bottom of the screen click on that and ur ROM zip file will start downloading.
This is what I got after enabling advanced and full
If I can just get that ota zip, I'll be good.
Heya try reinstalling Oxygen Updater and enable advanced mode in settings and select full update option then the download option should show. It worked for me!
I just did it. Absolutely nothing different
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
The only thing that changes is the discord invite
rtown195 said:
I just did it. Absolutely nothing different
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
The only thing that changes is the discord invite
Click to expand...
Click to collapse
Well it works for me and a couple of other people on TG too! U must be doing something wrong!
rtown195 said:
I just did it. Absolutely nothing different
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
The only thing that changes is the discord invite
Click to expand...
Click to collapse
You'll have to wait for the 11.0.2.3 update, which is the latest. OP sends it in waves, mine arrived yesterday.
Well damn
yeah I cant get the download option on Oxygen either. Tried unisntalling/installing app but no go
So I buy a phone specifically to have more freedom to mod, i have my bootloader unlocked and I can't even root my **** bc a Pos phone company is choosing to not give me the new firmware but others get it. This is so cool.
rtown195 said:
So I buy a phone specifically to have more freedom to mod, i have my bootloader unlocked and I can't even root my **** bc a Pos phone company is choosing to not give me the new firmware but others get it. This is so cool.
Click to expand...
Click to collapse
I think you can use the oxygen updater app to get the latest firmware.
I got it. Used adb TWRP to extract my img
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Extracted my own img with adb TWRP. No thanks to this guide
rtown195 said:
I got it. Used adb TWRP to extract my img
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Extracted my own img with adb TWRP. No thanks to this guide
Click to expand...
Click to collapse
It's good that you got it on your own but please be respectful to this guide. It has helped a lot of people.
How do we handle ota updates in future if we root with this method? How can we flash the new updates without twrp?
When you update, after downloading and installing new update before rebooting go to magisk manager and install magisk use the inactive slot option. Reboot still rooted.
---------- Post added at 02:46 PM ---------- Previous post was at 02:40 PM ----------
If you can't get your rom to extract your boot, I used the semi-broke twrp method mentioned in another rooting thread here on xda. Just make sure you use the modded magisk manager listed in thread to patch your boot, it's called the "debug apk". I spent a couple hours trying to use reg magisk manager 8.0.2 and don't work.
kjslabber said:
When you update, after downloading and installing new update before rebooting go to magisk manager and install magisk use the inactive slot option. Reboot still rooted.
---------- Post added at 02:46 PM ---------- Previous post was at 02:40 PM ----------
If you can't get your rom to extract your boot, I used the semi-broke twrp method mentioned in another rooting thread here on xda. Just make sure you use the modded magisk manager listed in thread to patch your boot, it's called the "debug apk". I spent a couple hours trying to use reg magisk manager 8.0.2 and don't work.
Click to expand...
Click to collapse
I also gave the link for Magisk Canary (debug.apk) ?
rtown195 said:
I got it. Used adb TWRP to extract my img
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Extracted my own img with adb TWRP. No thanks to this guide
Click to expand...
Click to collapse
Bruh I'm from India and we get the updates pretty fast here and for ur kind information we also get pretty fast updates on Oxygen Updater too. Ur twrp method is pretty good too, If I will update the thread with ur method included it would be a pretty big thread ?.
I have follow the whole guide, step by stp (TWRP method) and now Im in a bootloop... How can i fix it ?
I patched the Boot_a.img with magisk.
Should i try the boot_b ?
Related
Since lollipop there is no manual update option in huawei updater and even the huawei stock recovery has no or less interface which has no adb sideload option. This became a crunch to flash the update which your friend got and which u dont.
This Method is Universal for all huawei devices
In order to apply ota update using this method , root access is a major requirement so be sure your device is rooted.
If u had twrp recovery , at first flash SuperSu package to root your device (Try systemless root only) .
After successfull root ,flash stock recovery from twrp and reboot system.
Step 1:
In my case b370 is the last ota i found for kiw-l22 which vsriram92 posted here . Thanks to him for posting the update before 99% users got their update :good:
Download the relevant update package (ota) which you need a relevant base package to install it on . Ex: b360 as base for b370 update
step 2:
just remember the path where u downloaded the package . Install Flashify from playstore or From Here
Select Zip file which is the third option in flashify .
step 3 :
Navigate to the path where u downloaded ota package select the update.zip (ota package).
flashify starts downloading the package to its path asks you for root access .
Grand Su permissions , Select Cwm recovery if flashify asks as the next option.
Now the phone reboots to recovery and starts flashing.
After the ota update , your device will be unrooted . so take a backup of your stock recovery by following below guide.
Enable Usb debugging and connect ur phone to pc.
navigate to adb folder and place twrp.img or recovery.img in adb folder ,open command window from the same folder and type
Code:
adb reboot bootloader
Now type
Code:
fastboot boot recovery.img
or what_ever_its_name.img
now it temporarily boots twrp , take a backup of your stock recovery and then flash twrp for permanent install and then reroot ur device.
Happy flashing :laugh::good:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
rbtrai said:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
Click to expand...
Click to collapse
You might have installed a zip which is not stock ota update . i haven't posted this without trying . I installed b370 with this method and made this live here .
i downloaded from the link provided above which vsriram92 posted...
rbtrai said:
i downloaded from the link provided above which vsriram92 posted...
Click to expand...
Click to collapse
Were you in b360 before doing this ?
Thanks again Gopi. Another great contribution.
vsriram92 said:
Were you in b360 before doing this ?
Click to expand...
Click to collapse
yes ofcourse
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Ajith san said:
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Click to expand...
Click to collapse
Nope. It was there in EMUI 3 previously. Now, we can't unless it has only update.app.
so b370 is only for the ones who gave root access to their phones?
Like your contribution. Perfectly updated to B370.
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
great
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Zacki06 said:
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Click to expand...
Click to collapse
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
ShadySquirrel said:
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
Click to expand...
Click to collapse
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Zacki06 said:
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Click to expand...
Click to collapse
TBH, I'm on a verge to start building LOS or PAC/Slim/whatever is properly maintained and fast for my own needs and ditch EMUI completely....
I'm searching for other firmwares now via FirmwareFinder, there is a probability that one is a leaked test or something like that, because it simply doesn't want to flash. If I find out something, I'll continue on thread you've linked, to avoid flooding this one.
Hi. Thanks for your guide.
I need to update my phone with several ota updates. I just need to repeat this guide's procedure until updated to the last ota or there is a better way to do that?
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
How to update step by step.. Mention it plz
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just because you can't do it, that doesn't mean it's fake.
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just follow the procedure and you will be done
Steps:
Prepare and Notice
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Phone is already Oreo firmware, only tested same brand update and downgrade.
C. Backup data, it might be restore factory default setting especially using downgrade ROM version.
D. Unlock bootloader before flash steps.
E. After update successfully, device might be locked again.
F. HWOTA8 Package (HWOTA8_2017110501.zip)
Flash Update
A. Use Vol-Dn + USB Cable to boot into fastboot mode.
B. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery.
C. Disconnect USB cable, use Vol-Up + Power to boot into TWRP.
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
Downgrade Nougat
A. Put update.zip, update_data_public.zip, and update_all_hw.zip files into HWOTA8 repack directory.
B. Run repack.bat to update zip files.
C. Go through "Flash Update" steps and use repacked zip files.
D. Enter recovery and do factory reset.
Rebrand
A. Put Put hwota8_rebrand.zip and "OEMINFO.bin" (From HWOTA) into SDCard HWOTA8 directory.
B. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery.
C. Disconnect USB cable, use Vol-Up + Power to boot into TWRP.
D. Install hwota8_rebrand.zip, it reboots and factory reset failure.
E. Enter fastboot mode and unlock device again.
F. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery and enter it.
G. Do "Downgrade Nougat" steps to the rebrand firmware, it fails and reboot but fine.
H. When going to system press "Vol-Up" to enter eRecovery, do "Low-level format data partition".
I. Wait all done and recovery menu show up, reboot and do "Downgrade Nougat" again.
J. Update should be successful this time, rebrand done.
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
albertobom said:
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
Click to expand...
Click to collapse
You should be able to install ROLLBACK with it.
I'm going to test later today.
Ok, this is update oreo for oreo?
aureliomilitao said:
Ok, this is update oreo for oreo?
Click to expand...
Click to collapse
Yes I belive and rollback as well.
albertobom said:
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
Click to expand...
Click to collapse
ante0 said:
You should be able to install ROLLBACK with it.
I'm going to test later today.
Click to expand...
Click to collapse
Rollback installed now.
You have to modify script a little though, as rollback has no public zip.
So simply remove the line that says
echo --update_package=/sdcard/HWOTA8/update_data_public.zip > /cache/recovery/command
in hwota8_update.zip's update-binary.
You should even be able to install something that's not a ROLLBACK, as long as you factory reset after.
The rollback factory resets automatically.
ante0 said:
Rollback installed now.
You have to modify script a little though, as rollback has no public zip.
So simply remove the line that says
echo --update_package=/sdcard/HWOTA8/update_data_public.zip > /cache/recovery/command
in hwota8_update.zip's update-binary.
You should even be able to install something that's not a ROLLBACK, as long as you factory reset after.
The rollback factory resets automatically.
Click to expand...
Click to collapse
Amazing. Thanks my friend.
albertobom said:
Amazing. Thanks my friend.
Click to expand...
Click to collapse
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
Thanks for the info my friend that works for me. :good:
---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
BTW you change script back before test it right?
albertobom said:
Thanks for the info my friend that works for me. :good:
---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------
BTW you change script back before test it right?
Click to expand...
Click to collapse
Of course xD
I did forget first though, and it failed because it couldn't find files...
Rollback installs fine with SuperSU and Adaway (modifies /system) installed.
ante0 said:
Of course xD
I did forget first though, and it failed because it couldn't find files...
Rollback installs fine with SuperSU and Adaway (modifies /system) installed.
Click to expand...
Click to collapse
OK then. This means I can stay beta and update whenever I want
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
@mankindtw my friends you're the best.
it worked, I used the rom on the 13th and it appeared in the FF a rom on the 27th, I downloaded the files and I did this procedure and now whenever new roms appear, just follow here
Is there a way to root Mate 9 with Oreo and which is the best method?
It works on MHAL29C567B190 EMUI 5.1?
Can I do this procedure to update ?
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
Add "Downgrade Nougat" and new HWOTA8 package.
Curiousrge said:
It works on MHAL29C567B190 EMUI 5.1?
Can I do this procedure to update ?
Click to expand...
Click to collapse
No, you should use below HWOTA, not HWOTA8
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
mankindtw said:
Add "Downgrade Nougat" and new HWOTA8 package.
Click to expand...
Click to collapse
Did I just say how much I love you?
albertobom said:
Did I just say how much I love you?
Click to expand...
Click to collapse
I guess, you might love me even more now.
Have fun playing with it.
mankindtw said:
I guess, you might love me even more now.
Have fun playing with it.
Click to expand...
Click to collapse
You're the man.
Is there a way to disable vibration of the floating navigation dock when long pressed on oreo it is really annoying?
Install Android 9.0 Pie AOSP GSI
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Pre-Requisites
Please read carefully. Any questions which are already answered in OP will be ignored.
If you have a question, not answered in OP read last 2-3 pages. Any questions which are already answered in last 2-3 pages will also be ignored.
Not being rude, but people need to start reading.
Make sure you have unlocked the bootloader.
Text Guide
Install Android 9.0 Pie AOSP GSI
1. Download AB Arm64 GSI from link in downloads. Unzip it. Windows users can use Winrar. Mac users can use the Unarchiver.
2. Download and unzip adb & fastboot linked in downloads section.
3. Place the extracted system image (step 1) in platform-tools folder. Rename it to system-arm64.img.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
8. Erase System
Windows
Code:
fastboot erase system
Mac & Linux
Code:
./fastboot erase system
9. Flash Android Pie GSI
Windows
Code:
fastboot flash system system-arm64.img
Mac & Linux
Code:
./fastboot flash system system-arm64.img
10. Wipe/Factory Reset
Windows
Code:
fastboot -w
Mac & Linux
Code:
./fastboot -w
11. Reboot
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
11. Profit. Android 9.0 Pie. Rooting might result in broken Wi-fi. So, flash back stock boot.img if your wifi is broken after rooting.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page12
Android 9.0 Pie GSI Download Links :- https://github.com/phhusson/treble_experimentations/releases
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
crazykas said:
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
Click to expand...
Click to collapse
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
munchy_cool said:
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
Click to expand...
Click to collapse
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
crazykas said:
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
Click to expand...
Click to collapse
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
munchy_cool said:
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
Click to expand...
Click to collapse
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
crazykas said:
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
Click to expand...
Click to collapse
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
munchy_cool said:
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
Click to expand...
Click to collapse
Thanks man. Will try at night. Can't wait ????
MTP doesn't work.
Streect said:
MTP doesn't work.
Click to expand...
Click to collapse
It works. Enable it in Developer Tools.
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
HTCDevil said:
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
Click to expand...
Click to collapse
did you read the OP at all? it's mentioned step 1 which file you need.
How to install Gapps?
munchy_cool said:
[...]
Click to expand...
Click to collapse
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
speedunderx said:
How to install Gapps?
Click to expand...
Click to collapse
i didnt get time to check that. may have to install some apks. maybe the same apks which are needed for amazon fire tablets to get play store working.
soulicro said:
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
Click to expand...
Click to collapse
gsi's are pretty stable, check xda thread for bugs. will update signature soon
munchy_cool said:
did you read the OP at all? it's mentioned step 1 which file you need.
Click to expand...
Click to collapse
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Thanks.
HTCDevil said:
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Let him answer by itself. Thanks.
Click to expand...
Click to collapse
no problem on Linux.
munchy_cool said:
no problem on Linux.
Click to expand...
Click to collapse
Great, hope gapps work and camera is mostly Stable. Thank you
HTCDevil said:
Great, hope gapps work and camera is mostly Stable. Thank you
Click to expand...
Click to collapse
it does not have gapps. you may have to manually install some apks. try with apks needed for Play Store on amazon fire tablets.
if you figure those out, please let us know.
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:
We have root!
All you have to do is follow these few steps and have a working adb / fastboot installation
1 Download this patched boot image -
https://www.androidfilehost.com/?fid=10763459528675569219
2. Reboot your phone to the bootloader
Code:
adb reboot bootloader
3. Boot from the patched image
Code:
fastboot boot magisk_patched.img
4. Make sure you have the latest Magisk Manager Canary and do a direct install to patch your internal boot image on both slots.
Latest Magisk Manager -> https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Done!
It seems like a lot of people are still having issues. If this doesn't work for you, then my boot image is slightly different than yours. You can follow the steps from this post to pull your stock boot image. After you do that you can just patch your stock image with Magisk Canary. Pull the patched image from your phone and use it in step 3 above.
Special thanks to SAKO4444GODZ for pulling the stock boot img first
Reserved
Reserved 2
northmendo said:
I started this to share information and files in order to get root on the KB2005 US Unlocked 8T. I have tried the boot images from the other variations with no luck. So, lets discuss and get this thing rooted.
Click to expand...
Click to collapse
Maybe we can flash an older firmware? I currently can't because the system update app doesn't have the local update option.
Over here just patiently waiting for an ota. dont even want to put my sim in it from my oneplus 6t until I get root
dreisus said:
Over here just patiently waiting for an ota. dont even want to put my sim in it from my oneplus 6t until I get root
Click to expand...
Click to collapse
I got a download from OnePlus Updater. They just updated to support the 8T. I haven't got my payload dumper working yet. Heres the download if anyone wants to try it.
https://www.androidfilehost.com/?fid=10763459528675568207
Possible Extraction method from phone
When I boot from the 2001 boot.img, it doesn't get to the system ui, but I do have ADB access and su is available. Normally it would say that su could not be found, but now it waits for authorization (which I can't give because system UI won't display and the screen is blank). If we can make magisk auto accept su from shell we can get the 2005 boot.img. Difficult but worth a shot.
northmendo said:
I got a download from OnePlus Updater. They just updated to support the 8T. I haven't got my payload dumper working yet. Heres the download if anyone wants to try it.
https://www.androidfilehost.com/?fid=10763459528675568207
Click to expand...
Click to collapse
Downloaded it and got the boot.img but it says Unsupported/Unkown img format when I try to patch the boot.img
This is my first time using the unloader but it extracted everything fine from what I can tell. It's just the boot img that fails in Magisk when trying to patch.
Anyone else seeing this?
MNoisy said:
Downloaded it and got the boot.img but it says Unsupported/Unkown img format when I try to patch the boot.img
This is my first time using the unloader but it extracted everything fine from what I can tell. It's just the boot img that fails in Magisk when trying to patch.
Anyone else seeing this?
Click to expand...
Click to collapse
That zip is only 350MB so it won't contain a proper boot.img. You need to extract it from a full sized OTA zip which is around 3GB. So far there's no link to KB2005 full OTA zip yet.
zellleonhart said:
That zip is only 350MB so it won't contain a proper boot.img. You need to extract it from a full sized OTA zip which is around 3GB. So far there's no link to KB2005 full OTA zip yet.
Click to expand...
Click to collapse
Thanks for confirming!
I have done a full msm tool readback of the device, patched boot img, flashed and there is am encryption issue. Booted or flashed after a long boot up, it starts up plays the boot animation, then as it completes, the screen goes black. Only way out of it if it was flashed and not booted is flash unpatched boot, format and then reboot. It cannot be rooted at this time. I am compiling a kernel with kernel assisted root built in to see if that will circumvent the issue for root at least while on stock.
My device is kebab 2005 model too
Just flashed patched recovery - success
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
---------- Post added at 11:54 PM ---------- Previous post was at 11:32 PM ----------
SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
Click to expand...
Click to collapse
Stock boot.img should be attached in a zip file
checksums for the .img (after extraction, not the zip)
MD5: d6615931724d901956c8d855af75c1c0
SHA1: 01e699edec71dea408420b1aaed6e5bbdf6a9eb3
SHA256: 2f58564817ff189177e135fcee92a5070100aaa26529bbfafbdcf34e149ee998
SHA512: 2a579411ca054488b6114d9efb5f36e2a52bc6114775f33913b33a8ff0a29af71dbf5e8bb8d632a359cb489ebb146764e515e73c8140007791f42bdfc4c3a07b
Uploaded the zip correctly, it didn't upload last time, sorry.
SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
---------- Post added at 11:54 PM ---------- Previous post was at 11:32 PM ----------
Stock boot.img should be attached in a zip file
checksums for the .img (after extraction, not the zip)
MD5: d6615931724d901956c8d855af75c1c0
SHA1: 01e699edec71dea408420b1aaed6e5bbdf6a9eb3
SHA256: 2f58564817ff189177e135fcee92a5070100aaa26529bbfafbdcf34e149ee998
SHA512: 2a579411ca054488b6114d9efb5f36e2a52bc6114775f33913b33a8ff0a29af71dbf5e8bb8d632a359cb489ebb146764e515e73c8140007791f42bdfc4c3a07b
Click to expand...
Click to collapse
Uploaded the zip correctly, it didn't upload last time, sorry.
SAKO4444GODZ said:
Uploaded the zip correctly, it didn't upload last time, sorry.
Click to expand...
Click to collapse
Could you upload it somewhere else? I'm getting a 404 when attempting to download it.
TheUnkn0wn said:
Could you upload it somewhere else? I'm getting a 404 when attempting to download it.
Click to expand...
Click to collapse
I also get a 404, weird, I can't submit links yet, so any suggestions?
SAKO4444GODZ said:
I decided to take the risk and flashed the patched recovery from the EU 2003 version, it worked and I have root adb shell. I'm about to extract the 'boot.img'.
Click to expand...
Click to collapse
Funny I tried this too
Didn't work
Here's a semi-broken TWRP that allows su access through adb: https://drive.google.com/file/d/1dRXJj7HZcqlNsHlVcNH0qR3sNx_uBA__
DO NOT FLASH, ONLY USE WITH BOOT COMMAND!
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
dd if=/dev/block/by-name/boot_b of=/sdcard/boot_b.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb pull /sdcard/boot_b.img boot_b.img
I borked my boot_a by flashing it with boot_b (boot_b was broken on my device), so I was unable to obtain a working boot_a.img. If someone could kindly share their KB2005 boot_a.img that would be nice.
Thanks to @ SAKO4444GODZ and his extracted boot.img!! I patched it and now have working root. I'll update the front page.
https://i.imgur.com/pynYfD4.jpg success
---------- Post added at 12:28 AM ---------- Previous post was at 12:25 AM ----------
Oh, I can post links now? Here is the patched boot.img for US_2005
https://drive.google.com/file/d/1V_wI8dl4SulMst4G-yMcPQsjFFs8j_Ns/view?usp=sharing
SHA 512: 1e54faef40c104a3e93545fef821e3c94abb90e8eea56f1ee402705e54607b3b038ef614d16c91865daee2df1ac02134202a7e4061f05af312ead39b7732c7e4
Awesome!