Related
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
CiT42 said:
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
Click to expand...
Click to collapse
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Choose an username... said:
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Click to expand...
Click to collapse
I flashed DrakenFX's B29 stock rom. Didn't thought it would work with recovery but anyway ! Thank you.
Do you recommend some ROMs, kernels, etc ?
CiT42 said:
Do you recommend some ROMs, kernels, etc ?
Click to expand...
Click to collapse
Nah, they are all mostly bad. The best of the bunch seems to be NucleaRom, it has an okay kernel (Radioactive, not too good battery-wise but I've never seen so little UI lag, like, ever) and okay features (like 1/3 of what ResurrectionRemix has), an awesome maintainer (OrdenKrieger) and boots in like 15 seconds
But the stock ROM is currently the best of them all, not battery wise (you can get some obscenely high SOT numbers on LineageOS with Substratum black themes) but it's fluid and stuff runs well on it. The status bar is hideous though, and MiFavor is white themed, on an AMOLED screen, what the crap ZTE?
Don't try PureNexus, permanent hard brick from the looks of it.
LineageOS works okay but it has some compatibility problems with some apps I use, dunno
I think you could try the dual-boot patcher, that way you can test the roms and keep a working stock rom to use it as your daily driver without losing data. i never used the dual boot patcher though, so good luck if you will use it
I've bad experiences with Dual boot on my old 1+.
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Next Steps...
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
NoBodyUKnow said:
OK, finally getting back to this...
Click to expand...
Click to collapse
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
Click to expand...
Click to collapse
It did clear some things up, thank you. However, I still end up at the Qualcomm CrashDump Screen of Death. this happens at the very end of the process, after the second load of LOS 17 and TWRP Installer, while rebooting to recovery from the TWRP .img. I'm going to list every step I take and all of the files I use. There are a couple of places where I'm not sure I'm doing the right thing, and/or the outcome of that step is not as expected.
1. Download all of files:
TWRP Q .img
TWRP Installer
OP OS 10.3.1 Fastboot ROM
lineage-17.1-20200223_133843-UNOFFICIAL-fajita.zip
First step is to flash Oxygen 10 and TWRP Recovery to both slots. I unpack the OOS Fastboot ROM zip on my laptop, boot to my 6t's bootloader and connect that to my laptop. After making sure ADB/Fastboot sees the device, I run "flash-all.bat" by clicking on it. This seems to load OOS just fine. The phone boots to OOS and I turn the phone off.
(I've done all of this several times and there are variants: I've tried becoming a developer and turning on the advanced boot options in OOS 10, but I don't think that matters, as long as I can get back to the bootloader or recovery. Let me know if that is incorrect).
At this point, your instructions say
"reboot to recovery, flash the OTA zip again."
I've tried moving the OOS fastboot zip file to my phone and flashing from TWRP, but that doesn't work. I get an error complaining of wrong format. It seems to me, a Fastboot ROM can only be flashed from adb/flashboot. Is that correct?
Therefore, I have been going back to the bootloader and re-flashing OOS 10 from adb fastboot again. After this step, contrary to your guidance above, the phone does indeed boot directly to OOS.... A loooong, what seems to be initial boot. I then turn off the phone.
I reboot to recovery again - and it is now the stock recovery - so I follow your guidance to factory reset from there. It does boot into OOS, and it is another looonnng boot. I then turn off the phone, return to the bootloader, flash the TWRP .img, install the TWRP installer and move on to the LOS 17 process linked to above.
Though I'm not sure it's necessary, I follow these steps from the beginning of he process:
Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
Everything seems to work well, so I follow these steps, all from TWRP:
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
I do all of the steps below, with no problems:
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
Just a note at this point, to highlight that this is done from TWRP, as opposed to using adb fastboot as with OOS10. This is what I've done with ROM's in the past; the fastboot ROM thing is new to me.
Next, I
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery
This is where things go bad. In this reboot to recovery, the TWRP splash screen sits there for a long time, and then the Qualcomm CrashDump Screen of Death (QCDSoD) appears. If I hold the power button down for long time, the QCDSoD disappears and the phone reboots and starts to load LOS. Then, it switches to TWRP splash screen, and as before, end with the QCCDSoD.
I've been through this entire process maybe three times. Always the same outcome (you know what they say, about doing the same things and expecting different results...)
I did note, that on the OS Fastboot ROM page, there was some discussion of "Branded" phones, specifically T-Mobile phones. When I first got this phone, after loading TWRP, I swapped active slots. On the new, active slot, I booted the phone, and it was to a T-Mobile ROM. Not sure if that plays any part in all of this.
Appreciate your hanging with me. I'm going to rest my fingers
Is this a TMobile 6T?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Is this a TMobile 6T?
Click to expand...
Click to collapse
After a little research, it appears that it is a T-Mobile variant: the A6013. And, well.... I guess this may be a clue...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
NoBodyUKnow said:
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
Click to expand...
Click to collapse
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
NoBodyUKnow said:
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
Click to expand...
Click to collapse
You could always use a T-Mobile MSM Tool ?
Link
MSM Tools are usually my last resort as they relock the bootloader, but in this case, it's what you are after.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
NoBodyUKnow said:
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Click to expand...
Click to collapse
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
NoBodyUKnow said:
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
Click to expand...
Click to collapse
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Yes, but...
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
Yes, my goal is to have Lineage OS 17 (Android 10/Q) on a OnePlus 6T. Hopefully on the phone I have now, but on whatever 6T variant I need to get. I like the phone.
I tried before with a T-Mobile version of the A6013, and I could not get there. @OhioYJ offered some assistance and suggested the problem was the phone being a T-Mobile variant; that I needed a "Global" version. Therefore, I returned that phone and purchased an "International" A6010_41_200115. Is this the Global variant?
I've followed the processes detailed above on both phones and wound up at exactly the same place: The QUALCOMM CrashDump Mode screen. This happens after the second install of TWRP, when I reboot to Recovery.
In both cases, the phones came with OOS 9, and I'm updating to OOS10 via the Fastboot ROM before proceeding to LOS 17.
Is it possible to get to LOS 17 on the phone I have now?
Thanks!!!
OhioYJ said:
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Click to expand...
Click to collapse
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Mine is an A6013, I checked the phone and original box. I bought mine straight from OnePlus. TMobile ones will only have a single IMEI. The "Real" 6T will be dual sim and have two separate, unique IMEI numbers.
NoBodyUKnow said:
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Click to expand...
Click to collapse
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
DarthVader said:
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
Click to expand...
Click to collapse
@OhioYJ
I did as you suggested. As with my first phone (a T-Mobile variant), when I perform the reboot to recovery after flashing LOS 17 and TWRP, the TWRP intro screen appears for a long time ( 30 seconds + ). When it finally disappears, the Qual. Crash Dump Screen appears. By holding the power button for about 10 seconds, the phone reboots to LOS. After booting, I can navigate within LOS, but a warning flashes for a few milliseconds, about every ten seconds. I was able to capture a screenshot of the warning from the video I just linked to:
This continues to occur: if I try to reboot to recovery, the TWRP screen appears, lingers and then changes to the Qual Crash Dump screen. At this point, when I hold the power button for about 10 seconds, the phone boots to LOS. When LOS is running, the warning continues to appear at regular intervals.
Thinking I may just go for another phone, preferably one that supports GSM and CDMA, but at least a US, non-T-mobile phone with all of the GSM Bands. They are a little pricey though.
Happy to try other things with this phone though, if it might help further understanding of these phones.
Looking for w Breakthrough...
@OhioYJ @DarthVader
Gentleman,
I hope this update finds you and your loved ones safe, in this scary time.
I am still trying to get LOS 17 on my OP 6T, and I Keep ending up at the same place.: Qualcomm CrashDump Screen. l'm using the fastboot ROM's, and using those does not completely align with this part of OhioYJ's instructions:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
OhioYJ mentions "flashing the OTA Full .zip". The Fastboot ROM's have "OTA" in their labels and they are .zip files, but they will not flash in TWRP. They error out. They do run - and flash - from the bootloader, and this is what I've been doing. I'm guessing there are other, TWRP flasheable .zip files for the 6T. Maybe I should try those? Can't seem to find them. If so, can you point them out to me, please?
I humbly ask that you review this thread, looking closely at your guidance and my responses. I keep ending up at the same place - the Qualcom CrashDump Mode Screen.
Thanks!
NBUK
Hey everabody,
I tried to install TWRP on my OP6T, using the guide from lineage OS (https://wiki.lineageos.org/devices/fajita/install) but after the fifth Step in "Temporarily booting a custom recovery using fastboot", my device stuck into fastboot logo and after restarting the phone, i wasn´t able to reboot the OOS system or to get into TWRP, I could see only the warning, that the bootloader is unlocked or the fastboot mode. I tried several other guides to install TWRP on my phone, but the all lead to the same problem. I also tried to relock the bootloader to get rid of the warning screen, but that also didn´t work.
Than, I tried to flash stock ROM with the Tool All in one (https://forum.xda-developers.com/oneplus-6t/how-to/tool-tool-one-driversunlocktwrpfactory-t3860279) but I got an Error (something about personal data) now I am able to start the Phone, but it remains in the starting animation of OOS.
Now I just want my phone to work again, with OOS or Lineage OS. Please help me. Best reagards.
Update : phone restarts after flashing stock again, but play store does not download anything. I still want to get Lineage OS, twrp...
Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.
Thank you very much
OhioYJ said:
Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.
Click to expand...
Click to collapse
Dear OhioYJ, thank you very much.
Before starting the flashing process, I want to ask a few questions.
1. While running the adb& fastboot setup, the interface (the blue one) said that 0 files were copied. In a YT video I saw the same programm, but 4 files were copied in the video. Will adb and fastboot be disturbed by that?
2. after rebooting the phone (and editing my first post), I made a factory reset in the setting of OOS. Does this change anything?
3. in Funk Wizard´s source for downloading the TWRP image (official TWRP site) i can find only a few versions of the img and the Zip, but there are no specifications if they are made for Pie or Q, as OhioYJ mentioned in his answer. Is there any ploblem?
4. for installing Magisk, I visited the Thread and downloaded the latest stable version. Is that correct (no specific version for the device or something, I just want to make sure not to mix the whole thing up again)
thank you for your help
MedusaGnom said:
1. While running the adb& fastboot setup, the interface (the blue one) said that 0 files were copied. In a YT video I saw the same programm, but 4 files were copied in the video.
Click to expand...
Click to collapse
As long as the files are copied, I guess it doesn't matter. You can see the image below I did as an example just now for this post, but I'm used to a count as well. I use Linux though. As long as the files move, don't worry about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MedusaGnom said:
2. after rebooting the phone (and editing my first post), I made a factory reset in the setting of OOS. Does this change anything?
Click to expand...
Click to collapse
No. In fact when going between AOSP, like LOS, and OOS you'll have to use OOSs recovery to to do a factory reset to get the phone to boot.
MedusaGnom said:
3. in Funk Wizard´s source for downloading the TWRP image (official TWRP site) i can find only a few versions of the img and the Zip, but there are no specifications if they are made for Pie or Q, as OhioYJ mentioned in his answer. Is there any ploblem?
Click to expand...
Click to collapse
Glad you asked. Don't use the official version. It's out of date and will cause problems. This is the official maintainers thread. Download the main versions there. The install guide talks about installing to recover ramdisk, which you can do, but it's still perfectly fine to boot the image, and run the installer like normal. Using the installer is what I always do as it's easier.
MedusaGnom said:
4. for installing Magisk, I visited the Thread and downloaded the latest stable version. Is that correct (no specific version for the device or something, I just want to make sure not to mix the whole thing up again)
Click to expand...
Click to collapse
You are correct. 20.3 is the latest stable version. That's all you need. 20.3 will also install Magisk Manager 7.5.1 the latest version of the Manager as well so you don't even need to download that. I will recommend two additional things:
MagiskHide Props Config
UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip (In the first post, required for the MagiskHide Props to work)
MagiskHide Props Config will make it so you pass safetynet and still come up certified in the play store. You will need a terminal emulator to activate the props module. You can use anyone you prefer, I personally use this one.
I need an advice
OhioYJ said:
As long as the files are copied, I guess it doesn't matter. You can see the image below I did as an example just now for this post, but I'm used to a count as well. I use Linux though. As long as the files move, don't worry about it.
No. In fact when going between AOSP, like LOS, and OOS you'll have to use OOSs recovery to to do a factory reset to get the phone to boot.
Glad you asked. Don't use the official version. It's out of date and will cause problems. This is the official maintainers thread. Download the main versions there. The install guide talks about installing to recover ramdisk, which you can do, but it's still perfectly fine to boot the image, and run the installer like normal. Using the installer is what I always do as it's easier.
You are correct. 20.3 is the latest stable version. That's all you need. 20.3 will also install Magisk Manager 7.5.1 the latest version of the Manager as well so you don't even need to download that. I will recommend two additional things:
MagiskHide Props Config
UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip (In the first post, required for the MagiskHide Props to work)
MagiskHide Props Config will make it so you pass safetynet and still come up certified in the play store. You will need a terminal emulator to activate the props module. You can use anyone you prefer, I personally use this one.
Click to expand...
Click to collapse
Dear OhioYJ,
thank you for your help.
Right now i´m looking for the files you recommended in your fourth answer, but i can´t find MagiskHide Props Config. (could you give me a download link?)
Since my device decided to work again and even the Playstore started downloading, I am not sure if I want to risk new problems , than´s why I need an advice: is Lineage OS worth the risk? What could go wrong and is there a possibility to brick the phone irretrievable?
Is there a way just to get twrp and Lineage without rooting the device permanently, installing magisk etc? I need to use some banking apps, so i would have to unroot the phone after installing Lineage.
Is it dangerous to lock the bootloader again?
I´m sorry for my questions, but i do not have much experiece with this stuff, I only installed Lineage OS on the oneplus 1 and 2, what was very easy. Thank you very much.
MedusaGnom said:
Right now i´m looking for the files you recommended in your fourth answer, but i can´t find MagiskHide Props Config. (could you give me a download link?)
Click to expand...
Click to collapse
It's at the bottom of his first post. It's attached to the post.
MedusaGnom said:
wrong and is there a possibility to brick the phone irretrievable?
Click to expand...
Click to collapse
Highly unlikely, but anything is possible I guess. With OnePlus devices you have the MSMTool, which while I've frequently on here said should be a last resort, works very well. This will work without recovery or fastboot. While you have a working phone though, make sure you use FunkWizard's guide to backup your modem. <-- This is key if you are going to play with your phone, and install ROMs and such. Odds are you are never going to need them, but its the one unique thing to your device and it will save you if you ever happen to actually mess that up. Back these up some where safe (not on the phone).
MedusaGnom said:
than´s why I need an advice: is Lineage OS worth the risk?
Click to expand...
Click to collapse
Everyone must form their own opinion, tolerance level. The OS is very stable. Personally I don't own or buy a device that doesn't have LOS support (Before LOS it was CM). I don't even give a device to my son that doesn't have LOS on it. It gives me much more control over my privacy, data, and information. Even my battery life has been great, typically averaging 7-8 hours of SOT over 48 hours.
MedusaGnom said:
Is there a way just to get twrp and Lineage without rooting the device permanently, installing magisk etc? I need to use some banking apps, so i would have to unroot the phone after installing Lineage.
Click to expand...
Click to collapse
You don't have to root to have Lineage. Depends on the banking app, but some won't work without hiding the fact your bootloader is unlocked anyways. So you may not be able to run your app just running Lineage unrooted anyways. Only one way to find out I guess. I generally have as few apps as possible. I do know the few times I've used my banking app, it's worked with Magisk and that Module I've linked to above.
MedusaGnom said:
Is it dangerous to lock the bootloader again?
Click to expand...
Click to collapse
If you phone isn't completely stock, yes. If you are absolutely sure everything is stock, then it's not a problem. MSM Tool will put everything back as it was out of the box and relock the bootloader for you. Relocking / Unlocking the bootloader wipes the phone. Back everything up.
MedusaGnom said:
I only installed Lineage OS on the oneplus 1 and 2, what was very easy.
Click to expand...
Click to collapse
It's not that bad once you get it down, and get it converted over. It's just not like the "old days" where many devices were similar wipe caches, it was ok to wipe system, flash ROM, etc. I have a new tablet and you can't flash the those modules above in TWRP otherwise it refuses to boot again. Every device has something different. Once you're running LOS, updating is pretty straight forward:
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean instal)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
my plan
OhioYJ said:
It's at the bottom of his first post. It's attached to the post.
Highly unlikely, but anything is possible I guess. With OnePlus devices you have the MSMTool, which while I've frequently on here said should be a last resort, works very well. This will work without recovery or fastboot. While you have a working phone though, make sure you use FunkWizard's guide to backup your modem. <-- This is key if you are going to play with your phone, and install ROMs and such. Odds are you are never going to need them, but its the one unique thing to your device and it will save you if you ever happen to actually mess that up. Back these up some where safe (not on the phone).
Everyone must form their own opinion, tolerance level. The OS is very stable. Personally I don't own or buy a device that doesn't have LOS support (Before LOS it was CM). I don't even give a device to my son that doesn't have LOS on it. It gives me much more control over my privacy, data, and information. Even my battery life has been great, typically averaging 7-8 hours of SOT over 48 hours.
You don't have to root to have Lineage. Depends on the banking app, but some won't work without hiding the fact your bootloader is unlocked anyways. So you may not be able to run your app just running Lineage unrooted anyways. Only one way to find out I guess. I generally have as few apps as possible. I do know the few times I've used my banking app, it's worked with Magisk and that Module I've linked to above.
If you phone isn't completely stock, yes. If you are absolutely sure everything is stock, then it's not a problem. MSM Tool will put everything back as it was out of the box and relock the bootloader for you. Relocking / Unlocking the bootloader wipes the phone. Back everything up.
It's not that bad once you get it down, and get it converted over. It's just not like the "old days" where many devices were similar wipe caches, it was ok to wipe system, flash ROM, etc. I have a new tablet and you can't flash the those modules above in TWRP otherwise it refuses to boot again. Every device has something different. Once you're running LOS, updating is pretty straight forward:
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean instal)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
Click to expand...
Click to collapse
Thank you very much!
I will write down what i´m going to do, would be great if you would give it a savety check.
Status:
- I unlocked the bootloader and enabled usb debugging and advanced reboot
-I installed the OP drivers and adb and fastboot on my pc
- I downloaded the the fajita twrp image and the twrp installer by mauronfrio, Magisk-v20.3 , UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip and MagiskHidePropsConf-v5.2.4 on my pc
- I downloaded the official Lineage Os 17 for fajita on my pc
next steps (assuming)
- download gapps
- set swipe to unlock the phone
- store the twrp image, installer, Magisk, magisk hide , UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip, gapps and the lineage zip on my internal storage
- boot into fastboot mode
- fastboot flash twrp image
- fastboot boot into recovery
- flash (now in twrp) twrp installer
- reboot recovery
- create nandroid backup
- flash magisk and the other 2 files relating to magisk
- gain root access
- reboot recovery
- wipe system partition
- flash lineage os 17
- flash twrp installer
- flash gapps
- create a backup
- reboot system
further targets: undo root
optional: clean install gapps
Thank you very much
OhioYJ said:
Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.
Click to expand...
Click to collapse
Thank you so much for covering this topic properly. I'm just now rejoining the Android world after having to use iPhone for over a year. Still had my 6t floating around, almost brand new and trying to quickly Google my way to getting TWRP and Lineage installed. The install instructions on the Lineage site are incredibly wrong. After going to that link and tweaking a bit it installed perfectly.
So my current phone recently broke. So I decided to dust of my old Axon 7 which was still using Android 6.0.1. A bit old for these days since a lot of apps won't work. The best thing I could think of was to install a different rom. After a lot of work I finally managed to unlock the bootloader and install TWRP. Then I tried to flash a rom but to no avail. I have tried many things and now I can access only TWRP and EDL through ADB. I cannot access the Bootloader menu anymore. Does anyone know what to do next? How can I fix this and try to flash something again?
Edit: Forgot to mention that I currently have the most recent version of TWRP installed. And the flashing error I get is Error 7, Googled that and tried every "fix" but none of them worked. Another strange thing is that my phone used to be A2017G, but now when I connect it to my pc it shows up as A2017U, Is this a driver issue or did I change something unintended?
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
klałn said:
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
Click to expand...
Click to collapse
Thanks for the reply! I was a bit ahead of you and managed to create a vendor partition using the Party v0.5 script, now I can flash ROMs just fine but the system won't boot (blinking red light, black screen)
I am using the most recent TWRP version for Axon 7 (3.5.2_9-0), I am not sure if this is part of the problem
I've found some possible fixes related to my original question for getting into the bootloader menu, but I have no idea on what to change to regain access to it. I do remember that it said the device name was ailsa_ii as you mentioned, and that the bootloader version was not specified (it was just blank)
Edit: never mind the bootloader menu issue, I managed to get back into it. But the system still won't load.
On which bootstack you are right now?
Which rom you want to try?
Custom roms won't work on stock bootstacks.
First, I would recommend to backup persist/efs partition, before futher changes.
Second, I would recommend upgrade stock marshmallow to nougat, then nougat to oreo and after that, flash universal v2 oreo bootstack.
Bootloader/fastboot was locked by zte on most stock roms.
For what for you need fastboot mode? EDL mode isn't enough?
If you really need fastboot, you may try this aboot on oreo bootstack. Didn't try it with universal v2.
I have no idea what bootstack I am on right now to be honest. How can I check this?
I want to install LineageOS 17.1.
The bootloader is unlocked, I am sure of that.
Sorry for my ignorance, I know I am in way over my head but I am dedicated to make this work.
So you probably on stock marshmallow bootstack.
I still recommend to upgrade system step by step. From 6.0.1 to 7.0, then to 8.0 B02 and applying A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip.
Why this way? Most of a7 users did that at beginning and official updates may do some changes to persist partition.
Some people complained about 50% battery bug, which came out of nowhere.
If you want take a risk, you can flash DrakenFX bootstack straight away or flash A2017G_B02_OREO_FULL_EDL in edl mode and then DrakenFX bootstack. At least - please - do efs partition backup using EDL Tool by djkuz, before doing such a jump.
I don't know if this gonna work. If you brick your device, you will have to download full edl packages, which may take even more time, than official way to upgrade.
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
DNYO31 said:
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
Click to expand...
Click to collapse
Have you tried booting phone to edl mode by holding vol-up + vol-down and pressing power button?
ZTE logo might not appear, but you should enter to dfu/edl mode by pressing those buttons.
It's really hard to make a brick of Axon 7.
In 2016-2017, I had to ground test points on the motherboard to leave DFU mode, but it's not necessary anymore.
Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?
jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA
I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance
Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all
I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?