Hello guys is there anyone willing to help me out?
Im long term HTC user in the past 15 Plus years i was flshing whatever i want and im familiar with this but i switched to Pixel 2 and i want to clear for myself few things prior before to brick it.
I also read this guide: https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
But its seems like the thread is not updated and some users mention problems with flashing Magisk etc.
Im fully Stock locked bootloader with the latest Android Pie from 5 January 2018
The Pixel i use is Google Edition worlwide version not loocked to any network etc.
The main reason to want to Bootloader unlock it is because i need the Magisk in order to be able to flash and use few of the must have for me apps that i use all the time.
1st is SAURON audio - without Magisk and TWRP this is not posible.
2nnd few additional Magisk modules that i use non stop in the past few years.
What is not clear for me is the steps and exactly the second steb with Flashing Flashing factory images?!
In HTC i need to get the bootloader unlock S-OFF is i want and flash a TWRP in this case i can flash on top Magisk so here is different and not very clear for me as well.
When im now on the latest Android version from 5 January do i need still to flash FACTORY IMAGE after unlocking the bootloader?
Is anyone willing to help to clear the things out before to mess the device.
Thanks in advance
tsalta said:
Hello guys is there anyone willing to help me out?
Click to expand...
Click to collapse
Hi If you just want to unlock bootloader, there is no reason to flash factory image again. Just allow unlock bootloader in developer options, reboot to bootloader and run fastboot flashing unlock, this will fully wipe/factory reset your device.
Now you could boot/flash TWRP and install magisk.
When will be new monthly update available, flash it with help of this thread:
Code:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Good luck :good:
somin.n said:
Hi If you just want to unlock bootloader, there is no reason to flash factory image again. Just allow unlock bootloader in developer options, reboot to bootloader and run fastboot flashing unlock, this will fully wipe/factory reset your device.
Now you could boot/flash TWRP and install magisk.
When will be new monthly update available, flash it with help of this thread:
Code:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
Good luck :good:
Click to expand...
Click to collapse
Thank you for the info.
So this mean i dont need to flash Image if im with the latest stock Version.
I prefer to stay stock just miss some Magisk modules thats why i wondering what to do.
Can i flash just a Kernel for example KiriSakura after unlock the bootloader and install TWRP just to flash Kiri Kernel with the stock rom im now and other Magisk stuffs like Sauron etc.
Thanks again
Hi exactly, if you run latest stock you havn't flash it again after bootloader unlock.
If you want to petmanently flash twrp, you have to do it before flashing magisk, othetwise you willn't be able to boot os only twrp.
My ROM doesn't have a version that is available specifically for my phone (Motorola Moto E5). However, my phone is probably Project Treble-enabled (I'm not sure and I don't know how to check) and this ROM is shipped as a GSI image.
Can I safely install any GSI image not intended for my phone and will it still run after? And even if it doesn't work, will I still be able to flash a ROM? I don't want to brick my phone, because unbricking is hell.
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Maybe ask in an appropriate thread, but you could try dirty flash, stock is flashed the same way.
Odeya said:
Hi guys,
How do i update the pixel experience rom from android 12 to 13? is it just flash it through recovery and adb sideload, or is there any necessary step i should do before flashing it? like updating the recovery maybe? Im using pixel experience custom recovery and my device is unroot, only bootloader is unlocked
Any answers would be appreciated, thanks!
Click to expand...
Click to collapse
Backup all data and dirty flash. If you get errors, clean flash is helpful
Since it's a jump from one Android version to another, it's better to clean flash. Although, a dirty flash should still be possible once you wipe OS.
There should be a new, updated recovery file to flash as well. Tbh, the jump from A12 to 13 is not as big as the previous upgrades, with not much gains.
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.
How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?
All 3 phones manufactured in 2022.
The Bootloader is unlocked for all 3. USB Debugging is turned on.
- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.
- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.
- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.
Is it possible to get a Generic BOOT.IMG to modify for root?
Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?
Are there other ways to get root without a BOOT.IMG?
Is there a way to parse the entire phone to compile a BOOT.IMG?
The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!
Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?
Or, would we need a Jtag hardware reader?
Thank you in advance for your time and help which is greatly appreciated!
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
V0latyle said:
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Click to expand...
Click to collapse
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
defcondoc said:
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Click to expand...
Click to collapse
No, but it is the most popular and arguably the best
defcondoc said:
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
Click to expand...
Click to collapse
No, because again you need root to run adbd as root. I could be wrong...
defcondoc said:
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
Click to expand...
Click to collapse
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
kelvinchinedu said:
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
Click to expand...
Click to collapse
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.
Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
alecxs said:
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Click to expand...
Click to collapse
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?
To get a GSI that is already rooted, I must install the file with S in the filename?
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
defcondoc said:
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
Click to expand...
Click to collapse
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
omb714.1980 said:
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
Click to expand...
Click to collapse
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
defcondoc said:
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
Click to expand...
Click to collapse
I'm having the same issue with the ANS your not alone.
omb714.1980 said:
I'm having the same issue with the ANS your not alone.
Click to expand...
Click to collapse
I appreciate you letting me know. Good to know I'm not the only one.
Did anyone ever figure out how to unlock the bootloader yet?
ronnieshane1 said:
Did anyone ever figure out how to unlock the bootloader yet?
Click to expand...
Click to collapse
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
defcondoc said:
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
Click to expand...
Click to collapse
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.
hello folks,
Extreme noob here and I have caused myself a problem to prove it. I was trying to get Lineage OS got to flashing the lineage recovery for bramble specifically "fastboot flash vendor_boot vendor_boot.img" and have been stuck in fastboot mode sense.
What I'm pretty sure has happened is that I...didn't read closely enough and was not the proper Android 13.0.0 firmware it required. I was wondering if there was a link anywhere to the stock img that I can replace this with so as to start again and update the firmware? Only thing I've changed so far is different tries at flashing boot_a boot_b and vendor_boot. So I assume I just need an img that works with an older android version in there?
any help would be appreciated.
thank you