Has any one been able to successfully install a treble compatible rom?
I tried pushing the system image but having issues with the commands with adb. The newer ab slot confuses me a bit.
Would be interesting to see how the phone works.
Any help would be appreciated.
Have you had any success yet?
I've tried with no success.
I've flashed google's android 11 gsi, and https://github.com/phhusson/treble_experimentations/releases/ v300 system via fastbootd, but cannot get them to boot past the android loading screen.
I think the issue is that for some reason on the Duo, vbmeta cannot be flashed from fastboot or fastbootd, so you cannot disable AVB, which then won't allow any GSI to boot.
simondyno said:
I've tried with no success.
I've flashed google's android 11 gsi, and https://github.com/phhusson/treble_experimentations/releases/ v300 system via fastbootd, but cannot get them to boot past the android loading screen.
I think the issue is that for some reason on the Duo, vbmeta cannot be flashed from fastboot or fastbootd, so you cannot disable AVB, which then won't allow any GSI to boot.
Click to expand...
Click to collapse
If there is no vbmeta, then it probably needs to be included in the boot image. There is a python script available for AOSP to append the vbmeta or an empty vbmeta to a boot image. I believe it is called avbtool.py
Related
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
DragonPitbull said:
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
Click to expand...
Click to collapse
Cool This helps already a lot.
i unlocked the Bootloader properly, but then i got a partition error. I assume i´ve an error in the command line. The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
beinfo said:
The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
Click to expand...
Click to collapse
Try but REMENBER I am not responsible for any errors. Bootloader should unlocked by adb-fastboot!!
Spoiler: Instructions
1. You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options: reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
2. Device in fastboot
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
vbmeta file from stock ROM or pulled from device
3.
Code:
fastboot -w
4.
Code:
fastboot reboot fastboot
(you MUST be at the FASTBOOTD menu now. If not, you will not be able to flash the GSI successfully)
5.
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
6.
Code:
fastboot delete-logical-partition product
- deletes the product partition, allowing a larger system partition
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
6A. fastboot resize-logical-partition product 509344768
6B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
7.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
8.
Code:
fastboot -w
for confirm great & fast start GSI
9.
Code:
fastboot reboot bootloader
9A.
Code:
fastboot erase userdata
for confirm and boot clean
10. Reboot to system
Code:
fastboot reboot
Enjoy
I also have an N20 Pro which I received Dec 2020. Had some trouble setting it up. I got the OEM ROM from Doogee customer support and was able to extract the boot image and patch it with Magisk. I then burned it with the SP Flash tool. It wouldn't boot until I burned a special vbmeta.img to turn off encryption. Now it's working fine.
Sorry this doesn't help you with TWRP but I think most people looking for TWRP are really looking to root their phone.
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
Okay so what ive seen is that you should avoid flashing custom roms via adb fastboot especially with our doogee phones, and also there are many incompatiable roms so what you will need is to unlock bootloader and do the whole twrp install thing adn also install magisk
before hand install treble info from google playstore and take down the information "arm64 a/b" and search for roms with that information to install custom os/rom/gsi properly. GSI versions are more preferred if your phone supports treblle
if your twrp keeps getting wiped after reboot open file :mount your system and connect to pc via usbcable (mtp if not showing disable mtp and re- enable it )
now got to where build.prop is saved there will be a file called recovery from boot.p , copy the file to pc , open with notepad, remove everything , save and copy back to phone (overwrite)
then go ahead and install magisk
make sure your magisk is working install edxposed, riru core , and busybox ndk get the apps you need for them (edxposed manager...) and then instal and activate a module which you can test if its working(if framework is active in edxposed manager and the module working correctly then you can go ahead and
Install custom os through twrp
follow these instructions ( https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/ ) with your custom rom (corvus, havoc, lineage...
(the g-apps didnt flash for me (error code 64) but i just rebooted and everything was working fine (including gapps but camera sucked (doogee's rear camera setup was just terrible))
https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/
** i can confirm follow instructions properly and it should work (i used this pixel experience on my doogee n20 make sure you unzip the .xz file and youre flashing a .img file
**also make sure its the gsi file (
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
prashanth_ said:
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
Click to expand...
Click to collapse
I have miui 12 how to root?
Ameer9963 said:
I have miui 12 how to root?
Click to expand...
Click to collapse
Which guide have you followed?
prashanth_ said:
Which guide have you followed?
Click to expand...
Click to collapse
I have followed miui 11 guide
But i have miui 12
Ameer9963 said:
I have followed miui 11 guide
But i have miui 12
Click to expand...
Click to collapse
Plz post how to patch boot image
Magist patched boot image not working to root
So i wanted to install custom rom on my redmi 8a, installed TWRP and wiped the system without installing the rom, now my phone is stuck in the fastboot mode because i don't have system to load, also can't access the TWRP and file system from the pc. How can i flash MIUI? Tried with Mi Flash Tool, got an error "missmatching image and device". I tried downloading several different roms and also from official website, but still didn't succeed in flashing and every time get this exact error.
SOLVED! flashed patched vbmeta through fastboot and can open TWRP now
Hi.
So, I'm exactly in the same situation. For a moment there I thought I perma-bricked my phone...
Anyway, can you tell me more about how you solved it?
Where did you get the patched vbmeta file?
How can I flash it? Is it just a simple fastboot flash <partition> <file> command?
Anything else I need besides the vbmeta file?
Thanks in advance.
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog:
• Updated sources to latest
• Almost Everything working fine.
Only for MIUI 13 Android 11
Creator: @Aghora7
Download
Installation instructions
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
lurchiii said:
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
Click to expand...
Click to collapse
I can't answer to this question, because it depends on you made any mistakes during the installation or not
Its support for A12 miui 13.0.4
Does it support A12 eea europe rom ?
xristos1925 said:
Does it support A12 eea europe rom ?
Click to expand...
Click to collapse
it supports a11
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
sanjibukai said:
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
Click to expand...
Click to collapse
Once you have lineageos installed, you must to flash twrp via fastboot and then flash Gapps
1. Flash system ( when it's done, don't reboot phone, just flash twrp
2. If you already are on twrp flash your Google apps
3. When you're done with flashing gapps, restart phone to system (twrp will be gone after reboot)
4. You have installed Gapps
i don't know how to flash twrp permanently, if you want further informations about this recovery, then join fleur telegram development channel
BloxetPL said:
1. Flash system ( when it's done, don't reboot phone, just flash twrp
Click to expand...
Click to collapse
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
sanjibukai said:
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
Click to expand...
Click to collapse
Remove "fastboot reboot recovery" from SMINORI tool and instead of this type "fastboot flash boot twrp.img
fastboot boot twrp.img"
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
globalfandemic said:
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
Click to expand...
Click to collapse
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
BloxetPL said:
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
Click to expand...
Click to collapse
Already tried, still same issue.
Tried using a couple new commands too with no result:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
fastboot reboot recovery
Also tried using only the commands you gave:
fastboot flash boot twrp.img
fastboot reboot recovery