Related
Hey,
here is the prerooted + recovery TWRP flashable zip of Android Marshmallow for the D6603 Xperia Z3!
Downloaded with newest Version of XperiFirm than extracted by flashtool and created the tft with the right excluded files.
Zip created by a own compiled build of PRF Creator.
It includes RecRootV3 Forum Link
So it has these feautures:
-New TWRP 3.0.2 Recovery from shoey63
-ByeSELinux
-RIC Defeat
-Fixed sqsh mount in Script
-Updated Busybox
-SuperSU 2.71 in System Mode
Click to expand...
Click to collapse
How to:
1. Boot in Recovery
2. Make a "Factory Reset"
3. Install zip downloaded here
4. Wipe Cache + Dalvik Cache
5. Restart
Download:
Part1
Part2
Have Fun!
Credits:
Wolfbreak for RecRootV3
Hi, thanks for your work, :good:
Why 2 part,
One part and mega link please,
blameSTART said:
created the tft with the right excluded files.
Click to expand...
Click to collapse
What is means? Which files are excluded? Can you share, please.
Gladyator23 said:
Hi, thanks for your work, :good:
Why 2 part,
One part and mega link please,
Click to expand...
Click to collapse
No Problem
2 Parts because free users can download it 2
I upload it there because i have a uploaded account and not a mega account ^^
artlov said:
What is means? Which files are excluded? Can you share, please.
Click to expand...
Click to collapse
I excluded the loader.sin and the *.ta files, they are not necessary.
Hi. Thanks for the flashable ZIP.
I've flashed it, but now I have no root and no recovery...
Is there a way to fix this?
Update: after few tries of updating the SU Binary and phone resets root started to work (still Binary is not up to date - "#" is being displayed over time)
How should I reinstall TWRP 3.0.2? There is no version for D6603...
doogie333 said:
Hi. Thanks for the flashable ZIP.
I've flashed it, but now I have no root and no recovery...
Is there a way to fix this?
Click to expand...
Click to collapse
Hi,
From my experience: No. You have to return to LP and to start over again with rooting etc.
On my personal device (D6603) none of the prerooted ROMs since the first LP variants provided here keeps Root and Recocery. Don't know why... I helped myself always with flashing:
1) ROM
2) SuperSU
3) Recovery
4) xPosed
over again one directly after the other. Of course you will need a rooted ROM with recovery for this, but it's much easier to get with older ROMs.
I think same will be here: Get the ROM, get Wolfbreak's RecRoot. Then flash both from a recovery one after the other, clear cache and Dalvik cache and reboot. That's it...
Cheers
Zap
Did you used a dummy file instead of SuperSu.zip? Wolfbreaks RecRoot has SuperSu built in...
http://forum.xda-developers.com/showthread.php?p=66569775
Sent from my Z3 Monster using XDA Free mobile app
I flashed exaclty this rom to my phone and i got root + Recovery.
It should work :/
Please upload it somewhere else where I don't have to wait 6 hours for downloading. And what is the difference between these two parts?
Flockrock said:
Please upload it somewhere else where I don't have to wait 6 hours for downloading. And what is the difference between these two parts?
Click to expand...
Click to collapse
Just download these 2 parts and you can unpack it with for example winrar
Deleted
post deleted
Hello, guys. Today i'm compiling the latest twrp.img using official omnirom 8.0 & Lineage 14.1 source code.
Seems all works as it should. Enjoy.
Need:
* unlocked bootloader
* latest official firmware .291
How-to:
* download recovery.img
* turn off your phone and flash recovery
Code:
fastboot flash recovery name_of_recovery.img
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
Thanks:
* @nailyk for decryption
UPDATE_09.03.2017:
* new version 3.1.0-0
UPDATE_13.05.2017
* new version 3.1.1-0
UPDATE_03.12.2017
* new version 3.2.0-0
UPDATE_09.12.2017
* new version 3.2.1-0
UPDATE_14.12.2017
* added omni's version
Download Lineage 14.1 recovery:
HERE
Download Omni 8.0 recovery
HERE
Well done... Did you test also *.img flash?
I had some issues with 3.0.2.1 for aries. This gave me error messages (sorry cannot remember which in particular)
But 3.0.2.0 works as usual.
EDIT
* press vol-down + power, when phone vibrate, unpress only power button. See logo 'Sony' unpress vol-down button.
For me its just enough to release them both quite quickly after it vibrates...
Is it work only for android n? Or including android M? And is it fota recovery?
fluffi444 said:
Well done... Did you test also *.img flash?
Click to expand...
Click to collapse
What img files are you mean?
Recovery can flash only boot and recovery imgs
dddestiny said:
Is it work only for android n? Or including android M? And is it fota recovery?
Click to expand...
Click to collapse
It's work on Android M and yes, this is fota recovery
russel5 said:
What img files are you mean?
Recovery can flash only boot and recovery imgs
Click to expand...
Click to collapse
boot.img made problems. But I am going to test it for myself. No problem.
fluffi444 said:
boot.img made problems. But I am going to test it for myself. No problem.
Click to expand...
Click to collapse
OK - Looks like that it works!
But still one question left: In Backup CACHE is showing only with (0MB)
I know that backing up cache seams to be useless but sometimes its still usefull. In old TWRP 3.0.2.0 is shows mostly (4MB).
If I backup CACHE with 3.0.3.0 its give me the output 0MB saved.
Has it some thing to do with the arguments of CACHE in recovery.fstab?
Code:
noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic wait,check,formattable
This is the old from 3.0.2.0 (not yet tried to change that in 3.0.3.0)
Code:
nosuid,nodev wait
EDIT
And finally USB-OTG is working! Cool!!!
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
russel5 said:
@fluffi444 bro, twrp not using recovery.fstab, it's using twrp.fstab
and what size of your cache folder when your phone is booting up? my is only 40kb that's all.
Click to expand...
Click to collapse
OK - feel a bit dumb now ...
I have 4,08 MB (an 192,53 MB free) - that is what Solid Explorer gives me...
EDIT
I put now an 4,5 MB file to CACHE folder - An now it shows me (5 MB) in recovery
EDIT2
I check again single folders and files in CACHE folder - They have only 22,47 KB in total...(without my manual copied file)
I guess we can close this discussion Thanks again for your work and your help!
I guess they changed the way of correct recognition of the free space.
I installed this recovery in my Z3C running the AOSP 7.1.1 ROM, but, as soon as I turned my phone on afterwards, my SD card was accused to be corrupted. As soon as I went back to TWRP v3.0.2-0, everything went back to normal. It's a 512 GB card, if it matters.
Sent from my Sony D5833 using XDA Labs
casouzaj said:
I installed this recovery
Click to expand...
Click to collapse
Can you post the recovery log to see what happend?
russel5 said:
Can you post the recovery log to see what happend?
Click to expand...
Click to collapse
Nevermind! I flashed it again in order to grab the log, but the issue simply didn't happen. Don't know what caused it the first time I flashed it. I'm keeping it this way. Thanks, anyway!
Sent from my Sony D5833 using XDA Labs
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
How to flash the recovery on concept 3657? when I flash the recovery, it hints "partition table doesn't exist"
panzerox123 said:
@russel5 Im guessing this is not official, but im a little bit confused? What is that build.prop you have attached in the OP?
EDIT: Btw great work man!
Click to expand...
Click to collapse
What do you mean, not official? Build.prop generated when you compiled something from sources.
Sent from my Sony D5803 using XDA Labs
russel5 said:
What do you mean, not official? Build.prop generated when you compiled something from sources.
Click to expand...
Click to collapse
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
panzerox123 said:
By not official, I meant it's not on the twrp page yet ...
I was confused because build.prop says omni_aries
Click to expand...
Click to collapse
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
russel5 said:
It's not on twrp page because i need to write email and send this to omniteam, don't want.
And aries mean z3c, like sirius z2 and other. Omni used aosp names in devices tree, like this https://github.com/sonyxperiadev/device-sony-aries
Click to expand...
Click to collapse
I understand. So is this more stable than 3.0.2-1?
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
russel5 said:
There are so many peoples on my home forum had problems with this version 2-1.
This thread created for you, guys. You can tell me - stable this new version or not
For me all works like it should. Tested on unlocked bootloader and locked.
Click to expand...
Click to collapse
Full stable for me. Thanks again for your work.
anyone tried flashing this on carbon rom?
HI ALL! With new Rom
VertexOS aims to provide a simple but enhanced near-stock AOSP experience with carefully selected features and an emphasis on stability and smoothness.
what doesn't work ?
everything is working perfectly.
Coming from another ROM, OR if a CLEAN FLASH is required
1) Download the Vertex... .zip file.
2) Download a 7.1 GApps package.
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash the Vertex... .zip file
6) Flash Nougat-compatible GApps : http://opengapps.org/ / ARM64,7.1,pico
7) Reboot
Download:https://www.androidfilehost.com/?fid=745425885120707303
enjoy!
Credits:
- LineageOS
- AOSPA
- Citrus-CAF
- DU
- PureNexus
- Zephyr-OS
IF YOU LIKE MY WORK PLEASE HIT THANKS .
-IMPORTANT- : To install this rom you must have installed TWRP-3.0.3.0 , download from here https://www.androidfilehost.com/?fid=529152257862697990
To easy install from TWRP recovery :
1- open "install" section.
2- SELECT "install img" in the bottom .
4- Chose the place of TWRP-3.0.3.0.
5- install as RECOVERY , then reboot to recovery.
XDA:DevDB Information
ROM [AOSP + LOS], ROM for the Wileyfox Storm
Contributors
PS-DEV
Source Code: https://github.com/VertexOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP + LOS
Version Information
Status: Stable
Created 2017-02-11
Last Updated 2017-02-20
Received
Received !
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Cannot inatall gapps (Wrong Architecture)
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
I installed fine with the nano apps and 64 bit, no issues
miSAKe said:
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Click to expand...
Click to collapse
Check the first post . i have been edit.
Chron0s said:
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Click to expand...
Click to collapse
show your PM.
Chron0s said:
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
Click to expand...
Click to collapse
NO NO
ARM64 ARMv8 .
ChuckeCheese said:
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Click to expand...
Click to collapse
1- check to wipe this partitions :
- SYSTEM
- CACHE
- Dalvick-cache.
- DATA
and dont forget to factory reset .
2- first install rom then Gapps. download from here http://bit.ly/2kQf3Le
PS-DEV said:
Check the first post . i have been edit.
Click to expand...
Click to collapse
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
miSAKe said:
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
Click to expand...
Click to collapse
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
PS-DEV said:
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
Click to expand...
Click to collapse
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
miSAKe said:
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
Click to expand...
Click to collapse
The phone boot to rom or not ??
PS-DEV said:
The phone boot to rom or not ??
Click to expand...
Click to collapse
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
miSAKe said:
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
Click to expand...
Click to collapse
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
PS-DEV said:
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
Click to expand...
Click to collapse
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
miSAKe said:
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
Click to expand...
Click to collapse
Stock firmware or what? ,, to install version 13 Bootloader , just install any nightly cm13 then back to recovery and install TWRP 3.0.3.0 ??.
Create a vendor partition for cancro to flash a PT GSI IMAGE
This guide only suitable for MI4LTE and MI3W.
MI3TD don‘t support this method and ROM.
First we must thanks to the MkfsSion for his PT works on our MI4LTE.
https://github.com/MkfsSion/android_device_xiaomi_cancro
And thanks to the cjybyjk for his automatic treblizer tools.
https://github.com/cjybyjk/cancro_treblizer
Warning: this operation is highly experimental and may result in a serious risk of irreversibility
Method 1 With cjybyjk's cancro_treblizer.(Recommend this method now)
1.Let MI4LTE to fastboot mode.
We can press Volume - and Power button to let it into fastboot mode.
2.Let flash the TWRP which support ProjectTreble.
We can use the command [fastboot flash recovery x.img]
Recovery:https://drive.google.com/file/d/1Fc0SK_xYdmkFi5CzR4Vq8QLqQFQ1ikWk/view?usp=sharing
3.Let reboot into the TWRP and flash the cancro_treblizer.zip in TWRP and reboot into the TWRP again when finished.
https://drive.google.com/file/d/14EkMX9VKiC3kbELwtBkxmAYupCmCxPf5/view?usp=sharing
4.Mount the Cache System and Vendor partition and Wipe this 3 partitions.
5.Then we can flash the zip rom from the AFH below.
https://www.androidfilehost.com/?fid=11410932744536984188
6.If you flash the pie gsi arm rom and you must flash this omx-disable patch to fix the boot for pie.
https://drive.google.com/file/d/19TUZiX0vHxIlc9f_6wF2uySI8HcW7xqy/view?usp=sharing
7.Now you can use the nice ProjectTreble ROM on our MI4LTE!
Method 2 With 9008 mode and Diskgenius.(Not recommend now)
1.Let MI4LTE to fastboot mode.
We can press Volume - and Power button to let it into fastboot mode.
2.Let MI4LTE to disk mode(9008 mode).
Open the "磁盘模式工具.rar" ,Unzip it and double click the "清除fastboot进磁盘操作.bat" when MI4LTE go to black screen it was succeeded into disk mode.
Disk Mode Tools:https://drive.google.com/file/d/12uFsjwB_t_XzBWz0aeVJue5zdPiPCc7c/view?usp=sharing
3.Download the DiskGenius Software from the website:
http://www.diskgenius.com/
4.Open the DiskGenius and you will find all the MI4LTE partition in it and we need to restore aboot partition.
aboot partition file:https://drive.google.com/file/d/1aYikwwQQdAsa_XM7cKqv2f49aYAMNybu/view?usp=sharing
5.Then we need to restore ProjectTreble partition table.(For 16GB Version Only)
ProjectTreble partition table file:https://drive.google.com/file/d/1Zg_htr9tSfUHqr04pdxlCyn_qANnwJlM/view?usp=sharing
6.Then we can reboot the MI4LTE into the fastboot mode again and flash the TWRP which support ProjectTreble.
We can use the command fastboot flash recovery x.img
Recovery:https://drive.google.com/file/d/1Y-67W1MfMchny6ljCxKpU1_vq-PdLkpV/view?usp=sharing
7.Press Volume + and Power button to go into the TWRP.
8.Mount the Cache System and Vendor partition and Wipe this 3 partitions.
9.Then we can flash the zip rom from the AFH below.
https://androidfilehost.com/?fid=3700668719832236822
10.Now you can use the nice ProjectTreble ROM on our MI4LTE!
Now our MI4LTE is not ARM64 device so we can only flash A-Only and ARM GSI IMAGE.
Update 2018-08-21
Phh have just released the Android 9.0 GSI IMAGE have include ARM and ARM64 so our cancro can flash Android 9.0 GSI IMAGE for experience.
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
Update 2018-10-20
Fix App FC
Fix OMX
Fix GPS
Noteie PT GSI may need extra patch when you flash the pie gsi image with this pt package.
Cancro Rom Group
Group rules:
1.English only.(You can use the translator to communicate.)
2.Respect developers and administrators.
3. Please do not send spam.
4. Do not send stickers continuously.
Channel: @cancrorom
CN Group: @cancrogroup
https://t.me/micancro
前排支持
Supported ahead.
wow nice treble for our cancro,
is internal storage formatted or not?
Thanks for new thread.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.8.8.
Shiroyasha21 said:
wow nice treble for our cancro,
is internal storage formatted or not?
Click to expand...
Click to collapse
It's no problem to wipe internal storage but when you wipe this you must reboot into Recovery again to copy zip rom to internal storage.
Changed files to Google Driver instead of BaiduYun Disk.
Mi3 not supported(
酷安基佬前来支持:laugh:
酷安基佬来一波??
Sent from my Essential Products PH-1 using XDA Labs
酷安前来支持！
Come from Coolapk.
Supported ahead( 前排吃瓜）
Guy from Coolapk
请问恢复Treble分区那一步，具体是哪个分区？之前没弄Treble，网上搜了一下好像也没有Treble的包，那个GitHub项目好像并不是个可刷的包。抱歉不是太懂，不好意思
All of you, please use English.
Also please tell whether Mi 3 will be supported in future or not?
Thanks.
ptg251294 said:
All of you, please use English.
Also please tell whether Mi 3 will be supported in future or not?
Thanks.
Click to expand...
Click to collapse
Mi3 TD Pisces (old Tegra CPU phone) not supported.
Mi3 W Cancro I've tried a minutes ago, and removing aboot, repartitioning, install new trebled twrp, and install LOS completed successfully @gujiangjiang
小米MIX标准版4GB128GB银色MIUI10中国开发者8.8.8.
JulianJenner said:
Mi3 TD Pisces (old Tegra CPU phone) not supported.
Mi3 W Cancro I've tried a minutes ago, and removing aboot, repartitioning, install new trebled twrp, and install LOS completed successfully @gujiangjiang
小米MIX标准版4GB128GB银色MIUI10中国开发者8.8.8.
Click to expand...
Click to collapse
Thanks for your testing.
Have you guys only tried Lineage? Every GSI rom should work, right?
mdki1996 said:
Have you guys only tried Lineage? Every GSI rom should work, right?
Click to expand...
Click to collapse
I also tried AOSP GSI and works fine yet.
When you flashed PT successed and you can flash the all the GSI IMAGE by your self.
Now the Android P ProjectTreble image have not released yet so we can use aosp,aex,Los first to use now and wait the p image release by phh and if phh released the image for arm then we can easily flash it with PT.
Here are the rom lists for arm32 pt devices and you can try these pt rom now.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
https://forum.xda-developers.com/pr...evice-development/rom-carbonrom-noct-t3821947
https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
https://forum.xda-developers.com/pr...official-treble-enabled-resurrection-t3761279
https://drive.google.com/folderview?id=1SsPuw3ZtTvoslJyqwSJsmDQ42qvJvYVN
Here is the guide to teach how to flash gsi image with pt support.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
NOTE:
PLEASE FLASH ARM OR ARM32 GSI IMAGE NOT ARM64.
gujiangjiang said:
I also tried AOSP GSI and works fine yet.
When you flashed PT successed and you can flash the all the GSI IMAGE by your self.
Now the Android P ProjectTreble image have not released yet so we can use aosp,aex,Los first to use now and wait the p image release by phh and if phh released the image for arm then we can easily flash it with PT.
Here are the rom lists for arm32 pt devices and you can try these pt rom now.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
https://forum.xda-developers.com/pr...device-development/rom-aosp-extended-t3821934
https://forum.xda-developers.com/pr...evice-development/rom-carbonrom-noct-t3821947
https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
https://forum.xda-developers.com/pr...official-treble-enabled-resurrection-t3761279
https://drive.google.com/folderview?id=1SsPuw3ZtTvoslJyqwSJsmDQ42qvJvYVN
Here is the guide to teach how to flash gsi image with pt support.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
NOTE:
PLEASE FLASH ARM OR ARM32 GSI IMAGE NOT ARM64.
Click to expand...
Click to collapse
i try other GSI image,Aospe extended,DU,Aosp 8.1, but doesn't boot.reboot phone going fastboot mode
Haggiskop said:
i try other GSI image,Aospe extended,DU,Aosp 8.1, but doesn't boot.reboot phone going fastboot mode
Click to expand...
Click to collapse
I tried without problem.
Please confirm you have flash the pt support.
Then please confirm you download the right arm GAO image and use image flash method flash it not zip rom.
从我的 iPhone 发送，使用 Tapatalk
gujiangjiang said:
I tried without problem.
Please confirm you have flash the pt support.
Then please confirm you download the right arm GAO image and use image flash method flash it not zip rom.
从我的 iPhone 发送，使用 Tapatalk
Click to expand...
Click to collapse
i flash with twrp and without twrp fastboot mode but doesnt boot.arm a only version.lineage 15.1 cancro.zip
work only.
Stock Android 10 Fastboot Rom Project
How i made is using payload dumper to unpack payload.bin file inside recovery rom and editing flashing scripts to be usable for this unpacked files.
Requirements
ADB must be installed on PC (Click to ADB to download if you dont have it)
Unlocked Bootloader( fastboot flashing unlock + fastboot flashing unlock_critical )
Steps to install
> Unzip zip file into desktop and open the folder.
> Then run flash_all.bat file and it will install the new update and reboot to system automatically.
(Your files will not be erased if you already unlocked bootloader.)
Latest - v11.0.11.0 - Global - April Security Patch
Recommended Server : Quebec, Canada
DO NOT MIRROR THE DOWNLOAD LINKS BEFORE ASKING ME !
AndroidFileHost - v11.0.11.0 April Security Patch
AndroidFileHost - All Versions
If you want to lock your bootloader after installing it , you can use flash_all_lock.bat OR i prefer to lock it manually by doing this;
Run flash_all.bat and make sure phone boots after installing then open fastboot mode and type
fastboot flashing lock_critical
Then phone will restart automatically into recovery and wipe data.
After screen goes black hold power + volume down button (to open fastboot again) then type
fastboot flashing lock
And after booting you can disable OEM unlock from developer options if you want to.
XDA:DevDB Information
[Fastboot ROM] Android 10 Update , ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-03-19
Last Updated 2020-04-07
XDA:DevDB Information
[Fastboot ROM] Stock Android 10, ROM for the Xiaomi Mi A3
Contributors
TechGenius
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Version Information
Status: Stable
Current Stable Version: 11.0.11.0
Stable Release Date: 2020-04-07
Created 2020-04-07
Last Updated 2020-04-07
@TechGenius
thanks man
i updated my phone via ota rom
would you please put boot.img of this rom , it does not exist in ota file !
really good job bro thanks again
Is this possible on build with Magisk without twrp
Thanks dude!
Would your script flash on both slots A & B?
i does not go further than sending modem_b.
what can i do?
C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0>fastboot flash modem_b "C:\Users\MingBee\Downloads\laurel_sprout_global_images_V11.0.11.0.QFQMIXM_10.0\images\modem.img" ||
Sending 'modem_b' (114084 KB)
Click to expand...
Click to collapse
Hi! Does it would update 11.0.7.0 with root and TWRP, without losing the data?
Thank you!!
any one that downloaded this rom please upload boot.img
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
https://forum.xda-developers.com/sho...&postcount=340
PS
@TechGenius thanks for making Fastboot ROM for April build. You are truly a genius.
moyses said:
Is this possible on build with Magisk without twrp
Click to expand...
Click to collapse
#MmdRza said:
any one that downloaded this rom please upload boot.img
Click to expand...
Click to collapse
Have a look at THIS POST, you'll find the original boot and the pre-rooted one
HERE is the how-to guide and a list of original boots.
fuqi said:
i does not go further than sending modem_b.
what can i do?
Click to expand...
Click to collapse
did you solved?
Just installed using a notebook with windows 10 64Bit (i had issue with 32bit laptop)
Everything is fine but still receive the notification of android 10 update to install
i used a .bit file from a different release and it worked.
no update nag for me.
hi , at first thanks for your work!
2nd question: anibody have issues installing twrp? i' m stuck on fastboot everytime i try to install it.
Same issue here.
phillow said:
Same issue here.
Click to expand...
Click to collapse
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Is this the one that got pulled off?
Therion8594 said:
i try to install the patched boot image in the previous page for having root with magisk, give it a try :good:
Click to expand...
Click to collapse
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Masleyko said:
Have you tried it ? I flashed 11.0.11.0 fastboot A10 on girls Mi A3 .. and rooted it without TWRP using magisk 20.4 and im facing reboot to fastboot issue instead to recovery after trying any possible custom recovery there is for this phone..
Click to expand...
Click to collapse
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Therion8594 said:
Yes i don't know why but every recovery i've tried It go go fastboot..flash the boot image in the previous Page and everything work .
Click to expand...
Click to collapse
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
garylawwd said:
Because the twrp .IMG file was built only for pie. For Android 10 you will have to use this https://mega.nz/file/1HRAWYKQ#V9OmPxSy3r06qmW8uGszSEBp4qOBJMbmvsaCow2mTJw
Once it is flashed you can use the standard twrp or orangefox or shrp recovery.zip if you want to keep a custom recovery installed
Credits again to @Sapper Morton for creating this Android 10 flashable image
Click to expand...
Click to collapse
Yes, i've already flashed but i come back to MIUI for the battery, thanks anyway :good: