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.
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
Hey guys!
So as well all know support for this device is pretty Mich close to nothing, but luckily it sports the A/B partition system like the Pixel phones, so Treble GSI Roms are compatible. However, simply flashing the GSI files doesnt seem to work, it ends up in a boot loop.
Anyone willing to guide me or help out?
I'm sure there are many device owners who would be happy to have someone help them
Update: My bad, I used to have the Essential Phone which had the AB partition system
it doesnt support a/b partition is a-only... i wrote a guide about how to install android 10 on u11+ : https://forum.xda-developers.com/htc-u11/how-to/how-to-install-android-10-htc-u11-t4100409
Slok 00 said:
it doesnt support a/b partition is a-only... i wrote a guide about how to install android 10 on u11+ : https://forum.xda-developers.com/htc-u11/how-to/how-to-install-android-10-htc-u11-t4100409
Click to expand...
Click to collapse
Thanks Slok! Sometimes the relevant posts just slip right from under my nose
I am coming from a OnePlus 5, I literally just got my hands on OnePlus 9 a couple of hours ago. It looks like a few things has changed and things are not as straight forward as flashing a zip file in TWRP. I have been reading through a few things and just want to ask some questions.
Is TWRP even needed anymore? Most instructions on flashing roms is done via sideloading and booting into recovery via fastboot (some requires OSS while others LOS recovery).
What is the easiest way to root (on OSS 12)? Seems to be a good mixture of different ways to root and reading comments does not make it any easier, if anything even more confusing.
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
posar said:
Which OnePlus 9 do you have? I'm assuming you're on global OOS 12 as I don't think 12 has come to the T-Mobile variant officially, but I wanted to double check and see if I could point you in the right direction.
Click to expand...
Click to collapse
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Z-Blade said:
I got the 2115 model, I believe that is global. Can you not just flash ROMs in TWRP anymore? I see all of the ROMs requires sideload which means you need a computer. I am a bit of a flashaholic and even though sideload is not a big issue.
Click to expand...
Click to collapse
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
posar said:
Not really, unfortunately. For most ROMs, it seems you have to go to the most recent version of OOS 11 and then flash from there.
Click to expand...
Click to collapse
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Yeah, it seems as if the simple TWRP days are over, at least for OnePlus. Maybe someone smarter than me will get it working flawlessly.
Z-Blade said:
That is unfortunate. I got root going on OSS 12 but at this point I don't really see a reason to flash TWRP since the recommended way to flash custom ROMs is different. I hope all of the Devs ends up following a particular standard.
Click to expand...
Click to collapse
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
JustLeoSC said:
Can you tell me how did you obtain root on OSS 12? I tried severalmethods but ended up with errors an even some soft-bricked times. As you stated in the 1st message, there is plenty of ways around the internet and comments making it really confusing.
Click to expand...
Click to collapse
I downloaded the patched boot.img from the link below and I recommend you also down the normal stock boot.img as well.
[DISCONTINUED][OOS & PA] OnePlus 9 stock/patched boot images
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP. Hi! There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android...
forum.xda-developers.com
In that thread there is a link to a 'Great root guide', I used that root guide and the patched boot.img to root Android 12.
Nice! After several tries, some softbricks and a lot of haste for the different methos I finally got it rooted. Thank you man, it worked like a charm!
I was under the impression my phone was compatible and began the install instructions for LineageOS after unlocking my phone through this guide. I flashed the two partitions, flashed the recovery, attempted to boot into recovery and it gets stuck on boot. After attempting to ask the LineageOS community I realized Verizon's version is not supported, woo. I then tried to follow the unlock guide to flash back the stock image and Msm fails on Param preload with the error "Device not match image." Googling that I only found someone implying they were using the incorrect global image, however, I know I'm not. Is it possible to recover my phone now and if so, how?
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Xryphon said:
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Click to expand...
Click to collapse
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
rusty-op8 said:
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
Click to expand...
Click to collapse
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
rodken said:
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
Click to expand...
Click to collapse
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
rusty-op8 said:
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
Click to expand...
Click to collapse
All is not lost as long as your device can power on and is not completely bricked.
Is there any custom roms available for moto g62 if so please reply
i cannot find any custom roms, i have only unlocked the bootloader and install magisk
hi, me to need any unoficial rom without knox. I have blocked phone
4live2kill said:
i cannot find any custom roms, i have only unlocked the bootloader and install magisk
Click to expand...
Click to collapse
Could you write a step by step guide on how to do it?
synakszymon09 said:
Could you write a step by step guide on how to do it?
Click to expand...
Click to collapse
have written it up in your other post.
You do realise that android 12 is GSI compattiable?
smiley.raver said:
You do realise that android 12 is GSI compattiable?
Click to expand...
Click to collapse
Ya I have tried gsi but didn't like less customisation and not got for daily driver
most of the custom roms are GSI I have a heap of GSI roms that had way more customization not less..??
smiley.raver said:
most of the custom roms are GSI I have a heap of GSI roms that had way more customization not less..??
Click to expand...
Click to collapse
Can you
help with installation I have bricked my device by getting errors in adb commands
Joseph2810 said:
Can you
help with installation I have bricked my device by getting errors in adb commands
Click to expand...
Click to collapse
use motorola Rescue & smart assistant
you need to provide alot more details if you want help
what errors are you getting, when are these errors coming up, how are you trying to connect device etc what are you doing to get errors - what have you tried to fix it.
need to know alot more then you have bricked your device - what were you doing to brick it?
smiley.raver said:
use motorola Rescue & smart assistant
Click to expand...
Click to collapse
Yeah I have recovered it is not my first time
Joseph2810 said:
Yeah I have recovered it is not my first time
Click to expand...
Click to collapse
Mate your not making any sense right now.
You ask for help, but then say it's not your first time???
Why exactly are you wanting?
smiley.raver said:
you need to provide alot more details if you want help
what errors are you getting, when are these errors coming up, how are you trying to connect device etc what are you doing to get errors - what have you tried to fix it.
need to know alot more then you have bricked your device - what were you doing to brick it?
Click to expand...
Click to collapse
I forgot the name of the error some command don't work it is because I didn't get the correct guide please provide the correct guide
smiley.raver said:
Mate your not making any sense right now.
You ask for help, but then say it's not your first time???
Why exactly are you wanting?
Click to expand...
Click to collapse
I want to install gsi rom without getting bricked
Joseph2810 said:
I want to install gsi rom without getting bricked
Click to expand...
Click to collapse
Refer to my previous comments, need more information to the issues and how you got to softbrick. Which guide, is the guide suited to your particular phone eg a/b device vs a only, are you trying to flash a super partition to a super partition or a system image to a super partition via fastboot?
If your not willing to go in to depth into what's happening to how you brick your device, then please stop asking for help, as we cannot help you when we don't know the details of the issue.
Clearly it's only soft-bricked and not hard-bricked.
And if its not your first time installing GSI then the process doesn't change. There a plenty of guides out there.
Simple solution is dsu sideloader to which you will not have to worry about soft bricking your device
smiley.raver said:
Refer to my previous comments, need more information to the issues and how you got to softbrick. Which guide, is the guide suited to your particular phone eg a/b device vs a only, are you trying to flash a super partition to a super partition or a system image to a super partition via fastboot?
If your not willing to go in to depth into what's happening to how you brick your device, then please stop asking for help, as we cannot help you when we don't know the details of the issue.
Clearly it's only soft-bricked and not hard-bricked.
And if its not your first time installing GSI then the process doesn't change. There a plenty of guides out there.
Simple solution is dsu sideloader to which you will not have to worry about soft bricking your device
Click to expand...
Click to collapse
I don't want dual boot I want full installation without custom recovery
smiley.raver said:
Refer to my previous comments, need more information to the issues and how you got to softbrick. Which guide, is the guide suited to your particular phone eg a/b device vs a only, are you trying to flash a super partition to a super partition or a system image to a super partition via fastboot?
If your not willing to go in to depth into what's happening to how you brick your device, then please stop asking for help, as we cannot help you when we don't know the details of the issue.
Clearly it's only soft-bricked and not hard-bricked.
And if its not your first time installing GSI then the process doesn't change. There a plenty of guides out there.
Simple solution is dsu sideloader to which you will not have to worry about soft bricking your device
Click to expand...
Click to collapse
I did this guide but step 13 failed
Joseph2810 said:
I did this guide but step 13 failed
Click to expand...
Click to collapse
Again, how what is the error. Just telling me it fails does not provide us the information to help you.
If you are not willing to give the information, please stop asking for help, I will not ask for it again.
You are not providing anything. You are asking for help, and it could be that the guide does actually work, and it is a user input error.
So I will ask for the last time to which If you do not respond with full details of what you are doing step by step, with screenshots and the exact error and the exact commands you have used then I will not be responding as I cannot help you.
So provide the details of exactly what you have done, exactly the commands you have entered (all in one screenshot of terminal is acceptably fine) the exact error, and anything else you think maybe important.
I will not just go and get a full detailed step by step as all gsi are different, most GSI are easier to install with working custom recovery, and are you following the basic GSI rules eg is the system image you are trying to flash the same size or smaller then what is on your phone?
So please provide everything I am asking for, and if not then I will not be replying, someone else may, but we do not have the time to find a needle in a haystack as to what your problem is.
I do not have the time to try the guide and F**K around with my phone OS at this present time and most people won't as who is to say that the guide will work for me, which then still leaves the solution coming down to you providing information so that we can actually help you and find out why it's not working.
I have problem i installed lineage os gsi 20 with dsu and IT works perfectly but when installed same image installed with fastboot IT will stuck on boot can Anyone help me?