Related
Hi all
So it was all running nice and stable, before the evil b25 update that destroyed my axon 7 completely and made it useless, I'll tell how
so after updating I figured out I can't access fastboot to flash anything, and I figured out I wasn't the only one with this "meme" that zte made.
so I decided to roll back to b19 using Miflash and b19 edl package, I thought my problem would end here.
Then I flashed twrp via fastboot, and upgraded to b25 using b25 bootstack + b25 zip by drakenfx, all good.
then I tried to root b25 the good ol' way by flashing supersu zip, only to find that I'd end up with this newer meme, "unable to find su binary"
seems like the sort of thing you'd get if you had a locked bootloader, which is suspicious, judging that no one was able to get fastboot on b25
I also figured out I wans't the only one as people from "root b25" threads know that you can't root b25 even if you had twrp
so I rolled back again to b19 using miflash....you know the story
now here comes the interesting part, the meme, didn't go away, I tried to root my b19 a2017u by flashing supersu
I tried everything, flashing b19 bootstack, formatting data flashing different supersu versions etc.
, either ended up with a bootloop, or the famous "su binary is not installed"
I never had this before updating to b25 and now I can't get rid of it even without b25
can someone guide me to root stock b19 properly and get rid of this meme? (bonus if you know how to root b25 properly because I liked b25 more, there is a7x kernel for b25 so I guess we can root b25? maybe not? )
note that I don't want magisk, I just want the good ol' supersu, nothing more nothing less.
My opinion is the new b25 somehow messes the bootloader and now it's locked again, but this time you can't unlock it even if you downgrade and flash edl bootloader unlock via miflash.
guys, I think zte is just trolling us atm, you would not believe how much time I wasted flashing, I think my axon 7's nand is going to die soon.
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
Holding power and both volume keys at the same time for ~15 seconds (until the LED flashes) restarts EDL without actually having to get out y'kno.
Just saying
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
UPDATE ON THE SITUATION:
It didn't... *sigh*
but...it worths to mention 1 thing I noticed after booting (regardless of supersu version flashed)
That su permissions get granted, but for a limited periods/times only, and then I get the "root undetected/su binary not found" error afterwords.
which was suspicious, so I ran "su" command in terminal emulator with the supersu you provided and this is what I got
ailsa_ii:/ $ su
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e054ffff68 arg 0xaa1403e2d2800081
Basically a bunch of warnings like the one above, like a dozen of this line ending up with this specific note:
CANNOT LINK EXECUTABLE "sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Im losing hope, but at the same time I think I found a thread, only need a dev to help me currently
I'll post this in supersu thread and see, maybe I get a helpful reply
I will also try changing to ext4 because I'm heavily doubting that the reason for all this is my use of f2fs on data partition only.
Ghostface009 said:
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
buksua said:
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
Click to expand...
Click to collapse
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
Ghostface009 said:
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Click to expand...
Click to collapse
no fastboot on b25 but fastboot on b19
remember to flash B19-NOUGAT_FULL (Nougat 7.1.1) first than VERY IMPORTANT part is to flash B19-NOUGAT_TWRP (Nougat 7.1.1) right after.
just do step 1 and 2.
don't flash b25 yet if you want fastboot
if you want b25 and b25 root just follow step 3
buksua said:
no fastboot on b25
Click to expand...
Click to collapse
Yeah, not a big surprise
and I'll try everything later when I get enough time, but for now I look for a firmware flash-free method because I don't want to kill the ufs.
UPDATE FOR EVERYONE:
I FINALLY GOT SUPERSU WORKING (atleast this far)
sadly f2fs was the reason behind this error
Special thanks for @J0nhy
for providing the correct supersu version to flash :3
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
The file is no longer available through this link... is there another source?
zachstarmer said:
The file is no longer available through this link... is there another source?
Click to expand...
Click to collapse
wew, It's been a long time since my last login here.
afaik it was 2.79 su.
But why you're still on b25 when you can flash newer firmware? when I flashed b32 via edl, I got rid of all these probs (except f2fs, because zte decided that their stock firmware only supports ext4 )
I got fastboot and everything, root xposed etc, if you want the edl package you can search it in drakenfx's androidfilehost account :good:
make sure to backup internal storage manually and backup apps with TB for restoring after edl-flashing b32. I also suggest updating to b35 before rooting and restore since b32 was helluva buggy update
This is exactly why I won't run ZTE's stock ROM, it seems that only Magisk works on B32 and beyond. I have grown to hate Magisk over the years, due to a number of bad experiences with it on various ROMs/devices. On stock, Magisk makes my exFAT SD appear as corrupt, I refuse to format to vfat, fat32. I tried Phh's Superuser and SuperSU, either the device won't boot or I get errors about su not being available. So it's custom AOSP-based ROMs only for me. Which are far superior to stock in most ways.
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
The toolkit guide is probably the easiest one.
Read the whole thread and try again.
Sent from my ZTE A2017U using Tapatalk
runninghamster said:
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
Click to expand...
Click to collapse
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
I will try this today, thank you for your time in typing this
runninghamster said:
I will try this today, thank you for your time in typing this
Click to expand...
Click to collapse
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
raystef66 said:
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
Click to expand...
Click to collapse
Thank you so much, will try today!
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
Followed your steps and managed to unlock the bootloader successfully. Afterwards I tried to flash TWRP using the Axon Toolkit and this error appears. Have 0 clue why. A little help please.
View attached >>>
EDIT: nevermind, tried to boot into recovery and twrp booted, not sure why the error appeared though. thanks for the help!
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
KingBeefy said:
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
Click to expand...
Click to collapse
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
I promise the way above works
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
envizion58 said:
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
Click to expand...
Click to collapse
Like LOS and whatever, yeah, but it takes like 2 minutes. Stock won't flash, since magisk is there anyways
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
Hopefully I'm reading this correctly, but if you are referring to swiping as opposed to sideloading I've noticed that too. i do still sideload the ROMs but I swipe all mods and kernels. commonly I would get an error regarding /system not remounting after some flashes but that stopped a while back. @topjohnwu commented in a magisk thread to mount system before flashing as a fix. Its worked great.
Thanks for the response and if i read your question wrong fire it back at me for a second attempt lol
KingBeefy said:
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Click to expand...
Click to collapse
with our TWRP being janky as it is, trust me, you dont want living in the other slot.
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.
New video guide below
VIDEO GUIDE
1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.
*IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*
*IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRIGHTING IN THE NEXT FEW STEPS*
Note: This requires root
Type this into terminal or ADB shell with root privileges.
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Backup the partition to another device. Preferably a PC as you may need one in the later steps.
2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)
Use the MSMTool to restore your device to 10.5.4.Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.
Guide and Source for MSMTool
MSMTool 10.5.4 Download
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
[GUIDE] Unlock Factory Mode *root*
4. Now we need to perform a FP calibration. We want to fail.
Enter Factory Mode as shown in the previous guide. (*#801# in the stock dialer)
Swipe over to "Device Debugging"
Select "Finger print test"
Select "Finger print calibration test(Pure White - 90% Blue)
Select "Start Test"
Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.
The way I did this is by opening it extracting it via 7-ZIP on my PC
Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.
Open 'DATA' folder and delete 'gf_persist.so'
Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
It should ask you if you want to keep the old or new files. Select to keep the new.
Reboot.
7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.
Why does this work?
Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.
I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Thanks worked on.my TMobile OnePlus.
I can confirm working on OOS 1.5.6 too. I downgraded from 10.5.9 with downgrade rom, which restores OOS to 10.5.6, and followed your guide and it worked as a charm. The only problem is that i cannot lock back the bootloader, cause it breaks FP again. Did you maybe try to lock it to try? Nice work man.
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
TheKnux said:
T-Mobile OnePlus 8 here. Stock firmware, orginally had my bootloader unlocked, rooted with TWRP and Magisk, backed up modem, converted to international firmware (10.5.7), lost signal, had to restore modem, ota'd to 10.5.9, unlocked bootloader again, rooted, etc. All while having a working FP the whole time. Ended up flashing EdXposed via Magisk, broke SafetyNet, etc, did a factory reset on TWRP (3.4.0-1 test), wiped data, rebooted recovery, rebooted system, booted back to TWRP. Installed Magisk to see if it'll boot with root, same thing. MSM'd back to T-Mobile firmware, then converted to international again. After the conversion was done and I unlocked bootloader and rebooted to system, my FP was broken. Ended up MSM'ing back to T-Mobile stock to see if it would work again, nothing.
TL;DR does this method only work if I had a working FP to begin with like it did stock out of the box?
Click to expand...
Click to collapse
Just follow the guide, you'll have it working. You just have to backup your current persist
dzontra83 said:
Just follow the guide, you'll have it working. You just have to backup your current persist
Click to expand...
Click to collapse
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
TheKnux said:
So back it up even though it's broken? I'm on T-Mobile stock again, locked BL. Should I unlock, root, then pull persist and back it up?
Click to expand...
Click to collapse
Exactly, a T-Mobile user confirmed guide to work, check 2nd post
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
TheKnux said:
While on 10.5.7, unlocked bootloader, I flash TWRP, then reboot, and it boots back to TWRP. When I flash Magisk 20.4 zip in TWRP, it goes to boot, then enters CrashDump Mode. When I try and use the flash-all to downgrade to 10.5.4, I get a bunch of fastboot "cannot flash critical partitions" errors, it fails, and goes back to CrashDump Mode. What am I doing wrong? Also, is it really necessary to downgrade to an earlier version of OOS to use Engineering Mode or can I use 10.5.7?
Click to expand...
Click to collapse
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
dzontra83 said:
When you unlock bootloader, only boot into TWRP, then install magisk, i thin it Is still recommend to only boot into TWRP, not to flash it.
Click to expand...
Click to collapse
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
TheKnux said:
Thank you so much, that worked! New problem, what do I do since I can't downgrade to an earlier OOS (10.5.4)?
Performing the test on T-Mobile 10.5.7, when performing the test, nothing is failing after pressing start test. Its all passing, what should I do?
When trying to downgrade using the 10.5.4 MSM Tool. it gives an error of "Unsupported Target TMO" and "param preload" and fails.
Click to expand...
Click to collapse
Did you follow the instructions in test exactly? In second test you must't press the sensor.
Can help you with TMobile model, I have international one.
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
TheKnux said:
I figured it out. I was just being a dumbass I guess. Has anyone noticed the fingerprint sensor not being able to read that well compared to before it was broken? It seems like it fails a lot more before it succeeds. Unless now that it's working, we can perform the calibration again and it'll work better?
Click to expand...
Click to collapse
Don't know about that, mine works just fine
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
TheKnux said:
So I think I messed up, I ended up performing the calibration again, while it was already working, and now it says "fingerprint hardware not present" any suggestions on how to fix? I performed the instructions in the guide (again) and nothing worked. When the error pops up, if I press back, the error message goes away and the FP icon is there. When I tap on it, it lights up white but doesn't vibrate or register anything. I already used the MSM tool to go back to Tmobile stock, then used the fastboot ROM to go to Global 10.5.7, followed the guide again, still nothing.
Click to expand...
Click to collapse
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
dzontra83 said:
The initial backup of the persist.img should do the trick, if you repeat the process once again, it should work
Click to expand...
Click to collapse
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
TheKnux said:
I tried that, multiple times. Still not working. Is it possible for someone to upload their persist.img so I can try it or is it device specific? Granted, I pulled my initial persist.img from stock rooted Tmobile ROM AFTER I broke it even though it worked before (long story). I wasn't able to downgrade to 10.5.4 because when I tried using the MSM tool, it gave me a TMO device error and I couldn't use a fastboot ROM to go to 10.5.4 cause it kept entering CrashDump mode every time it tried rebooting to fastboot to finish the flash process .
Click to expand...
Click to collapse
Your cannot use someone else's persist, you must't use yours.
dzontra83 said:
Your cannot use someone else's persist, you must't use yours.
Click to expand...
Click to collapse
What about someone else's DATA and ENGINEERINGMODE folders? I've tried everything. Even recalibrating multiple times. It's not giving me a bunch of errors like it did before, just one error. The last error is FAIL! OPERATION_STEP_GET_KB_CALIBRATION TEST FAIL:GF_ERROR_GENERIC
Just wondering, what is the point of downgrading to an earlier OOS? If I was able to do it on the Tmobile firmware with success, is there an importance in downgrading?
Thank you so very very much!!! I have a T-Mobile 7T Pro 5G McLaren which hasn't had a working fp in almost 2 months. I hadn't made a backup of persist before the fp broke, so I thought I was completely screwed. Luckily, I did make a backup of persist before trying to use the fp calibration tool myself without any luck shortly after it broke (basically just clicking stuff and guessing lol). Found this thread and I had my FP scanner working again perfectly in less than 15 minutes!!!! Thank you soooo much for all the hours and effort you put into figuring this out!!!!!!!
Didn't have to run the msm tool to revert to older version of OOS and lose all my data either!!
Just one question and it's just for my curiosity. Why do we delete "gf_persist.so" from our original persist.img before copying/pasting into /persist partition after "calibration"? Is gf_persist.so not a file containing part of the original calibration? Is that the file which is being fixed by running the hidden calibration commands?
If anyone can help me, it would be much appreciated. https://forum.xda-developers.com/oneplus-8/help/broken-persist-img-problems-t4129587