Database Info

[STOCK][CROSSFLASH][GUIDE] How to install Stock Rom (or crossflash) using LG UP

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a guide on how to install Stock Rom or Crossflash on any LG G7 ThinQ
(Except for G710TM and G710V)
Please read everything written down and on the second post before asking questions!​
Before we do anything i have to explain some stuff:
I am not responsible for any damages that may occur during the installation or after it. I dont have every G7 on the world to test it so something unexpected can happen. Still if something is not clear ask here for help.
Stock roms should work on almost every model (G710TM (Anything related to T-Mobile) models are not supported)
Note: for models from ATT, Cricket, Sprint, BoostMobile, VirginMobile, AIO and Tracfone wont be able to go back to their stock firmware because ther is no KDZ or Dump available. Note2: It's not recommended to flash ANY Stock rom to G710V. You may not be able to complete the startup setup.
Some features may or may not work:
VoLTE/VoWIFI
Loss of Serial Number
Widevine will downgrade to L3 (No Netflix HD)
SafetyNet Issues
Join our Telegram Group here:
>> {Mod edit! Oswald Boelcke, Senior Moderator} <<
Let's Begin​
Step 0:Make sure that you have read everything that was written above. Also please uninstall any previous version of LGUP if presented.
BACKUP BEFORE DOING ANYTHING!!!​
Step 1:Everything that you need:
https://drive.google.com/open?id=18i2WZksRjcrvg-KQjaHuzInd7_sbRBvq (USB Drivers)
https://drive.google.com/open?id=1dJZxrj7nteDDUcQpiJLpX9Mjumm5mtKp (LGUP 1.15.06)
https://drive.google.com/open?id=1V8IF2vJed3bQBsBCHLNBJdnW4gRj2uo0 (LGUP_Common/ LGUP dll)
https://lg-firmwares.com/ (KDZ Files if you dont have any) (Ignore the G710TM KDZs)
Click to expand...
Click to collapse
Step 2:After downloading everything install:
The USB Drivers (LGMobileDriver_WHQL_Ver_4.2.0.exe)
Then LGUP (LGUP_Dev_Frame_Ver_1_15_0_6.msi)
Step 3:Turn off your phone and then:
Hold volume up
Plug your USB Cable to your phone while holding volume up (The usb must be connected to your pc)!
Now the phone should look like this.
Click to expand...
Click to collapse
Step 4:Open the device manager
There will be a tab with the name "Ports"
Open it and it shoud look lime this.
Note:If you dont see it or there is a problem with is. please try reinstalling the drivers from before.
At the end it should say COMX.
Remember that number. We will need it in the next step.
Step 5:Time to install pie!
Go to
Code:
C:\Program Files (x86)\LG Electronics\LGUP
Extract the "common" folder from LGUP dll (LGUP_Common.zip) inside the folder "model".
Then go back to C:\Program Files (x86)\LG Electronics\LGUP (if you're not already there)
Hold the shift key and right click on a free space.
Choose to open a command prompt.
Note:If you're on windows 10 it will be called a PowerShell. After oppening it type cmd and hit enter.
After that type
Code:
lgup_cmd.exe com[B]X[/B] "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" [KDZ Loctation]
X = Your number from step 4 (e.g. com3)
[KDZ Location] = Your full path to your KDZ File (G710_Something_something.kdz)
After that the phone should start being flashed and after a bit it should boot into your new Stock Rom​
Click to expand...
Click to collapse
Feel free to ask questions!
Credit and a lot of thanks to:​
@Sellerie_ for his amazing help with TWRP and custom system overlay for the G7
@J0SH1X for getting AOSP to work on oreo and pie firmware and also his awesome work on TWRP

Nothing to see here​

Best guide so far! Thanks a lot!

God bless You man!

Nice work!! How is camera working on AOSP? Wide angle working?

oliake said:
Nice work!! How is camera working on AOSP? Wide angle working?
Click to expand...
Click to collapse
Works great with the lastes apk from Arnova

LameMonster82 said:
Works great with the lastes apk from Arnova
Click to expand...
Click to collapse
Cool, thanks! Another question, i'm trying to flash korean version of pie but when I try to flash it, It looks like this. And yes I chose the right port which is 4 in my case but it still says ''COM0''
Do you know how to fix this? Thanks!
Selected Port : COM0
SW Version :
Model Name :
Can't get device SW version
Download Error

oliake said:
Cool, thanks! Another question, i'm trying to flash korean version of pie but when I try to flash it, It looks like this. And yes I chose the right port which is 4 in my case but it still says ''COM0''
Do you know how to fix this? Thanks!
Selected Port : COM0
SW Version :
Model Name :
Can't get device SW version
Download Error
Click to expand...
Click to collapse
It seems that you didnt extract the zip correctly.

Guys I got error "[SW PATH] is null"
after lgup_cmd.exe com5 (in my case) C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll C:\Program Files (x86)\LG Electronics\LGUP\model\common\G710N20c_00_LGU_KR_OP_0107.kdz

tweteks said:
Guys I got error "[SW PATH] is null"
after lgup_cmd.exe com5 (in my case) C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll C:\Program Files (x86)\LG Electronics\LGUP\model\common\G710N20c_00_LGU_KR_OP_0107.kdz
Click to expand...
Click to collapse
By kdz location i mean where you downloaded your kdz.
Also i forgot to add quotes for the path so i guess thank you for showing it to me
In your case the command should be:
Code:
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" [KDZ Path like your download folder or the place where you downloaded the kdz file]
For example
Code:
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "D:\MyFiles\Desktop\LG G7 Files\G710NO20c_00_OPEN_KR_OP_0107.kdz"

LameMonster82 said:
It seems that you didnt extract the zip correctly.
Click to expand...
Click to collapse
Problem was with the DLL like you said, but it was that Powershell wouldn't find it so in the command where it says model\common\LGUP_Common.dll, I erased LGUP_Common.dll from the code and manually drag the DLL file from the folder and drop it into code instead, if you understand what I mean! So the code would look something like this instead lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common"C:\Program Files (x86)\LG Electronics\LGUP\model\LGUP_Common.dll" and that worked and now I have pie installed on my phone!
Thank you so much for the tutorial, it was so easy to follow!

Next problem LameMonster82
C:\platform-tools>fastboot --set-active=a flash boot_a TWRP_RealPie.img
Sending 'boot_a' (65536 KB) OKAY [ 1.682s]
Writing 'boot_a' OKAY [ 0.360s]
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 2.262s
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_
a
unknown partition 'vbmeta_a'
fastboot: error: cannot determine image filename for 'vbmeta_a'

tweteks said:
Next problem LameMonster82
C:\platform-tools>fastboot --set-active=a flash boot_a TWRP_RealPie.img
Sending 'boot_a' (65536 KB) OKAY [ 1.682s]
Writing 'boot_a' OKAY [ 0.360s]
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 2.262s
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_
a
unknown partition 'vbmeta_a'
fastboot: error: cannot determine image filename for 'vbmeta_a'
Click to expand...
Click to collapse
You forgot to put vbmeta_a.img full path at the end
Example:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a[B] "D:\MyFiles\Desktop\LG G7 Files\vbmeta_a.img"[/B]

Guys I got same bug on HavocOS, Resurrection Remix n Pixel Dust - led notificator always blinking (light blue color)
Any ideas to solve the problem?
Anybody else got same?
Options to disable LED inside ROMs isnt working.
Start blinking with ROM's logo show up.

tweteks said:
Guys I got same bug on HavocOS, Resurrection Remix n Pixel Dust - led notificator always blinking (light blue color)
Any ideas to solve the problem?
Anybody else got same?
Options to disable LED inside ROMs isnt working.
Start blinking with ROM's logo show up.
Click to expand...
Click to collapse
As I said it's a bug in AOSP that is ultra hard to fix. You just have to deal with it

Can i flash pie on my branded g7?
(Sorry for the silly question, but i've never flashed a phone ?)

MP39 said:
Can i flash pie on my branded g7?
(Sorry for the silly question, but i've never flashed a phone ?)
Click to expand...
Click to collapse
As I said most models work

Hello! Does this work with LG g7 plus 6gb dual sim eaw modell?

Inerent said:
Hello! Does this work with LG g7 plus 6gb dual sim eaw modell?
Click to expand...
Click to collapse
You can try reading the thread but yeah it does

---------- Post added at 07:55 PM ---------- Previous post was at 07:51 PM ----------
LameMonster82 said:
You can try reading the thread but yeah it does
Click to expand...
Click to collapse
1. I have read the thread, but I'm a little suspicious. I just don't want to break my imei, partitions or important things.
2. Is your method different than flashing a firmware with lgup, or the power shell command does something else than normal flashing with lgup?
Thx for your tutorial.
P. S. I want to go for the stock Korean firmware but as I said I am afraid of breaking things like repartitioning the storage, loosing imei and efs folder, serial numbers, drm keys etc. I'm also on dualism, will that work?

Alcatel 1 Root Achieved

Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks dude, that worked perfectly.
Any idea how to get GAPPs working?

What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.

I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...

Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.

ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu

Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.

ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed

With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.

I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?

hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.

Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!

FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?

Sometimes the phone gets stuck on boot, any clues?

No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo

I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!

Solution
@caish5
 @FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.

Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse

I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.

Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?

[ROM][LINUX][ANGELICA][ANGELICAN] Droidian Bookworm

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements​
Android 10 firmware for your device:
Redmi 9C/9C NFC angelica: LINK.
Angelica​
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_angelica-api29-armhf-nightly_XXXXXXXX.zip
Installation​
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Notes​
The default password is 1234.
List of working things can be found at https://github.com/droidian-mt6765/device-page
Bugs​
Encryption is not supported.
Mobile data needs an APN to be set up from Settings -> Mobile -> Access Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or receiving phone calls. Toggle Mobile Data from the settings off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strenght is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Mobile hotspot does not work.
Final notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Attached images are from different devices but the interface looks and acts the same.

will it work on redmi 9c nfc ?

skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
Not tested

FakeShell said:
Not tested
Click to expand...
Click to collapse
Ok

It looks very promising. Isn't this something similar to Ubuntu Touch? I'd love to set this rom as my daily driver, but the bug list and its seriousness is way too much for a daily driver phone. I will, however, try it as a tester. Nice work though!

i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)

Hanhan.i7 said:
i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)
Click to expand...
Click to collapse
This is a known issue with droidian on MTK devices
Screen touching and power button not work on Dandelion · Issue #1 · droidian-mt6765/adaptation-droidian-garden
Hi @FakeShell: Thanks for your porting Droidian to Redmi 9A (Dandelion), is amzing! I followed the guide and got it running successfully! I'm having some problems with the touch screen and power bu...
github.com

skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
hello i doing exacly like in solution but it wont boot ;/ dont work on redmi 9c NFC Angelican

Not tested on angelican
only dandelion and angelica

FakeShell said:
View attachment 5665903​Requirements​
Android 10 firmware for your device:
Redmi 9A dandelion: LINK.
Redmi 9C angelica: LINK.
Dandelion​
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Angelica​
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Dandelion installation​
Flash boot-dandelion.img: fastboot flash boot boot-dandelion.img.
Flash dtbo-dandelion.img: fastboot flash dtbo dtbo-dandelion.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-dandelion.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Angelica installation​
Flash boot-angelica.img: fastboot flash boot boot-angelica.img.
Flash dtbo-angelica.img: fastboot flash dtbo dtbo-angelica.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Notes​
The default password is 1234.
Xiaomi has not updated their kernel source tree and as a result some models of 9A and 9C have non functional display panels with our kernel.
Droidian GSIs are experimental! Bugs and missing features are expected.
List of working things can be found at https://garden.bardia.tech
Bugs​
Mobile data needs an APN to be set up from Settings -> Mobile -> Acess Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or recieving phone calls. Toggle Mobile Data from the settins off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strengh is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid which is currently not available on angelica and dandelion.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Just like bluetooth, hotspot does not work from settings either and has to be used from a GUI application (such as the default advanced network app) or from terminal
Flashlight can be used via the desktop icons only.
Final notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Click to expand...
Click to collapse
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.

MarvinG_88 said:
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.
Click to expand...
Click to collapse
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process

FakeShell said:
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process
Click to expand...
Click to collapse
pbrp worked . Thanks for the guidance!

Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone. It is a Redmi 9C NFC

Mario6w891 said:
Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone
Click to expand...
Click to collapse
Landscape issue is present in a few other mediatek devices as well (there was also a touch issue on all mediateks which we fixed) no fix for that yet
Check which slot your simcard is in and change it in /etc/ofono/ril_subscription.conf
change the values ril_0 to ril_1 and slot1 to slot2
systemctl restart ofono ofono2mm
you also have to set your apn settings manually in gnome control center/settings app
its a low end device and mediateks were always in the slower end on linux so you will experience slow downs nothing we can do

Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/

Mario6w891 said:
Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/
Click to expand...
Click to collapse
You can find your carriers APN in their website or by just searching the web

Thank you again, but I switched my OS due to missing features I needed like WhatsApp.

Cubot Pocket: unlock bootloader and flashing GSI/lineageOS

I finally got my cubot pocket. I like my devices without GAPPS so I unlocked the bootloader and finally managed to flash a GSI.
This post contains: observations and general hints for this level of development, a guide to unlock the bootloader and what I did so far to flash a GSI.
Unlocking the bootloader​This works similar to other Spreadtrum/Unisoc-based devices.
The crucial thing is to issue get_identifier_token from fastboot -> reboot to bootloader. If you issue it in adb reboot fastboot, it will say OKAY and may also print a four character string, but this is not the token you're looking for.
Also, when you flash the unlock_bootloader signature.bin, it will prompt you on the phone, but you have to react differently than described on the phone - see below.
enable Android developer mode (Settings -> About Phone -> tap "build number" >= 7x)
enable OEM unlocking (Settings -> System -> Developer Options -> OEM unlocking)
enable ADB (Settings -> System -> Developer Options -> USB debugging)
adb reboot fastboot
choose "reboot to bootloader"
Code:
$ fastboot oem get_identifier_token
proceed as described here
finally:
Code:
$ fastboot flashing unlock_bootloader signature.bin
this prompts you to press volume up to cancel, volume down to confirm.
But volume down and power don't have any effect, instead volume up starts wiping user.
wiping takes a bit longer than I'd expect, for me 433 s.
Congratulations, you now own your phone a bit more than before!
Flashing GSIs (probably applies to ROMs in general)​It's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
get and unpack necessary files as necessary: boot.img, vbmeta-sign.img, a ROM that you want, p.ex. AndyYan's Lineage GSI
fastboot resize-logical-partition product_a 38000
fastboot flash system [unpacked ROM file]
I also factory reset it afterwards
General/random notes​
there are two different things reachable as "bootloader":
in fastboot switch to bootloader. The device displays the Cubot splash and from the display it looks stuck, but it exposes a fastboot interface -> useful
$ adb|fastboot reboot bootloader
shows the droid with open service door, saying "no command". It also exposes adb, but I don't see a way how to authorise it. Maybe via the debug UART? I didn't yet read the UART when I stumbled upon this. Currently it seems useless to me.
there are test points for the debug UART easily reachable once you disassemble it.
I didn't see anything with a 3.3V USB UART adapter, but a logic analyser with 1.4 V threshold works -> it probably uses 1.8 V logic level. UART-wise it's 115200 8n1.
I think I don't have anything to hook up to the TX currently.
UART log of boot
it's easy to softbrick this device, and I haven't found a nice way out of softbricked yet. Two not-so-nice-ways
- drain the battery, which obviously requires lots of patience
- disassemble the device and disconnect the battery
then flash the original ROM from the cubot site following the instructions there.
Once it bootloops, I didn't manage to power it off or get into fastboot / recovery using the device's keys.
the device reconfigures it's USB during boot and there's a limited time for the SPDFlashTool's mode that flashes complete firmwares. That means that it's not really feasible to run SPDFlashTool inside a VM.
the phone actually does something with the battery detached but USB power attached. For example, it's possible to flash it with the SPDFlashTool. However, it doesn't boot the linux kernel / Android, this seems to be inhibited.
This is in contrast to many other devices that are not laptops for which the PMIC does not provide power to the system when the battery is disconnected.
Old notes / how not to do it: Flashing GSIs (probably applies to ROMs in general)​
it's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
system_a is a bit below 1 GB ( 0x3CF5D000 B) which is likely smaller than any interesting GSI.
attempting to flash yields
Code:
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
There's the general hint to delete the product partition by running
fastboot delete-logical-partition product
then it's actually possible to flash a GSI, however:
the device bootloops -> log
From the log I realised I need to modify vbmeta, so:
it does android verified boot / AVB which from my understanding the easiest way forward is to disable it by:
creating a vbmeta.img with
Code:
$ avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
the padding necessary might be 16384 instead, according to the hovatek thread below.
it might be necessary to pad it additionally. There's a tutorial and a script here
when I flash both the hovatek-unpadded avbtool-4096-padded and hovatek-padded avbtool-16384-padded vbmeta, the device bootloops -> log
I guess the next step would be to unpack the vendor PAC ROM and check how the vbmeta image looks there.
Since with the original vbmeta it looks like it's restarting when it's already running linux / android, another way to go at this might be to change the kernel cmdline: instruct it to not do verity - Does anyone know how this is possible?

reserved for future use

dead ends (so far...)​
didn't manage to find what image header magic number was wrong with the vbmeta.img (was already in the starting post)
the vbmeta actually doesn't chain to system, but there's a vbmeta_system partition (and vbmeta_vendor.img, vbmeta_system_ext.img, vbmeta_product.img) - I flashed the empty vbmeta disabling checking to vbmeta_system... and it bootloops again
this time the error is:
Code:
sprd_get_all_imgversion: ab_slot_flag is 0
read successed
sprd_get_all_imgversion: rpmb read blk 16382 successful
invalid sprd imgversion magic 0 exp a50000a5
uboot_vboot_verify_img() return error:param->a0=3
could be that it's just necessary to write the magic number to the correct offset, but I coulnd't figure out where this offset is - the images in the PAC don't have this number, so I guess it's embedded on-the-fly while flashing.
searching for imgversion+spreadtrum gets 0 relevant results - I guess it's very unusual that people hook up to the debug uart
I didn't manage to disassemble uboot.img - At least the disassemble doesn't look like a bootloader to me. Not an expert with disassemblies though!
modifying boot.img with magisk also results in invalid sprd imgversion, so no root or disabled verity through this route
I didn't manage to read back from flash through SPD ResearchDownload, I get the error "incompatible partition" for userdata - and I can't deselect it :/
(I thought it might be possible to get the sprd imgversion magic throught this route
Partial success​I managed to boot a GSI by signed by google through Dynamic System Updates (DSU).
It kind of looks like it's running in emulation though: settings say "About emulated device" and it gets an own userdata.img
the DSU page also says it will only run GSIs signed by google or the vendor (not sure which key that would be, but I doubt there are any) - I haven't tried flashing anything this route
Open Ends:​reverse engineering the imgversion thing​It should be possible to figure out how this imgversion business works, ultimatively from the u-boot.img / PAC content. Anyone has any idea how to proceed there? I tried:
binwalk: doesn't look useful to me, nothing got extracted -> here
arm-none-eabi-objdump -b binary -D u-boot-sign.bin -m armv8-a -Mforce-thumb
(also without -Mforce-thumb and with -m armv7)
I'm pretty sure it's actually U-boot: there is the U-boot version string matching the one printed to uart and also the printf-string for the imgversion
requested U-boot source code from Cubot​I requested source for all GPL'ed parts of the Pocket from Cubot, but especially U-Boot and the kernel. I'd be a pleasantly surprised if something comes out of this though
reading back the flash​Does anyone have an idea how to do that? without root no access to /dev/block/mmcblk* and I didn't get SPD ResearchDownload to read it.

It's nice that you could unlock the bootloader! I'll try to do it soon (maybe in some months, but ok lol)
Anyway, which GSI did you try? And about the vbmeta, I think it should be enough to flash the blank vbmeta.img from google. Maybe we could use the original vbmeta.img from stock ROM with the --disable-xxxxx flags.
This is the tutorial from phhusson's group (the man behind the treble project):
0. Get an up-to-date fastboot on your computer (fastboot —version should give version >= 29)
1. Get vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
2. Get A/B GSI (I'm guessing you need ARM64), don't forget to uncompress it
3. From running Android, do adb reboot bootloader
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. fastboot reboot fastboot
6. fastboot flash system system-xxxx.img
6bis. If fastboot tells you there isn't enough place, do fastboot delete-logical-partition product, fastboot delete-logical-partition product_a, fastboot delete-logical-partition product_b and run the fastboot flash command again
7. On your phone, the screen should have a button "go back to recovery", select it, then select "factory reset / wipe data"
8. Reboot and enjoy

Thanks for your work. I got my Cubot Pocket unlocked too. I have booted LineageOS 19 via DSU Sideloader. It runs like a charm but there is no way to flash the GSI permanent.

@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?

wori said:
@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?
Click to expand...
Click to collapse
I tried it. My Navigation Bar is showing and working normal.
Automatic Display Brightness is working too.
I dont use gestures, but if you tell me how to do it, i will check that too.
Image: lineage-19.1-20220719-UNOFFICIAL-arm64_bvS.img.xz
and DSU-Sideloader 1.03 from Github. Default Settings

thanks for trying!
You can change it in Settings->System->Navigation->System Navigation->check Gesture Navigation
So: interesting that you got a lineage build working, maybe that's the important difference! From google's doc I understand that there's some verifcation, but looks like it's not. Since I actually don't want the google build, I'll try with lineage next. Did you also try with the built-in DSU way, like described in googles doc?

wori said:
Did you also try with the built-in DSU way, like described in googles doc?
Click to expand...
Click to collapse
As I understood, the app is doing exactly the same like the Google Doc say. It seems like unlocking the Bootloader is enough to boot a custom-DSU.I have read something about signed Images that will boot without unlocking the Bootloader, but i didnt try it. I just want to get rid of all the Google-Stuff before using the Pocket Hope we can get it working.
btw: Gestures seem to work. swipe from right to middle closes Apps. from middle to up opens Menue

After a Weekend of fails i flashed Lineage 19 to my old KingKong mini and its working on the first try. Problem seems to be the Unisoc T310. The success-rate of flashing GSI to T310 seems to be really low. Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?

changer86 said:
Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
Click to expand...
Click to collapse
GSI on Unisoc device
My tablet is unisoc t310 T803 with oem android 11 here is were im stuck I reflashed oem super.img and the system booted fine so i can start fresh i erased product and system, and flashed lineage 17.1
www.hovatek.com
seems this guy has succeeded and his device looks pretty similar to pocket in treble info
im unisoc tablet has oem stock A11 and no GSI A10 was to boot. my oem system is system as root AB arm64. so I have no choice but to use Arm64 AB GSI A11 because A10 will not boot
Click to expand...
Click to collapse

Hi, can you help me with this situation? I can't unlock bootloader on cubot pocket.
I tried to unlock on my ubuntu and windows devices.
FAILEN ( Flashing Lock Flag is locked. Please unlock it first)
I don't know that I will do for this problem
Spoiler: image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@raary did you enable OEM unlocking in the Android settings?

wori said:
@raary did you enable OEM unlocking in the Android settings?
Click to expand...
Click to collapse
Yes of course

raary said:
Yes of course
Click to expand...
Click to collapse
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.

changer86 said:
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
Click to expand...
Click to collapse
Thank you, I will be try to unlock

@wori any updates on flashing gsi?

@badcodelab not from my side. I got frustrated and also had some other things to do. Hopefully find some time + energy to continue working on this.

I can't stay in stock OS, my GSI on cubot pocket have only 16 Gb via DSU sideload less for me, correct custom not exist for this, sad

@wori, @changer86 i didn't get clear from your posts if you tried to use signed vbmeta from the stock rom
also i haven't manage to make research tool to unpack boot.img nor super.img
by some reasons they stay listed as zero-sized .flag files in the target folder

xT2213-1 (Austin) Moto G 5G 2022, S1SAS32.47-59-3

Any custom roms like lineage for this device? This is not kiev.

Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months

Fytdyh said:
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
Click to expand...
Click to collapse
I tried using a stock firmware and patched magisk but when I booted up the phone I got this

gr3uh said:
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked. .
Click to expand...
Click to collapse
I think I used the wrong firmware possibly

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
Click to expand...
Click to collapse
Makes no sense since I was perfectly able to unlock the bootloader using Motorola's official guide.

I recommend posting your questions here :
https://forum.xda-developers.com/t/...noob-friendly.2257421/page-2453#post-87357675
Do say what you did, what you flashed. Everyone can help you faster if you are concise and say what did you flash or did to that device. Whenever you try something, write it down.

mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it

Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!

3×5 said:
Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!
Click to expand...
Click to collapse
I've been told there will never be any progress on custom roms and firmware for this device since it is mediatek and mediatek is locked down their binaries making it hard for people to make custom rom. That being said you can try porting your own twrp or flashing a GSI.

KParsons0697 said:
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
Click to expand...
Click to collapse
My phone I bought it from a carrier and it was locked until payed off, paid it and waited a few days and it worked. Rooting this device was easy, just wish rom development would come sometime. I hear android 13 should be coming to this device around the beginning of Q2 of 2023

@gr3uh, thanks for the reply. I could try a GSI, but really my goal is to have an open-as-possible, de-Googled phone. I don't even really care about MicroG, or any of this. Even with no services at all, I can use Google Maps in a browser.
I assume if I install the stock firmware from lolinet, it'll have all the Google Play services. Will the phone also be rooter at that point? Or do I have to also root the phone, and then manually remove all the play services?
The big picture question is this: what's the simplest route to me De-Googling this phone?
Bonus question: why is the stock firmware hosted on a site called 'lolinet'? Maybe I don't want to know...

Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.

I should also point out that when I boot into fastbootd on the phone, it says 'Secure boot - yes' even though I flashed that empty vbmeta image and got:
Code:
target reported max download size of 268435456 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.000s]
writing 'vbmeta_b'...
OKAY [ 0.073s]
finished. total time: 0.074s

3×5 said:
Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
Click to expand...
Click to collapse
There should be a batch file in the zip you can use to flash the dynamic partition covers everything just edit it to fit your need. And run as betch

Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)

3×5 said:
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
Click to expand...
Click to collapse
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Thanks for the clarification. Unfortunately, my image is just an img.xz file. There's no .bat script and no zip.
I ran fastboot getvar current-slot and it says 'current-slot: b'. Then I ran fastboot flash system_b imagefile.img.xz and I got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165282916 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
OKAY [ 9.401s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
finished. total time: 14.558s
So basically the same problem as before. I tried running 'fastboot delete-logical-partition product_b' and got:
Code:
fastboot: usage: unknown command delete-logical-partition
I could try 'fastboot flash super imagefile.img.xz' but I don't know if I'm supposed to delete super first, and I don't want to make things worse. So any advice would be appreciated.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Alright, I was able to flash the GSI ROM, but it didn't work. My phone thinks the OS is corrupted. I think my only choice now is to go back to my stock ROM. I tried to flash the super partition but running
Code:
./fastboot flash super ../super.img_sparsechunk.0
and it did this through sparsechunk 26. Then I rebooted and I still have no OS.
Now this stock ROM does not have a .bat file, but it does have flashfile.xml. Is there any way I can use this to automate the flashing process? At this point, I'm thinking I'm going to have to flash every partition.
Related question: In the flashfile, it specifies partitions as logo_a, vbmeta_system_a, etc. But when I run '
fastboot getvar current-slot' it says my current slot is 'b'. So should I replace every instance of _a with _b?