Related
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy
Hi my OnePlus 8 was running OS 11 beta 2. After installing lucky patcher the device went into bootloops.
I used MSMtool to recover. And after recovery and setup i observed the fingerprint doesn't work.
Updated to stable 11 from OTA. Still the same.
Please help
firoz3321 said:
Hi my OnePlus 8 was running OS 11 beta 2. After installing lucky patcher the device went into bootloops.
I used MSMtool to recover. And after recovery and setup i observed the fingerprint doesn't work.
Updated to stable 11 from OTA. Still the same.
Please help
Click to expand...
Click to collapse
Hi,
Just wanted you to know that LP is known for not being reliable, for having many false apk that most of the time are torjans, and even if you used it for UI customizations, there are better ways to do it (like substratum).
I don't have the answer you're searching for, but please, someone ask about that app, let him know that before the thread is closed (because LP is considered as a warez thus is forbidden to talk about here).
Hope you'll find an answer
Please help
firoz3321 said:
Please help
Click to expand...
Click to collapse
If you didn't backup your persist partition before you lost your fingerprint functionality then you need to try and follow the guide here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455/
If you backed up your persist partition before using MSM, then you only need to restore your working persist partition.
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Abdullah.Csit said:
Everyone can answer you. Not means that he answer you because he knows the answer since he born !
He had search, read & get knowledge.
It always recommended to read about Gsi carefully before install it on your device if you fear bricking then find out on your responsibility.
Hope you got me.
Regards
Click to expand...
Click to collapse
Thanks. I just want to know if anyone has successfully installed the official method.
LazCoder said:
Thanks. I just want to know if anyone has successfully installed the official method.
Click to expand...
Click to collapse
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Abdullah.Csit said:
Every one followed the official method has get successfully installation. most devices has same instructions. sometimes you get stuck on Boot loop or system not booting just change the version of GSI build.
Good luck
Click to expand...
Click to collapse
Thanks, then I'll have to take the risk. If the GSI does not boot I will install the stock ROM. I haven't reset it to factory reset since I bought it. Or I will buy a Pixel device to avoid dealing with all this, but Google Pixel devices are not sold in Turkey.
LazCoder said:
Hello, I want to install official android 12 GSI ROM on my device (Mi A2). I have stock ROM installed on my device and I want to install it by following the official installation instructions. I doubt my device will work with official installation instructions, but my device is fully treble supported. Will my device work in this case? The only answer to this question will be to do this, but I'm afraid of bricking my device.
Click to expand...
Click to collapse
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
mottaM said:
I tried to install on my redmi 6a. Treble compatible. However failed. Even android 10 gsi not working! Bootloops only. I have bricked my phone 100 times because now i have found an easy way to unbrick it without taking off back cover!!!
Click to expand...
Click to collapse
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
areallydumbperson said:
I have a Nokia 2.2 same chipset (mt6761) and android 12 gsi works
Click to expand...
Click to collapse
It doesn't matter which chip it is. It matters what version the phone was released with and whether it supports future GSI releases.
LazCoder said:
Just because your device is treble compatible doesn't mean it supports new Android versions. Did you check if it supports new versions?
Click to expand...
Click to collapse
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
Sad for you.
mottaM said:
There's probably this reason behind it: The kernel, Vendor etc of the stock rom is 32 bit only. Unfortunately there is no 32 bit gsi image. I tried finding some 64 bit OS for my device but there is none
Click to expand...
Click to collapse
After researching I was wrong but 32 bit vendor just so interesting
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
jwoegerbauer said:
@LazCoder
Your phone's SoC is 64-bit.
You will need to recompile your entire ROM as 64 bit, then flash the GSI
GSIs will need the vendor and kernel and well everything else to be 64 bit
Click to expand...
Click to collapse
Can I simply flash android 11 then flash android 12 gsi?
aqiluii said:
Can I simply flash android 11 then flash android 12 gsi?
Click to expand...
Click to collapse
Official sources say it's possible. But you should check compatibility first.
How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.
hloooooo :;/
I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.
Zanci19 said:
I heard about this TreeUI. It works perfectly for me.
https://forum.xda-developers.com/t/...eeui-0-9-5-beta-for-a8-a8-a7-m20-m30.4252235/
Download the file from there, and in TWRP, flash it as a system image. It should automatically redirect you to the setup. Keep in mind that the resolution and DPI will be incorrect. I fixed it using Easy DPI Changer.
There are some known bugs though. For example, Samsung Camera doesn't work (third party apps will work), and the face unlock. I'd recommend you read the page carefully. If you need anything else, let me know.
EDIT: Just noticed you want Android 12, not 11. My bad. You can try flashing Pixel Experience on your phone. Check this video. Look at the youtuber of this video too, I'm sure you'll find much more help there.
Click to expand...
Click to collapse
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.
Just asked that yesterday, still waiting for reply. I really hope someone will finally make a custom rom designed for this device! GSI images have that bug, and some apps don't open. I'm so sick of staying on Samsung firmware.
Futazaki said:
I tried flashing Android 12 GSI (Arrow and Corvus) but both GSI have lockscreen bug and I can't access my TWRP when flashed. I was wondering if you have any workarounds or fix for these issues. I also tried following the steps shown in the attached link to a YouTube video but there are no fix as well.
Click to expand...
Click to collapse
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.
Zanci19 said:
Get Odin, and flash the stock firmware on your phone. However, this will erase all data on your device, so make a backup first. If you have any questions, feel free to ask me.
Click to expand...
Click to collapse
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.
Futazaki said:
I tried doing this, reverting to the 2020 version to bypass the Knox Security and Encrypted Data sh*t but still, Android 12 has its bugs.
Click to expand...
Click to collapse
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps
AaliShine said:
How are you everyone I am new here I need your serious help please all of great expert kindly focus to my problem it would be easy for you so my problem is actually recently a couple of days ago I just root my Samsung A7 2018 SM-A750F mobile and its Android version was and are now Android 10 okay now I have successfully rooted my this Samsung A7 2018 Android 10 version mobile after hard and painful time I successfully rooted but now I want I like and I really Desire to install latest Android release version Android 12 ok but I want to install custom rom Android 12 with rooted capability so what should I do now I have already my mobile rooted with Android 10 how could I root my mobile with Android 12 version with this model please is someone give a video guide it would be greatful thank you.
Click to expand...
Click to collapse
Sorry for being a little late, ForkLineage-19.1 GSI seems to be working fine on stock kernel, except MTP. Link : https://xiaomemeindex.com/treble/?dir=ForkLineage
random.tek said:
Just before installing android 12, you would want to go to TWRP > Advanced > Terminal and type this command:
Code:
mount /vendor;rm /vendor/lib64/hw/keystore*&&echo "persist.sys.binary_xml=false" >> /vendor/build.prop
Hope this helps
Click to expand...
Click to collapse
Thanks, I'll try this later today. I kinda settled on stock rom since GSI has bad battery backup. Does this get rid of the lockscreen bug?
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?
Futazaki said:
EDIT: it returns an error saying
Code:
rm: can't remove '/vendor/lib64/hw/keystore*': No such file or directory
any help?
Click to expand...
Click to collapse
Sorry for the late reply. The directory is already removed, so you should be good to go