Related
Hi!
I'd like to get rid of the HTC original firmware on my U12+.
I just tried to flash GSIs of LineageOS 17 by AndyYan then AOSP 10.0 by phhusson, without luck.
I have a factory unlocked HTC U12+ (fastboot mode showing Secure Boot : Development, Secure State : S-Off, Device State : Unlocked(U)) so I went straight to the "flash GSI without TWRP" part of the official XDA tutorial: I factory reset the phone, rebooted in bootloader, then erased system and successfully flashed lineage-17.0-20191117-UNOFFICIAL-treble_arm64_avN.img.
But after reboot, I got a bootloop.
I've wanted to try the TWRP method, but upon launch it asked my password for decryption. While I'm sure of the code I've used and typed, decryption doesn't work, so TWRP didn't help.
Then I've flashed the AOSP GSI via fastboot, but then I got a "This device is corrupt. It can't be trusted and will not boot" error message.
So as suggested on another thread I've used the SD card method to flash a RUU, specifically 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528103_signed_2_4.zip. It flashed successfully, but then it booted to the static white HTC logo on black background and stayed there for 20 min.
I can still boot to fastboot mode/download mode, but I don't know what to do.
I can't figure what I'm doing wrong, can you help me, please?
After another attempt I've managed to go back full stock using the microSD card method.
Then I've been able to boot TWRP, which first showed a "Mount" "Decrypt data" screen, asking for a password. The 6 digits code I've used previously doesn't work. So TWRP "failed to decrypt data", also was "unable to mount storage" and "failed to unmount /system_root (device or resource busy)". As suggested, I formatted/wiped data to remove encryption.
Then I performed a factory reset, adb pushed system-quack-arm64-ab-vanilla.img to /data, then flashed it successfully to the system partition, as requested in the afore mentioned official tutorial. On reboot I get another bootloop. Bootscreens shows the HTC and Powered by Android wordmarks and also "** ORANGE **" on the top left corner of the screen.
What am I missing?! :-/
After first boot of flashed RUU at the HTC logo reboot the device. Got there myself, rebooted(using power button) and the OS booted up perfectly.
TWRP doesn't decrypt latest Pie with July Patch. So you will not decrypt it. (Wiping does not decrypt).
I used temporary TWRP, flashed permanent (with touchscreen patch), installed Magisk, Rooted, installed LeeDroid from Magisk for example.
Make sure you have a correct RUU for your CID version.
I am not sure how a project treble ROM will work on this device. You still need signed HTC drivers. I don't think we are ready now for 10 on this device for daily use. HTC did quite awful with the Pie update and many bugs are still not fixed after 6 months.
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
I was unable to determine CID and MID yesterday from fastboot mode or TWRP, so I've downloaded the latest RUU for dual SIM and EMEA model, as my U12+ is dual SIM and I live in Europe.
Now that the phone is back to full stock, I just installed a terminal app right on the phone and executed the following:
getprop ro.cid : 11111111
getprop ro.boot.mid : empty
I understand that the phone is "SuperCID", but I don't really understand what that implies.
Regarding Treble, Treble Info by Hackintosh Five reports (translated from French by me): "Your device supports the old Project Treble version, using VNDK version 26.0."
But the U12+ is listed as supported on phhusson's wiki. A few issues are listed, but I'm fine with them.
I've read a tutorial that asks to "extract the GSI and vendor+boot zips", but then doesn't what to do with the vendor+boot zips. Do you know?
Lastly, do you know what the **GREEN** or **ORANGE** overlay means on the boot screen?
Thank you for your help!
Romano2K said:
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
Thank you for your help!
Click to expand...
Click to collapse
SuperCID implies you can install any RUU (not specific CID). So you can "transform" your US version into european or asian... for a specific reason. No need to do that. Usually there was a specific base that was needed to install a custom ROM or Custom Recovery or people just wanted a different version because they lived in a different part of the world from where the phone was purposed.
I am guessing the **GREEN*** overlay has smth to do with the RUU (if it's embedded in the Boot animation zip (basically pictures+ sound)) or has smth to do with the nature of your tempering (S-OFF/SuperCid etc.)
with this device and serves as a warning for users/devs/internal testing.
You should find your answers on a different section. More active. I see no activity here. And it's HTC's fault for dying" on us. I myself bought the U12 just to own (probably) the last flaghsip device they make. Here's to the comeback.... but I am not sure it will be real. HTC was one of the fastest to update, for example.. until 2019. We are still with bugs and on the July patch. Right not, in reality I am just hoping for one last Pie update to fix bugs and that's it. Will give this device a 1 year run and buy something better.
So go to the Android general section where you can ask how can you compile your ROM on this device. They should help. I can not offer sufficient knowhow on this topic.
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Interesting. Will look into your tutorial. So thank you. If the boot animation.zip was modified you will find in in root/system/[search for it] -you can lookup up each image that forms the animation to check. I myself modified the ZIP to not include the annoying audio, so i deleted it. )
So is the GSI good for daily use? I would mess around with it until i sell my HTC U11. Still using the U11 as a daily driver for the past 2 weeks. And by selling it i mean practically giving a perfectly good phone away for scrap... because it's old.
Deonix said:
I myself modified the ZIP to not include the annoying audio, so i deleted it.
Click to expand...
Click to collapse
That's clever! The HTC boot sound was annoying when I had trouble booting the bootloader, because of the tactile buttons.
Deonix said:
So is the GSI good for daily use?
Click to expand...
Click to collapse
At this point I have a big problem with AOSP 10.0: brightness is blocked at 100%. There's a workaround involving adb, but for some reason adb isn't working with this firmware, even though I've activated developer options and USB debugging. I haven't had the time to tinker yet, I'll give it a try asap and I'll report back!
Thank you again for your help
Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Did Bluetooth work for you on AOSP? Tried to install a few GSIs over the last couple of days but I cannot get Bluetooth working for calls or media. Apparently it's a known issue but none of the fixes I can find here on the forums seem to work for me. Just wondered what your experience was on another U12. I even tried your guide but still no Bluetooth for me.
Useful post about the GREEN message.
I have a Motorola one vision and I want to multiboot it. I already have twrp and magisk root, but when I try to install dualboot patcher or multirom etc... (I have tried all of them) it says that my phone isn't compatible with those multiboots.
Can someone help me porting a multiboot for my phone?
RaphaNinja08 said:
I have a Motorola one vision and I want to multiboot it. I already have twrp and magisk root, but when I try to install dualboot patcher or multirom etc... (I have tried all of them) it says that my phone isn't compatible with those multiboots.
Can someone help me porting a multiboot for my phone?
Click to expand...
Click to collapse
I've never used any of those tools myself but my guess is that they're outdated and doesn't work on devices with A/B slots.
In theory you'd be able to dual boot by switching slots, but it's not exactly that simple in reality.
Both slots share the same data partition, so in order to switch slot you'd have to reset or even format data every time you switch.
Not very practical.
To make it work properly I think we would need a custom made twrp and a repartitioned data so that also data would be split up as A/B.
Kind of how oneplus 7 solved dual boot.
[RECOVERY][DUALBOOT][MAGISK][3.3.1-79][Unified]Unofficial TWRP for OnePlus 7/7 Pro/5G
Can we adapt one plus 7 multiboot for Motorola one vision or something like that?
tys0n said:
I've never used any of those tools myself but my guess is that they're outdated and doesn't work on devices with A/B slots.
In theory you'd be able to dual boot by switching slots, but it's not exactly that simple in reality.
Both slots share the same data partition, so in order to switch slot you'd have to reset or even format data every time you switch.
Not very practical.
To make it work properly I think we would need a custom made twrp and a repartitioned data so that also data would be split up as A/B.
Kind of how oneplus 7 solved dual boot.
[RECOVERY][DUALBOOT][MAGISK][3.3.1-79][Unified]Unofficial TWRP for OnePlus 7/7 Pro/5G
Click to expand...
Click to collapse
Can we adapt one plus 7 multiboot for Motorola one vision or something like that?
I know a flashing zip that adapt dualboot patcher for other devices, but when I flashed it returned with an error.
RaphaNinja08 said:
Can we adapt one plus 7 multiboot for Motorola one vision or something like that?
I know a flashing zip that adapt dualboot patcher for other devices, but when I flashed it returned with an error.
Click to expand...
Click to collapse
The developer of Dualboot patcher had dropped the project due to change in android rom structure done by google i.e system as root structure, starting from pie i guess, which totally doesn't work with Dualboot patcher's mbtool.
So adding support for new devices running right from pie won't work. And yes, the one plus method will work ,but there is need of lots of coding, proper repartitioning and above that many testers are needed.
Can please some good developer manage to provide something like that custom twrp with dual boot or any other alternative way?
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
Your device already rooted right? How long u wait to unlock bootloader?
Kuma_Chaser said:
Your device already rooted right? How long u wait to unlock bootloader?
Click to expand...
Click to collapse
You have to wait 604,800 seconds. Same for everyone
A possible solution could be to create a new dynamic partition and flash your custom OS onto it.
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Slim K said:
Your mentioned example for the one plus 7 pro uses the unused B partition from A/B partition slot to boot other ROMs.
Sadly our device uses A-Only partitioning scheme.
Click to expand...
Click to collapse
drahtwurst said:
people on xda working on that for other fons already here (TWRP), here (TWRP) and here (orangefox). would be great to have that for poco x3 nfc too
Click to expand...
Click to collapse
Did you check those posts and above comment? They all do use A/B partitions the x3 does not have. And imo a true non buggy/ deep hack multi boot solution without partition support is yet to find.
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
drahtwurst said:
i was showing links i found for anyone interested and hopefully//partially//capable in developing a solution. it is clear, the poco does not have a/b patition scheme. are you mad i did not provide a solution?
Click to expand...
Click to collapse
Why should I be mad? I am not interested in dual boot. I am just telling you, that it wont be of any help as all 3 links point to OnePlus devices (2 also to already linked OP7) where TWRP/OF does make use of A/B partitioning. It doesnt mather how many twrp dual boot links you post if you can clearly see that they use s.t. which the x3 nfc does not have.
To make that more clear here mi a2 A/B do you think it will help? No. Several old methods of dual booting, one thing more buggy than the other https://www.xda-developers.com/dual-boot-on-android-a-power-users-holy-grail/ and lets not forget https://forum.xda-developers.com/t/app-boot-manager-pro-dual-boot-unlimited-roms-wip.1617055/ ... all useless (never stable or for A10+ anyway). There was this rel good working method for Sony Dev. loading up in early in modified kernel but yeah device specific, limited kernel & Co. .... Had no future. Except A/B partitioning there is simply nothing that works (good and/or modern devices).
you have clearly more oversight. i just guessed A/B partitioning can be done somehow. maybe dual boot is not even the best solution for what i am looking for. it used to be for me some years ago.
still searching for best solution to use banking+navigation but avoid gaugle + tracking as much as possible. keeping data with myself using FOSS apps+nextcloud is what i started with recently. OT.
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.
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?